Self-request as a PMC member for COMDEV
Hi, Repost this thread and cc Swapnil for more visibility. I'm reviewing and patching related repos now and noticed that this request is pending. Since active committers are reviewing patches, this is not in a rush. But I'm afraid that this email gets overwhelmed. Rich Bowen wrote: > Meanwhile, as per ComDev policy, your request to be a ComDev PMC member is > approved. Swapnil, can you pull the lever, please. My profile for reference https://whimsy.apache.org/roster/committer/tison. Best, tison. Rich Bowen 于2024年2月12日周一 23:23写道： > > On Feb 12, 2024, at 10:13 AM, tison wrote: > > > > According to the INFRA ticket [1], we'd better create the > > apache/community GitHub repo first. > > > > I'm glad to execute the self-serve command but I'm yet to be a COMDEV > > PMC member. I remember that in another thread, it's said that an > > Apache Member can self-request to be a PMC member, so: > > > > * If any COMDEV PMC member can create the GitHub repo on self-serve > > platform [2]; > > * If it's possible, I'd like to self-request to be a PMC member and do > > the set up by myself. > > > Done. > > Meanwhile, as per ComDev policy, your request to be a ComDev PMC member is > approved. Swapnil, can you pull the lever, please. > > Thanks. - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [jira] [Commented] (COMDEV-543) Sharpeners use cases
Hi, I added the list because I had it at hand so it could be used to improve the existing document; if I had time at the moment, I would have written it in the style of the existing document, but sadly, I do not at the moment. Re “too many release candidates”, one thing I have observed is that sometimes people rush through checking RCs or stop after a single issue is found and don’t do a full check; this can lead to unnecessary RCs being created. Encouraging people to come up with a checklist and follow all steps when reviewing RCs is something that can help a community. Kind Regards, Justin - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [jira] [Commented] (COMDEV-543) Sharpeners use cases
On 2/14/24 21:33, Rich Bowen wrote: On Feb 14, 2024, at 2:46 PM, Phil Steitz wrote: I guess I am too late here, but fwiw, I agree strongly with Rich's comment. I would much rather see the checklisty stuff incorporated into either the use cases or the main doc somewhere and not presented as "things 'we' are looking for". I do not like at all the statement in the intro to the new doc, "However, having an idea of what red flags we're looking for in a project can be a helpful way to start looking for places to mentor, and sharpen, our projects." You are definitely not too late here, and I would certainly hope that nobody feels that I have any more say than anybody else in what we do here. I instigated. I am not the leader. Please own the document, and edit it in whatever way you see fit. That is absolutely the wrong message to give. Who is "we"? This kind of thing sets the tone of the working group as some kind of external policing / inspecting function. That will not help. Yes, that is indeed my concern. My two cents: Put some emphasis on this being about building and strengthening communities, rather than compliance. What *will help* is people showing up, listening and coming up with useful suggestions for how to solve problems that communities are facing. In some cases, that may actually mean helping them explain why their way of doing things is perfectly fine. I was shocked, for example, by "too many release candidates" on the list of "red flags." That is ridiculous, IMO, and nobody's business but the community. A sharpener certainly might help share experience about how other projects have handled packaging, testing and deployment issues, but just jumping in because a few releases have burned through a few RC numbers makes zero sense. Please do take that document as a 0.001 version, and edit/update/delete it as you see fit. We are in the “what if” phase here. - 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: [jira] [Commented] (COMDEV-543) Sharpeners use cases
On Feb 14, 2024, at 2:46 PM, Phil Steitz wrote: > > I guess I am too late here, but fwiw, I agree strongly with Rich's > comment. I would much rather see the checklisty stuff incorporated into > either the use cases or the main doc somewhere and not presented as "things > 'we' are looking for". I do not like at all the statement in the intro to > the new doc, > "However, having an idea of what red flags we're looking for > in a project can be a helpful way to start looking for places to mentor, > and sharpen, our projects." You are definitely not too late here, and I would certainly hope that nobody feels that I have any more say than anybody else in what we do here. I instigated. I am not the leader. Please own the document, and edit it in whatever way you see fit. > > That is absolutely the wrong message to give. Who is "we"? This kind of > thing sets the tone of the working group as some kind of external policing > / inspecting function. That will not help. > Yes, that is indeed my concern. > What *will help* is people showing up, listening and coming up with useful > suggestions for how to solve problems that communities are facing. In some > cases, that may actually mean helping them explain why their way of doing > things is perfectly fine. I was shocked, for example, by "too many release > candidates" on the list of "red flags." That is ridiculous, IMO, and > nobody's business but the community. A sharpener certainly might help > share experience about how other projects have handled packaging, testing > and deployment issues, but just jumping in because a few releases have > burned through a few RC numbers makes zero sense. Please do take that document as a 0.001 version, and edit/update/delete it as you see fit. We are in the “what if” phase here. - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [jira] [Commented] (COMDEV-543) Sharpeners use cases
To be clear Justin’s red flags are here: https://github.com/apache/comdev-working-groups/blob/main/wg-sharpeners/red-flags.md > On Feb 14, 2024, at 11:46 AM, Phil Steitz wrote: > > I guess I am too late here, but fwiw, I agree strongly with Rich's > comment. I would much rather see the checklisty stuff incorporated into > either the use cases or the main doc somewhere and not presented as "things > 'we' are looking for". I do not like at all the statement in the intro to > the new doc, I agree with Phil and would also add that this list of red flags is repetitive and is not a definitive list. It completely lacks nuance and you could reasonably bike shed what color of flag each of Justin’s signals deserves. > "However, having an idea of what red flags we're looking for > in a project can be a helpful way to start looking for places to mentor, > and sharpen, our projects." > > That is absolutely the wrong message to give. Who is "we"? This kind of > thing sets the tone of the working group as some kind of external policing > / inspecting function. That will not help. I’ve seen the impact of this list being to provide many disjoint concerns instead of carefully providing a list of concerns and assuming good intention from the PMC about one or more Members concerns. A scattershot approach is not respectful of the PMC. > What *will help* is people showing up, listening and coming up with useful > suggestions for how to solve problems that communities are facing. In some > cases, that may actually mean helping them explain why their way of doing > things is perfectly fine. I was shocked, for example, by "too many release > candidates" on the list of "red flags." That is ridiculous, IMO, and > nobody's business but the community. My reaction as well. There can be many more RCs for x.y.0 than for x.y.4. Regards, Dave > A sharpener certainly might help > share experience about how other projects have handled packaging, testing > and deployment issues, but just jumping in because a few releases have > burned through a few RC numbers makes zero sense. > > Phil > > > > On Wed, Feb 14, 2024 at 7:39 AM Rich Bowen (Jira) wrote: > >> >>[ >> https://issues.apache.org/jira/browse/COMDEV-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17817400#comment-17817400 >> ] >> >> Rich Bowen commented on COMDEV-543: >> --- >> >> Added to doc in https://github.com/apache/comdev-working-groups/pull/2 >> >>> Sharpeners use cases >>> >>> >>>Key: COMDEV-543 >>>URL: https://issues.apache.org/jira/browse/COMDEV-543 >>>Project: Community Development >>> Issue Type: Improvement >>> Components: Comdev >>> Reporter: Phil Steitz >>> Priority: Minor >>>Attachments: use-cases.md >>> >>> >>> Brain dump of ideas for sharpeners use cases >> >> >> >> -- >> This message was sent by Atlassian Jira >> (v8.20.10#820010) >> >> - >> 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: [jira] [Commented] (COMDEV-543) Sharpeners use cases
I guess I am too late here, but fwiw, I agree strongly with Rich's comment. I would much rather see the checklisty stuff incorporated into either the use cases or the main doc somewhere and not presented as "things 'we' are looking for". I do not like at all the statement in the intro to the new doc, "However, having an idea of what red flags we're looking for in a project can be a helpful way to start looking for places to mentor, and sharpen, our projects." That is absolutely the wrong message to give. Who is "we"? This kind of thing sets the tone of the working group as some kind of external policing / inspecting function. That will not help. What *will help* is people showing up, listening and coming up with useful suggestions for how to solve problems that communities are facing. In some cases, that may actually mean helping them explain why their way of doing things is perfectly fine. I was shocked, for example, by "too many release candidates" on the list of "red flags." That is ridiculous, IMO, and nobody's business but the community. A sharpener certainly might help share experience about how other projects have handled packaging, testing and deployment issues, but just jumping in because a few releases have burned through a few RC numbers makes zero sense. Phil On Wed, Feb 14, 2024 at 7:39 AM Rich Bowen (Jira) wrote: > > [ > https://issues.apache.org/jira/browse/COMDEV-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17817400#comment-17817400 > ] > > Rich Bowen commented on COMDEV-543: > --- > > Added to doc in https://github.com/apache/comdev-working-groups/pull/2 > > > Sharpeners use cases > > > > > > Key: COMDEV-543 > > URL: https://issues.apache.org/jira/browse/COMDEV-543 > > Project: Community Development > > Issue Type: Improvement > > Components: Comdev > >Reporter: Phil Steitz > >Priority: Minor > > Attachments: use-cases.md > > > > > > Brain dump of ideas for sharpeners use cases > > > > -- > This message was sent by Atlassian Jira > (v8.20.10#820010) > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
Re: [PR] Add .asf.yaml [comdev-working-groups]
rbowen merged PR #3: URL: https://github.com/apache/comdev-working-groups/pull/3 -- 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] Update .asf.yaml (comdev-site)
tisonkun opened a new pull request, #158: URL: https://github.com/apache/comdev-site/pull/158 I remember the default email title has been changed months ago. Also for `jira_options` config. -- 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 .asf.yaml [comdev-working-groups]
tisonkun opened a new pull request, #3: URL: https://github.com/apache/comdev-working-groups/pull/3 Mainly for the `jira_options` that I hope it works well to link with JIRA tickets. -- 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
[jira] [Commented] (COMDEV-543) Sharpeners use cases
[ https://issues.apache.org/jira/browse/COMDEV-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17817400#comment-17817400 ] Rich Bowen commented on COMDEV-543: --- Added to doc in https://github.com/apache/comdev-working-groups/pull/2 > Sharpeners use cases > > > Key: COMDEV-543 > URL: https://issues.apache.org/jira/browse/COMDEV-543 > Project: Community Development > Issue Type: Improvement > Components: Comdev >Reporter: Phil Steitz >Priority: Minor > Attachments: use-cases.md > > > Brain dump of ideas for sharpeners use cases -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [PR] Adds the list of red flags contributed by Justin. [comdev-working-groups]
rbowen merged PR #2: URL: https://github.com/apache/comdev-working-groups/pull/2 -- 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] Adds the list of red flags contributed by Justin. [comdev-working-groups]
rbowen opened a new pull request, #2: URL: https://github.com/apache/comdev-working-groups/pull/2 Adds list of red flags contributed by Justin in https://issues.apache.org/jira/browse/COMDEV-543 We should work towards 1) categorizing these and 2) linking from each to constructive ways to address the problem. -- 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
[jira] [Commented] (COMDEV-543) Sharpeners use cases
[ https://issues.apache.org/jira/browse/COMDEV-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17817389#comment-17817389 ] Justin Mclean commented on COMDEV-543: -- I agree guiding projects on what to do in these situations is the more difficult part, but this was the list I had at hand that might help form the document you have started on, particularly the couple of gaps it has. > Sharpeners use cases > > > Key: COMDEV-543 > URL: https://issues.apache.org/jira/browse/COMDEV-543 > Project: Community Development > Issue Type: Improvement > Components: Comdev >Reporter: Phil Steitz >Priority: Minor > Attachments: use-cases.md > > > Brain dump of ideas for sharpeners use cases -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-543) Sharpeners use cases
[ https://issues.apache.org/jira/browse/COMDEV-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17817371#comment-17817371 ] Rich Bowen commented on COMDEV-543: --- These are all good, but I am *very* concerned that we would be, or be perceived as, a bunch of heavies showing up to Enforce The Rules. We should endeavor to ensure that any list of Red Flags is offset by a list of best practice and good advice. Because scolding people for breaking the rules is *much* easier than giving good advice, and I am concerned that people wishing to get involved will see that as an easy way in, and thus poison the well for the program in general. > Sharpeners use cases > > > Key: COMDEV-543 > URL: https://issues.apache.org/jira/browse/COMDEV-543 > Project: Community Development > Issue Type: Improvement > Components: Comdev >Reporter: Phil Steitz >Priority: Minor > Attachments: use-cases.md > > > Brain dump of ideas for sharpeners use cases -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
