infrastructure work for TLP move

classic Classic list List threaded Threaded
17 messages Options
Reply | Threaded
Open this post in threaded view
|

infrastructure work for TLP move

Torsten Curdt
I've prepared the TODO for the infrastructure work. Please cross-
check and give feedback. I am not sure how we want to handle the wiki  
migration.

cheers

--
The board has agreed to create the Commons project. (Please note that  
there has been a previous commons TLP)

To aid in the process, would the Infrastructure team please do the  
following:

#=======================================

[1] Root Tasks

Create unix group "commons". If it already exists remove previous  
members.

Add following usernames to group "commons":

bayard
jochen
imario
scolebourne
dennisl
niallp
mvdb
ozeigermann
joehni
oheger
mbenson
martinc
psteitz
tcurdt
dfs
rwinston
luc
pietsch
dion
brentworden
skitching
rahul

Verify that domain "commons.apache.org" is correctly setup.


#=======================================
[1] Mailing List

(i) addresses

     I. [hidden email]

         * Henri Yandell                <[hidden email]>
         * Jochen Wiedmann              <[hidden email]>
         * Mario Ivankovits             <[hidden email]>
         * Stephen Colebourne           <[hidden email]>
         * Dennis Lundberg              <[hidden email]>
         * Niall Pemberton              <[hidden email]>
         * Martin van den Bemt          <[hidden email]>
         * Oliver Zeigermann            <[hidden email]>
         * Jörg Schaible                <[hidden email]>
         * Oliver Heger                 <[hidden email]>
         * Matt Benson                  <[hidden email]>
         * Martin Cooper                <[hidden email]>
         * Phil Steitz                  <[hidden email]>
         * Torsten Curdt                <[hidden email]>
         * Daniel Savarese              <[hidden email]>
         * Rory Winston                 <[hidden email]>
         * Luc Maisonobe                <[hidden email]>
         * Joerg Pietschmann            <[hidden email]>
         * Dion Gillard                 <[hidden email]>
         * Brent Worden                 <[hidden email]>
         * Simon Kitching               <[hidden email]>
         * Rahul Akolkar                <[hidden email]>


    II. [hidden email]  migrate subscribers from  commons-
[hidden email]
   III. [hidden email]  migrate subscribers from  commons-
[hidden email]
NOTE: if possible forward [hidden email] to  
[hidden email]

(ii) remote moderators ...

   As this is a migration of the mailing list the current moderators  
will take over on the different domain.

(iii) archives

    I. http://commons.apache.org/mail/commons/user/YYYYMM.gz
   II. http://commons.apache.org/mail/commons/dev/YYYYMM.gz
III. private@commons to be archived in the private area.

(iv) options

    I. Reply-To: Header [X] yes [ ] no
   II. Message Trailer  [X] yes [ ] no

#=======================================
[2] Source Control

(i) Subversion

     Move the existing jakarta/commons tree to TLP

#=======================================
[3] Initial Committer list

bayard
jochen
imario
scolebourne
dennisl
niallp
mvdb
ozeigermann
joehni
oheger
mbenson
martinc
psteitz
tcurdt
dfs
rwinston
luc
pietsch
dion
brentworden
skitching
rahul

#=======================================
[4] Wiki

(i) Wiki pages need to be migrated

     http://wiki.apache.org/jakarta-commons/FrontPage

     This can be done by the community itself.

#=======================================
[5] Bug tracking

(i) Project URLs need to be migrated

     This can be done by the community itself.
---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: infrastructure work for TLP move

sebb-2-2
Does anything need to be done to the SVN authorization file?

There is currently a commons group in it, but it contains only

commons=gstein,jerenkrantz

Presumably all the new commons committers are currently in the jakarta group.
No point removing them (at least at present), but do they need to be
added to the commons group, or does a new commons group need to be
created?

The new SVN parent may need to be added, along with the appropriate rights.

S.
On 27/06/07, Torsten Curdt <[hidden email]> wrote:

