Looks great! Can we just disable "issue", "pull request" and "wiki"?
And it would be good to provide project link in the description line. On Fri, Nov 4, 2016 at 4:07 AM Trevor Bramwell < [email protected]> wrote: Hi Luke, et al., The OPNFV Gerrit repos should now exist under https://github.com/opnfv, and they get updated within 30s of Gerrit changes being merged. We are still working on getting the bot in place to close PR's and forward people onto a 'Getting started with OPNFV' page. For those interested in seeing their OPNFV contributions show up in their Github profile, they will need to update their list of email addresses on their Github account to include the address used to submit changes to Gerrit. If you see any repos missing, or have any concerns, please let us know at [email protected]. Regards, Trevor Bramwell On Fri, Oct 21, 2016 at 10:38:03AM +0100, Luke Hinds wrote: > Hi All, > > I took my eye off the ball and missed the dates for this week. > > Did anything transpire? > > Luke > > > > > > > On Wed, Oct 5, 2016 at 10:41 AM, Christopher Price < [email protected] > > > wrote: > > > >> Hi Folks, > >> > >> > >> > >> I’d like to propose that we: > >> > >> 1) Clarify how we want this to be done (looks like we have a > >> solid idea of this now) > >> > >> 2) Determine whom will “own” the github account (Aric &/or Trevor > >> I guess) > >> > >> 3) Present and discuss in community (October 13th call I think is > >> the best) > >> > >> 4) Present it to the TSC for approval (October 18th would seem > >> adequate) > >> > >> 5) Make it so… > >> > >> > >> > >> Maybe we can capture this on the wiki in some way. > >> > >> I have made a start: https://wiki.opnfv.org/display > >> /DEV/Licensing+and+External+repo%27s+discussion#Licensinga > >> ndExternalrepo%27sdiscussion-ProposalforOPNFVrepomirroringtoGitHub but > >> it probably needs some niceness added to it. J > >> > >> We can present and discuss this on the 13th and potentially use it for > >> TSC approval on the 18th. > >> > >> > >> > >> / Chris > >> > >> > >> > >> *From: *<[email protected]> on behalf of Peter > >> Lee <[email protected]> > >> *Date: *Wednesday 5 October 2016 at 04:58 > >> *To: *"SULLIVAN, BRYAN L" <[email protected]>, Aric Gardner < > >> [email protected]>, "MORTON JR., AL" <[email protected]> > >> *Cc: *TECH-DISCUSS OPNFV <[email protected]> > >> > >> *Subject: *Re: [opnfv-tech-discuss] OPNFV on Github > >> > >> > >> > >> I started the opnfv org in github a while back to host the promise > >> project and associated assets. I'd be happy to transfer the ownership of > >> the GitHub opnfv org to whoever we designate as the new owner. > >> > >> Thanks, > >> > >> Peter > >> > >> On Tue, Oct 4, 2016 at 1:02 PM SULLIVAN, BRYAN L <[email protected]> wrote: > >> > >> Aric, > >> > >> When you say " mirroring to github is done " you don't mean currently, > >> right? ("will be done") > >> > >> Also - any chance we could get Iben to donate opnfv to us as the org > >> name? He got out ahead of this game a while back: > >> https://github.com/opnfv > >> It would be great if we could hang our repos off that link and org... > >> > >> Thanks, > >> Bryan Sullivan | AT&T > >> > >> -----Original Message----- > >> From: [email protected] [mailto: > >> [email protected]] On Behalf Of Aric Gardner > >> Sent: Tuesday, October 04, 2016 12:32 PM > >> To: MORTON JR., AL <[email protected]> > >> Cc: [email protected] > >> Subject: Re: [opnfv-tech-discuss] OPNFV on Github > >> > >> The mirroring to github is done with a Gerrit plugin and updates live. > >> > >> Regards, > >> Aric > >> > >> On Tue, Oct 4, 2016 at 12:06 PM, MORTON, ALFRED C (AL) < [email protected]> > >> wrote: > >> > Sounds good to me, +1. > >> > > >> > > >> > > >> > Additional question: > >> > > >> > How often will we execute the mirroring operation to GitHub? > >> > > >> > Nightly (UTC)? > >> > > >> > > >> > > >> > Al > >> > > >> > > >> > > >> > From: [email protected] > >> > [mailto:[email protected]] On Behalf Of Ash > >> > Sent: Tuesday, October 04, 2016 11:47 AM > >> > To: Leif Madsen > >> > Cc: [email protected] > >> > Subject: Re: [opnfv-tech-discuss] OPNFV on Github > >> > > >> > > >> > > >> > It sounds like we're all in violent agreement on this. And I'm okay for > >> the > >> > meeting being delayed to the 13th. > >> > > >> > > >> > > >> > So, to summarize: > >> > > >> > > >> > > >> > 1) The github repo should be a read-only mirror of Gerrit. > >> > > >> > 2) Gerrit should be the workflow for and point for all check-ins > >> > > >> > 3) Still, to protect ourselves on github, all admins/owners will utilize > >> > 2-factor authentication for security purposes. > >> > > >> > 4) We will postpone the community discussion until Bin's 10/13 call. > >> > > >> > 5) Since the github repo will be a mirror of what's on Gerrit, it will > >> > continue to reinforce/reflect OPNFV governance, license practices, and > >> any > >> > other legalities that might have an impact upon our community. > >> > > >> > > >> > > >> > Sound good? > >> > > >> > > >> > > >> > Best, > >> > > >> > > >> > > >> > Ash > >> > > >> > > >> > > >> > On Tue, Oct 4, 2016 at 8:15 AM, Leif Madsen <[email protected]> wrote: > >> > > >> > On Mon, Sep 26, 2016 at 08:17:20AM +0800, Zhipeng Huang wrote: > >> >> As far as I understand for OpenStack they just mirror it to github, any > >> >> code review and patch acceptance is still done in OpenStack gerrit. > >> >> > >> >> OPNFV should have the mirror so that a broader ecosystem of software > >> >> developers could be built for NFV even if they could only browse the > >> code > >> >> on github > >> > > >> > Exactly. As soon as you get into trying to merge PRs from GitHub you're > >> > going to cause all sorts of issues. > >> > > >> > Gerrit should be the defacto source for changes, and GitHub simply as a > >> > nice location to clone / view from. There should be no need to make > >> > inbound changes from GitHub a thing. > >> > > >> > -- > >> > Leif Madsen | Partner Engineer - NFV & CI > >> > NFV Partner Engineering > >> > Red Hat > >> > GPG: (D670F846) BEE0 336E 5406 42BA 6194 6831 B38A 291E D670 F846 > >> > > >> > _______________________________________________ > >> > opnfv-tech-discuss mailing list > >> > [email protected] > >> > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss > >> > > >> > > >> > > >> > > >> > _______________________________________________ > >> > opnfv-tech-discuss mailing list > >> > [email protected] > >> > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss > >> > > >> _______________________________________________ > >> opnfv-tech-discuss mailing list > >> [email protected] > >> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss > >> _______________________________________________ > >> opnfv-tech-discuss mailing list > >> [email protected] > >> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss > >> > >> -- > >> > >> Peter Lee > >> Corenova Technologies > >> +1 310 400 6450 <+1%20310-400-6450> > >> [email protected] > >> > >> _______________________________________________ opnfv-tech-discuss > >> mailing list [email protected] > >> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss > >> > >> _______________________________________________ > >> opnfv-tech-discuss mailing list > >> [email protected] > >> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss > >> > >> > > > > > > -- > > Luke Hinds | NFV Partner Engineering | Office of Technology | Red Hat > > e: [email protected] | irc: lhinds @freenode | m: +44 77 45 63 98 84 | t: +44 > > 12 52 36 2483 > > > > > > -- > Luke Hinds | NFV Partner Engineering | Office of Technology | Red Hat > e: [email protected] | irc: lhinds @freenode | m: +44 77 45 63 98 84 | t: +44 > 12 52 36 2483 > _______________________________________________ > opnfv-tech-discuss mailing list > [email protected] > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss _______________________________________________ opnfv-tech-discuss mailing list [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
_______________________________________________ opnfv-tech-discuss mailing list [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
