Maintainer monthly report

[arthurzam]

<@mattst88> arthurzam: a monthly email ping to maintainers :)
<@mattst88> seriously, it's something I've wanted to write a tool to do
<@arthurzam> mattst88: what is this?
<@mattst88> let me find my notes
<+dwfreed> 'imlate' by email, basically?
<@mattst88> more than that, but that would be a part of it, yeah
<@mattst88> the ideas I had were, a monthly email to maintainers noting --
<@mattst88> - package stabilization candidates
<@mattst88> - packages with redundant versions in tree
<@mattst88> - summary of QA warnings for their packages
<@mattst88> - list of open bugs assigned to them
<@mattst88> - list of bugs assigned to them that were closed in the last month
<@mattst88> and for projects themselves (e.g. x11@, gnome@, etc) --
<@mattst88> -- shortlog of project members' commits to the project's packages
<@mattst88> -- shortlog of non-project members' commits to the project's packages
<@mattst88> end
<@mattst88> maybe even a list of the packages maintained. I've run into many maintainers who have literally forgotten that they're the maintainer of a package
<@mattst88> I think it'd be great if the monthly mails went to a mailing list for archival purposes as well
<@arthurzam> I see. I'm suddenly afraid of packages.g.o becoming write thingy (sending stuff to others) instead of just supplying data
<@arthurzam> I'm unsure how to handle it sending email (by which address, why should it be accepted, etc) on the infra side.
<@arthurzam> How to make it opt in/opt out - or just mandatory for all devs?
<+negril> make a data api that you can pull the data from and let the rest be figured out by others?
<@arthurzam> Most of it can be done from current data in DB. Only "closed bugs" doesn't exist
<@mattst88> negril: yeah, that might be the best way to do it