David Nuescheler wrote: > Hi Jukka, > > Just a random thought. > >> "to move the codebase *and* to bring the mapping tool >> developers in as Jackrabbit committers" > > This is probably stating the obvious (my apologies): > > If there is no precedent that we could align with, then we possibly > could look at this particular case just like any other code contribution. > > Which would mean that the current committers would contribute > their code to the Jackrabbit community and would then follow the > normal path to become committers in the Jackrabbit community. > > While I understand that this would mean that the current > committers are sort of giving up a little bit of their more direct > influence on "their" code (for a while), this may still be a clean > and efficient way of doing it. > > I guess you already had this process in mind and were looking > for more elegant alternatives.
We could take that approach. Or, another approach would be to start viewing the two parts of Graffito as independent podlings (whether they actually separate their mailing lists and other resources though is not relevant/necessary here I think). Then, we can look at how ready the mapping code/community is for graduation, and when ready, graduate it to the Jackrabbit TLP, just like any other incubating project (Jackrabbit PMC vote, incubator PMC vote, etc, etc). Regards, Upayavira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
