- Issue created by @quietone
- 🇺🇸United States hestenet Portland, OR 🇺🇸
In terms of including the responsible parties in this:
So from a technical point of view:
- The announcement feed content is posted as a blog entry to: https://www.drupal.org/about/announcements/blog →
- So either a DA staff member or core team member could do that part.
BUT
- There is an extra step to publish the JSON feed (an extra safety net) - that only a DA engineering team member can do <-- so that's probably the role we should mention.
Historically I've been doing all this, but I'm not the only empowered to do so.
- 🇳🇿New Zealand quietone
Thanks. I've updated the suggested content and made an MR.
- Issue was unassigned.
- Status changed to Needs review
about 1 year ago 12:57am 13 September 2024 - 🇭🇺Hungary Gábor Hojtsy Hungary
gábor hojtsy → made their first commit to this issue’s fork.
- 🇭🇺Hungary Gábor Hojtsy Hungary
Added Drupal CMS on suggestion from @catch. I think the rest of the text is reasonable. I don't think anything else is needed here.
- 🇩🇰Denmark ressa Copenhagen
I created 🌱 Post more frequently to the Announcement Feed Active and there was agreement that the feed could be improved with more frequent news.
As I see it, the best solution would be to share more articles from https://www.drupal.org/news → . It shouldn't be all all posts from News, since there are many irrelevant posts, like sponsored articles.
My suggestion is -- like CiviCRM, mentioned in that issue -- to aim for adding one news item per week. It's not too little, nor too much. Or do you all think once a week is too often?
The point is to get some more relevant content in the announcement feed, it is currently too stale ...
- 🇩🇰Denmark ressa Copenhagen
Also, doesn't the release of Drupal CMS today deserve a mention? :)
- Status changed to RTBC
17 days ago 11:11am 5 September 2025 -
gábor hojtsy →
committed 240a09bf on main authored by
quietone →
[#3473507] docs: Add standing orders for announcement feed By: quietone...
-
gábor hojtsy →
committed 240a09bf on main authored by
quietone →
Now that this issue is closed, please review the contribution record.
As a contributor, attribute any organization helped you, or if you volunteered your own time.
Maintainers, please credit people who helped resolve this issue.