Re: ApacheCon CFP closing soon (11 February)
On Jan 18, 2017 18:00, "Matthew Sacks" wrote: Proposal: dissociate from Linux foundation as the ASF has nothing to do with Linux and never did. Matthew, We are 3 years into a 5 year contract with LF to produce ApacheCon. This was a decision made by a lot of people, after months of discussion, and not something we jumped into. If you would like to be part of future ApacheCon decision making, I encourage you to join the Community Development mailing list and join the ongoing conversation about future events. Thanks. On Wed, Jan 18, 2017 at 8:45 AM Rich Bowen wrote: > Hello, fellow Apache enthusiast. Thanks for your participation, and > > interest in, the projects of the Apache Software Foundation. > > > > I wanted to remind you that the Call For Papers (CFP) for ApacheCon > > North America, and Apache: Big Data North America, closes in less than a > > month. If you've been putting it off because there was lots of time > > left, it's time to dig for that inspiration and get those talk proposals > in. > > > > It's also time to discuss with your developer and user community whether > > there's a track of talks that you might want to propose, so that you > > have more complete coverage of your project than a talk or two. > > > > We're looking for talks directly, and indirectly, related to projects at > > the Apache Software Foundation. These can be anything from in-depth > > technical discussions of the projects you work with, to talks about > > community, documentation, legal issues, marketing, and so on. We're also > > very interested in talks about projects and services built on top of > > Apache projects, and case studies of how you use Apache projects to > > solve real-world problems. > > > > We are particularly interested in presentations from Apache projects > > either in the Incubator, or recently graduated. ApacheCon is where > > people come to find out what technology they'll be using this time next > > year. > > > > Important URLs are: > > > > To submit a talk for Apache: Big Data - > > > http://events.linuxfoundation.org/events/apache-big-data- north-america/program/cfp > > To submit a talk for ApacheCon - > > > http://events.linuxfoundation.org/events/apachecon-north- america/program/cfp > > > > To register for Apache: Big Data - > > > http://events.linuxfoundation.org/events/apache-big-data- north-america/attend/register- > > To register for ApacheCon - > > > http://events.linuxfoundation.org/events/apachecon-north- america/attend/register- > > > > Early Bird registration rates end March 12th, but if you're a committer > > on an Apache project, you get the low committer rate, which is less than > > half of the early bird rate! > > > > For further updated about ApacheCon, follow us on Twitter, @ApacheCon, > > or drop by our IRC channel, #apachecon on the Freenode IRC network. Or > > contact me - rbo...@apache.org - with any questions or concerns. > > > > Thanks! > > > > Rich Bowen, VP Conferences, Apache Software Foundation > > > > -- > > (You've received this email because you're on a dev@ or users@ mailing > > list of an Apache Software Foundation project. For subscription and > > unsubscription information, consult the headers of this email message, > > as this varies from one list to another.) > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > For additional commands, e-mail: dev-h...@community.apache.org > > > >
Joining the Apache Foundation
What are the advantages of joining the Apache Foundation? Yes, I've read the pages on your website, but I don't understand how a project would benefit from joining the Foundation apart from using the organization infrastructure. Since a project is required to grow a community (from the incubator) before becoming an "official" Apache project, I could as well just do the work and rent a VM to host everything, or use other websites that host code/trackers/mailing-lists for free. There is actually a drawback from joining the community: all code becomes licensed to the Apache Foundation under the Apache License. I see why an abandoned project would benefit from this, as it could get a new life instead of dying because nobody cares about it anymore... but what about other, active projects? Who is the Apache Foundation for? At moment, I want my privacy to be protected. https://mytemp.email/ - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Joining the Apache Foundation
The ASF is for the community, i.e. community over code. It’s benefits are numerous and include: - high-quality infra, e.g. issue tracking, automated testing, code scanning, mailing lists, IRC, binary and source distribution, etc. - project mentorship, ASF is packed with folks that understand how open source projects work. Your knowledge will lifted to their level. - diversity, i.e. not just one company / individual responsible for the project. This mitigates the ‘bus factor’ and brings new blood / ideas in. - exposure There are conferences, notifications, websites, etc. - community focus / values. This is just a small sampling of benefits. I am sure if you looked, you would find blogs, podcasts and more containing testimonials from others. Good luck, Shawn > On Jan 19, 2017, at 7:33 AM, g...@rudymail.ml wrote: > > What are the advantages of joining the Apache Foundation? > Yes, I've read the pages on your website, but I don't understand how a > project would benefit from joining the Foundation apart from using the > organization infrastructure. Since a project is required to grow a community > (from the incubator) before becoming an "official" Apache project, I could as > well just do the work and rent a VM to host everything, or use other websites > that host code/trackers/mailing-lists for free. There is actually a drawback > from joining the community: all code becomes licensed to the Apache > Foundation under the Apache License. > I see why an abandoned project would benefit from this, as it could get a new > life instead of dying because nobody cares about it anymore... but what about > other, active projects? Who is the Apache Foundation for? > > > At moment, I want my privacy to be protected. > https://mytemp.email/ > > - > 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: Joining the Apache Foundation
Hi, On Thu, Jan 19, 2017 at 2:33 PM, wrote: > ...There is actually a drawback from joining the community: all code > becomes licensed to the Apache Foundation under the Apache License... This is actually a huge benefit for some types of projects and users, especially when it's about projects which are strategic to one's business. Our projects and their names belong to the Foundation, which is neutral and doesn't belong to any company, government or other organization. The risk with projects which belong to individuals or companies is that those can change their minds, disappear or sometimes become crazy or evil. And you're then in dire straits with such a project - there are many "interesting" examples of such failures. The neutrality of the ASF is a guarantee that our projects will be available forever (*) under the same permissive terms. We also have a clear mechanism at http://attic.apache.org/ for retiring projects while allowing anyone to fork them as needed. -Bertrand (*) the current thinking is "at least for the next 50 years" which should be sufficient ;-) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
The Apache Brand [was: Re: Joining the Apache Foundation]
> On Jan 19, 2017, at 9:50 AM, Bertrand Delacretaz > wrote: > > Hi, > > On Thu, Jan 19, 2017 at 2:33 PM, wrote: >> ...There is actually a drawback from joining the community: all code >> becomes licensed to the Apache Foundation under the Apache License... > > This is actually a huge benefit for some types of projects and users, > especially when it's about projects which are strategic to one's > business. > > Our projects and their names belong to the Foundation, which is > neutral and doesn't belong to any company, government or other > organization. > > The risk with projects which belong to individuals or companies is > that those can change their minds, disappear or sometimes become crazy > or evil. And you're then in dire straits with such a project - there > are many "interesting" examples of such failures. > > The neutrality of the ASF is a guarantee that our projects will be > available forever (*) under the same permissive terms. We also have a > clear mechanism at http://attic.apache.org/ for retiring projects > while allowing anyone to fork them as needed. > When you think of an Apache project, you associate a few attributes with that project - this is what marketing folks would call “the brand promise”. - The project is serious. It’s not just one guy in Mom and Dad’s basement. - The project has a license that I can use in business. I don’t need to worry about being forced to publish my source code if I don’t want to. I know that the license can’t be revoked arbitrarily, and it isn’t contingent on renewing a support contract. - The project isn’t driven by a single company who might abandon it or go bankrupt. It’s driven by a community that independent and diverse, so I know that some other company’s failure won’t leave me hanging or searching for a new system. That means I can integrate the product into my business with minimal risk. - The “open-source” version of the project is complete and useful - it isn’t just a teaser for the commercial version (of course there might be product support that I can pay for if I need it). - Training and support can be provided by more than one company, so I have choices in where I buy those follow-on products. - The development is open and public - I can see and participate in the decision-making around features and architecture. - Development is driven by a diverse project community, not just one company’s marketing plan. So again, we have diversity and the project has a life beyond a single company or person. - The project is probably decent quality and It has a formal release process. - The software is “owned” by a trusted and neutral charitable entity, the Apache Software Foundation. - The Apache Software Foundation will support my right to continue using and developing the software under the Apache license. This brand promise makes it much much more likely that serious users will adopt the project’s software, and that the project has a continued life, independent of any one developer or company. In return for the right to put “Apache” in front of your project name, your project community essentially agrees to support the Apache brand promise, by contributing your code under the Apache license, adopting apache’s procedures and philosophy, and by protecting the trademarks that your project establishes. Cheers, Greg Trasuk > -Bertrand > > (*) the current thinking is "at least for the next 50 years" which > should be sufficient ;-) > > - > 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
