On Fri, May 24, 2019 at 11:11 AM Adam Williamson <adamwill@xxxxxxxxxxxxxxxxx> wrote: > > On Thu, 2019-05-23 at 20:32 -0400, Christopher wrote: > > Do these compose reports need to spam devel@ ? > > I don't think most packagers are involved in composes, > > Yes, they are. All packagers are involved in composes. Composes are > made from the packages built by packagers. :P Most of the bugs in > composes are caused by...bugs in packages. What I mean is that most packagers wouldn't know what to do with these. These emails don't have any useful information for a packager to follow up with. If there's a composition failure attributable to a package, then those directly involved with composes, could easily pass that information down to the relevant packager. I just think that more automated notices that don't apply to *everyone* on the list, make it harder for packagers to stay subscribed to the list. This kind of information can easily be presented in a more friendly manner by doing something like: 1. Provide a status webpage, 2. Publish to a subscribable service, like an RSS feed, 3. Put the automated emails to a separate composes@ or notifications@ list to allow opt-in. It's nice to be able to keep the human-to-human conversations separate from the bots. It's not critical... it's just nicer, and I think it would help. _______________________________________________ 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