> I've prepared the TODO for the infrastructure work. Please cross-
> check and give feedback. I am not sure how we want to handle the wiki
> migration.
>
> cheers
>
> --
> The board has agreed to create the Commons project. (Please note that
> there has been a previous commons TLP)
>
> To aid in the process, would the Infrastructure team please do the
> following:
>
> #=======================================
>
> [1] Root Tasks
>
> Create unix group "commons". If it already exists remove previous
> members.
>
> Add following usernames to group "commons":
>
> bayard
> jochen
> imario
> scolebourne
> dennisl
> niallp
> mvdb
> ozeigermann
> joehni
> oheger
> mbenson
> martinc
> psteitz
> tcurdt
> dfs
> rwinston
> luc
> pietsch
> dion
> brentworden
> skitching
> rahul
>
> Verify that domain "commons.apache.org" is correctly setup.
>
>
> #=======================================
> [1] Mailing List
>
> (i) addresses
>
>     I. [hidden email]
>
>         * Henri Yandell                <[hidden email]>
>         * Jochen Wiedmann              <[hidden email]>
>         * Mario Ivankovits             <[hidden email]>
>         * Stephen Colebourne           <[hidden email]>
>         * Dennis Lundberg              <[hidden email]>
>         * Niall Pemberton              <[hidden email]>
>         * Martin van den Bemt          <[hidden email]>
>         * Oliver Zeigermann            <[hidden email]>
>         * Jörg Schaible                <[hidden email]>
>         * Oliver Heger                 <[hidden email]>
>         * Matt Benson                  <[hidden email]>
>         * Martin Cooper                <[hidden email]>
>         * Phil Steitz                  <[hidden email]>
>         * Torsten Curdt                <[hidden email]>
>         * Daniel Savarese              <[hidden email]>
>         * Rory Winston                 <[hidden email]>
>         * Luc Maisonobe                <[hidden email]>
>         * Joerg Pietschmann            <[hidden email]>
>         * Dion Gillard                 <[hidden email]>
>         * Brent Worden                 <[hidden email]>
>         * Simon Kitching               <[hidden email]>
>         * Rahul Akolkar                <[hidden email]>
>
>
>    II. [hidden email]  migrate subscribers from  commons-
> [hidden email]
>   III. [hidden email]  migrate subscribers from  commons-
> [hidden email]
> NOTE: if possible forward [hidden email] to
> [hidden email]
>
> (ii) remote moderators ...
>
>   As this is a migration of the mailing list the current moderators
> will take over on the different domain.
>
> (iii) archives
>
>    I. http://commons.apache.org/mail/commons/user/YYYYMM.gz
>   II. http://commons.apache.org/mail/commons/dev/YYYYMM.gz
> III. private@commons to be archived in the private area.
>
> (iv) options
>
>    I. Reply-To: Header [X] yes [ ] no
>   II. Message Trailer  [X] yes [ ] no
>
> #=======================================
> [2] Source Control
>
> (i) Subversion
>
>     Move the existing jakarta/commons tree to TLP
>
> #=======================================
> [3] Initial Committer list
>
> bayard
> jochen
> imario
> scolebourne
> dennisl
> niallp
> mvdb
> ozeigermann
> joehni
> oheger
> mbenson
> martinc
> psteitz
> tcurdt
> dfs
> rwinston
> luc
> pietsch
> dion
> brentworden
> skitching
> rahul
>
> #=======================================
> [4] Wiki
>
> (i) Wiki pages need to be migrated
>
>     http://wiki.apache.org/jakarta-commons/FrontPage
>
>     This can be done by the community itself.
>
> #=======================================
> [5] Bug tracking
>
> (i) Project URLs need to be migrated
>
>     This can be done by the community itself.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: infrastructure work for TLP move

Henri Yandell
Personally, my vote would be to say:

commons=committers

Others tend to disagree :)

