Sounds good to me! We need more activity! /Anders
On Fri, Feb 14, 2020 at 2:54 PM Baptiste Mathus <[email protected]> wrote: > Thanks for raising this question Anders! > > AFAIK, we don't have a strict process. Or at least I'd say this process > has not been exercised enough in the last years to be considered really > *our* process I guess... > > So, I've been pondering a bit on this. > > Given our current status (I.e. not extremely active and many de facto > abandoned plugins) > I'm thinking that maybe we'd want to transform our process to be more like > the Jenkins one: moving away from an all-or-nothing maintainer access, and > giving maintainer permissions in a more open manner/less barrier (which was > anyway part of the reasoning behind MOJO vs. Apache). > > Also, our current status from an ownership perspective seems quite > dangerous: we have 31 owners (23 having 2FA enabled). > > I would propose *something* like the following: > > * We reduce the number of people with owner status (e.g. by removing the > ones without 2FA enabled, then pinging existing people to see if they're > willing to keep the permissions) > > * We initiate maintainers' team per plugin. > ** By default, we could for instance only put 'members' (as listed in > GitHub) who merged anything since we switched to GitHub. > > Anyway, not really asking for specifics at this stage. More like: do you > agree with the general idea/intent? > > Overall what I'm saying is I think we should together make the barrier > lower so mojohaus keeps rocking, instead of keeping it locked and it > progressively decays even more in terms of activity... > > WDYT ? > > -- Baptiste > > Le mar. 11 févr. 2020 à 08:56, Anders Hammar <[email protected]> a écrit : > >> Hi, >> >> At Codehaus Mojo I think we added new devs/committers to the team when >> accepting them, so they can work on all plugins. But know it looks like >> some devs have been added separately to just one plugin. >> As there is a new dev whosing interest in working with ther aspectj-m-p I >> wonder how we should handle that? >> >> /Anders >> >> -- >> You received this message because you are subscribed to the Google Groups >> "mojohaus-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/mojohaus-dev/CAKDUN1u7nVywOa9D%2BfD6fSEDA29RfKaDFgJaCBdduh_2W7MQ-A%40mail.gmail.com >> <https://groups.google.com/d/msgid/mojohaus-dev/CAKDUN1u7nVywOa9D%2BfD6fSEDA29RfKaDFgJaCBdduh_2W7MQ-A%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- > You received this message because you are subscribed to the Google Groups > "mojohaus-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/mojohaus-dev/CANWgJS6ZTM3f2rEv8sVLW8UeuU6a0vJvTzfKPx3E-jHNXwG3Rw%40mail.gmail.com > <https://groups.google.com/d/msgid/mojohaus-dev/CANWgJS6ZTM3f2rEv8sVLW8UeuU6a0vJvTzfKPx3E-jHNXwG3Rw%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "mojohaus-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/CAKDUN1vUbA_YLcfyrr9aUDtNL0qyJSf1%3D7a_sR5NjMeOQA7JKg%40mail.gmail.com.
