Hi,
I am sure this might have already been discussed, if so apologies.
Is there any reason we don't mirror our repos to github (similar as happens
with openstack).
I ask as it could encourage more developers to get involved by increasing
exposure (especially for independents).
We already have a
Luke,
"External" repos is something we want to have a discussion on in early/mid
October (borrowing Bin's Thursday Technical Community Discussion mtg.)
In OpenStack, if someone contributes to the github repo, do some of those
github contributions also get "moved" to the main OpenStack repo? If y
Nicholas ;
openstack-...@lists.opnfv.org; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] OPNFV on Github
Luke,
"External" repos is something we want to have a discussion on in early/mid
October (borrowing Bin's Thursday Technical Community Discussion mtg.)
I
That's what I did for ONOSFW. If it sits behind a private gerrit, then they
don't know to use what they can't see.
Sent from my iPad
> On Sep 26, 2016, at 12:54 AM, Luke Hinds wrote:
>
> Hi,
>
> I am sure this might have already been discussed, if so apologies.
>
> Is there any reason we do
I can make a meeting on 10/6, but will be on my way back from Disney :)
So, previously, I had my Github location as my primary spot, which worked great
for trying to build up a community. It was easier than the current private
Gerrit arrangement. But it also has a downside. After discussion with
Lots of good thoughts here.
One other thing is the legal aspect -- I know that developers don't
necessarily like lawyers and don't like legal constraints impinging on
their innovation and their work. On the other hand, as an open source
project that holds the communal IP for important work for our
In the fashion I mentioned, it doesn't bypass the our governance.
One of the issues we always have to contend with is the DCO. It still requires
that the Dev that is ultimately bringing something into our ecosystem is doing
some level of due diligence. But this isn't a new risk.
Sent from my
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
On M
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
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, al
Madsen
Cc: opnfv-tech-discuss@lists.opnfv.org
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.
; Nightly (UTC)?
>
>
>
> Al
>
>
>
> From: opnfv-tech-discuss-boun...@lists.opnfv.org
> [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Ash
> Sent: Tuesday, October 04, 2016 11:47 AM
> To: Leif Madsen
> Cc: opnfv-tech-discuss@lists.opnfv.org
> S
> -Original Message-
> From: Aric Gardner [mailto:agard...@linuxfoundation.org]
...
> The mirroring to github is done with a Gerrit plugin and updates live.
>
> Regards,
> Aric
[ACM]
Thanks Aric, seems more than adequate to me!
Al
>
> On Tue, Oct 4, 2016 at 12:06 PM, MORTON, ALFRED
., AL
Cc: opnfv-tech-discuss@lists.opnfv.org
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) wrote:
> Sounds good to me, +1.
>
>
>
> Additional
nt: Tuesday, October 04, 2016 12:32 PM
> To: MORTON JR., AL
> Cc: opnfv-tech-discuss@lists.opnfv.org
> 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
;SULLIVAN, BRYAN L" , Aric Gardner
, "MORTON JR., AL"
Cc: TECH-DISCUSS OPNFV
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 Gi
hris
>
>
>
> *From: * on behalf of Peter
> Lee
> *Date: *Wednesday 5 October 2016 at 04:58
> *To: *"SULLIVAN, BRYAN L" , Aric Gardner <
> agard...@linuxfoundation.org>, "MORTON JR., AL"
> *Cc: *TECH-DISCUSS OPNFV
>
> *Subject: *Re: [opnf
use it for
>> TSC approval on the 18th.
>>
>>
>>
>> / Chris
>>
>>
>>
>> *From: * on behalf of Peter
>> Lee
>> *Date: *Wednesday 5 October 2016 at 04:58
>> *To: *"SULLIVAN, BRYAN L" , Aric Gardner <
>> agard...@l
uss this on the 13th and potentially use it for
> >> TSC approval on the 18th.
> >>
> >>
> >>
> >> / Chris
> >>
> >>
> >>
> >> *From: * on behalf of Peter
> >> Lee
> >> *Date: *Wednesday 5 October 2016 at 04:58
&g
icensing+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 poten
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
Two great ideas!
> Can we just disable "issue", "pull request" and "wiki"?
Should the disabling of issues and PRs be a permanent solution?
Maybe instead of setting up the bot to close PRs, we just don't allow
them and provide a link in each repo description to a getting started
page?
> And it w
discussion-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.
> > >>
> > >&
23 matches
Mail list logo
