Yes, this could be a good idea. Might be too small as a gsoc project though.
I'd happily take this as i am anyways going to try for gsoc 19 with fedora,this could be a good starting point.
A simple dockerized/contenerized python based app could be done as a very simple implementation.
On Nov 17, 2018 4:35 PM, "Mattia Verga" <mattia.verga@xxxxxxxxxxxxxx> wrote:
Too often there are "non responsive maintainer" messages here.
Sometimes this is because a maintainer has lost their interest in Fedora
and left their responsibilities without communication, which means their
packages can be left unmaintained for long time in repositories before
someone notice that.
At other times the maintainer is still active, but for some reason they
are unreachable to users (email change, etc.).
I would propose some sort of automatic check of maintainer responsivity.
Maybe a tool that checks a packager activity in the last 6 months and if
there is no activity then sends an email asking the maintainer to
confirm they're still involved in Fedora. In case there's no reply,
either automatically orphan their packages or notify someone
(devel-list) to try to reach them.
What do you think?
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx
