> From: Scott Eade <[EMAIL PROTECTED]> > > I am now proceeding with the following steps: > 1. Organizing for an apache.org domain to point to the werken.com Scarab > instance. > 2. Updating the project.xml files for the above projects to point to the > werken.com Scarab instance (depending on how difficult it becomes to > establish the apache.org domain name it may be necessary to point these to > the werken.com address as an interim step). > 3. Organizing for bugzilla to no longer accept turbine issues. > 4. If someone can provide me with the admin userid for the Scarab instance > at issues.apache.org/scarab I will flag the unused modules over there as > deleted.
I published this list of steps over on [EMAIL PROTECTED] and received a response from Pier Fumagalli that indicated that if we want it we can get the necessary karma to maintain the Scarab instance at issues.apache.org/scarab (this is actually the nagoya box). I think we would all prefer to have only a single scarab install, but which one will it be and which project will suffer. Here is the choice: Either: 1: Stick to the migration plan outlined above and try and convince the OJB guys to join the other turbine projects over at scarab.werken.com. Or 2: Update the issues.apache.org/scarab instance and migrate the torque issues over from werken.com. While opinions from everyone are most welcome, I think this decision really lies in the hands of Stephen Haberman and John McNally - the people that volunteered to maintain the scarab install. I'll just sit on my hands until I hear from these two. Cheers, Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
