Honestly, though, I think a shepherd would be better for the
project... they're good at moving things along. :)
One thing that things like Reactor and any other community OSS
project is always missing is a contributor's guide, a developer's
guide, whatever... something that has at least rudimentary
descriptions of how the different pieces and parts work, and work
together, along with a style guide/code standards, instructions for
sending your code in (if you're not a committer), and any other
relevant information that someone trying to fix bugs or add features
needs to know.
I think having something like that available, and having it be _very
well done_ is going to make a huge difference in the amount of code
we get from everyday users. If you want volunteers to help out with
the code, this is going to be, IMO, critical... especially with
something as complicated as Reactor.
That's my 2 cents.
J
On Sep 18, 2008, at 7:12 AM, Tom Chiverton wrote:
On Thursday 18 Sep 2008, Doug Hughes wrote:
Once we've decided who's going to sheppard this thing I'd make a
public
blog announcement and *hopefully*, some people will volunteer to
help out.
I think what is really needed is, yes, a sheppard to (for instance)
produce a
road map and give people a bit of an incentive to 'scratch their
itch' and
commit some code.
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Reactor for ColdFusion Mailing List
[EMAIL PROTECTED]
Archives at: http://www.mail-archive.com/reactor%40doughughes.net/
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
