[Nitro] Revisiting some Og issues again: RFC
Mark Van De Vyver
mvyver at gmail.com
Mon Nov 26 20:10:05 EST 2007
Reviewing some posts over the last few months, I've made a summary (in
no particular order) and proposal.
I've not quoted names since this i just my impression.
- There is widespread interest in Og as a standalone project.
- Og is incorrectly considered as being bound to Nitro.
- Specs and developer level documentation are scarce.
- Intermediate level documentation of Og is scarce, i.e. for people
wanting to write user level docs.
- Confusion exists about what version of Og is 'current'.
- Confusion exists about what the Og roadmap is.
- Darcs may be a barrier to entry (cf svn, git, mercurial...?).
- Og needs a stable branch and a development branch.
It seems there was some interest in volunteering to help on different
aspects, of the above, but this might have changed over the last few
Is it worth considering setting up something like Og-dev on google
code or some such service, calling that the development branch and
inviting committers, Rubinius style?
This would allow people to tackle any of the above issues they wished to.
Given this would be aimed at the intermediate/developer level much of
the results of this effort would feed into a stable branch as things
are ironed out?
More information about the Nitro-general