Automating the NonResponsiveMaintainers policy

[Reindl Harald]

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
http://koji.fedoraproject.org/koji/buildinfo?buildID=263131

* 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



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <http://lists.fedoraproject.org/pipermail/devel/attachments/20120302/7bf473df/attachment.sig>