Return-Path: 
 <dev-return-7246-apmail-apex-dev-archive=apex.apache.org@apex.incubator.apache.org>
X-Original-To: apmail-apex-dev-archive@minotaur.apache.org
Delivered-To: apmail-apex-dev-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 46E8B19D4E
	for <apmail-apex-dev-archive@minotaur.apache.org>;
 Wed, 16 Mar 2016 06:52:23 +0000 (UTC)
Received: (qmail 38565 invoked by uid 500); 16 Mar 2016 06:52:23 -0000
Delivered-To: apmail-apex-dev-archive@apex.apache.org
Received: (qmail 38484 invoked by uid 500); 16 Mar 2016 06:52:23 -0000
Mailing-List: contact dev-help@apex.incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@apex.incubator.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@apex.incubator.apache.org>
List-Post: <mailto:dev@apex.incubator.apache.org>
List-Id: <dev.apex.incubator.apache.org>
Reply-To: dev@apex.incubator.apache.org
Delivered-To: mailing list dev@apex.incubator.apache.org
Received: (qmail 38472 invoked by uid 99); 16 Mar 2016 06:52:22 -0000
Received: from pnap-us-west-generic-nat.apache.org (HELO
 spamd4-us-west.apache.org) (209.188.14.142)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Mar 2016 06:52:22 +0000
Received: from localhost (localhost [127.0.0.1])
	by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org)
 with ESMTP id 7B61EC0316
	for <dev@apex.apache.org>; Wed, 16 Mar 2016 06:52:22 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: -4.021
X-Spam-Level: 
X-Spam-Status: No, score=-4.021 tagged_above=-999 required=6.31
	tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5,
	RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01,
	RP_MATCHES_RCVD=-0.001] autolearn=disabled
Received: from mx2-lw-us.apache.org ([10.40.0.8])
	by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new,
 port 10024)
	with ESMTP id v6s1aEwX6ISp for <dev@apex.apache.org>;
	Wed, 16 Mar 2016 06:52:20 +0000 (UTC)
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with SMTP
 id 0F62F5F1EC
	for <dev@apex.incubator.apache.org>; Wed, 16 Mar 2016 06:52:19 +0000 (UTC)
Received: (qmail 38463 invoked by uid 99); 16 Mar 2016 06:52:19 -0000
Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org)
 (140.211.11.23)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Mar 2016 06:52:19 +0000
Received: by git1-us-west.apache.org (ASF Mail Server at
 git1-us-west.apache.org, from userid 33)
	id 7B9EAE016C; Wed, 16 Mar 2016 06:52:19 +0000 (UTC)
From: chinmaykolhatkar <git@git.apache.org>
To: dev@apex.incubator.apache.org
Reply-To: dev@apex.incubator.apache.org
References: <git-pr-22-incubator-apex-site@git.apache.org>
In-Reply-To: <git-pr-22-incubator-apex-site@git.apache.org>
Subject: [GitHub] incubator-apex-site pull request: APEXCORE-321 bylaws draft
Content-Type: text/plain
Message-Id: <20160316065219.7B9EAE016C@git1-us-west.apache.org>
Date: Wed, 16 Mar 2016 06:52:19 +0000 (UTC)

Github user chinmaykolhatkar commented on a diff in the pull request:

    https://github.com/apache/incubator-apex-site/pull/22#discussion_r56288031
  
    --- 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> with
    +associated rights and responsibilities. These roles govern what tasks an individual
    +may perform within the project. The roles are defined in the following sections:
    +
    +###Users
    +
    +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
    +forums.
    +
    +###Contributors
    +
    +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.
    +
    +###Committers
    +
    +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 for
    +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 more
    +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,
    +etc.
    +
    +
    +###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
    +&ldquo;emeritus/inactive&rdquo; by not contributing in any form to the project for
    +over one year. An emeritus PMC member may request reinstatement to the PMC. Such
    +reinstatement is subject to lazy consensus of active PMC members. A PMC member may
    +resign their membership from the PMC by their own declaration. Membership of the
    +PMC can be revoked by an unanimous vote of all the active PMC members other than
    +the member in question.
    +
    +The chair of the PMC is appointed by the ASF board. The chair is an office
    +holder of the Apache Software Foundation (Vice President, Apache Apex) and has
    +primary responsibility to the board for the management of the projects within the
    +scope of the Apex PMC. The chair reports to the board quarterly on developments
    +within the Apex project. The PMC may consider the position of PMC chair annually,
    +and if supported by a successful vote to change the PMC chair, may recommend a new
    +chair to the board. Ultimately, however, it is the board&rsquo;s responsibility who
    +it chooses to appoint as the PMC chair.
    +
    +##Decision Making
    +
    +Within the Apex project, different types of decisions require different forms of
    +approval. For example, the previous section describes several decisions which require
    +&ldquo;lazy consensus&rdquo; approval. This section defines how voting is performed,
    +the types of approvals, and which types of decision require which type of
    +approval.
    +
    +###Voting
    +
    +Decisions regarding the project are made by votes on the primary project
    +development mailing list (<a class="externalLink" href=
    +"mailto:dev@apex.apache.org)">dev@apex.apache.org)</a>. Where necessary, PMC voting
    +may take place on the private Apex PMC mailing list. Votes are clearly indicated by
    +subject line starting with [VOTE]. Votes may contain multiple items for approval
    +and these should be clearly separated. Voting is carried out by replying to the
    +vote mail. Voting may take four flavours:
    +
    +<table border="0" class="table table-striped">
    +<tbody>
    +  <tr class="a">
    +    <td>+1</td>
    +
    +    <td>&ldquo;Yes,&rdquo; &ldquo;Agree,&rdquo; or &ldquo;the action should be
    +    performed.&rdquo; In general, this vote also indicates a willingness on the
    +    behalf of the voter in &ldquo;making it happen&rdquo;</td>
    +  </tr>
    +
    +  <tr class="b">
    +    <td>+0</td>
    +
    +    <td>This vote indicates a willingness for the action under consideration to
    +    go ahead. The voter, however will not be able to help.</td>
    +  </tr>
    +
    +  <tr class="a">
    +    <td>-0</td>
    +
    +    <td>This vote indicates that the voter does not, in general, agree with the
    --- End diff --
    
    Should the voter saying "-0" also tell why its not a positive vote or why the voter does not agree similar to veto vote?



---
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.
---