Re: ASF on Redbubble
All, It isn't looking good. Redbubble have denied the suspension appeal and still haven't explained why the account has been suspended. I've asked but I am not sure I am going to get a response. I think we need to start looking for alternative services. Suggestions welcome. I haven't informed the PMCs using Redbubble yet. I'll do that if my request for an explanation of why the account was suspended gets nowhere. Mark On 21/02/2024 15:31, Mark Thomas wrote: On 21/02/2024 14:44, Richard Zowalla wrote: Hey Mark, I am unable to find the ComDev store on Redbubble at all. My previous orders from ComDev are gone (or I ordered from the wrong people in the recent years). So if you have a link for me, would be great :) Sigh. Redbubble have suspended our account. I'll see what I can do to fix that. Mark Best Richard Am Mittwoch, dem 21.02.2024 um 08:46 + schrieb Mark Thomas: On 20/02/2024 21:55, Jeff Zemerick wrote: Hi all, Hopefully this list is the best place for this. I have ordered several OpenNLP shirts in the past from Redbubble. I did a recent order for OpenNLP, Airflow, Solr, and NiFi shirts (can never have enough, right?) and RedBubble canceled the OpenNLP and Airflow ones due to Redbubble’s IP/Publicity Rights Policy [1]. I only see Solr in the ComDev store. It may be the case that RedBubble is (finally) taking steps against sellers that sell items using logos they don't have the rights to. Last time I went looking there were a LOT of items with logos for commercial software. You might have got caught up in that. I just wanted to bring it to the ASF's attention. Is Redbubble still the place to get ASF swag? It is the place ComDev maintains although some projects may have set up alternatives. The simplest solution may be to get those PMCs to request that the relevant logos are added to the ComDev store. It just needs an email from someone on the PMC to this list confirming that the PMC would like the logo added. Mark - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Query about the GitHub statistics for Lucene
Hi, I have a query about the GitHub statistics that are being generated the Lucene project [1]. They appear to be not accurate, or at least something is not quite right with them. For example, I (as well as many other project members) opened several issues and PRs in Jan and Feb of 2024, but the graphs show no activity [2]. Can someone please take a look at why this might be the case, or redirect me to the right place where I can further understand how to resolve this. Thanks, -Chris. (Lucene PMC Chair) [1] https://reporter.apache.org/wizard/statistics?lucene#commitactivity [2] https://reporter.apache.org/wizard/statistics?lucene#githubpractivity - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [PR] Prototype "volunteers" page (comdev-site)
bdelacretaz commented on PR #146: URL: https://github.com/apache/comdev-site/pull/146#issuecomment-1961010970 I'm planning to merge this early next week unless someone objects. -- 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] Prototype "volunteers" page (comdev-site)
sebbASF commented on PR #146: URL: https://github.com/apache/comdev-site/pull/146#issuecomment-1961033402 It's very difficult to review the PR, as it appears to have a lot of unrelated changes. It would be better to make separate changes in separate commits, otherwise the history is very difficult to follow. -- 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] Prototype "volunteers" page (comdev-site)
bdelacretaz commented on PR #146: URL: https://github.com/apache/comdev-site/pull/146#issuecomment-1961058802 > it appears to have a lot of unrelated changes.. yes, sorry I messed up after rebasing, fixed 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] Prototype "volunteers" page (comdev-site)
sebbASF commented on PR #146: URL: https://github.com/apache/comdev-site/pull/146#issuecomment-1961091696 It's better, but there are still some changes that appear to be unrelated -- 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] Prototype "volunteers" page (comdev-site)
I've not had a chance to review carefully because I'm traveling but I love the idea and am +1 to the patch in concept. Since it is replacing something that doesn't work, I see no risk in moving forward with this. Thanks! Rich On Fri, Feb 23, 2024, 03:44 bdelacretaz (via GitHub) wrote: > > bdelacretaz commented on PR #146: > URL: > https://github.com/apache/comdev-site/pull/146#issuecomment-1961010970 > >I'm planning to merge this early next week unless someone objects. > > > -- > 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: Query about the GitHub statistics for Lucene
The second half of your question: https://reporter.apache.org/about.html Unfortunately the tool is not actively maintained at the moment. We could certainly use some more eyes and fingers on it. Rich On Fri, Feb 23, 2024, 03:20 Chris Hegarty wrote: > Hi, > > I have a query about the GitHub statistics that are being generated the > Lucene project [1]. They appear to be not accurate, or at least something > is not quite right with them. > > For example, I (as well as many other project members) opened several > issues and PRs in Jan and Feb of 2024, but the graphs show no activity [2]. > > Can someone please take a look at why this might be the case, or redirect > me to the right place where I can further understand how to resolve this. > > Thanks, > -Chris. (Lucene PMC Chair) > > [1] https://reporter.apache.org/wizard/statistics?lucene#commitactivity > [2] https://reporter.apache.org/wizard/statistics?lucene#githubpractivity > > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
[PR] Add Jarek as interested in membership [comdev-working-groups]
potiuk opened a new pull request, #12: URL: https://github.com/apache/comdev-working-groups/pull/12 (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: 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] Replace NameTBD with Advisor [comdev-working-groups]
potiuk opened a new pull request, #13: URL: https://github.com/apache/comdev-working-groups/pull/13 Seems that Advisor is the result of all the discussions that happened - this is one place where it has not been updated. I also removed the section about "Why the name" - because Advisor does not need an explanation (which on its own is a sign that this is a better name) -- 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] Ad Security issues handling as an important use case [comdev-working-groups]
potiuk opened a new pull request, #14: URL: https://github.com/apache/comdev-working-groups/pull/14 The security issue handling is an important aspects and one that all projects should have very good policies and processes about, so I think we shoudl add it here. -- 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] Exclude .idea project to not accidentally commit .idea directory [comdev-working-groups]
potiuk opened a new pull request, #15: URL: https://github.com/apache/comdev-working-groups/pull/15 Many of us use different IDEs. I use VIm and IntelliJ interchangeably, for editing markdown files I find IntelliJ rather helpful with preview and Intellij creates .idea folder which can be accidentally added and committed to the repository. Excluding .idea in .gitignore will prevent it from happening ` -- 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 Jarek as interested in membership [comdev-working-groups]
rbowen merged PR #12: URL: https://github.com/apache/comdev-working-groups/pull/12 -- 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] Replace NameTBD with Advisor [comdev-working-groups]
rbowen merged PR #13: URL: https://github.com/apache/comdev-working-groups/pull/13 -- 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] Ad Security issues handling as an important use case [comdev-working-groups]
rbowen commented on PR #14: URL: https://github.com/apache/comdev-working-groups/pull/14#issuecomment-1961883753 I'm not sure I agree. We have a Security committee, and they are the correct people to handled security issues. I'm not at all sure they want passionate amateurs trying to do their job. I would want to have Mark, and others on that committee, weigh in on whether they is actually helpful. -- 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] Propose "why" folder that we will keep as "advisors" knowledge base [comdev-working-groups]
potiuk opened a new pull request, #16: URL: https://github.com/apache/comdev-working-groups/pull/16 I would like to propose the "why" folder, where we will keep a (very) short summary about some of the rules and policies that we will be - as Advisors - discussing with the projects we will advise. I think we need something like that - also as a place where we - advisors - will be able to update and exchange our understanding on why there are certain rules and policies. Also to discuss future variations and changes to those rules, possibly resulting from interactions with multiple PMCs when we will learn from them how they are applying certain rules and policies in their environment. I gave an example of how I see such "why" captured information could look like - starting with the most familiar (for me) release process and I am curious what others think about 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] Ad Security issues handling as an important use case [comdev-working-groups]
potiuk commented on PR #14: URL: https://github.com/apache/comdev-working-groups/pull/14#issuecomment-1961924471 > I'm not sure I agree. We have a Security committee, and they are the correct people to handled security issues. I'm not at all sure they want passionate amateurs trying to do their job. I would want to have Mark, and others on that committee, weigh in on whether they is actually helpful. Courious about your opinion @raboof @iamamoose @pjfanning -- 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 bi-directional approach for Advisors [comdev-working-groups]
potiuk opened a new pull request, #17: URL: https://github.com/apache/comdev-working-groups/pull/17 This is something I wanted to proposed from the beginnig of seing the Sharpenes apporach. I believe the original approach where Advisors just advise the projects their join - and the flow is in one direction, they should treat the opportunity of interacting with different PMCs as an opportunity to learn from the projects and discuss with other advisors whether the current incarnation of the rules we have is applicable in practice and whether maybe they should be adjusted and improved or maybe they should be updated to be better applicable to different projects - coming from various culturs, backgrounds, projects with different sizes, with different stakeholder engagement. Having the relation works in both directions is an opportunity to learn and adapt, and to exchange findings between the Advisors that might lead to better adaptability and better common understanding of the rules and policies we have, and more participatory role of both Advisors and PMCs that might get beter chance to shape the way how Foundation works on an ongoing way, as well as to give the board an opportunity to listen to the voices and better understand the varuious needs of various 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] Exclude .idea project to not accidentally commit .idea directory [comdev-working-groups]
rbowen merged PR #15: URL: https://github.com/apache/comdev-working-groups/pull/15 -- 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 bi-directional approach for Advisors [comdev-working-groups]
rbowen merged PR #17: URL: https://github.com/apache/comdev-working-groups/pull/17 -- 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 FAQ on how to start (and end) Advisor relationship with PMC [comdev-working-groups]
potiuk opened a new pull request, #18: URL: https://github.com/apache/comdev-working-groups/pull/18 This PR adds quite a bit of clarity on how the process of initiating (and ending) the relationship between the Advispr and PMC is expected to happen. It's more on a FAQ rather than rules, and it describes the usual way it can happen, with focus put on the voluntary nature of being an Advisor and clarifies the role of Board in the process. -- 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]
rbowen commented on code in PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#discussion_r1501152118 ## 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) Review Comment: I am not persuaded that we need a new mailing list for this. I see this WG as one of the core functionalities of the ComDev PMC, and moving that discussion off to another list seems a way to remove it from view, with no particular benefit. I'd ask that we keep it in the main list until such time that people actually complain that there's too much noise, since I think we can all learn from these discussions. -- 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]
rbowen commented on code in PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#discussion_r1501153319 ## 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: Any member can be subscribed to any project's dev@ or private@ list without giving justification for doing so. That's actually in the bylaws. We cannot mandate that a member unsub from these lists. -- 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_r1501153331 ## 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) Review Comment: Fine with that as well. I think having it all on comdev list is great. -- 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_r1501154060 ## 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: Good point. I think maybe we should work out a way to just have a list of people who are advisors for PMC? Maybe in this repository ? -- 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-1961978300 > Interesting idea. Yeah, I like this. It also gives us something to point to when projects push back, in a "this isn't personal, it's just the way things are" kind of way. Especially in conjunction with the notion that we're also there to learn, and possibly improve the process/rules. 100% agree. There is a huge value in something being publicly stated in "semi-official" way. Just writing things down and pointing to it as a link is enough to stop treating things as personal opinion but something that is "commonly understood". Also when we connect it with the gorup of advisors who are mostly a "group ASF members who actually care enough to spend their personal time on helping other projects" has additional benefit that it is not seen as something that is "top-> bottom" but more like "group of peers agreed this is how it is". -- 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_r1501173776 ## 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) Review Comment: I think I addressed 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_r1501174824 ## 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: Addressed it. Left TODO: on how to add youself as an advisor, but left the unsubsribe out. ## 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: Addressed it. Left TODO: on how to add youself as an advisor, but left the unsubscribe out. -- 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]
rbowen commented on code in PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#discussion_r1501186272 ## 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: > Good point. I think maybe we should work out a way to just have a list of people who are advisors for PMC? Maybe in this repository ? Yeah, I like the idea of tracking this -- not least because it might discourage multiple Advisors "ganging up" on one 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. 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_r1501200329 ## 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: > Yeah, I like the idea of tracking this -- not least because it might discourage multiple Advisors "ganging up" on one project. Yep. We just need to figure out the most light-weight way of tracking it and keeping it up-to-date. It would be useful on many levels to keep track of who is an advisor to which 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. 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]
rbowen commented on code in PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#discussion_r1501228575 ## 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: Perhaps, in the spirit of Minimal Viable Solution, a simple alpha-sorted list of projects, and the ApacheID of their Advisor, right here in this repo. -- 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_r1501285983 ## 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: Something like that - absolutely. Nothong more complex. -- 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 Security issues handling as an important use case [comdev-working-groups]
justinmclean commented on PR #14: URL: https://github.com/apache/comdev-working-groups/pull/14#issuecomment-1962180930 Projects often need to be pointed in the right direction for the correct process when a security issue arises. I can see an Advisor doing that. -- 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]
justinmclean commented on code in PR #16: URL: https://github.com/apache/comdev-working-groups/pull/16#discussion_r1501296133 ## 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: I'd note it also gives the PMC and release manager some legal protection. -- 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]
justinmclean commented on code in PR #16: URL: https://github.com/apache/comdev-working-groups/pull/16#discussion_r1501297317 ## 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: There is some variation: a few projects use super majority voting, some have voters sign releases, the length of time a vote is open often varies, some projects consider the RM as an implicit +1, not all projects announce releases, and there are probably a few things I've forgotten about. -- 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]
On Sat, 24 Feb 2024 at 00:53, justinmclean (via GitHub) wrote: > > > justinmclean commented on code in PR #16: > URL: > https://github.com/apache/comdev-working-groups/pull/16#discussion_r1501297317 > > > ## > 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: >There is some variation: a few projects use super majority voting, some > have voters sign releases, the length of time a vote is open often varies, > some projects consider the RM as an implicit +1, not all projects announce > releases, and there are probably a few things I've forgotten about. An implicit +1 from the RM is not something that should be encouraged. Also the minimum length of time for voting is 72 hours, except for urgent security-related 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 > - 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]
HI, > An implicit +1 from the RM is not something that should be encouraged. I agree, but some projects still do it. > Also the minimum length of time for voting is 72 hours, except for > urgent security-related releases. A few projects have longer times for voting, so they still fit within the 72 minimum. Kind Regards, Justin
Re: [PR] Propose "why" folder that we will keep as "advisors" knowledge base [comdev-working-groups]
tisonkun commented on code in PR #16: URL: https://github.com/apache/comdev-working-groups/pull/16#discussion_r1501325488 ## 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: > some projects consider the RM as an implicit +1 Here is a patch to explain no RM implicit +1 https://github.com/apache/www-site/pull/338. -- 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]
tisonkun commented on code in PR #16: URL: https://github.com/apache/comdev-working-groups/pull/16#discussion_r1501325628 ## 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: ```suggestion The process is mandatory for all ASF projects. The process is the same for all projects. ``` Typo. Also, I agree with Justin's comment that the process can be subtly different. Or you can elaborate a bit what "the same" part is that is mandatory. -- 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]
tisonkun commented on code in PR #16: URL: https://github.com/apache/comdev-working-groups/pull/16#discussion_r1501326585 ## 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: The answer is not included in the new file. Do you expect elaborate it in the new file later, or we should create a dedicated answer. I remember that the original purpose of this "red flag" was to encourage RMs to waiting for more inputs instead of eagerly cancelling release candidates which increases the release burden. -- 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]
tisonkun commented on code in PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#discussion_r1501327362 ## 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: > how As stated below that "An Advisor must be an ASF member", I think that add oneself to the list can be done with a lazy consensus. Or if we're confident that the advisor WG is active enough, 3 +1 from the WG. I personally trust a member and their "describe your experience, skill and interests. Introduce yourself as a prospect Advisor" would show enough motivation. -- 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]
tisonkun commented on code in PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#discussion_r1501327566 ## 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: According to the original mailing list thread of this WG, it doesn't aim at creating a new office in the foundation. So I assume that there is no special relationship between the Advisor with other office at least at the "advising" level. Instead, the advisor WG working on the guidelines and generating knowledge. Every advisor WG member or anyone, as individuals, applying this guidelines to advice 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]
tisonkun commented on code in PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#discussion_r1501328880 ## 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: > how A NOTICE or request on the mailing list (dev@ or private@community should be OK IMO). Something like https://lists.apache.org/thread/1k116oyo1fc4kk3vdqg6hfz0x1bpxn21. -- 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]
tisonkun commented on code in PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#discussion_r1501328950 ## 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) Review Comment: ```suggestion start participating in the project's mailing lists (dev and/or private) ``` nit -- 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]
tisonkun commented on code in PR #18: URL: https://github.com/apache/comdev-working-groups/pull/18#discussion_r1501329155 ## 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: > become an Advisor I don't think we'd establish a formal Advisor role in the project. But any advisor comes with a certain issue/suggestion, or shout-out (of course) for the 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. 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
