Re: [PR] Add next examples that discourages to contributions [comdev-working-groups]
potiuk commented on PR #19: URL: https://github.com/apache/comdev-working-groups/pull/19#issuecomment-1962388856 > Inspiring by this simple discussion, I'm taking to try to activate more contributors > > https://lists.apache.org/thread/y1b0x39g3xkh45klmv9ndfj1czcrx4zb > > we will see what happens Cool. For testing the RC - what works for us perfectly is that when we send an RC we generat this kind of issue: https://github.com/apache/airflow/issues/37648 - all the contributors who contributed to the release candidate are `@-mentioned` and invited to test their changes, and we have `checkmarks` that the release manager checks when someone confirms that a change/fix works as expected - we regularly have 60%-80% changes tested and verified for pretty much all releases -- 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-unsubscr...@community.apache.org 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
Re: [PR] Add next examples that discourages to contributions [comdev-working-groups]
slawekjaranowski commented on PR #19: URL: https://github.com/apache/comdev-working-groups/pull/19#issuecomment-1962385814 Inspiring by this simple discussion, I'm taking to try to activate more contributors https://lists.apache.org/thread/y1b0x39g3xkh45klmv9ndfj1czcrx4zb we will see what happens -- 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-unsubscr...@community.apache.org 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
Re: [PR] Add a chapter about "collaborative" aspect of Advisors [comdev-working-groups]
slawekjaranowski commented on PR #20: URL: https://github.com/apache/comdev-working-groups/pull/20#issuecomment-1962335940 > Fingers crossed that we will be able to incentivise enough engaged members and PMCs to make Advisors a useful platformm for this kind of collaboration. Good luck from me. Sometime looking from outside on a project can open an eyes for a new ideas. -- 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-unsubscr...@community.apache.org 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
Re: [PR] Add next examples that discourages to contributions [comdev-working-groups]
potiuk commented on code in PR #19: URL: https://github.com/apache/comdev-working-groups/pull/19#discussion_r1501401856 ## wg-advisors/red-flags.md: ## @@ -20,6 +20,9 @@ not a policeman enforcing the rules. * Discussions are happening off-list. * Too much talk is happening on the private list. * Users' questions are going unanswered on the mailing list. +* Users' reported issues are going uncommented and untouched. Review Comment: Example from Airflow: We are using "collaborators" for that (AKA triage team) where we ask and encourage people to become members of the team and help to triage the issues/PR, we actively "recruit" people to the team (often those people become committers or stop being active so it's natural but also from time to time we have a "call for collaborators" - which reminds people that there is something like "collaborators" and why. But it's far from perfect I would love to know how others are doing it :D -- 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-unsubscr...@community.apache.org 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
Re: [PR] Add next examples that discourages to contributions [comdev-working-groups]
potiuk commented on code in PR #19: URL: https://github.com/apache/comdev-working-groups/pull/19#discussion_r1501401856 ## wg-advisors/red-flags.md: ## @@ -20,6 +20,9 @@ not a policeman enforcing the rules. * Discussions are happening off-list. * Too much talk is happening on the private list. * Users' questions are going unanswered on the mailing list. +* Users' reported issues are going uncommented and untouched. Review Comment: Example from Airflow: We are using "collaborators" for that (aka known as triage team) where we ask and encourage people to become members of the team and help to triage the issues/PR, we actively "recruit" people to the team (often those people become committers or stop being active so it's natural but also from time to time we have a "call for collaborators" - which reminds people that there is something like "collaborators" and why. But it's far from perfect I would love to know how others are doing it :D -- 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-unsubscr...@community.apache.org 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
[PR] Add a chapter about "collaborative" aspect of Advisors [comdev-working-groups]
potiuk opened a new pull request, #20: URL: https://github.com/apache/comdev-working-groups/pull/20 Having a - potentially - bigger and engaged group of Advisors that can exchange best practices they learn from the project and have the possibility of shaping best practices that other Advisors will also disseminate among other projects, is probably one of the biggest values of a group such as Advisors and we should state it explicitly that such collaboration is expected and encouraged. Also this might be one of the important incentives for Advisors to get engaged, and for PMCs to ask for Advisors when they know that whatever they do with Advisors is not only to apply "top-bottom" rules and principles, but also to be able to share their own practices and ideas and variations coming from different stages, size, stakeholder engagement they are in - and knowing that they can also shape the common understanding and interpretation of the rules and principles the ASF is built on. Fingers crossed that we will be able to incentivise enough engaged members and PMCs to make Advisors a useful platformm for this kind of collaboration. -- 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-unsubscr...@community.apache.org 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
Re: [PR] Add next examples that discourages to contributions [comdev-working-groups]
potiuk commented on PR #19: URL: https://github.com/apache/comdev-working-groups/pull/19#issuecomment-1962325653 > Although I'm afraid it's too generic to be a red flag, these are good points. I think one of the good things - assuming we will have a number of advisors advising a number of projects - those might be a great subject to discuss - how PMCs are dealing with those? how they dealt with it when things became too overwhelming? How they engaged wider community. I think `advisors` is a great platform to discuss it and bring those ideas in and disseminate it among other PMCs - that's the "Bi-directionality" I added yesterday, but I will also add a small chapter about this "platform" thingie. -- 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-unsubscr...@community.apache.org 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
Re: [PR] Add next examples that discourages to contributions [comdev-working-groups]
slawekjaranowski commented on code in PR #19: URL: https://github.com/apache/comdev-working-groups/pull/19#discussion_r1501397552 ## wg-advisors/red-flags.md: ## @@ -20,6 +20,9 @@ not a policeman enforcing the rules. * Discussions are happening off-list. * Too much talk is happening on the private list. * Users' questions are going unanswered on the mailing list. +* Users' reported issues are going uncommented and untouched. Review Comment: In PMCs like Maven we have many projects which are different and many times to do a PR review, comment issues deeper knowledge is needed in a specific project ... but not all commiters good know all projects and so on ... So helping from contributors can be very valuable. It can be very interesting how others projects deal with such cases ... -- 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-unsubscr...@community.apache.org 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
Re: [PR] Propose "why" folder that we will keep as "advisors" knowledge base [comdev-working-groups]
potiuk commented on PR #16: URL: https://github.com/apache/comdev-working-groups/pull/16#issuecomment-1962324323 Ready for the next round of reviews. -- 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-unsubscr...@community.apache.org 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
Re: [PR] Propose "why" folder that we will keep as "advisors" knowledge base [comdev-working-groups]
potiuk commented on code in PR #16: URL: https://github.com/apache/comdev-working-groups/pull/16#discussion_r1501396031 ## wg-advisors/red-flags.md: ## @@ -15,7 +15,7 @@ not a policeman enforcing the rules. * Has a website external to apache.org * Is missing reports * Is missing release votes -* Has too many release candidates +* Has too many release candidates: [why](why/why_release_process.md) Review Comment: I tried to separate it, but indeed it seems better if it is combined in the release process. I just stressed how important it is to engage the dev community in the release/testing process and added a little description summarising why we are doing it. Should be explained now. -- 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-unsubscr...@community.apache.org 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
Re: [PR] Propose "why" folder that we will keep as "advisors" knowledge base [comdev-working-groups]
potiuk commented on code in PR #16: URL: https://github.com/apache/comdev-working-groups/pull/16#discussion_r1501395596 ## wg-advisors/why/why_release_process.md: ## @@ -0,0 +1,30 @@ +# Release process + +## Summary + +ASF project release software following a well defined process involving PMC members voting on release +candidates, publishing the artifacts in the ASF distribution system, and announcing the release to the +community. + +## Links to relevant documents + +* [Release Policy](https://www.apache.org/dev/release.html) +* [Release Distribution Policy](https://www.apache.org/dev/release-distribution.html) + +## Why are we doing it? + +We are doing it because this is what the ASF is doing. ASF delivers "Software for the public good" +and the act of releasing software is a key part of that. The process is designed to ensure that the +software is properly vetted and that the community is aware of the release and that the process of +releasing software is transparent, open and secure. Releasing the software is a Legal Act of the +Foundation and it has consequences for the Foundation as software released by the Foundation is +the main way the Foundation interacts with the public and can be hold accountable for the software +it releases. + +## Is it mandatory and what are conditions? + +The process is mandatory for all ASF projects. The process is the same for all projects. This Review Comment: Added. Also split out the "non-negotiables". -- 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-unsubscr...@community.apache.org 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
Re: [PR] Propose "why" folder that we will keep as "advisors" knowledge base [comdev-working-groups]
potiuk commented on code in PR #16: URL: https://github.com/apache/comdev-working-groups/pull/16#discussion_r1501395470 ## wg-advisors/why/why_release_process.md: ## @@ -0,0 +1,30 @@ +# Release process + +## Summary + +ASF project release software following a well defined process involving PMC members voting on release +candidates, publishing the artifacts in the ASF distribution system, and announcing the release to the +community. + +## Links to relevant documents + +* [Release Policy](https://www.apache.org/dev/release.html) +* [Release Distribution Policy](https://www.apache.org/dev/release-distribution.html) + +## Why are we doing it? + +We are doing it because this is what the ASF is doing. ASF delivers "Software for the public good" +and the act of releasing software is a key part of that. The process is designed to ensure that the +software is properly vetted and that the community is aware of the release and that the process of +releasing software is transparent, open and secure. Releasing the software is a Legal Act of the +Foundation and it has consequences for the Foundation as software released by the Foundation is +the main way the Foundation interacts with the public and can be hold accountable for the software +it releases. + +## Is it mandatory and what are conditions? + +The process is mandatory for all ASF projects. The process is the same for all projects. This + +## Are there variations for different projects? + +Not really. The process is the same for all projects. Review Comment: I added a short description describing those variations - with the goal to make it clearer for both "purposes". I hope it's better now. -- 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-unsubscr...@community.apache.org 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
Re: [PR] Add FAQ on how to start (and end) Advisor relationship with PMC [comdev-working-groups]
potiuk commented on PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#issuecomment-1962319343 Ready for the next round of reviews :) -- 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-unsubscr...@community.apache.org 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
Re: [PR] Add FAQ on how to start (and end) Advisor relationship with PMC [comdev-working-groups]
potiuk commented on code in PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#discussion_r1501388602 ## wg-advisors/README.md: ## @@ -102,4 +109,38 @@ the ASF. Trust is transitive - that is, you may not know all members personally, but each member was nominated and elected by people that you, in turn, nominated and elected. +### How to initiate PMC <-> Advisor relationship? + +There is no formal process for this. As an advisor, you may simply +start participating in the project's mailing lists (dev and private) +after introducing yourself and asking if this is fine for you to become +an Advisor. The PMC must be allowed to say "no thank you" without providing any Review Comment: Yeah. I added a small paragraph stating that Advisor is not the "advised PMC" role but a ComDev role. -- 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-unsubscr...@community.apache.org 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
Re: [PR] Add FAQ on how to start (and end) Advisor relationship with PMC [comdev-working-groups]
potiuk commented on code in PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#discussion_r1501388411 ## wg-advisors/README.md: ## @@ -102,4 +109,38 @@ the ASF. Trust is transitive - that is, you may not know all members personally, but each member was nominated and elected by people that you, in turn, nominated and elected. +### How to initiate PMC <-> Advisor relationship? + +There is no formal process for this. As an advisor, you may simply +start participating in the project's mailing lists (dev and private) +after introducing yourself and asking if this is fine for you to become +an Advisor. The PMC must be allowed to say "no thank you" without providing any +reason, and you must respect that decision, and not offer again unless +invited. +You can also be invited by the PMC to become an Advisor. When you become +an Advisor, you should sign yourself up to the list of advisors in this +repository (TODO: how) and describe your experience, skills and what +you can bring as an Advisor (TODO: how). + +The ASF Board can also - during regular Board project review process - to +identify a project that could benefit from an Advisor, and ask the PMC +to consider inviting an Advisor, and cc: dev@community.apache.org mailing +list to make the advisors aware of such a project (which might also initiate +a voluntary Advisor to step up and offer their help). In general the PMC +should be allowed to decide whether they want an Advisor, and who that +Advisor could bem but if any Advisor is interested in a project, they +are encouraged to reach out to the PMC and offer their help. + +In neither case, the Board is appointing an Advisor. The Board is only +asking the PMC to consider inviting an Advisor, and cc: the +dev@community.apache.org mailing list to give the opportunity for +the interested Advisors to step up and volunteer to help the project. + +### How to stop being an Advisor? + +You may stop being an Advisor at any time. You should inform the PMC +that you are stepping down and remove yourself from being advisor of +the PMC (TODO: how) You do not need to provide any reason for stepping down, Review Comment: Clarified that a bit - maybe without the example :). but should be pretty clear now how to do 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-unsubscr...@community.apache.org 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
Re: [PR] Add FAQ on how to start (and end) Advisor relationship with PMC [comdev-working-groups]
potiuk commented on code in PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#discussion_r1501388274 ## wg-advisors/README.md: ## @@ -102,4 +109,38 @@ the ASF. Trust is transitive - that is, you may not know all members personally, but each member was nominated and elected by people that you, in turn, nominated and elected. +### How to initiate PMC <-> Advisor relationship? Review Comment: I added a paragraph clarifying this, I hope it's ok. I also separated out a Board involvement. We've been discussing that with @rbowen a lot on how the Board <-> PMC <-> Advisors triangle relation should look like. I **think** I captured all the aspects of it in this iteration. -- 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-unsubscr...@community.apache.org 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
Re: [PR] Add FAQ on how to start (and end) Advisor relationship with PMC [comdev-working-groups]
potiuk commented on code in PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#discussion_r1501387753 ## wg-advisors/README.md: ## @@ -91,6 +91,13 @@ the indulgence of the PMC, advisor. Do not abuse this relationship. ## FAQ +## How to become an Advisor? + +Just subscribe to dev@community.apache.org and (TODO: how) add yourself Review Comment: Clarified and updated all these points in the new version. -- 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-unsubscr...@community.apache.org 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
Re: [PR] Add FAQ on how to start (and end) Advisor relationship with PMC [comdev-working-groups]
potiuk commented on code in PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#discussion_r1501387636 ## wg-advisors/README.md: ## @@ -102,4 +102,37 @@ the ASF. Trust is transitive - that is, you may not know all members personally, but each member was nominated and elected by people that you, in turn, nominated and elected. +### How to initiate PMC <-> Advisor relationship? +There is no formal process for this. As an advisor, you may simply +start participating in the project's mailing lists (dev and private) +after introducing yourself and asking if this is fine for you to become +an Advisor. The PMC must be allowed to say "no thank you" without providing any +reason, and you must respect that decision, and not offer again unless +invited. + +You can also be invited by the PMC to become an Advisor. When you become +an Advisor, you should sign yourself up to the list of advisors in this +repository (TODO: how) and describe your experience, skills and what +you can bring as an Advisor (TODO: how). + +The ASF Board can also - during regular Board project review process - to +identify a project that could benefit from an Advisor, and ask the PMC +to consider inviting an Advisor, and cc: advisors mailing list (TODO: add the list) +to make the advisors aware of such a project (which might also initiate +a voluntary Advisor to step up and offer their help). In general the PMC +should be allowed to decide whether they want an Advisor, and who that +Advisor could bem but if any Advisor is interested in a project, they +are encouraged to reach out to the PMC and offer their help. + +In neither case, the Board is appointing an Advisor. The Board is only +asking the PMC to consider inviting an Advisor, and cc: advisors mailing +list to make the advisors aware of such a project. + +### How to stop being an Advisor? + +You may stop being an Advisor at any time. You should inform the PMC +that you are stepping down, and then unsubscribe from the private@ list +and devlist. You do not need to provide any reason for stepping down, Review Comment: Added a proposal for such a table. -- 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-unsubscr...@community.apache.org 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
Re: [PR] Add next examples that discourages to contributions [comdev-working-groups]
potiuk commented on code in PR #19: URL: https://github.com/apache/comdev-working-groups/pull/19#discussion_r1501378100 ## wg-advisors/red-flags.md: ## @@ -20,6 +20,9 @@ not a policeman enforcing the rules. * Discussions are happening off-list. * Too much talk is happening on the private list. * Users' questions are going unanswered on the mailing list. +* Users' reported issues are going uncommented and untouched. Review Comment: +1 on all of these. I think one of the big advisors roles might be to help to figure out how to deal with those oat different stages of the priojects (and here I see great opportunity to exchange learnings between projects - and advisors talking between themselves about some ideas to improve. For me - for example it was eye-opening that those do not have to be committers to respond - and finding ways to encourage users/contributors to respond to each other and review each other's code - also as a way to become a committer. -- 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-unsubscr...@community.apache.org 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
Re: [PR] Propose "why" folder that we will keep as "advisors" knowledge base [comdev-working-groups]
potiuk commented on code in PR #16: URL: https://github.com/apache/comdev-working-groups/pull/16#discussion_r1501372589 ## wg-advisors/red-flags.md: ## @@ -15,7 +15,7 @@ not a policeman enforcing the rules. * Has a website external to apache.org * Is missing reports * Is missing release votes -* Has too many release candidates +* Has too many release candidates: [why](why/why_release_process.md) Review Comment: It's an interesting one. This is precisely the kind of discussions that I **hoped** the `why` document will start :) IMHO that one actually deserves a separate "why", as this red flag is (now that you explained it not really about software releases "per se" but about communication and process around the releases, and possibly about involving the community during the relase process and engaging them in testing - whcih is a subtly different thing and possibly deserves another "why". I wil propose something soon :) -- 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-unsubscr...@community.apache.org 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
[PR] Add next examples that discourages to contributions [comdev-working-groups]
slawekjaranowski opened a new pull request, #19: URL: https://github.com/apache/comdev-working-groups/pull/19 I think such issues related to approving PR and finally prepare next release with accepted contributions can have impact for new contributions. -- 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-unsubscr...@community.apache.org 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
Re: [PR] Propose "why" folder that we will keep as "advisors" knowledge base [comdev-working-groups]
potiuk commented on code in PR #16: URL: https://github.com/apache/comdev-working-groups/pull/16#discussion_r1501372091 ## wg-advisors/why/why_release_process.md: ## @@ -0,0 +1,30 @@ +# Release process + +## Summary + +ASF project release software following a well defined process involving PMC members voting on release +candidates, publishing the artifacts in the ASF distribution system, and announcing the release to the +community. + +## Links to relevant documents + +* [Release Policy](https://www.apache.org/dev/release.html) +* [Release Distribution Policy](https://www.apache.org/dev/release-distribution.html) + +## Why are we doing it? + +We are doing it because this is what the ASF is doing. ASF delivers "Software for the public good" +and the act of releasing software is a key part of that. The process is designed to ensure that the +software is properly vetted and that the community is aware of the release and that the process of +releasing software is transparent, open and secure. Releasing the software is a Legal Act of the +Foundation and it has consequences for the Foundation as software released by the Foundation is +the main way the Foundation interacts with the public and can be hold accountable for the software +it releases. + +## Is it mandatory and what are conditions? + +The process is mandatory for all ASF projects. The process is the same for all projects. This + +## Are there variations for different projects? + +Not really. The process is the same for all projects. Review Comment: Yes. Worth mentioning the variations. But I think going into oo many details is not a good idea. It will be of coure always an art how "deep" we should describe it here, but the rule of thumb I think such document should not go into details where the linked document cover them, it should be a one-pager max and it should mostly focus on the most important "why's" - providing a very broad context that is otherwise distiributed among several documents, heads of people, discussions etc. etc. I think it serves two purposes: * for the advisor - so that they can always come back here and immediately see - hey, why actually we are doing it ? - a... here it is - and go into details if needed * for the advised ones - to be assured that what we are advising them is not a "cargo cult" and tha we have very good reason that you can read about it here why we are doing it - without having to go through all the piles of documents and discussions or asking others. I will expand it a little bit soon. ## wg-advisors/why/why_release_process.md: ## @@ -0,0 +1,30 @@ +# Release process + +## Summary + +ASF project release software following a well defined process involving PMC members voting on release +candidates, publishing the artifacts in the ASF distribution system, and announcing the release to the +community. + +## Links to relevant documents + +* [Release Policy](https://www.apache.org/dev/release.html) +* [Release Distribution Policy](https://www.apache.org/dev/release-distribution.html) + +## Why are we doing it? + +We are doing it because this is what the ASF is doing. ASF delivers "Software for the public good" +and the act of releasing software is a key part of that. The process is designed to ensure that the +software is properly vetted and that the community is aware of the release and that the process of +releasing software is transparent, open and secure. Releasing the software is a Legal Act of the +Foundation and it has consequences for the Foundation as software released by the Foundation is +the main way the Foundation interacts with the public and can be hold accountable for the software +it releases. + +## Is it mandatory and what are conditions? + +The process is mandatory for all ASF projects. The process is the same for all projects. This Review Comment: Yep. I will add 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-unsubscr...@community.apache.org 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
Re: [PR] Propose "why" folder that we will keep as "advisors" knowledge base [comdev-working-groups]
potiuk commented on code in PR #16: URL: https://github.com/apache/comdev-working-groups/pull/16#discussion_r1501371159 ## wg-advisors/why/why_release_process.md: ## @@ -0,0 +1,30 @@ +# Release process + +## Summary + +ASF project release software following a well defined process involving PMC members voting on release +candidates, publishing the artifacts in the ASF distribution system, and announcing the release to the +community. + +## Links to relevant documents + +* [Release Policy](https://www.apache.org/dev/release.html) +* [Release Distribution Policy](https://www.apache.org/dev/release-distribution.html) + +## Why are we doing it? + +We are doing it because this is what the ASF is doing. ASF delivers "Software for the public good" +and the act of releasing software is a key part of that. The process is designed to ensure that the +software is properly vetted and that the community is aware of the release and that the process of +releasing software is transparent, open and secure. Releasing the software is a Legal Act of the +Foundation and it has consequences for the Foundation as software released by the Foundation is +the main way the Foundation interacts with the public and can be hold accountable for the software +it releases. Review Comment: Good point. -- 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-unsubscr...@community.apache.org 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
Re: [PR] Add FAQ on how to start (and end) Advisor relationship with PMC [comdev-working-groups]
potiuk commented on code in PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#discussion_r1501371004 ## wg-advisors/README.md: ## @@ -102,4 +109,38 @@ the ASF. Trust is transitive - that is, you may not know all members personally, but each member was nominated and elected by people that you, in turn, nominated and elected. +### How to initiate PMC <-> Advisor relationship? Review Comment: Yep. That's how I see it as well (and I think previous paragraphs describe it well) - that this is a group of peer ASF members that help other PMCs and gathers information/exchanges knowledge how various PMC are interpreting and more importantly "executing" their vision of "Apache Way" - and advise on making it as common as possible where needed **with** the open mind and accepting the fact that there are variations among projects. -- 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-unsubscr...@community.apache.org 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
Re: [PR] Add FAQ on how to start (and end) Advisor relationship with PMC [comdev-working-groups]
potiuk commented on code in PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#discussion_r1501370655 ## wg-advisors/README.md: ## @@ -91,6 +91,13 @@ the indulgence of the PMC, advisor. Do not abuse this relationship. ## FAQ +## How to become an Advisor? + +Just subscribe to dev@community.apache.org and (TODO: how) add yourself Review Comment: I agree, I think it should be enough to have a member to open a PR with this information here - we will keep a list/table of advisors with information. It's a public pleace - not guarded by membership access (which is good) so no email addresses just maybe name, github id, apache id, and short paragraph about the Adviso should be enough, -- 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-unsubscr...@community.apache.org 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
