Re: [atomic-devel] Procedure for adding Project Atomic Github Repos

2016-02-15 Thread Joe Brockmeier
On 02/15/2016 01:45 PM, Josh Berkus wrote: > > I mean, 3 days is enough, but not if Day 1 is Good Friday or July 3rd. Well, I mean business days really. I don't really count Sat/Sun, holidays. Best, jzb -- Joe Brockmeier | Community Team, OSAS j...@redhat.com | http://community.redhat.com/ Twi

Re: [atomic-devel] Procedure for adding Project Atomic Github Repos

2016-02-15 Thread Josh Berkus
On 02/15/2016 10:42 AM, Joe Brockmeier wrote: On 02/15/2016 01:36 PM, Daniel J Walsh wrote: 4. Wait about one week for feedback. Otherwise looks good, but I'd say 72 hours is enough wait time for lazy consensus. Maybe "three to six days, depending on timing"? I mean, 3 days is enough, but n

Re: [atomic-devel] Procedure for adding Project Atomic Github Repos

2016-02-15 Thread Joe Brockmeier
On 02/15/2016 01:36 PM, Daniel J Walsh wrote: >> 4. Wait about one week for feedback. >> Otherwise looks good, but I'd say 72 hours is enough wait time for lazy consensus. Best, jzb -- Joe Brockmeier | Community Team, OSAS j...@redhat.com | http://community.redhat.com/ Twitter: @jzb | http://di

Re: [atomic-devel] Procedure for adding Project Atomic Github Repos

2016-02-15 Thread Daniel J Walsh
On 02/15/2016 01:10 PM, Josh Berkus wrote: > Folks, > > Langdon has requested a written procedure for adding new repos, and a > change in responsibilities for that. Procedure follows. Please > comment if you see that I've left anything out. > > Also, is there some good place to post this proced

[atomic-devel] Procedure for adding Project Atomic Github Repos

2016-02-15 Thread Josh Berkus
Folks, Langdon has requested a written procedure for adding new repos, and a change in responsibilities for that. Procedure follows. Please comment if you see that I've left anything out. Also, is there some good place to post this procedure? Requesting a New or Migrated Repository - Norm