Attendance

@ninianepress @ninthcoder @leonnugraha @femkreations @atachibana @emmaht @estelaris @thisisyeasin @javiercasares

Housekeeping

• Where: #docs channel on Slack
• Agenda: Docs Team bi-weekly meeting March 7, 2023
• Meeting facilitator: @ninianepress
• Note taker: @ninianepress
• Next meeting facilitator: @leonnugraha
• Next meeting note taker: @ninianepress
• Next triage facilitator: @ninianepress

Find the complete Transcript of the meeting on Slack.

Please note: @ninianepress wrote this summary as @femkreations was unavailable due to other high-priority Documentation Team tasks, and will also write the next summary for similar reasons in place of @estelaris.

Project checks

@wigno updated #497 and #496.

@emmaht reviewed the above tasks, and @leonnugraha published them.

@wigno also finished the draft for #283.

@leonnugraha added links in the End-User Inventory.

@femkreations added related tasks to the 6.2 Project Board in GitHubGitHub 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/:

• Two separate views were created based on the high-priority and medium-priority task labels.
• Tasks on the 6.1 Project Board on GitHub have been organized to only keep ones that have no further updated for WordPress v6.2.

@atachibana completed task #13.

@estelaris mentioned that the Documentation Sitemap was implemented on March 6th.

Discussion on application for Google Season of Docs

The discussion surrounding the application for the Google Season of Docs has been rescheduled to the next meeting.

Check out the additional details in the summary from the previous bi-weekly Docs Team meeting under the same heading.

Collaboration on HelpHub and DevHub redesign request

@estelaris noted the following for translating documentation:

• The HelpHub and DevDocs redesign request post was published to gather information on processes and needs from locale teams.
• @estelaris is presenting and discussing the new documentation sites (HelpHub and DevHub) in a recent WordCampWordCamp 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. and will work with the Spanish team.
• @javiercasares has ideas on how to test/try out ways of translating.
• @estelaris is working on figuring out if we can use the Inventory as a tracker for polyglots so they are aware when we upload new articles.

How to improve the Glossary in WordPress

Also, in terms of collaboration with the marketing team:

• @estelaris is looking into the marketing team’s initiative to move the WordPress Glossary to a different place as a single source of reference for WordPress terms.
• The idea is to replace the many glossaries in the handbooks and make sure we are using the same definition for matching terms.
• Make teams should be in charge of updating and adding new glossary terms, as needed.
• @chanthaboune is aware of this initiative and has requested to be updated so support can be provided.

Update on the Docs inventory

This part of the meeting was unintentionally missed so it will be added to the agenda for the next bi-weekly Docs Team meeting.

Open floor

@estelaris has already reached out to the 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, but asked if any one had suggestions on how to get a page listing for the Support Articles page in Spanish. There are currently no sitemaps on the Rosetta sites:

• @javiercasares suggested an alternate solution if other options aren’t available: Creating a page with the link list by using an APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways.. One currently exists, though, it’s empty.

Please note: As a reminder, Daylight Saving is quickly approaching. In Europe it begins on March 26th and in North America Daylight Saving started on March 12th. Regardless, Documentation Team meetings remain at the same scheduled time of 14:00 UTC.

#docs, #meetings, #summary

Attendance

@ninianepress @ninthcoder @femkreations @estelaris @sereedmedia

Housekeeping

• Where: #docs channel on Slack
• Agenda: Docs Team bi-weekly meeting February 21, 2023
• Meeting facilitator: @ninianepress
• Note taker: @ninianepress
• Next meeting facilitator: @ninianepress
• Next meeting note taker: @femkreations
• Next triage facilitator: @ninianepress

Find the complete Transcript of the meeting on Slack.

Project checks

@leonnugraha worked on the Navigation block article during the WC Asia Contributor Day. Because it’s so outdated, it requires a new document once the WordPress v6.2 release candidateRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. is out. Work on this article will continue then.

@femkreations completed gardening the closed pull requests in GitHubGitHub 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/ from 14.2 through 15.1, and added the “User Documentation” label.

Additionally, 4 issues in 6.0 and 1 issue in 6.1 were closed.

@estelaris mentioned that the biggest ticket for the categorization project – moving technical articles to DevHub with issue #388 – is now closed. A big thank you goes out to @JavierCasares.

Discussion on application for Google Season of Docs

The discussion for a proposed application for the Google Season of Docs has been rescheduled to the next meeting.

Google has a program where you can apply as 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. project. If you get chosen, Google will help you with the project’s documentation.

In 2020, the Documentation Team participated, and our style guide was completed. We need to think of a good project in order to be chosen since the competition is high. @milana_cap is already making inquiries to see if we can participate again this year.

It’s important to note that the application process has changed so this will also need to be considered in future discussion.

@sereedmedia mentioned asynchronously that the glossary may be a great project to apply for and @estelaris agreed.

Open floor

@estelaris is meeting with the Polyglots TeamPolyglots Team Polyglots Team is a group of multilingual translators who work on translating plugins, themes, documentation, and front-facing marketing copy. https://make.wordpress.org/polyglots/teams/. to discuss collaboration on documentation updates.

#docs, #meetings, #summary

Attendance

