[policy, no patch] Deprecate and remove the Announcements module

@xmacinfo, thank you for following drupal.org policy and disclosing that an AI tool was used to help with this issue.

The first step in deprecating an extension is to create a policy issue to discuss the decision. That decision require sign off from the core committer roles as well as the subsystem maintainer for the extension. Only if is approved is the work for deprecating it started. And then that work is done by following the core process given in Remove a core extension and move it to a contributed project.

This issue should be changed to be a [policy, no patch] issue. Anything related to actually doing the deprecation should be removed as it is not needed in a policy issue. From my reading of this issue the second and third paragraphs seem suitable for a policy discussion.

Some recent examples of such policy issues that may be useful are:

• #3590816: [policy, no patch] Deprecate Olivero and move to contrib
• #3576460: [policy, no patch] Deprecate and remove Claro
• #3476879: [Policy] Move Contact module to contrib

@xmacinfo, As with most AI output I have come across this is verbose and repetitive. Was this reviewed to trim it down to the essentials and thus reduce the workload for reviewers? I ask because the Policy on the use of AI when contributing to Drupal states that "Posting issue comments, MR descriptions, or forum posts that are unreviewed AI output, not your own words." do not meet our standards.

@xmacinfo, thanks.

This policy issue does not need a release note snippet. And, in fact the release notes for extension removals is standard so a release note snipped isn't needed. What is done is to tag the issue that does the actual deprecation with, "x.y.z release notes". That is sufficient for it to be found when writing the release notes.

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.

That is from the original issue stating the purpose and justification for a messaging channel in core, #2940739: Project messaging channel in core initiative. It shows that the idea was to have "infrequent" updates that are not "relevant to the day-to-day needs of Drupal site builders and administrators". That suggests that the module is being used as designed and yet that same infrequency and lack of relevant to day-to-day is the motivation for this proposal. Interesting.

The issue summary also says that there are "multiple up-to-date communication channels". While that is true, the original issue also states that the channel is for the many Drupal users that do not have an account or follow Drupal project news, or engage with other Drupal communication channels. So, having this channel gives us a way to communicate with this set of users.

If the motivation is more about frequency there is an issue for discussing that, #3498976: Post more frequently to the Announcement Feed.

Do we have usage stats for this module?

Do we have usage stats for this module?

Some stats are here (latest are from 09/2025): https://www.drupal.org/project/drupal/issues/3158669

Instead of removing should we be using it more to make it worth it.

Each month, the DA and core committers discuss what is to be added to the announcements feed. Anyone, can also make an issue in the governance project to discuss having an announcement made.

Since the module is still relatively new should we hold on deprecating it then

Going to postpone, looking on https://www.drupal.org/project/issues/search/governance?text=&assigned=&... I see announcements about camps which seem like great announcements. Not everyone is on slack or other thread channels so anyway to get more engagement. Think postpone is the good status.

@smustgrave, can you clarify what needs to happen to un-postpone this issue and add it to the remaining tasks as explained in Remining tasks. Thanks

Sure!

@smustgrave, I don't understand how this can be postponed on "Determine if announcements can be used more.". Where would that discussion take place, if not here on this issue?

I think this should stay at needs review. There isn't a maintainer for this module so removing that tag.

Don't understand what's to review. Consensus has been to try and use announcements more. So putting in review just seems like it's going to waste away

Adding the slack conversation https://drupal.slack.com/archives/C079NQPQUEN/p1783091910574039 only a few comments but no one seemed to agree with removing this right now.

@godoislate mentioned

there was a slack thread between some people in core leadership and the DA about it, so it'd be up to them to comment

We've been discussion all the extension removals at one time. I have setup an issue for that and this is postponed on the core team completing their review, which is not yet scheduled.

I am setting this back to active to allow final discussion and in preparation for discussion by the Leadership Team that will hopefully happen at DrupalCon.