Re: LDAP changes to support podlings

2017-01-22 Thread Sam Ruby
On Wed, Jan 18, 2017 at 8:51 PM, John D. Ament wrote: > On Wed, Jan 18, 2017 at 8:25 PM Sam Ruby wrote: > >> On Wed, Jan 18, 2017 at 1:37 PM, Felix Meschberger >> wrote: >> > >> > Hi Sam >> > >> > Like this very much. Thanks ! >> > >> > Started doing that for OpenWhisk and realized some strange

Re: LDAP changes to support podlings

2017-01-18 Thread John D. Ament
On Wed, Jan 18, 2017 at 8:25 PM Sam Ruby wrote: > On Wed, Jan 18, 2017 at 1:37 PM, Felix Meschberger > wrote: > > > > Hi Sam > > > > Like this very much. Thanks ! > > > > Started doing that for OpenWhisk and realized some strange UI behaviour: > > To add a PPMC member I have to click + then sear

Re: LDAP changes to support podlings

2017-01-18 Thread Sam Ruby
On Wed, Jan 18, 2017 at 1:37 PM, Felix Meschberger wrote: > > Hi Sam > > Like this very much. Thanks ! > > Started doing that for OpenWhisk and realized some strange UI behaviour: > To add a PPMC member I have to click + then search for the user, click on + > again and then click on „Add to PPMC“

Re: LDAP changes to support podlings

2017-01-18 Thread Greg Stein
I agree with Felix that too many confirmations exist in the workflow right now, but it worked great. And I was able to correct some missing people on the mynewt PPMC. Yay! On Wed, Jan 18, 2017 at 1:37 PM, Felix Meschberger wrote: > Hi Sam > > Like this very much. Thanks ! > > Started doing that

Re: LDAP changes to support podlings

2017-01-18 Thread Felix Meschberger
Hi Sam Like this very much. Thanks ! Started doing that for OpenWhisk and realized some strange UI behaviour: To add a PPMC member I have to click + then search for the user, click on + again and then click on „Add to PPMC“ button What is the reason for the last „Add to PPMC“ button click ? Th

Re: LDAP changes to support podlings

2017-01-18 Thread Sam Ruby
On Mon, Jan 16, 2017 at 1:05 PM, Sam Ruby wrote: > Current status: for ppmcs that have lists in the subversion puppet > definitions, those lists have been loaded into LDAP, and augmented with > mentor information from podlings.xml. A list of all current podlings can be > found here, and those tha

Re: LDAP changes to support podlings

2017-01-17 Thread Sam Ruby
On Tue, Jan 17, 2017 at 1:57 PM, John D. Ament wrote: > On Tue, Jan 17, 2017 at 1:11 PM Sam Ruby wrote: > >> On Mon, Jan 16, 2017 at 1:31 PM, Stian Soiland-Reyes >> wrote: >> > Not sure what was the decision to be made here, but +1 to all >> suggestions. >> > All of PPMC as podling owners makes

Re: LDAP changes to support podlings

2017-01-17 Thread John D. Ament
On Tue, Jan 17, 2017 at 1:11 PM Sam Ruby wrote: > On Mon, Jan 16, 2017 at 1:31 PM, Stian Soiland-Reyes > wrote: > > Not sure what was the decision to be made here, but +1 to all > suggestions. > > All of PPMC as podling owners makes sense to me as long as > private@podling > > is notified. > > T

Re: LDAP changes to support podlings

2017-01-17 Thread Sam Ruby
On Mon, Jan 16, 2017 at 1:31 PM, Stian Soiland-Reyes wrote: > Not sure what was the decision to be made here, but +1 to all suggestions. > All of PPMC as podling owners makes sense to me as long as private@podling > is notified. The following four podlings don't have private@podling lists: ["log4

Re: LDAP changes to support podlings

2017-01-16 Thread Stian Soiland-Reyes
Not sure what was the decision to be made here, but +1 to all suggestions. All of PPMC as podling owners makes sense to me as long as private@podling is notified. Great work! On 16 Jan 2017 6:05 pm, "Sam Ruby" wrote: > TL;DR: We need to decide, for each PPMC, who gets to update the PPMC list