Re: Use GitLab, not GitHub

2019-02-18 Thread Manfred Moser
sebb wrote on 2019-02-18 11:22: > On Mon, 18 Feb 2019 at 19:19, Manfred Moser wrote: >> >> Ultimately I think the only way you can move the needle on this is by >> >> 1. talking about it like you did >> >> 2. making it happen - e.g. you could just start with your own project, agree >> in your

Re: Use GitLab, not GitHub

2019-02-18 Thread Joan Touzet
Julian asked: > Re. "owning our data": we do own our source code but what about all > the conversational metadata in GH? In the Subversion project we have > a GH mirror of the code but pull requests and code comments etc. in > GH aren't even copied to the Subversion PMC mailing lists, apart > from

Re: Use GitLab, not GitHub

2019-02-18 Thread sebb
On Mon, 18 Feb 2019 at 19:19, Manfred Moser wrote: > > Ultimately I think the only way you can move the needle on this is by > > 1. talking about it like you did > > 2. making it happen - e.g. you could just start with your own project, agree > in your PM group to mirror to gitlab and then adapt

Re: Use GitLab, not GitHub

2019-02-18 Thread Manfred Moser
Ultimately I think the only way you can move the needle on this is by 1. talking about it like you did 2. making it happen - e.g. you could just start with your own project, agree in your PM group to mirror to gitlab and then adapt your processes In the end .. imho it doesnt matter where you m

Re: Use GitLab, not GitHub

2019-02-18 Thread Jorge Betancourt
On Mon, Feb 18, 2019 at 6:51 PM Julian Foad wrote: > Jorge Betancourt wrote: > > [...] Like Rich said > > there is a great value on being reachable to outside contributors, [...] > > That's illusory. GitLab isn't hard to reach. Should we have suggested 20 > years ago that our infrastructure shoul

Re: Use GitLab, not GitHub

2019-02-18 Thread Rich Bowen
On 2/18/19 12:54 PM, Julian Foad wrote: > Rich Bowen wrote: >> Gitlab is MIT licensed, and the presumption from this thread is that we >> would host it ourselves [...] > > Correction: *could* host it ourselves -- if we wanted or needed to. I > explicitly didn't presume that we would. > Ah. O

Re: Use GitLab, not GitHub

2019-02-18 Thread Julian Foad
Rich Bowen wrote: > Gitlab is MIT licensed, and the presumption from this thread is that we > would host it ourselves [...] Correction: *could* host it ourselves -- if we wanted or needed to. I explicitly didn't presume that we would. -- - Julian ---

Re: Use GitLab, not GitHub

2019-02-18 Thread Julian Foad
Jorge Betancourt wrote: > [...] Like Rich said > there is a great value on being reachable to outside contributors, [...] That's illusory. GitLab isn't hard to reach. Should we have suggested 20 years ago that our infrastructure should be primarily Microsoft tools because they were familiar to t

Re: Use GitLab, not GitHub

2019-02-18 Thread Rich Bowen
On 2/18/19 12:38 PM, Austin Bennett wrote: > Not taking a stance on any migration; can't help but wondering: What > prevents GitLab from getting to the point where GitHub is now and in the > future an equivalent push is to be suggested to move away from GitLab? Gitlab is MIT licensed, and the

Re: Use GitLab, not GitHub

2019-02-18 Thread Austin Bennett
Not taking a stance on any migration; can't help but wondering: What prevents GitLab from getting to the point where GitHub is now and in the future an equivalent push is to be suggested to move away from GitLab? On Mon, Feb 18, 2019 at 9:23 AM Jorge Betancourt wrote: > Hi, > > It is true tha

Re: Use GitLab, not GitHub

2019-02-18 Thread Jorge Betancourt
Hi, It is true that Github is, at the end of the day, a commercial entity, and that we're placing valuable metadata, regarding the changes that eventually will end up being maintained by the members of our projects. Like Rich said there is a great value on being reachable to outside contributors,

Re: Use GitLab, not GitHub

2019-02-18 Thread Rich Bowen
On 2/18/19 9:30 AM, Julian Foad wrote: > Thanks for your comments, Rich. > > Re. "owning our data": we do own our source code but what about all the > conversational metadata in GH? In the Subversion project we have a GH mirror > of the code but pull requests and code comments etc. in GH aren

Re: Use GitLab, not GitHub

2019-02-18 Thread Julian Foad
Thanks for your comments, Rich. Re. "owning our data": we do own our source code but what about all the conversational metadata in GH? In the Subversion project we have a GH mirror of the code but pull requests and code comments etc. in GH aren't even copied to the Subversion PMC mailing lists,

Re: Use GitLab, not GitHub

2019-02-18 Thread Rich Bowen
o thinks so. It would be nice to hear from > others a word of support, or better still anyone wanting to get started. > > - Julian > (no connections with the companies/products involved, just a desire for > software Freedom) > https://blog.foad.me.uk/2018/11/28/use-gitlab-not-gi

Use GitLab, not GitHub

2019-02-18 Thread Julian Foad
connections with the companies/products involved, just a desire for software Freedom) https://blog.foad.me.uk/2018/11/28/use-gitlab-not-github/ - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For addi