On Sun, Dec 20, 2020 at 7:14 PM Simon Lees
On 12/21/20 3:14 AM, Stefan Brüns wrote:
On Sonntag, 20. Dezember 2020 17:03:49 CET Mark Stopka wrote:
On Sun, Dec 20, 2020 at 3:11 PM Neal Gompa
wrote: We have ways to do conflict resolution, this isn't it.
Because repeatedly with no reasonable justification rejecting requests for access to a project you are a CO-MAINTAINER, not OWNER is, as well as rejecting update requests for a package that was not touched in 4 years by anybody else without any meaningful justification either.
I gave justification several times. Everyone can submit requests, not just maintainers, so while not being a maintainer you can still contribute.
Maintainers role is curating, and for this you have to know packaging policies. A newcomer should show they are knowing these rules, and this can be done by doing proper SRs.
I somewhat agree, but also somewhat disagree, if no one is looking after a package and someone wants to including taking over being the bugowner I don't see too many problems with a newer contributor taking over, this happens in many places, when I started maintaining enlightenment I only had half an idea what I was doing and learned as I went. Afterall we have a separate review team and a bunch of bots that will generally catch anything that gets missed.
At the point nobody is looking after it and it has no obvious maintainer working on it, then I could see that. But in this case, the maintainer clearly still cares.
As a side note can you please use the proper list addresses so that my mail filters work and I have some idea which lists i'm replying to :-)
Err, it seemed like you didn't quite Cc the list correctly? I got the most "interesting" list of CC addresses. :) -- 真実はいつも一つ!/ Always, there's only one truth!