You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@community.apache.org by "rbowen (via GitHub)" <gi...@apache.org> on 2023/04/20 12:34:44 UTC
[GitHub] [comdev-site] rbowen opened a new pull request, #102: Best practice docs for PMCs, etc
rbowen opened a new pull request, #102:
URL: https://github.com/apache/comdev-site/pull/102
This starts documentation around best practice for folks on the various rungs of the "contributor ladder" as they call it at the CNCF:
Contributors
Committers
PMC members
There are more rungs to the ladder, including users on the one end, and ASF members, officers, and board members on the other end. We're not there yet, but contributions are welcome.
The intent is that the format is conversational, as brief as possible, and very full of references to other resources, including formal policy, tools/scripts, and examples of where things are done well (eg great board reports, or projects that foster welcoming communities).
This is definitely a work in progress, and there are a number of "to be written" sections throughout. Come plan along.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: [GitHub] [comdev-site] potiuk commented on a diff in pull request #102: Best practice docs for PMCs, etc
Posted by Rich Bowen <rb...@rcbowen.com>.
On Fri, Apr 21, 2023, 10:30 potiuk (via GitHub) <gi...@apache.org> wrote:
>
> +PMC are binding on the outcome. Other community members may vote as
> +well, but those votes are advisory only, and not binding.
> +
> +A PMC member may veto a technical decision, such as a proposed patch.
>
> Review Comment:
> Comment here. I am not sure how it is in other projects, but we never
> thought PMC members have more "voting" or "veto" rights in case of
> technical decisions than committers have. At least in our cases PMC members
> have no more power to decide if a certain - even big - change in the
> direction of the project should happen. The only "binding" decisions that
> only PMC members have are release votes, all other votes in our case -
> including voting on big "Airflow Improvement Proposals", commiters have
> binding votes, and also committers have veto powers for those.
>
> I wonder if this is normal/expected - in the light of this comment, I
> believe it could be up to the project to decide who has the voting powers
> and it is also - I think - reflected here
> https://www.apache.org/foundation/voting.html
>
> So maybe worth to mention that thos voting powers can be also - if the
> PMC members decide - passed to regular committers?
>
> Or maybe we are doing it wrongly ?
>
Not wrong. I'd say your project is being more inclusive than it is strictly
required to be.
One should of course take the opinions of committers into consideration but
only the PMC is the final word on disagreements.
>
[GitHub] [comdev-site] potiuk commented on pull request #102: Best practice docs for PMCs, etc
Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk commented on PR #102:
URL: https://github.com/apache/comdev-site/pull/102#issuecomment-1517926192
Small comments only - this looks great @rbowen and others who commented
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
[GitHub] [comdev-site] cottage14 commented on a diff in pull request #102: Best practice docs for PMCs, etc
Posted by "cottage14 (via GitHub)" <gi...@apache.org>.
cottage14 commented on code in PR #102:
URL: https://github.com/apache/comdev-site/pull/102#discussion_r1172565399
##########
source/pmc/_index.md:
##########
@@ -0,0 +1,72 @@
+---
+title: Project Management Committees
+---
+
+The Project Management Committee, or PMC, is the technical steering
+committee for a project. This group determines the roadmap for the
+project, decides who will be added as committers and PMC members, and
+reports quarterly to the Board of Directors.
+
+* [PMC Responsibilities](#pmc-responsibilities)
+* [Chair](#chair)
+* [Voting](#voting)
+* [Reporting](#reporting)
+* [Adding new committers](#adding-new-committers)
+* [Adding new PMC members](#adding-new-pmc-members)
+* [What to do as a new member](#what-to-do-as-a-new-member)
+
+## PMC Responsibilities
+
+The PMC is responsible for the management of the project. This includes
+both the technical decisions, and ensuring that the project is operating
+in community-friendly ways.
+
+The PMC is also responsibile for voting on releases of their project, to
+ensure that each release is tested, and is an official ASF release
+artifact.
+
+[Read more about PMC responsibilities](/pmc/responsibilities)
+
+
+## Chair
+
+The PMC Chair acts as the voice of the project to the board, and is
+responsibile for filing a quarterly report. They are not the project
+leader, but are a peer of the other PMC members, who has been selected,
+for a time, to take the role of secretary and spokesperson.
+
+[Read more about the PMC Chair](/pmc/chair)
+
+## Voting
+
+While most actions of a project are decided by discussion and consensus,
+there are a number of situations in which a vote is necessary. You can
+read more about voting on the [ASF main
+website](https://apache.org/foundation/voting.html).
+
+## Reporting
+
+A PMC is required to file a report to the Board of Directors every
+quarter, on a schedule determined by the Board. [Read more about what
+goes into a PMC report](/pmc/reporting).
+
+## Adding new committers
+
+The addition of new committers is essential to the long-term
Review Comment:
Don't need 'new', as the sentence makes sense without it. Also true for lines 53 and 61
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: [GitHub] [comdev-site] bdelacretaz commented on pull request #102: Best practice docs for PMCs, etc
Posted by rb...@rcbowen.com.
On Thu, 2023-04-20 at 13:17 +0000, bdelacretaz (via GitHub) wrote:
>
> bdelacretaz commented on PR #102:
> URL:
> https://github.com/apache/comdev-site/pull/102#issuecomment-1516313840
>
> This looks really nice and useful, thanks!
>
> I see at least two existing pages that overlap with this new
> content:
>
> * https://apache.org/foundation/how-it-works.html
Yes, the how-it-works page is useful, but very terse, and tries to cram
everything into one page, rather than segregating by audience, as I'm
trying to do. Both are useful, but I think they should like to each
other.
> * https://community.apache.org/contributors/
That page is very muddled, and I have plans to un-muddle it. I think it
tries to cover too much in one page, and also addresses several
audiences at the same time.
>
> The first one might just need a link to this new content, which is
> less formal and more detailed. And also the reverse link, maybe a
> "See Also" section in your contributors ladder page?
>
> The second one might be replaced by your new content? In which
> case I'd suggest
> [redirecting](https://github.com/apache/comdev-site/blob/main/static/
> .htaccess), so that the old URL remains valid.
My intent is that /contributors/, /committers/, and /pmc/ would each
have an index page that outlines what topics are covered in that
directory. I don't want to lose the content that is currently on
/contributors/index but I think that it might end up going other
places.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
[GitHub] [comdev-site] bdelacretaz commented on pull request #102: Best practice docs for PMCs, etc
Posted by "bdelacretaz (via GitHub)" <gi...@apache.org>.
bdelacretaz commented on PR #102:
URL: https://github.com/apache/comdev-site/pull/102#issuecomment-1516313840
This looks really nice and useful, thanks!
I see at least two existing pages that overlap with this new content:
* https://apache.org/foundation/how-it-works.html
* https://community.apache.org/contributors/
The first one might just need a link to this new content, which is less formal and more detailed. And also the reverse link, maybe a "See Also" section in your contributors ladder page?
The second one might be replaced by your new content? In which case I'd suggest [redirecting](https://github.com/apache/comdev-site/blob/main/static/.htaccess), so that the old URL remains valid.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
[GitHub] [comdev-site] cottage14 commented on a diff in pull request #102: Best practice docs for PMCs, etc
Posted by "cottage14 (via GitHub)" <gi...@apache.org>.
cottage14 commented on code in PR #102:
URL: https://github.com/apache/comdev-site/pull/102#discussion_r1172567130
##########
source/pmc/_index.md:
##########
@@ -0,0 +1,72 @@
+---
+title: Project Management Committees
+---
+
+The Project Management Committee, or PMC, is the technical steering
+committee for a project. This group determines the roadmap for the
+project, decides who will be added as committers and PMC members, and
+reports quarterly to the Board of Directors.
+
+* [PMC Responsibilities](#pmc-responsibilities)
+* [Chair](#chair)
+* [Voting](#voting)
+* [Reporting](#reporting)
+* [Adding new committers](#adding-new-committers)
+* [Adding new PMC members](#adding-new-pmc-members)
+* [What to do as a new member](#what-to-do-as-a-new-member)
+
+## PMC Responsibilities
+
+The PMC is responsible for the management of the project. This includes
+both the technical decisions, and ensuring that the project is operating
+in community-friendly ways.
+
+The PMC is also responsibile for voting on releases of their project, to
+ensure that each release is tested, and is an official ASF release
+artifact.
+
+[Read more about PMC responsibilities](/pmc/responsibilities)
+
+
+## Chair
+
+The PMC Chair acts as the voice of the project to the board, and is
+responsibile for filing a quarterly report. They are not the project
+leader, but are a peer of the other PMC members, who has been selected,
+for a time, to take the role of secretary and spokesperson.
+
+[Read more about the PMC Chair](/pmc/chair)
+
+## Voting
+
+While most actions of a project are decided by discussion and consensus,
+there are a number of situations in which a vote is necessary. You can
+read more about voting on the [ASF main
+website](https://apache.org/foundation/voting.html).
+
+## Reporting
+
+A PMC is required to file a report to the Board of Directors every
+quarter, on a schedule determined by the Board. [Read more about what
+goes into a PMC report](/pmc/reporting).
+
+## Adding new committers
+
+The addition of new committers is essential to the long-term
+sustainability of an open source project. The PMC is responsible for
+determining who will be added as a committer. [Read more about how new
+committers are added to a project](/pmc/adding-committers).
+
+
+## Adding new PMC members
+
+The PMC members identify project participants who they want to be
+members of the PMC. [Read more about the process of adding new PMC
+members](/pmc/adding-pmc-members).
+
+## What to do as a new member
+
+If you've just been added as a new PMC member, there's a number of
+things that you'll need to do to be an effective part of the PMC. [Read
+more about getting started as a new PMC member](/pmc/new-member).
Review Comment:
). ==> .)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
[GitHub] [comdev-site] cottage14 commented on a diff in pull request #102: Best practice docs for PMCs, etc
Posted by "cottage14 (via GitHub)" <gi...@apache.org>.
cottage14 commented on code in PR #102:
URL: https://github.com/apache/comdev-site/pull/102#discussion_r1172551026
##########
source/contributor-ladder.md:
##########
@@ -0,0 +1,122 @@
+---
+title: ASF Contributor Ladder
+---
+
+Projects at the ASF offer a way to grow in your responsibilites in the
+project, from being a user, all the way up to being a maintainer of the
+project. While the specific details may look different from one project
+to another, the rungs of the ladder look mostly the same.
+
+* [User](#user)
+* [Contributor](#contributor)
+* [Committer](#committer)
+* [PMC Member](#pmc-member)
+* [ASF Member](#asf-member)
+* [Officers of the Foundation](#officers-of-the-foundation)
+* [Board of Directors](#board-of-directors)
+
+## User
+
+Everything that we do in an ASF project is for the user. As a user of an
+Apache project, your responsibilities are just to enjoy the software.
+
+We encourage you to join the user mailing list to ask questions, and
+make suggestions. Members of the project are there to help out when you
+run into problems. You can find this list (or lists) by looking under the
+project name on [lists.apache.org](https://lists.apache.org).
+
+As a user, you're expected to abide by the project's [code of
+conduct](https://www.apache.org/foundation/policies/conduct), so that
+interactions are polite, friendly, and helpful.
+
+As you become a power user of the project, you may consider becoming a
+contributor.
+
+## Contributor
+
+While most people think of open source contributors as being coders,
+there are a wider variety of ways that you can contribute to a project.
+
+Most users' first contribution will be to open a ticket on the project's
+issue tracker, or to answer a less experienced user's questions. These
+actions help shape the future direction of the project, and are
+important contributions.
+
+We encourage you to join the project's developer mailing list at this
+time, to engage with the dicussions about the direction that the project
+is taking. You can find this list (or lists) by looking under the
+project name on [lists.apache.org](https://lists.apache.org).
+
+Other contributions may include design, promotion, documentation
+improvements, events, and may other things.
+
+[See more about being a contributor](/contributors).
+
+As you become more involved with contributint to the project, you may
+want to work towards [becoming a
+committer](/contribotirs/becomingacommitter).
+
+## Committer
+
+After making a number of contributions to a project, you may be invited
+to become a committer. Note that the criteria for inviting a contributor
+to become a committer will vary greatly from one project to another.
+
+Once you have been invited to becomg a committer, and have accepted this
+invitation, you are authorized to commit changed directly to the
+project's source code repository. Note, however, that different projects
+may have different social norms around committing changes.
+
+Broadly referred to as CTR (Commit Then Review) and RTC (Review The
+Commit), the exact mechanisms may vary. For example, you may be
+authorized to commit documentation changes without approval, while code
+changes may be submitted as a pull request, for other committers to
+review and approve before they are merged.
+
+[See more information about being a committer](/committers).
+
+## PMC Member
+
+After being a committer for some time, you may be invited to be a member
+of the project's Project Management Committee. This group acts as the
+steering committee for the project, making decisions about the project's
+road map, what features will be added, and other decisions around the
+project.
+
+The PMC *should* be conducting all of these conversations on the public
+developer mailing list(s), in the view of the entire community. A PMC
+also has a private mailing list, which is for discussion of topics such
+as the addition of new committers and PMC members, and any other
+sensitive topics.
+
+[See more information about being a PMC member](/pmc).
+
+## Foundation Member
+
+When someone has been involved at the ASF for a while, they may be
+invited to become a member of the Foundation. This entitles them to vote
+for the Board of Directors, to participate in the members mailing list,
Review Comment:
members mailing list ==> members' mailing list
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
[GitHub] [comdev-site] cottage14 commented on a diff in pull request #102: Best practice docs for PMCs, etc
Posted by "cottage14 (via GitHub)" <gi...@apache.org>.
cottage14 commented on code in PR #102:
URL: https://github.com/apache/comdev-site/pull/102#discussion_r1172544153
##########
source/contributor-ladder.md:
##########
@@ -0,0 +1,122 @@
+---
+title: ASF Contributor Ladder
+---
+
+Projects at the ASF offer a way to grow in your responsibilites in the
+project, from being a user, all the way up to being a maintainer of the
+project. While the specific details may look different from one project
+to another, the rungs of the ladder look mostly the same.
+
+* [User](#user)
+* [Contributor](#contributor)
+* [Committer](#committer)
+* [PMC Member](#pmc-member)
+* [ASF Member](#asf-member)
+* [Officers of the Foundation](#officers-of-the-foundation)
+* [Board of Directors](#board-of-directors)
+
+## User
+
+Everything that we do in an ASF project is for the user. As a user of an
+Apache project, your responsibilities are just to enjoy the software.
+
+We encourage you to join the user mailing list to ask questions, and
+make suggestions. Members of the project are there to help out when you
+run into problems. You can find this list (or lists) by looking under the
+project name on [lists.apache.org](https://lists.apache.org).
+
+As a user, you're expected to abide by the project's [code of
+conduct](https://www.apache.org/foundation/policies/conduct), so that
+interactions are polite, friendly, and helpful.
+
+As you become a power user of the project, you may consider becoming a
+contributor.
+
+## Contributor
+
+While most people think of open source contributors as being coders,
+there are a wider variety of ways that you can contribute to a project.
+
+Most users' first contribution will be to open a ticket on the project's
+issue tracker, or to answer a less experienced user's questions. These
+actions help shape the future direction of the project, and are
+important contributions.
+
+We encourage you to join the project's developer mailing list at this
+time, to engage with the dicussions about the direction that the project
+is taking. You can find this list (or lists) by looking under the
+project name on [lists.apache.org](https://lists.apache.org).
+
+Other contributions may include design, promotion, documentation
+improvements, events, and may other things.
+
+[See more about being a contributor](/contributors).
+
+As you become more involved with contributint to the project, you may
+want to work towards [becoming a
+committer](/contribotirs/becomingacommitter).
Review Comment:
is 'contribotirs' correct??
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
[GitHub] [comdev-site] cottage14 commented on a diff in pull request #102: Best practice docs for PMCs, etc
Posted by "cottage14 (via GitHub)" <gi...@apache.org>.
cottage14 commented on code in PR #102:
URL: https://github.com/apache/comdev-site/pull/102#discussion_r1172542784
##########
source/contributor-ladder.md:
##########
@@ -0,0 +1,122 @@
+---
+title: ASF Contributor Ladder
+---
+
+Projects at the ASF offer a way to grow in your responsibilites in the
+project, from being a user, all the way up to being a maintainer of the
+project. While the specific details may look different from one project
+to another, the rungs of the ladder look mostly the same.
+
+* [User](#user)
+* [Contributor](#contributor)
+* [Committer](#committer)
+* [PMC Member](#pmc-member)
+* [ASF Member](#asf-member)
+* [Officers of the Foundation](#officers-of-the-foundation)
+* [Board of Directors](#board-of-directors)
+
+## User
+
+Everything that we do in an ASF project is for the user. As a user of an
+Apache project, your responsibilities are just to enjoy the software.
+
+We encourage you to join the user mailing list to ask questions, and
+make suggestions. Members of the project are there to help out when you
+run into problems. You can find this list (or lists) by looking under the
+project name on [lists.apache.org](https://lists.apache.org).
+
+As a user, you're expected to abide by the project's [code of
+conduct](https://www.apache.org/foundation/policies/conduct), so that
+interactions are polite, friendly, and helpful.
+
+As you become a power user of the project, you may consider becoming a
+contributor.
+
+## Contributor
+
+While most people think of open source contributors as being coders,
+there are a wider variety of ways that you can contribute to a project.
+
+Most users' first contribution will be to open a ticket on the project's
+issue tracker, or to answer a less experienced user's questions. These
+actions help shape the future direction of the project, and are
+important contributions.
+
+We encourage you to join the project's developer mailing list at this
+time, to engage with the dicussions about the direction that the project
+is taking. You can find this list (or lists) by looking under the
+project name on [lists.apache.org](https://lists.apache.org).
+
+Other contributions may include design, promotion, documentation
+improvements, events, and may other things.
Review Comment:
Line 51: might be better as 'improvements, organizing events, and many other things.' Corrects typo, too
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
[GitHub] [comdev-site] rbowen merged pull request #102: Best practice docs for PMCs, etc
Posted by "rbowen (via GitHub)" <gi...@apache.org>.
rbowen merged PR #102:
URL: https://github.com/apache/comdev-site/pull/102
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
[GitHub] [comdev-site] potiuk commented on a diff in pull request #102: Best practice docs for PMCs, etc
Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk commented on code in PR #102:
URL: https://github.com/apache/comdev-site/pull/102#discussion_r1173844845
##########
source/pmc/responsibilities.md:
##########
@@ -0,0 +1,88 @@
+---
+title: PMC Responsibilities
+---
+
+The Project Management Committee (PMC) is responsible for the oversight
+of the project, including technical decisions, ensuring that the project
+is operating in accordance with ASF norms, adding new members to the
+project, and voting on releases.
+
+* [Conducting business](#conducting-business)
+* [Ensuring project health](#ensuring-project-health)
+* [Adding community members](#adding-community-members)
+* [Reporting](/pmc/reporting)
+
+## Conducting Business
+
+The PMC is expected to conduct all of its business on the public
+developers mailing list, in the full view of the community.
+
+The private@ list is for communication about private matters, such as
+discussion of proposed committers, proposed new PMC members, and
+communication from the Board of Directors. Do not use it for discussion
+of features, roadmap, or other technical decisions.
+
+The Board of Directors will occasionally send you comments or queries,
+often related to your quarterly board report. Any PMC member can, and
+should, respond to these. You should not wait for the Chair to respond
+to these queries.
+
+The PMC is tasked with making decisions on the direction of the project,
+They can, and should, also incorporate the voice of the larger community
+in these decisions. However, if a vote is taken, only the votes of the
+PMC are binding on the outcome. Other community members may vote as
+well, but those votes are advisory only, and not binding.
+
+A PMC member may veto a technical decision, such as a proposed patch.
+However, they must be able to back this veto up with a technical reason,
+and be willing to discuss possible resolutions to their objection.
+
+Further discussion of voting may be found on the [Foundation
+website](https://www.apache.org/foundation/voting.html).
+
+## Making a release
+
+The process for releasing a official Apache software artifact may be
+found on the [Infra
+website](https://infra.apache.org/release-publishing.html). As a PMC
+member, you are expected to read and understand that process.
+
+When you vote on a release, it should be an indication that you have
Review Comment:
I love that part. We've been informally doing it all the times but sometimes it was just `+1` - having it spelled here is a good best practice to have.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
[GitHub] [comdev-site] cottage14 commented on a diff in pull request #102: Best practice docs for PMCs, etc
Posted by "cottage14 (via GitHub)" <gi...@apache.org>.
cottage14 commented on code in PR #102:
URL: https://github.com/apache/comdev-site/pull/102#discussion_r1172560082
##########
source/contributors/mailing-lists.md:
##########
@@ -0,0 +1,55 @@
+---
+title: Mailing lists
+---
+
+The ASF has a long tradition of using mailing lists as the primary
+communication format in projects. This is not merely because we've
+always done it that way, but is an intentional decision for the health
+and sustainability of our communities.
+
+## Inclusion and transparency
+
+Mailing lists ensure that all members of the community can participate
+on a level field, regardless of time zone or availability, whereas
+synchronous communication platforms (IRC, Slack, Discord, etc) benefit
+only those who are online, and in the channel, at the time of the
+conversation.
+
+Mailing lists also allow archival, so that decisions can be understood
Review Comment:
archival ==> archiving
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
[GitHub] [comdev-site] cottage14 commented on a diff in pull request #102: Best practice docs for PMCs, etc
Posted by "cottage14 (via GitHub)" <gi...@apache.org>.
cottage14 commented on code in PR #102:
URL: https://github.com/apache/comdev-site/pull/102#discussion_r1172565399
##########
source/pmc/_index.md:
##########
@@ -0,0 +1,72 @@
+---
+title: Project Management Committees
+---
+
+The Project Management Committee, or PMC, is the technical steering
+committee for a project. This group determines the roadmap for the
+project, decides who will be added as committers and PMC members, and
+reports quarterly to the Board of Directors.
+
+* [PMC Responsibilities](#pmc-responsibilities)
+* [Chair](#chair)
+* [Voting](#voting)
+* [Reporting](#reporting)
+* [Adding new committers](#adding-new-committers)
+* [Adding new PMC members](#adding-new-pmc-members)
+* [What to do as a new member](#what-to-do-as-a-new-member)
+
+## PMC Responsibilities
+
+The PMC is responsible for the management of the project. This includes
+both the technical decisions, and ensuring that the project is operating
+in community-friendly ways.
+
+The PMC is also responsibile for voting on releases of their project, to
+ensure that each release is tested, and is an official ASF release
+artifact.
+
+[Read more about PMC responsibilities](/pmc/responsibilities)
+
+
+## Chair
+
+The PMC Chair acts as the voice of the project to the board, and is
+responsibile for filing a quarterly report. They are not the project
+leader, but are a peer of the other PMC members, who has been selected,
+for a time, to take the role of secretary and spokesperson.
+
+[Read more about the PMC Chair](/pmc/chair)
+
+## Voting
+
+While most actions of a project are decided by discussion and consensus,
+there are a number of situations in which a vote is necessary. You can
+read more about voting on the [ASF main
+website](https://apache.org/foundation/voting.html).
+
+## Reporting
+
+A PMC is required to file a report to the Board of Directors every
+quarter, on a schedule determined by the Board. [Read more about what
+goes into a PMC report](/pmc/reporting).
+
+## Adding new committers
+
+The addition of new committers is essential to the long-term
Review Comment:
Don't need 'new', as the sentence makes sense without it
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
[GitHub] [comdev-site] rbowen commented on pull request #102: Best practice docs for PMCs, etc
Posted by "rbowen (via GitHub)" <gi...@apache.org>.
rbowen commented on PR #102:
URL: https://github.com/apache/comdev-site/pull/102#issuecomment-1516614526
All comments addressed. Any objections to merging and moving forward?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
[GitHub] [comdev-site] cottage14 commented on a diff in pull request #102: Best practice docs for PMCs, etc
Posted by "cottage14 (via GitHub)" <gi...@apache.org>.
cottage14 commented on code in PR #102:
URL: https://github.com/apache/comdev-site/pull/102#discussion_r1172546675
##########
source/contributor-ladder.md:
##########
@@ -0,0 +1,122 @@
+---
+title: ASF Contributor Ladder
+---
+
+Projects at the ASF offer a way to grow in your responsibilites in the
+project, from being a user, all the way up to being a maintainer of the
+project. While the specific details may look different from one project
+to another, the rungs of the ladder look mostly the same.
+
+* [User](#user)
+* [Contributor](#contributor)
+* [Committer](#committer)
+* [PMC Member](#pmc-member)
+* [ASF Member](#asf-member)
+* [Officers of the Foundation](#officers-of-the-foundation)
+* [Board of Directors](#board-of-directors)
+
+## User
+
+Everything that we do in an ASF project is for the user. As a user of an
+Apache project, your responsibilities are just to enjoy the software.
+
+We encourage you to join the user mailing list to ask questions, and
+make suggestions. Members of the project are there to help out when you
+run into problems. You can find this list (or lists) by looking under the
+project name on [lists.apache.org](https://lists.apache.org).
+
+As a user, you're expected to abide by the project's [code of
+conduct](https://www.apache.org/foundation/policies/conduct), so that
+interactions are polite, friendly, and helpful.
+
+As you become a power user of the project, you may consider becoming a
+contributor.
+
+## Contributor
+
+While most people think of open source contributors as being coders,
+there are a wider variety of ways that you can contribute to a project.
+
+Most users' first contribution will be to open a ticket on the project's
+issue tracker, or to answer a less experienced user's questions. These
+actions help shape the future direction of the project, and are
+important contributions.
+
+We encourage you to join the project's developer mailing list at this
+time, to engage with the dicussions about the direction that the project
+is taking. You can find this list (or lists) by looking under the
+project name on [lists.apache.org](https://lists.apache.org).
+
+Other contributions may include design, promotion, documentation
+improvements, events, and may other things.
+
+[See more about being a contributor](/contributors).
+
+As you become more involved with contributint to the project, you may
+want to work towards [becoming a
+committer](/contribotirs/becomingacommitter).
+
+## Committer
+
+After making a number of contributions to a project, you may be invited
+to become a committer. Note that the criteria for inviting a contributor
+to become a committer will vary greatly from one project to another.
+
+Once you have been invited to becomg a committer, and have accepted this
+invitation, you are authorized to commit changed directly to the
Review Comment:
changed ==> changes
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
[GitHub] [comdev-site] cottage14 commented on a diff in pull request #102: Best practice docs for PMCs, etc
Posted by "cottage14 (via GitHub)" <gi...@apache.org>.
cottage14 commented on code in PR #102:
URL: https://github.com/apache/comdev-site/pull/102#discussion_r1172549188
##########
source/contributor-ladder.md:
##########
@@ -0,0 +1,122 @@
+---
+title: ASF Contributor Ladder
+---
+
+Projects at the ASF offer a way to grow in your responsibilites in the
+project, from being a user, all the way up to being a maintainer of the
+project. While the specific details may look different from one project
+to another, the rungs of the ladder look mostly the same.
+
+* [User](#user)
+* [Contributor](#contributor)
+* [Committer](#committer)
+* [PMC Member](#pmc-member)
+* [ASF Member](#asf-member)
+* [Officers of the Foundation](#officers-of-the-foundation)
+* [Board of Directors](#board-of-directors)
+
+## User
+
+Everything that we do in an ASF project is for the user. As a user of an
+Apache project, your responsibilities are just to enjoy the software.
+
+We encourage you to join the user mailing list to ask questions, and
+make suggestions. Members of the project are there to help out when you
+run into problems. You can find this list (or lists) by looking under the
+project name on [lists.apache.org](https://lists.apache.org).
+
+As a user, you're expected to abide by the project's [code of
+conduct](https://www.apache.org/foundation/policies/conduct), so that
+interactions are polite, friendly, and helpful.
+
+As you become a power user of the project, you may consider becoming a
+contributor.
+
+## Contributor
+
+While most people think of open source contributors as being coders,
+there are a wider variety of ways that you can contribute to a project.
+
+Most users' first contribution will be to open a ticket on the project's
+issue tracker, or to answer a less experienced user's questions. These
+actions help shape the future direction of the project, and are
+important contributions.
+
+We encourage you to join the project's developer mailing list at this
+time, to engage with the dicussions about the direction that the project
+is taking. You can find this list (or lists) by looking under the
+project name on [lists.apache.org](https://lists.apache.org).
+
+Other contributions may include design, promotion, documentation
+improvements, events, and may other things.
+
+[See more about being a contributor](/contributors).
+
+As you become more involved with contributint to the project, you may
+want to work towards [becoming a
+committer](/contribotirs/becomingacommitter).
+
+## Committer
+
+After making a number of contributions to a project, you may be invited
+to become a committer. Note that the criteria for inviting a contributor
+to become a committer will vary greatly from one project to another.
+
+Once you have been invited to becomg a committer, and have accepted this
+invitation, you are authorized to commit changed directly to the
+project's source code repository. Note, however, that different projects
+may have different social norms around committing changes.
+
+Broadly referred to as CTR (Commit Then Review) and RTC (Review The
+Commit), the exact mechanisms may vary. For example, you may be
+authorized to commit documentation changes without approval, while code
+changes may be submitted as a pull request, for other committers to
+review and approve before they are merged.
+
+[See more information about being a committer](/committers).
+
+## PMC Member
+
+After being a committer for some time, you may be invited to be a member
Review Comment:
again, passive voice obscures who is acting. Would be clearer as "After you have been a committer for some time, the project's PMC may invite you to become a member..." (and the next line would need related changes)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
[GitHub] [comdev-site] rbowen commented on a diff in pull request #102: Best practice docs for PMCs, etc
Posted by "rbowen (via GitHub)" <gi...@apache.org>.
rbowen commented on code in PR #102:
URL: https://github.com/apache/comdev-site/pull/102#discussion_r1172804091
##########
source/pmc/_index.md:
##########
@@ -0,0 +1,72 @@
+---
+title: Project Management Committees
+---
+
+The Project Management Committee, or PMC, is the technical steering
+committee for a project. This group determines the roadmap for the
+project, decides who will be added as committers and PMC members, and
+reports quarterly to the Board of Directors.
+
+* [PMC Responsibilities](#pmc-responsibilities)
+* [Chair](#chair)
+* [Voting](#voting)
+* [Reporting](#reporting)
+* [Adding new committers](#adding-new-committers)
+* [Adding new PMC members](#adding-new-pmc-members)
+* [What to do as a new member](#what-to-do-as-a-new-member)
+
+## PMC Responsibilities
+
+The PMC is responsible for the management of the project. This includes
+both the technical decisions, and ensuring that the project is operating
+in community-friendly ways.
+
+The PMC is also responsibile for voting on releases of their project, to
+ensure that each release is tested, and is an official ASF release
+artifact.
+
+[Read more about PMC responsibilities](/pmc/responsibilities)
+
+
+## Chair
+
+The PMC Chair acts as the voice of the project to the board, and is
+responsibile for filing a quarterly report. They are not the project
+leader, but are a peer of the other PMC members, who has been selected,
+for a time, to take the role of secretary and spokesperson.
+
+[Read more about the PMC Chair](/pmc/chair)
+
+## Voting
+
+While most actions of a project are decided by discussion and consensus,
+there are a number of situations in which a vote is necessary. You can
+read more about voting on the [ASF main
+website](https://apache.org/foundation/voting.html).
+
+## Reporting
+
+A PMC is required to file a report to the Board of Directors every
+quarter, on a schedule determined by the Board. [Read more about what
+goes into a PMC report](/pmc/reporting).
+
+## Adding new committers
+
+The addition of new committers is essential to the long-term
+sustainability of an open source project. The PMC is responsible for
+determining who will be added as a committer. [Read more about how new
+committers are added to a project](/pmc/adding-committers).
+
+
+## Adding new PMC members
+
+The PMC members identify project participants who they want to be
+members of the PMC. [Read more about the process of adding new PMC
+members](/pmc/adding-pmc-members).
+
+## What to do as a new member
+
+If you've just been added as a new PMC member, there's a number of
+things that you'll need to do to be an effective part of the PMC. [Read
+more about getting started as a new PMC member](/pmc/new-member).
Review Comment:
No, I don't think so. the (...) in this is markdown syntax for a link, not punctuation. So the period correctly goes outside of that paren.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
[GitHub] [comdev-site] cottage14 commented on a diff in pull request #102: Best practice docs for PMCs, etc
Posted by "cottage14 (via GitHub)" <gi...@apache.org>.
cottage14 commented on code in PR #102:
URL: https://github.com/apache/comdev-site/pull/102#discussion_r1172559623
##########
source/contributors/mailing-lists.md:
##########
@@ -0,0 +1,55 @@
+---
+title: Mailing lists
+---
+
+The ASF has a long tradition of using mailing lists as the primary
+communication format in projects. This is not merely because we've
+always done it that way, but is an intentional decision for the health
+and sustainability of our communities.
+
+## Inclusion and transparency
+
+Mailing lists ensure that all members of the community can participate
+on a level field, regardless of time zone or availability, whereas
+synchronous communication platforms (IRC, Slack, Discord, etc) benefit
Review Comment:
etc) ==> etc.)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
[GitHub] [comdev-site] cottage14 commented on a diff in pull request #102: Best practice docs for PMCs, etc
Posted by "cottage14 (via GitHub)" <gi...@apache.org>.
cottage14 commented on code in PR #102:
URL: https://github.com/apache/comdev-site/pull/102#discussion_r1172552556
##########
source/contributor-ladder.md:
##########
@@ -0,0 +1,122 @@
+---
+title: ASF Contributor Ladder
+---
+
+Projects at the ASF offer a way to grow in your responsibilites in the
+project, from being a user, all the way up to being a maintainer of the
+project. While the specific details may look different from one project
+to another, the rungs of the ladder look mostly the same.
+
+* [User](#user)
+* [Contributor](#contributor)
+* [Committer](#committer)
+* [PMC Member](#pmc-member)
+* [ASF Member](#asf-member)
+* [Officers of the Foundation](#officers-of-the-foundation)
+* [Board of Directors](#board-of-directors)
+
+## User
+
+Everything that we do in an ASF project is for the user. As a user of an
+Apache project, your responsibilities are just to enjoy the software.
+
+We encourage you to join the user mailing list to ask questions, and
+make suggestions. Members of the project are there to help out when you
+run into problems. You can find this list (or lists) by looking under the
+project name on [lists.apache.org](https://lists.apache.org).
+
+As a user, you're expected to abide by the project's [code of
+conduct](https://www.apache.org/foundation/policies/conduct), so that
+interactions are polite, friendly, and helpful.
+
+As you become a power user of the project, you may consider becoming a
+contributor.
+
+## Contributor
+
+While most people think of open source contributors as being coders,
+there are a wider variety of ways that you can contribute to a project.
+
+Most users' first contribution will be to open a ticket on the project's
+issue tracker, or to answer a less experienced user's questions. These
+actions help shape the future direction of the project, and are
+important contributions.
+
+We encourage you to join the project's developer mailing list at this
+time, to engage with the dicussions about the direction that the project
+is taking. You can find this list (or lists) by looking under the
+project name on [lists.apache.org](https://lists.apache.org).
+
+Other contributions may include design, promotion, documentation
+improvements, events, and may other things.
+
+[See more about being a contributor](/contributors).
+
+As you become more involved with contributint to the project, you may
+want to work towards [becoming a
+committer](/contribotirs/becomingacommitter).
+
+## Committer
+
+After making a number of contributions to a project, you may be invited
+to become a committer. Note that the criteria for inviting a contributor
+to become a committer will vary greatly from one project to another.
+
+Once you have been invited to becomg a committer, and have accepted this
+invitation, you are authorized to commit changed directly to the
+project's source code repository. Note, however, that different projects
+may have different social norms around committing changes.
+
+Broadly referred to as CTR (Commit Then Review) and RTC (Review The
+Commit), the exact mechanisms may vary. For example, you may be
+authorized to commit documentation changes without approval, while code
+changes may be submitted as a pull request, for other committers to
+review and approve before they are merged.
+
+[See more information about being a committer](/committers).
+
+## PMC Member
+
+After being a committer for some time, you may be invited to be a member
+of the project's Project Management Committee. This group acts as the
+steering committee for the project, making decisions about the project's
+road map, what features will be added, and other decisions around the
+project.
+
+The PMC *should* be conducting all of these conversations on the public
+developer mailing list(s), in the view of the entire community. A PMC
+also has a private mailing list, which is for discussion of topics such
+as the addition of new committers and PMC members, and any other
+sensitive topics.
+
+[See more information about being a PMC member](/pmc).
+
+## Foundation Member
+
+When someone has been involved at the ASF for a while, they may be
+invited to become a member of the Foundation. This entitles them to vote
+for the Board of Directors, to participate in the members mailing list,
+and to invite others to become Foundation members.
+
+[See more about being a Foundation
+member](https://apache.org/foundation/governance/members.html)
+
+## Officers of the Foundation
+
+Officers of the Foundation are responsible for various aspects of the
+day-to-day operation of the Foundation. You can see how these roles are
+broken down in the [Foundation organization
+chart](https://whimsy.apache.org/foundation/orgchart/board).
+
+## Board of Directors
+
+The Board of Directors is responsible for the governance of the
+Foundation. This includes overseeing projects, to ensure they are
+behaving in accordance with ASF policies and norms.
Review Comment:
Add "The members of the ASF elect the members of the Board annually for one-year terms."
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
[GitHub] [comdev-site] cottage14 commented on a diff in pull request #102: Best practice docs for PMCs, etc
Posted by "cottage14 (via GitHub)" <gi...@apache.org>.
cottage14 commented on code in PR #102:
URL: https://github.com/apache/comdev-site/pull/102#discussion_r1172545711
##########
source/contributor-ladder.md:
##########
@@ -0,0 +1,122 @@
+---
+title: ASF Contributor Ladder
+---
+
+Projects at the ASF offer a way to grow in your responsibilites in the
+project, from being a user, all the way up to being a maintainer of the
+project. While the specific details may look different from one project
+to another, the rungs of the ladder look mostly the same.
+
+* [User](#user)
+* [Contributor](#contributor)
+* [Committer](#committer)
+* [PMC Member](#pmc-member)
+* [ASF Member](#asf-member)
+* [Officers of the Foundation](#officers-of-the-foundation)
+* [Board of Directors](#board-of-directors)
+
+## User
+
+Everything that we do in an ASF project is for the user. As a user of an
+Apache project, your responsibilities are just to enjoy the software.
+
+We encourage you to join the user mailing list to ask questions, and
+make suggestions. Members of the project are there to help out when you
+run into problems. You can find this list (or lists) by looking under the
+project name on [lists.apache.org](https://lists.apache.org).
+
+As a user, you're expected to abide by the project's [code of
+conduct](https://www.apache.org/foundation/policies/conduct), so that
+interactions are polite, friendly, and helpful.
+
+As you become a power user of the project, you may consider becoming a
+contributor.
+
+## Contributor
+
+While most people think of open source contributors as being coders,
+there are a wider variety of ways that you can contribute to a project.
+
+Most users' first contribution will be to open a ticket on the project's
+issue tracker, or to answer a less experienced user's questions. These
+actions help shape the future direction of the project, and are
+important contributions.
+
+We encourage you to join the project's developer mailing list at this
+time, to engage with the dicussions about the direction that the project
+is taking. You can find this list (or lists) by looking under the
+project name on [lists.apache.org](https://lists.apache.org).
+
+Other contributions may include design, promotion, documentation
+improvements, events, and may other things.
+
+[See more about being a contributor](/contributors).
+
+As you become more involved with contributint to the project, you may
+want to work towards [becoming a
+committer](/contribotirs/becomingacommitter).
+
+## Committer
+
+After making a number of contributions to a project, you may be invited
Review Comment:
line 61: passive voice obscures who is acting. Would be clearer as "After you have made a number of contributions to a project, its PMC may invite you..."
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
[GitHub] [comdev-site] potiuk commented on a diff in pull request #102: Best practice docs for PMCs, etc
Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk commented on code in PR #102:
URL: https://github.com/apache/comdev-site/pull/102#discussion_r1173842272
##########
source/pmc/responsibilities.md:
##########
@@ -0,0 +1,88 @@
+---
+title: PMC Responsibilities
+---
+
+The Project Management Committee (PMC) is responsible for the oversight
+of the project, including technical decisions, ensuring that the project
+is operating in accordance with ASF norms, adding new members to the
+project, and voting on releases.
+
+* [Conducting business](#conducting-business)
+* [Ensuring project health](#ensuring-project-health)
+* [Adding community members](#adding-community-members)
+* [Reporting](/pmc/reporting)
+
+## Conducting Business
+
+The PMC is expected to conduct all of its business on the public
+developers mailing list, in the full view of the community.
+
+The private@ list is for communication about private matters, such as
+discussion of proposed committers, proposed new PMC members, and
+communication from the Board of Directors. Do not use it for discussion
+of features, roadmap, or other technical decisions.
+
+The Board of Directors will occasionally send you comments or queries,
+often related to your quarterly board report. Any PMC member can, and
+should, respond to these. You should not wait for the Chair to respond
+to these queries.
+
+The PMC is tasked with making decisions on the direction of the project,
+They can, and should, also incorporate the voice of the larger community
+in these decisions. However, if a vote is taken, only the votes of the
+PMC are binding on the outcome. Other community members may vote as
+well, but those votes are advisory only, and not binding.
+
+A PMC member may veto a technical decision, such as a proposed patch.
Review Comment:
Comment here. I am not sure how it is in other projects, but we never thought PMC members have more "voting" or "veto" rights in case of technical decisions than committers have. At least in our cases PMC members have no more power to decide if a certain - even big - change in the direction of the project should happen. The only "binding" decisions that only PMC members have are release votes, all other votes in our case - including voting on big "Airflow Improvement Proposals", commiters have binding votes, and also committers have veto powers for those.
I wonder if this is normal/expected - in the light of this comment, I believe it could be up to the project to decide who has the voting powers and it is also - I think - reflected here https://www.apache.org/foundation/voting.html
So maybe worth to mention that thos voting powers can be also - if the PMC members decide - passed to regular committers?
Or maybe we are doing it wrongly ?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
[GitHub] [comdev-site] cottage14 commented on a diff in pull request #102: Best practice docs for PMCs, etc
Posted by "cottage14 (via GitHub)" <gi...@apache.org>.
cottage14 commented on code in PR #102:
URL: https://github.com/apache/comdev-site/pull/102#discussion_r1172552556
##########
source/contributor-ladder.md:
##########
@@ -0,0 +1,122 @@
+---
+title: ASF Contributor Ladder
+---
+
+Projects at the ASF offer a way to grow in your responsibilites in the
+project, from being a user, all the way up to being a maintainer of the
+project. While the specific details may look different from one project
+to another, the rungs of the ladder look mostly the same.
+
+* [User](#user)
+* [Contributor](#contributor)
+* [Committer](#committer)
+* [PMC Member](#pmc-member)
+* [ASF Member](#asf-member)
+* [Officers of the Foundation](#officers-of-the-foundation)
+* [Board of Directors](#board-of-directors)
+
+## User
+
+Everything that we do in an ASF project is for the user. As a user of an
+Apache project, your responsibilities are just to enjoy the software.
+
+We encourage you to join the user mailing list to ask questions, and
+make suggestions. Members of the project are there to help out when you
+run into problems. You can find this list (or lists) by looking under the
+project name on [lists.apache.org](https://lists.apache.org).
+
+As a user, you're expected to abide by the project's [code of
+conduct](https://www.apache.org/foundation/policies/conduct), so that
+interactions are polite, friendly, and helpful.
+
+As you become a power user of the project, you may consider becoming a
+contributor.
+
+## Contributor
+
+While most people think of open source contributors as being coders,
+there are a wider variety of ways that you can contribute to a project.
+
+Most users' first contribution will be to open a ticket on the project's
+issue tracker, or to answer a less experienced user's questions. These
+actions help shape the future direction of the project, and are
+important contributions.
+
+We encourage you to join the project's developer mailing list at this
+time, to engage with the dicussions about the direction that the project
+is taking. You can find this list (or lists) by looking under the
+project name on [lists.apache.org](https://lists.apache.org).
+
+Other contributions may include design, promotion, documentation
+improvements, events, and may other things.
+
+[See more about being a contributor](/contributors).
+
+As you become more involved with contributint to the project, you may
+want to work towards [becoming a
+committer](/contribotirs/becomingacommitter).
+
+## Committer
+
+After making a number of contributions to a project, you may be invited
+to become a committer. Note that the criteria for inviting a contributor
+to become a committer will vary greatly from one project to another.
+
+Once you have been invited to becomg a committer, and have accepted this
+invitation, you are authorized to commit changed directly to the
+project's source code repository. Note, however, that different projects
+may have different social norms around committing changes.
+
+Broadly referred to as CTR (Commit Then Review) and RTC (Review The
+Commit), the exact mechanisms may vary. For example, you may be
+authorized to commit documentation changes without approval, while code
+changes may be submitted as a pull request, for other committers to
+review and approve before they are merged.
+
+[See more information about being a committer](/committers).
+
+## PMC Member
+
+After being a committer for some time, you may be invited to be a member
+of the project's Project Management Committee. This group acts as the
+steering committee for the project, making decisions about the project's
+road map, what features will be added, and other decisions around the
+project.
+
+The PMC *should* be conducting all of these conversations on the public
+developer mailing list(s), in the view of the entire community. A PMC
+also has a private mailing list, which is for discussion of topics such
+as the addition of new committers and PMC members, and any other
+sensitive topics.
+
+[See more information about being a PMC member](/pmc).
+
+## Foundation Member
+
+When someone has been involved at the ASF for a while, they may be
+invited to become a member of the Foundation. This entitles them to vote
+for the Board of Directors, to participate in the members mailing list,
+and to invite others to become Foundation members.
+
+[See more about being a Foundation
+member](https://apache.org/foundation/governance/members.html)
+
+## Officers of the Foundation
+
+Officers of the Foundation are responsible for various aspects of the
+day-to-day operation of the Foundation. You can see how these roles are
+broken down in the [Foundation organization
+chart](https://whimsy.apache.org/foundation/orgchart/board).
+
+## Board of Directors
+
+The Board of Directors is responsible for the governance of the
+Foundation. This includes overseeing projects, to ensure they are
+behaving in accordance with ASF policies and norms.
Review Comment:
Add "The members of the ASF elected the members of the Board annually for one-year terms."
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
[GitHub] [comdev-site] cottage14 commented on a diff in pull request #102: Best practice docs for PMCs, etc
Posted by "cottage14 (via GitHub)" <gi...@apache.org>.
cottage14 commented on code in PR #102:
URL: https://github.com/apache/comdev-site/pull/102#discussion_r1172550559
##########
source/contributor-ladder.md:
##########
@@ -0,0 +1,122 @@
+---
+title: ASF Contributor Ladder
+---
+
+Projects at the ASF offer a way to grow in your responsibilites in the
+project, from being a user, all the way up to being a maintainer of the
+project. While the specific details may look different from one project
+to another, the rungs of the ladder look mostly the same.
+
+* [User](#user)
+* [Contributor](#contributor)
+* [Committer](#committer)
+* [PMC Member](#pmc-member)
+* [ASF Member](#asf-member)
+* [Officers of the Foundation](#officers-of-the-foundation)
+* [Board of Directors](#board-of-directors)
+
+## User
+
+Everything that we do in an ASF project is for the user. As a user of an
+Apache project, your responsibilities are just to enjoy the software.
+
+We encourage you to join the user mailing list to ask questions, and
+make suggestions. Members of the project are there to help out when you
+run into problems. You can find this list (or lists) by looking under the
+project name on [lists.apache.org](https://lists.apache.org).
+
+As a user, you're expected to abide by the project's [code of
+conduct](https://www.apache.org/foundation/policies/conduct), so that
+interactions are polite, friendly, and helpful.
+
+As you become a power user of the project, you may consider becoming a
+contributor.
+
+## Contributor
+
+While most people think of open source contributors as being coders,
+there are a wider variety of ways that you can contribute to a project.
+
+Most users' first contribution will be to open a ticket on the project's
+issue tracker, or to answer a less experienced user's questions. These
+actions help shape the future direction of the project, and are
+important contributions.
+
+We encourage you to join the project's developer mailing list at this
+time, to engage with the dicussions about the direction that the project
+is taking. You can find this list (or lists) by looking under the
+project name on [lists.apache.org](https://lists.apache.org).
+
+Other contributions may include design, promotion, documentation
+improvements, events, and may other things.
+
+[See more about being a contributor](/contributors).
+
+As you become more involved with contributint to the project, you may
+want to work towards [becoming a
+committer](/contribotirs/becomingacommitter).
+
+## Committer
+
+After making a number of contributions to a project, you may be invited
+to become a committer. Note that the criteria for inviting a contributor
+to become a committer will vary greatly from one project to another.
+
+Once you have been invited to becomg a committer, and have accepted this
+invitation, you are authorized to commit changed directly to the
+project's source code repository. Note, however, that different projects
+may have different social norms around committing changes.
+
+Broadly referred to as CTR (Commit Then Review) and RTC (Review The
+Commit), the exact mechanisms may vary. For example, you may be
+authorized to commit documentation changes without approval, while code
+changes may be submitted as a pull request, for other committers to
+review and approve before they are merged.
+
+[See more information about being a committer](/committers).
+
+## PMC Member
+
+After being a committer for some time, you may be invited to be a member
+of the project's Project Management Committee. This group acts as the
+steering committee for the project, making decisions about the project's
+road map, what features will be added, and other decisions around the
+project.
+
+The PMC *should* be conducting all of these conversations on the public
+developer mailing list(s), in the view of the entire community. A PMC
+also has a private mailing list, which is for discussion of topics such
+as the addition of new committers and PMC members, and any other
+sensitive topics.
+
+[See more information about being a PMC member](/pmc).
+
+## Foundation Member
+
+When someone has been involved at the ASF for a while, they may be
+invited to become a member of the Foundation. This entitles them to vote
Review Comment:
invited by whom?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
[GitHub] [comdev-site] cottage14 commented on a diff in pull request #102: Best practice docs for PMCs, etc
Posted by "cottage14 (via GitHub)" <gi...@apache.org>.
cottage14 commented on code in PR #102:
URL: https://github.com/apache/comdev-site/pull/102#discussion_r1172547346
##########
source/contributor-ladder.md:
##########
@@ -0,0 +1,122 @@
+---
+title: ASF Contributor Ladder
+---
+
+Projects at the ASF offer a way to grow in your responsibilites in the
+project, from being a user, all the way up to being a maintainer of the
+project. While the specific details may look different from one project
+to another, the rungs of the ladder look mostly the same.
+
+* [User](#user)
+* [Contributor](#contributor)
+* [Committer](#committer)
+* [PMC Member](#pmc-member)
+* [ASF Member](#asf-member)
+* [Officers of the Foundation](#officers-of-the-foundation)
+* [Board of Directors](#board-of-directors)
+
+## User
+
+Everything that we do in an ASF project is for the user. As a user of an
+Apache project, your responsibilities are just to enjoy the software.
+
+We encourage you to join the user mailing list to ask questions, and
+make suggestions. Members of the project are there to help out when you
+run into problems. You can find this list (or lists) by looking under the
+project name on [lists.apache.org](https://lists.apache.org).
+
+As a user, you're expected to abide by the project's [code of
+conduct](https://www.apache.org/foundation/policies/conduct), so that
+interactions are polite, friendly, and helpful.
+
+As you become a power user of the project, you may consider becoming a
+contributor.
+
+## Contributor
+
+While most people think of open source contributors as being coders,
+there are a wider variety of ways that you can contribute to a project.
+
+Most users' first contribution will be to open a ticket on the project's
+issue tracker, or to answer a less experienced user's questions. These
+actions help shape the future direction of the project, and are
+important contributions.
+
+We encourage you to join the project's developer mailing list at this
+time, to engage with the dicussions about the direction that the project
+is taking. You can find this list (or lists) by looking under the
+project name on [lists.apache.org](https://lists.apache.org).
+
+Other contributions may include design, promotion, documentation
+improvements, events, and may other things.
+
+[See more about being a contributor](/contributors).
+
+As you become more involved with contributint to the project, you may
+want to work towards [becoming a
+committer](/contribotirs/becomingacommitter).
+
+## Committer
+
+After making a number of contributions to a project, you may be invited
+to become a committer. Note that the criteria for inviting a contributor
+to become a committer will vary greatly from one project to another.
+
+Once you have been invited to becomg a committer, and have accepted this
+invitation, you are authorized to commit changed directly to the
+project's source code repository. Note, however, that different projects
+may have different social norms around committing changes.
+
+Broadly referred to as CTR (Commit Then Review) and RTC (Review The
Review Comment:
Review The ==> Review Then
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
[GitHub] [comdev-site] cottage14 commented on a diff in pull request #102: Best practice docs for PMCs, etc
Posted by "cottage14 (via GitHub)" <gi...@apache.org>.
cottage14 commented on code in PR #102:
URL: https://github.com/apache/comdev-site/pull/102#discussion_r1172546277
##########
source/contributor-ladder.md:
##########
@@ -0,0 +1,122 @@
+---
+title: ASF Contributor Ladder
+---
+
+Projects at the ASF offer a way to grow in your responsibilites in the
+project, from being a user, all the way up to being a maintainer of the
+project. While the specific details may look different from one project
+to another, the rungs of the ladder look mostly the same.
+
+* [User](#user)
+* [Contributor](#contributor)
+* [Committer](#committer)
+* [PMC Member](#pmc-member)
+* [ASF Member](#asf-member)
+* [Officers of the Foundation](#officers-of-the-foundation)
+* [Board of Directors](#board-of-directors)
+
+## User
+
+Everything that we do in an ASF project is for the user. As a user of an
+Apache project, your responsibilities are just to enjoy the software.
+
+We encourage you to join the user mailing list to ask questions, and
+make suggestions. Members of the project are there to help out when you
+run into problems. You can find this list (or lists) by looking under the
+project name on [lists.apache.org](https://lists.apache.org).
+
+As a user, you're expected to abide by the project's [code of
+conduct](https://www.apache.org/foundation/policies/conduct), so that
+interactions are polite, friendly, and helpful.
+
+As you become a power user of the project, you may consider becoming a
+contributor.
+
+## Contributor
+
+While most people think of open source contributors as being coders,
+there are a wider variety of ways that you can contribute to a project.
+
+Most users' first contribution will be to open a ticket on the project's
+issue tracker, or to answer a less experienced user's questions. These
+actions help shape the future direction of the project, and are
+important contributions.
+
+We encourage you to join the project's developer mailing list at this
+time, to engage with the dicussions about the direction that the project
+is taking. You can find this list (or lists) by looking under the
+project name on [lists.apache.org](https://lists.apache.org).
+
+Other contributions may include design, promotion, documentation
+improvements, events, and may other things.
+
+[See more about being a contributor](/contributors).
+
+As you become more involved with contributint to the project, you may
+want to work towards [becoming a
+committer](/contribotirs/becomingacommitter).
+
+## Committer
+
+After making a number of contributions to a project, you may be invited
+to become a committer. Note that the criteria for inviting a contributor
+to become a committer will vary greatly from one project to another.
+
+Once you have been invited to becomg a committer, and have accepted this
Review Comment:
becomg ==> become
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
[GitHub] [comdev-site] cottage14 commented on a diff in pull request #102: Best practice docs for PMCs, etc
Posted by "cottage14 (via GitHub)" <gi...@apache.org>.
cottage14 commented on code in PR #102:
URL: https://github.com/apache/comdev-site/pull/102#discussion_r1172543386
##########
source/contributor-ladder.md:
##########
@@ -0,0 +1,122 @@
+---
+title: ASF Contributor Ladder
+---
+
+Projects at the ASF offer a way to grow in your responsibilites in the
+project, from being a user, all the way up to being a maintainer of the
+project. While the specific details may look different from one project
+to another, the rungs of the ladder look mostly the same.
+
+* [User](#user)
+* [Contributor](#contributor)
+* [Committer](#committer)
+* [PMC Member](#pmc-member)
+* [ASF Member](#asf-member)
+* [Officers of the Foundation](#officers-of-the-foundation)
+* [Board of Directors](#board-of-directors)
+
+## User
+
+Everything that we do in an ASF project is for the user. As a user of an
+Apache project, your responsibilities are just to enjoy the software.
+
+We encourage you to join the user mailing list to ask questions, and
+make suggestions. Members of the project are there to help out when you
+run into problems. You can find this list (or lists) by looking under the
+project name on [lists.apache.org](https://lists.apache.org).
+
+As a user, you're expected to abide by the project's [code of
+conduct](https://www.apache.org/foundation/policies/conduct), so that
+interactions are polite, friendly, and helpful.
+
+As you become a power user of the project, you may consider becoming a
+contributor.
+
+## Contributor
+
+While most people think of open source contributors as being coders,
+there are a wider variety of ways that you can contribute to a project.
+
+Most users' first contribution will be to open a ticket on the project's
+issue tracker, or to answer a less experienced user's questions. These
+actions help shape the future direction of the project, and are
+important contributions.
+
+We encourage you to join the project's developer mailing list at this
+time, to engage with the dicussions about the direction that the project
+is taking. You can find this list (or lists) by looking under the
+project name on [lists.apache.org](https://lists.apache.org).
+
+Other contributions may include design, promotion, documentation
+improvements, events, and may other things.
+
+[See more about being a contributor](/contributors).
+
+As you become more involved with contributint to the project, you may
Review Comment:
contributint ==> contributing
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org