=============================== #opendaylight-meeting: odlforge =============================== Meeting started by colindixon at 18:10:19 UTC. The full logs are available at http://meetings.opendaylight.org/opendaylight-meeting/2014/odlforge/opendaylight-meeting-odlforge.2014-08-14-18.10.log.html . Meeting summary --------------- * LINK: http://ci.openstack.org/stackforge.html (cdub, 18:10:26) * the core idea is to give people a place to do real work with code without having to go through project proposal project (colindixon, 18:11:45) * it’s also a great way to start and maintain things until they become good incubation projects and have the TSC have good data about how much interest there is (colindixon, 18:12:42) * LINK: https://github.com/odlforge (cdub, 18:12:57) * key point is that it *is not* actual ODL code, it isn’t shipped in releases, or officially blessed (colindixon, 18:13:00) * the above link makes that clear by differentiating between git.opendaylight.org, our mirror at github.com/opendaylight, and github.com/odlforge (colindixon, 18:14:08) * LINK: https://meetings.opendaylight.org/opendaylight-meeting/2014/odlforge/opendaylight-meeting-odlforge.2014-08-14-18.10.log.txt (colindixon, 18:15:10) * so far, the only thing that has been done is to create that empty github page (colindixon, 18:15:32) * edwarnicke asks why we stood it up on github instead of our own infrastructure (colindixon, 18:15:57) * cdub says that the github is there just for the same reason our current github thing is there, i.e., to mirror our own internal gerrit things (colindixon, 18:16:54) * tykeal says that his current thoughts are to have only one gerrit set up with a separate tree named “forge” or “odlforge” (colindixon, 18:17:29) * edwarnicke expresses some worry that that might not be enough separation since forge patches would show up looking similar to regular projects (colindixon, 18:18:34) * tykeal’s thoghts on how to get this working (colindixon, 18:21:33) * current ideas: separate tree in a current gerrit (cdub, 18:21:53) * right now the thought was a separate tree in gerrit for two reasons: (1) people can keep their current profile and (2) less infrastructure to set up (colindixon, 18:22:07) * there would be a wholly separate jenkins for forge with something like jenkins-forge.opendaylight.org or something similar (colindixon, 18:22:59) * for bugzilla, there’s no way to clearly tag things as forge and tykeal really doesn’t want to set up another bugzilla (colindixon, 18:23:32) * likely punt on bz (hard to separate and hard to set up new one) (cdub, 18:23:38) * use dev list w/ forge project [topic] (no new lists!) (cdub, 18:24:05) * last thing is mailing lists, tykeal says he’s adamantly opposed to giving them their own mailing lists (colindixon, 18:24:34) * separate repositories for forge artifacts (colindixon, 18:25:10) * nexus...opendaylight-forge repo and use org.opendaylight.forge namespace (cdub, 18:25:11) * gerrit separation concern (a cset gerrit link doesn't indicate the project until you click on it) (cdub, 18:30:34) * cdub proposes the idea of setting up a single project to test out things like infrastructure, etc. (tbachman, 18:41:55) * edwarnicke expresses concern about separation (tbachman, 18:42:04) * tykeal believes the separation issue boils down to gerrit (tbachman, 18:42:19) * edwarnick asks if we’ll have a separate gerrit for odlforge (tbachman, 18:42:29) * tykeal says that if we go that route, we will not allow imports of history (tbachman, 18:42:48) * b/c there is no way to confirm that the same SSO ID exists in both gerrit systems at the same time (tbachman, 18:43:11) * be sure odl projects can't depend on odlforge projects (cdub, 18:46:17) Meeting ended at 18:50:46 UTC. People present (lines said) --------------------------- * colindixon (27) * cdub (12) * rexpugh (7) * tbachman (6) * odl_meetbot (5) * Madhu_ (2) * tykeal (1) * dfarrell07 (1) * phrobb (0) * edwarnicke (0) Generated by `MeetBot`_ 0.1.4