Mike Gerdts wrote:
> Having a place where there is a low barrier
> to entry (without distinction between project and community) would be
> a very good thing.
> The focus should be on...
>
> - Get up and productive quickly
> - Gentle introduction to bureaucracy
> - Set time line to be absorbed by existing community, form a new
> community, or disband
>
I really like your ordering - it "feels" much more friendly to
innovation and experimentation and growing:
1) Get the code out there
2) Get a web/email presence working
3) Start building a community around your work
4) Figure out where you fit in OS.o and make a proposal
This is markedly different from what OS.o currently does:
1) Start building a community around your work
(with no presence on OS.o to anchor things)
2) Figure out where you fit in OS.o and make a proposal
(with no understanding of OS.o's bureaucracy...)
3) Put up with the ratholing and nitpicking and arguing
from people who don't know anything about your effort
about whether your effort is worthy...
4) Don't give up in frustration
5) Get a web/email presence working
6) Get the code out there
-John
