Re: Introducing myself to the community

2019-02-18 Thread Maxim Solodovnik
Hello Fon, please also check GSOC ideas page: https://s.apache.org/gsoc2019ideas On Tue, 19 Feb 2019 at 05:06, Fon Lawrence wrote: > > Thanks Rafael, > I will look into it immediately. > > Regards > Lawrence > > On Mon, Feb 18, 2019 at 1:35 PM Rafael Cruz > wrote: > > > Hi! > > > > I'm quite

Re: Introducing myself to the community

2019-02-18 Thread Fon Lawrence
Thanks Rafael, I will look into it immediately. Regards Lawrence On Mon, Feb 18, 2019 at 1:35 PM Rafael Cruz wrote: > Hi! > > I'm quite new in the community, same as you. I'm sure that you've read it, > in any case, I put you here several links that helped me to understand a > little bit how

rebooted community-vm / added RAM

2019-02-18 Thread Chris Lambertus
Hi Comdev, I had to reboot community-vm. It had run out of memory and was causing problems with our monitoring and config management. I added an additional 5GB of ram (3->8GB) so it should be good now. -Chris - To

Re: Introducing myself to the community

2019-02-18 Thread Rafael Cruz
Hi! I'm quite new in the community, same as you. I'm sure that you've read it, in any case, I put you here several links that helped me to understand a little bit how it works. http://www.apache.org/foundation/how-it-works.html http://www.apache.org/dev/contributors.html

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 >

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

Introducing myself to the community

2019-02-18 Thread Fon Lawrence
Hi everyone, Am Fon Lawrence Che. A computer science student from the University of Buea, Cameroon. I am comfortable with Java and of recent I started learning the spring framework. I also have basic knowledge in javascript. I will love to start contributing to the community and I will also

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

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.

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

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

Re: Help with task: Ensure all Apache TLPs have Wikipedia pages

2019-02-18 Thread Dmitriy Pavlov
Sorry, I've misread the initial email. I'll double check if there is a missing project in Wikipedia. Sincerely, Dmitriy Pavlov пн, 18 февр. 2019 г. в 20:32, Dmitriy Pavlov : > Hi Rich, > > The task is still in the list of help-wanted service here >

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

Re: Help with task: Ensure all Apache TLPs have Wikipedia pages

2019-02-18 Thread Dmitriy Pavlov
Hi Rich, The task is still in the list of help-wanted service here https://helpwanted.apache.org/task.html?0b349bee48c7e47a20fb29222b8217fa61b11d31 Should I mark it as done? Sincerely, Dmitriy Pavlov пн, 18 февр. 2019 г. в 17:05, Rich Bowen : > Has anyone verified where we are on this task,

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

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

Re: Use GitLab, not GitHub

2019-02-18 Thread Rich Bowen
On 2/18/19 9:13 AM, Julian Foad wrote: > Every time I use GitHub I am supporting proprietary software and silo systems. > > Every time I use GitLab I am supporting open source software and open systems. > > I don't see the ASF's values being upheld by encouraging our projects to use >

Use GitLab, not GitHub

2019-02-18 Thread Julian Foad
Every time I use GitHub I am supporting proprietary software and silo systems. Every time I use GitLab I am supporting open source software and open systems. I don't see the ASF's values being upheld by encouraging our projects to use GitHub. To me it's equivalent to encouraging our members and

Re: Help with task: Ensure all Apache TLPs have Wikipedia pages

2019-02-18 Thread Rich Bowen
Has anyone verified where we are on this task, recently? I think we may already have done this, and, if so, we really should drop this task from the list. Can someone take a moment to verify where we stand on this? Perhaps even one of the people who has said they want to help with the task?