Unfortunately we didn’t see anyone volunteering to take notes for this meeting. Which is why I decided to publish this summary as a consolidated note for the convenience of all. I wish I was made aware of the situation earlier than this.
Ahmed Chaion
Attendance
@kartiks16, @atachibana, @softservenet, @kenshino, @fahimmurshed , @sukafia, @bizanimesh, @justinahinon, @tacitonic, @estelaris, @chaion07, @bph,
Find the Agenda of the Meeting here.
Thanks to @chaion07 for Facilitating the meeting.
House Keeping
Notetaker: We could use a few volunteers to take notes for our weekly meetings. If you want to help then please comment here or let us know during our meetings.
Facilitator for the next meeting: @softservenet
Next Meeting: 19 October 2020
Find the complete Transcript of the meeting on Slack.
Project Updates
@atachibana reported on the migration and re-routing of Codex to Code:
- 32 Classes out 43 have been completed which is an improvement of almost 7% leading to 74.4% from last week’s 67.4%, and
- 62 Hooks out of 355 have been completed which is an improvement of 3.1% leading to 17.5% from last week’s 14.4%.
- @atachibana thanked @stevenlinx for the contribution.
@justinahinon provided update on the Gutenberg Developer Documentation:
- Last week during #core-js offices hours there was a discussion about the uses cases of the new Gutenberg developer documentation. Reference: https://make.wordpress.org/docs/2020/08/13/plan-proposal-for-a-new-better-structured-gutenberg-developer-documentation/
- A new use case document is being currently filled
- So if anyone have a use case in mind for the documentation, feel free to suggest with comments or update the document.
@bph also provided an update beforehand on Digital check in for Block-Editor End User Documentation (BEE-docs). Birgit requested that the BEE-docs team members leave comments on that post. (asynch to the meeting)
She also informed that with the help of many contributors the team collectively passed the 50% milestone for pages catching up to 5.5
The team couldn’t discuss the following agenda items due to dependency on @milana_cap and others:
Q3 Update
@kenshino shared a link: https://docs.google.com/document/d/18R79xWKOBp6Hosfs7Ao2kh-lFfhP3mR-4AbR4_BbeOo/edit# containing the Q3 Update Document for everyone to collaborate. He requested the members responsible for their team to add information respectively for a collective update. This collective information will be shared as ‘Team Updates’ that is posted in Updates Blog similar to the Quarterly Updates | Q2 2020
New Member Mentoring
@softservenet provided update as following:
- The members of the team is focusing on taking turns to onboard new contributors to the #docs Team.
- Anyone who has recently joined the team or still looking to find ways towards their first contribution should contact a member of the ‘New Member Mentoring Team’.
- The Team is working on improving the process with task coordination for new members.
Monthly Coffee Break Reminder (October 2020)
@sukafia provided information on this agenda item:
- The coffee break is taking place on the 29th of October, 12:00 UTC (with a EU-friendly time).
- Please DM @sukafia or @chaion07 to get a calendar invite.
Meeting Times
There has been a broad discussion on the meeting time that may be suitable for majority of the team members. However it has proven to be very difficult with the DST (daylight saving time) practiced in different parts of the world. Reference to the discussion: https://wordpress.slack.com/archives/C02RP4WU5/p1602518383390100
Google Season of Docs 2020
Diana Mivelli provided update as following:
- Been reviewing HelpHub articles and titles and recommending title updates.
- Trying to make sure article titles adhere to sentence-case capitalization style (instead of title case) and suggesting titles away from gerunds.
- Taking note of some overlapping content/duplicate content articles accordingly.
- Discussing the ways to managing these suggestions as they come up with @estelaris.
@tacitonic provided update too:
- About to finish the Language and Grammar section.
- Updated the progress in the README file daily: https://github.com/WordPress/WordPress-Documentation-Style-Guide
- The style guide markdown importing and parsing (from GitHub to wp.org) is underway.
- Extended the project duration from the standard length (3 months) to a long running project (5 months) upon I discussion with mentors, and found it appropriate to extend it owing to multiple factors.
Open Floor
@mkaz brought the discussion about ‘comments on Handbook‘. Reference to the discussion can be found here: https://wordpress.slack.com/archives/C02RP4WU5/p1602519419426800
@bph shared a link to the ticket in reference to the topic discussion.