While quickly discussing request notifications on IRC we more or less decided that it would be best to send an email to everyone on the notification list saying that they need to be subscribed to the aur-requests ML to discuss the request. Though I'm not sure if we want to send that message to people every time, so maybe only send said notification email to a user once?

Also, since there's a red line in the action box that says if there are any PRQs open against the package.

Not sure what you mean by only sending the notification once. We should inform users about every package request. However, if you wanted to say that we do not need to send an email when the request status changes (e.g. accepted/rejected), I agree on that.

This is a very important thing I think. Even if everything is not lost (at least not the git repo, right?), I’ve been warned of the deletion of some package I use only at the time of deletion notification: the PRQ is not notified and you might definitively miss it if you don’t go to the package page on a regular basis. Since not everyone is telling in comments that’s they are opening a PRQ (including myself in my recent spree, totally forgot about that…), this is quite annoying. :(

I’ve subscribed to aur-requests for a time, but the volume was annoying just to be notified for the packages I use. Since I’m considering becoming a TU, I’ll have to subscribe again anyway so won’t be impacted any further, but from an user point of view I definitively understand that people don’t want to subscribe to this list just to receive hypothetical notifications regarding the packages they use. ;)

More generally, before I’ve remembered the existence of “projects” in FlySpray, I’ve posted something like this to the ML[0]: “could we receive mails when a package for which we have subscribed is flagged out-of-date, and also
when a request is filed against it? In short, I would like to be notified whenever anything related to a package I’ve subscribed for happens. These could be options just like updates notifications are currently.”

To precise this a bit more, the list of notifications should include (to my opinion at least):

– out-of-date notifications, a patch have been submitted[1] for co-maintainers, but I think it could be nice to notify users too (maybe tied to update ones option?). Should I open a new issue for this one?
– (co-)maintainership changes (own/disown/add/delete), this is  FS#15412  I think.
– package renaming. This is probably a hard one, is it possible to do it, is it desirable (to be honest, the only use case I have in mind is the fixing of my own misuse of pkgbase), and should I open an issue for this one?
– PRQ, this issue.

For this last one, maybe you could add something like that at the bottom of the notification email:
“Reminder: In order to reply to this email and discuss this PRQ, you must be subscribed to [aur-requests](https://lists.archlinux.org/listinfo/aur-requests)”

Like Lukas, I’m not sure what you meant Johannes, but in contrary to him I understood it more like “tell the user once about aur-requests when he receive its first PRQ notifications”, but outside of the fact this is state based and would require storing and looking each time for one more field in the user DB, I think it’s a good idea to always remind that fact, hence my proposed solution. It’s just a tiny line at the end, so it doesn’t cost much to send it each time.

Finally, I definitively agree with Lukas that we should inform on every request, but regarding status changes this shouldn’t be necessary indeed excepted in case of reject, because all other cases trigger a standard notification email (to be exact, some actually do and others should as discussed above).

But I suppose all this also depends on  FS#31851 .

[0] https://lists.archlinux.org/pipermail/aur-general/2016-November/032931.html
[1] https://lists.archlinux.org/pipermail/aur-dev/2016-November/004171.html