[though in practice you have to list each committer group
alphabetically as groups aren't nested in the svn auth file]

Hen

On 6/27/07, sebb <[hidden email]> wrote:

> Does anything need to be done to the SVN authorization file?
>
> There is currently a commons group in it, but it contains only
>
> commons=gstein,jerenkrantz
>
> Presumably all the new commons committers are currently in the jakarta group.
> No point removing them (at least at present), but do they need to be
> added to the commons group, or does a new commons group need to be
> created?
>
> The new SVN parent may need to be added, along with the appropriate rights.
>
> S.
> On 27/06/07, Torsten Curdt <[hidden email]> wrote:
> > I've prepared the TODO for the infrastructure work. Please cross-
> > check and give feedback. I am not sure how we want to handle the wiki
> > migration.
> >
> > cheers
> >
> > --
> > The board has agreed to create the Commons project. (Please note that
> > there has been a previous commons TLP)
> >
> > To aid in the process, would the Infrastructure team please do the
> > following:
> >
> > #=======================================
> >
> > [1] Root Tasks
> >
> > Create unix group "commons". If it already exists remove previous
> > members.
> >
> > Add following usernames to group "commons":
> >
> > bayard
> > jochen
> > imario
> > scolebourne
> > dennisl
> > niallp
> > mvdb
> > ozeigermann
> > joehni
> > oheger
> > mbenson
> > martinc
> > psteitz
> > tcurdt
> > dfs
> > rwinston
> > luc
> > pietsch
> > dion
> > brentworden
> > skitching
> > rahul
> >
> > Verify that domain "commons.apache.org" is correctly setup.
> >
> >
> > #=======================================
> > [1] Mailing List
> >
> > (i) addresses
> >
> >     I. [hidden email]
> >
> >         * Henri Yandell                <[hidden email]>
> >         * Jochen Wiedmann              <[hidden email]>
> >         * Mario Ivankovits             <[hidden email]>
> >         * Stephen Colebourne           <[hidden email]>
> >         * Dennis Lundberg              <[hidden email]>
> >         * Niall Pemberton              <[hidden email]>
> >         * Martin van den Bemt          <[hidden email]>
> >         * Oliver Zeigermann            <[hidden email]>
> >         * Jörg Schaible                <[hidden email]>
> >         * Oliver Heger                 <[hidden email]>
> >         * Matt Benson                  <[hidden email]>
> >         * Martin Cooper                <[hidden email]>
> >         * Phil Steitz                  <[hidden email]>
> >         * Torsten Curdt                <[hidden email]>
> >         * Daniel Savarese              <[hidden email]>
> >         * Rory Winston                 <[hidden email]>
> >         * Luc Maisonobe                <[hidden email]>
> >         * Joerg Pietschmann            <[hidden email]>
> >         * Dion Gillard                 <[hidden email]>
> >         * Brent Worden                 <[hidden email]>
> >         * Simon Kitching               <[hidden email]>
> >         * Rahul Akolkar                <[hidden email]>
> >
> >
> >    II. [hidden email]  migrate subscribers from  commons-
> > [hidden email]
> >   III. [hidden email]  migrate subscribers from  commons-
> > [hidden email]
> > NOTE: if possible forward [hidden email] to
> > [hidden email]
> >
> > (ii) remote moderators ...
> >
> >   As this is a migration of the mailing list the current moderators
> > will take over on the different domain.
> >
> > (iii) archives
> >
> >    I. http://commons.apache.org/mail/commons/user/YYYYMM.gz
> >   II. http://commons.apache.org/mail/commons/dev/YYYYMM.gz
> > III. private@commons to be archived in the private area.
> >
> > (iv) options
> >
> >    I. Reply-To: Header [X] yes [ ] no
> >   II. Message Trailer  [X] yes [ ] no
> >
> > #=======================================
> > [2] Source Control
> >
> > (i) Subversion
> >
> >     Move the existing jakarta/commons tree to TLP
> >
> > #=======================================
> > [3] Initial Committer list
> >
> > bayard
> > jochen
> > imario
> > scolebourne
> > dennisl
> > niallp
> > mvdb
> > ozeigermann
> > joehni
> > oheger
> > mbenson
> > martinc
> > psteitz
> > tcurdt
> > dfs
> > rwinston
> > luc
> > pietsch
> > dion
> > brentworden
> > skitching
> > rahul
> >
> > #=======================================
> > [4] Wiki
> >
> > (i) Wiki pages need to be migrated
> >
> >     http://wiki.apache.org/jakarta-commons/FrontPage
> >
> >     This can be done by the community itself.
> >
> > #=======================================
> > [5] Bug tracking
> >
> > (i) Project URLs need to be migrated
> >
> >     This can be done by the community itself.
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: infrastructure work for TLP move

Phil Steitz
On 6/27/07, Henri Yandell <[hidden email]> wrote:
> Personally, my vote would be to say:
>
> commons=committers

You mean all apache committers?  I agree that we should continue the
tradition of granting commons karma to any committer who asks for it.
I don't know much about how this works in svn or what the risk /
downside of auto-granting commons karma to new committers would be,
but I agree with the principle that any ASF committer should be
welcome here.

There are also a lot of current commons committers missing from the
list above.  My preference would be to have them remain commons
committers if that is not too hard to do. In any case, any current
commons committer who wants karma should get it.

Phil

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: infrastructure work for TLP move

Niall Pemberton
On 6/28/07, Phil Steitz <[hidden email]> wrote:

> On 6/27/07, Henri Yandell <[hidden email]> wrote:
> > Personally, my vote would be to say:
> >
> > commons=committers
>
> You mean all apache committers?  I agree that we should continue the
> tradition of granting commons karma to any committer who asks for it.
> I don't know much about how this works in svn or what the risk /
> downside of auto-granting commons karma to new committers would be,
> but I agree with the principle that any ASF committer should be
> welcome here.
>
> There are also a lot of current commons committers missing from the
> list above.  My preference would be to have them remain commons
> committers if that is not too hard to do. In any case, any current
> commons committer who wants karma should get it.

I agree - please lets not remove commit privledge from anyone who
currently has it in Commons.

Niall

> Phil

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: infrastructure work for TLP move

Henri Yandell
On 6/27/07, Niall Pemberton <[hidden email]> wrote:

> On 6/28/07, Phil Steitz <[hidden email]> wrote:
> > On 6/27/07, Henri Yandell <[hidden email]> wrote:
> > > Personally, my vote would be to say:
> > >
> > > commons=committers
> >
> > You mean all apache committers?  I agree that we should continue the
> > tradition of granting commons karma to any committer who asks for it.
> > I don't know much about how this works in svn or what the risk /
> > downside of auto-granting commons karma to new committers would be,
> > but I agree with the principle that any ASF committer should be
> > welcome here.
> >
> > There are also a lot of current commons committers missing from the
> > list above.  My preference would be to have them remain commons
> > committers if that is not too hard to do. In any case, any current
> > commons committer who wants karma should get it.
>
> I agree - please lets not remove commit privledge from anyone who
> currently has it in Commons.

Presuming no one recognizes the social genius of my first proposal,
then I recommend that we make the list of committers be anyone who has
committed in the last 2 years.

Hen

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: infrastructure work for TLP move

Niall Pemberton
On 6/28/07, Henri Yandell <[hidden email]> wrote:

> On 6/27/07, Niall Pemberton <[hidden email]> wrote:
> > On 6/28/07, Phil Steitz <[hidden email]> wrote:
> > > On 6/27/07, Henri Yandell <[hidden email]> wrote:
> > > > Personally, my vote would be to say:
> > > >
> > > > commons=committers
> > >
> > > You mean all apache committers?  I agree that we should continue the
> > > tradition of granting commons karma to any committer who asks for it.
> > > I don't know much about how this works in svn or what the risk /
> > > downside of auto-granting commons karma to new committers would be,
> > > but I agree with the principle that any ASF committer should be
> > > welcome here.
> > >
> > > There are also a lot of current commons committers missing from the
> > > list above.  My preference would be to have them remain commons
> > > committers if that is not too hard to do. In any case, any current
> > > commons committer who wants karma should get it.
> >
> > I agree - please lets not remove commit privledge from anyone who
> > currently has it in Commons.
>
> Presuming no one recognizes the social genius of my first proposal,
> then I recommend that we make the list of committers be anyone who has
> committed in the last 2 years.

Why have you gone from proposing to add any remaining ASF Commiters
that don't currently have access to now removing access from anyone
who hasn't committed in the last two years? This seems a bit random in
principle to me to take one position to open things up one minute and
then another to make it more restrictive the next.

I also dislike arbitrary limits - you choose 2 years - maybe someone
else will prefer 1 year and so on. I still think anyone that currently
has access should keep it and not loose their commit access to
Commons.

Niall

> Hen

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: infrastructure work for TLP move

Niall Pemberton
In reply to this post by Torsten Curdt
On 6/27/07, Torsten Curdt <[hidden email]> wrote:
<snip>

> #=======================================
> [1] Mailing List
>
> (i) addresses
>
>      I. [hidden email]
>
>          * Henri Yandell                <[hidden email]>
>          * Jochen Wiedmann              <[hidden email]>
>          * Mario Ivankovits             <[hidden email]>
>          * Stephen Colebourne           <[hidden email]>
>          * Dennis Lundberg              <[hidden email]>
>          * Niall Pemberton              <[hidden email]>
>          * Martin van den Bemt          <[hidden email]>
>          * Oliver Zeigermann            <[hidden email]>
>          * Jörg Schaible                <[hidden email]>
>          * Oliver Heger                 <[hidden email]>
>          * Matt Benson                  <[hidden email]>
>          * Martin Cooper                <[hidden email]>
>          * Phil Steitz                  <[hidden email]>
>          * Torsten Curdt                <[hidden email]>
>          * Daniel Savarese              <[hidden email]>
>          * Rory Winston                 <[hidden email]>
>          * Luc Maisonobe                <[hidden email]>
>          * Joerg Pietschmann            <[hidden email]>
>          * Dion Gillard                 <[hidden email]>
>          * Brent Worden                 <[hidden email]>
>          * Simon Kitching               <[hidden email]>
>          * Rahul Akolkar                <[hidden email]>
>
>
>     II. [hidden email]  migrate subscribers from  commons-
> [hidden email]
>    III. [hidden email]  migrate subscribers from  commons-
> [hidden email]
> NOTE: if possible forward [hidden email] to
> [hidden email]

My preference is commits@ is not forwarded to dev - makes searching
mail archives easier - also in discussion on splitting the lists in
the past we've talked about having an issues@ list as well. Not sure
what the consensus was, but thats my preference.

Niall

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: infrastructure work for TLP move

Henri Yandell
In reply to this post by Niall Pemberton
On 6/27/07, Niall Pemberton <[hidden email]> wrote:

> On 6/28/07, Henri Yandell <[hidden email]> wrote:
> > On 6/27/07, Niall Pemberton <[hidden email]> wrote:
> > > On 6/28/07, Phil Steitz <[hidden email]> wrote:
> > > > On 6/27/07, Henri Yandell <[hidden email]> wrote:
> > > > > Personally, my vote would be to say:
> > > > >
> > > > > commons=committers
> > > >
> > > > You mean all apache committers?  I agree that we should continue the
> > > > tradition of granting commons karma to any committer who asks for it.
> > > > I don't know much about how this works in svn or what the risk /
> > > > downside of auto-granting commons karma to new committers would be,
> > > > but I agree with the principle that any ASF committer should be
> > > > welcome here.
> > > >
> > > > There are also a lot of current commons committers missing from the
> > > > list above.  My preference would be to have them remain commons
> > > > committers if that is not too hard to do. In any case, any current
> > > > commons committer who wants karma should get it.
> > >
> > > I agree - please lets not remove commit privledge from anyone who
> > > currently has it in Commons.
> >
> > Presuming no one recognizes the social genius of my first proposal,
> > then I recommend that we make the list of committers be anyone who has
> > committed in the last 2 years.
>
> Why have you gone from proposing to add any remaining ASF Commiters
> that don't currently have access to now removing access from anyone
> who hasn't committed in the last two years? This seems a bit random in
> principle to me to take one position to open things up one minute and
> then another to make it more restrictive the next.

Just looking for something simple.

> I also dislike arbitrary limits - you choose 2 years - maybe someone
> else will prefer 1 year and so on. I still think anyone that currently
> has access should keep it and not loose their commit access to
> Commons.

Pondered that one. We could keep the commons commit list as the
jakarta group. Seemed a bit odd though.

Hen

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: infrastructure work for TLP move

Martin van den Bemt
In reply to this post by Niall Pemberton
Agree with Niall..

Archives are pretty much unusable with commits messages and jira issues..

Mvgr,
Martin

Niall Pemberton wrote:

> On 6/27/07, Torsten Curdt <[hidden email]> wrote:
> <snip>
>> #=======================================
>> [1] Mailing List
>>
>> (i) addresses
>>
>>      I. [hidden email]
>>
>>          * Henri Yandell                <[hidden email]>
>>          * Jochen Wiedmann              <[hidden email]>
>>          * Mario Ivankovits             <[hidden email]>
>>          * Stephen Colebourne           <[hidden email]>
>>          * Dennis Lundberg              <[hidden email]>
>>          * Niall Pemberton              <[hidden email]>
>>          * Martin van den Bemt          <[hidden email]>
>>          * Oliver Zeigermann            <[hidden email]>
>>          * Jörg Schaible                <[hidden email]>
>>          * Oliver Heger                 <[hidden email]>
>>          * Matt Benson                  <[hidden email]>
>>          * Martin Cooper                <[hidden email]>
>>          * Phil Steitz                  <[hidden email]>
>>          * Torsten Curdt                <[hidden email]>
>>          * Daniel Savarese              <[hidden email]>
>>          * Rory Winston                 <[hidden email]>
>>          * Luc Maisonobe                <[hidden email]>
>>          * Joerg Pietschmann            <[hidden email]>
>>          * Dion Gillard                 <[hidden email]>
>>          * Brent Worden                 <[hidden email]>
>>          * Simon Kitching               <[hidden email]>
>>          * Rahul Akolkar                <[hidden email]>
>>
>>
>>     II. [hidden email]  migrate subscribers from  commons-
>> [hidden email]
>>    III. [hidden email]  migrate subscribers from  commons-
>> [hidden email]
>> NOTE: if possible forward [hidden email] to
>> [hidden email]
>
> My preference is commits@ is not forwarded to dev - makes searching
> mail archives easier - also in discussion on splitting the lists in
> the past we've talked about having an issues@ list as well. Not sure
> what the consensus was, but thats my preference.
>
> Niall
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: infrastructure work for TLP move

Martin van den Bemt
In reply to this post by Henri Yandell
I don't see a problem in doing the last 2 years, which kind of gives us a nice clean "committer"
base and if we miss people, they simply need to ask for it.
Another options is just copy & pasting the jakarta committers block from asf-authorization, that way
you know everyone who has access, still has access..

Mvgr,
Martin

Henri Yandell wrote:

> On 6/27/07, Niall Pemberton <[hidden email]> wrote:
>> On 6/28/07, Henri Yandell <[hidden email]> wrote:
>> > On 6/27/07, Niall Pemberton <[hidden email]> wrote:
>> > > On 6/28/07, Phil Steitz <[hidden email]> wrote:
>> > > > On 6/27/07, Henri Yandell <[hidden email]> wrote:
>> > > > > Personally, my vote would be to say:
>> > > > >
>> > > > > commons=committers
>> > > >
>> > > > You mean all apache committers?  I agree that we should continue
>> the
>> > > > tradition of granting commons karma to any committer who asks
>> for it.
>> > > > I don't know much about how this works in svn or what the risk /
>> > > > downside of auto-granting commons karma to new committers would be,
>> > > > but I agree with the principle that any ASF committer should be
>> > > > welcome here.
>> > > >
>> > > > There are also a lot of current commons committers missing from the
>> > > > list above.  My preference would be to have them remain commons
>> > > > committers if that is not too hard to do. In any case, any current
>> > > > commons committer who wants karma should get it.
>> > >
>> > > I agree - please lets not remove commit privledge from anyone who
>> > > currently has it in Commons.
>> >
>> > Presuming no one recognizes the social genius of my first proposal,
>> > then I recommend that we make the list of committers be anyone who has
>> > committed in the last 2 years.
>>
>> Why have you gone from proposing to add any remaining ASF Commiters
>> that don't currently have access to now removing access from anyone
>> who hasn't committed in the last two years? This seems a bit random in
>> principle to me to take one position to open things up one minute and
>> then another to make it more restrictive the next.
>
> Just looking for something simple.
>
>> I also dislike arbitrary limits - you choose 2 years - maybe someone
>> else will prefer 1 year and so on. I still think anyone that currently
>> has access should keep it and not loose their commit access to
>> Commons.
>
> Pondered that one. We could keep the commons commit list as the
> jakarta group. Seemed a bit odd though.
>
> Hen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: infrastructure work for TLP move

Stephen Colebourne
In reply to this post by Torsten Curdt
I also would strongly prefer to use this opportunity to create a commits list and an issues list.

Commons is big enough to need it, and it would increase the signal to noise on the main list, especially when searching.

Stephen


----- Original Message ----
From: Martin van den Bemt <[hidden email]>
> Agree with Niall..
>
> Archives are pretty much unusable with commits messages and jira issues..
>





---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: infrastructure work for TLP move

Henri Yandell
+1.

On 6/28/07, Stephen Colebourne <[hidden email]> wrote:

> I also would strongly prefer to use this opportunity to create a commits list and an issues list.
>
> Commons is big enough to need it, and it would increase the signal to noise on the main list, especially when searching.
>
> Stephen
>
>
> ----- Original Message ----
> From: Martin van den Bemt <[hidden email]>
> > Agree with Niall..
> >
> > Archives are pretty much unusable with commits messages and jira issues..
> >
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: infrastructure work for TLP move

Dennis Lundberg-2
In reply to this post by Stephen Colebourne
+1

Stephen Colebourne wrote:

> I also would strongly prefer to use this opportunity to create a commits list and an issues list.
>
> Commons is big enough to need it, and it would increase the signal to noise on the main list, especially when searching.
>
> Stephen
>
>
> ----- Original Message ----
> From: Martin van den Bemt <[hidden email]>
>> Agree with Niall..
>>
>> Archives are pretty much unusable with commits messages and jira issues..
>>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


--
Dennis Lundberg

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: infrastructure work for TLP move

Torsten Curdt
In reply to this post by Martin van den Bemt
Same here. I think 2 years is reasonable. They can ask to get commit  
rights back at any time.

Henry, care to compile the list? Didn't you have some scripts for  
that already? :)