@ninianepress @milana_cap @leonnugraha @femkreations @estelaris @ninthcoder @JavierCasares @magaliechetrit

Housekeeping

• Where: #docs channel on Slack
• Agenda: Docs Team bi-weekly meeting February 7, 2023
• Meeting facilitator: @ninianepress
• Note taker: @leonnugraha
• Next meeting facilitator: @ninianepress
• Next meeting note taker: @leonnugraha
• Next triage facilitator: @ninianepress

Find the complete Transcript of the meeting on Slack.

Project checks

@milana_cap finished the WordCamp Asia Contributor Day Plan.

@femkreations completed reviewing the closed pull requests (PRs) in GitHubGitHub 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/ for Gutenberg from 14.2 through 15.0, and the User Documentation label was added. Femy also reviewed and closed one WordPress 6.1 issue.

@estelaris posted #652 and #651, but it was later moved to the 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. TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. Ticket #6740.

@leonnugraha reviewed and published #502 and #176.

Discussion on what can be done for the WCAS Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/.

@milana_cap is working on an interactive plan to onboard new contributors.

@milana_cap also organized onboarding sessions for the new non-project roles: Issue Triage Facilitator, Issues Coordinator, and Issues Reviewer. The session will be recorded, and posted on WordPress.tv.

Open floor

@JavierCasares mentioned two meta trac tickets – #6411 and #6714. Both need follow-ups and @milana_cap will leave a comment on the ticket for updates or ask about them in an upcoming meta meeting.

Props to @leonnugraha for writing this meeting summary.

#docs, #meetings, #summary

Attendance

@leonnugraha @ninianepress @milana_cap @estelaris @ninthcoder @atachibana @femkreations

Housekeeping

• Where: #docs channel on Slack
• Agenda: Agenda for Docs Team Bi-Weekly January 24, 2023
• Meeting Facilitator: @leonnugraha
• Note Taker: @ninianepress
• Next Meeting Facilitator: @ninianepress
• Next Meeting Note Taker: @leonnugraha
• Next Triage Facilitator: @ninianepress

Find the complete Transcript of the meeting on Slack.

Project checks

@milana_cap is working on crafting the WCAS Contributor Day task list.

@ninianepress finished issue #128.

Status update for HelpHub

@estelaris walked through the recently finished updates to the End-User Documentation (HelpHub, internally).

For full details of these changes, please see New look, new site, new HelpHub.

Status update for DevHub

@estelaris noted that @javiercasares (not in attendance) is the project lead for the Developer Handbook (DevHub, internally) redesign. She mentioned that the design has been finalized, and development work has begun.

Open floor

@milana_cap mentioned there is a new non-project role in the team that no one has been doing before: GitHub issues coordinator.

@femkreations would also like to note that issue gardening for v6.2 is in progress from the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ pull requests (PRs).

#docs, #meetings, #summary

Attendance

@ninianepress @milana_cap @leonnugraha @femkreations @atachibana @thisisyeasin @estelaris @wigno @vanpariyar @kartiks16 @samanthaxmunoz @ninthcoder @daisyo @webtechpooja @onlykawshar

Housekeeping

• Where: #docs channel on Slack
• Agenda: Agenda for Docs Team Bi-Weekly January 10, 2023
• Meeting Facilitator: @ninianepress
• Note Taker: @leonnugraha
• Next Meeting Facilitator: @ninianepress
• Next Meeting Note Taker: @leonnugraha

Find the complete Transcript of the meeting on Slack.

Moving HelpHub to the New Site

@estelaris is working with the 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 to replace the /support site with the /documentation site. The new URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org is expected to be ready after January 17, 2023. In the meantime, contributors should refrain from adding, editing, or publishing content on the /support site as they will be lost.

Read this post for more information.

Project Checks

@leonnugraha – Reviewed and published #234 and #314

@milana_cap – Almost completed the Team roles page(s)

@ninianepress – Finishing an update that was supposed to be done by the end of 2022

@wigno – Completed #506, and it’s now ready for review. Will plan to work on #508 and #502 this week

Topics for the 2023 WordPress Community Summit

We should think, as a team, of possible topics for the Community Summit. What are the Documentation team needs that can, in full or partially, be solved in an environment where all other teams are present? 

@estelaris proposed the following topic: How will we collaborate with polyglots to translate the documentation and help them create the new sitemap? We need to push for translations. Otherwise, a lot of our work will stagnate as an English version only

@ninianepress wants to submit a topic that @milana_cap mentioned during last year’s WCEU – about a waterfall solution across teams for everyone to be able to collaborate on projects across all teams. @milana_cap added an example that the Training/Learning team has been discussing for a long time with the Docs team on how to make a tool that would help us all communicate better about release changes.

@atachibana pointed out several workflow issues for the HelpHub that can be improved. Through the discussions, we agreed that we could discuss these issues internally within the Docs team.

Open Floor

@wigno volunteered to review and publish documentation content. @leonnugraha will help him to get going.

@milana_cap has an idea for three little tools that should help with some workflows and will build something to test out:

• Meeting agenda generator
• Meeting summary generator
• New contributor orientation tool/onboarding tool

@estelaris will ask the meta team about the users’ access when the /documentation site is live.

Props to @leonnugraha for writing this meeting summary.

#docs, #meetings, #summary