hi,
At 02:06 2/2/01 -0800, Jon Stevens wrote:
>Then you should be suggesting another top level project be created instead
>of creating a pseudo project that is half within Avalon and half within the
>top level namespace.
>
>Just like there is for Jetspeed.
No one else commented on this from PMC so I guess this is general consensus?
ie. 1 Project == 1 Product.
When any project grows such that there is multiple products they should be
split off into multiple projects. Personally I don't see the advantage of
splitting a community like that - especially when the split off project may
not have enough momentum to survive.
While I don't really like the idea of splitting Avalon at the moment if
it's the only option to move forward then so be it ;) To propose the split
do I just go back to Avalon and try to get consensus via vote and then
reapproach here with a proposal? If so does the proposal have to be formal
or can it be informal?
Cheers,
Pete
*-----------------------------------------------------*
| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof." |
| - John Kenneth Galbraith |
*-----------------------------------------------------*
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