cheers
--
Torsten


On 28.06.2007, at 10:14, Martin van den Bemt wrote:

> I don't see a problem in doing the last 2 years, which kind of  
> gives us a nice clean "committer"
> base and if we miss people, they simply need to ask for it.
> Another options is just copy & pasting the jakarta committers block  
> from asf-authorization, that way
> you know everyone who has access, still has access..
>
> Mvgr,
> Martin
>
> Henri Yandell wrote:
>> On 6/27/07, Niall Pemberton <[hidden email]> wrote:
>>> On 6/28/07, Henri Yandell <[hidden email]> wrote:
>>>> On 6/27/07, Niall Pemberton <[hidden email]> wrote:
>>>>> On 6/28/07, Phil Steitz <[hidden email]> wrote:
>>>>>> On 6/27/07, Henri Yandell <[hidden email]> wrote:
>>>>>>> Personally, my vote would be to say:
>>>>>>>
>>>>>>> commons=committers
>>>>>>
>>>>>> You mean all apache committers?  I agree that we should continue
>>> the
>>>>>> tradition of granting commons karma to any committer who asks
>>> for it.
>>>>>> I don't know much about how this works in svn or what the risk /
>>>>>> downside of auto-granting commons karma to new committers  
>>>>>> would be,
>>>>>> but I agree with the principle that any ASF committer should be
>>>>>> welcome here.
>>>>>>
>>>>>> There are also a lot of current commons committers missing  
>>>>>> from the
>>>>>> list above.  My preference would be to have them remain commons
>>>>>> committers if that is not too hard to do. In any case, any  
>>>>>> current
>>>>>> commons committer who wants karma should get it.
>>>>>
>>>>> I agree - please lets not remove commit privledge from anyone who
>>>>> currently has it in Commons.
>>>>
>>>> Presuming no one recognizes the social genius of my first proposal,
>>>> then I recommend that we make the list of committers be anyone  
>>>> who has
>>>> committed in the last 2 years.
>>>
>>> Why have you gone from proposing to add any remaining ASF Commiters
>>> that don't currently have access to now removing access from anyone
>>> who hasn't committed in the last two years? This seems a bit  
>>> random in
>>> principle to me to take one position to open things up one minute  
>>> and
>>> then another to make it more restrictive the next.
>>
>> Just looking for something simple.
>>
>>> I also dislike arbitrary limits - you choose 2 years - maybe someone
>>> else will prefer 1 year and so on. I still think anyone that  
>>> currently
>>> has access should keep it and not loose their commit access to
>>> Commons.
>>
>> Pondered that one. We could keep the commons commit list as the
>> jakarta group. Seemed a bit odd though.
>>
>> Hen
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: infrastructure work for TLP move

