community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shane Curcuru <...@shanecurcuru.org>
Subject Re: contributions and their lifecycle
Date Mon, 23 Jan 2017 00:08:21 GMT
A. Soroka wrote on 1/22/17 5:27 PM:
> Just a quick question for anyone who wants to answer or has any
> advice:
> 
> Other than the obvious Apache-wide conditions (proper measures for
> intellectual property, etc.), does anyone have examples of policies
> for accepting and maintaining (code) contributions to a project? I am
> thinking here about the kinds of conditions that must obtain for a
> piece of code to remain viable.

There aren't any Apache-wide policies or guidelines about that (i.e.
lifecycle of a module within a project); technical governance is left up
to each PMC to decide their own working style.

At the whole project level, the board reviews quarterly reports to see
that a PMC has at least three PMC members who are present in the project
- if not actively developing, at least regularly reviewing the mailing
lists.  Three PMC members are required to vote on a release needed for a
security fix, for example.

  https://www.apache.org/foundation/board/reporting

When a project seems inactive or dips to three of fewer PMC members
present, the board will typically ask the PMC to either figure out a
plan to add more active PMC members to provide oversight, or to ask the
community to consider moving to the Attic.

Mature projects with little code/release activity are fine, if that's
where their technology cycle is, as long as at least three PMC members
are present enough to provide oversight.

- Shane

> For example, in a (non-Apache) project with which I am involved, any
> contribution must have at least two committers ready to take
> responsibility for it. If at any time after contribution of a module,
> that stops being the case, that module starts moving on a road to
> being deprecated out of the mainline codebase into ancillary curation
> (a process that can stop and reverse at any time if more committers
> are willing to join in).
> 
> So I'm looking for examples of similar conditions to meet for
> contributions to be accepted, simple rules to measure commitment and
> community, and on the other end of the lifecycle, examples of
> conditions that decide when a piece of a project has lost vitality
> and should be excised from the responsibilities that all committers
> share.
> 
> Thanks for any examples, pointers, experiences, thoughts to ponder!
> 
> ---
> A. Soroka
> Apache Jena


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org


Mime
View raw message