[Vote Results] Moving commons-sql to db.apache.org (repost)

[Thomas Dudziak <to...@first.fhg.de>]

Hi all,

two weeks ago I started a vote about moving commons-sql from jakarta 
commons to db. Here are the results:

+1    : 9 votes
+/-0  : 0 votes
-1    : 0 votes

with two remarks:

* commons-sql should not be moved into db-commons but rather be its own 
project with a non-"commons" name (see below)
* the current db.apache.org committers should get commit rights to the 
new project automatically so as to stipulate work on it as a common base 
component of OJB and Torque

As it seems the vote got a positive result, we can now go on moving the 
project ? Since I'm not aware of how the procedure of moving a project 
between apache 'spaces' is (got to be somewhat similar to making a sub 
project top-level ?), could someone please point it out to me ? Here's 
my impression of what the steps are:

* Define a name for the new db.apache.org project (see remark 1). I'd 
like to name it along the lines DbUtils (which is already taken by 
commons-dbutils, btw), e.g. DbSetupUtils or likewise. Suggestions are 
welcome !

* Ask Infrastructure for creation of a project space (SVN space, mailing 
lists, etc.) in db.apache.org, including giving commit rights to all 
db.apache.org committers (if that is possible)

* Migrate the repository to the new location (e.g. cvs2svn etc.) - 
perhaps infrastructure can do this ?

* Remove the old repository and replace the 'old' website with a page 
that directs to the new website in db.apache.org

Is that about right, or did I forget something ?

regards,
Thomas Dudziak


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org

RE: [Vote Results] Moving commons-sql to db.apache.org (repost)

[Tim O'Brien <to...@discursive.com>]

> > * Ask Infrastructure for creation of a project space (SVN space, mailing
> > lists, etc.) in db.apache.org, including giving commit rights to all
> > db.apache.org committers (if that is possible)
> > 
> > * Migrate the repository to the new location (e.g. cvs2svn etc.) -
> > perhaps infrastructure can do this ?
>
> How about waiting until Commons is in SVN and then we can just svn move it?

Give infrastructure at least a week for this.  Has the DB TLP started moving to SVN yet?

Also, anyone who has previously performed a commit on the commons-sql project should probably be given the option to retain that level of access.

tim

Re: [Vote Results] Moving commons-sql to db.apache.org (repost)

[Henri Yandell <fl...@gmail.com>]

On Wed, 22 Dec 2004 16:20:43 +0100, Thomas Dudziak <to...@first.fhg.de> wrote:

> * Define a name for the new db.apache.org project (see remark 1). I'd
> like to name it along the lines DbUtils (which is already taken by
> commons-dbutils, btw), e.g. DbSetupUtils or likewise. Suggestions are
> welcome !

Heh, when we made DbUtils we wanted to call it commons-sql, but it was
already taken :)

> * Ask Infrastructure for creation of a project space (SVN space, mailing
> lists, etc.) in db.apache.org, including giving commit rights to all
> db.apache.org committers (if that is possible)
> 
> * Migrate the repository to the new location (e.g. cvs2svn etc.) -
> perhaps infrastructure can do this ?

How about waiting until Commons is in SVN and then we can just svn move it?

> * Remove the old repository and replace the 'old' website with a page
> that directs to the new website in db.apache.org

+1

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org