I'd never seen the original list that is mentioned in the article, but
one of the entries seemed strikingly relevant to the current situation
with OpenQM:
"Myth #6: If I give away my software to the Open Source community,
thousands of developers will suddenly start working for me for
nothing.
There is no guarantee that simply "dumping" source code on the
community will make a FLOSS project appear, and there have been
several examples of such behavior to be viewed even negatively,
because the community may see this as "garbage dumping" of code. The
reality is that for a collaborative community to form, there must be
first of all a good communication and interaction strategy and effort
in place as a basic requisite. Also, investing in community creation
and dissemination efforts does also increase the probability of a
bidirectional effort sharing. It is important to mention that surveys
like OSSWatch or CIO Insight found a significant proportion of
companies and public administrations (between 14% and 25%) contribute
back patches or participate actively in FLOSS communities."
This sentence defines the critical part of the formula: "The reality
is that for a collaborative community to form, there must be first of
all a good communication and interaction strategy and effort in place
as a basic requisite."
I imagine many of you will see this as beating a dead horse, but I
just wanted to point out that I'm not a sole voice in how the lack of
promotion could cause a project to fall flat.
I no longer have time available to work on OpenQM as I'd hoped, but my
offer of free hosting on either a Windows or Linux server still
stands.
tnx.
g.
> I imagine many of you will see this as beating a dead horse
Yes.
> I no longer have time available to work on OpenQM as I'd hoped
ROFL. Irony at its best.
--
Kevin Powick
Gosh, it must be an incredible strain to be so much better than
everyone else.
You seem to be holding up pretty well though. Good job!
g.
> Gosh, it must be an incredible strain to be so much better than
> everyone else.
Non sequitur
--
Kevin Powick