So what do we have:
* Source Control ================
We can stick with CVS or switch over to SVN now that the 1.0 release of SVN seems near (rumors say next week). If we switch to SVN it may become more difficult for other Apache committers to contribute, I'm not sure.
If we stick with CVS, we simply should as infrastructure to
mv jakarta-gump gump
IMHO.
jakarta-gump CVS is still linked to jakarta-alexandria. Since alexadria should be tarred up and since SVN will be released soon, I am +1 to SVN and -1 to CVS.
Do we want to keep our current policy of "every ASF committer can commit to Gump"?
Yes, and AFAIK also the majority of others already said they support it.
* Website =========
Somebody will have to come up with a forrest skin for gump.apache.org and maybe tweak our current site to make it stand alone. I don't feel forrest savvy enough to even think about doing so. 8-)
Ok, then me works on this :-)
I'll use the new krysalis-site skin with a Gump color scheme.
If there are designers listening, please take the Forrest site, make a hardcopy of it, and change the colors for Gump. In this way we can decide on a color scheme and I can put it in :-)
I'd have karma for jakarta-site to make the changes there once our new site is up.
We should ask for a virtual host on minotaur for the site IMHO. Once we have gump builds on a different ASF machine, we can always ProxyPass the results into the gump.apache.org URI space if we want to.
* mailing list(s) =================
move [EMAIL PROTECTED] to [EMAIL PROTECTED] or is there a better name?
[EMAIL PROTECTED] +1
This also involves adapting eyebrowse and JIRA. Adam, can you change the JIRA configuration as admin or do we need infrastructure help?
Any other lists we'd initially want? Split commit messages from the rest?
IMHO no, not yet. Hmmm, wait.
IMHO, as has already been proposed, we should separate the code and the metadata in two different dirs. In this way we can make the metadata commits go to [EMAIL PROTECTED] while all code commits go to [EMAIL PROTECTED]
* JIRA ======
Apart from changing the mailing list, is there anything else we'd need to do?
* Wiki ======
The old Wiki has been used for the Newsletter reports IIRC, do we want a Wiki for Gump?
Yes. It makes it very easy to add docs, and we still keep oversight.
IMHO wiki diffs should go to the dev list, but I'm ok also for the commit list.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
