Facilitator & Attendance
Facilitator: @felipeelia
Attendance: @milana_cap, @atachibana, @marcio, @bph, @audrasjb, @tjnowell, @nullbyte, @pbrocks, @carike, @tomf, @kulsumsiddique, @nobnob, @kartikshukla, @estelaris, @kenshino, @clorith and @fierevere.
Note-taker: @audrasjb
Next week Facilitator: @kulsumsiddique
Meeting transcript on Slack
DevHub migration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. status
@atachibana shared some stats about this project: 322 of 1069 pages were re-routed from Codex to Code Reference, which is 30.1% of all.
This is one of the ongoing efforts of the Documentation team. If anybody wants to help, they can contact @atachibana via DM or via #docs
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/. channel.
New contributors are encouraged to read this handbook page to learn more about contributing to HelpHub articles.
Discussion on the Docs team organization in general
As WordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Asia is coming, it would be nice to reach an agreement on two items: Team Workflows and Badges distribution.
Team workflow
It refers to reporting an issue about WordPress documentation. There is a Trello board for that. Most workflows are covered, if not all.
@milana_cap hopes to have the Workflows page published in the first week of February.
Badges
Contributors are encouraged to leave comments and suggestions on this post by the end of this week so @milana_cap can start working on a P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org/. proposal.
@felipeelia pointed out the example of someone who noted an error on one of the available docs and asked if they would be elligible to receive the docs contributor badge. @bph noted that it’s a micro-contribution. Several micro-contributions could lead people to receive a contributor badge. @felipeelia pointed out that it would need to keep track of each contribution in a document. @bph added that normally each contributor could keep track of it and let the Team know, when the threshold is reached.
@estalris noted that the design team do triages and people who participate on triages don’t receive a badge, because that is a micro-contribution. Only members with a specific project or role in the team are the ones that receive badges. Note: it’s for the Team badge.
Support team has a 400 replies goal to receive the contributor badge. Becoming a moderator comes with the team badge.
HelpHub
@atachibana is working on the progress and will prepare something for the next meeting.
@kenshino said he would love for that Survey to be ready to be distributed at WC Asia, in one month.
The goal is to build the questions of the survey with the general theme being “How do you think we can improve the WordPress documentation?”. Some questions using the likert scale to track how good it is now so the Team can repeat the survey in the future. Some open fields to get proper feedback so it’s possible to define future projects better.
@estelaris worked on the subcategory issue https://docs.google.com/spreadsheets/d/1qSNKiAwLbc2nLrtGLj4Ndp4-N0daZOfgazlsSYnFXqM/edit?usp=sharing. That was her first draft in trying to organize the articles, but she needs help to define the subcategories.
A discussion started about the relevancy of categorization, but the Team agreed categorization makes sense when there is a lot of content as users would be able to filter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. what they want to look for. @kenshino noted that we’re trying to solve a discovery issue and those won’t be solved with one method. Categorizing them is a start. But a proper search system is also necessary.
@estelaris and @atachibana are going to work together on sub-categorization system.
New readme.txt file for the Developer Handbook
@carike noted that the Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Privacy team discussed the proposed headers for readme.txt
files. There is some debate about whether external calls need to be one item or split into three. Everyone agrees with the headers in general though. Next step is a meta 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. ticket. They cannot update the readme.txt before the new headers are added, as this would lead to confusion.
Custom fields page
@leogermani edited the Custom Fields page as previously discussed. He added an entry to the Workflows card in Trello about Code reference.
#meetings, #summary