Thank you for the discussion. It's clear that we can adopt the model where a PMC member mentors committers in the role of RM.
Let's update the release docs to reflect this change. On Sun, Feb 11, 2024, at 00:02, tison wrote: > +1 for Sheng's suggestion. Here are my experiences: > > Flink works well with the model a PMC member guides committers as RM and > nominates them as PMC members when they "know what and how to check, and > why those checks matter for a project". > > I used this flavor in Pulsar and successfully helped its C# committer to > run release and become a PMC member. > > As far as I know, only updating the KEYS file and upload artifacts to > release SVN folder require PMC member extra privileges. > > Best, > tison. > > > Sheng Wu <[email protected]>于2024年2月8日 周四06:07写道： > >> Short version, if someone is trusted to be a RM, you should make him/her a >> PMC member. >> Or, in a more practical way, a new RM as committer should be guided by >> another RM(PMC member), so svn wouldn't be a block, the new people still >> are able to sign the source tar and all other works. >> >> The key to be a RM is to know what and how to check, and why those checks >> matter for a project. >> >> Sheng Wu 吴晟 >> >> Apache SkyWalking >> Twitter, wusheng1108 >> >> >> Xinyou Ji <[email protected]>于2024年2月8日 周四05:47写道： >> >> > Hi, >> > >> > I prefer the way that the committers having the write access on the >> d.a.o. >> > branch. Having more potential RMs is a good thing, and involving a PMC >> > member for each release even when the PMC member is not an RM could be >> > difficult. >> > >> > Best, >> > Xinyou >> > >> > From: Xuanwo <[email protected]> >> > Date: Tuesday, February 6, 2024 at 21:08 >> > To: [email protected] <[email protected]> >> > Subject: [DISCUSS] Change the distribution policy so that committers can >> > push to the dist repository as well >> > Hi, everyone >> > >> > I started this discussion about OpenDAL's distribution policy at >> > >> https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2F&data=05%7C02%7C%7C15d03a27627f4649aecc08dc27819dc2%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638428684861009536%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=4BlnXmlcvxqyNL5cF6JgBzfZuXxEHzTChuv8AgiCQ90%3D&reserved=0 >> > <https://dist.apache.org/> (shortened as d.a.o) release branch. >> > >> > While in the incubator, all committers have direct write access to d.a.o >> > release branch, meaning PMCs don't need to do extra work if the RM is a >> > committer. >> > >> > However, once OpenDAL becomes a TLP, only PMCs will have write access to >> > d.a.o release branch. As noted in >> > >> https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fopendal%2Fissues%2F4150&data=05%7C02%7C%7C15d03a27627f4649aecc08dc27819dc2%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638428684861018317%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=qA0KanccmquttjTgWqYs%2BPfqcvMrLAo3gXFcDNPc8vk%3D&reserved=0 >> > <https://github.com/apache/opendal/issues/4150>, if an RM is a committer >> > but not a PMC, we'll need a PMC member involved in the release process to >> > update the KEYS and manage the release branch. >> > >> > We have two options here: >> > >> > - Change the release process: Involve a PMC member in the release >> process. >> > - Change the distribution policy: Allow committers to write release >> branch >> > of d.a.o (the same as before) >> > >> > What do you think? Feel free to leave your comments and decision below. >> > >> > Xuanwo >> > >> -- Xuanwo
