You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Henri Yandell <fl...@gmail.com> on 2011/04/29 07:34:33 UTC
OGNL Infrastructure questions
Below is a thread from the Commons Dev list in which I'm recommending
that OGNL use the commons dev mailing list and that the svn
permissions allow the ognl committers and the commons committers to
have read write access.
http://commons.markmail.org/thread/ku3ouuilpiicb5is
Is this a concern for anyone?
OGNL's target is to graduate into Commons rather than to TLP, so
making it act like a TLP seems destined to cause problems.
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: OGNL Infrastructure questions
Posted by Simone Tripodi <si...@apache.org>.
Hi Christian!!!
it makes a lot of sense, IMHO, it should maintain the stability of
both ecosystems!
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Mon, May 2, 2011 at 8:26 AM, Christian Grobmeier <gr...@gmail.com> wrote:
>> My issue (for the commons PMC I guess) is how committer votes will
>> happen when OGNL graduates.
>>
>> After graduation, how would one of the current contributors propose a
>> new committer if they are not themselves on the Commons PMC?
>
> Proposal:
>
> - If you are a Commons PMC Member, you are an OGNL PPMC member by default
> - If a Committer is invited to the PPMC, an additional vote on Commons
> PMC is necessary, b/c he will join the Commons PMC after graduation by
> default
> - A contributor can be proposed by anybody - its up to the PPMC to open the vote
> - A new Committer can be elected by the PPMC with binding votes; as
> usual other Committers can vote unbinding. I don't think it creates
> any problems b/c usually there is already a consens on adding a person
> before calling a vote.
>
> Makes sense?
>
> Cheers
> Christian
>
>
>
>
>>
>> Upayavira
>>
>> On Sun, 01 May 2011 19:56 +0200, "Simone Tripodi"
>> <si...@apache.org> wrote:
>>> Hi Upayavira!!!
>>> I agree that commons folks can have rw rights, so people are already
>>> used to co-work in the 'commons way'.
>>> Moreover, I agreed on joining
>>>
>>> - dev@commons.a.o
>>> - users@commons.a.o
>>> - issues@commons.a.o
>>> - create the private ML where commons PMCs can join.
>>>
>>> Does it make sense?
>>> Simo
>>>
>>> http://people.apache.org/~simonetripodi/
>>> http://www.99soft.org/
>>>
>>>
>>>
>>> On Sun, May 1, 2011 at 7:22 PM, Upayavira <uv...@odoko.co.uk> wrote:
>>> > use commons-user: +1
>>> > put SVN in 'incubator' space: +1
>>> > grant "commons rw: +1 (assuming current OGNL committers agree)
>>> >
>>> > As to a private list, I think the benefit would be the opportunity for
>>> > the OGNL committers to learn how such management happens. Where, for
>>> > example, would committer votes happen? The issue with graduation to
>>> > Commons is what happens after graduation - do they suddenly loose some
>>> > power over their own affairs, e.g. ease of seeing vote threads. So not
>>> > sure the best on this one.
>>> >
>>> > Upayavira
>>> >
>>> > On Fri, 29 Apr 2011 08:29 -0700, "Henri Yandell" <fl...@gmail.com>
>>> > wrote:
>>> >> Agreed, no need to use the svn location from Commons; though I ask to
>>> >> allow @commons rw access.
>>> >>
>>> >> The committer of the podling would not automatically become PMC
>>> >> members, so I don't think there is a need to setup a private list (or
>>> >> even to consider it a PPMC).
>>> >>
>>> >> Hen
>>> >>
>>> >> On Thu, Apr 28, 2011 at 11:05 PM, Christian Grobmeier
>>> >> <gr...@gmail.com> wrote:
>>> >> >> we could share MLs and also SVN (Sandbox
>>> >> >> would be nice, not?)
>>> >> >
>>> >> > MLs are fine, b/c one would need to change address later, and
>>> >> > searching for pre-graduation threads is more easily.
>>> >> >
>>> >> > For SVN I don't see a benefit. The repos can be moved with less effort
>>> >> > once component is graduated. I would like to avoid to get something
>>> >> > into the sandbox which is not cleared from legal perspective. What, if
>>> >> > OGNL fails in the incubator and we just forget to remove the code from
>>> >> > the sandbox? If its in the incubator part, it is like a tag
>>> >> > saying:"beware"
>>> >> >
>>> >> > I would be +1 on user/dev ML but leave SVN in incubator
>>> >> > Is there a need to create a pmc ML for OGNL to discuss incubation
>>> >> > related matters?
>>> >> >
>>> >> > Cheers
>>> >> >
>>> >> >> What Incubator PMCs think about it?
>>> >> >> Simo
>>> >> >>
>>> >> >> http://people.apache.org/~simonetripodi/
>>> >> >> http://www.99soft.org/
>>> >> >>
>>> >> >>
>>> >> >>
>>> >> >> On Fri, Apr 29, 2011 at 7:34 AM, Henri Yandell <fl...@gmail.com> wrote:
>>> >> >>> Below is a thread from the Commons Dev list in which I'm recommending
>>> >> >>> that OGNL use the commons dev mailing list and that the svn
>>> >> >>> permissions allow the ognl committers and the commons committers to
>>> >> >>> have read write access.
>>> >> >>>
>>> >> >>> http://commons.markmail.org/thread/ku3ouuilpiicb5is
>>> >> >>>
>>> >> >>> Is this a concern for anyone?
>>> >> >>>
>>> >> >>> OGNL's target is to graduate into Commons rather than to TLP, so
>>> >> >>> making it act like a TLP seems destined to cause problems.
>>> >> >>>
>>> >> >>> Hen
>>> >> >>>
>>> >> >>> ---------------------------------------------------------------------
>>> >> >>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> >> >>> For additional commands, e-mail: general-help@incubator.apache.org
>>> >> >>>
>>> >> >>>
>>> >> >>
>>> >> >> ---------------------------------------------------------------------
>>> >> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> >> >> For additional commands, e-mail: general-help@incubator.apache.org
>>> >> >>
>>> >> >>
>>> >> >
>>> >> >
>>> >> >
>>> >> > --
>>> >> > http://www.grobmeier.de
>>> >> >
>>> >> > ---------------------------------------------------------------------
>>> >> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> >> > For additional commands, e-mail: general-help@incubator.apache.org
>>> >> >
>>> >> >
>>> >>
>>> >> ---------------------------------------------------------------------
>>> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> >> For additional commands, e-mail: general-help@incubator.apache.org
>>> >>
>>> >
>>> > ---------------------------------------------------------------------
>>> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> > For additional commands, e-mail: general-help@incubator.apache.org
>>> >
>>> >
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>
>
>
> --
> http://www.grobmeier.de
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: OGNL Infrastructure questions
Posted by Olivier Lamy <ol...@apache.org>.
+1 too
/Olivier
2011/5/3 Lukasz Lenart <lu...@googlemail.com>:
> +1 for JIRA space and issues@commons.a.o
>
>
> Kind regards
> --
> Łukasz
> + 48 606 323 122 http://www.lenart.org.pl/
> Warszawa JUG conference - Confitura http://confitura.pl/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: OGNL Infrastructure questions
Posted by Olivier Lamy <ol...@apache.org>.
+1 too
/Olivier
2011/5/3 Lukasz Lenart <lu...@googlemail.com>:
> +1 for JIRA space and issues@commons.a.o
>
>
> Kind regards
> --
> Łukasz
> + 48 606 323 122 http://www.lenart.org.pl/
> Warszawa JUG conference - Confitura http://confitura.pl/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: OGNL Infrastructure questions
Posted by Lukasz Lenart <lu...@googlemail.com>.
+1 for JIRA space and issues@commons.a.o
Kind regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
Warszawa JUG conference - Confitura http://confitura.pl/
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: OGNL Infrastructure questions
Posted by sebb <se...@gmail.com>.
On 3 May 2011 14:25, Christian Grobmeier <gr...@gmail.com> wrote:
> Hi,
>
> Simo, I guess you are referring to:
> "Use issues@commons.apache.org' for Jira change notification"
>
> I am +1
Likewise, +1
>
> Cheers
> Christian
>
>
> On Tue, May 3, 2011 at 2:20 PM, Simone Tripodi <si...@apache.org> wrote:
>> Hi all guys,
>> do you agree on Gavin's suggestion on INFRA-3600[1]?
>> I agree but before giving him the confirmation can someone please review?
>> Many thanks in advance,
>> Simo
>>
>> [1] https://issues.apache.org/jira/browse/INFRA-3600
>>
>> http://people.apache.org/~simonetripodi/
>> http://www.99soft.org/
>>
>>
>>
>> On Tue, May 3, 2011 at 7:52 AM, Simone Tripodi <si...@apache.org> wrote:
>>> Hi again,
>>> As you already noticed, the main Issue is INFRA-3597[1].
>>> Many thanks in advance!
>>> Simo
>>>
>>> [1] https://issues.apache.org/jira/browse/INFRA-3597
>>>
>>> http://people.apache.org/~simonetripodi/
>>> http://www.99soft.org/
>>>
>>>
>>>
>>> On Tue, May 3, 2011 at 7:39 AM, Simone Tripodi <si...@apache.org> wrote:
>>>> Hi all guys,
>>>> the discussion in following up on INFRA-3601[1], please join to
>>>> correct me if I'm wrong!
>>>> Many thanks in advance,
>>>> Simo
>>>>
>>>> [1] https://issues.apache.org/jira/browse/INFRA-3601
>>>>
>>>> http://people.apache.org/~simonetripodi/
>>>> http://www.99soft.org/
>>>>
>>>>
>>>>
>>>> On Mon, May 2, 2011 at 10:35 AM, Mark Struberg <st...@yahoo.de> wrote:
>>>>> just for the record (for the new contributors). As long as your incubating the following rules apply:
>>>>>
>>>>> http://incubator.apache.org/guides/ppmc.html
>>>>>
>>>>> At the time you graduate you need to check who really was active and 'cleanup' the PPMC. So not every person which was on the PPMC automatically makes it to the final PMC anyway ...
>>>>>
>>>>> LieGrue,
>>>>> strub
>>>>>
>>>>> --- On Mon, 5/2/11, Olivier Lamy <ol...@apache.org> wrote:
>>>>>
>>>>>> From: Olivier Lamy <ol...@apache.org>
>>>>>> Subject: Re: OGNL Infrastructure questions
>>>>>> To: general@incubator.apache.org
>>>>>> Date: Monday, May 2, 2011, 7:11 AM
>>>>>> +1
>>>>>>
>>>>>>
>>>>>>
>>>>>> 2011/5/2 Christian Grobmeier <gr...@gmail.com>:
>>>>>> >> My issue (for the commons PMC I guess) is how
>>>>>> committer votes will
>>>>>> >> happen when OGNL graduates.
>>>>>> >>
>>>>>> >> After graduation, how would one of the current
>>>>>> contributors propose a
>>>>>> >> new committer if they are not themselves on the
>>>>>> Commons PMC?
>>>>>> >
>>>>>> > Proposal:
>>>>>> >
>>>>>> > - If you are a Commons PMC Member, you are an OGNL
>>>>>> PPMC member by default
>>>>>> > - If a Committer is invited to the PPMC, an additional
>>>>>> vote on Commons
>>>>>> > PMC is necessary, b/c he will join the Commons PMC
>>>>>> after graduation by
>>>>>> > default
>>>>>> > - A contributor can be proposed by anybody - its up to
>>>>>> the PPMC to open the vote
>>>>>> > - A new Committer can be elected by the PPMC with
>>>>>> binding votes; as
>>>>>> > usual other Committers can vote unbinding. I don't
>>>>>> think it creates
>>>>>> > any problems b/c usually there is already a consens on
>>>>>> adding a person
>>>>>> > before calling a vote.
>>>>>> >
>>>>>> > Makes sense?
>>>>>> >
>>>>>> > Cheers
>>>>>> > Christian
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> >>
>>>>>> >> Upayavira
>>>>>> >>
>>>>>> >> On Sun, 01 May 2011 19:56 +0200, "Simone Tripodi"
>>>>>> >> <si...@apache.org>
>>>>>> wrote:
>>>>>> >>> Hi Upayavira!!!
>>>>>> >>> I agree that commons folks can have rw rights,
>>>>>> so people are already
>>>>>> >>> used to co-work in the 'commons way'.
>>>>>> >>> Moreover, I agreed on joining
>>>>>> >>>
>>>>>> >>> - dev@commons.a.o
>>>>>> >>> - users@commons.a.o
>>>>>> >>> - issues@commons.a.o
>>>>>> >>> - create the private ML where commons PMCs can
>>>>>> join.
>>>>>> >>>
>>>>>> >>> Does it make sense?
>>>>>> >>> Simo
>>>>>> >>>
>>>>>> >>> http://people.apache.org/~simonetripodi/
>>>>>> >>> http://www.99soft.org/
>>>>>> >>>
>>>>>> >>>
>>>>>> >>>
>>>>>> >>> On Sun, May 1, 2011 at 7:22 PM, Upayavira
>>>>>> <uv...@odoko.co.uk>
>>>>>> wrote:
>>>>>> >>> > use commons-user: +1
>>>>>> >>> > put SVN in 'incubator' space: +1
>>>>>> >>> > grant "commons rw: +1 (assuming current
>>>>>> OGNL committers agree)
>>>>>> >>> >
>>>>>> >>> > As to a private list, I think the benefit
>>>>>> would be the opportunity for
>>>>>> >>> > the OGNL committers to learn how such
>>>>>> management happens. Where, for
>>>>>> >>> > example, would committer votes happen?
>>>>>> The issue with graduation to
>>>>>> >>> > Commons is what happens after graduation
>>>>>> - do they suddenly loose some
>>>>>> >>> > power over their own affairs, e.g. ease
>>>>>> of seeing vote threads. So not
>>>>>> >>> > sure the best on this one.
>>>>>> >>> >
>>>>>> >>> > Upayavira
>>>>>> >>> >
>>>>>> >>> > On Fri, 29 Apr 2011 08:29 -0700, "Henri
>>>>>> Yandell" <fl...@gmail.com>
>>>>>> >>> > wrote:
>>>>>> >>> >> Agreed, no need to use the svn
>>>>>> location from Commons; though I ask to
>>>>>> >>> >> allow @commons rw access.
>>>>>> >>> >>
>>>>>> >>> >> The committer of the podling would
>>>>>> not automatically become PMC
>>>>>> >>> >> members, so I don't think there is a
>>>>>> need to setup a private list (or
>>>>>> >>> >> even to consider it a PPMC).
>>>>>> >>> >>
>>>>>> >>> >> Hen
>>>>>> >>> >>
>>>>>> >>> >> On Thu, Apr 28, 2011 at 11:05 PM,
>>>>>> Christian Grobmeier
>>>>>> >>> >> <gr...@gmail.com>
>>>>>> wrote:
>>>>>> >>> >> >> we could share MLs and also
>>>>>> SVN (Sandbox
>>>>>> >>> >> >> would be nice, not?)
>>>>>> >>> >> >
>>>>>> >>> >> > MLs are fine, b/c one would need
>>>>>> to change address later, and
>>>>>> >>> >> > searching for pre-graduation
>>>>>> threads is more easily.
>>>>>> >>> >> >
>>>>>> >>> >> > For SVN I don't see a benefit.
>>>>>> The repos can be moved with less effort
>>>>>> >>> >> > once component is graduated. I
>>>>>> would like to avoid to get something
>>>>>> >>> >> > into the sandbox which is not
>>>>>> cleared from legal perspective. What, if
>>>>>> >>> >> > OGNL fails in the incubator and
>>>>>> we just forget to remove the code from
>>>>>> >>> >> > the sandbox? If its in the
>>>>>> incubator part, it is like a tag
>>>>>> >>> >> > saying:"beware"
>>>>>> >>> >> >
>>>>>> >>> >> > I would be +1 on user/dev ML but
>>>>>> leave SVN in incubator
>>>>>> >>> >> > Is there a need to create a pmc
>>>>>> ML for OGNL to discuss incubation
>>>>>> >>> >> > related matters?
>>>>>> >>> >> >
>>>>>> >>> >> > Cheers
>>>>>> >>> >> >
>>>>>> >>> >> >> What Incubator PMCs think
>>>>>> about it?
>>>>>> >>> >> >> Simo
>>>>>> >>> >> >>
>>>>>> >>> >> >> http://people.apache.org/~simonetripodi/
>>>>>> >>> >> >> http://www.99soft.org/
>>>>>> >>> >> >>
>>>>>> >>> >> >>
>>>>>> >>> >> >>
>>>>>> >>> >> >> On Fri, Apr 29, 2011 at 7:34
>>>>>> AM, Henri Yandell <fl...@gmail.com>
>>>>>> wrote:
>>>>>> >>> >> >>> Below is a thread from
>>>>>> the Commons Dev list in which I'm recommending
>>>>>> >>> >> >>> that OGNL use the
>>>>>> commons dev mailing list and that the svn
>>>>>> >>> >> >>> permissions allow the
>>>>>> ognl committers and the commons committers to
>>>>>> >>> >> >>> have read write access.
>>>>>> >>> >> >>>
>>>>>> >>> >> >>> http://commons.markmail.org/thread/ku3ouuilpiicb5is
>>>>>> >>> >> >>>
>>>>>> >>> >> >>> Is this a concern for
>>>>>> anyone?
>>>>>> >>> >> >>>
>>>>>> >>> >> >>> OGNL's target is to
>>>>>> graduate into Commons rather than to TLP, so
>>>>>> >>> >> >>> making it act like a TLP
>>>>>> seems destined to cause problems.
>>>>>> >>> >> >>>
>>>>>> >>> >> >>> Hen
>>>>>> >>> >> >>>
>>>>>> >>> >> >>>
>>>>>> ---------------------------------------------------------------------
>>>>>> >>> >> >>> To unsubscribe, e-mail:
>>>>>> general-unsubscribe@incubator.apache.org
>>>>>> >>> >> >>> For additional commands,
>>>>>> e-mail: general-help@incubator.apache.org
>>>>>> >>> >> >>>
>>>>>> >>> >> >>>
>>>>>> >>> >> >>
>>>>>> >>> >> >>
>>>>>> ---------------------------------------------------------------------
>>>>>> >>> >> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>>> >>> >> >> For additional commands,
>>>>>> e-mail: general-help@incubator.apache.org
>>>>>> >>> >> >>
>>>>>> >>> >> >>
>>>>>> >>> >> >
>>>>>> >>> >> >
>>>>>> >>> >> >
>>>>>> >>> >> > --
>>>>>> >>> >> > http://www.grobmeier.de
>>>>>> >>> >> >
>>>>>> >>> >> >
>>>>>> ---------------------------------------------------------------------
>>>>>> >>> >> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>>> >>> >> > For additional commands, e-mail:
>>>>>> general-help@incubator.apache.org
>>>>>> >>> >> >
>>>>>> >>> >> >
>>>>>> >>> >>
>>>>>> >>> >>
>>>>>> ---------------------------------------------------------------------
>>>>>> >>> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>>> >>> >> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>> >>> >>
>>>>>> >>> >
>>>>>> >>> >
>>>>>> ---------------------------------------------------------------------
>>>>>> >>> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>>> >>> > For additional commands, e-mail: general-help@incubator.apache.org
>>>>>> >>> >
>>>>>> >>> >
>>>>>> >>>
>>>>>> >>>
>>>>>> ---------------------------------------------------------------------
>>>>>> >>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>>> >>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>> >>>
>>>>>> >>
>>>>>> >>
>>>>>> ---------------------------------------------------------------------
>>>>>> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>>> >> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>> >>
>>>>>> >>
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> > --
>>>>>> > http://www.grobmeier.de
>>>>>> >
>>>>>> >
>>>>>> ---------------------------------------------------------------------
>>>>>> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>>> > For additional commands, e-mail: general-help@incubator.apache.org
>>>>>> >
>>>>>> >
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Olivier Lamy
>>>>>> http://twitter.com/olamy
>>>>>> http://www.linkedin.com/in/olamy
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>
>>>>>
>>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>
>
>
> --
> http://www.grobmeier.de
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: OGNL Infrastructure questions
Posted by sebb <se...@gmail.com>.
On 3 May 2011 14:25, Christian Grobmeier <gr...@gmail.com> wrote:
> Hi,
>
> Simo, I guess you are referring to:
> "Use issues@commons.apache.org' for Jira change notification"
>
> I am +1
Likewise, +1
>
> Cheers
> Christian
>
>
> On Tue, May 3, 2011 at 2:20 PM, Simone Tripodi <si...@apache.org> wrote:
>> Hi all guys,
>> do you agree on Gavin's suggestion on INFRA-3600[1]?
>> I agree but before giving him the confirmation can someone please review?
>> Many thanks in advance,
>> Simo
>>
>> [1] https://issues.apache.org/jira/browse/INFRA-3600
>>
>> http://people.apache.org/~simonetripodi/
>> http://www.99soft.org/
>>
>>
>>
>> On Tue, May 3, 2011 at 7:52 AM, Simone Tripodi <si...@apache.org> wrote:
>>> Hi again,
>>> As you already noticed, the main Issue is INFRA-3597[1].
>>> Many thanks in advance!
>>> Simo
>>>
>>> [1] https://issues.apache.org/jira/browse/INFRA-3597
>>>
>>> http://people.apache.org/~simonetripodi/
>>> http://www.99soft.org/
>>>
>>>
>>>
>>> On Tue, May 3, 2011 at 7:39 AM, Simone Tripodi <si...@apache.org> wrote:
>>>> Hi all guys,
>>>> the discussion in following up on INFRA-3601[1], please join to
>>>> correct me if I'm wrong!
>>>> Many thanks in advance,
>>>> Simo
>>>>
>>>> [1] https://issues.apache.org/jira/browse/INFRA-3601
>>>>
>>>> http://people.apache.org/~simonetripodi/
>>>> http://www.99soft.org/
>>>>
>>>>
>>>>
>>>> On Mon, May 2, 2011 at 10:35 AM, Mark Struberg <st...@yahoo.de> wrote:
>>>>> just for the record (for the new contributors). As long as your incubating the following rules apply:
>>>>>
>>>>> http://incubator.apache.org/guides/ppmc.html
>>>>>
>>>>> At the time you graduate you need to check who really was active and 'cleanup' the PPMC. So not every person which was on the PPMC automatically makes it to the final PMC anyway ...
>>>>>
>>>>> LieGrue,
>>>>> strub
>>>>>
>>>>> --- On Mon, 5/2/11, Olivier Lamy <ol...@apache.org> wrote:
>>>>>
>>>>>> From: Olivier Lamy <ol...@apache.org>
>>>>>> Subject: Re: OGNL Infrastructure questions
>>>>>> To: general@incubator.apache.org
>>>>>> Date: Monday, May 2, 2011, 7:11 AM
>>>>>> +1
>>>>>>
>>>>>>
>>>>>>
>>>>>> 2011/5/2 Christian Grobmeier <gr...@gmail.com>:
>>>>>> >> My issue (for the commons PMC I guess) is how
>>>>>> committer votes will
>>>>>> >> happen when OGNL graduates.
>>>>>> >>
>>>>>> >> After graduation, how would one of the current
>>>>>> contributors propose a
>>>>>> >> new committer if they are not themselves on the
>>>>>> Commons PMC?
>>>>>> >
>>>>>> > Proposal:
>>>>>> >
>>>>>> > - If you are a Commons PMC Member, you are an OGNL
>>>>>> PPMC member by default
>>>>>> > - If a Committer is invited to the PPMC, an additional
>>>>>> vote on Commons
>>>>>> > PMC is necessary, b/c he will join the Commons PMC
>>>>>> after graduation by
>>>>>> > default
>>>>>> > - A contributor can be proposed by anybody - its up to
>>>>>> the PPMC to open the vote
>>>>>> > - A new Committer can be elected by the PPMC with
>>>>>> binding votes; as
>>>>>> > usual other Committers can vote unbinding. I don't
>>>>>> think it creates
>>>>>> > any problems b/c usually there is already a consens on
>>>>>> adding a person
>>>>>> > before calling a vote.
>>>>>> >
>>>>>> > Makes sense?
>>>>>> >
>>>>>> > Cheers
>>>>>> > Christian
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> >>
>>>>>> >> Upayavira
>>>>>> >>
>>>>>> >> On Sun, 01 May 2011 19:56 +0200, "Simone Tripodi"
>>>>>> >> <si...@apache.org>
>>>>>> wrote:
>>>>>> >>> Hi Upayavira!!!
>>>>>> >>> I agree that commons folks can have rw rights,
>>>>>> so people are already
>>>>>> >>> used to co-work in the 'commons way'.
>>>>>> >>> Moreover, I agreed on joining
>>>>>> >>>
>>>>>> >>> - dev@commons.a.o
>>>>>> >>> - users@commons.a.o
>>>>>> >>> - issues@commons.a.o
>>>>>> >>> - create the private ML where commons PMCs can
>>>>>> join.
>>>>>> >>>
>>>>>> >>> Does it make sense?
>>>>>> >>> Simo
>>>>>> >>>
>>>>>> >>> http://people.apache.org/~simonetripodi/
>>>>>> >>> http://www.99soft.org/
>>>>>> >>>
>>>>>> >>>
>>>>>> >>>
>>>>>> >>> On Sun, May 1, 2011 at 7:22 PM, Upayavira
>>>>>> <uv...@odoko.co.uk>
>>>>>> wrote:
>>>>>> >>> > use commons-user: +1
>>>>>> >>> > put SVN in 'incubator' space: +1
>>>>>> >>> > grant "commons rw: +1 (assuming current
>>>>>> OGNL committers agree)
>>>>>> >>> >
>>>>>> >>> > As to a private list, I think the benefit
>>>>>> would be the opportunity for
>>>>>> >>> > the OGNL committers to learn how such
>>>>>> management happens. Where, for
>>>>>> >>> > example, would committer votes happen?
>>>>>> The issue with graduation to
>>>>>> >>> > Commons is what happens after graduation
>>>>>> - do they suddenly loose some
>>>>>> >>> > power over their own affairs, e.g. ease
>>>>>> of seeing vote threads. So not
>>>>>> >>> > sure the best on this one.
>>>>>> >>> >
>>>>>> >>> > Upayavira
>>>>>> >>> >
>>>>>> >>> > On Fri, 29 Apr 2011 08:29 -0700, "Henri
>>>>>> Yandell" <fl...@gmail.com>
>>>>>> >>> > wrote:
>>>>>> >>> >> Agreed, no need to use the svn
>>>>>> location from Commons; though I ask to
>>>>>> >>> >> allow @commons rw access.
>>>>>> >>> >>
>>>>>> >>> >> The committer of the podling would
>>>>>> not automatically become PMC
>>>>>> >>> >> members, so I don't think there is a
>>>>>> need to setup a private list (or
>>>>>> >>> >> even to consider it a PPMC).
>>>>>> >>> >>
>>>>>> >>> >> Hen
>>>>>> >>> >>
>>>>>> >>> >> On Thu, Apr 28, 2011 at 11:05 PM,
>>>>>> Christian Grobmeier
>>>>>> >>> >> <gr...@gmail.com>
>>>>>> wrote:
>>>>>> >>> >> >> we could share MLs and also
>>>>>> SVN (Sandbox
>>>>>> >>> >> >> would be nice, not?)
>>>>>> >>> >> >
>>>>>> >>> >> > MLs are fine, b/c one would need
>>>>>> to change address later, and
>>>>>> >>> >> > searching for pre-graduation
>>>>>> threads is more easily.
>>>>>> >>> >> >
>>>>>> >>> >> > For SVN I don't see a benefit.
>>>>>> The repos can be moved with less effort
>>>>>> >>> >> > once component is graduated. I
>>>>>> would like to avoid to get something
>>>>>> >>> >> > into the sandbox which is not
>>>>>> cleared from legal perspective. What, if
>>>>>> >>> >> > OGNL fails in the incubator and
>>>>>> we just forget to remove the code from
>>>>>> >>> >> > the sandbox? If its in the
>>>>>> incubator part, it is like a tag
>>>>>> >>> >> > saying:"beware"
>>>>>> >>> >> >
>>>>>> >>> >> > I would be +1 on user/dev ML but
>>>>>> leave SVN in incubator
>>>>>> >>> >> > Is there a need to create a pmc
>>>>>> ML for OGNL to discuss incubation
>>>>>> >>> >> > related matters?
>>>>>> >>> >> >
>>>>>> >>> >> > Cheers
>>>>>> >>> >> >
>>>>>> >>> >> >> What Incubator PMCs think
>>>>>> about it?
>>>>>> >>> >> >> Simo
>>>>>> >>> >> >>
>>>>>> >>> >> >> http://people.apache.org/~simonetripodi/
>>>>>> >>> >> >> http://www.99soft.org/
>>>>>> >>> >> >>
>>>>>> >>> >> >>
>>>>>> >>> >> >>
>>>>>> >>> >> >> On Fri, Apr 29, 2011 at 7:34
>>>>>> AM, Henri Yandell <fl...@gmail.com>
>>>>>> wrote:
>>>>>> >>> >> >>> Below is a thread from
>>>>>> the Commons Dev list in which I'm recommending
>>>>>> >>> >> >>> that OGNL use the
>>>>>> commons dev mailing list and that the svn
>>>>>> >>> >> >>> permissions allow the
>>>>>> ognl committers and the commons committers to
>>>>>> >>> >> >>> have read write access.
>>>>>> >>> >> >>>
>>>>>> >>> >> >>> http://commons.markmail.org/thread/ku3ouuilpiicb5is
>>>>>> >>> >> >>>
>>>>>> >>> >> >>> Is this a concern for
>>>>>> anyone?
>>>>>> >>> >> >>>
>>>>>> >>> >> >>> OGNL's target is to
>>>>>> graduate into Commons rather than to TLP, so
>>>>>> >>> >> >>> making it act like a TLP
>>>>>> seems destined to cause problems.
>>>>>> >>> >> >>>
>>>>>> >>> >> >>> Hen
>>>>>> >>> >> >>>
>>>>>> >>> >> >>>
>>>>>> ---------------------------------------------------------------------
>>>>>> >>> >> >>> To unsubscribe, e-mail:
>>>>>> general-unsubscribe@incubator.apache.org
>>>>>> >>> >> >>> For additional commands,
>>>>>> e-mail: general-help@incubator.apache.org
>>>>>> >>> >> >>>
>>>>>> >>> >> >>>
>>>>>> >>> >> >>
>>>>>> >>> >> >>
>>>>>> ---------------------------------------------------------------------
>>>>>> >>> >> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>>> >>> >> >> For additional commands,
>>>>>> e-mail: general-help@incubator.apache.org
>>>>>> >>> >> >>
>>>>>> >>> >> >>
>>>>>> >>> >> >
>>>>>> >>> >> >
>>>>>> >>> >> >
>>>>>> >>> >> > --
>>>>>> >>> >> > http://www.grobmeier.de
>>>>>> >>> >> >
>>>>>> >>> >> >
>>>>>> ---------------------------------------------------------------------
>>>>>> >>> >> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>>> >>> >> > For additional commands, e-mail:
>>>>>> general-help@incubator.apache.org
>>>>>> >>> >> >
>>>>>> >>> >> >
>>>>>> >>> >>
>>>>>> >>> >>
>>>>>> ---------------------------------------------------------------------
>>>>>> >>> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>>> >>> >> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>> >>> >>
>>>>>> >>> >
>>>>>> >>> >
>>>>>> ---------------------------------------------------------------------
>>>>>> >>> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>>> >>> > For additional commands, e-mail: general-help@incubator.apache.org
>>>>>> >>> >
>>>>>> >>> >
>>>>>> >>>
>>>>>> >>>
>>>>>> ---------------------------------------------------------------------
>>>>>> >>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>>> >>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>> >>>
>>>>>> >>
>>>>>> >>
>>>>>> ---------------------------------------------------------------------
>>>>>> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>>> >> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>> >>
>>>>>> >>
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> > --
>>>>>> > http://www.grobmeier.de
>>>>>> >
>>>>>> >
>>>>>> ---------------------------------------------------------------------
>>>>>> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>>> > For additional commands, e-mail: general-help@incubator.apache.org
>>>>>> >
>>>>>> >
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Olivier Lamy
>>>>>> http://twitter.com/olamy
>>>>>> http://www.linkedin.com/in/olamy
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>
>>>>>
>>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>
>
>
> --
> http://www.grobmeier.de
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: OGNL Infrastructure questions
Posted by Christian Grobmeier <gr...@gmail.com>.
Hi,
Simo, I guess you are referring to:
"Use issues@commons.apache.org' for Jira change notification"
I am +1
Cheers
Christian
On Tue, May 3, 2011 at 2:20 PM, Simone Tripodi <si...@apache.org> wrote:
> Hi all guys,
> do you agree on Gavin's suggestion on INFRA-3600[1]?
> I agree but before giving him the confirmation can someone please review?
> Many thanks in advance,
> Simo
>
> [1] https://issues.apache.org/jira/browse/INFRA-3600
>
> http://people.apache.org/~simonetripodi/
> http://www.99soft.org/
>
>
>
> On Tue, May 3, 2011 at 7:52 AM, Simone Tripodi <si...@apache.org> wrote:
>> Hi again,
>> As you already noticed, the main Issue is INFRA-3597[1].
>> Many thanks in advance!
>> Simo
>>
>> [1] https://issues.apache.org/jira/browse/INFRA-3597
>>
>> http://people.apache.org/~simonetripodi/
>> http://www.99soft.org/
>>
>>
>>
>> On Tue, May 3, 2011 at 7:39 AM, Simone Tripodi <si...@apache.org> wrote:
>>> Hi all guys,
>>> the discussion in following up on INFRA-3601[1], please join to
>>> correct me if I'm wrong!
>>> Many thanks in advance,
>>> Simo
>>>
>>> [1] https://issues.apache.org/jira/browse/INFRA-3601
>>>
>>> http://people.apache.org/~simonetripodi/
>>> http://www.99soft.org/
>>>
>>>
>>>
>>> On Mon, May 2, 2011 at 10:35 AM, Mark Struberg <st...@yahoo.de> wrote:
>>>> just for the record (for the new contributors). As long as your incubating the following rules apply:
>>>>
>>>> http://incubator.apache.org/guides/ppmc.html
>>>>
>>>> At the time you graduate you need to check who really was active and 'cleanup' the PPMC. So not every person which was on the PPMC automatically makes it to the final PMC anyway ...
>>>>
>>>> LieGrue,
>>>> strub
>>>>
>>>> --- On Mon, 5/2/11, Olivier Lamy <ol...@apache.org> wrote:
>>>>
>>>>> From: Olivier Lamy <ol...@apache.org>
>>>>> Subject: Re: OGNL Infrastructure questions
>>>>> To: general@incubator.apache.org
>>>>> Date: Monday, May 2, 2011, 7:11 AM
>>>>> +1
>>>>>
>>>>>
>>>>>
>>>>> 2011/5/2 Christian Grobmeier <gr...@gmail.com>:
>>>>> >> My issue (for the commons PMC I guess) is how
>>>>> committer votes will
>>>>> >> happen when OGNL graduates.
>>>>> >>
>>>>> >> After graduation, how would one of the current
>>>>> contributors propose a
>>>>> >> new committer if they are not themselves on the
>>>>> Commons PMC?
>>>>> >
>>>>> > Proposal:
>>>>> >
>>>>> > - If you are a Commons PMC Member, you are an OGNL
>>>>> PPMC member by default
>>>>> > - If a Committer is invited to the PPMC, an additional
>>>>> vote on Commons
>>>>> > PMC is necessary, b/c he will join the Commons PMC
>>>>> after graduation by
>>>>> > default
>>>>> > - A contributor can be proposed by anybody - its up to
>>>>> the PPMC to open the vote
>>>>> > - A new Committer can be elected by the PPMC with
>>>>> binding votes; as
>>>>> > usual other Committers can vote unbinding. I don't
>>>>> think it creates
>>>>> > any problems b/c usually there is already a consens on
>>>>> adding a person
>>>>> > before calling a vote.
>>>>> >
>>>>> > Makes sense?
>>>>> >
>>>>> > Cheers
>>>>> > Christian
>>>>> >
>>>>> >
>>>>> >
>>>>> >
>>>>> >>
>>>>> >> Upayavira
>>>>> >>
>>>>> >> On Sun, 01 May 2011 19:56 +0200, "Simone Tripodi"
>>>>> >> <si...@apache.org>
>>>>> wrote:
>>>>> >>> Hi Upayavira!!!
>>>>> >>> I agree that commons folks can have rw rights,
>>>>> so people are already
>>>>> >>> used to co-work in the 'commons way'.
>>>>> >>> Moreover, I agreed on joining
>>>>> >>>
>>>>> >>> - dev@commons.a.o
>>>>> >>> - users@commons.a.o
>>>>> >>> - issues@commons.a.o
>>>>> >>> - create the private ML where commons PMCs can
>>>>> join.
>>>>> >>>
>>>>> >>> Does it make sense?
>>>>> >>> Simo
>>>>> >>>
>>>>> >>> http://people.apache.org/~simonetripodi/
>>>>> >>> http://www.99soft.org/
>>>>> >>>
>>>>> >>>
>>>>> >>>
>>>>> >>> On Sun, May 1, 2011 at 7:22 PM, Upayavira
>>>>> <uv...@odoko.co.uk>
>>>>> wrote:
>>>>> >>> > use commons-user: +1
>>>>> >>> > put SVN in 'incubator' space: +1
>>>>> >>> > grant "commons rw: +1 (assuming current
>>>>> OGNL committers agree)
>>>>> >>> >
>>>>> >>> > As to a private list, I think the benefit
>>>>> would be the opportunity for
>>>>> >>> > the OGNL committers to learn how such
>>>>> management happens. Where, for
>>>>> >>> > example, would committer votes happen?
>>>>> The issue with graduation to
>>>>> >>> > Commons is what happens after graduation
>>>>> - do they suddenly loose some
>>>>> >>> > power over their own affairs, e.g. ease
>>>>> of seeing vote threads. So not
>>>>> >>> > sure the best on this one.
>>>>> >>> >
>>>>> >>> > Upayavira
>>>>> >>> >
>>>>> >>> > On Fri, 29 Apr 2011 08:29 -0700, "Henri
>>>>> Yandell" <fl...@gmail.com>
>>>>> >>> > wrote:
>>>>> >>> >> Agreed, no need to use the svn
>>>>> location from Commons; though I ask to
>>>>> >>> >> allow @commons rw access.
>>>>> >>> >>
>>>>> >>> >> The committer of the podling would
>>>>> not automatically become PMC
>>>>> >>> >> members, so I don't think there is a
>>>>> need to setup a private list (or
>>>>> >>> >> even to consider it a PPMC).
>>>>> >>> >>
>>>>> >>> >> Hen
>>>>> >>> >>
>>>>> >>> >> On Thu, Apr 28, 2011 at 11:05 PM,
>>>>> Christian Grobmeier
>>>>> >>> >> <gr...@gmail.com>
>>>>> wrote:
>>>>> >>> >> >> we could share MLs and also
>>>>> SVN (Sandbox
>>>>> >>> >> >> would be nice, not?)
>>>>> >>> >> >
>>>>> >>> >> > MLs are fine, b/c one would need
>>>>> to change address later, and
>>>>> >>> >> > searching for pre-graduation
>>>>> threads is more easily.
>>>>> >>> >> >
>>>>> >>> >> > For SVN I don't see a benefit.
>>>>> The repos can be moved with less effort
>>>>> >>> >> > once component is graduated. I
>>>>> would like to avoid to get something
>>>>> >>> >> > into the sandbox which is not
>>>>> cleared from legal perspective. What, if
>>>>> >>> >> > OGNL fails in the incubator and
>>>>> we just forget to remove the code from
>>>>> >>> >> > the sandbox? If its in the
>>>>> incubator part, it is like a tag
>>>>> >>> >> > saying:"beware"
>>>>> >>> >> >
>>>>> >>> >> > I would be +1 on user/dev ML but
>>>>> leave SVN in incubator
>>>>> >>> >> > Is there a need to create a pmc
>>>>> ML for OGNL to discuss incubation
>>>>> >>> >> > related matters?
>>>>> >>> >> >
>>>>> >>> >> > Cheers
>>>>> >>> >> >
>>>>> >>> >> >> What Incubator PMCs think
>>>>> about it?
>>>>> >>> >> >> Simo
>>>>> >>> >> >>
>>>>> >>> >> >> http://people.apache.org/~simonetripodi/
>>>>> >>> >> >> http://www.99soft.org/
>>>>> >>> >> >>
>>>>> >>> >> >>
>>>>> >>> >> >>
>>>>> >>> >> >> On Fri, Apr 29, 2011 at 7:34
>>>>> AM, Henri Yandell <fl...@gmail.com>
>>>>> wrote:
>>>>> >>> >> >>> Below is a thread from
>>>>> the Commons Dev list in which I'm recommending
>>>>> >>> >> >>> that OGNL use the
>>>>> commons dev mailing list and that the svn
>>>>> >>> >> >>> permissions allow the
>>>>> ognl committers and the commons committers to
>>>>> >>> >> >>> have read write access.
>>>>> >>> >> >>>
>>>>> >>> >> >>> http://commons.markmail.org/thread/ku3ouuilpiicb5is
>>>>> >>> >> >>>
>>>>> >>> >> >>> Is this a concern for
>>>>> anyone?
>>>>> >>> >> >>>
>>>>> >>> >> >>> OGNL's target is to
>>>>> graduate into Commons rather than to TLP, so
>>>>> >>> >> >>> making it act like a TLP
>>>>> seems destined to cause problems.
>>>>> >>> >> >>>
>>>>> >>> >> >>> Hen
>>>>> >>> >> >>>
>>>>> >>> >> >>>
>>>>> ---------------------------------------------------------------------
>>>>> >>> >> >>> To unsubscribe, e-mail:
>>>>> general-unsubscribe@incubator.apache.org
>>>>> >>> >> >>> For additional commands,
>>>>> e-mail: general-help@incubator.apache.org
>>>>> >>> >> >>>
>>>>> >>> >> >>>
>>>>> >>> >> >>
>>>>> >>> >> >>
>>>>> ---------------------------------------------------------------------
>>>>> >>> >> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>> >>> >> >> For additional commands,
>>>>> e-mail: general-help@incubator.apache.org
>>>>> >>> >> >>
>>>>> >>> >> >>
>>>>> >>> >> >
>>>>> >>> >> >
>>>>> >>> >> >
>>>>> >>> >> > --
>>>>> >>> >> > http://www.grobmeier.de
>>>>> >>> >> >
>>>>> >>> >> >
>>>>> ---------------------------------------------------------------------
>>>>> >>> >> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>> >>> >> > For additional commands, e-mail:
>>>>> general-help@incubator.apache.org
>>>>> >>> >> >
>>>>> >>> >> >
>>>>> >>> >>
>>>>> >>> >>
>>>>> ---------------------------------------------------------------------
>>>>> >>> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>> >>> >> For additional commands, e-mail: general-help@incubator.apache.org
>>>>> >>> >>
>>>>> >>> >
>>>>> >>> >
>>>>> ---------------------------------------------------------------------
>>>>> >>> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>> >>> > For additional commands, e-mail: general-help@incubator.apache.org
>>>>> >>> >
>>>>> >>> >
>>>>> >>>
>>>>> >>>
>>>>> ---------------------------------------------------------------------
>>>>> >>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>> >>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>> >>>
>>>>> >>
>>>>> >>
>>>>> ---------------------------------------------------------------------
>>>>> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>> >> For additional commands, e-mail: general-help@incubator.apache.org
>>>>> >>
>>>>> >>
>>>>> >
>>>>> >
>>>>> >
>>>>> > --
>>>>> > http://www.grobmeier.de
>>>>> >
>>>>> >
>>>>> ---------------------------------------------------------------------
>>>>> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>> > For additional commands, e-mail: general-help@incubator.apache.org
>>>>> >
>>>>> >
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Olivier Lamy
>>>>> http://twitter.com/olamy
>>>>> http://www.linkedin.com/in/olamy
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>
>>>>
>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
--
http://www.grobmeier.de
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: OGNL Infrastructure questions
Posted by Lukasz Lenart <lu...@googlemail.com>.
+1 for JIRA space and issues@commons.a.o
Kind regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
Warszawa JUG conference - Confitura http://confitura.pl/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: OGNL Infrastructure questions
Posted by Christian Grobmeier <gr...@gmail.com>.
Hi,
Simo, I guess you are referring to:
"Use issues@commons.apache.org' for Jira change notification"
I am +1
Cheers
Christian
On Tue, May 3, 2011 at 2:20 PM, Simone Tripodi <si...@apache.org> wrote:
> Hi all guys,
> do you agree on Gavin's suggestion on INFRA-3600[1]?
> I agree but before giving him the confirmation can someone please review?
> Many thanks in advance,
> Simo
>
> [1] https://issues.apache.org/jira/browse/INFRA-3600
>
> http://people.apache.org/~simonetripodi/
> http://www.99soft.org/
>
>
>
> On Tue, May 3, 2011 at 7:52 AM, Simone Tripodi <si...@apache.org> wrote:
>> Hi again,
>> As you already noticed, the main Issue is INFRA-3597[1].
>> Many thanks in advance!
>> Simo
>>
>> [1] https://issues.apache.org/jira/browse/INFRA-3597
>>
>> http://people.apache.org/~simonetripodi/
>> http://www.99soft.org/
>>
>>
>>
>> On Tue, May 3, 2011 at 7:39 AM, Simone Tripodi <si...@apache.org> wrote:
>>> Hi all guys,
>>> the discussion in following up on INFRA-3601[1], please join to
>>> correct me if I'm wrong!
>>> Many thanks in advance,
>>> Simo
>>>
>>> [1] https://issues.apache.org/jira/browse/INFRA-3601
>>>
>>> http://people.apache.org/~simonetripodi/
>>> http://www.99soft.org/
>>>
>>>
>>>
>>> On Mon, May 2, 2011 at 10:35 AM, Mark Struberg <st...@yahoo.de> wrote:
>>>> just for the record (for the new contributors). As long as your incubating the following rules apply:
>>>>
>>>> http://incubator.apache.org/guides/ppmc.html
>>>>
>>>> At the time you graduate you need to check who really was active and 'cleanup' the PPMC. So not every person which was on the PPMC automatically makes it to the final PMC anyway ...
>>>>
>>>> LieGrue,
>>>> strub
>>>>
>>>> --- On Mon, 5/2/11, Olivier Lamy <ol...@apache.org> wrote:
>>>>
>>>>> From: Olivier Lamy <ol...@apache.org>
>>>>> Subject: Re: OGNL Infrastructure questions
>>>>> To: general@incubator.apache.org
>>>>> Date: Monday, May 2, 2011, 7:11 AM
>>>>> +1
>>>>>
>>>>>
>>>>>
>>>>> 2011/5/2 Christian Grobmeier <gr...@gmail.com>:
>>>>> >> My issue (for the commons PMC I guess) is how
>>>>> committer votes will
>>>>> >> happen when OGNL graduates.
>>>>> >>
>>>>> >> After graduation, how would one of the current
>>>>> contributors propose a
>>>>> >> new committer if they are not themselves on the
>>>>> Commons PMC?
>>>>> >
>>>>> > Proposal:
>>>>> >
>>>>> > - If you are a Commons PMC Member, you are an OGNL
>>>>> PPMC member by default
>>>>> > - If a Committer is invited to the PPMC, an additional
>>>>> vote on Commons
>>>>> > PMC is necessary, b/c he will join the Commons PMC
>>>>> after graduation by
>>>>> > default
>>>>> > - A contributor can be proposed by anybody - its up to
>>>>> the PPMC to open the vote
>>>>> > - A new Committer can be elected by the PPMC with
>>>>> binding votes; as
>>>>> > usual other Committers can vote unbinding. I don't
>>>>> think it creates
>>>>> > any problems b/c usually there is already a consens on
>>>>> adding a person
>>>>> > before calling a vote.
>>>>> >
>>>>> > Makes sense?
>>>>> >
>>>>> > Cheers
>>>>> > Christian
>>>>> >
>>>>> >
>>>>> >
>>>>> >
>>>>> >>
>>>>> >> Upayavira
>>>>> >>
>>>>> >> On Sun, 01 May 2011 19:56 +0200, "Simone Tripodi"
>>>>> >> <si...@apache.org>
>>>>> wrote:
>>>>> >>> Hi Upayavira!!!
>>>>> >>> I agree that commons folks can have rw rights,
>>>>> so people are already
>>>>> >>> used to co-work in the 'commons way'.
>>>>> >>> Moreover, I agreed on joining
>>>>> >>>
>>>>> >>> - dev@commons.a.o
>>>>> >>> - users@commons.a.o
>>>>> >>> - issues@commons.a.o
>>>>> >>> - create the private ML where commons PMCs can
>>>>> join.
>>>>> >>>
>>>>> >>> Does it make sense?
>>>>> >>> Simo
>>>>> >>>
>>>>> >>> http://people.apache.org/~simonetripodi/
>>>>> >>> http://www.99soft.org/
>>>>> >>>
>>>>> >>>
>>>>> >>>
>>>>> >>> On Sun, May 1, 2011 at 7:22 PM, Upayavira
>>>>> <uv...@odoko.co.uk>
>>>>> wrote:
>>>>> >>> > use commons-user: +1
>>>>> >>> > put SVN in 'incubator' space: +1
>>>>> >>> > grant "commons rw: +1 (assuming current
>>>>> OGNL committers agree)
>>>>> >>> >
>>>>> >>> > As to a private list, I think the benefit
>>>>> would be the opportunity for
>>>>> >>> > the OGNL committers to learn how such
>>>>> management happens. Where, for
>>>>> >>> > example, would committer votes happen?
>>>>> The issue with graduation to
>>>>> >>> > Commons is what happens after graduation
>>>>> - do they suddenly loose some
>>>>> >>> > power over their own affairs, e.g. ease
>>>>> of seeing vote threads. So not
>>>>> >>> > sure the best on this one.
>>>>> >>> >
>>>>> >>> > Upayavira
>>>>> >>> >
>>>>> >>> > On Fri, 29 Apr 2011 08:29 -0700, "Henri
>>>>> Yandell" <fl...@gmail.com>
>>>>> >>> > wrote:
>>>>> >>> >> Agreed, no need to use the svn
>>>>> location from Commons; though I ask to
>>>>> >>> >> allow @commons rw access.
>>>>> >>> >>
>>>>> >>> >> The committer of the podling would
>>>>> not automatically become PMC
>>>>> >>> >> members, so I don't think there is a
>>>>> need to setup a private list (or
>>>>> >>> >> even to consider it a PPMC).
>>>>> >>> >>
>>>>> >>> >> Hen
>>>>> >>> >>
>>>>> >>> >> On Thu, Apr 28, 2011 at 11:05 PM,
>>>>> Christian Grobmeier
>>>>> >>> >> <gr...@gmail.com>
>>>>> wrote:
>>>>> >>> >> >> we could share MLs and also
>>>>> SVN (Sandbox
>>>>> >>> >> >> would be nice, not?)
>>>>> >>> >> >
>>>>> >>> >> > MLs are fine, b/c one would need
>>>>> to change address later, and
>>>>> >>> >> > searching for pre-graduation
>>>>> threads is more easily.
>>>>> >>> >> >
>>>>> >>> >> > For SVN I don't see a benefit.
>>>>> The repos can be moved with less effort
>>>>> >>> >> > once component is graduated. I
>>>>> would like to avoid to get something
>>>>> >>> >> > into the sandbox which is not
>>>>> cleared from legal perspective. What, if
>>>>> >>> >> > OGNL fails in the incubator and
>>>>> we just forget to remove the code from
>>>>> >>> >> > the sandbox? If its in the
>>>>> incubator part, it is like a tag
>>>>> >>> >> > saying:"beware"
>>>>> >>> >> >
>>>>> >>> >> > I would be +1 on user/dev ML but
>>>>> leave SVN in incubator
>>>>> >>> >> > Is there a need to create a pmc
>>>>> ML for OGNL to discuss incubation
>>>>> >>> >> > related matters?
>>>>> >>> >> >
>>>>> >>> >> > Cheers
>>>>> >>> >> >
>>>>> >>> >> >> What Incubator PMCs think
>>>>> about it?
>>>>> >>> >> >> Simo
>>>>> >>> >> >>
>>>>> >>> >> >> http://people.apache.org/~simonetripodi/
>>>>> >>> >> >> http://www.99soft.org/
>>>>> >>> >> >>
>>>>> >>> >> >>
>>>>> >>> >> >>
>>>>> >>> >> >> On Fri, Apr 29, 2011 at 7:34
>>>>> AM, Henri Yandell <fl...@gmail.com>
>>>>> wrote:
>>>>> >>> >> >>> Below is a thread from
>>>>> the Commons Dev list in which I'm recommending
>>>>> >>> >> >>> that OGNL use the
>>>>> commons dev mailing list and that the svn
>>>>> >>> >> >>> permissions allow the
>>>>> ognl committers and the commons committers to
>>>>> >>> >> >>> have read write access.
>>>>> >>> >> >>>
>>>>> >>> >> >>> http://commons.markmail.org/thread/ku3ouuilpiicb5is
>>>>> >>> >> >>>
>>>>> >>> >> >>> Is this a concern for
>>>>> anyone?
>>>>> >>> >> >>>
>>>>> >>> >> >>> OGNL's target is to
>>>>> graduate into Commons rather than to TLP, so
>>>>> >>> >> >>> making it act like a TLP
>>>>> seems destined to cause problems.
>>>>> >>> >> >>>
>>>>> >>> >> >>> Hen
>>>>> >>> >> >>>
>>>>> >>> >> >>>
>>>>> ---------------------------------------------------------------------
>>>>> >>> >> >>> To unsubscribe, e-mail:
>>>>> general-unsubscribe@incubator.apache.org
>>>>> >>> >> >>> For additional commands,
>>>>> e-mail: general-help@incubator.apache.org
>>>>> >>> >> >>>
>>>>> >>> >> >>>
>>>>> >>> >> >>
>>>>> >>> >> >>
>>>>> ---------------------------------------------------------------------
>>>>> >>> >> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>> >>> >> >> For additional commands,
>>>>> e-mail: general-help@incubator.apache.org
>>>>> >>> >> >>
>>>>> >>> >> >>
>>>>> >>> >> >
>>>>> >>> >> >
>>>>> >>> >> >
>>>>> >>> >> > --
>>>>> >>> >> > http://www.grobmeier.de
>>>>> >>> >> >
>>>>> >>> >> >
>>>>> ---------------------------------------------------------------------
>>>>> >>> >> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>> >>> >> > For additional commands, e-mail:
>>>>> general-help@incubator.apache.org
>>>>> >>> >> >
>>>>> >>> >> >
>>>>> >>> >>
>>>>> >>> >>
>>>>> ---------------------------------------------------------------------
>>>>> >>> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>> >>> >> For additional commands, e-mail: general-help@incubator.apache.org
>>>>> >>> >>
>>>>> >>> >
>>>>> >>> >
>>>>> ---------------------------------------------------------------------
>>>>> >>> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>> >>> > For additional commands, e-mail: general-help@incubator.apache.org
>>>>> >>> >
>>>>> >>> >
>>>>> >>>
>>>>> >>>
>>>>> ---------------------------------------------------------------------
>>>>> >>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>> >>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>> >>>
>>>>> >>
>>>>> >>
>>>>> ---------------------------------------------------------------------
>>>>> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>> >> For additional commands, e-mail: general-help@incubator.apache.org
>>>>> >>
>>>>> >>
>>>>> >
>>>>> >
>>>>> >
>>>>> > --
>>>>> > http://www.grobmeier.de
>>>>> >
>>>>> >
>>>>> ---------------------------------------------------------------------
>>>>> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>> > For additional commands, e-mail: general-help@incubator.apache.org
>>>>> >
>>>>> >
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Olivier Lamy
>>>>> http://twitter.com/olamy
>>>>> http://www.linkedin.com/in/olamy
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>
>>>>
>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
--
http://www.grobmeier.de
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: OGNL Infrastructure questions
Posted by Simone Tripodi <si...@apache.org>.
Hi all guys,
do you agree on Gavin's suggestion on INFRA-3600[1]?
I agree but before giving him the confirmation can someone please review?
Many thanks in advance,
Simo
[1] https://issues.apache.org/jira/browse/INFRA-3600
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Tue, May 3, 2011 at 7:52 AM, Simone Tripodi <si...@apache.org> wrote:
> Hi again,
> As you already noticed, the main Issue is INFRA-3597[1].
> Many thanks in advance!
> Simo
>
> [1] https://issues.apache.org/jira/browse/INFRA-3597
>
> http://people.apache.org/~simonetripodi/
> http://www.99soft.org/
>
>
>
> On Tue, May 3, 2011 at 7:39 AM, Simone Tripodi <si...@apache.org> wrote:
>> Hi all guys,
>> the discussion in following up on INFRA-3601[1], please join to
>> correct me if I'm wrong!
>> Many thanks in advance,
>> Simo
>>
>> [1] https://issues.apache.org/jira/browse/INFRA-3601
>>
>> http://people.apache.org/~simonetripodi/
>> http://www.99soft.org/
>>
>>
>>
>> On Mon, May 2, 2011 at 10:35 AM, Mark Struberg <st...@yahoo.de> wrote:
>>> just for the record (for the new contributors). As long as your incubating the following rules apply:
>>>
>>> http://incubator.apache.org/guides/ppmc.html
>>>
>>> At the time you graduate you need to check who really was active and 'cleanup' the PPMC. So not every person which was on the PPMC automatically makes it to the final PMC anyway ...
>>>
>>> LieGrue,
>>> strub
>>>
>>> --- On Mon, 5/2/11, Olivier Lamy <ol...@apache.org> wrote:
>>>
>>>> From: Olivier Lamy <ol...@apache.org>
>>>> Subject: Re: OGNL Infrastructure questions
>>>> To: general@incubator.apache.org
>>>> Date: Monday, May 2, 2011, 7:11 AM
>>>> +1
>>>>
>>>>
>>>>
>>>> 2011/5/2 Christian Grobmeier <gr...@gmail.com>:
>>>> >> My issue (for the commons PMC I guess) is how
>>>> committer votes will
>>>> >> happen when OGNL graduates.
>>>> >>
>>>> >> After graduation, how would one of the current
>>>> contributors propose a
>>>> >> new committer if they are not themselves on the
>>>> Commons PMC?
>>>> >
>>>> > Proposal:
>>>> >
>>>> > - If you are a Commons PMC Member, you are an OGNL
>>>> PPMC member by default
>>>> > - If a Committer is invited to the PPMC, an additional
>>>> vote on Commons
>>>> > PMC is necessary, b/c he will join the Commons PMC
>>>> after graduation by
>>>> > default
>>>> > - A contributor can be proposed by anybody - its up to
>>>> the PPMC to open the vote
>>>> > - A new Committer can be elected by the PPMC with
>>>> binding votes; as
>>>> > usual other Committers can vote unbinding. I don't
>>>> think it creates
>>>> > any problems b/c usually there is already a consens on
>>>> adding a person
>>>> > before calling a vote.
>>>> >
>>>> > Makes sense?
>>>> >
>>>> > Cheers
>>>> > Christian
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >>
>>>> >> Upayavira
>>>> >>
>>>> >> On Sun, 01 May 2011 19:56 +0200, "Simone Tripodi"
>>>> >> <si...@apache.org>
>>>> wrote:
>>>> >>> Hi Upayavira!!!
>>>> >>> I agree that commons folks can have rw rights,
>>>> so people are already
>>>> >>> used to co-work in the 'commons way'.
>>>> >>> Moreover, I agreed on joining
>>>> >>>
>>>> >>> - dev@commons.a.o
>>>> >>> - users@commons.a.o
>>>> >>> - issues@commons.a.o
>>>> >>> - create the private ML where commons PMCs can
>>>> join.
>>>> >>>
>>>> >>> Does it make sense?
>>>> >>> Simo
>>>> >>>
>>>> >>> http://people.apache.org/~simonetripodi/
>>>> >>> http://www.99soft.org/
>>>> >>>
>>>> >>>
>>>> >>>
>>>> >>> On Sun, May 1, 2011 at 7:22 PM, Upayavira
>>>> <uv...@odoko.co.uk>
>>>> wrote:
>>>> >>> > use commons-user: +1
>>>> >>> > put SVN in 'incubator' space: +1
>>>> >>> > grant "commons rw: +1 (assuming current
>>>> OGNL committers agree)
>>>> >>> >
>>>> >>> > As to a private list, I think the benefit
>>>> would be the opportunity for
>>>> >>> > the OGNL committers to learn how such
>>>> management happens. Where, for
>>>> >>> > example, would committer votes happen?
>>>> The issue with graduation to
>>>> >>> > Commons is what happens after graduation
>>>> - do they suddenly loose some
>>>> >>> > power over their own affairs, e.g. ease
>>>> of seeing vote threads. So not
>>>> >>> > sure the best on this one.
>>>> >>> >
>>>> >>> > Upayavira
>>>> >>> >
>>>> >>> > On Fri, 29 Apr 2011 08:29 -0700, "Henri
>>>> Yandell" <fl...@gmail.com>
>>>> >>> > wrote:
>>>> >>> >> Agreed, no need to use the svn
>>>> location from Commons; though I ask to
>>>> >>> >> allow @commons rw access.
>>>> >>> >>
>>>> >>> >> The committer of the podling would
>>>> not automatically become PMC
>>>> >>> >> members, so I don't think there is a
>>>> need to setup a private list (or
>>>> >>> >> even to consider it a PPMC).
>>>> >>> >>
>>>> >>> >> Hen
>>>> >>> >>
>>>> >>> >> On Thu, Apr 28, 2011 at 11:05 PM,
>>>> Christian Grobmeier
>>>> >>> >> <gr...@gmail.com>
>>>> wrote:
>>>> >>> >> >> we could share MLs and also
>>>> SVN (Sandbox
>>>> >>> >> >> would be nice, not?)
>>>> >>> >> >
>>>> >>> >> > MLs are fine, b/c one would need
>>>> to change address later, and
>>>> >>> >> > searching for pre-graduation
>>>> threads is more easily.
>>>> >>> >> >
>>>> >>> >> > For SVN I don't see a benefit.
>>>> The repos can be moved with less effort
>>>> >>> >> > once component is graduated. I
>>>> would like to avoid to get something
>>>> >>> >> > into the sandbox which is not
>>>> cleared from legal perspective. What, if
>>>> >>> >> > OGNL fails in the incubator and
>>>> we just forget to remove the code from
>>>> >>> >> > the sandbox? If its in the
>>>> incubator part, it is like a tag
>>>> >>> >> > saying:"beware"
>>>> >>> >> >
>>>> >>> >> > I would be +1 on user/dev ML but
>>>> leave SVN in incubator
>>>> >>> >> > Is there a need to create a pmc
>>>> ML for OGNL to discuss incubation
>>>> >>> >> > related matters?
>>>> >>> >> >
>>>> >>> >> > Cheers
>>>> >>> >> >
>>>> >>> >> >> What Incubator PMCs think
>>>> about it?
>>>> >>> >> >> Simo
>>>> >>> >> >>
>>>> >>> >> >> http://people.apache.org/~simonetripodi/
>>>> >>> >> >> http://www.99soft.org/
>>>> >>> >> >>
>>>> >>> >> >>
>>>> >>> >> >>
>>>> >>> >> >> On Fri, Apr 29, 2011 at 7:34
>>>> AM, Henri Yandell <fl...@gmail.com>
>>>> wrote:
>>>> >>> >> >>> Below is a thread from
>>>> the Commons Dev list in which I'm recommending
>>>> >>> >> >>> that OGNL use the
>>>> commons dev mailing list and that the svn
>>>> >>> >> >>> permissions allow the
>>>> ognl committers and the commons committers to
>>>> >>> >> >>> have read write access.
>>>> >>> >> >>>
>>>> >>> >> >>> http://commons.markmail.org/thread/ku3ouuilpiicb5is
>>>> >>> >> >>>
>>>> >>> >> >>> Is this a concern for
>>>> anyone?
>>>> >>> >> >>>
>>>> >>> >> >>> OGNL's target is to
>>>> graduate into Commons rather than to TLP, so
>>>> >>> >> >>> making it act like a TLP
>>>> seems destined to cause problems.
>>>> >>> >> >>>
>>>> >>> >> >>> Hen
>>>> >>> >> >>>
>>>> >>> >> >>>
>>>> ---------------------------------------------------------------------
>>>> >>> >> >>> To unsubscribe, e-mail:
>>>> general-unsubscribe@incubator.apache.org
>>>> >>> >> >>> For additional commands,
>>>> e-mail: general-help@incubator.apache.org
>>>> >>> >> >>>
>>>> >>> >> >>>
>>>> >>> >> >>
>>>> >>> >> >>
>>>> ---------------------------------------------------------------------
>>>> >>> >> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> >>> >> >> For additional commands,
>>>> e-mail: general-help@incubator.apache.org
>>>> >>> >> >>
>>>> >>> >> >>
>>>> >>> >> >
>>>> >>> >> >
>>>> >>> >> >
>>>> >>> >> > --
>>>> >>> >> > http://www.grobmeier.de
>>>> >>> >> >
>>>> >>> >> >
>>>> ---------------------------------------------------------------------
>>>> >>> >> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> >>> >> > For additional commands, e-mail:
>>>> general-help@incubator.apache.org
>>>> >>> >> >
>>>> >>> >> >
>>>> >>> >>
>>>> >>> >>
>>>> ---------------------------------------------------------------------
>>>> >>> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> >>> >> For additional commands, e-mail: general-help@incubator.apache.org
>>>> >>> >>
>>>> >>> >
>>>> >>> >
>>>> ---------------------------------------------------------------------
>>>> >>> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> >>> > For additional commands, e-mail: general-help@incubator.apache.org
>>>> >>> >
>>>> >>> >
>>>> >>>
>>>> >>>
>>>> ---------------------------------------------------------------------
>>>> >>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> >>> For additional commands, e-mail: general-help@incubator.apache.org
>>>> >>>
>>>> >>
>>>> >>
>>>> ---------------------------------------------------------------------
>>>> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> >> For additional commands, e-mail: general-help@incubator.apache.org
>>>> >>
>>>> >>
>>>> >
>>>> >
>>>> >
>>>> > --
>>>> > http://www.grobmeier.de
>>>> >
>>>> >
>>>> ---------------------------------------------------------------------
>>>> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> > For additional commands, e-mail: general-help@incubator.apache.org
>>>> >
>>>> >
>>>>
>>>>
>>>>
>>>> --
>>>> Olivier Lamy
>>>> http://twitter.com/olamy
>>>> http://www.linkedin.com/in/olamy
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: OGNL Infrastructure questions
Posted by Simone Tripodi <si...@apache.org>.
Hi all guys,
do you agree on Gavin's suggestion on INFRA-3600[1]?
I agree but before giving him the confirmation can someone please review?
Many thanks in advance,
Simo
[1] https://issues.apache.org/jira/browse/INFRA-3600
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Tue, May 3, 2011 at 7:52 AM, Simone Tripodi <si...@apache.org> wrote:
> Hi again,
> As you already noticed, the main Issue is INFRA-3597[1].
> Many thanks in advance!
> Simo
>
> [1] https://issues.apache.org/jira/browse/INFRA-3597
>
> http://people.apache.org/~simonetripodi/
> http://www.99soft.org/
>
>
>
> On Tue, May 3, 2011 at 7:39 AM, Simone Tripodi <si...@apache.org> wrote:
>> Hi all guys,
>> the discussion in following up on INFRA-3601[1], please join to
>> correct me if I'm wrong!
>> Many thanks in advance,
>> Simo
>>
>> [1] https://issues.apache.org/jira/browse/INFRA-3601
>>
>> http://people.apache.org/~simonetripodi/
>> http://www.99soft.org/
>>
>>
>>
>> On Mon, May 2, 2011 at 10:35 AM, Mark Struberg <st...@yahoo.de> wrote:
>>> just for the record (for the new contributors). As long as your incubating the following rules apply:
>>>
>>> http://incubator.apache.org/guides/ppmc.html
>>>
>>> At the time you graduate you need to check who really was active and 'cleanup' the PPMC. So not every person which was on the PPMC automatically makes it to the final PMC anyway ...
>>>
>>> LieGrue,
>>> strub
>>>
>>> --- On Mon, 5/2/11, Olivier Lamy <ol...@apache.org> wrote:
>>>
>>>> From: Olivier Lamy <ol...@apache.org>
>>>> Subject: Re: OGNL Infrastructure questions
>>>> To: general@incubator.apache.org
>>>> Date: Monday, May 2, 2011, 7:11 AM
>>>> +1
>>>>
>>>>
>>>>
>>>> 2011/5/2 Christian Grobmeier <gr...@gmail.com>:
>>>> >> My issue (for the commons PMC I guess) is how
>>>> committer votes will
>>>> >> happen when OGNL graduates.
>>>> >>
>>>> >> After graduation, how would one of the current
>>>> contributors propose a
>>>> >> new committer if they are not themselves on the
>>>> Commons PMC?
>>>> >
>>>> > Proposal:
>>>> >
>>>> > - If you are a Commons PMC Member, you are an OGNL
>>>> PPMC member by default
>>>> > - If a Committer is invited to the PPMC, an additional
>>>> vote on Commons
>>>> > PMC is necessary, b/c he will join the Commons PMC
>>>> after graduation by
>>>> > default
>>>> > - A contributor can be proposed by anybody - its up to
>>>> the PPMC to open the vote
>>>> > - A new Committer can be elected by the PPMC with
>>>> binding votes; as
>>>> > usual other Committers can vote unbinding. I don't
>>>> think it creates
>>>> > any problems b/c usually there is already a consens on
>>>> adding a person
>>>> > before calling a vote.
>>>> >
>>>> > Makes sense?
>>>> >
>>>> > Cheers
>>>> > Christian
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >>
>>>> >> Upayavira
>>>> >>
>>>> >> On Sun, 01 May 2011 19:56 +0200, "Simone Tripodi"
>>>> >> <si...@apache.org>
>>>> wrote:
>>>> >>> Hi Upayavira!!!
>>>> >>> I agree that commons folks can have rw rights,
>>>> so people are already
>>>> >>> used to co-work in the 'commons way'.
>>>> >>> Moreover, I agreed on joining
>>>> >>>
>>>> >>> - dev@commons.a.o
>>>> >>> - users@commons.a.o
>>>> >>> - issues@commons.a.o
>>>> >>> - create the private ML where commons PMCs can
>>>> join.
>>>> >>>
>>>> >>> Does it make sense?
>>>> >>> Simo
>>>> >>>
>>>> >>> http://people.apache.org/~simonetripodi/
>>>> >>> http://www.99soft.org/
>>>> >>>
>>>> >>>
>>>> >>>
>>>> >>> On Sun, May 1, 2011 at 7:22 PM, Upayavira
>>>> <uv...@odoko.co.uk>
>>>> wrote:
>>>> >>> > use commons-user: +1
>>>> >>> > put SVN in 'incubator' space: +1
>>>> >>> > grant "commons rw: +1 (assuming current
>>>> OGNL committers agree)
>>>> >>> >
>>>> >>> > As to a private list, I think the benefit
>>>> would be the opportunity for
>>>> >>> > the OGNL committers to learn how such
>>>> management happens. Where, for
>>>> >>> > example, would committer votes happen?
>>>> The issue with graduation to
>>>> >>> > Commons is what happens after graduation
>>>> - do they suddenly loose some
>>>> >>> > power over their own affairs, e.g. ease
>>>> of seeing vote threads. So not
>>>> >>> > sure the best on this one.
>>>> >>> >
>>>> >>> > Upayavira
>>>> >>> >
>>>> >>> > On Fri, 29 Apr 2011 08:29 -0700, "Henri
>>>> Yandell" <fl...@gmail.com>
>>>> >>> > wrote:
>>>> >>> >> Agreed, no need to use the svn
>>>> location from Commons; though I ask to
>>>> >>> >> allow @commons rw access.
>>>> >>> >>
>>>> >>> >> The committer of the podling would
>>>> not automatically become PMC
>>>> >>> >> members, so I don't think there is a
>>>> need to setup a private list (or
>>>> >>> >> even to consider it a PPMC).
>>>> >>> >>
>>>> >>> >> Hen
>>>> >>> >>
>>>> >>> >> On Thu, Apr 28, 2011 at 11:05 PM,
>>>> Christian Grobmeier
>>>> >>> >> <gr...@gmail.com>
>>>> wrote:
>>>> >>> >> >> we could share MLs and also
>>>> SVN (Sandbox
>>>> >>> >> >> would be nice, not?)
>>>> >>> >> >
>>>> >>> >> > MLs are fine, b/c one would need
>>>> to change address later, and
>>>> >>> >> > searching for pre-graduation
>>>> threads is more easily.
>>>> >>> >> >
>>>> >>> >> > For SVN I don't see a benefit.
>>>> The repos can be moved with less effort
>>>> >>> >> > once component is graduated. I
>>>> would like to avoid to get something
>>>> >>> >> > into the sandbox which is not
>>>> cleared from legal perspective. What, if
>>>> >>> >> > OGNL fails in the incubator and
>>>> we just forget to remove the code from
>>>> >>> >> > the sandbox? If its in the
>>>> incubator part, it is like a tag
>>>> >>> >> > saying:"beware"
>>>> >>> >> >
>>>> >>> >> > I would be +1 on user/dev ML but
>>>> leave SVN in incubator
>>>> >>> >> > Is there a need to create a pmc
>>>> ML for OGNL to discuss incubation
>>>> >>> >> > related matters?
>>>> >>> >> >
>>>> >>> >> > Cheers
>>>> >>> >> >
>>>> >>> >> >> What Incubator PMCs think
>>>> about it?
>>>> >>> >> >> Simo
>>>> >>> >> >>
>>>> >>> >> >> http://people.apache.org/~simonetripodi/
>>>> >>> >> >> http://www.99soft.org/
>>>> >>> >> >>
>>>> >>> >> >>
>>>> >>> >> >>
>>>> >>> >> >> On Fri, Apr 29, 2011 at 7:34
>>>> AM, Henri Yandell <fl...@gmail.com>
>>>> wrote:
>>>> >>> >> >>> Below is a thread from
>>>> the Commons Dev list in which I'm recommending
>>>> >>> >> >>> that OGNL use the
>>>> commons dev mailing list and that the svn
>>>> >>> >> >>> permissions allow the
>>>> ognl committers and the commons committers to
>>>> >>> >> >>> have read write access.
>>>> >>> >> >>>
>>>> >>> >> >>> http://commons.markmail.org/thread/ku3ouuilpiicb5is
>>>> >>> >> >>>
>>>> >>> >> >>> Is this a concern for
>>>> anyone?
>>>> >>> >> >>>
>>>> >>> >> >>> OGNL's target is to
>>>> graduate into Commons rather than to TLP, so
>>>> >>> >> >>> making it act like a TLP
>>>> seems destined to cause problems.
>>>> >>> >> >>>
>>>> >>> >> >>> Hen
>>>> >>> >> >>>
>>>> >>> >> >>>
>>>> ---------------------------------------------------------------------
>>>> >>> >> >>> To unsubscribe, e-mail:
>>>> general-unsubscribe@incubator.apache.org
>>>> >>> >> >>> For additional commands,
>>>> e-mail: general-help@incubator.apache.org
>>>> >>> >> >>>
>>>> >>> >> >>>
>>>> >>> >> >>
>>>> >>> >> >>
>>>> ---------------------------------------------------------------------
>>>> >>> >> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> >>> >> >> For additional commands,
>>>> e-mail: general-help@incubator.apache.org
>>>> >>> >> >>
>>>> >>> >> >>
>>>> >>> >> >
>>>> >>> >> >
>>>> >>> >> >
>>>> >>> >> > --
>>>> >>> >> > http://www.grobmeier.de
>>>> >>> >> >
>>>> >>> >> >
>>>> ---------------------------------------------------------------------
>>>> >>> >> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> >>> >> > For additional commands, e-mail:
>>>> general-help@incubator.apache.org
>>>> >>> >> >
>>>> >>> >> >
>>>> >>> >>
>>>> >>> >>
>>>> ---------------------------------------------------------------------
>>>> >>> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> >>> >> For additional commands, e-mail: general-help@incubator.apache.org
>>>> >>> >>
>>>> >>> >
>>>> >>> >
>>>> ---------------------------------------------------------------------
>>>> >>> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> >>> > For additional commands, e-mail: general-help@incubator.apache.org
>>>> >>> >
>>>> >>> >
>>>> >>>
>>>> >>>
>>>> ---------------------------------------------------------------------
>>>> >>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> >>> For additional commands, e-mail: general-help@incubator.apache.org
>>>> >>>
>>>> >>
>>>> >>
>>>> ---------------------------------------------------------------------
>>>> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> >> For additional commands, e-mail: general-help@incubator.apache.org
>>>> >>
>>>> >>
>>>> >
>>>> >
>>>> >
>>>> > --
>>>> > http://www.grobmeier.de
>>>> >
>>>> >
>>>> ---------------------------------------------------------------------
>>>> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> > For additional commands, e-mail: general-help@incubator.apache.org
>>>> >
>>>> >
>>>>
>>>>
>>>>
>>>> --
>>>> Olivier Lamy
>>>> http://twitter.com/olamy
>>>> http://www.linkedin.com/in/olamy
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: OGNL Infrastructure questions
Posted by Simone Tripodi <si...@apache.org>.
Hi again,
As you already noticed, the main Issue is INFRA-3597[1].
Many thanks in advance!
Simo
[1] https://issues.apache.org/jira/browse/INFRA-3597
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Tue, May 3, 2011 at 7:39 AM, Simone Tripodi <si...@apache.org> wrote:
> Hi all guys,
> the discussion in following up on INFRA-3601[1], please join to
> correct me if I'm wrong!
> Many thanks in advance,
> Simo
>
> [1] https://issues.apache.org/jira/browse/INFRA-3601
>
> http://people.apache.org/~simonetripodi/
> http://www.99soft.org/
>
>
>
> On Mon, May 2, 2011 at 10:35 AM, Mark Struberg <st...@yahoo.de> wrote:
>> just for the record (for the new contributors). As long as your incubating the following rules apply:
>>
>> http://incubator.apache.org/guides/ppmc.html
>>
>> At the time you graduate you need to check who really was active and 'cleanup' the PPMC. So not every person which was on the PPMC automatically makes it to the final PMC anyway ...
>>
>> LieGrue,
>> strub
>>
>> --- On Mon, 5/2/11, Olivier Lamy <ol...@apache.org> wrote:
>>
>>> From: Olivier Lamy <ol...@apache.org>
>>> Subject: Re: OGNL Infrastructure questions
>>> To: general@incubator.apache.org
>>> Date: Monday, May 2, 2011, 7:11 AM
>>> +1
>>>
>>>
>>>
>>> 2011/5/2 Christian Grobmeier <gr...@gmail.com>:
>>> >> My issue (for the commons PMC I guess) is how
>>> committer votes will
>>> >> happen when OGNL graduates.
>>> >>
>>> >> After graduation, how would one of the current
>>> contributors propose a
>>> >> new committer if they are not themselves on the
>>> Commons PMC?
>>> >
>>> > Proposal:
>>> >
>>> > - If you are a Commons PMC Member, you are an OGNL
>>> PPMC member by default
>>> > - If a Committer is invited to the PPMC, an additional
>>> vote on Commons
>>> > PMC is necessary, b/c he will join the Commons PMC
>>> after graduation by
>>> > default
>>> > - A contributor can be proposed by anybody - its up to
>>> the PPMC to open the vote
>>> > - A new Committer can be elected by the PPMC with
>>> binding votes; as
>>> > usual other Committers can vote unbinding. I don't
>>> think it creates
>>> > any problems b/c usually there is already a consens on
>>> adding a person
>>> > before calling a vote.
>>> >
>>> > Makes sense?
>>> >
>>> > Cheers
>>> > Christian
>>> >
>>> >
>>> >
>>> >
>>> >>
>>> >> Upayavira
>>> >>
>>> >> On Sun, 01 May 2011 19:56 +0200, "Simone Tripodi"
>>> >> <si...@apache.org>
>>> wrote:
>>> >>> Hi Upayavira!!!
>>> >>> I agree that commons folks can have rw rights,
>>> so people are already
>>> >>> used to co-work in the 'commons way'.
>>> >>> Moreover, I agreed on joining
>>> >>>
>>> >>> - dev@commons.a.o
>>> >>> - users@commons.a.o
>>> >>> - issues@commons.a.o
>>> >>> - create the private ML where commons PMCs can
>>> join.
>>> >>>
>>> >>> Does it make sense?
>>> >>> Simo
>>> >>>
>>> >>> http://people.apache.org/~simonetripodi/
>>> >>> http://www.99soft.org/
>>> >>>
>>> >>>
>>> >>>
>>> >>> On Sun, May 1, 2011 at 7:22 PM, Upayavira
>>> <uv...@odoko.co.uk>
>>> wrote:
>>> >>> > use commons-user: +1
>>> >>> > put SVN in 'incubator' space: +1
>>> >>> > grant "commons rw: +1 (assuming current
>>> OGNL committers agree)
>>> >>> >
>>> >>> > As to a private list, I think the benefit
>>> would be the opportunity for
>>> >>> > the OGNL committers to learn how such
>>> management happens. Where, for
>>> >>> > example, would committer votes happen?
>>> The issue with graduation to
>>> >>> > Commons is what happens after graduation
>>> - do they suddenly loose some
>>> >>> > power over their own affairs, e.g. ease
>>> of seeing vote threads. So not
>>> >>> > sure the best on this one.
>>> >>> >
>>> >>> > Upayavira
>>> >>> >
>>> >>> > On Fri, 29 Apr 2011 08:29 -0700, "Henri
>>> Yandell" <fl...@gmail.com>
>>> >>> > wrote:
>>> >>> >> Agreed, no need to use the svn
>>> location from Commons; though I ask to
>>> >>> >> allow @commons rw access.
>>> >>> >>
>>> >>> >> The committer of the podling would
>>> not automatically become PMC
>>> >>> >> members, so I don't think there is a
>>> need to setup a private list (or
>>> >>> >> even to consider it a PPMC).
>>> >>> >>
>>> >>> >> Hen
>>> >>> >>
>>> >>> >> On Thu, Apr 28, 2011 at 11:05 PM,
>>> Christian Grobmeier
>>> >>> >> <gr...@gmail.com>
>>> wrote:
>>> >>> >> >> we could share MLs and also
>>> SVN (Sandbox
>>> >>> >> >> would be nice, not?)
>>> >>> >> >
>>> >>> >> > MLs are fine, b/c one would need
>>> to change address later, and
>>> >>> >> > searching for pre-graduation
>>> threads is more easily.
>>> >>> >> >
>>> >>> >> > For SVN I don't see a benefit.
>>> The repos can be moved with less effort
>>> >>> >> > once component is graduated. I
>>> would like to avoid to get something
>>> >>> >> > into the sandbox which is not
>>> cleared from legal perspective. What, if
>>> >>> >> > OGNL fails in the incubator and
>>> we just forget to remove the code from
>>> >>> >> > the sandbox? If its in the
>>> incubator part, it is like a tag
>>> >>> >> > saying:"beware"
>>> >>> >> >
>>> >>> >> > I would be +1 on user/dev ML but
>>> leave SVN in incubator
>>> >>> >> > Is there a need to create a pmc
>>> ML for OGNL to discuss incubation
>>> >>> >> > related matters?
>>> >>> >> >
>>> >>> >> > Cheers
>>> >>> >> >
>>> >>> >> >> What Incubator PMCs think
>>> about it?
>>> >>> >> >> Simo
>>> >>> >> >>
>>> >>> >> >> http://people.apache.org/~simonetripodi/
>>> >>> >> >> http://www.99soft.org/
>>> >>> >> >>
>>> >>> >> >>
>>> >>> >> >>
>>> >>> >> >> On Fri, Apr 29, 2011 at 7:34
>>> AM, Henri Yandell <fl...@gmail.com>
>>> wrote:
>>> >>> >> >>> Below is a thread from
>>> the Commons Dev list in which I'm recommending
>>> >>> >> >>> that OGNL use the
>>> commons dev mailing list and that the svn
>>> >>> >> >>> permissions allow the
>>> ognl committers and the commons committers to
>>> >>> >> >>> have read write access.
>>> >>> >> >>>
>>> >>> >> >>> http://commons.markmail.org/thread/ku3ouuilpiicb5is
>>> >>> >> >>>
>>> >>> >> >>> Is this a concern for
>>> anyone?
>>> >>> >> >>>
>>> >>> >> >>> OGNL's target is to
>>> graduate into Commons rather than to TLP, so
>>> >>> >> >>> making it act like a TLP
>>> seems destined to cause problems.
>>> >>> >> >>>
>>> >>> >> >>> Hen
>>> >>> >> >>>
>>> >>> >> >>>
>>> ---------------------------------------------------------------------
>>> >>> >> >>> To unsubscribe, e-mail:
>>> general-unsubscribe@incubator.apache.org
>>> >>> >> >>> For additional commands,
>>> e-mail: general-help@incubator.apache.org
>>> >>> >> >>>
>>> >>> >> >>>
>>> >>> >> >>
>>> >>> >> >>
>>> ---------------------------------------------------------------------
>>> >>> >> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> >>> >> >> For additional commands,
>>> e-mail: general-help@incubator.apache.org
>>> >>> >> >>
>>> >>> >> >>
>>> >>> >> >
>>> >>> >> >
>>> >>> >> >
>>> >>> >> > --
>>> >>> >> > http://www.grobmeier.de
>>> >>> >> >
>>> >>> >> >
>>> ---------------------------------------------------------------------
>>> >>> >> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> >>> >> > For additional commands, e-mail:
>>> general-help@incubator.apache.org
>>> >>> >> >
>>> >>> >> >
>>> >>> >>
>>> >>> >>
>>> ---------------------------------------------------------------------
>>> >>> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> >>> >> For additional commands, e-mail: general-help@incubator.apache.org
>>> >>> >>
>>> >>> >
>>> >>> >
>>> ---------------------------------------------------------------------
>>> >>> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> >>> > For additional commands, e-mail: general-help@incubator.apache.org
>>> >>> >
>>> >>> >
>>> >>>
>>> >>>
>>> ---------------------------------------------------------------------
>>> >>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> >>> For additional commands, e-mail: general-help@incubator.apache.org
>>> >>>
>>> >>
>>> >>
>>> ---------------------------------------------------------------------
>>> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> >> For additional commands, e-mail: general-help@incubator.apache.org
>>> >>
>>> >>
>>> >
>>> >
>>> >
>>> > --
>>> > http://www.grobmeier.de
>>> >
>>> >
>>> ---------------------------------------------------------------------
>>> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> > For additional commands, e-mail: general-help@incubator.apache.org
>>> >
>>> >
>>>
>>>
>>>
>>> --
>>> Olivier Lamy
>>> http://twitter.com/olamy
>>> http://www.linkedin.com/in/olamy
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: OGNL Infrastructure questions
Posted by Simone Tripodi <si...@apache.org>.
Hi all guys,
the discussion in following up on INFRA-3601[1], please join to
correct me if I'm wrong!
Many thanks in advance,
Simo
[1] https://issues.apache.org/jira/browse/INFRA-3601
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Mon, May 2, 2011 at 10:35 AM, Mark Struberg <st...@yahoo.de> wrote:
> just for the record (for the new contributors). As long as your incubating the following rules apply:
>
> http://incubator.apache.org/guides/ppmc.html
>
> At the time you graduate you need to check who really was active and 'cleanup' the PPMC. So not every person which was on the PPMC automatically makes it to the final PMC anyway ...
>
> LieGrue,
> strub
>
> --- On Mon, 5/2/11, Olivier Lamy <ol...@apache.org> wrote:
>
>> From: Olivier Lamy <ol...@apache.org>
>> Subject: Re: OGNL Infrastructure questions
>> To: general@incubator.apache.org
>> Date: Monday, May 2, 2011, 7:11 AM
>> +1
>>
>>
>>
>> 2011/5/2 Christian Grobmeier <gr...@gmail.com>:
>> >> My issue (for the commons PMC I guess) is how
>> committer votes will
>> >> happen when OGNL graduates.
>> >>
>> >> After graduation, how would one of the current
>> contributors propose a
>> >> new committer if they are not themselves on the
>> Commons PMC?
>> >
>> > Proposal:
>> >
>> > - If you are a Commons PMC Member, you are an OGNL
>> PPMC member by default
>> > - If a Committer is invited to the PPMC, an additional
>> vote on Commons
>> > PMC is necessary, b/c he will join the Commons PMC
>> after graduation by
>> > default
>> > - A contributor can be proposed by anybody - its up to
>> the PPMC to open the vote
>> > - A new Committer can be elected by the PPMC with
>> binding votes; as
>> > usual other Committers can vote unbinding. I don't
>> think it creates
>> > any problems b/c usually there is already a consens on
>> adding a person
>> > before calling a vote.
>> >
>> > Makes sense?
>> >
>> > Cheers
>> > Christian
>> >
>> >
>> >
>> >
>> >>
>> >> Upayavira
>> >>
>> >> On Sun, 01 May 2011 19:56 +0200, "Simone Tripodi"
>> >> <si...@apache.org>
>> wrote:
>> >>> Hi Upayavira!!!
>> >>> I agree that commons folks can have rw rights,
>> so people are already
>> >>> used to co-work in the 'commons way'.
>> >>> Moreover, I agreed on joining
>> >>>
>> >>> - dev@commons.a.o
>> >>> - users@commons.a.o
>> >>> - issues@commons.a.o
>> >>> - create the private ML where commons PMCs can
>> join.
>> >>>
>> >>> Does it make sense?
>> >>> Simo
>> >>>
>> >>> http://people.apache.org/~simonetripodi/
>> >>> http://www.99soft.org/
>> >>>
>> >>>
>> >>>
>> >>> On Sun, May 1, 2011 at 7:22 PM, Upayavira
>> <uv...@odoko.co.uk>
>> wrote:
>> >>> > use commons-user: +1
>> >>> > put SVN in 'incubator' space: +1
>> >>> > grant "commons rw: +1 (assuming current
>> OGNL committers agree)
>> >>> >
>> >>> > As to a private list, I think the benefit
>> would be the opportunity for
>> >>> > the OGNL committers to learn how such
>> management happens. Where, for
>> >>> > example, would committer votes happen?
>> The issue with graduation to
>> >>> > Commons is what happens after graduation
>> - do they suddenly loose some
>> >>> > power over their own affairs, e.g. ease
>> of seeing vote threads. So not
>> >>> > sure the best on this one.
>> >>> >
>> >>> > Upayavira
>> >>> >
>> >>> > On Fri, 29 Apr 2011 08:29 -0700, "Henri
>> Yandell" <fl...@gmail.com>
>> >>> > wrote:
>> >>> >> Agreed, no need to use the svn
>> location from Commons; though I ask to
>> >>> >> allow @commons rw access.
>> >>> >>
>> >>> >> The committer of the podling would
>> not automatically become PMC
>> >>> >> members, so I don't think there is a
>> need to setup a private list (or
>> >>> >> even to consider it a PPMC).
>> >>> >>
>> >>> >> Hen
>> >>> >>
>> >>> >> On Thu, Apr 28, 2011 at 11:05 PM,
>> Christian Grobmeier
>> >>> >> <gr...@gmail.com>
>> wrote:
>> >>> >> >> we could share MLs and also
>> SVN (Sandbox
>> >>> >> >> would be nice, not?)
>> >>> >> >
>> >>> >> > MLs are fine, b/c one would need
>> to change address later, and
>> >>> >> > searching for pre-graduation
>> threads is more easily.
>> >>> >> >
>> >>> >> > For SVN I don't see a benefit.
>> The repos can be moved with less effort
>> >>> >> > once component is graduated. I
>> would like to avoid to get something
>> >>> >> > into the sandbox which is not
>> cleared from legal perspective. What, if
>> >>> >> > OGNL fails in the incubator and
>> we just forget to remove the code from
>> >>> >> > the sandbox? If its in the
>> incubator part, it is like a tag
>> >>> >> > saying:"beware"
>> >>> >> >
>> >>> >> > I would be +1 on user/dev ML but
>> leave SVN in incubator
>> >>> >> > Is there a need to create a pmc
>> ML for OGNL to discuss incubation
>> >>> >> > related matters?
>> >>> >> >
>> >>> >> > Cheers
>> >>> >> >
>> >>> >> >> What Incubator PMCs think
>> about it?
>> >>> >> >> Simo
>> >>> >> >>
>> >>> >> >> http://people.apache.org/~simonetripodi/
>> >>> >> >> http://www.99soft.org/
>> >>> >> >>
>> >>> >> >>
>> >>> >> >>
>> >>> >> >> On Fri, Apr 29, 2011 at 7:34
>> AM, Henri Yandell <fl...@gmail.com>
>> wrote:
>> >>> >> >>> Below is a thread from
>> the Commons Dev list in which I'm recommending
>> >>> >> >>> that OGNL use the
>> commons dev mailing list and that the svn
>> >>> >> >>> permissions allow the
>> ognl committers and the commons committers to
>> >>> >> >>> have read write access.
>> >>> >> >>>
>> >>> >> >>> http://commons.markmail.org/thread/ku3ouuilpiicb5is
>> >>> >> >>>
>> >>> >> >>> Is this a concern for
>> anyone?
>> >>> >> >>>
>> >>> >> >>> OGNL's target is to
>> graduate into Commons rather than to TLP, so
>> >>> >> >>> making it act like a TLP
>> seems destined to cause problems.
>> >>> >> >>>
>> >>> >> >>> Hen
>> >>> >> >>>
>> >>> >> >>>
>> ---------------------------------------------------------------------
>> >>> >> >>> To unsubscribe, e-mail:
>> general-unsubscribe@incubator.apache.org
>> >>> >> >>> For additional commands,
>> e-mail: general-help@incubator.apache.org
>> >>> >> >>>
>> >>> >> >>>
>> >>> >> >>
>> >>> >> >>
>> ---------------------------------------------------------------------
>> >>> >> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> >>> >> >> For additional commands,
>> e-mail: general-help@incubator.apache.org
>> >>> >> >>
>> >>> >> >>
>> >>> >> >
>> >>> >> >
>> >>> >> >
>> >>> >> > --
>> >>> >> > http://www.grobmeier.de
>> >>> >> >
>> >>> >> >
>> ---------------------------------------------------------------------
>> >>> >> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> >>> >> > For additional commands, e-mail:
>> general-help@incubator.apache.org
>> >>> >> >
>> >>> >> >
>> >>> >>
>> >>> >>
>> ---------------------------------------------------------------------
>> >>> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> >>> >> For additional commands, e-mail: general-help@incubator.apache.org
>> >>> >>
>> >>> >
>> >>> >
>> ---------------------------------------------------------------------
>> >>> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> >>> > For additional commands, e-mail: general-help@incubator.apache.org
>> >>> >
>> >>> >
>> >>>
>> >>>
>> ---------------------------------------------------------------------
>> >>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> >>> For additional commands, e-mail: general-help@incubator.apache.org
>> >>>
>> >>
>> >>
>> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> >> For additional commands, e-mail: general-help@incubator.apache.org
>> >>
>> >>
>> >
>> >
>> >
>> > --
>> > http://www.grobmeier.de
>> >
>> >
>> ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> > For additional commands, e-mail: general-help@incubator.apache.org
>> >
>> >
>>
>>
>>
>> --
>> Olivier Lamy
>> http://twitter.com/olamy
>> http://www.linkedin.com/in/olamy
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: OGNL Infrastructure questions
Posted by Mark Struberg <st...@yahoo.de>.
just for the record (for the new contributors). As long as your incubating the following rules apply:
http://incubator.apache.org/guides/ppmc.html
At the time you graduate you need to check who really was active and 'cleanup' the PPMC. So not every person which was on the PPMC automatically makes it to the final PMC anyway ...
LieGrue,
strub
--- On Mon, 5/2/11, Olivier Lamy <ol...@apache.org> wrote:
> From: Olivier Lamy <ol...@apache.org>
> Subject: Re: OGNL Infrastructure questions
> To: general@incubator.apache.org
> Date: Monday, May 2, 2011, 7:11 AM
> +1
>
>
>
> 2011/5/2 Christian Grobmeier <gr...@gmail.com>:
> >> My issue (for the commons PMC I guess) is how
> committer votes will
> >> happen when OGNL graduates.
> >>
> >> After graduation, how would one of the current
> contributors propose a
> >> new committer if they are not themselves on the
> Commons PMC?
> >
> > Proposal:
> >
> > - If you are a Commons PMC Member, you are an OGNL
> PPMC member by default
> > - If a Committer is invited to the PPMC, an additional
> vote on Commons
> > PMC is necessary, b/c he will join the Commons PMC
> after graduation by
> > default
> > - A contributor can be proposed by anybody - its up to
> the PPMC to open the vote
> > - A new Committer can be elected by the PPMC with
> binding votes; as
> > usual other Committers can vote unbinding. I don't
> think it creates
> > any problems b/c usually there is already a consens on
> adding a person
> > before calling a vote.
> >
> > Makes sense?
> >
> > Cheers
> > Christian
> >
> >
> >
> >
> >>
> >> Upayavira
> >>
> >> On Sun, 01 May 2011 19:56 +0200, "Simone Tripodi"
> >> <si...@apache.org>
> wrote:
> >>> Hi Upayavira!!!
> >>> I agree that commons folks can have rw rights,
> so people are already
> >>> used to co-work in the 'commons way'.
> >>> Moreover, I agreed on joining
> >>>
> >>> - dev@commons.a.o
> >>> - users@commons.a.o
> >>> - issues@commons.a.o
> >>> - create the private ML where commons PMCs can
> join.
> >>>
> >>> Does it make sense?
> >>> Simo
> >>>
> >>> http://people.apache.org/~simonetripodi/
> >>> http://www.99soft.org/
> >>>
> >>>
> >>>
> >>> On Sun, May 1, 2011 at 7:22 PM, Upayavira
> <uv...@odoko.co.uk>
> wrote:
> >>> > use commons-user: +1
> >>> > put SVN in 'incubator' space: +1
> >>> > grant "commons rw: +1 (assuming current
> OGNL committers agree)
> >>> >
> >>> > As to a private list, I think the benefit
> would be the opportunity for
> >>> > the OGNL committers to learn how such
> management happens. Where, for
> >>> > example, would committer votes happen?
> The issue with graduation to
> >>> > Commons is what happens after graduation
> - do they suddenly loose some
> >>> > power over their own affairs, e.g. ease
> of seeing vote threads. So not
> >>> > sure the best on this one.
> >>> >
> >>> > Upayavira
> >>> >
> >>> > On Fri, 29 Apr 2011 08:29 -0700, "Henri
> Yandell" <fl...@gmail.com>
> >>> > wrote:
> >>> >> Agreed, no need to use the svn
> location from Commons; though I ask to
> >>> >> allow @commons rw access.
> >>> >>
> >>> >> The committer of the podling would
> not automatically become PMC
> >>> >> members, so I don't think there is a
> need to setup a private list (or
> >>> >> even to consider it a PPMC).
> >>> >>
> >>> >> Hen
> >>> >>
> >>> >> On Thu, Apr 28, 2011 at 11:05 PM,
> Christian Grobmeier
> >>> >> <gr...@gmail.com>
> wrote:
> >>> >> >> we could share MLs and also
> SVN (Sandbox
> >>> >> >> would be nice, not?)
> >>> >> >
> >>> >> > MLs are fine, b/c one would need
> to change address later, and
> >>> >> > searching for pre-graduation
> threads is more easily.
> >>> >> >
> >>> >> > For SVN I don't see a benefit.
> The repos can be moved with less effort
> >>> >> > once component is graduated. I
> would like to avoid to get something
> >>> >> > into the sandbox which is not
> cleared from legal perspective. What, if
> >>> >> > OGNL fails in the incubator and
> we just forget to remove the code from
> >>> >> > the sandbox? If its in the
> incubator part, it is like a tag
> >>> >> > saying:"beware"
> >>> >> >
> >>> >> > I would be +1 on user/dev ML but
> leave SVN in incubator
> >>> >> > Is there a need to create a pmc
> ML for OGNL to discuss incubation
> >>> >> > related matters?
> >>> >> >
> >>> >> > Cheers
> >>> >> >
> >>> >> >> What Incubator PMCs think
> about it?
> >>> >> >> Simo
> >>> >> >>
> >>> >> >> http://people.apache.org/~simonetripodi/
> >>> >> >> http://www.99soft.org/
> >>> >> >>
> >>> >> >>
> >>> >> >>
> >>> >> >> On Fri, Apr 29, 2011 at 7:34
> AM, Henri Yandell <fl...@gmail.com>
> wrote:
> >>> >> >>> Below is a thread from
> the Commons Dev list in which I'm recommending
> >>> >> >>> that OGNL use the
> commons dev mailing list and that the svn
> >>> >> >>> permissions allow the
> ognl committers and the commons committers to
> >>> >> >>> have read write access.
> >>> >> >>>
> >>> >> >>> http://commons.markmail.org/thread/ku3ouuilpiicb5is
> >>> >> >>>
> >>> >> >>> Is this a concern for
> anyone?
> >>> >> >>>
> >>> >> >>> OGNL's target is to
> graduate into Commons rather than to TLP, so
> >>> >> >>> making it act like a TLP
> seems destined to cause problems.
> >>> >> >>>
> >>> >> >>> Hen
> >>> >> >>>
> >>> >> >>>
> ---------------------------------------------------------------------
> >>> >> >>> To unsubscribe, e-mail:
> general-unsubscribe@incubator.apache.org
> >>> >> >>> For additional commands,
> e-mail: general-help@incubator.apache.org
> >>> >> >>>
> >>> >> >>>
> >>> >> >>
> >>> >> >>
> ---------------------------------------------------------------------
> >>> >> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >>> >> >> For additional commands,
> e-mail: general-help@incubator.apache.org
> >>> >> >>
> >>> >> >>
> >>> >> >
> >>> >> >
> >>> >> >
> >>> >> > --
> >>> >> > http://www.grobmeier.de
> >>> >> >
> >>> >> >
> ---------------------------------------------------------------------
> >>> >> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >>> >> > For additional commands, e-mail:
> general-help@incubator.apache.org
> >>> >> >
> >>> >> >
> >>> >>
> >>> >>
> ---------------------------------------------------------------------
> >>> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >>> >> For additional commands, e-mail: general-help@incubator.apache.org
> >>> >>
> >>> >
> >>> >
> ---------------------------------------------------------------------
> >>> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >>> > For additional commands, e-mail: general-help@incubator.apache.org
> >>> >
> >>> >
> >>>
> >>>
> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >>> For additional commands, e-mail: general-help@incubator.apache.org
> >>>
> >>
> >>
> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >> For additional commands, e-mail: general-help@incubator.apache.org
> >>
> >>
> >
> >
> >
> > --
> > http://www.grobmeier.de
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
> >
>
>
>
> --
> Olivier Lamy
> http://twitter.com/olamy
> http://www.linkedin.com/in/olamy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: OGNL Infrastructure questions
Posted by Olivier Lamy <ol...@apache.org>.
+1
2011/5/2 Christian Grobmeier <gr...@gmail.com>:
>> My issue (for the commons PMC I guess) is how committer votes will
>> happen when OGNL graduates.
>>
>> After graduation, how would one of the current contributors propose a
>> new committer if they are not themselves on the Commons PMC?
>
> Proposal:
>
> - If you are a Commons PMC Member, you are an OGNL PPMC member by default
> - If a Committer is invited to the PPMC, an additional vote on Commons
> PMC is necessary, b/c he will join the Commons PMC after graduation by
> default
> - A contributor can be proposed by anybody - its up to the PPMC to open the vote
> - A new Committer can be elected by the PPMC with binding votes; as
> usual other Committers can vote unbinding. I don't think it creates
> any problems b/c usually there is already a consens on adding a person
> before calling a vote.
>
> Makes sense?
>
> Cheers
> Christian
>
>
>
>
>>
>> Upayavira
>>
>> On Sun, 01 May 2011 19:56 +0200, "Simone Tripodi"
>> <si...@apache.org> wrote:
>>> Hi Upayavira!!!
>>> I agree that commons folks can have rw rights, so people are already
>>> used to co-work in the 'commons way'.
>>> Moreover, I agreed on joining
>>>
>>> - dev@commons.a.o
>>> - users@commons.a.o
>>> - issues@commons.a.o
>>> - create the private ML where commons PMCs can join.
>>>
>>> Does it make sense?
>>> Simo
>>>
>>> http://people.apache.org/~simonetripodi/
>>> http://www.99soft.org/
>>>
>>>
>>>
>>> On Sun, May 1, 2011 at 7:22 PM, Upayavira <uv...@odoko.co.uk> wrote:
>>> > use commons-user: +1
>>> > put SVN in 'incubator' space: +1
>>> > grant "commons rw: +1 (assuming current OGNL committers agree)
>>> >
>>> > As to a private list, I think the benefit would be the opportunity for
>>> > the OGNL committers to learn how such management happens. Where, for
>>> > example, would committer votes happen? The issue with graduation to
>>> > Commons is what happens after graduation - do they suddenly loose some
>>> > power over their own affairs, e.g. ease of seeing vote threads. So not
>>> > sure the best on this one.
>>> >
>>> > Upayavira
>>> >
>>> > On Fri, 29 Apr 2011 08:29 -0700, "Henri Yandell" <fl...@gmail.com>
>>> > wrote:
>>> >> Agreed, no need to use the svn location from Commons; though I ask to
>>> >> allow @commons rw access.
>>> >>
>>> >> The committer of the podling would not automatically become PMC
>>> >> members, so I don't think there is a need to setup a private list (or
>>> >> even to consider it a PPMC).
>>> >>
>>> >> Hen
>>> >>
>>> >> On Thu, Apr 28, 2011 at 11:05 PM, Christian Grobmeier
>>> >> <gr...@gmail.com> wrote:
>>> >> >> we could share MLs and also SVN (Sandbox
>>> >> >> would be nice, not?)
>>> >> >
>>> >> > MLs are fine, b/c one would need to change address later, and
>>> >> > searching for pre-graduation threads is more easily.
>>> >> >
>>> >> > For SVN I don't see a benefit. The repos can be moved with less effort
>>> >> > once component is graduated. I would like to avoid to get something
>>> >> > into the sandbox which is not cleared from legal perspective. What, if
>>> >> > OGNL fails in the incubator and we just forget to remove the code from
>>> >> > the sandbox? If its in the incubator part, it is like a tag
>>> >> > saying:"beware"
>>> >> >
>>> >> > I would be +1 on user/dev ML but leave SVN in incubator
>>> >> > Is there a need to create a pmc ML for OGNL to discuss incubation
>>> >> > related matters?
>>> >> >
>>> >> > Cheers
>>> >> >
>>> >> >> What Incubator PMCs think about it?
>>> >> >> Simo
>>> >> >>
>>> >> >> http://people.apache.org/~simonetripodi/
>>> >> >> http://www.99soft.org/
>>> >> >>
>>> >> >>
>>> >> >>
>>> >> >> On Fri, Apr 29, 2011 at 7:34 AM, Henri Yandell <fl...@gmail.com> wrote:
>>> >> >>> Below is a thread from the Commons Dev list in which I'm recommending
>>> >> >>> that OGNL use the commons dev mailing list and that the svn
>>> >> >>> permissions allow the ognl committers and the commons committers to
>>> >> >>> have read write access.
>>> >> >>>
>>> >> >>> http://commons.markmail.org/thread/ku3ouuilpiicb5is
>>> >> >>>
>>> >> >>> Is this a concern for anyone?
>>> >> >>>
>>> >> >>> OGNL's target is to graduate into Commons rather than to TLP, so
>>> >> >>> making it act like a TLP seems destined to cause problems.
>>> >> >>>
>>> >> >>> Hen
>>> >> >>>
>>> >> >>> ---------------------------------------------------------------------
>>> >> >>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> >> >>> For additional commands, e-mail: general-help@incubator.apache.org
>>> >> >>>
>>> >> >>>
>>> >> >>
>>> >> >> ---------------------------------------------------------------------
>>> >> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> >> >> For additional commands, e-mail: general-help@incubator.apache.org
>>> >> >>
>>> >> >>
>>> >> >
>>> >> >
>>> >> >
>>> >> > --
>>> >> > http://www.grobmeier.de
>>> >> >
>>> >> > ---------------------------------------------------------------------
>>> >> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> >> > For additional commands, e-mail: general-help@incubator.apache.org
>>> >> >
>>> >> >
>>> >>
>>> >> ---------------------------------------------------------------------
>>> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> >> For additional commands, e-mail: general-help@incubator.apache.org
>>> >>
>>> >
>>> > ---------------------------------------------------------------------
>>> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> > For additional commands, e-mail: general-help@incubator.apache.org
>>> >
>>> >
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>
>
>
> --
> http://www.grobmeier.de
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
--
Olivier Lamy
http://twitter.com/olamy
http://www.linkedin.com/in/olamy
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: OGNL Infrastructure questions
Posted by Christian Grobmeier <gr...@gmail.com>.
> My issue (for the commons PMC I guess) is how committer votes will
> happen when OGNL graduates.
>
> After graduation, how would one of the current contributors propose a
> new committer if they are not themselves on the Commons PMC?
Proposal:
- If you are a Commons PMC Member, you are an OGNL PPMC member by default
- If a Committer is invited to the PPMC, an additional vote on Commons
PMC is necessary, b/c he will join the Commons PMC after graduation by
default
- A contributor can be proposed by anybody - its up to the PPMC to open the vote
- A new Committer can be elected by the PPMC with binding votes; as
usual other Committers can vote unbinding. I don't think it creates
any problems b/c usually there is already a consens on adding a person
before calling a vote.
Makes sense?
Cheers
Christian
>
> Upayavira
>
> On Sun, 01 May 2011 19:56 +0200, "Simone Tripodi"
> <si...@apache.org> wrote:
>> Hi Upayavira!!!
>> I agree that commons folks can have rw rights, so people are already
>> used to co-work in the 'commons way'.
>> Moreover, I agreed on joining
>>
>> - dev@commons.a.o
>> - users@commons.a.o
>> - issues@commons.a.o
>> - create the private ML where commons PMCs can join.
>>
>> Does it make sense?
>> Simo
>>
>> http://people.apache.org/~simonetripodi/
>> http://www.99soft.org/
>>
>>
>>
>> On Sun, May 1, 2011 at 7:22 PM, Upayavira <uv...@odoko.co.uk> wrote:
>> > use commons-user: +1
>> > put SVN in 'incubator' space: +1
>> > grant "commons rw: +1 (assuming current OGNL committers agree)
>> >
>> > As to a private list, I think the benefit would be the opportunity for
>> > the OGNL committers to learn how such management happens. Where, for
>> > example, would committer votes happen? The issue with graduation to
>> > Commons is what happens after graduation - do they suddenly loose some
>> > power over their own affairs, e.g. ease of seeing vote threads. So not
>> > sure the best on this one.
>> >
>> > Upayavira
>> >
>> > On Fri, 29 Apr 2011 08:29 -0700, "Henri Yandell" <fl...@gmail.com>
>> > wrote:
>> >> Agreed, no need to use the svn location from Commons; though I ask to
>> >> allow @commons rw access.
>> >>
>> >> The committer of the podling would not automatically become PMC
>> >> members, so I don't think there is a need to setup a private list (or
>> >> even to consider it a PPMC).
>> >>
>> >> Hen
>> >>
>> >> On Thu, Apr 28, 2011 at 11:05 PM, Christian Grobmeier
>> >> <gr...@gmail.com> wrote:
>> >> >> we could share MLs and also SVN (Sandbox
>> >> >> would be nice, not?)
>> >> >
>> >> > MLs are fine, b/c one would need to change address later, and
>> >> > searching for pre-graduation threads is more easily.
>> >> >
>> >> > For SVN I don't see a benefit. The repos can be moved with less effort
>> >> > once component is graduated. I would like to avoid to get something
>> >> > into the sandbox which is not cleared from legal perspective. What, if
>> >> > OGNL fails in the incubator and we just forget to remove the code from
>> >> > the sandbox? If its in the incubator part, it is like a tag
>> >> > saying:"beware"
>> >> >
>> >> > I would be +1 on user/dev ML but leave SVN in incubator
>> >> > Is there a need to create a pmc ML for OGNL to discuss incubation
>> >> > related matters?
>> >> >
>> >> > Cheers
>> >> >
>> >> >> What Incubator PMCs think about it?
>> >> >> Simo
>> >> >>
>> >> >> http://people.apache.org/~simonetripodi/
>> >> >> http://www.99soft.org/
>> >> >>
>> >> >>
>> >> >>
>> >> >> On Fri, Apr 29, 2011 at 7:34 AM, Henri Yandell <fl...@gmail.com> wrote:
>> >> >>> Below is a thread from the Commons Dev list in which I'm recommending
>> >> >>> that OGNL use the commons dev mailing list and that the svn
>> >> >>> permissions allow the ognl committers and the commons committers to
>> >> >>> have read write access.
>> >> >>>
>> >> >>> http://commons.markmail.org/thread/ku3ouuilpiicb5is
>> >> >>>
>> >> >>> Is this a concern for anyone?
>> >> >>>
>> >> >>> OGNL's target is to graduate into Commons rather than to TLP, so
>> >> >>> making it act like a TLP seems destined to cause problems.
>> >> >>>
>> >> >>> Hen
>> >> >>>
>> >> >>> ---------------------------------------------------------------------
>> >> >>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> >> >>> For additional commands, e-mail: general-help@incubator.apache.org
>> >> >>>
>> >> >>>
>> >> >>
>> >> >> ---------------------------------------------------------------------
>> >> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> >> >> For additional commands, e-mail: general-help@incubator.apache.org
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > http://www.grobmeier.de
>> >> >
>> >> > ---------------------------------------------------------------------
>> >> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> >> > For additional commands, e-mail: general-help@incubator.apache.org
>> >> >
>> >> >
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> >> For additional commands, e-mail: general-help@incubator.apache.org
>> >>
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> > For additional commands, e-mail: general-help@incubator.apache.org
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
--
http://www.grobmeier.de
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: OGNL Infrastructure questions
Posted by Upayavira <uv...@odoko.co.uk>.
Hi Simone,
My issue (for the commons PMC I guess) is how committer votes will
happen when OGNL graduates.
After graduation, how would one of the current contributors propose a
new committer if they are not themselves on the Commons PMC?
Upayavira
On Sun, 01 May 2011 19:56 +0200, "Simone Tripodi"
<si...@apache.org> wrote:
> Hi Upayavira!!!
> I agree that commons folks can have rw rights, so people are already
> used to co-work in the 'commons way'.
> Moreover, I agreed on joining
>
> - dev@commons.a.o
> - users@commons.a.o
> - issues@commons.a.o
> - create the private ML where commons PMCs can join.
>
> Does it make sense?
> Simo
>
> http://people.apache.org/~simonetripodi/
> http://www.99soft.org/
>
>
>
> On Sun, May 1, 2011 at 7:22 PM, Upayavira <uv...@odoko.co.uk> wrote:
> > use commons-user: +1
> > put SVN in 'incubator' space: +1
> > grant "commons rw: +1 (assuming current OGNL committers agree)
> >
> > As to a private list, I think the benefit would be the opportunity for
> > the OGNL committers to learn how such management happens. Where, for
> > example, would committer votes happen? The issue with graduation to
> > Commons is what happens after graduation - do they suddenly loose some
> > power over their own affairs, e.g. ease of seeing vote threads. So not
> > sure the best on this one.
> >
> > Upayavira
> >
> > On Fri, 29 Apr 2011 08:29 -0700, "Henri Yandell" <fl...@gmail.com>
> > wrote:
> >> Agreed, no need to use the svn location from Commons; though I ask to
> >> allow @commons rw access.
> >>
> >> The committer of the podling would not automatically become PMC
> >> members, so I don't think there is a need to setup a private list (or
> >> even to consider it a PPMC).
> >>
> >> Hen
> >>
> >> On Thu, Apr 28, 2011 at 11:05 PM, Christian Grobmeier
> >> <gr...@gmail.com> wrote:
> >> >> we could share MLs and also SVN (Sandbox
> >> >> would be nice, not?)
> >> >
> >> > MLs are fine, b/c one would need to change address later, and
> >> > searching for pre-graduation threads is more easily.
> >> >
> >> > For SVN I don't see a benefit. The repos can be moved with less effort
> >> > once component is graduated. I would like to avoid to get something
> >> > into the sandbox which is not cleared from legal perspective. What, if
> >> > OGNL fails in the incubator and we just forget to remove the code from
> >> > the sandbox? If its in the incubator part, it is like a tag
> >> > saying:"beware"
> >> >
> >> > I would be +1 on user/dev ML but leave SVN in incubator
> >> > Is there a need to create a pmc ML for OGNL to discuss incubation
> >> > related matters?
> >> >
> >> > Cheers
> >> >
> >> >> What Incubator PMCs think about it?
> >> >> Simo
> >> >>
> >> >> http://people.apache.org/~simonetripodi/
> >> >> http://www.99soft.org/
> >> >>
> >> >>
> >> >>
> >> >> On Fri, Apr 29, 2011 at 7:34 AM, Henri Yandell <fl...@gmail.com> wrote:
> >> >>> Below is a thread from the Commons Dev list in which I'm recommending
> >> >>> that OGNL use the commons dev mailing list and that the svn
> >> >>> permissions allow the ognl committers and the commons committers to
> >> >>> have read write access.
> >> >>>
> >> >>> http://commons.markmail.org/thread/ku3ouuilpiicb5is
> >> >>>
> >> >>> Is this a concern for anyone?
> >> >>>
> >> >>> OGNL's target is to graduate into Commons rather than to TLP, so
> >> >>> making it act like a TLP seems destined to cause problems.
> >> >>>
> >> >>> Hen
> >> >>>
> >> >>> ---------------------------------------------------------------------
> >> >>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >> >>> For additional commands, e-mail: general-help@incubator.apache.org
> >> >>>
> >> >>>
> >> >>
> >> >> ---------------------------------------------------------------------
> >> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >> >> For additional commands, e-mail: general-help@incubator.apache.org
> >> >>
> >> >>
> >> >
> >> >
> >> >
> >> > --
> >> > http://www.grobmeier.de
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >> > For additional commands, e-mail: general-help@incubator.apache.org
> >> >
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >> For additional commands, e-mail: general-help@incubator.apache.org
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: OGNL Infrastructure questions
Posted by Simone Tripodi <si...@apache.org>.
Hi Upayavira!!!
I agree that commons folks can have rw rights, so people are already
used to co-work in the 'commons way'.
Moreover, I agreed on joining
- dev@commons.a.o
- users@commons.a.o
- issues@commons.a.o
- create the private ML where commons PMCs can join.
Does it make sense?
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Sun, May 1, 2011 at 7:22 PM, Upayavira <uv...@odoko.co.uk> wrote:
> use commons-user: +1
> put SVN in 'incubator' space: +1
> grant "commons rw: +1 (assuming current OGNL committers agree)
>
> As to a private list, I think the benefit would be the opportunity for
> the OGNL committers to learn how such management happens. Where, for
> example, would committer votes happen? The issue with graduation to
> Commons is what happens after graduation - do they suddenly loose some
> power over their own affairs, e.g. ease of seeing vote threads. So not
> sure the best on this one.
>
> Upayavira
>
> On Fri, 29 Apr 2011 08:29 -0700, "Henri Yandell" <fl...@gmail.com>
> wrote:
>> Agreed, no need to use the svn location from Commons; though I ask to
>> allow @commons rw access.
>>
>> The committer of the podling would not automatically become PMC
>> members, so I don't think there is a need to setup a private list (or
>> even to consider it a PPMC).
>>
>> Hen
>>
>> On Thu, Apr 28, 2011 at 11:05 PM, Christian Grobmeier
>> <gr...@gmail.com> wrote:
>> >> we could share MLs and also SVN (Sandbox
>> >> would be nice, not?)
>> >
>> > MLs are fine, b/c one would need to change address later, and
>> > searching for pre-graduation threads is more easily.
>> >
>> > For SVN I don't see a benefit. The repos can be moved with less effort
>> > once component is graduated. I would like to avoid to get something
>> > into the sandbox which is not cleared from legal perspective. What, if
>> > OGNL fails in the incubator and we just forget to remove the code from
>> > the sandbox? If its in the incubator part, it is like a tag
>> > saying:"beware"
>> >
>> > I would be +1 on user/dev ML but leave SVN in incubator
>> > Is there a need to create a pmc ML for OGNL to discuss incubation
>> > related matters?
>> >
>> > Cheers
>> >
>> >> What Incubator PMCs think about it?
>> >> Simo
>> >>
>> >> http://people.apache.org/~simonetripodi/
>> >> http://www.99soft.org/
>> >>
>> >>
>> >>
>> >> On Fri, Apr 29, 2011 at 7:34 AM, Henri Yandell <fl...@gmail.com> wrote:
>> >>> Below is a thread from the Commons Dev list in which I'm recommending
>> >>> that OGNL use the commons dev mailing list and that the svn
>> >>> permissions allow the ognl committers and the commons committers to
>> >>> have read write access.
>> >>>
>> >>> http://commons.markmail.org/thread/ku3ouuilpiicb5is
>> >>>
>> >>> Is this a concern for anyone?
>> >>>
>> >>> OGNL's target is to graduate into Commons rather than to TLP, so
>> >>> making it act like a TLP seems destined to cause problems.
>> >>>
>> >>> Hen
>> >>>
>> >>> ---------------------------------------------------------------------
>> >>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> >>> For additional commands, e-mail: general-help@incubator.apache.org
>> >>>
>> >>>
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> >> For additional commands, e-mail: general-help@incubator.apache.org
>> >>
>> >>
>> >
>> >
>> >
>> > --
>> > http://www.grobmeier.de
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> > For additional commands, e-mail: general-help@incubator.apache.org
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: OGNL Infrastructure questions
Posted by Henri Yandell <fl...@gmail.com>.
Committer votes happen on the PMC list. There won't be an OGNL PMC -
so I don't see this as losing a power over their own affairs. It's not
a power they begin with.
When OGNL is deemed ready by the Incubator, (ie: Incubator PMC has
voted to graduate it), the Commons PMC would vote to accept the code
(probably in public) and would vote in private to accept the OGNL
committers. For example, if there is a committer who joins OGNL but
then does nothing, I wouldn't expect Commons to grant karma.
In the meantime the addition of committers would presumably be a
proposal by the sponsors on the Incubator PMC list.
[I know there's a lot of assumption of TLP in the Incubator approach,
so I can see how the above seems out of whack with those assumptions]
Hen
On Sun, May 1, 2011 at 10:22 AM, Upayavira <uv...@odoko.co.uk> wrote:
> use commons-user: +1
> put SVN in 'incubator' space: +1
> grant "commons rw: +1 (assuming current OGNL committers agree)
>
> As to a private list, I think the benefit would be the opportunity for
> the OGNL committers to learn how such management happens. Where, for
> example, would committer votes happen? The issue with graduation to
> Commons is what happens after graduation - do they suddenly loose some
> power over their own affairs, e.g. ease of seeing vote threads. So not
> sure the best on this one.
>
> Upayavira
>
> On Fri, 29 Apr 2011 08:29 -0700, "Henri Yandell" <fl...@gmail.com>
> wrote:
>> Agreed, no need to use the svn location from Commons; though I ask to
>> allow @commons rw access.
>>
>> The committer of the podling would not automatically become PMC
>> members, so I don't think there is a need to setup a private list (or
>> even to consider it a PPMC).
>>
>> Hen
>>
>> On Thu, Apr 28, 2011 at 11:05 PM, Christian Grobmeier
>> <gr...@gmail.com> wrote:
>> >> we could share MLs and also SVN (Sandbox
>> >> would be nice, not?)
>> >
>> > MLs are fine, b/c one would need to change address later, and
>> > searching for pre-graduation threads is more easily.
>> >
>> > For SVN I don't see a benefit. The repos can be moved with less effort
>> > once component is graduated. I would like to avoid to get something
>> > into the sandbox which is not cleared from legal perspective. What, if
>> > OGNL fails in the incubator and we just forget to remove the code from
>> > the sandbox? If its in the incubator part, it is like a tag
>> > saying:"beware"
>> >
>> > I would be +1 on user/dev ML but leave SVN in incubator
>> > Is there a need to create a pmc ML for OGNL to discuss incubation
>> > related matters?
>> >
>> > Cheers
>> >
>> >> What Incubator PMCs think about it?
>> >> Simo
>> >>
>> >> http://people.apache.org/~simonetripodi/
>> >> http://www.99soft.org/
>> >>
>> >>
>> >>
>> >> On Fri, Apr 29, 2011 at 7:34 AM, Henri Yandell <fl...@gmail.com> wrote:
>> >>> Below is a thread from the Commons Dev list in which I'm recommending
>> >>> that OGNL use the commons dev mailing list and that the svn
>> >>> permissions allow the ognl committers and the commons committers to
>> >>> have read write access.
>> >>>
>> >>> http://commons.markmail.org/thread/ku3ouuilpiicb5is
>> >>>
>> >>> Is this a concern for anyone?
>> >>>
>> >>> OGNL's target is to graduate into Commons rather than to TLP, so
>> >>> making it act like a TLP seems destined to cause problems.
>> >>>
>> >>> Hen
>> >>>
>> >>> ---------------------------------------------------------------------
>> >>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> >>> For additional commands, e-mail: general-help@incubator.apache.org
>> >>>
>> >>>
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> >> For additional commands, e-mail: general-help@incubator.apache.org
>> >>
>> >>
>> >
>> >
>> >
>> > --
>> > http://www.grobmeier.de
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> > For additional commands, e-mail: general-help@incubator.apache.org
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: OGNL Infrastructure questions
Posted by Upayavira <uv...@odoko.co.uk>.
use commons-user: +1
put SVN in 'incubator' space: +1
grant "commons rw: +1 (assuming current OGNL committers agree)
As to a private list, I think the benefit would be the opportunity for
the OGNL committers to learn how such management happens. Where, for
example, would committer votes happen? The issue with graduation to
Commons is what happens after graduation - do they suddenly loose some
power over their own affairs, e.g. ease of seeing vote threads. So not
sure the best on this one.
Upayavira
On Fri, 29 Apr 2011 08:29 -0700, "Henri Yandell" <fl...@gmail.com>
wrote:
> Agreed, no need to use the svn location from Commons; though I ask to
> allow @commons rw access.
>
> The committer of the podling would not automatically become PMC
> members, so I don't think there is a need to setup a private list (or
> even to consider it a PPMC).
>
> Hen
>
> On Thu, Apr 28, 2011 at 11:05 PM, Christian Grobmeier
> <gr...@gmail.com> wrote:
> >> we could share MLs and also SVN (Sandbox
> >> would be nice, not?)
> >
> > MLs are fine, b/c one would need to change address later, and
> > searching for pre-graduation threads is more easily.
> >
> > For SVN I don't see a benefit. The repos can be moved with less effort
> > once component is graduated. I would like to avoid to get something
> > into the sandbox which is not cleared from legal perspective. What, if
> > OGNL fails in the incubator and we just forget to remove the code from
> > the sandbox? If its in the incubator part, it is like a tag
> > saying:"beware"
> >
> > I would be +1 on user/dev ML but leave SVN in incubator
> > Is there a need to create a pmc ML for OGNL to discuss incubation
> > related matters?
> >
> > Cheers
> >
> >> What Incubator PMCs think about it?
> >> Simo
> >>
> >> http://people.apache.org/~simonetripodi/
> >> http://www.99soft.org/
> >>
> >>
> >>
> >> On Fri, Apr 29, 2011 at 7:34 AM, Henri Yandell <fl...@gmail.com> wrote:
> >>> Below is a thread from the Commons Dev list in which I'm recommending
> >>> that OGNL use the commons dev mailing list and that the svn
> >>> permissions allow the ognl committers and the commons committers to
> >>> have read write access.
> >>>
> >>> http://commons.markmail.org/thread/ku3ouuilpiicb5is
> >>>
> >>> Is this a concern for anyone?
> >>>
> >>> OGNL's target is to graduate into Commons rather than to TLP, so
> >>> making it act like a TLP seems destined to cause problems.
> >>>
> >>> Hen
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >>> For additional commands, e-mail: general-help@incubator.apache.org
> >>>
> >>>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >> For additional commands, e-mail: general-help@incubator.apache.org
> >>
> >>
> >
> >
> >
> > --
> > http://www.grobmeier.de
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: OGNL Infrastructure questions
Posted by Henri Yandell <fl...@gmail.com>.
Agreed, no need to use the svn location from Commons; though I ask to
allow @commons rw access.
The committer of the podling would not automatically become PMC
members, so I don't think there is a need to setup a private list (or
even to consider it a PPMC).
Hen
On Thu, Apr 28, 2011 at 11:05 PM, Christian Grobmeier
<gr...@gmail.com> wrote:
>> we could share MLs and also SVN (Sandbox
>> would be nice, not?)
>
> MLs are fine, b/c one would need to change address later, and
> searching for pre-graduation threads is more easily.
>
> For SVN I don't see a benefit. The repos can be moved with less effort
> once component is graduated. I would like to avoid to get something
> into the sandbox which is not cleared from legal perspective. What, if
> OGNL fails in the incubator and we just forget to remove the code from
> the sandbox? If its in the incubator part, it is like a tag
> saying:"beware"
>
> I would be +1 on user/dev ML but leave SVN in incubator
> Is there a need to create a pmc ML for OGNL to discuss incubation
> related matters?
>
> Cheers
>
>> What Incubator PMCs think about it?
>> Simo
>>
>> http://people.apache.org/~simonetripodi/
>> http://www.99soft.org/
>>
>>
>>
>> On Fri, Apr 29, 2011 at 7:34 AM, Henri Yandell <fl...@gmail.com> wrote:
>>> Below is a thread from the Commons Dev list in which I'm recommending
>>> that OGNL use the commons dev mailing list and that the svn
>>> permissions allow the ognl committers and the commons committers to
>>> have read write access.
>>>
>>> http://commons.markmail.org/thread/ku3ouuilpiicb5is
>>>
>>> Is this a concern for anyone?
>>>
>>> OGNL's target is to graduate into Commons rather than to TLP, so
>>> making it act like a TLP seems destined to cause problems.
>>>
>>> Hen
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>
>
>
> --
> http://www.grobmeier.de
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: OGNL Infrastructure questions
Posted by Antonio Petrelli <an...@gmail.com>.
2011/4/29 Christian Grobmeier <gr...@gmail.com>
> For SVN I don't see a benefit. The repos can be moved with less effort
> once component is graduated. I would like to avoid to get something
> into the sandbox which is not cleared from legal perspective. What, if
> OGNL fails in the incubator and we just forget to remove the code from
> the sandbox? If its in the incubator part, it is like a tag
> saying:"beware"
>
+1
Moving from a project to another under Apache SVN infrastructure is simple,
since all the projects are under the same repository. I already saw this
move when Tiles became TLP after separating from Struts.
Antonio
Re: OGNL Infrastructure questions
Posted by Christian Grobmeier <gr...@gmail.com>.
> we could share MLs and also SVN (Sandbox
> would be nice, not?)
MLs are fine, b/c one would need to change address later, and
searching for pre-graduation threads is more easily.
For SVN I don't see a benefit. The repos can be moved with less effort
once component is graduated. I would like to avoid to get something
into the sandbox which is not cleared from legal perspective. What, if
OGNL fails in the incubator and we just forget to remove the code from
the sandbox? If its in the incubator part, it is like a tag
saying:"beware"
I would be +1 on user/dev ML but leave SVN in incubator
Is there a need to create a pmc ML for OGNL to discuss incubation
related matters?
Cheers
> What Incubator PMCs think about it?
> Simo
>
> http://people.apache.org/~simonetripodi/
> http://www.99soft.org/
>
>
>
> On Fri, Apr 29, 2011 at 7:34 AM, Henri Yandell <fl...@gmail.com> wrote:
>> Below is a thread from the Commons Dev list in which I'm recommending
>> that OGNL use the commons dev mailing list and that the svn
>> permissions allow the ognl committers and the commons committers to
>> have read write access.
>>
>> http://commons.markmail.org/thread/ku3ouuilpiicb5is
>>
>> Is this a concern for anyone?
>>
>> OGNL's target is to graduate into Commons rather than to TLP, so
>> making it act like a TLP seems destined to cause problems.
>>
>> Hen
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
--
http://www.grobmeier.de
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: OGNL Infrastructure questions
Posted by Simone Tripodi <si...@apache.org>.
Hi Henri!
thanks for following up the conversation! I agree that joining the
existing Commons infra would simplify the process to graduate OGNL as
a proper Commons component, we could share MLs and also SVN (Sandbox
would be nice, not?)
What Incubator PMCs think about it?
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Fri, Apr 29, 2011 at 7:34 AM, Henri Yandell <fl...@gmail.com> wrote:
> Below is a thread from the Commons Dev list in which I'm recommending
> that OGNL use the commons dev mailing list and that the svn
> permissions allow the ognl committers and the commons committers to
> have read write access.
>
> http://commons.markmail.org/thread/ku3ouuilpiicb5is
>
> Is this a concern for anyone?
>
> OGNL's target is to graduate into Commons rather than to TLP, so
> making it act like a TLP seems destined to cause problems.
>
> Hen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org