On 1/8/14, 11:05 AM, sebb wrote:
> On 8 January 2014 18:37, Phil Steitz <phil.ste...@gmail.com> wrote:
>> Why not just drop it?
> Because it does has some use in listing PMC members/committers - which
> then don't need to be repeated per component.

What exactly is the benefit of that?

Phil
>
>> I would rather see collective energy go
>> toward maintaining the individual component team lists.
> Indeed; the above would be a once-off change.
>
>> Phil
>>
>> On 1/8/14, 6:50 AM, sebb wrote:
>>> The team list [1] has several problems.
>>>
>>> - it is linked from the lhs menu as PMC yet the heading is "The
>>> following is a list of developers with commit privileges that have
>>> directly contributed to the project in one way or another."
>>> - it only contains (ex) PMC members currently
>>> - it gets out of date quickly, and partly duplicates the information in LDAP
>>>
>>> I think it needs a rethink.
>>>
>>> The only info that is not available from LDAP is the list of
>>> non-committer contributors, however that mainly makes sense at the
>>> component level.
>>>
>>> I see no point in trying to maintain committer and PMC lists manually.
>>> Maybe there is a way to merge LDAP entries into the pom.
>>> This would have to be redone every time there is a committer or PMC change.
>>>
>>> Alternatively maybe there is a way to link to the LDAP lists on
>>> people.a.o, and just use the pom for contributors.
>>>
>>> One solution for the main site would be to have 3 links:
>>> Contributors => [1] (in which case the pom would need to be adjusted
>>> for every contributor)
>>> Committers => [2]
>>> PMC => [3]
>>>
>>> Thoughts?
>>>
>>> [1] http://commons.staging.apache.org/team-list.html
>>> [2] http://people.apache.org/committers-by-project.html#commons
>>> [3] http://people.apache.org/committers-by-project.html#commons-pmc
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>> For additional commands, e-mail: dev-h...@commons.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>


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

Reply via email to