I have created modules in Scarab (scarab.werken.com/issues) for the turbine projects thus:
Global (GLO) Global > Turbine (TBN) Global > Turbine > Turbine-2 (TTW) Global > Turbine > Turbine-2 > Source (TTWS) Global > Turbine > Turbine-2 > Documentation (TTWD) Global > Turbine > Turbine-3 (TTH) Global > Turbine > Turbine-3 > Source (TTHS) Global > Turbine > Turbine-3 > Documentation (TTHD) Global > Turbine > Turbine Site (TSIT) Global > Turbine > Fulcrum (FUL) Global > Turbine > Fulcrum > Source (FULS) Global > Turbine > Fulcrum > Documentation (FULD) Global > Turbine > TDK (TDK) Global > Turbine > TDK > Source (TDKS) Global > Turbine > TDK > Documentation (TDKD) Global > JCS (JCS) Global > JCS > Source (JCSS) Global > JCS > Documentation (JCSD) Global > Torque (TRQ) Global > Torque > Source (TRQS) Global > Torque > Documentation (TRQD) For the codes (shown in brackets above) I have followed the standard used by the sample projects delivered with Scarab. For those that are curious, "TTW" is Turbine-2 and "TTH" is Turbine-3 (the codes are a maximum of 4 alpha characters). Note that the pre-existing Global > Torque module is now known as Global > Torque > Source and any new issues will be allocated the TRQS prefix (as opposed to TRQ for the existing issues). These modules are available now, but will not appear until you request a role to access them (recommended role type is Developer as I believe Observer does not allow you to modify any issues you create). There are a number of container modules (basically all modules that don't end with "Source" or "Documentation" with the exception of "Turbine Site") that are not intended for direct use - the best thing to do is to not request roles for these modules, that way they will not clutter up your module list. Please recall that Maven is continuing to use the Jira instance at werken.com and OJB is using the un-maintained Scarab instance at issues.apache.org/scarab. I will be sending a note to the relevant dev lists providing them with an update. 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. Help from anyone willing to pitch in on moving the existing issues from bugzilla over to Scarab would be most welcome. 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]>
