[11:24:00 CST(-0600)] <holdorph> EricDalquist: you around?
[11:24:04 CST(-0600)] <EricDalquist> yers
[11:24:41 CST(-0600)] <holdorph> how strong a possibility (how likely) is it that some (all?) of the fully sponsored jasig portlets will move from svn to github?
[11:24:56 CST(-0600)] <EricDalquist> depends on the project committer I suppose
[11:25:05 CST(-0600)] <EricDalquist> but I'd be for the portlets I work on moving
[11:25:15 CST(-0600)] <EricDalquist> I believe jen is in of the same opinion
[11:26:00 CST(-0600)] <holdorph> if you were going to submit a new porlet, never been in jasig svn before, to incubation right now, would you just put it into github?
[11:26:21 CST(-0600)] <athena> i would
[11:26:37 CST(-0600)] <athena> and yes, certainly hoping the portlets i work on move sometime soon
[11:27:11 CST(-0600)] <holdorph> ok, right now there is a "Jasig" github user. how do we see new portlets/projects working
[11:27:26 CST(-0600)] <holdorph> would they start under Jasig or start under some other user?
[11:27:40 CST(-0600)] <holdorph> sorry Jasig organization
[11:28:34 CST(-0600)] <holdorph> (i'm asking these questions on behalf of the incubation working group, in case it matters)
[11:28:42 CST(-0600)] <EricDalquist> so there is a strong possibility that some will move, potentially all of them could move if the various portlet project leads are happy with the idea
[11:29:17 CST(-0600)] <EricDalquist> I think they would start under the Jasig organization
[11:29:47 CST(-0600)] <holdorph> is it possible to move a project repo from under a user account to under jasig on github?
[11:29:51 CST(-0600)] <EricDalquist> yes
[11:30:11 CST(-0600)] <EricDalquist> you have to have admin access to the Jasig org and the project in question
[11:30:21 CST(-0600)] <EricDalquist> but that's not difficult to get setup
[11:30:35 CST(-0600)] <holdorph> hmm.... so if you don't have admin to both you can't move it?
[11:30:46 CST(-0600)] <holdorph> er, it can't get moved, is a better way to ask that
[11:31:03 CST(-0600)] <EricDalquist> I don't think so
[11:31:22 CST(-0600)] <EricDalquist> though you can easily clone it from user/Project and then push it to jasig/Project
[11:31:39 CST(-0600)] <EricDalquist> I'm not sure what extra neatness happens with github's data when you do an actual move though
[11:31:54 CST(-0600)] <athena> and i'm sure we could grant temporary admin access, if we really needed to
[11:32:07 CST(-0600)] <EricDalquist> We should probably setup the incubation group as admins of the Jasig org on github anyways
[11:32:15 CST(-0600)] <EricDalquist> since they are the primary entry point for new projects
[11:32:33 CST(-0600)] <EricDalquist> and could be responsible for creating new projects and project teams
[11:32:56 CST(-0600)] <holdorph> that sounds like an interesting way to go. it might be efficient.
[11:33:16 CST(-0600)] <EricDalquist> then if some user has a project they want moved
[11:33:31 CST(-0600)] <EricDalquist> they coordinate with the incu group and grant one of the incu members admin access to the project
[11:33:37 CST(-0600)] <EricDalquist> which I think would let it be moved
[11:33:41 CST(-0600)] <holdorph> nod
[11:34:08 CST(-0600)] <holdorph> and for new projects not yet in github, the incubation member could create the project and then assign the developer/project lead as a committer to that project
[11:34:21 CST(-0600)] <EricDalquist> yes
[11:34:40 CST(-0600)] <EricDalquist> and either assign an existing steering committee team or create a new one for the project
[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.