The Apache Way

What does Apache OpenOffice.org (Incubating) mean?

Who is Ross Gardler?

Ross GardlerVice President of Community DevelopmentThe Apache Software Foundation

rgardler@apache.org@rgardler

What is The Apache Software Foundation?

InfrastructureLegal

Social

Technical

Projects94 top level projects

57 incubating projects

32 labs projects

16 attic projects

Apache projects

HTTP Server

Abdera

ActiveMQ

Ant

APR

Archiva

Aries

Avro

Axis

Buildr

Camel

Cassandra

Cayenne

Chemistry

Click

Cocoon

Commons

Continuum

CouchDB

CXF

DB

Directory

ESME

Felix

Forrest

Geronimo

Gump

Hadoop

Harmony

HBase

Hive

HttpComponents

Jackrabbit

Jakarta

James

jUDDI

Karaf

Lenya

Libcloud

Logging

Lucene

Mahout

Maven

Mina

MyFaces

Nutch

ODE

OODT

OFBiz

OpenEJB

OpenJPA

OpenWebBeans

PDFBox

Perl

Pig

Pivot

POI

Portals

Qpid

River

Roller

Santuario

ServiceMix

Shindig

Shiro

Sling

SpamAssassin

STDCXX

Struts

Subversion

Synapse

Tapestry

Tcl

Thrift

Tika

Tiles

Tomcat

TrafficServer

Turbine

Tuscany

UIMA

Web Services

Wicket

Xalan

Xerces

XML

XMLBeans

XML Graphics

Zoo Keeper

Incubating Projects...

Apache's tagline

We are more than a group of projects sharing a server, we are a community of developers and users.

Apache's Mission

The Apache Software Foundation providessupport 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 thatleads the way in its field.

Apache's Mission (redux)

Let developers do what they do best developApache Software Foundation handles the rest

The Apache WayOpen Development vs. Open Source

Everyone is equal, everyone is a volunteer

All technical decisions about a project are public

She who has the best idea leadsUntil a better idea emerges

Apache does not pay for development

Who are we?

2663 committersPeople who have earned write access to one or more projects

370 active membersPeople who have earned the right to vote for the board

>4000 iCLAsPeople who have clearance to licence IP to the Foundation

Committer geographic diversity

Merit Earns Influence

Use

Evangelism

Feature Requests

User Support

Documentation

Testing

Bug Reports

Design

Patches

Collaboration

Infrastructure

Mentoring

How Decisions are Made

Most decisions are reversible

If it didn't happen on the list, it didn't happen

Uncontroversial or small changesLazy Consensus assume it's OK JFDI

Controversial, irreversible or large changesPropose then wait a minimum of 72 hoursAnyone can veto it (the -1 notation)

Silence means you have lazy Consensus+1 also indicates support

How Conflict is Resolved

Everyone has a veto (-1)Only committers veto is binding

Veto must be supported Reasoned argument with course of action

Willingness to implement alternative

Veto's force discussion and, if supported, version control rollback

Code can be vetoed, releases cannot

Undue Influence?

What if there are only committers from FooBar Corporation?

It should not happenIncubator graduation requires diversity

If it does happen, through attritionBoard can (and occasionally does) intervene

Quarterly board reports, community oversight

Apache OpenOffice.Org (incubating)

The only history slide...

I'm one of Eight OOo Mentors

We provide no technical guidanceSocial guidance only

We help the community adopt the Apache Way

We help to ensureEveryone is equal

Everyone has a voice

We do not dictate, we guideThere are just a few fixed rules, we enforce those

Future of Apache OpenOffice.org

It's not up to the ASF, it's up to youAt least if you care enough to engage constructively

I asked the ooo-dev what their priorities areMany views presented

Some consistency

Some points to discuss

Here's a few...

Independence

Enable corporate, non-profit, and volunteer stakeholders to contribute in a collaborative fashion.

Reuse

Build a constructive working and technical relationship so that the source code developed at Apache can be readily used downstream by everyone.

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, anddownstream requirements

Open

We will make our relationship with other projects a priorityearly in the life of the Apache Incubator project

Interoperability

Build close relationships with appropriate Apache Projects to enhance the features of OO.o and improve interoperability.

One result...

Yesterday I learned (via the ooo-dev mailing list) of the donation of Lotus Symphony

End of the IBM Symphony Fork

Symphony packages OO.o as Eclipse pluginsMore reuse potential, even beyond Eclipse?

Not a diversion from next release of OO.o

You and OO.o

How do we collaborate upstream/downstream?

As one responder on the ooo-dev list said

We will find a way

Over to you...

Get involvedooo-dev@incubator.apache.org


@rgardler

UsersUsersContributorsUsersCommittersContributorsUsersCommittersMembersContributors