Community Participatory Agreement Draft

Disclaimer: This is a draft. I am the messenger. Feedback is appreciated.

This is a Code of Conduct for $Project, governing your relationship to
$Project and vice-versa, detailing expectations about your participation
and how any problems with your interaction will be addressed.   You
are not required to pledge agreement or assent to this Code of Conduct,
but you are advised that it describes project governance practices that
affect you.

$Project exists to develop, promote, and otherwise further open source
software codebase(s).  Towards this end, there is a group of project
leaders appointed or elected according to $Project’s specific internal
arrangements, some of whom, individually or as groups, will administer
the various project forums and mechanisms, including responding to
participants’ conduct they deem to create significant problems for
$Project.

At all times, the project leaders are responsible for making their
decisions with an eye to the long-term well-being of $Project.  This
could include disciplinary measures such as moderation of participants’
statements in $Project’s public forums, issuing warnings, or in some
cases removing participants from forums or other $Project functions,
either temporarily or permanently.  Project leaders are encouraged
to use the minimal amount of force consistent with advancing the
project’s goals and good order, and encouraged to always announce in a
public place any imposition of a sanction on a partipant, and also the
lifting of that saction if that happens.  That public place might
ideally be a publicly archived mailing list for that purpose, with mail
to the participant sent directly to the participant and CC’d to the
mailing list to create a public record.  This advances the goal of
transparency in $Project management concerning participant problems.
Equally, project leaders are encouraged to be impartial, in the sense of
having the same expectations and exposure to sanctions for bad behaviour
on all persons including themselves.

Recourse:  This Code of Conduct does not attempt to bind project leaders
to mandatory obligations because that is not possible.  Leaders of an
open source project are (collectively) sovereign over it to the extent
permitted by law and rights over property.  At the same time, the Code
of Conduct acknowledges in advance that $Project, like all other
projects, may be maladministered and fail to meet your needs as a
participant, and may not even meet anyone’s needs.   Your recourse if
you feel strongly enough that $Project is being run unfairly,
or incompetently, or in any other way unacceptably is to fork $Project’s
codebase.  Although $Project may own some assets including without
limitation trademarks, $Project’s open-source code is explicitly lawful
to fork by anyone who feels he/she wishes to do so for any reason.

–<end outline>–