Paul Libbrecht
In reply to this post by Torsten Curdt
Hello Torsten,

indeed... I just wanted to avoid making noise there... but in any  
case... I might be out of the two years window but I would wish to  
keep jelly committership, my ASF user-name is polx.

I would also favour splitting the lists so that commits and jira  
mails come separately but we need to care that they are properly  
advertised and that it is indicated on dev and users that such mails  
are elsewhere.

Also be sure that announces of such (mail-list splitting,  
committership overtake, ...) is announced as a separate mail... such  
long threads as this one needs more hand-pealing.

thanks

paul


Le 1 juil. 07 à 02:32, Torsten Curdt a écrit :

> I think it's clear that old committers can get back access at any  
> time. That's for sure.
> But could you bring this up on commons-dev? We probably should send  
> around an announcement for that.
>
> cheers
> --
> Torsten
>
> On 28.06.2007, at 00:31, Paul Libbrecht wrote:
>
>> if I dare request, I would prefer to keep committership even  
>> though my activities haven't been greatly active in jelly.
>> Similarly, I think, for Peter Royal.
>>
>> paul
>>
>>
>>
>> Le 27 juin 07 à 17:52, Torsten Curdt a écrit :
>>
>>> I've prepared the TODO for the infrastructure work. Please cross-
>>> check and give feedback. I am not sure how we want to handle the  
>>> wiki migration.
>>>
>>> cheers
>>>
>>> --
>>> The board has agreed to create the Commons project. (Please note  
>>> that there has been a previous commons TLP)
>>>
>>> To aid in the process, would the Infrastructure team please do  
>>> the following:
>>>
>>> #=======================================
>>>
>>> [1] Root Tasks
>>>
>>> Create unix group "commons". If it already exists remove previous  
>>> members.
>>>
>>> Add following usernames to group "commons":
>>>
>>> bayard
>>> jochen
>>> imario
>>> scolebourne
>>> dennisl
>>> niallp
>>> mvdb
>>> ozeigermann
>>> joehni
>>> oheger
>>> mbenson
>>> martinc
>>> psteitz
>>> tcurdt
>>> dfs
>>> rwinston
>>> luc
>>> pietsch
>>> dion
>>> brentworden
>>> skitching
>>> rahul
>>>
>>> Verify that domain "commons.apache.org" is correctly setup.
>>>
>>>
>>> #=======================================
>>> [1] Mailing List
>>>
>>> (i) addresses
>>>
>>>     I. [hidden email]
>>>
>>>         * Henri Yandell                <[hidden email]>
>>>         * Jochen Wiedmann              <[hidden email]>
>>>         * Mario Ivankovits             <[hidden email]>
>>>         * Stephen Colebourne           <[hidden email]>
>>>         * Dennis Lundberg              <[hidden email]>
>>>         * Niall Pemberton              <[hidden email]>
>>>         * Martin van den Bemt          <[hidden email]>
>>>         * Oliver Zeigermann            <[hidden email]>
>>>         * Jörg Schaible                <[hidden email]>
>>>         * Oliver Heger                 <[hidden email]>
>>>         * Matt Benson                  <[hidden email]>
>>>         * Martin Cooper                <[hidden email]>
>>>         * Phil Steitz                  <[hidden email]>
>>>         * Torsten Curdt                <[hidden email]>
>>>         * Daniel Savarese              <[hidden email]>
>>>         * Rory Winston                 <[hidden email]>
>>>         * Luc Maisonobe                <[hidden email]>
>>>         * Joerg Pietschmann            <[hidden email]>
>>>         * Dion Gillard                 <[hidden email]>
>>>         * Brent Worden                 <[hidden email]>
>>>         * Simon Kitching               <[hidden email]>
>>>         * Rahul Akolkar                <[hidden email]>
>>>
>>>
>>>    II. [hidden email]  migrate subscribers from  commons-
>>> [hidden email]
>>>   III. [hidden email]  migrate subscribers from  commons-
>>> [hidden email]
>>> NOTE: if possible forward [hidden email] to  
>>> [hidden email]
>>>
>>> (ii) remote moderators ...
>>>
>>>   As this is a migration of the mailing list the current  
>>> moderators will take over on the different domain.
>>>
>>> (iii) archives
>>>
>>>    I. http://commons.apache.org/mail/commons/user/YYYYMM.gz
>>>   II. http://commons.apache.org/mail/commons/dev/YYYYMM.gz
>>> III. private@commons to be archived in the private area.
>>>
>>> (iv) options
>>>
>>>    I. Reply-To: Header [X] yes [ ] no
>>>   II. Message Trailer  [X] yes [ ] no
>>>
>>> #=======================================
>>> [2] Source Control
>>>
>>> (i) Subversion
>>>
>>>     Move the existing jakarta/commons tree to TLP
>>>
>>> #=======================================
>>> [3] Initial Committer list
>>>
>>> bayard
>>> jochen
>>> imario
>>> scolebourne
>>> dennisl
>>> niallp
>>> mvdb
>>> ozeigermann
>>> joehni
>>> oheger
>>> mbenson
>>> martinc
>>> psteitz
>>> tcurdt
>>> dfs
>>> rwinston
>>> luc
>>> pietsch
>>> dion
>>> brentworden
>>> skitching
>>> rahul
>>>
>>> #=======================================
>>> [4] Wiki
>>>
>>> (i) Wiki pages need to be migrated
>>>
>>>     http://wiki.apache.org/jakarta-commons/FrontPage
>>>
>>>     This can be done by the community itself.
>>>
>>> #=======================================
>>> [5] Bug tracking
>>>
>>> (i) Project URLs need to be migrated
>>>
>>>     This can be done by the community itself.
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>>
>


