Re: Requests for comdev membership
> On Sep 3, 2023, at 04:36, Shane Curcuru wrote: > > Craig L Russell wrote on 9/1/23 2:28 PM: >> I recently sent a PR for the site and nothing happened. No one reviewed. No >> one commented. > > Link? There's only one open PR (not from you), and the most recent closed PR > you submitted was closed quickly by sebb. > > https://github.com/apache/comdev-site/pull/124 > > Just trying to ensure we're all talking about the same repo. Yes, the repo I was referring to is comdev-site. I'm sorry I mischaracterized the months-long process of updating the page to improve the process of adding new committers. > > The README.md does provide fairly decent description about how to make > changes, although we don't define CTR or RTC or other policies. I'd opt for > CTR since getting volunteers interested is more important than avoiding > potential mistakes. > > Personally, I'd like to see us adopt a modified Incubator concept, where any > Apache committer can simply asked to be made a ComDev committer, and the PMC > will turn on commit for ComDev repos too. That should be sufficient for most > cases, without needing to special case our repos for all committers ever. This sounds like it is worth trying. Craig > > -- > - Shane > ComDev PMC > The Apache Software Foundation > > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > Craig L Russell c...@apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Requests for comdev membership
Craig L Russell wrote on 9/1/23 2:28 PM: I recently sent a PR for the site and nothing happened. No one reviewed. No one commented. Link? There's only one open PR (not from you), and the most recent closed PR you submitted was closed quickly by sebb. https://github.com/apache/comdev-site/pull/124 Just trying to ensure we're all talking about the same repo. The README.md does provide fairly decent description about how to make changes, although we don't define CTR or RTC or other policies. I'd opt for CTR since getting volunteers interested is more important than avoiding potential mistakes. Personally, I'd like to see us adopt a modified Incubator concept, where any Apache committer can simply asked to be made a ComDev committer, and the PMC will turn on commit for ComDev repos too. That should be sufficient for most cases, without needing to special case our repos for all committers ever. -- - Shane ComDev PMC The Apache Software Foundation - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Requests for comdev membership
I just checked the repo, there aren't any open PRs from you Craig [1] or I am checking the wrong place maybe, though I don't have the c-bit on comdev, but would have definitely tried to review. I tried to check what policy is followed with comdev but couldn't find any reference to that. If there is a lack of volunteers who can review the code, the project can have CTR [2] if not already. Though I do agree the content of the website is pretty generic and centric to the entire Apache community and a lot of people have insights around that & they can contribute to that or help with that Letting all apache committers access to that repo might be a solution but that looks like taking away a part from the comdev, and mostly the folks on the PMC won't agree and is fair enough too, they did the hard work maintaining that and developing the content, they might not want anybody else who they don't trust to change or modify that -Ayush [1] https://github.com/apache/comdev-site/pulls [2] https://www.apache.org/foundation/glossary#CommitThenReview On Fri, 1 Sept 2023 at 23:59, Craig L Russell wrote: > > I recently sent a PR for the site and nothing happened. No one reviewed. No > one commented. > > Just one data point but... Is there a process for review of PRs? > > Craig > > On 2023/08/17 03:50:04 Rich Bowen wrote: > > It seems to me that the recent requests for comdev membership are symptoms > > of broken process. I understand that this is necessary to get things done, > > but the fact that someone has to be a comdev member in order to edit the > > website is broken. I am not sure what the way forward is here, but if > > someone has some insight into how things work, and can suggest a more > > reasonable way around this than making contractors comdev members, I would > > be much appreciative > > > > Rich > > > > - > 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: Requests for comdev membership
I recently sent a PR for the site and nothing happened. No one reviewed. No one commented. Just one data point but... Is there a process for review of PRs? Craig On 2023/08/17 03:50:04 Rich Bowen wrote: > It seems to me that the recent requests for comdev membership are symptoms > of broken process. I understand that this is necessary to get things done, > but the fact that someone has to be a comdev member in order to edit the > website is broken. I am not sure what the way forward is here, but if > someone has some insight into how things work, and can suggest a more > reasonable way around this than making contractors comdev members, I would > be much appreciative > > Rich > - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Requests for comdev membership
I think it is easier than you think. 1. People who want to make changes submit PRs (if it’s svn does Comdev have a process?) 2. Like any PMC, members and committers approve and merge PRs. What’s the problem? Not enough PR review? Yurking and all the best, Dave Sent from my iPhone > On Aug 16, 2023, at 8:50 PM, Rich Bowen wrote: > > It seems to me that the recent requests for comdev membership are symptoms > of broken process. I understand that this is necessary to get things done, > but the fact that someone has to be a comdev member in order to edit the > website is broken. I am not sure what the way forward is here, but if > someone has some insight into how things work, and can suggest a more > reasonable way around this than making contractors comdev members, I would > be much appreciative > > Rich - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Requests for comdev membership
It seems to me that the recent requests for comdev membership are symptoms of broken process. I understand that this is necessary to get things done, but the fact that someone has to be a comdev member in order to edit the website is broken. I am not sure what the way forward is here, but if someone has some insight into how things work, and can suggest a more reasonable way around this than making contractors comdev members, I would be much appreciative Rich
