Dne 15. 02. 19 v 14:22 Emmanuel Seyman napsal(a):
> * Hans de Goede [15/02/2019 12:09] :
>> And automatic scripts really just should hand it over to the first 
>> co-maintainer
>> in the list.


As long as we have no idea if the other maintainers are active, I am
strongly against the automation. I've been there. Followed nor
responsive policy just to find out later that instead of orphaning the
package, next inactive maintainer became owner. Very frustrating ....


Vít


> This inspires two observations (which I'm sure you already know).
>
> * There's no such thing as "the first co-maintainer"
>
> There are co-maintainers and they all have equal standing. Picking one
> to give the package to is going to require one of:
>   1) asking them to figure it out amongst themselves
>   2) something based on /dev/random
>   3) running 'git shortlog -s | sort -nr' and going down the list
>
> * It's more polite to ask first
>
> Making someone the maintainer should probably require his informed consent.
> A co-maintainer might exist for the sole case of maintaing (perl|python|php)
> bindings of a given application. In this case, making them the point of
> contract will probably not yield the results you're looking for.
>
> Emmanuel
> _______________________________________________
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Reply via email to