Infrastructure Conclusions(?)

[Stefan Bodewig <bo...@apache.org>]

So let me summarize what I sense as result so far:

Source Control
==============

We'll stick with CVS for now and keep our open for all committers
policy.  Rename jakarta-gump to gump.

We may talk about separating code and metadata as well as migrationg
to svn later.

Mailing Lists
=============

Ask for the creation of pmc@gump.apache.org with the initial
subscribers

       * Adam Jack <aj...@apache.org>
       * Davanum Srinivas <di...@apache.org>
       * Leo Simons <le...@apache.org>
       * Martin van den Bemt <mv...@apache.org>       
       * Nick Chalko <ni...@apache.org>
       * Nicola Ken Barozzi <ni...@apache.org>
       * Scott Sanders <sa...@apache.org> 
       * Stefan Bodewig <bo...@apache.org>
       * Stefano Mazzocchi <st...@apache.org>

subscription moderated, moderators would be me and Adam (is that OK
with you, Adam?)

Since we don't have any official announcement of the board decision
yet, I simply assume that there haven't been any changes to the PMC
list we proposed.

Ask for general@gump.apache.org - the list should be the same as
gump@jakarta.apache.org (all subscribers transfered, same moderators,
archives being carried over, old address forwards to the new for some
time).

I originally proposed dev@gump but think Leo is right.  Still no
strong opinion though.

We can talk about a separate commits list if traffic becomes too big.

Web-Site
========

Ask for the gump.apache.org virtual host and a new Unix group gump
with the members identical to the current PMC.  /www/gump.apache.org
owned by group gump.

ProxyPass content from moof once there is some content, details can be
hashed out later.

Wiki
====

We can create one ourselves.  After all Leo is the Wiki master and at
least the five ASF members on this PMC are in the apsite group as
well.

Unless there are any objections I'd take this to infrastructure
Tuesday evening.  If consensus is obvious before that, feel free to go
ahead (I'll be offline myself).

Stefan

Re: Infrastructure Conclusions(?)

["Adam R. B. Jack" <aj...@trysybase.com>]

Do we need some form of RDBMS or XML-DB or ????? I am starting to think that
Gumpy needs a view of history in order to detect relationship changes, and
such.

I don't have much preference, I could see us wanting a multitude of store
types at various times, but Python might dictate for us. I've not really
found much in the way of DB support in Python, for any flavours, although I
did find a MySQL library on sourceforge. Furtther, and I wish to respect
Stefano's views on graphs & build a store conducive to those endeavours.
Heck, maybe it is XML in files.

Any thoughts? Also, what is "available" on/internal to Apache?

regards

Adam

Re: Infrastructure Conclusions(?)

["Adam R. B. Jack" <aj...@trysybase.com>]

This seems accurate to me, I'm fine with all of it & being moderator to
things.

I believe I can update JIRA configuration (as Admin, without needing help
from infra@) when the new mailing lists are created.

regards

Adam
----- Original Message ----- 
From: "Stefan Bodewig" <bo...@apache.org>
To: <gu...@jakarta.apache.org>
Sent: Friday, February 20, 2004 1:19 AM
Subject: Infrastructure Conclusions(?)


> So let me summarize what I sense as result so far:
>
> Source Control
> ==============
>
> We'll stick with CVS for now and keep our open for all committers
> policy.  Rename jakarta-gump to gump.
>
> We may talk about separating code and metadata as well as migrationg
> to svn later.
>
> Mailing Lists
> =============
>
> Ask for the creation of pmc@gump.apache.org with the initial
> subscribers
>
>        * Adam Jack <aj...@apache.org>
>        * Davanum Srinivas <di...@apache.org>
>        * Leo Simons <le...@apache.org>
>        * Martin van den Bemt <mv...@apache.org>
>        * Nick Chalko <ni...@apache.org>
>        * Nicola Ken Barozzi <ni...@apache.org>
>        * Scott Sanders <sa...@apache.org>
>        * Stefan Bodewig <bo...@apache.org>
>        * Stefano Mazzocchi <st...@apache.org>
>
> subscription moderated, moderators would be me and Adam (is that OK
> with you, Adam?)
>
> Since we don't have any official announcement of the board decision
> yet, I simply assume that there haven't been any changes to the PMC
> list we proposed.
>
> Ask for general@gump.apache.org - the list should be the same as
> gump@jakarta.apache.org (all subscribers transfered, same moderators,
> archives being carried over, old address forwards to the new for some
> time).
>
> I originally proposed dev@gump but think Leo is right.  Still no
> strong opinion though.
>
> We can talk about a separate commits list if traffic becomes too big.
>
> Web-Site
> ========
>
> Ask for the gump.apache.org virtual host and a new Unix group gump
> with the members identical to the current PMC.  /www/gump.apache.org
> owned by group gump.
>
> ProxyPass content from moof once there is some content, details can be
> hashed out later.
>
> Wiki
> ====
>
> We can create one ourselves.  After all Leo is the Wiki master and at
> least the five ASF members on this PMC are in the apsite group as
> well.
>
> Unless there are any objections I'd take this to infrastructure
> Tuesday evening.  If consensus is obvious before that, feel free to go
> ahead (I'll be offline myself).
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: gump-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: gump-help@jakarta.apache.org
>