Entries tagged [community]

Friday March 17, 2017

Community Development News - February 2017

Welcome to our monthly blog update about what is happening in Apache Community Development. This month we have news about ApacheCon, Apache Big Data and our range of mini themed conferences, we also invite you to promote your talk on Feathercast.

ApacheCon NA 2017 - Miami


During February our main focus was in promoting Apache Big Data and the new format ApacheCon in Miami. Over 225 submissions were received and we'd like to thank everyone that was involved in helping review them all. There are 126 sessions planned for Apachecon and 90 sessions for Big Data. The full schedule for both conferences have now been published and details can be found at the links below:

ApacheCon NA 2017 Schedule
Apache Big Data NA 2017 Schedule


Five mini or themed conferences will also be running alongside ApacheCon and Apache Big Data. More details can be found at the following links:

Apache IoT (Internet of Things)
Cloudstack Collaboration Conference
FlexJS Summit
Apache Traffic Server and Traffic Control Summit
TomcatCon


Conference dates are 16th - 18th May 2017 and registrations for ApacheCon or Big Data can be done via the Linux Foundation website. Please check individual schedules if you are only attending any of the mini conferences as they may begin before the main conferences.

PLEASE NOTE: With the exception of the Flex and Traffic Server events, which begin before the main event, admission to one of these events also secures you entrance to the others.

Promote Your Talk on Feathercast!

Congratulations if you were lucky enough to get a talk accepted for ApacheCon, Big Data or any of the mini summits. Would you like to promote your talk by participating in a short interview for Feathercast? .
Interviews are approximately 5 minutes and will be published on the feathercast.apache.org website. We also usually share these links via social media. If you would like to organize an interview with then please send an email to the feathercast mailing list at feathercast-AT-apache.org with your details ad one of our team members will contact you.

Contacting Community Development

Remember that we are always happy to get your feedback and comments so please feel free to contact us, follow our events and participate in our discussions on our mailing list. If you would like to be kept up to date with all the latest news about what is happening in Community Development then please subscribe to our mailing list by sending an email to dev-subscribe AT community DOT apache DOT org.

Monday December 20, 2010

Who should use Apache Extras?

Who should host their projects on Apache Extras



Apache Extras is aimed primarily those who are unable or unwilling to licence their code under the Apache License V2, but want to signal their relationship to one or more Apache project community.



One example of this is my own Drupal connector for Apache Wookie (Incubating). This needs to be GPL licensed due to the Drupal dependency, but it contains Apache Licensed code as well. Consequently it cannot be hosted at Drupal, nor can it be hosted at the ASF. Now, with Apache Extras, it has a home that is associated with at least one of those organisations.


A second group of projects that may choose to host on Apache Extras are those who wish to manage their projects in a way that is not aligned with our own collaborative consensus based processes.

Wednesday December 15, 2010

Why Apache Extras?


[Read More]

Tuesday September 21, 2010

How Apache Projects Use Consensus

What are those 'veto' votes about, anyway? What does Apache mean by 'consensus', and how does it foster 'community over code'?

[Read More]

Thursday June 03, 2010

What makes Apache projects different?

Sharing a code repository with some other programmers might seem enough to create an open source project; the Apache Software Foundation goes further and focuses on making projects sustainable in the long term, and ensuring that our code is legally clean.

This means that our projects have to follow a (small) number of rules, and a number of best practices have been established over the years.

Here's a quick description of how Apache projects are born and live on - some of the items below are derived from the ASF's bylaws (http://www.apache.org/foundation/bylaws.html), while others are best practices that evolved over time.

Projects enter the ASF via the Incubator, anyone can suggest a new project as described on the Incubator website (http://incubator.apache.org).

A Project Management Committee (PMC) oversees each project on behalf of its users, contributors, committers and the foundation itself.

New committers and PMC members are elected by the PMC based on merit.

Committers and PMC members are not necessarily ASF members, to be members they have to be elected separately (see "roles" in http://www.apache.org/foundation/how-it-works.html).

Each project has at least one private and one public (development,"dev") mailing list which are the only official communication channels for the PMC members and committers.

Discussions and decisions about people (such as the elections mentioned above) usually happen on the project's private list, but that's not a hard rule, each PMC can decide.

All other decisions happen on the dev list, discussions on the private list are kept to a minimum.

"If it didn't happen on the dev list, it didn't happen" - which leads to:

a) Elections of committers and PMC members are published on the dev list once finalized.

b) Out-of-band discussions (IRC etc.) are summarized on the dev list as soon as they have impact on the project, code or community.

Where possible, decisions are made by consensus. The ASF has voting procedures to help reach this consensus (http://www.apache.org/foundation/voting.html).

Releases are created according to the ASF's release rules (http://www.apache.org/dev/release.html), and all released software uses the Apache License (http://www.apache.org/licenses/).

A formal PMC vote is required to publish a release. By voting to accept the release, the PMC makes the release an act of the foundation, as opposed to a personal action of the the release manager. This is a very important distinction should any legal issues arise.

Each PMC reports to the ASF's board of directors, usually quarterly. The PMC's report mentions progress made and any problems encountered. Items of particular relevance to the board include community activities,
software releases, development work and compliance with the ASF's rules and best practices.

Trademarks and logos used by ASF projects belong to the ASF.

Don't hesitate to ask on the community development mailing list (http://community.apache.org/) if you have questions about this - and in the meantime, have fun at the ASF, commit early and communicate often!

Calendar

Search

Hot Blogs (today's hits)

Tag Cloud

Categories

Feeds

Links

Navigation