Your SlideShare is downloading. ×

The Apache Way and


Published on

A presentation on The Apache Way and what it means to Apache …

A presentation on The Apache Way and what it means to Apache

Presented at the ODF Plugfest in Berlin, July 2011

There is a video of this presentation session at

Published in: Technology
1 Comment
No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. The Apache Way What does “Apache (Incubating)” mean?
  • 2. Who is Ross Gardler? Ross Gardler Vice President of Community Development The Apache Software Foundation [email_address] @rgardler
  • 3. What is The Apache Software Foundation?
    • Infrastructure
    • Projects
      • 94 top level projects
      • 6. 57 incubating projects
      • 7. 32 labs projects
      • 8. 16 attic projects
  • 9. Apache projects Incubating Projects...
  • 95. Apache's tagline We are more than a group of projects sharing a server, we are a community of developers and users .
  • 96. Apache's Mission The Apache Software Foundation provides support for the Apache community of open source software projects . The Apache projects are characterized by a collaborative, consensus based development process, an open and pragmatic software license , and a desire to create high quality software that leads the way in its field.
  • 97. Apache's Mission (redux)
    • Let developers do what they do best – develop
      • Apache Software Foundation handles the rest
    • The Apache Way
      • Open Development vs. Open Source
      • 98. Everyone is equal, everyone is a volunteer
      • 99. All technical decisions about a project are public
      • 100. She who has the best idea leads
        • Until a better idea emerges
    • Apache does not pay for development
  • 101. Who are we?
    • 2663 committers
      • People who have earned write access to one or more projects
    • 370 active members
      • People who have earned the right to vote for the board
    • >4000 iCLAs
      • People who have clearance to licence IP to the Foundation
  • 102. Committer geographic diversity
  • 103. Merit Earns Influence
  • 115. How Decisions are Made
    • Most decisions are reversible
    • 116. “ If it didn't happen on the list, it didn't happen”
    • 117. Uncontroversial or small changes
      • Lazy Consensus – assume it's OK – JFDI
    • Controversial, irreversible or large changes
      • Propose then wait a minimum of 72 hours
        • Anyone can veto it (the -1 notation)
      • Silence means you have lazy Consensus
        • +1 also indicates support
  • 118. How Conflict is Resolved
    • Everyone has a veto (-1)
      • Only committers veto is binding
    • Veto must be supported
      • Reasoned argument with course of action
      • 119. Willingness to implement alternative
    • Veto's force discussion and, if supported, version control rollback
    • 120. Code can be vetoed, releases cannot
  • 121. Undue Influence?
    • What if there are only committers from FooBar Corporation?
    • 122. It should not happen
      • Incubator graduation requires diversity
    • If it does happen, through attrition
      • Board can (and occasionally does) intervene
      • 123. Quarterly board reports, community oversight
  • 124. Apache OpenOffice.Org (incubating)
  • 125. The only history slide...
  • 126. I'm one of Eight OOo Mentors
    • We provide no technical guidance
      • Social guidance only
      • 127. We help the community adopt the Apache Way
    • We help to ensure
      • Everyone is equal
      • 128. Everyone has a voice
    • We do not dictate, we guide
      • There are just a few fixed rules, we enforce those
  • 129. Future of Apache
    • It's not up to the ASF, it's up to you
      • At least if you care enough to engage constructively
    • I asked the ooo-dev what their priorities are
      • Many views presented
      • 130. Some consistency
      • 131. Some points to discuss
      • 132. Here's a few...
  • 133. Independence Enable corporate, non-profit, and volunteer stakeholders to contribute in a collaborative fashion.
  • 134. Reuse Build a constructive working and technical relationship so that the source code developed at Apache can be readily used downstream by everyone.
  • 135. Collaboration Collaboration is not just on code, some suggestions for other forms of collaboration... jointly sponsored events, interoperability 'plugfests', standards development, shared build infrastructure, shared release mirrors, coordination of build schedules and version numbers, defect lists, and downstream requirements
  • 136. Open We will make our relationship with other projects a priority early in the life of the Apache Incubator project
  • 137. Interoperability Build close relationships with appropriate Apache Projects to enhance the features of OO.o and improve interoperability.
  • 138. One result...
    • Yesterday I learned (via the ooo-dev mailing list) of the donation of Lotus Symphony
    • 139. End of the IBM Symphony Fork
    • 140. Symphony packages OO.o as Eclipse plugins
      • More reuse potential, even beyond Eclipse?
    • Not a diversion from next release of OO.o
  • 141. You and OO.o
    • How do we collaborate upstream/downstream?
    • 142. As one responder on the ooo-dev list said “We will find a way”
  • 143. Over to you...
    • Get involved
      • [email_address]