[GitHub] [comdev-site] adityasharma7 commented on a change in pull request #25: Update apache-project-maturity-model.md
adityasharma7 commented on a change in pull request #25: URL: https://github.com/apache/comdev-site/pull/25#discussion_r539170026 ## File path: source/apache-way/apache-project-maturity-model.md ## @@ -6,54 +6,53 @@ The **Apache Project Maturity Model** provides a suggested framework for evaluat # Overview -The goal of this maturity model is to describe how Apache projects operate, in a concise and high-level way, and to provide a basic framework that projects may choose to use to evaluate themselves. +The goals of this maturity model are to describe how Apache projects operate in a concise and high-level way, and to provide a basic framework that projects may choose to use to evaluate themselves. -It is meant to be usable outside of Apache as well, for projects that might want to adopt some or all of these principles. Projects that envision moving to Apache at some point might start working towards this to prepare for their move. +It is usable outside of Apache as well, for projects that might want to adopt some or all of these principles. Projects that envision moving to Apache at some point might start working towards this to prepare for their move. -It does not describe all the details of how our projects operate, but aims to capture the invariants of Apache projects and point to additional information where needed. To keep the main model as concise as possible we use footnotes for anything that's not part of the core model. +It does not describe all the details of how our projects operate, but aims to capture the invariants of Apache projects and point to additional information where needed. To be as concise as possible we use footnotes for anything that's not part of the core model. -Contrary to other maturity models, we do not define staged partial compliance levels. A mature Apache project complies with all the elements of this model, and other projects are welcome to pick and choose the elements that suit their goals. +Contrary to other maturity models, we do not define staged partial compliance levels. A mature Apache project complies with all the elements of this model, and other projects are welcome to adopt the elements that suit their goals. Note that we try to avoid using the word "must" below. The model describes the state of a mature project, as opposed to a set of rules. -Projects which incubate at Apache might not fit into all the parts of this model, however a major goal of incubation is to bring the project's community closer to it. +Projects which incubate at Apache might not fit into all the parts of this model; however a major goal of incubation is to bring the project's community closer to it. -Questions and feedback about this model are welcome on the https://lists.apache.org/list.html?dev@community.apache.org";>comdev mailing list. +We welcome qQuestions and feedback about this model on the https://lists.apache.org/list.html?dev@community.apache.org"; target="_blank">comdev mailing list. Review comment: ```suggestion We welcome Questions and feedback about this model on the https://lists.apache.org/list.html?dev@community.apache.org"; target="_blank">comdev 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[GitHub] [comdev-site] cottage14 opened a new pull request #39: Update use-the-comdev-issue-tracker-for-gsoc-tasks.md
cottage14 opened a new pull request #39: URL: https://github.com/apache/comdev-site/pull/39 Minor edits for clarity. 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[GitHub] [comdev-site] rlenferink merged pull request #39: Update use-the-comdev-issue-tracker-for-gsoc-tasks.md
rlenferink merged pull request #39: URL: https://github.com/apache/comdev-site/pull/39 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[GitHub] [comdev-site] rlenferink merged pull request #34: Update experiences.md
rlenferink merged pull request #34: URL: https://github.com/apache/comdev-site/pull/34 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[GitHub] [comdev-site] rlenferink merged pull request #30: Update voting.md
rlenferink merged pull request #30: URL: https://github.com/apache/comdev-site/pull/30 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[GitHub] [comdev-site] adityasharma7 commented on a change in pull request #38: Update projectIndependence.md
adityasharma7 commented on a change in pull request #38: URL: https://github.com/apache/comdev-site/pull/38#discussion_r539839380 ## File path: source/projectIndependence.md ## @@ -2,50 +2,47 @@ title: Project Independence --- -While not all aspects of the Apache Way are practiced the same way by -all projects at the ASF, there are a number of rules and policies that Apache -projects are required to follow – things like complying with PMC +While not all ASF projects practice all aspects of the Apache Way in the same way, there are a number of rules and policies that Apache +projects must follow – things like complying with PMC [release voting][1], [legal policy][2], [brand policy][3], using [mailing lists][4], etc., which are [documented in various places][5]. A community is not merely a set of rules; it is also a set of behaviors -that are expressed by the participants when interacting within that +that the participants express when interacting within that community. While the ASF is happy to host many different styles of project communities, there are some core behaviors that -are expected and required of any Apache project. +we expect and requir of any Apache project. Review comment: ```suggestion we expect and require of any Apache project. ``` 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
