I am OK with the idea of *adopting* Neko and Jing, however, I would like to see those as sub-projects.
As Arnaud mentioned, we've previously discussed the idea of creating a sub-project of NekoHTML, however, the discussion stopped without any outcome. I suggest we refresh our memory on the past suggestions and finally decide what and how many sub-projects we create, including the details on how we manage those. Here is the list of proposals (the ones made in the past and new ones): 1. What is the criteria for creating a sub-project? Should we consider how many committers are interested and willing to work on the sub-project, should we consider user requirements? Where does the vote take place, i.e. xerces-j-dev, xerces-j-user? 2. Sub-project repositories: a) Have separate repositories. b) Add sub-projects under "xml-xerces/java", i.e. "xml-xerces/java/neko", "xml-xerces/java/relaxng". I have a slight preference for this approach. 3. Do we want to create only one sub-project, i.e. "toolbox"? 4. Sub-projects should have its own build file, documentation and jar files, i.e. xerces-neko.jar. 5. Exposing sub projects: a) sub-projects could be linked directly from the xml.apache.org web site b) sub-projects are linked from the Xerces web site. 6. Mailing lists: a) Create a mailing list for developers/users of the sub-project. b) Create one mailing list for all sub-projects. c) Don't create any mailing lists -- use xerces-j-dev/user for discussions. 7. Sub-projects should have its own releases (which don't necessarily match Xerces ones). 8. We should consider separate HTML/WML DOM components from the main Xerces projects. Thank you, -- Elena Litani / IBM Toronto --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
