My reaction (being ignorant of the machinery behind phonebook and authorization) is that adding to asf-authorization-template on podling creation would be ok (since it is done only once per podling, by a mentor who presumably knows what they are doing) but adding to asf-authorization-template each time a committer is appointed is probably too error-prone.
I might be naive but it seems that the fact that x is a committer to podling y should be represented in one and only one place and the phonebook ought to drive from that. Julian > On May 14, 2016, at 1:01 PM, Roman Shaposhnik <ro...@shaposhnik.org> wrote: > > To answer back into the original thread (based on the question about > Phonebook last week): > > On Thu, Apr 28, 2016 at 6:51 PM, John D. Ament <johndam...@apache.org> wrote: >> All, >> >> Due to some changes in recent times around the ASF, I think I've identified >> a new setup step for podlings. >> >> I'd like to recommend adding to the asf-authorization-template as a setup >> step to display the newly created podling in phonebook ( >> home.apache.org/phonebook.html) and that whenever a new committer is added >> that this authorization template be updated. >> >> Any objections? Questions or concerns? > > I like the idea. My only concern is that what needs to be updated today > is esoteric (puppet file?) and confusing (svn?). Is there any chance we > can make it less so? > > As I understand the key issue here is that we don't want to create LDAP > entries for podling committers, correct? > > Roman. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
