Summary of the WordPress Developer Blog (versus network, site) meeting, which took place in the #core-dev-blog channel on the Make WordPress Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.. Start of the meeting in Slack.
Attendees: @bph, @marybaum, @webcommsat, @greenshady, @ironnysh, @magdalenapaciorek
Last meeting notes: Dev Blog editorial meeting summary, December 14, 2023, Thank you to @webcommsat for the summary.
Updates and new post
The WordPress Developer Blog redesign is now live on site. It’s easier to read and better connected to the other Developer Resources. Contributors were asked to browse the new site and if they find something quirky, to let developers know via an issue on the GitHub repo.
There was only one post published since our last meeting:
Extending plugins using custom SlotFills by Ryan Welcher, reviewed by Justin Tadlock, JuanMa Garrido and Mary Baum.
The project board, to follow along, is available on GitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/. There is a new column on the project board: “Needs writer”. (see below).
Posts in Progress:
The Todo-List is growing, and we need to increase efforts to get them published.
Topics in need of a writer
If you are interested in taking on a topic from this list or know someone who would be a good person to writer about them, comment on the Issue or ping The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” @bph in slack either in the #core-dev-blog channel or in a DM.
Posts in need of reviews:
New Topics approved
During the project status section, the question was raised if there should be two additional columns on the project board to be more explicit as to the current state of a topic’s progression to publishing.
The discussion made clear that there is a need for more explicit steps between reviews on a writer’s journey to a published article. It also made clear that more details are needed about the first and second review entail and the responsibilities/task for authors and reviewers.
Birgit will connect with other content producing teams to inquire about their process and learn how they handle reviews in the project boards. Meanwhile, we could test the following workflow for a few articles.
- Writer writes and moves project card to “Ready for 1st review”
- When done, reviewer moves the card to “Done w/ 1st Review”, adding comments to Google Doc or to the issue.
- Writer edits and moves card to Ready for 2nd review
- When done, Reviewer moves card to “Done w/ 2nd Review”, adding comments to Google Doc or to the issue
- Writer edits some more and moves content to Blog – “Ready to Publish”
- “Final Publishing check” – only a separate step for writers getting their first post over the finish line. Experienced writers, use the Pre-publish check list and publish their posts.
The two additional columns are now available on the project board.
Next meeting 1st of February 2024 at 13:00 UTC in the #core-dev-blog channel
Props to @greenshady for review.