Re: [DISCUSS] Project member emeritus policy change

Hi, in general +1...but... I would enhance the description (rules) a bit...because if someone is doing some bug reporting/reviewing issues etc. that is participating as well...in the general idea of contributing... Kind regards Karl Heinz Marbaise On 22.10.24 18:17, Tamás Cservenák wrote: Ho

Re: [DISCUSS] Project member emeritus policy change

+0 I agree that it would be a good practice to clean up, but in the end it is not a big deal to have people listed Thanks for raising the discussion, having these conversations about the community itself is always a great opportunity for the project to grow and become stronger Some comments inli

Re: [DISCUSS] Project member emeritus policy change

+-0 but maybe start to setup a routine which will generate a "team2.html" page with a column "latest contribution" (mail or commit or review?) and from there see how it looks like and then spawn again the emeritus topic? Romain Manni-Bucau @rmannibucau | Blog

Re: [DISCUSS] Project member emeritus policy change

+1 On Tue, Oct 22, 2024 at 6:17 PM Tamás Cservenák wrote: > Howdy, > > I would like to propose a project policy change (followed by > implementation) regarding "emeritus" status of PMCs and members. > > Proposal: > 1) IF a PMC member is inactive for 24 months (did NOT participate in > any VOTE [

Re: [DISCUSS] Project member emeritus policy change

Supply chain attacks are a concern. In practice I've never heard of one of these coming about because of old committer account compromise. I have seen them happen because: 1. A threat actor actively targets a project and becomes a coimmitter by submitting good patches over time. 2. An entire proj

Re: [DISCUSS] Project member emeritus policy change

If the goal here is to simply clarify the metrics on project participation, perhaps we could run one of the tools from CHAOSS that will tell us how many people participate and how (mail list, commits, reviews, etc.) On Wed, Oct 23, 2024 at 3:20 PM Ralph Goers wrote: > FWIW, if Maven adopts the i

Re: [DISCUSS] Project member emeritus policy change

FWIW, if Maven adopts the idea of modifying https://maven.apache.org/team.html similar to the Logging Services team page I linked too then I would likely move myself to the inactive list. Although I do occasionally participate in threads like this and vote on occasion I haven’t committed to the

Re: [DISCUSS] Project member emeritus policy change

+1 Regarding the "dormant PMC member" issue that Eliotte mentioned. I am happy people are willing to contribute again! From what I understand, an inactive member is only marked as inactive / emeritus. They are not removed from the PMC. They can become active again by simply contributing and

Re: [DISCUSS] Project member emeritus policy change

+1 Agree. Not sure of special flag, getting back online will be as simple as sending an email to PMC list On Wed, 23 Oct 2024 at 15:45, Slawomir Jaranowski wrote: > > On Tue, 22 Oct 2024 at 21:43, Guillaume Nodet wrote: > > > > I think the idea is not to *remove* members. > > My understanding (a

Re: [DISCUSS] Project member emeritus policy change

On Tue, 22 Oct 2024 at 21:43, Guillaume Nodet wrote: > > I think the idea is not to *remove* members. > My understanding (at least, what I agree with) is to flag members as active > or not. I don't see an option to flag a user ... We can simply remove from the project and as requested we can add

Re: [DISCUSS] Project member emeritus policy change

I think the idea is not to *remove* members. My understanding (at least, what I agree with) is to flag members as active or not. This would help having a better understanding of the community dynamics, as indicated in the original email. If we don't remove members, any inactive member can just be

Re: [DISCUSS] Project member emeritus policy change

-1 At least once I have personally brought a long dormant Maven PMC member out of hibernation to approve PRs and releases, and it was very helpful for moving the train along when active PMC members weren't interested enough in what my team was doing to review code and vote for releases. And now th

Re: [DISCUSS] Project member emeritus policy change

Le mar. 22 oct. 2024 à 19:31, Ralph Goers a écrit : > I would suggest that just responding on mailing lists count as well. It is > fairly easy to see if a user’s email shows up in any of the mailing lists. > This would also include GitHub commits, PRs, discussions, etc. since they > all generate

Re: [DISCUSS] Project member emeritus policy change

I would suggest that just responding on mailing lists count as well. It is fairly easy to see if a user’s email shows up in any of the mailing lists. This would also include GitHub commits, PRs, discussions, etc. since they all generate email to a list. Also - do you truly mean “emeritus” (remo

Re: [DISCUSS] Project member emeritus policy change

+1 (nb) (already read the thread on slack) Am 22.10.2024 um 18:17 schrieb Tamás Cservenák: Howdy, I would like to propose a project policy change (followed by implementation) regarding "emeritus" status of PMCs and members. Proposal: 1) IF a PMC member is inactive for 24 months (did NOT parti

[DISCUSS] Project member emeritus policy change

Howdy, I would like to propose a project policy change (followed by implementation) regarding "emeritus" status of PMCs and members. Proposal: 1) IF a PMC member is inactive for 24 months (did NOT participate in any VOTE [by casting binding vote] OR did not create any commit that ended up in the