Automating the NonResponsiveMaintainers policy

Aleksandar Kurtakov akurtako at
Fri Mar 2 16:55:37 UTC 2012

----- Original Message -----
> From: "Reindl Harald" <h.reindl at>
> To: "Development discussions related to Fedora" <devel at>
> Cc: "Aleksandar Kurtakov" <akurtako at>
> Sent: Friday, March 2, 2012 6:45:14 PM
> Subject: Re: Automating the NonResponsiveMaintainers policy
> Am 02.03.2012 17:35, schrieb Aleksandar Kurtakov:
> >> it takes exactly 5 minutes to write a systemd-unit for most
> >> services like postfix/dbmail and nothing happens, even
> >> not if the one you called "boy" submits patches, unit-files
> >> and pinging maintainers since 3 releases with the result get
> >> ignored
> > 
> > Sure, everyone is free to come and show me how a random bug is
> > fixable in 5 minutes
> where did i say "fix a random bug in 5 minutes"?
> this postfix-update was before F16 release
> there were more postfix updates in the timeframe
> * writing the systemd-unit takes 2 minutes for postfix
> * no need for package anything, install put it locally in
> /etc/systemd/system
> * so testing takes another 3 minutes, no compile needed
> and now explain me what a maintainer knowing that the change to
> systemd was
> done with F15 is thinking by ship  the package with F16 again as
> sysv-service
> while users partly converted 20 different services in
> /ect/systemd/system/
> hallelujha, in F17 postfix has a systemd-unit
> read the changelog who is responsible for this and compare
> the name with the tread-starter, take a deep breath and
> think about how fursutrated it must be for him running
> behinfd maintainers from one release to the next

Have you ever thought that for number of people this systemd units might be something they know nothing about and they need to spend time on it?
That's why I say random bug. If this issue is not random for you it doesn't mean that's the same for everyone else. 
Have you ever thought that different people might have different priorities? 
If someone wants something to happen - step in and do it. 



More information about the devel mailing list