Hello, I still think smaller changes might be better propagated using bodhi system. I know severity is used usually for security updates. But can we make more user-friendly summaries of enhancement updates? I think it might be sorted by severity and list only enhancement or newpackage type updates. Then we could make a nicer summary page with smaller, but still important changes. I think not only new packages are interesting. But a good place describing improvements in existing package in compact enough format is something I miss. What if we make summary for all enhancement updates, putting first high-severity updates. That might be rebases including new functionality for example, which might be useful to users. If only small feature would be added, maintainer may choose medium or low severity. It may generate monthly summaries without much additional work for maintainers. If upstream has a good documentation or blog, it might be sufficient just few bullets with hyperlink to upstream article introducing that features. I think often separate Fedora article would not be required. But do we have any better overview of changes targeted to end-users? I am not aware of anything good myself. I think bodhi enhancement is already not bad [1]. Could we propagate it a bit? Should those updates also include links to Fedora Changes explicit articles? Could we highlight those referencing them with higher 'importance'? If we would be able to hide minor improvements, I think it could pretty interesting for checking upcoming releases. Cheers, Petr 1. https://bodhi.fedoraproject.org/updates/?releases=F36&type=enhancement On 12/26/21 21:09, Matthew Miller wrote: > On Sat, Dec 25, 2021 at 09:15:38PM +0100, Fabio Valentini wrote: >> So ... maybe we could have a mailing list for this? >> >> Maybe "awesome-announce" or "the-new-shinyness" (I'm kidding! I'm bad >> with names!) at lists.fedoraproject.org, where all Fedora contributors >> could post the fancy new thing that they just made? Because we >> definitely don't have a good place for announcements like that right >> now (the community blog might be the right place for some of those, >> but it is a higher barrier to actually write a blog post that gets >> edited etc. instead of writing an e-mail to a mailing list). > Hmmm. > > The Community Blog should have a pretty low barrier to entry. Are > people feeling blocked by that? We should try to adjust if so. > > As it is, the bar is basically "is this appropriate for this site" and "is > the categorization right", with the editorial pass mostly being for > egregious problems. In other words, I don't think it's actually much more > heavyweight than a moderated announce mailing list would be. > > But I also am not sure Community Blog is the right audience — that's > intended to be contributor-facing, and this seems like something aimed to e > more user-facing. > -- Petr Menšík Software Engineer Red Hat, http://www.redhat.com/ email: pemensik@xxxxxxxxxx PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
