Re: [DISCUSS] Retirement Policies related to GitHub/GitBox

2018-07-24 Thread Stian Soiland-Reyes
On Tue, 10 Jul 2018 23:19:01 -0500, Greg Stein wrote: > On Fri, Jun 29, 2018 at 9:35 PM Greg Stein wrote: > > > On Fri, Jun 29, 2018 at 1:10 PM Dave Fisher wrote: > > >... > > > >> For podlings that have an active GitHub through GitBox the implication of > >> this step is that the IPMC will now

Re: [DISCUSS] Retirement Policies related to GitHub/GitBox

2018-07-10 Thread Greg Stein
On Fri, Jun 29, 2018 at 9:35 PM Greg Stein wrote: > On Fri, Jun 29, 2018 at 1:10 PM Dave Fisher wrote: > >... > >> For podlings that have an active GitHub through GitBox the implication of >> this step is that the IPMC will now have control of the GitHub auth. >> >> (1) What needs to be done to

Re: [DISCUSS] Retirement Policies related to GitHub/GitBox

2018-06-29 Thread Greg Stein
On Fri, Jun 29, 2018 at 1:10 PM Dave Fisher wrote: >... > For podlings that have an active GitHub through GitBox the implication of > this step is that the IPMC will now have control of the GitHub auth. > > (1) What needs to be done to the archive to make it clear that the podling > is retired? S

[DISCUSS] Retirement Policies related to GitHub/GitBox

2018-06-29 Thread Dave Fisher
Hi - Since the subject has come up. I think that the retirement policy as described by the website [1] needs to be updated. Update ${podling} Incubator SVN Add entries to asf-mailer.conf and send mail to cvs at incubator.apache.org Remove entries from asf-authorizaton - this makes the directory