To follow up here, we have a case here where a new committer (for one specific mojo) wants to do a release. Mirko brought up the idea of having a smaller group of people do the releases. Should we go that route, or should all committers for a mojo also be able to do releases? What we need to understand is that the privs on Sonatype OSSRH is for the whole org.codehaus.mojo groupId, not specific mojo sub-groupIds. So when you get access you can publish all mojos. But as you don't have write privs for all git repos releases shouldn't happen by accident though.
On Mon, Feb 17, 2020 at 9:30 AM Baptiste Mathus <[email protected]> wrote: > Yeah, I agree about the automation (obviously :)). I'm just not definitely > *personally* committing to it as I know this takes time to do well, and > even then takes some maintenance time. > > @Mirko: yes, the/some releases AFAIK started not following our process. I > *think > *many got pushed out without an email here, though I might be wrong. > I think instead of frowning at this, we probably should go back to David's > take and my answer above around making things easier. > E.g. I was thinking using a common build & release pipeline for all > plugins to make everything easy for contributors. > I know how to do this, I just quite lack the time to do this these days. > > -- Baptiste > > Le dim. 16 févr. 2020 à 23:44, David Karlsen <[email protected]> a > écrit : > >> Opening up seems reasonable. >> By using automated tooling (bots) it's easier to lock down repos (e.g. >> not requiring owner, or even direct write-access) - and handle more things >> through PR labelling. This makes it easier to onboard people. >> I used to maintain the aspectj plugin - but have not found the time for >> it, so I believe it was forked and some folks use that, but there is now >> interest in maintaining the original again - as seen on the mailing-list. >> >> tirsdag 11. februar 2020 08.56.12 UTC+1 skrev Anders Hammar følgende: >>> >>> 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/85dbc717-8633-48a8-89ec-2e5455902377%40googlegroups.com >> <https://groups.google.com/d/msgid/mojohaus-dev/85dbc717-8633-48a8-89ec-2e5455902377%40googlegroups.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/CANWgJS43v81Pu%2BvRTEyc_CKs95YjAhqVmF8SaF5NOdJacZ1yaA%40mail.gmail.com > <https://groups.google.com/d/msgid/mojohaus-dev/CANWgJS43v81Pu%2BvRTEyc_CKs95YjAhqVmF8SaF5NOdJacZ1yaA%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/CAKDUN1unjpX1mJ%2BsmYZWd75DkJe0C2TrKrShN7Mx44PEQZrN3w%40mail.gmail.com.
