When the Make WordPress network was created back in 2012, every team that existed at the time got its own blog to use for transparent communication, collaboration, and coordination. An Updates blog was also created to be a place each team could use to report on their activity to other teams, and beyond.
The number of contributors and teams has grown in the nearly-ten years since, along with the user base of WordPress itself. As organizations expand, more coordination and communication work becomes necessary to keep everyone connected and working together. We’ve always used the Updates blog for this, because it was our only contributor-focused, cross-team space.
As more contributors get involved in cross-team efforts, I have heard complaints that it’s distracting or confusing when the Updates blog is used for announcements (like this one) and discussions (like these).
The last thing that I want is to create confusion or distract from the way teams keep each other informed, so I think the best solution is to create a new blog for all-project communications and cross-team collaboration. This blog should make it easier to host and find discussions that affect all teams, and make WordPress project “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. User permissions will be closed-selection, with the list of people who can author posts listed on the sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme.. Since the work accomplished on this blog exists across all teams, contributions won’t receive an additional profile badge. Once the work on make.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org//project feels more settled, we can all take a look to see if a specific badge is needed.
P.S. – From an open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. perspective, this idea might sound pretty “business-y.” A simpler explanation might be that this is similar to the work done by our MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. team: creating and maintaining the tools, infrastructure, safety, and processes that make contribution possible and more successful.