Re: [PR] Propose "why" explanation on discussions and decision making [comdev-working-groups]
potiuk commented on PR #29: URL: https://github.com/apache/comdev-working-groups/pull/29#issuecomment-1992264772 Added some updates based on @justinmclean's comment. I really would love to hear from others, mainly about "using other tools as well". I think there are a number of "let's only use devlist" or "bring all the communication to the devlist automaticallly" - but as stated in the current version - there is a balance between "low signal-to-noise" on one end and "decisions made outside of the list" - which is I think the `gist` of the whole `why`. Too much in one direction is bad, too much in the other is also bad for other reasons. I wonder if the way described now is good in describing 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: notifications-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Propose "why" explanation on discussions and decision making [comdev-working-groups]
potiuk commented on code in PR #29: URL: https://github.com/apache/comdev-working-groups/pull/29#discussion_r1521914018 ## wg-advisors/why/why_discussions_and_decisions.md: ## @@ -1,13 +1,77 @@ # Why discussion and decision making had to happen on the mailing list -TODO: - ## Summary +Discussions and decision making should happen on the mailing list to ensure that the project is +transparent and that all decisions are made in the open. This is important to ensure that all +community members have the opportunity to participate in the decision making process. + ## Links to relevant documents +* [The Apache Way](https://www.apache.org/theapacheway/) +* [Mailing list guidelines](https://www.apache.org/foundation/mailinglists.html) + ## Why are we doing it? +Mailing list the primary communication channel for the project. It has been chosen - at the dawn of the +Foundation as the primary communication channel because it was the most inclusive and accessible channel +for all community members, allowing for asynchronous communication and ensuring that all community members +have the opportunity to participate. All the important decisions and discussions happens there - including +the decision to invite new committers and PMC members, the decisions to release software, and the decisions +to change the project's direction. Review Comment: I like the "informatoin density" particaularly (and agree). I added a small chapter stressing the properties you mentioned -- 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: notifications-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Propose "why" explanation on discussions and decision making [comdev-working-groups]
potiuk commented on code in PR #29: URL: https://github.com/apache/comdev-working-groups/pull/29#discussion_r1521901040 ## wg-advisors/why/why_discussions_and_decisions.md: ## @@ -1,13 +1,77 @@ # Why discussion and decision making had to happen on the mailing list -TODO: - ## Summary +Discussions and decision making should happen on the mailing list to ensure that the project is +transparent and that all decisions are made in the open. This is important to ensure that all +community members have the opportunity to participate in the decision making process. + ## Links to relevant documents +* [The Apache Way](https://www.apache.org/theapacheway/) +* [Mailing list guidelines](https://www.apache.org/foundation/mailinglists.html) + ## Why are we doing it? +Mailing list the primary communication channel for the project. It has been chosen - at the dawn of the +Foundation as the primary communication channel because it was the most inclusive and accessible channel +for all community members, allowing for asynchronous communication and ensuring that all community members +have the opportunity to participate. All the important decisions and discussions happens there - including +the decision to invite new committers and PMC members, the decisions to release software, and the decisions +to change the project's direction. + +Why the time passed and technology evolved, the mailing list still keep a lot of the properties that made it +the primary communication channel for the project. It is still the most inclusive and accessible channel for +all community members, they allow for asynchronous communication and do not require from the community members +to be online at the same time and to setup accounts with particular external services. + +They also provide a permanent record of the discussions and decisions and the Apache Software Foundation +Infrastructure team makes sure that the archives are preserved and available for the future, including the +ability to search and browse the archives, as well as permanently link to the discussions and decisions so +that they can be always referred to in the future. + +The communication on mailing list happens in English, which is the language of the Foundation, +and the language of the majority of the Foundation's community members. + +An important aspect of using the mailing list is that it allows anyone (including PMC members, committers, +contributors, and users, but also people from outside - Board members, other PMCs, non-ASF folks) to take +a look at the way how decisions are made and even participate in the discussions and decisions, and to +peek into the PMC status. This is important for the Foundation's transparency and for the community building +process. + +PMCs have at least two lists: dev@ and private@ - but it is important to mention that the private@ list should +only be used for discussions that are absolutely not suitable for public consumption, such as discussions +about security vulnerabilities, or discussions about individuals that are not suitable for public consumption +and should be kept private. The private@ list should not be used for discussions about the project's direction, +releases, or other important decisions. Review Comment: Yep. Added. -- 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: notifications-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Add links to wg git repos [comdev-site]
rbowen merged PR #163: URL: https://github.com/apache/comdev-site/pull/163 -- 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: notifications-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Add links to wg git repos [comdev-site]
rbowen opened a new pull request, #163: URL: https://github.com/apache/comdev-site/pull/163 (no 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: notifications-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] New "ASF volunteers" page to replace the community.zones.a.o apps [comdev-site]
rbowen commented on PR #146: URL: https://github.com/apache/comdev-site/pull/146#issuecomment-1991876154 +1 to all of this, and to go ahead and merge. I am content to fix problems as they come up, rather than demanding perfection before merging. Thanks for all of this work! -- 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: notifications-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Adds 'workinggroups' web content, and links to that content [comdev-site]
rbowen merged PR #162: URL: https://github.com/apache/comdev-site/pull/162 -- 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: notifications-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Adds 'workinggroups' web content, and links to that content [comdev-site]
rbowen opened a new pull request, #162: URL: https://github.com/apache/comdev-site/pull/162 (no 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: notifications-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Add justinmclean to advisor list [comdev-working-groups]
justinmclean opened a new pull request, #31: URL: https://github.com/apache/comdev-working-groups/pull/31 (no 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: notifications-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Add Calvin Kirs(kirs) to advisor list [comdev-working-groups]
CalvinKirs opened a new pull request, #30: URL: https://github.com/apache/comdev-working-groups/pull/30 (no 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: notifications-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
