[Nitro] Retrospective and future direction.

Dylan Bruzenak dylanb at digitalvalence.com
Thu Apr 20 03:55:22 EDT 2006

Too bad I'm all questions and no answers ;)  Hopefully as more people 
join more of this can be decentralized.  Maybe there is some way to make 
it easier to review patches ?  Some sort of quick apply and testing or a 
public forum for reading the code...  Awfully late here, so I'm just 
pinging things off the wall.
> As of yet, we haven't had competing contributors. :)
> I think the bottleneck is that I'm currently the only one reviewing
> and applying them. Trying to balance that with fixing bugs when I only
> get a few hours a day to do anything Nitro related just isn't working.
> Reviewing patches is actually a pretty good way of becoming familiar
> with the code base (it's how I started), so if there's anyone
> interested in helping out, please let me know.  :)
> For submitters, tests are expected, whether bugs or enhancements. For
> an enhancement, docs are expected as well.
> --
> "Never tell people how to do things. Tell them what to do and they
> will surprise you with their ingenuity." —General George S. Patton
> _______________________________________________
> Nitro-general mailing list
> Nitro-general at rubyforge.org
> http://rubyforge.org/mailman/listinfo/nitro-general

More information about the Nitro-general mailing list