...
[11:35:08 CST(-0600)] <holdorph> well i might have a testcase for that, if we're interested in exploring it. https://issues.jasig.org/browse/INC-38
[11:35:23 CST(-0600)] <holdorph> see the last comment on that ticket.
[11:35:24 CST(-0600)] <EricDalquist> cool
[11:35:33 CST(-0600)] <EricDalquist> so where would be the best place to document this stuff?
[11:35:54 CST(-0600)] <EricDalquist> we have https://wiki.jasig.org/display/JCH/Git+Hosting
[11:35:59 CST(-0600)] <EricDalquist> which doesn't really have much at all on it
[11:36:22 CST(-0600)] * holdorph looks
[11:37:24 CST(-0600)] <holdorph> there used to be some instructions on this page related to how it was done for subversion: https://wiki.jasig.org/display/JCH/Subversion+Access
[11:37:26 CST(-0600)] <EricDalquist> it would be good to document the desired permission (dev teams have read/write access, steering teams have read/write/admin access) as well as workflow for requesting new projects from the Jasig "owners" team and moving existing projects
[11:38:57 CST(-0600)] <holdorph> grr, some days I hate wireless
[11:39:10 CST(-0600)] <EricDalquist> I could just try and capture it here https://wiki.jasig.org/display/JCH/Git+Hosting then
[12:56:38 CST(-0600)] <EricDalquist> holdorph how does this look: https://wiki.jasig.org/display/JCH/Git+Hosting
[12:57:04 CST(-0600)] <EricDalquist> the only other thing that needs to be done for that to work is add the incubation group members as owners
[14:04:33 CST(-0600)] <holdorph> EricDalquist: just got back from lunch. On that git hosting page, specifically on the 'for existing projects" part... From the conversation earlier, it seemed like the approach i thought you mentioned and seemed to make sense, was to have the existing project make the incubation member an admin, and then have the incubation member move the project. It might not matter, but I'm nervous about the current recommendation, in term
[14:31:02 CST(-0600)] <EricDalquist> holdorph my earlier idea doesn't actually work
[14:31:13 CST(-0600)] <EricDalquist> the current approach doesn't really have any negative side effects
[14:31:38 CST(-0600)] <EricDalquist> that "Repository Migration Team" isn't associated with any repositories
[14:32:06 CST(-0600)] <EricDalquist> but because it as and "admin" permission it allows the member to migrate any repositories they own.
[14:52:08 CST(-0600)] <holdorph> ok, sounds good.