The Apache Way What does “Apache OpenOffice.org (Incubating)” mean?
Who is Ross Gardler? Ross Gardler Vice President of Community Development The Apache Software Foundation [email_address] @...
What is The Apache Software Foundation? <ul><li>Infrastructure </li><ul><li>Legal
Social
Technical </li></ul><li>Projects </li><ul><li>94 top level projects
57 incubating projects
32 labs projects
16 attic projects </li></ul></ul>
Apache projects <ul><li>HTTP Server
Abdera
ActiveMQ
Ant
APR
Archiva
Aries
Avro
Axis
Buildr
Camel
Cassandra
Cayenne
Chemistry
Click
Cocoon
Commons
Upcoming SlideShare
Loading in...5
×

The Apache Way and OpenOffice.org

5,729

Published on

A presentation on The Apache Way and what it means to Apache OpenOffice.org

Presented at the ODF Plugfest in Berlin, July 2011

There is a video of this presentation session at https://plus.google.com/109175303602657131317/posts/KHGcDTZMJMN

Published in: Technology
1 Comment
2 Likes
Statistics
Notes
No Downloads
Views
Total Views
5,729
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
65
Comments
1
Likes
2
Embeds 0
No embeds

No notes for slide

The Apache Way and OpenOffice.org

  1. 1. The Apache Way What does “Apache OpenOffice.org (Incubating)” mean?
  2. 2. Who is Ross Gardler? Ross Gardler Vice President of Community Development The Apache Software Foundation [email_address] @rgardler
  3. 3. What is The Apache Software Foundation? <ul><li>Infrastructure </li><ul><li>Legal
  4. 4. Social
  5. 5. Technical </li></ul><li>Projects </li><ul><li>94 top level projects
  6. 6. 57 incubating projects
  7. 7. 32 labs projects
  8. 8. 16 attic projects </li></ul></ul>
  9. 9. Apache projects <ul><li>HTTP Server
  10. 10. Abdera
  11. 11. ActiveMQ
  12. 12. Ant
  13. 13. APR
  14. 14. Archiva
  15. 15. Aries
  16. 16. Avro
  17. 17. Axis
  18. 18. Buildr
  19. 19. Camel
  20. 20. Cassandra
  21. 21. Cayenne
  22. 22. Chemistry
  23. 23. Click
  24. 24. Cocoon
  25. 25. Commons
  26. 26. Continuum
  27. 27. CouchDB
  28. 28. CXF
  29. 29. DB
  30. 30. Directory
  31. 31. ESME </li></ul><ul><li>Felix
  32. 32. Forrest
  33. 33. Geronimo
  34. 34. Gump
  35. 35. Hadoop
  36. 36. Harmony
  37. 37. HBase
  38. 38. Hive
  39. 39. HttpComponents
  40. 40. Jackrabbit
  41. 41. Jakarta
  42. 42. James
  43. 43. jUDDI
  44. 44. Karaf
  45. 45. Lenya
  46. 46. Libcloud
  47. 47. Logging
  48. 48. Lucene
  49. 49. Mahout
  50. 50. Maven
  51. 51. Mina
  52. 52. MyFaces
  53. 53. Nutch </li></ul><ul><li>ODE
  54. 54. OODT
  55. 55. OFBiz
  56. 56. OpenEJB
  57. 57. OpenJPA
  58. 58. OpenWebBeans
  59. 59. PDFBox
  60. 60. Perl
  61. 61. Pig
  62. 62. Pivot
  63. 63. POI
  64. 64. Portals
  65. 65. Qpid
  66. 66. River
  67. 67. Roller
  68. 68. Santuario
  69. 69. ServiceMix
  70. 70. Shindig
  71. 71. Shiro
  72. 72. Sling
  73. 73. SpamAssassin
  74. 74. STDCXX
  75. 75. Struts </li></ul><ul><li>Subversion
  76. 76. Synapse
  77. 77. Tapestry
  78. 78. Tcl
  79. 79. Thrift
  80. 80. Tika
  81. 81. Tiles
  82. 82. Tomcat
  83. 83. TrafficServer
  84. 84. Turbine
  85. 85. Tuscany
  86. 86. UIMA
  87. 87. Web Services
  88. 88. Wicket
  89. 89. Xalan
  90. 90. Xerces
  91. 91. XML
  92. 92. XMLBeans
  93. 93. XML Graphics
  94. 94. Zoo Keeper </li></ul>Incubating Projects...
  95. 95. Apache's tagline We are more than a group of projects sharing a server, we are a community of developers and users .
  96. 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. 97. Apache's Mission (redux) <ul><li>Let developers do what they do best – develop </li><ul><li>Apache Software Foundation handles the rest </li></ul><li>The Apache Way </li><ul><li>Open Development vs. Open Source
  98. 98. Everyone is equal, everyone is a volunteer
  99. 99. All technical decisions about a project are public
  100. 100. She who has the best idea leads </li><ul><li>Until a better idea emerges </li></ul></ul><li>Apache does not pay for development </li></ul>
  101. 101. Who are we? <ul><li>2663 committers </li><ul><li>People who have earned write access to one or more projects </li></ul><li>370 active members </li><ul><li>People who have earned the right to vote for the board </li></ul><li>>4000 iCLAs </li><ul><li>People who have clearance to licence IP to the Foundation </li></ul></ul>
  102. 102. Committer geographic diversity
  103. 103. Merit Earns Influence <ul><li>Use
  104. 104. Evangelism
  105. 105. Feature Requests
  106. 106. User Support
  107. 107. Documentation
  108. 108. Testing
  109. 109. Bug Reports
  110. 110. Design
  111. 111. Patches
  112. 112. Collaboration
  113. 113. Infrastructure
  114. 114. Mentoring </li></ul>
  115. 115. How Decisions are Made <ul><li>Most decisions are reversible
  116. 116. “ If it didn't happen on the list, it didn't happen”
  117. 117. Uncontroversial or small changes </li><ul><li>Lazy Consensus – assume it's OK – JFDI </li></ul><li>Controversial, irreversible or large changes </li><ul><li>Propose then wait a minimum of 72 hours </li><ul><li>Anyone can veto it (the -1 notation) </li></ul><li>Silence means you have lazy Consensus </li><ul><li>+1 also indicates support </li></ul></ul></ul>
  118. 118. How Conflict is Resolved <ul><li>Everyone has a veto (-1) </li><ul><li>Only committers veto is binding </li></ul><li>Veto must be supported </li><ul><li>Reasoned argument with course of action
  119. 119. Willingness to implement alternative </li></ul><li>Veto's force discussion and, if supported, version control rollback
  120. 120. Code can be vetoed, releases cannot </li></ul>
  121. 121. Undue Influence? <ul><li>What if there are only committers from FooBar Corporation?
  122. 122. It should not happen </li><ul><li>Incubator graduation requires diversity </li></ul><li>If it does happen, through attrition </li><ul><li>Board can (and occasionally does) intervene
  123. 123. Quarterly board reports, community oversight </li></ul></ul>
  124. 124. Apache OpenOffice.Org (incubating)
  125. 125. The only history slide...
  126. 126. I'm one of Eight OOo Mentors <ul><li>We provide no technical guidance </li><ul><li>Social guidance only
  127. 127. We help the community adopt the Apache Way </li></ul><li>We help to ensure </li><ul><li>Everyone is equal
  128. 128. Everyone has a voice </li></ul><li>We do not dictate, we guide </li><ul><li>There are just a few fixed rules, we enforce those </li></ul></ul>
  129. 129. Future of Apache OpenOffice.org <ul><li>It's not up to the ASF, it's up to you </li><ul><li>At least if you care enough to engage constructively </li></ul><li>I asked the ooo-dev what their priorities are </li><ul><li>Many views presented
  130. 130. Some consistency
  131. 131. Some points to discuss
  132. 132. Here's a few... </li></ul></ul>
  133. 133. Independence Enable corporate, non-profit, and volunteer stakeholders to contribute in a collaborative fashion.
  134. 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. 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. 136. Open We will make our relationship with other projects a priority early in the life of the Apache Incubator project
  137. 137. Interoperability Build close relationships with appropriate Apache Projects to enhance the features of OO.o and improve interoperability.
  138. 138. One result... <ul><li>Yesterday I learned (via the ooo-dev mailing list) of the donation of Lotus Symphony
  139. 139. End of the IBM Symphony Fork
  140. 140. Symphony packages OO.o as Eclipse plugins </li><ul><li>More reuse potential, even beyond Eclipse? </li></ul><li>Not a diversion from next release of OO.o </li></ul>
  141. 141. You and OO.o <ul><li>How do we collaborate upstream/downstream?
  142. 142. As one responder on the ooo-dev list said “We will find a way” </li></ul>
  143. 143. Over to you... <ul><li>Get involved </li><ul><li>[email_address] </li></ul></ul>
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×