Re: How do we announce new packages?
On Fri, Jan 07, 2022 at 10:52:14AM +0100, Vít Ondruch wrote: > >>Then, the Group 3 person could ... wait, actually. Let's continue this > >>discussion with the Fedora Magazine folks. Please join me over at > >>https://discussion.fedoraproject.org/t/idea-for-collecting-cool-new-features-cool-new-packages-article-ideas/35761 > >Alright, I'm not sure why the discussion needed to *move*, but I've > >commented there. > To save me from participating I mean, I guess if you don't want to. But: that's where the Fedora Magazine discussions are, and this isn't really a _devel_ topic anyway. I know it's, *gasp*, a forum rather than another mailing list, but... the same thing would apply if that team were still using a mailing list. -- Matthew Miller Fedora Project Leader ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: How do we announce new packages?
Dne 06. 01. 22 v 19:38 Fabio Valentini napsal(a): On Thu, Jan 6, 2022 at 12:40 AM Matthew Miller wrote: On Wed, Jan 05, 2022 at 08:28:08PM +0100, Fabio Valentini wrote: So ... something like: - create a ticketing system for idea / text submissions (project with issue tracker on pagure?) - there, Fedora contributors can propose their cool new features / packages for inclusion in the next article - person / small group of people curate submissions, put together a final article, and propose it for Fedora Magazine I admit that this *does* sound better than "yet-another-mailing-list", though it's probably more work :) Yeah, that'd work. Another idea would be to rather than creating a new ticketing system, put it alongside the Magazine article proposals with #new-feature/#new-packages tag (instead of #article-idea or something). Then, the Group 3 person could ... wait, actually. Let's continue this discussion with the Fedora Magazine folks. Please join me over at https://discussion.fedoraproject.org/t/idea-for-collecting-cool-new-features-cool-new-packages-article-ideas/35761 Alright, I'm not sure why the discussion needed to *move*, but I've commented there. To save me from participating Vít OpenPGP_signature Description: OpenPGP digital signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: How do we announce new packages?
On Thu, Jan 6, 2022 at 12:40 AM Matthew Miller wrote: > > On Wed, Jan 05, 2022 at 08:28:08PM +0100, Fabio Valentini wrote: > > So ... something like: > > > > - create a ticketing system for idea / text submissions (project with > > issue tracker on pagure?) > > - there, Fedora contributors can propose their cool new features / > > packages for inclusion in the next article > > - person / small group of people curate submissions, put together a > > final article, and propose it for Fedora Magazine > > > > I admit that this *does* sound better than "yet-another-mailing-list", > > though it's probably more work :) > > > Yeah, that'd work. Another idea would be to rather than creating a new > ticketing system, put it alongside the Magazine article proposals with > #new-feature/#new-packages tag (instead of #article-idea or something). > > Then, the Group 3 person could ... wait, actually. Let's continue this > discussion with the Fedora Magazine folks. Please join me over at > https://discussion.fedoraproject.org/t/idea-for-collecting-cool-new-features-cool-new-packages-article-ideas/35761 Alright, I'm not sure why the discussion needed to *move*, but I've commented there. Fabio ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: How do we announce new packages?
On Wed, Jan 05, 2022 at 08:28:08PM +0100, Fabio Valentini wrote: > So ... something like: > > - create a ticketing system for idea / text submissions (project with > issue tracker on pagure?) > - there, Fedora contributors can propose their cool new features / > packages for inclusion in the next article > - person / small group of people curate submissions, put together a > final article, and propose it for Fedora Magazine > > I admit that this *does* sound better than "yet-another-mailing-list", > though it's probably more work :) Yeah, that'd work. Another idea would be to rather than creating a new ticketing system, put it alongside the Magazine article proposals with #new-feature/#new-packages tag (instead of #article-idea or something). Then, the Group 3 person could ... wait, actually. Let's continue this discussion with the Fedora Magazine folks. Please join me over at https://discussion.fedoraproject.org/t/idea-for-collecting-cool-new-features-cool-new-packages-article-ideas/35761 -- Matthew Miller Fedora Project Leader ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: How do we announce new packages?
On Wed, Jan 5, 2022 at 10:18 PM Ben Cotton wrote: > > On Wed, Jan 5, 2022 at 2:29 PM Fabio Valentini wrote: > > > > - create a ticketing system for idea / text submissions (project with > > issue tracker on pagure?) > > - there, Fedora contributors can propose their cool new features / > > packages for inclusion in the next article > > - person / small group of people curate submissions, put together a > > final article, and propose it for Fedora Magazine > > > > I admit that this *does* sound better than "yet-another-mailing-list", > > though it's probably more work :) > > The work (assuming we're just interested in new packages) could be > shortcut a bit by looking at the SCM requests repo: > https://pagure.io/releng/fedora-scm-requests/issues > > This only gives you the new packages, not any useful text, which the > maintainer might be better positioned to provide. Although you could > just use the Description: from the spec file. But one person could > probably put this together for the month in a relatively short time. > > Of course, if we want to include stuff beyond "here's the new > packages", this breaks down. The ticket system approach is probably > the best in that case, but the hard part is going to get people to > remember to add to it. Yeah, but just looking at "new" packages probably won't be enough (whether getting the data from fedora-scm-requests, bodhi, or compose reports, etc.). There's just too much low-level stuff getting added all the time (and by that I mean packaging of new library dependencies, to keep all applications happy and up-to-date), but most of those "new" packages are not interesting to users at all. Still, I'd hope that most people who worked on some cool new feature for Fedora would want people to know about it? Opening a ticket to get it included in a "Cool new stuff in Fedora this $MONTH" listicle seems like a low barrier to get things out "to the world". Fabio ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: How do we announce new packages?
On Wed, Jan 5, 2022 at 2:29 PM Fabio Valentini wrote: > > - create a ticketing system for idea / text submissions (project with > issue tracker on pagure?) > - there, Fedora contributors can propose their cool new features / > packages for inclusion in the next article > - person / small group of people curate submissions, put together a > final article, and propose it for Fedora Magazine > > I admit that this *does* sound better than "yet-another-mailing-list", > though it's probably more work :) The work (assuming we're just interested in new packages) could be shortcut a bit by looking at the SCM requests repo: https://pagure.io/releng/fedora-scm-requests/issues This only gives you the new packages, not any useful text, which the maintainer might be better positioned to provide. Although you could just use the Description: from the spec file. But one person could probably put this together for the month in a relatively short time. Of course, if we want to include stuff beyond "here's the new packages", this breaks down. The ticket system approach is probably the best in that case, but the hard part is going to get people to remember to add to it. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: How do we announce new packages?
On Sun, Jan 2, 2022 at 10:09 PM Matthew Miller wrote: > > On Sun, Jan 02, 2022 at 09:19:15PM +0100, Dan Čermák wrote: > > > new-tech? noteable-changes? new-features? > > > > fedora-contributor-announce? > > Heh: see > https://discussion.fedoraproject.org/t/proposal-contributor-announce-mailing-list/28902 > It's still on my todo list! > > But going back up in this thread ... this particular topic isn't supposed to > be contributor-focused, is it? So I don't think that's the right solution. > > I'm also hesitant about creating _even more_ lists.* I think that tends to > just fragment things more and create more confusion. So, I have two > counter-proposals: > > 1. As previously noted, Fedora Magazine seems like the right audience. Maybe >interested people could collect topics and run an article every month? > > 2. There is a News & Announcements category on Fedora Discussion, and people >can get that by email if they want (or as an RSS feed), and can have >granular control over what they're notified on by tag. We can create a >#new-and-cool tag or similar. So ... something like: - create a ticketing system for idea / text submissions (project with issue tracker on pagure?) - there, Fedora contributors can propose their cool new features / packages for inclusion in the next article - person / small group of people curate submissions, put together a final article, and propose it for Fedora Magazine I admit that this *does* sound better than "yet-another-mailing-list", though it's probably more work :) Fabio ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: How do we announce new packages?
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=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: pemen...@redhat.com PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: How do we announce new packages?
On Sunday, 2 January 2022 21.08.45 WET Matthew Miller wrote: > 1. As previously noted, Fedora Magazine seems like the right audience. Maybe > interested people could collect topics and run an article every month? FWIW I agree with you. In particular I remember a similar effort for R packages (the last example): https://rviews.rstudio.com/2021/12/21/november-2021-top-40-new-cran-packages/ There is a tag called "top-40" that it is not used consistently, e.g, the previous entry: https://rviews.rstudio.com/2021/11/29/october-2021-top-40-new-cran-packages/ The nice thing in this type of reports is how the different packages are placed together in related areas. And yes this is a time consuming task. :-) -- José Abílio___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: How do we announce new packages?
On Sun, Jan 02, 2022 at 09:19:15PM +0100, Dan Čermák wrote: > > new-tech? noteable-changes? new-features? > > fedora-contributor-announce? Heh: see https://discussion.fedoraproject.org/t/proposal-contributor-announce-mailing-list/28902 It's still on my todo list! But going back up in this thread ... this particular topic isn't supposed to be contributor-focused, is it? So I don't think that's the right solution. I'm also hesitant about creating _even more_ lists.* I think that tends to just fragment things more and create more confusion. So, I have two counter-proposals: 1. As previously noted, Fedora Magazine seems like the right audience. Maybe interested people could collect topics and run an article every month? 2. There is a News & Announcements category on Fedora Discussion, and people can get that by email if they want (or as an RSS feed), and can have granular control over what they're notified on by tag. We can create a #new-and-cool tag or similar. * Spoiler for upcoming post in which I encourage teams to move to Fedora Discussion! -- Matthew Miller Fedora Project Leader ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: How do we announce new packages?
Kevin Fenzi writes: > On Sat, Jan 01, 2022 at 12:23:49PM +0100, Dan Čermák wrote: >> Fabio Valentini writes: >> >> > On Sun, Dec 26, 2021 at 9:09 PM 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. >> > >> > Those are exactly my thoughts. I don't think there's a way for Fedora >> > contributors to "market" the cool new thing they've been working on to >> > *users* (or tech publications)? >> > >> > I mean, submitting a Change Proposal results in things getting >> > announced pretty publicly, but that does not fit for smaller changes, >> > or changes that are not specific to the next Fedora release. >> > >> > I know that some tech news websites follow discussions on the devel >> > list (and probably the announcement lists), but those are mostly not >> > really of interest to *users*, and there's no mailing list for "here's >> > a cool new feature!" that they can subscribe to. That might skew >> > newsworthy items more towards the "negative news" side of things, like >> > "this package is orphaned / retired" / "Is this maintainer still >> > responsive" etc., having more *positive* news to report on would be >> > nice for Fedora. >> >> So how about we just create such a list, make it moderated, ensure that >> every post gets at least *some* proofreading and see how it works out? > > I'm game... but that brings us to the hardest problem in computers: > what do we name it? :) > > new-tech? noteable-changes? new-features? fedora-contributor-announce? > And... who will moderate? Perhaps we could/should file a infra ticket on > the list and have interested parties add their names there? Sounds good to me. Cheers, Dan ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: How do we announce new packages?
On Sat, Jan 01, 2022 at 12:23:49PM +0100, Dan Čermák wrote: > Fabio Valentini writes: > > > On Sun, Dec 26, 2021 at 9:09 PM 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. > > > > Those are exactly my thoughts. I don't think there's a way for Fedora > > contributors to "market" the cool new thing they've been working on to > > *users* (or tech publications)? > > > > I mean, submitting a Change Proposal results in things getting > > announced pretty publicly, but that does not fit for smaller changes, > > or changes that are not specific to the next Fedora release. > > > > I know that some tech news websites follow discussions on the devel > > list (and probably the announcement lists), but those are mostly not > > really of interest to *users*, and there's no mailing list for "here's > > a cool new feature!" that they can subscribe to. That might skew > > newsworthy items more towards the "negative news" side of things, like > > "this package is orphaned / retired" / "Is this maintainer still > > responsive" etc., having more *positive* news to report on would be > > nice for Fedora. > > So how about we just create such a list, make it moderated, ensure that > every post gets at least *some* proofreading and see how it works out? I'm game... but that brings us to the hardest problem in computers: what do we name it? :) new-tech? noteable-changes? new-features? And... who will moderate? Perhaps we could/should file a infra ticket on the list and have interested parties add their names there? kevin signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: How do we announce new packages?
Fabio Valentini writes: > On Sun, Dec 26, 2021 at 9:09 PM 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. > > Those are exactly my thoughts. I don't think there's a way for Fedora > contributors to "market" the cool new thing they've been working on to > *users* (or tech publications)? > > I mean, submitting a Change Proposal results in things getting > announced pretty publicly, but that does not fit for smaller changes, > or changes that are not specific to the next Fedora release. > > I know that some tech news websites follow discussions on the devel > list (and probably the announcement lists), but those are mostly not > really of interest to *users*, and there's no mailing list for "here's > a cool new feature!" that they can subscribe to. That might skew > newsworthy items more towards the "negative news" side of things, like > "this package is orphaned / retired" / "Is this maintainer still > responsive" etc., having more *positive* news to report on would be > nice for Fedora. So how about we just create such a list, make it moderated, ensure that every post gets at least *some* proofreading and see how it works out? Cheers, Dan ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: How do we announce new packages?
On Sun, Dec 26, 2021 at 9:09 PM 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. Those are exactly my thoughts. I don't think there's a way for Fedora contributors to "market" the cool new thing they've been working on to *users* (or tech publications)? I mean, submitting a Change Proposal results in things getting announced pretty publicly, but that does not fit for smaller changes, or changes that are not specific to the next Fedora release. I know that some tech news websites follow discussions on the devel list (and probably the announcement lists), but those are mostly not really of interest to *users*, and there's no mailing list for "here's a cool new feature!" that they can subscribe to. That might skew newsworthy items more towards the "negative news" side of things, like "this package is orphaned / retired" / "Is this maintainer still responsive" etc., having more *positive* news to report on would be nice for Fedora. Fabio ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: How do we announce new packages?
On Sun, Dec 26, 2021 at 2:02 PM Matthew Miller wrote: > Fedora Magazine semi-regularly runs "cool new projects in Copr" articles > (https://fedoramagazine.org/?s=copr). It doesn't seem like too much of > stretch to occasionally also have "cool new packages in the distro" article > occasionally. > > +1 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: How do we announce new packages?
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. -- Matthew Miller Fedora Project Leader ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: How do we announce new packages?
On Sat, Dec 25, 2021 at 11:37:10PM +, Gary Buhrmaster wrote: > The Fedora Community Blog and the Fedora Magazine > are obvious places to look for such info, which target > different communities. > > In both cases, it would seem some with strong > writing and editorial skills (and time, which is often > the constraining factor) would need to be the ones > to take the firehouse of something like the compose > report and convert to something less intimidating. Fedora Magazine semi-regularly runs "cool new projects in Copr" articles (https://fedoramagazine.org/?s=copr). It doesn't seem like too much of stretch to occasionally also have "cool new packages in the distro" article occasionally. -- Matthew Miller Fedora Project Leader ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: How do we announce new packages?
Il 22/12/21 14:49, Petr Menšík ha scritto: > > If newpackage is chosen in Bodhi update, it can be listed from it: > > https://bodhi.fedoraproject.org/updates/?search==__current__=__pending__=newpackage=1 > > Slight problem is rawhide only builds do not have newpackage updates > in bodhi. I think they do not have any good place to watch them. It > lists bunch of packages, but it seems only good coincidence. > > Rawhide updates for Rawhide are marked newpackage in Bodhi only when they're come from a side-tag and the user chooses the right update type in the update form. Currently Bodhi's automatic rawhide update creator doesn't check if a package was already present in distribution. I've just submitted a PR [1] that should make the automatic rawhide update creator capable of detecting new package, hopefully this would be solved in a future release. After that, it should be quite simple to get new packages by a RSS feed like https://bodhi.fedoraproject.org/rss/updates/?search==__pending__=newpackage Mattia [1] https://github.com/fedora-infra/bodhi/pull/4324 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: How do we announce new packages?
On Sat, Dec 25, 2021 at 8:16 PM Fabio Valentini wrote: > (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). The Fedora Community Blog and the Fedora Magazine are obvious places to look for such info, which target different communities. In both cases, it would seem some with strong writing and editorial skills (and time, which is often the constraining factor) would need to be the ones to take the firehouse of something like the compose report and convert to something less intimidating. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: How do we announce new packages?
On Wed, Dec 22, 2021 at 2:07 PM Eduard Lucena wrote: > > Hello people. > > First of all, I'm not a developer or a packager, I just try to help with the > little things I know to do. One thing I try to do is to check news, forums, > ML and places where people talk about Fedora. > > A thing I noted is that a lot of people in magazines and news sites like > phoronix, hacker news and other sites follow this list to get news about the > project and it started to worry me that a big part of the traffic follow > orphaned and retired packages, but nothing is never revealed/published when a > new package enter the repositories or nothing similar, maybe a review swap > but it's not enough. > > Trying to market the number of packages, the amount of free and open source > software that we offer, how this could be measured and published? Is that > something that require to much work? This is an area that we definitely could do more "marketing" in. There's lots of times that "I worked on a cool new feature" (new packages, or updates for existing packages, etc.) would be too small for submitting a Change proposal, and often, these "small" shiny things are also pushed to stable releases. 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). Fabio ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: How do we announce new packages?
There are the "Fedora rawhide compose report" email coming (almost) daily into this ML, which contains list of added packages. Nevertheless, the "Changes" [1] process is the main way to announce and increase visibility of the new features which goes to Fedora. Vít [1] https://docs.fedoraproject.org/en-US/program_management/changes_policy/ Dne 22. 12. 21 v 14:07 Eduard Lucena napsal(a): Hello people. First of all, I'm not a developer or a packager, I just try to help with the little things I know to do. One thing I try to do is to check news, forums, ML and places where people talk about Fedora. A thing I noted is that a lot of people in magazines and news sites like phoronix, hacker news and other sites follow this list to get news about the project and it started to worry me that a big part of the traffic follow orphaned and retired packages, but nothing is never revealed/published when a new package enter the repositories or nothing similar, maybe a review swap but it's not enough. Trying to market the number of packages, the amount of free and open source software that we offer, how this could be measured and published? Is that something that require to much work? Br, -- Eduard Lucena Móvil: +56962318010 GNU/Linux User #589060 Ubuntu User #8749 Fedora Marketing Representative ___ devel mailing list --devel@lists.fedoraproject.org To unsubscribe send an email todevel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it:https://pagure.io/fedora-infrastructure OpenPGP_signature Description: OpenPGP digital signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: How do we announce new packages?
If newpackage is chosen in Bodhi update, it can be listed from it: https://bodhi.fedoraproject.org/updates/?search==__current__=__pending__=newpackage=1 Slight problem is rawhide only builds do not have newpackage updates in bodhi. I think they do not have any good place to watch them. It lists bunch of packages, but it seems only good coincidence. https://bodhi.fedoraproject.org/updates/?search==F36=newpackage Should the first successful rawhide build trigger newpackage update on current rawhide release? It would also handle case when new package is build only in Rawhide. Review bug then has to be closed manually, because it never passes ON_QA phase without build and bodhi update for stable release. Because the review bug is required for repository creation, I think it would be nice to simplify using it for initial update also on rawhide. Cheers, Petr On 12/22/21 14:07, Eduard Lucena wrote: > Hello people. > > First of all, I'm not a developer or a packager, I just try to help > with the little things I know to do. One thing I try to do is to check > news, forums, ML and places where people talk about Fedora. > > A thing I noted is that a lot of people in magazines and news sites > like phoronix, hacker news and other sites follow this list to get > news about the project and it started to worry me that a big part of > the traffic follow orphaned and retired packages, but nothing is never > revealed/published when a new package enter the repositories or > nothing similar, maybe a review swap but it's not enough. > > Trying to market the number of packages, the amount of free and open > source software that we offer, how this could be measured and > published? Is that something that require to much work? > > Br, > -- > Eduard Lucena > Móvil: +56962318010 > GNU/Linux User #589060 > Ubuntu User #8749 > Fedora Marketing Representative > > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > 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@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure -- Petr Menšík Software Engineer Red Hat, http://www.redhat.com/ email: pemen...@redhat.com PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
