Re: Introducing myself to the community
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 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 > > > > http://www.apache.org/dev/git.html > > > > Regards. > > > > El lun., 18 feb. 2019 a las 19:50, Fon Lawrence ( > >) > > escribió: > > > > > 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 like > > to > > > participate in the Gsoc 2019 session. > > > > > > I will be pleased if I could get a brief introduction on how to get > > > started. > > > > > > Regards > > > > > -- WBR Maxim aka solomax - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Introducing myself to the community
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 it works. > > http://www.apache.org/foundation/how-it-works.html > > http://www.apache.org/dev/contributors.html > > http://www.apache.org/dev/git.html > > Regards. > > El lun., 18 feb. 2019 a las 19:50, Fon Lawrence ( >) > escribió: > > > 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 like > to > > participate in the Gsoc 2019 session. > > > > I will be pleased if I could get a brief introduction on how to get > > started. > > > > Regards > > >
rebooted community-vm / added RAM
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 unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Introducing myself to the community
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 http://www.apache.org/dev/git.html Regards. El lun., 18 feb. 2019 a las 19:50, Fon Lawrence () escribió: > 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 like to > participate in the Gsoc 2019 session. > > I will be pleased if I could get a brief introduction on how to get > started. > > Regards >
Re: Use GitLab, not GitHub
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 PM group to mirror to gitlab and then adapt your processes >> >> In the end .. imho it doesnt matter where you mirror to ... the bigger >> question is what you do with your workflow in terms >> of accepting pull requests and such. And there is definitely a danger of >> becoming dependent on a commercial entity (MS/Github) .. but then you already >> e,g. use JIRA for your issue tracking now.. > > AFAIK, the ASF JIRA runs on ASF hardware, as does Bugzilla. Yes .. but JIRA is a proprietary software provided by Atlassian so similar issues apply. - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Use GitLab, not GitHub
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 the first message in each PR which is; these are known > limitations. We get all comments on issues and PRs to our notifications@ mailing list. Maybe you should check with Infra as to how this works for us, but not for you. The only real difference is that they are not well- threaded vs. what you get if you subscribe yourself, but this is a minor inconvenience. Rich also responded: > 2) This is a decision made by Infra, at the extensive, YEARS-LONG > pressuring of our projects. This is something our projects wanted, and > demanded, and even, in cases, threatened to leave over. I don't think we ever threatened to leave over it, but we did make a years-long campaign for it (and were the first project on git vs. svn!) The simple fact is that developers are on GH. We get more code contributions and involvement in our community because we moved our code and issue management to GH. As a more end-user-focused project than many at ASF, our project needs that kind of interaction to live and breathe well. We were too isolated in JIRA, and we've easily added 33% of our current contributor code base through drive-by PRs on our GH repo. GL doesn't offer this tangible feature, even if I agree with you that it would be better in principle to support GL over GH. The secondary advantage of GH Issues being more user-friendly than JIRA was a nice- to-have, but the real goal for us was discoverability and interaction with all the other open source projects in the Erlang, C/C++ and JavaScript communities. That's where they all are, so that's where we are glad to be. > Re. "infra": infra is here to create and manage the infra to support > the projects' wants and needs; I am speaking here to the community > to try to influence their wants and needs. No thanks. -Joan - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Use GitLab, not GitHub
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 your processes > > In the end .. imho it doesnt matter where you mirror to ... the bigger > question is what you do with your workflow in terms > of accepting pull requests and such. And there is definitely a danger of > becoming dependent on a commercial entity (MS/Github) .. but then you already > e,g. use JIRA for your issue tracking now.. AFAIK, the ASF JIRA runs on ASF hardware, as does Bugzilla. > Manfred > > Julian Foad wrote on 2019-02-18 06:30: > > > 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, apart from the first message in each PR > > which > > is; these are known limitations. > > > > Re. "infra": infra is here to create and manage the infra to support the > > projects' wants and needs; I am speaking here to the community to try to > > influence their wants and needs. > > > > - Julian > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > For additional commands, e-mail: dev-h...@community.apache.org > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Use GitLab, not GitHub
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 mirror to ... the bigger question is what you do with your workflow in terms of accepting pull requests and such. And there is definitely a danger of becoming dependent on a commercial entity (MS/Github) .. but then you already e,g. use JIRA for your issue tracking now.. Manfred Julian Foad wrote on 2019-02-18 06:30: > 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, apart from the first message in each PR > which > is; these are known limitations. > > Re. "infra": infra is here to create and manage the infra to support the > projects' wants and needs; I am speaking here to the community to try to > influence their wants and needs. > > - Julian > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Introducing myself to the community
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 like to participate in the Gsoc 2019 session. I will be pleased if I could get a brief introduction on how to get started. Regards
Re: Use GitLab, not GitHub
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 should be primarily Microsoft tools > because they were familiar to the most developers worldwide? > I agree with you, both are easy to use and it is basically the same workflow (from a contributor point of view), but it is a reality that a great deal of developers already use Github. For good or for bad people assume that open source code lives on Github, although in reality it could be hosted elsewhere. Again, I'm not advocating for using Github, I'm just saying that it is understandable why it is considered more approachable (popular) than Gitlab. Best Regards, Jorge > -- > - Julian > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
Re: Use GitLab, not GitHub
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. Ok, I misunderstood. Not sure I see a difference, then, if we don't host it ourselves. -- Rich Bowen - rbo...@rcbowen.com http://rcbowen.com/ @rbowen - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Use GitLab, not GitHub
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 - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Use GitLab, not GitHub
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 the most developers worldwide? -- - Julian - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Use GitLab, not GitHub
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 presumption from this thread is that we would host it ourselves, rather than use a commercial service. Thus we would own the data, and also "own" the code, even if Gitlab, the company, decided to do something different in the future. > > > > On Mon, Feb 18, 2019 at 9:23 AM Jorge Betancourt > wrote: > >> 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, and >> right now I would say that a lot of them find use through Github because at >> this point is a very logical assumption (from the user's point of view). >> >> I've seen that some projects (I've seen this on Nutch) mirror the >> interactions on Github into Jira, at least as long as the PR is linked to >> the appropriate issue in Jira, that way we still keep the conversation >> around the proposed changes in our control. The integration could be >> improved but I think this protects us partially. Perhaps this could be used >> by more/all projects? At least it could be included in the contributions >> guidelines of our repositories. >> >> Best Regards, >> Jorge >> >> On Mon, Feb 18, 2019 at 3:39 PM Rich Bowen wrote: >> >>> >>> >>> 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't >>> even copied to the Subversion PMC mailing lists, apart from the first >>> message in each PR which is; these are known limitations. >>> >>> Indeed. This is a very good point. >>> Re. "infra": infra is here to create and manage the infra to support >> the >>> projects' wants and needs; I am speaking here to the community to try to >>> influence their wants and needs. >>> >>> Yeah, I would also like to see us move away from GitHub. But the >>> argument that it's where people look first, is compelling. Perhaps we >>> can be influential in changing that? I don't know. >>> >>> >>> >>> -- >>> Rich Bowen - rbo...@rcbowen.com >>> http://rcbowen.com/ >>> @rbowen >>> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >>> For additional commands, e-mail: dev-h...@community.apache.org >>> >>> >> > -- Rich Bowen - rbo...@rcbowen.com http://rcbowen.com/ @rbowen - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Help with task: Ensure all Apache TLPs have Wikipedia pages
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 > 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, 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? >> >> Meanwhile, NONE of the people who have volunteered to help with this >> have so much as responded to my followup emails to them. Has anyone else >> had any followup from any of the volunteers? >> >> --Rich >> >> On 2/16/19 2:50 AM, S M wrote: >> > I would like to help out with the task listed at /task.html?0b349bee >> > >> > >> > >> > >> > تم الإرسال من جهاز Samsung >> > >> > >> > - >> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >> > For additional commands, e-mail: dev-h...@community.apache.org >> > >> >> -- >> Rich Bowen - rbo...@rcbowen.com >> http://rcbowen.com/ >> @rbowen >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >> For additional commands, e-mail: dev-h...@community.apache.org >> >>
Re: Use GitLab, not GitHub
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 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, and > right now I would say that a lot of them find use through Github because at > this point is a very logical assumption (from the user's point of view). > > I've seen that some projects (I've seen this on Nutch) mirror the > interactions on Github into Jira, at least as long as the PR is linked to > the appropriate issue in Jira, that way we still keep the conversation > around the proposed changes in our control. The integration could be > improved but I think this protects us partially. Perhaps this could be used > by more/all projects? At least it could be included in the contributions > guidelines of our repositories. > > Best Regards, > Jorge > > On Mon, Feb 18, 2019 at 3:39 PM Rich Bowen wrote: > > > > > > > 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't > > even copied to the Subversion PMC mailing lists, apart from the first > > message in each PR which is; these are known limitations. > > > > Indeed. This is a very good point. > > > > > > > > Re. "infra": infra is here to create and manage the infra to support > the > > projects' wants and needs; I am speaking here to the community to try to > > influence their wants and needs. > > > > Yeah, I would also like to see us move away from GitHub. But the > > argument that it's where people look first, is compelling. Perhaps we > > can be influential in changing that? I don't know. > > > > > > > > -- > > Rich Bowen - rbo...@rcbowen.com > > http://rcbowen.com/ > > @rbowen > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > For additional commands, e-mail: dev-h...@community.apache.org > > > > >
Re: Help with task: Ensure all Apache TLPs have Wikipedia pages
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, 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? > > Meanwhile, NONE of the people who have volunteered to help with this > have so much as responded to my followup emails to them. Has anyone else > had any followup from any of the volunteers? > > --Rich > > On 2/16/19 2:50 AM, S M wrote: > > I would like to help out with the task listed at /task.html?0b349bee > > > > > > > > > > تم الإرسال من جهاز Samsung > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > For additional commands, e-mail: dev-h...@community.apache.org > > > > -- > Rich Bowen - rbo...@rcbowen.com > http://rcbowen.com/ > @rbowen > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
Re: Use GitLab, not GitHub
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, and right now I would say that a lot of them find use through Github because at this point is a very logical assumption (from the user's point of view). I've seen that some projects (I've seen this on Nutch) mirror the interactions on Github into Jira, at least as long as the PR is linked to the appropriate issue in Jira, that way we still keep the conversation around the proposed changes in our control. The integration could be improved but I think this protects us partially. Perhaps this could be used by more/all projects? At least it could be included in the contributions guidelines of our repositories. Best Regards, Jorge On Mon, Feb 18, 2019 at 3:39 PM Rich Bowen wrote: > > > 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't > even copied to the Subversion PMC mailing lists, apart from the first > message in each PR which is; these are known limitations. > > Indeed. This is a very good point. > > > > > Re. "infra": infra is here to create and manage the infra to support the > projects' wants and needs; I am speaking here to the community to try to > influence their wants and needs. > > Yeah, I would also like to see us move away from GitHub. But the > argument that it's where people look first, is compelling. Perhaps we > can be influential in changing that? I don't know. > > > > -- > Rich Bowen - rbo...@rcbowen.com > http://rcbowen.com/ > @rbowen > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
Re: Use GitLab, not GitHub
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't even copied > to the Subversion PMC mailing lists, apart from the first message in each PR > which is; these are known limitations. Indeed. This is a very good point. > > Re. "infra": infra is here to create and manage the infra to support the > projects' wants and needs; I am speaking here to the community to try to > influence their wants and needs. Yeah, I would also like to see us move away from GitHub. But the argument that it's where people look first, is compelling. Perhaps we can be influential in changing that? I don't know. -- Rich Bowen - rbo...@rcbowen.com http://rcbowen.com/ @rbowen - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Use GitLab, not GitHub
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, apart from the first message in each PR which is; these are known limitations. Re. "infra": infra is here to create and manage the infra to support the projects' wants and needs; I am speaking here to the community to try to influence their wants and needs. - Julian - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Use GitLab, not GitHub
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 > GitHub. To me it's equivalent to encouraging our members and contributors to > use Facebook instead of email for communication. In contrast to when we first > started down this path a few years ago, GitLab now provides a similar service > except it's also Free as in Freedom. By using GitLab, in addition to > supporting FOSS, we would also be able to adapt it to fit our needs and > desires. Use our own hostnames (gitlab.TLP.apache.org). Integrate with our > own user accounts. Own our own data. Our own project mirroring > configurations. With no obligation for infra to host and run it initially if > we prefer gitlab.com or another provider to do so. And no lock-in to the > vendor's policies and charges. > > I strongly believe we should be transitioning to GitLab. > > I assume I'm not the only one who 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-github/ While I don't necessarily disagree with you, I'd like to point out two things. 1) We *DO* own our own data. Github is only ever a mirror. 2) This is a decision made by Infra, at the extensive, YEARS-LONG pressuring of our projects. This is something our projects wanted, and demanded, and even, in cases, threatened to leave over. So you might want to take it up with Infra, and with those projects, before investing a lot of time into this. The ASF tries to offer services to projects, based on what they ask for. Along the way, we use various third-party services, from hosting, to monitoring solutions, to Git hosting providers, because we lack the people-power to do everything ourselves. This is often as much (more?) a financial decision as a philosophical one. -- Rich Bowen - rbo...@rcbowen.com http://rcbowen.com/ @rbowen - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Use GitLab, not GitHub
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 contributors to use Facebook instead of email for communication. In contrast to when we first started down this path a few years ago, GitLab now provides a similar service except it's also Free as in Freedom. By using GitLab, in addition to supporting FOSS, we would also be able to adapt it to fit our needs and desires. Use our own hostnames (gitlab.TLP.apache.org). Integrate with our own user accounts. Own our own data. Our own project mirroring configurations. With no obligation for infra to host and run it initially if we prefer gitlab.com or another provider to do so. And no lock-in to the vendor's policies and charges. I strongly believe we should be transitioning to GitLab. I assume I'm not the only one who 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-github/ - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Help with task: Ensure all Apache TLPs have Wikipedia pages
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? Meanwhile, NONE of the people who have volunteered to help with this have so much as responded to my followup emails to them. Has anyone else had any followup from any of the volunteers? --Rich On 2/16/19 2:50 AM, S M wrote: > I would like to help out with the task listed at /task.html?0b349bee > > > > > تم الإرسال من جهاز Samsung > > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > -- Rich Bowen - rbo...@rcbowen.com http://rcbowen.com/ @rbowen - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
