openoffice-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "donaldupre ." <>
Subject Re: AOO Governance (was RE: Next release and gbuild)
Date Thu, 17 Mar 2016 17:41:09 GMT
Not only it is possible to compel, it is imperative for a viable project.
As Stalin once said, "When there's a person, there's a problem." :)
Lack of management hierarchy just can't work in the long run.
The history of OpenOffice also shows its peak was when an organization with
a clear command structure developed it.
Lazy consensus is in fact the manner to operate because fluid is lazy...
Accomplishments depend not only on the capacity, capability, and
willingness of contributors, but mainly on the way they are being guided
and steered.

On Thu, Mar 17, 2016 at 6:02 PM, Dennis E. Hamilton <
> wrote:

> Technically, we do not have a management hierarchy on Apache projects,
> although there are some rather limited governance roles.  There can be
> self-organizing *informal* teams that are basically people working together
> for some common within-project purpose and those are fluid and definitely
> self-generated.  There is no holacracy.  It is important for onlookers to
> understand there is no executive and there is no *command* structure.  It
> is not possible to compel anything.
> There is a form of status with regard to privileges, in that committers
> are trusted to review and approve the submissions of other contributors and
> can do more without oversight (while review is always possible).  There is
> also a limited form of governance invested in members of the Project
> Management Committee (PMC) which have binding votes on release candidates
> and on procedural and personnel matters such as inviting contributors to
> become committers and to become members of the PMC.  This is all striving
> toward sustainability of the project.
> Effort happens here *only* if someone steps in and operates in a
> consensus-seeking manner.  What is accomplished depends on the capacity,
> capability, and willingness of such contributors.  The sustainability of
> the project depends in part on how contributed effort leads to the
> cultivation and preparation of additional contributors so that capacity is
> continually renewed.
> Finally, there is a form of oversight, in that the project is accountable
> to the foundation for operating in accordance with the foundation bylaws
> and other principles and practices employed across Apache projects.  The
> Chair of the PMC is ratified by the Board of the Foundation and is an
> Officer of the Foundation (i.e., Apache Software Foundation Vice President
> for Apache OpenOffice).  The Chair is accountable to the Board while in all
> other respects being just another member of the PMC.
> For Apache OpenOffice, there is more about this form of operation at <
> For an indication of the status of the project over time, the AOO
> quarterly reports to the Board included in approved Board minutes are
> extracted and collected for historical convenience at <
> The latest accepted quarterly report is maintained at <
> The next report (for the January-March quarter) will be submitted to the
> April 20, 2016, meeting of the ASF Board.  It will be added to the history
> after subsequent approval of the minutes of that meeting. (The complete ASF
> Board Minutes that are the authoritative source of the extracts can be
> found via <>.)
>  - Dennis
> > -----Original Message-----
> > From: donaldupre . []
> > Sent: Thursday, March 17, 2016 00:11
> > To:
> > Subject: Re: Next release and gbuild
> >
> > On Tue, Mar 15, 2016 at 8:46 PM, Pedro Giffuni <> wrote:
> >
> > > Either someone steps in or we just have a team of people do things.
> > >
> >
> > Holacracy is not a good idea.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message