Post more frequently to the Announcement Feed

ll the discussion about post content so far has been in the governance queue, so moving this there.

I do agree it should be more frequent. For a start there should be a Drupal CMS announcement (and then further release announcements).

Thanks for moving it to a better place, and I am glad you agree. I'll update the Issue Summary with a frequency proposal. Like CiviCRM, I think aiming for adding one news item per week is reasonable, not too little, not too much.

At the moment there are the following kinds of regular posts:

Core releases - 2 per year (Drupal core committers responsible for writing them)

DrupalCon US + Europe - 2 per year (DA responsible for writing them)

DrupalCon Asia, South America etc. - currently an undefined number of these per year between 0 and 3 (DA again)

I think it is likely that Drupal CMS releases will be announced in the announcements feed too, I don't know how many announceable releases there will be per year (or even if there's an issue discussing this), my guess would be somewhere between 2 and 4.

There is a proposal to add a Drupal camps roundup 📌 Announcements feed: Create upcoming camps post Active but it hasn't happened yet.

If all of these happen, that would be 10-15 posts per year.

I agree that 12 items a year would be an improvement, but it's still too few in my opinion ...

More subjects could be included, to increase the frequency, and if Drupal camps and more articles from https://www.drupal.org/news → were included, I think one item a week is realistic.

Maybe even include minor releases of the current official release, such as Drupal 10.4.1 → ? At least security releases should be included.

PS. It looks like Drupal 10.4.0 - 17 December 2024 was forgotten ...

We didn't forget 10.4.0, anything worth talking about in 10.4.0 was also in 11.1.0. 10.4 got a mention on the 11.1 post https://www.drupal.org/blog/drupal-11-1-0 → but doing a separate announcement post would have meant they both had to go out within a day or two of each other and either the 10.4 one would say very little, or it would duplicate the 11.1 post.

We did have some packaging issues with the 11.1 release, it is quite possible that if we'd actually released them on the same day the post would have been "11.1 and 10.4 released" - but still one post.

We might do a PSA-style post for the 'last minor' of the 10.x branch especially if we have an official EOL date by then, but I don't think we'd do them for the other maintenance minors before then.

For similar reasons, I don't think we should announce patch releases - sites get notified about them via update status, and there's really nothing to say.

Security releases - I think we'd only do that for very severe core security releases, but maybe for those.

Thanks for clarifying. And yes, a "11.1 and 10.4 released" would have made sense, had they been released at the same time.

I think that simply sharing some of all the articles from https://www.drupal.org/news → would be an easy win, there are enough to choose from.

I think we didn't want to overwhelm users with a lot of posts, especially given that we enabled the Announcements module by default for all existing installation in D7. So while I agree that currently there is too few posts in the feed, I am not sure it would be a good idea to add all from https://www.drupal.org/news → . There is also an issue for camps/events ( 📌 Announcements feed: Create upcoming camps post Active ), which I think would be a good idea to regularly include.

Well, I never suggested adding all posts from News (note, that I use the word "some"). There are many irrelevant posts, like sponsored articles.

What I do suggest is posting about once a week in the Announcement feed, and some items could be picked from https://www.drupal.org/news → , some could be new Drupal releases, some about upcoming Drupal camps, etc.

Or do you think once a week is too often?

The point is to get some more relevant content in the announcement feed, it is currently too inactive ...

For me this is not just about frequency but topics. For example, I don't think it makes that much sense to post updates about new Drupal CMS versions to *existing* Drupal users, since there is no upgrade path. However, if there are more frequent posts covering more diverse topics, it doesn't matter as much.

I don't really have the answer but I do think it's worth a discussion of who this feed is for and what its strategic aims are, alongside any attempt to post more frequently.

Accidental title update!

The original discussion about the feed is here: 🌱 Project messaging channel in core initiative Fixed

The vast majority of Drupal users do not have accounts on Drupal.org, and likely do not regularly follow Drupal project news, or engage with communications channels that promote important updates, news and events, or support for the community and association.
Project messaging channel initiative
The goal of this initiative is to provide a channel for messaging about the Drupal project within the administrative interface of core. This channel could provide information about upcoming releases, new feature highlights, events like DrupalCon, and promote support of the project via Association membership or other programs.

For me, Drupal CMS releases fit into that goal pretty well, because it is project news. It's not really supposed to be relevant to the site in most cases, but the site owner, except for maybe something like 7.x and 10.x EOL announcements because those really only affect people running sites on those versions.

Bump as the last announcement is about DrupalCon Atlanta coming up and it already happened.

I think we might want to highlight things like the Aaron Winborn award (yearly) and Driesnote recaps (2-3 per year) in the announcements.

IMHO major releases of Drupal CMS should also be included (2 per year?).