Posts on make/project should be auto shared on all make sites

[jorbin]

This comes out of a slack discussion: ​https://wordpress.slack.com/archives/C02RQBWTW/p1757520671755739

The first comment on many posts on ​https://make.wordpress.org/project/ is to cross post to multiple other teams. As things that are being worked on from a full project standpoint affect every other team, auto cross posting would make sense and make things easier.

[tobifjellner]

We've got so much traffic on make/polyglots that this kind of automatic sharing probably wouldn't be that useful.
There or night be better to add a sidebar widget with the latest posts on /project instead.

[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 ​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.