The Apache Way is a phrase used to describe the style of community-led development that characterises projects at the ASF. This talk covers how the ASF is structured to support that, how we apply The Apache Way, and why that has led to such successful projects.

1. The Apache Way
@brettporter
Brett Porter
Director, Apache Software Foundation
Head of Architecture, SafetyCulture

2. Hats

3. ASF 💜 Data Projects

4. Community Matters

5. About the ASF
• Independent US non-profit
• Volunteer organisation
• Virtual world-wide organisation
• Began as the Apache Group in 1996
• Incorporated as the ASF in 1999

6. Purpose of the ASF
Provide open source software to the public free of charge

7. Purpose of the ASF
• Collaborative infrastructure for open source development
• Legal entity for donation purposes
• Shelter from law suits
• PR & Marketing
• Protection of the Apache brand

8. Structure of the ASF

9. Structure of the ASF
• Apache Members are the “shareholders” of the Foundation
• Members are nominated and elected by the current Members
• Currently 684, with 64 of them added this year

10. Structure of the ASF
• Board consists of 9 (volunteer) directors elected by the membership each year
• Rich Bowen, Shane Curcuru, Bertrand Delacretaz, Ted Dunning, Jim Jagielski, Chris Mattmann, Brett Porter,
Phil Steitz, Mark Thomas
• Board appoints (volunteer) Executive Officers
• Chairman
• President
• Treasurer
• Secretary
• Executive Vice President
• Vice Chairman

11. Structure of the ASF
• Board committees
• Legal Affairs
• Security Team
• Operations are handled by President and appointed Officers
• Infrastructure
• Fundraising
• Marketing and Publicity
• Brand Management
• Travel Assistance
• Executive Assistant

12. Projects

13. The Apache Way
• Govern of Merit
• Peer to Peer
• Consensus decision making
• Open, online communication
• Responsible oversight

14. It’s about what you do.
Those who do, decide.

15. Roles

16. Peer to Peer
• The ASF works with people, not companies.
• All votes hold the same weight.
• Participate based on needs.
• Community over code.
• Committers and members should hold one another with respect.

17. Consensus Decision Making
• Most decisions made on mailing list without voting, sometimes by way of
lazy consensus.
• For releases, 3 +1’s required, no veto
• A -1 veto requires proposal of alternate solution

18. Open Communication
• Communication is done online
• Email lists are preferred form of communication - dev@, commits@,
users@
• Most communication is publicly archived
• Most lists are open to any subscriber

19. Responsible Oversight
• Small commits, peer reviewed
• Security is mandatory
• Ensure license compliance
• Release only high quality software
• No abuse of Apache brand or community

20. Apache License
• “Liberal” open source software license
• Grants copyright and patent licenses
• Requires appropriate attribution
• Protects brand - cannot call your product “Apache XYZ”
• Easily reused by other projects & organisations

21. The Apache Way
• Govern of Merit
• Peer to Peer
• Consensus decision making
• Open, online communication
• Responsible oversight

22. Apache in 2017

23. Apache in 2017
• Projects: 309 Committees: 184 Incubating: 53

24. Apache in 2017
• Committers: 6316

25. Apache in 2017

26. ASF Budget FY18
Infrastructure
59%
Publicity
13%
Brand
6%
Conferences
1%
Travel Assistance
4%
Treasury
4%
Fundraising
3%
General & Admin
8%
Other Expenses
3%
Expenses
Public Donations
9%
Sponsorship
88%
Other Income
3%
Income

27. Sponsors
• 8 Platinum sponsors
• 8 Gold sponsors
• 12 Silver sponsors
• 20 Bronze sponsors
• 11 Infrastructure sponsors
• Public donations

28. The Apache Way
• Meritocracy
• Peer to Peer
• Consensus decision making
• Open, online communication
• Responsible oversight

29. Thank You!
@brettporter @TheASF
brett@apache.org http://apache.org