[wp-meta] [Making WordPress.org] #8086: Posts on make/project should be auto shared on all make sites

Making WordPress.org noreply at wordpress.org
Thu Sep 18 18:14:45 UTC 2025


#8086: Posts on make/project should be auto shared on all make sites
--------------------------------------+---------------------
 Reporter:  jorbin                    |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Make (Get Involved) / P2  |  Resolution:
 Keywords:                            |
--------------------------------------+---------------------

Comment (by desrosj):

 I've given this some more thought, and I tend to agree that cross-posts
 can be pretty noisy. This is especially true if you subscribe to multiple
 Make blogs and the post is cross-posted to several different Make blogs.
 Automatic cross-posting is probably not the right solution here as it
 risks people ignoring the notifications because there are too many.

 I wanted to step back and clarify what the problem is that we are trying
 to solve: some teams feel that they are not appropriately made aware of
 announcements that impact them. In this case, the
 [https://make.wordpress.org/core/2025/07/28/roadmap-to-6-9/ 6.9 Roadmap
 announcement] was only published on the Make Core blog and not cross-
 posted to other Make Team Blogs.

 Cross-posting should be reserved for single-team work that may impact one
 or two (but not more than 3?) others. The work would clearly belong under
 the responsible team's blog, and the cross-posting is just sharing as a
 courtesy.

 Instead of cross-posting by default, making it more widely known that the
 Make Project blog is where any announcements that set direction for the
 project, or impact multiple teams should be published seems like the
 better approach. The is clearly listed as the purpose of the blog in the
 sidebar already:

 > This p2 is for all-project communications and cross-team collaboration.
 It's a place to host and find discussions that affect all teams, and
 WordPress' “back-office” work more transparent.
 >
 > This blog is not associated with any one team, but rather with all the
 teams, and may be used for topics ranging from short-term initiatives to
 long-term maintenance work.

 There are only 85 subscribers to the Project blog currently, which is far
 too low.

 We should probably share each new post published on the Project blog into
 the `#announcements` channel on Slack.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/8086#comment:3>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org


More information about the wp-meta mailing list