Re: [DISCUSS] Remove 72 hour waiting time to add PPMC members.
Hi, > While this is a legitimate concern, as far as I know the Board and the > IPMC have not once exercised the right of veto It has happened, but we’re talking only a few times, so it is still a very rare exception. Podlings have more frequently been queried about their PMC makeup on graduation and in several cases asked to make changes, so I think we can cover any issues at that point. Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Remove 72 hour waiting time to add PPMC members.
> If we now exercise our means to object [to] a nomination after it’s executed, > we have this odd unpleasant situation of the person knowing what happened. While this is a legitimate concern, as far as I know the Board and the IPMC have not once exercised the right of veto, for hundreds if not thousands of PMC and PPMC appointments. So, let's optimize the common code path (approval without objection) over the rare path (veto from the Board/IPMC). On Sat, Oct 15, 2022 at 9:40 AM Christofer Dutz wrote: > > Hi, > > Well, I guess one of the reasons for the 72 hour was, that others can express > their doubts before the person is invited. > If we now exercise our means to object a nomination after it’s executed, we > have this odd unpleasant situation of the person knowing what happened. > > But I guess we could try it and put it back in place if we see things go > south. > > Chris > > > From: Justin Mclean > Date: Friday, 14. October 2022 at 17:39 > To: general@incubator.apache.org > Subject: Re: [DISCUSS] Remove 72 hour waiting time to add PPMC members. > Hi, > > > I’m a bit worried that in contrast to PMCs PPMCs are usually not quite > > familiar with how things work at Apache. > > Would we still have an option to intervene, if for example one PPMC bunch > > adds people from the same company, for example? > > I have a slight concern there as well, but this would very rarely occur. The > IPMC can remove people from the PPMC if they were inappropriately added. > > Kind Regards, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Remove 72 hour waiting time to add PPMC members.
Hi, Well, I guess one of the reasons for the 72 hour was, that others can express their doubts before the person is invited. If we now exercise our means to object a nomination after it’s executed, we have this odd unpleasant situation of the person knowing what happened. But I guess we could try it and put it back in place if we see things go south. Chris From: Justin Mclean Date: Friday, 14. October 2022 at 17:39 To: general@incubator.apache.org Subject: Re: [DISCUSS] Remove 72 hour waiting time to add PPMC members. Hi, > I’m a bit worried that in contrast to PMCs PPMCs are usually not quite > familiar with how things work at Apache. > Would we still have an option to intervene, if for example one PPMC bunch > adds people from the same company, for example? I have a slight concern there as well, but this would very rarely occur. The IPMC can remove people from the PPMC if they were inappropriately added. Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Proposal to Revive Apache Livy Community
Awesome - thanks, Justin! On Sat, Oct 15, 2022, 11:51 AM Justin Mclean wrote: > Hi, > > The project is free to choose RTC or RTC. I just wanted to check if it was > considered. I’ve seen in some cases, CTR tends to put a lot of work onto > existing committers and cause frustration when contributions are not > reviewed in a timely way. > > Another thing to consider is what someone would have to do to become a > committer. A RTC with a low committer bar would probably work better than a > RTC with a high committer bar. > > You are not an IPMC member but can ask to become one as you are an ASF > member. > > I started a roll call on the Livy private list that may get the attention > of any existing PMC members. > > Kind Regards, > Justin > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: Proposal to Revive Apache Livy Community
Hi, The project is free to choose RTC or RTC. I just wanted to check if it was considered. I’ve seen in some cases, CTR tends to put a lot of work onto existing committers and cause frustration when contributions are not reviewed in a timely way. Another thing to consider is what someone would have to do to become a committer. A RTC with a low committer bar would probably work better than a RTC with a high committer bar. You are not an IPMC member but can ask to become one as you are an ASF member. I started a roll call on the Livy private list that may get the attention of any existing PMC members. Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Proposal to Revive Apache Livy Community
Hi Justin - Thanks for the feedback. I can buy all of that other than the dev practices suggestion. The project originally used RTC as per the original proposal and being a more mature podling, I don't think we need to move that fast. With new committers, it will also be good to ensure others are familiar with the code going in. For pulling in large features from forks, we can have feature branches that are CTR and define merge criteria. I believe that I was an IPMC member at some point and have been a mentor on other podlings (still am???) but maybe somehow that went away? We would certainly welcome any other mentors as well. JB is currently listed as a Mentor on the site - I added him as a committer. @JB do you intend to be a Committer or Mentor going forward? The proposal was sent to the d...@livy.incubator.org list as well in order to get their thoughts. There have also been public threads about retiring it where this has been discussed as you know. Do you have further suggestions for how to reach out and/or how long to wait? Thanks again! --larry On Sat, Oct 15, 2022 at 12:24 AM Justin Mclean wrote: > Hi, > > A couple of things stand out here to me: > - Your mentors need to be IPMC members. > - It would be helpful to include mentors who are not all affiliated with > one company > - It would be helpful to know what the existing PMC and the wider > community think about this reboot. It may be there’s no one left, and no > objections from those who are still about, but we should give them some > time to speak up. > - RTC can slow development and, in some cases, limit contributions, > particularly when you have a less active project. Have you considered CTR? > - While asking existing PPMC members to opt-in is probably fine, I think > you should leave existing committers as they are and not remove anyone > unless they asked to be removed. > - Existing PPMC members who don’t explicitly opt-out should be able to > rejoin the PPMC later if they ask. > > Kind Regards, > Justin > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
[VOTE] Release Apache brpc (Incubating) 1.3.0
Hi Incubator Community, This is a call for a vote to release Apache brpc(Incubating) version 1.3.0. The Apache brpc community has voted and approved the release of Apache brpc (Incubating) 1.3.0. We now kindly request the Incubator PMC members review and vote on this incubator release. brpc is an industrial-grade RPC framework with extremely high performance, and it supports multiple protocols, full rpc features, and has many convenient tools. brpc community vote thread: https://lists.apache.org/thread/hrymv716j1q5cw382h1t0zq7gjpp2tbd Vote result thread: https://lists.apache.org/thread/xzkp3zlqkf7khnctfoqxdqxs8fkj6lt7 The release candidate: https://dist.apache.org/repos/dist/dev/incubator/brpc/1.3.0/ This release has been signed with a PGP available here: https://downloads.apache.org/incubator/brpc/KEYS Git tag for the release: https://github.com/apache/incubator-brpc/releases/tag/1.3.0 Build guide and get started instructions can be found at: https://brpc.apache.org/docs/getting_started The vote will be open for at least 72 hours or until the necessary number of votes is reached. Please vote accordingly: [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove with the reason Regards, Huixxi Apache brpc (Incubating) community - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