smime.p7s (2K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: infrastructure work for TLP move

diongillard
I'll heartily second Paul's request, he's an integral part of the Jelly
team.

On 7/2/07, Paul Libbrecht <[hidden email]> wrote:

>
> Hello Torsten,
>
> indeed... I just wanted to avoid making noise there... but in any
> case... I might be out of the two years window but I would wish to
> keep jelly committership, my ASF user-name is polx.
>
> I would also favour splitting the lists so that commits and jira
> mails come separately but we need to care that they are properly
> advertised and that it is indicated on dev and users that such mails
> are elsewhere.
>
> Also be sure that announces of such (mail-list splitting,
> committership overtake, ...) is announced as a separate mail... such
> long threads as this one needs more hand-pealing.
>
> thanks
>
> paul
>
>
> Le 1 juil. 07 à 02:32, Torsten Curdt a écrit :
>
> > I think it's clear that old committers can get back access at any
> > time. That's for sure.
> > But could you bring this up on commons-dev? We probably should send
> > around an announcement for that.
> >
> > cheers
> > --
> > Torsten
> >
> > On 28.06.2007, at 00:31, Paul Libbrecht wrote:
> >
> >> if I dare request, I would prefer to keep committership even
> >> though my activities haven't been greatly active in jelly.
> >> Similarly, I think, for Peter Royal.
> >>
> >> paul
> >>
> >>
> >>
> >> Le 27 juin 07 à 17:52, Torsten Curdt a écrit :
> >>
> >>> I've prepared the TODO for the infrastructure work. Please cross-
> >>> check and give feedback. I am not sure how we want to handle the
> >>> wiki migration.
> >>>
> >>> cheers
> >>>
> >>> --
> >>> The board has agreed to create the Commons project. (Please note
> >>> that there has been a previous commons TLP)
> >>>
> >>> To aid in the process, would the Infrastructure team please do
> >>> the following:
> >>>
> >>> #=======================================
> >>>
> >>> [1] Root Tasks
> >>>
> >>> Create unix group "commons". If it already exists remove previous
> >>> members.
> >>>
> >>> Add following usernames to group "commons":
> >>>
> >>> bayard
> >>> jochen
> >>> imario
> >>> scolebourne
> >>> dennisl
> >>> niallp
> >>> mvdb
> >>> ozeigermann
> >>> joehni
> >>> oheger
> >>> mbenson
> >>> martinc
> >>> psteitz
> >>> tcurdt
> >>> dfs
> >>> rwinston
> >>> luc
> >>> pietsch
> >>> dion
> >>> brentworden
> >>> skitching
> >>> rahul
> >>>
> >>> Verify that domain "commons.apache.org" is correctly setup.
> >>>
> >>>
> >>> #=======================================
> >>> [1] Mailing List
> >>>
> >>> (i) addresses
> >>>
> >>>     I. [hidden email]
> >>>
> >>>         * Henri Yandell                <[hidden email]>
> >>>         * Jochen Wiedmann              <[hidden email]>
> >>>         * Mario Ivankovits             <[hidden email]>
> >>>         * Stephen Colebourne           <[hidden email]>
> >>>         * Dennis Lundberg              <[hidden email]>
> >>>         * Niall Pemberton              <[hidden email]>
> >>>         * Martin van den Bemt          <[hidden email]>
> >>>         * Oliver Zeigermann            <[hidden email]>
> >>>         * Jörg Schaible                <[hidden email]>
> >>>         * Oliver Heger                 <[hidden email]>
> >>>         * Matt Benson                  <[hidden email]>
> >>>         * Martin Cooper                <[hidden email]>
> >>>         * Phil Steitz                  <[hidden email]>
> >>>         * Torsten Curdt                <[hidden email]>
> >>>         * Daniel Savarese              <[hidden email]>
> >>>         * Rory Winston                 <[hidden email]>
> >>>         * Luc Maisonobe                <[hidden email]>
> >>>         * Joerg Pietschmann            <[hidden email]>
> >>>         * Dion Gillard                 <[hidden email]>
> >>>         * Brent Worden                 <[hidden email]>
> >>>         * Simon Kitching               <[hidden email]>
> >>>         * Rahul Akolkar                <[hidden email]>
> >>>
> >>>
> >>>    II. [hidden email]  migrate subscribers from  commons-
> >>> [hidden email]
> >>>   III. [hidden email]  migrate subscribers from  commons-
> >>> [hidden email]
> >>> NOTE: if possible forward [hidden email] to
> >>> [hidden email]
> >>>
> >>> (ii) remote moderators ...
> >>>
> >>>   As this is a migration of the mailing list the current
> >>> moderators will take over on the different domain.
> >>>
> >>> (iii) archives
> >>>
> >>>    I. http://commons.apache.org/mail/commons/user/YYYYMM.gz
> >>>   II. http://commons.apache.org/mail/commons/dev/YYYYMM.gz
> >>> III. private@commons to be archived in the private area.
> >>>
> >>> (iv) options
> >>>
> >>>    I. Reply-To: Header [X] yes [ ] no
> >>>   II. Message Trailer  [X] yes [ ] no
> >>>
> >>> #=======================================
> >>> [2] Source Control
> >>>
> >>> (i) Subversion
> >>>
> >>>     Move the existing jakarta/commons tree to TLP
> >>>
> >>> #=======================================
> >>> [3] Initial Committer list
> >>>
> >>> bayard
> >>> jochen
> >>> imario
> >>> scolebourne
> >>> dennisl
> >>> niallp
> >>> mvdb
> >>> ozeigermann
> >>> joehni
> >>> oheger
> >>> mbenson
> >>> martinc
> >>> psteitz
> >>> tcurdt
> >>> dfs
> >>> rwinston
> >>> luc
> >>> pietsch
> >>> dion
> >>> brentworden
> >>> skitching
> >>> rahul
> >>>
> >>> #=======================================
> >>> [4] Wiki
> >>>
> >>> (i) Wiki pages need to be migrated
> >>>
> >>>     http://wiki.apache.org/jakarta-commons/FrontPage
> >>>
> >>>     This can be done by the community itself.
> >>>
> >>> #=======================================
> >>> [5] Bug tracking
> >>>
> >>> (i) Project URLs need to be migrated
> >>>
> >>>     This can be done by the community itself.
> >>> --------------------------------------------------------------------
> >>> -
> >>> To unsubscribe, e-mail: [hidden email]
> >>> For additional commands, e-mail: [hidden email]
> >>>
> >>
> >
>
>
>


--
dIon Gillard
Rule #131 of Acquisition: Information is Profit.