apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From alanfgates <...@git.apache.org>
Subject [GitHub] incubator-apex-site pull request: APEXCORE-321 bylaws draft
Date Thu, 17 Mar 2016 16:38:55 GMT
Github user alanfgates commented on a diff in the pull request:

    --- Diff: src/md/bylaws.md ---
    @@ -0,0 +1,381 @@
    +#*** draft subject to top level project approval ***
    +#Apache Apex Project Bylaws 
    +This document defines the bylaws under which the Apache Apex project operates. It
    +defines the roles and responsibilities of the project, who may vote, how voting works,
    +how conflicts are resolved, etc.
    +Apex is a project of the <a class="externalLink" href=
    +"http://www.apache.org/foundation/">Apache Software Foundation</a>. The Foundation
    +holds the copyright on Apache code including the code in the Apex codebase. The
    +<a class="externalLink" href="http://www.apache.org/foundation/faq.html">Foundation
    +FAQ</a> explains the operation and background of the foundation.
    +Apex is typical of Apache projects in that it operates under a set of principles,
    +known collectively as the "Apache Way". If you are new to Apache
    +development, please refer to the <a class="externalLink" href=
    +"http://incubator.apache.org/">Incubator project</a> for more information on
how Apache
    +projects operate.
    +##Roles and Responsibilities
    +Apache projects define a <a class="externalLink" href=
    +"http://www.apache.org/foundation/how-it-works.html#roles">set of roles</a>
    +associated rights and responsibilities. These roles govern what tasks an individual
    +may perform within the project. The roles are defined in the following sections:
    +The most important participants in the project are people who use our software.
    +The majority of our developers start out as users and guide their development
    +efforts from the user&rsquo;s perspective.
    +Users contribute to the Apache projects by providing feedback to developers in
    +the form of bug reports and feature suggestions. As well, users participate in the
    +Apache community by helping other users on mailing lists and user support
    +All of the volunteers who are contributing time, code, documentation, or
    +resources to the Apex Project. A contributor that makes sustained, welcome
    +contributions to the project may be invited to become a Committer, though the exact
    +timing of such invitations depends on many factors.
    +The project&rsquo;s Committers are responsible for the project&rsquo;s technical
    +management. All committers have write access to the project&rsquo;s source
    +repositories. Committers may cast binding votes on any technical discussion
    +regarding the project.
    +Committer access is by invitation only and must be approved by lazy consensus of
    +the active PMC members. A Committer may request removal of their commit privileges
    +by their own declaration. A committer will be considered
    +&ldquo;emeritus/inactive&rdquo; by not contributing in any form to the project
    +over 1 year. An emeritus committer may request reinstatement of commit access from
    +the PMC. Such reinstatement is subject to lazy consensus of active PMC members
    +Commit access can be revoked by a unanimous vote of all the active PMC members
    +(except the committer in question if they are also a PMC member).
    +All Apache committers are required to have a signed Contributor License
    +Agreement (<a class="externalLink" href=
    +"http://www.apache.org/licenses/icla.txt">CLA</a>) on file with the Apache Software
    +Foundation. There is a <a class="externalLink" href=
    +"http://www.apache.org/dev/committers.html">Committer FAQ</a> which provides
    +details on the requirements for Committers
    +A committer who makes a sustained contribution to the project may be invited to
    +become a member of the PMC. The form of contribution is not limited to code. It can
    +also include code review, helping out users on the mailing lists, documentation,
    +###Project Management Committee
    +The Project Management Committee (PMC) for Apache Apex was created by a
    +resolution of the board of the Apache Software Foundation on ***TBD***. The
    +PMC is responsible to the board and the ASF for the management and oversight of the
    +Apache Apex codebase. The responsibilities of the PMC include:
    +* Deciding what is distributed as products of the project. In particular all releases
must be approved by the PMC
    +* Maintaining the project&rsquo;s shared resources, including the codebase repository,
mailing lists, websites.
    +* Speaking on behalf of the project
    +* Resolving license disputes regarding products of the project
    +* Nominating new PMC members and committers
    +* Maintaining these bylaws and other guidelines of the project
    +Membership of the PMC is by invitation only and must be approved by a lazy
    +consensus of active PMC members. A PMC member is considered
    --- End diff --
    Note, the board must also approve new PMC members.  They must also approve the removal
of any PMC members (line 95 below).

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.

View raw message