A laymans request for advice

[Tom Mahoney]

Greetings,

I realize this may not be the place to ask, if this is the case then
if someone could direct me to another resource it would be
appreciated.

A group of us are about ready to begin a rather largish project that
we want to restrict to the following...

1) The source is open (obviously) but building but building derivitive
works are not. The software is intended to be 'used' for the
purpose(s) for which it was intended, at least until it's matured.

2) Contributions fall under these restrictions.

3) Prohibit anyone but the copyright holder(s) from making money from
the software (the software will probably be free, but we want to
prohibit anyone else from making money on what we intended to be a
free product). Commercial licenses would be available (duel-license?)
upon approval.

The main reasoning behind our project is that it has the ability to
become too diluted in its early stages, we need to stick to a rapidly
evolving standard without the overhead of supporting product(s) based
on our code (or formats, protocols) that don't "keep up" with our
changes, etc.

On the other hand, we'd like to open the source rather than use a
commercial license because we'd like to reach a wider audience of
advisors and contributors to allow the project to be somewhat
"democratic" in its development and goals. I'm sure you folks have
heard close variations of this question many times, but personally
after much digging I've got more questions than answers.

T.M.