Summary for Docs Team Meeting: July 27, 2020

Attendance

@atachibana @marcio-zebedeu @sukafia @milana_cap @chaion07 @bph @ibdz @collinsmbaka @estelaris @crstauf  @themiked @kenshino @prubhtej @tacitonic @lvg2013 @softservenet @b-07 @glorialchemica @khushbu1983 @kafleg @fierevere @mohitmishra @darkog

Agenda

You can find the Agenda here.

Notetaker: @b-07

Notes Reviewed by: @collinsmbaka and @tacitonic

Facilitator: @tacitonic

Facilitator for Next Meeting: @tacitonic

Follow the meeting on the Slack channel for Docs

Project Updates

@atachibana: For re-routing of Codex to Code Reference, 1049 of 1070 (98.0% <- 97.1%) Function pages have been completed.

@stevenlinx & @collinsmbaka are processing complex cases with opened tickets.

BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. Editor End-User Documentation (BEEDocs):

@collinsmbaka: Published issuu, crowdsignal, and reverbnation blocks & reviewed the TrelloTrello Project management system using the concepts of boards and cards to organize tasks in a sane way. This is what the make.wordpress.com/marketing team uses for example: https://trello.com/b/8UGHVBu8/wp-marketing. board.

@tacitonic: Arranged the task list spreadsheet priority-wise, got in touch with the contributors who have claimed blocks but are not worked upon.

@bph: Started looking at WordPress.comWordPress.com An online implementation of WordPress code that lets you immediately access a new WordPress environment to publish your content. WordPress.com is a private company owned by Automattic that hosts the largest multisite in the world. This is arguably the best place to start blogging if you have never touched WordPress before. https://wordpress.com/ documentation to see what can be ‘harvested’, reviewed contributors documents, in the works and already published, with @atachibana worked on Block Directory documentation, started on a third worksheet in our spreadsheet with WordPress 5.5 and more task listing: BlockPattern, Image Editing, Block Directory.

@khushbu1983: Published articles reviewed by @tacitonic from spreadsheet.

External Linking Policy

@milana_cap reported that she didn’t manage to do anything new on this agenda. But she’ll be sharing Google docs soon with this so we all can comment and join the discussion. She also mentioned that the team is trying to change the strategy because it’s impossible to label websites as “commercial” and “personal” only. So they’ll focus on the license, which has to be compatible with GPLGPL GPL is an acronym for GNU Public License. It is the standard license WordPress uses for Open Source licensing https://wordpress.org/about/license/. The GPL is a ‘copyleft’ license https://www.gnu.org/licenses/copyleft.en.html. This means that derivative work can only be distributed under the same license terms. This is in distinction to permissive free software licenses, of which the BSD license and the MIT License are widely used examples. 2+.

New Member Mentor Training

@Prubhtej provided a new member update: 4 new members joined docs last week; docs has added 33 new members for July. @sukafia mentioned that most of the new members joined last week came from other teams to ask specific questions. @softservenett has written a post for the docs channel extension: https://make.wordpress.org/docs/2020/07/20/proposal-for-docs-channel-extension/

Monthly Coffee Break

The July Coffee Break is set for this Thursday (July 30) at 1500 UTC.

Google Season of Docs 2020

@kenshino reported that they’re still evaluating proposals. The deadline for evaluating the proposals is 28th July. 

Open Floor

@bph mentioned that the next Block Editor Enduser documentation team meeting will be on August 10. 

@themiked mentioned that he’s concerned about the way of doing the ‘keep the content promotion free’ part. He also mentioned that defining content and promotion is going to be a challenge and he’s looking forward to seeing the first draft. 

Please feel welcome to suggest revisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. in the comments.

#docs, #meeting-notes, #meetings, #notes

Summary of Docs Team Meeting for July 20, 2020

Attendance

@atachibana, @bph, @burhandodhy, @chaion07, @collinsmbaka, @crstauf, @daverick, @deadpool76, @estelaris, @FahimMurshed, @ibdz, @kartiks16, @Kenshino, @Leslie, @manthanadmane, @mkaz, @mohitmishra, @nullbyte, @Prubhtej, @ramiy, @saiftheboss7, @sasiddiqui, @sncoker, @softservenet, @tacitonic, @themiked, @timohaver, @williampatton (28 people attending)

Meeting 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.

Meeting Agenda: https://make.wordpress.org/docs/2020/07/20/agenda-for-docs-team-meeting-july-20-2020/

Meeting Transcript: https://wordpress.slack.com/archives/C02RP4WU5/p1595257204344100

Meeting Facilitator: @chaion07

Meeting Notes by: @timohaver

Facilitator for Next Meeting: @tacitonic

Follow docs team meetings on the WordPress.org Slack workspace by joining the # docs channel.

Project Updates

@atachibana reported that almost all work is complete for the migration and re-routing of Codex to Code Reference for Functions. @stevenlinx and @collinsmbaka are working through the more complex cases that remain. 

@bph itemized the many activities of the Block Editor End-user documentation team (BEE-docs). The team is balancing ongoing work for WordPress 5.4 with preparations for 5.5.

@mkaz published his Create a Block tutorial in the Block Editor Handbook

External Linking Policy

With @milana_cap unavailable, @Kenshino proposed deferring this agenda item to the next meeting. @chaion07 asked everyone to comment on the recent posts relating to this topic

Google Season of Docs 2020

@Kenshino reported that @cbringmann is working with Season of Docs mentors to review GSOD proposals.

New Member Mentor Training

@Prubhtej provided a new member update: seven new members joined docs last week; docs has added 29 new members for July.

@softservenet published a post proposing additional Slack channels for new member engagement.

Monthly Coffee Break

@chaion07 promised there will be a Doodle up soon with APAC-friendly options for choosing a day and time. He estimated that the next Coffee Break will happen in the last week of July.

Open Floor

On behalf of the Marketing team, @nullbyte asked how to go about publishing a FAQ for WordPress 5.5 on HelpHub and DevHub.


Please feel welcome to suggest revisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. in the comments.

#meeting-notes, #meetings, #notes

Summary for Docs Team Meeting on 29th June 2020

Attendance

@kenshino, @sukafia, @chaion07, @tacitonic, @atachibana, @kenshino, @sukafia, @chaion07, @tacitonic, @atachibana, @cristiano.zanca, @glorialchemica, @wpza, @mkaz, @crstauf, @milana_cap, @fahimmurshed, @Prubhtej_9, @estelaris, @tomjn, @timohaver, @yui, @mte90, @newyorkerlaura, @bph, @collinsmbaka, @ataurr, @softservenet, @imneet94, @abutalha94, @ibdz, @manthanadmane, @themiked, @mekalekahi.

Find the Agenda of the Meeting here.

Thanks to @kenshino for Facilitating the Meeting.

Notetaker & Facilitator Selection

Notetaker: @chaion07

Facilitator for the next meeting: @chaion07

Next Meeting will be held on: 06 July 2020

Find the complete Transcript of the meeting on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

Project Updates

@atachibana informed that 1014 out of 1070 pages had been completed. Currently the project is at 94.8% completion which is a 0.80% improvement from last week. He also thanked @stevenlinx for the contribution.

@bph reported that the Bee-Docs Meetings are held every Mondays at 14:00 UTC in #meta-helphub. Meetings start with the following items for contributor check-in:

  1. What have you been working on?
  2. What do you want to work on next?
  3. What are your blockers, (apart from time and 
  4. handling any blockers.

@bph also thanked @tacitonic for his committed work with new contributors, reviewing and publishing articles. The team is currently also working on the following:

  • Documentation for TrelloTrello Project management system using the concepts of boards and cards to organize tasks in a sane way. This is what the make.wordpress.com/marketing team uses for example: https://trello.com/b/8UGHVBu8/wp-marketing. board so all contributors know how to work in it and so that we can all track what’s going on
  • WordPress.comWordPress.com An online implementation of WordPress code that lets you immediately access a new WordPress environment to publish your content. WordPress.com is a private company owned by Automattic that hosts the largest multisite in the world. This is arguably the best place to start blogging if you have never touched WordPress before. https://wordpress.com/ documentation to fill some of our gaps and get a head start on some 5.5 features.

Categorization Project

@kenshino mentioned about @swissspidy‘s contributing to a XML Sitemap Documentation too.

@estelaris wrote a p2 post on classification and appreciated everyone who commented. The deadline for comments is set as 5 July 21:59 UTC. The team will again discuss this at the next weekly meeting on 06 July 2020. @estelaris and @ibdz will get together this week to continue with the design, leaving navigation aside until we resolve the classification.

@milana_cap is currently overseeing the work on BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. Editor Docs for developers and she invited everyone to get involved with this tutorial prepared by @makz and it needs testing.

@makz added by saying that ‘The Create a Block’ Tutorial got merged in, but not linked up yet and still need to add Block Directory updates which you can browse on Github.

@christiano.zanca shared the news of Italian HelpHub being started. You can visit https://it.wordpress.org/support/ and experience it first hand.

External Linking Policy

@milana_cap is thinking of parts of the process as:

  • Proposal made by anyone (for external resource) – perhaps prepare a template
  • Review by Docs team members – need a list of criteria for this
  • Public post about proposal, review and reasons for acceptance/rejecting; and
  • Add resources to the public list of “Allowed resources”.

For the ‘list of requirements’ she’s thinking about the following types of resources:

  • Personal blogs
  • Tutorial sites (Udemy, Coursera, Skillshare, etc.)
  • Forums (Stack Overflow, TechRepublic, etc.)
  • Commercial blog (Not Allowed)

You can join the conversation by visiting the p2 post related to this topic. @milana_cap is considering writing another p2 post on this.

New Member Mentoring Team

@sukafia reported that the Mentoring Team is actively reaching out and checking up on new members. The team is ensuring that every member gets a Welcome Message and is provided with links to helpful resources and guidance relevant to #docs. 5 new members have joined since last week, raising the numbers for this month to 68. The ‘New Member Mentoring Team’ will be having a meeting  to discuss our next steps & ways to improve the mentorship initiative.

You can contact @sukafia, @softservenet, @tacitonic or @Prubhtej_9 with your ideas, suggestions and comments.

Monthly Coffee Break (June 2020 Updates)

We have 12 people joining in the Monthly Coffee Break for June where we have discussed informal topics and tried to understand each other. We have received positive feedback from participants so @sukafia will create another Doodle for the month of July and share it in the #docs channel. 

@chaion07 will volunteer alongside @sukafia to continue writing a monthly summary piece on the coffee break in the form of a p2 post.

Google Season of Docs

All Technical Writers who are interested to participate in the Google Season of Docs for 2020 are requested to comment in this p2 post. A lot of the mentors have their designated Google Form or other means of communication to submit their ‘expression of interest’ by the technical writers. Technical Writers are requested to follow the guidelines provided by the Mentors for their specific project idea as mentioned in the post. You can also comment in the #docs channel and tag your Mentor for faster communications if needed.

End of Meeting Notes

#meetings, #notes

Summary for Docs Team Meeting for June 8, 2020

Attendance

@atachibana @bph @chaion07 @cguntur @collinsmbaka @estelaris @Femy @ibdz @kmeze @MakeWebBetter @manthanadmane @marcio-zebedeu @mkaz @Prubhtej @rbest @Ruchit @Sunday @tacitonic @timohaver @tomf
(20 people attending) 

Meeting 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.

Agenda: https://make.wordpress.org/docs/2020/06/08/agenda-for-docs-team-meeting-june-08-2020/

Meeting Facilitator: @chaion07

Meeting Notes by: @timohaver

Notes Reviewed by: @collinsmbaka

Facilitator for Next Meeting: @collinsmbaka

Follow the docs team meeting on the WordPress.org Slack workspace by joining the # docs channel.

Project Updates

@atachibana expressed thanks to all WCEU contributors, reporting more progress for the re-routing of Codex to Code Reference for Functions: now 987 of 1070 (92.2%) complete. 

@bph extended a welcome to all new contributors to blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor end-user documentation. Following a strong response from WCEU 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/., she is still catching up to reviewing new work. Half the work on the new contributor list has been published. The team also added more editors to make updates and correct errors. Going forward, she is transitioning team communication to the #meta-helphub channel.

@mkaz is seeking feedback for a draft version of the Create a Block tutorial in 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/ developer documentation.

Categorization Project, Alterations Workflow, User Stories

@estelaris will write a P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org/. post on current journey mapping on documentation. 

New Member Mentor Training

@Sunday plans to resume new contributor sessions next week, after a two week pause due to WCEU. @tomf reports that the mentoring team has been noting all the new docs team arrivals and has plans to reach out.

WCEU Contributor Day Wrap Up

This will come from @zzap who was not available for this week’s meeting. 

Monthly Coffee Breaks/Zoom sessions

@chaion07 asked everyone to participate in @Sunday‘s Doodle (online poll) to help determine the best prospective meeting times. @tomf suggested that perhaps the meeting time should alternate monthly, if there isn’t a time that is practical for everyone.

Open Floor 

Based on recent reporting about Instagram, @bph raised a copyright concern relating to the use of embed blocks. She asked for feedback for adding a general disclaimer to embed blocks’ documentation.


Please feel welcome to suggest meeting notes revisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. in the comments.

#meeting-notes, #meetings, #notes

Summary for Docs Team Meeting: April 6, 2020

Attendance

@milana_cap, @chaion07, @sasiddiqui, @atachibana, @christiano.zanca, @kafleg, @softservenet, @ataurr, @marcio-zebedeu, @bph, @yui, @sukafia, @aion11, @estelaris, @nobnob, @stefanocassone, @kenshino, @themiked, @joyously

Notetaker & Facilitator Selection

Note @chaion07

Notes Reviewed by: @milana_cap

Facilitator for the next meeting: @sukafia

Next Meeting will be held on: April 13, 2020

Categorization Project, Alterations Workflow (discussion)

@estelaris shared the link of the spreadsheet for the project. https://docs.google.com/spreadsheets/d/1_Ea2yeF5Rfy_YDk7pBRJ4rdljhMjygXFqBq8gWwhbaE/edit#gid=1431454973 She suggested that the entire team should start adding stories to that page, so we can conclude on the main categories and the subcategories the idea is that we can think as a user, following the workflow to build a site. The names in brackets were meant more like the article, not the categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging..

@milana_cap advised that the text in brackets should be of raw categorization and if it can be moved to a separate column and there was no mention of User.

@softservenet asked if any decisions were made to use themes on those 3 labels.

@themiked added saying that he wants to pay better attention at his local WP beginner meetups (whenever that takes place the next time) and see if there are questions asked which would be a good fit here.

@softservenet pointed that we had 3 main categories decided from the previous meeting.

@milana_cap emphasized moving it to a separate column as it can possibly be a mess after over 10 stories has been written.

@themiked warned as soon as we start to try and funnel towards predefined categories, those categories will start to define the questions. Categorization should be the last step, if it’s even needed at all.

@milana_cap invited everyone to add more user stories and use existing ones as an example.

@estelaris further added categorization is needed to improve search but yes, that is the goal for this exercise. She also encouraged everyone to bring a predefined categorization for the next meeting so that we can discuss it.

@milana_cap asked @estelaris about the deadline for ‘User Stories’ to which @milana_cap suggested to have 7 days to add as many stories as possible.

Project Updates

@atachibana provided updates on Re-routing of the Codex page to Code Reference for Functions, where 443 out of 1069 that is 41.4% is complete Thanks to @stevenlinx (as always). He also mentioned that @collinsmbaka and @sukafia had also contributed to the cause.

@estelaris reminded everyone to add their respective WordPress Usernames to the working document so that it can be added to the contributors list at the end of the project.

@chaion07 reported that he had applied for the HelpHub for BN_BD to be added to the site https://bn.wordpress.org/ with a support ticket.

@christiano.zanca informed that the Italy HelpHub Team is using the italian Polyglots way of translating: using Google docs and some sorts of per-translation methods. Thus it is taking longer than usual. @milana_cap asked if it would be moved to Rosetta later and if so then it should be alright. This is a huge project and every team should find their own way to be most productive. @christiano.zanca shared the link of the tool they are using: ttps://wp-info.org/tools/helphubchanges.php to which @milana_cap suggested of another one that she had developed which compares locale with original including the last modified dates so you can see if your version is outdated or not. Link: https://developerka.org/helphub-updates/

@themiked provided updates on the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party handbook that he is 20% through reviewing content and converting from classic blocks into actual blocks. He discussed having 2 items specifically. The first one is the external linking, which is also being discussed in the blog. While visiting the cpt section it seemed natural to link to generatewp, but we need a decision beforehand. So this is more of a reminder. The second one is that the plugin related content in the codex seems to be much more feature complete, so if it should be rolled into the plugin handbook, or we should be referring to it. Either way, having the same or similar content in two places may seem confusing and wasteful. @milana_cap shared the associated link: https://make.wordpress.org/docs/2020/03/16/external-linking-in-docs-policy/ She further added that it is wasteful and a nightmare for maintenance. She further suggested that the next step should be to create the list of exact content and then we can decide if it should be moved to developer handbooks or somewhere else or just leave it as is.

@joyously questioned on the perspectives of the write up should be either on using a plugin or writing  for a plugin. To which @themiked replied with both revolve around writing and suggested a link: https://codex.wordpress.org/Writing_a_Plugin and more generally https://codex.wordpress.org/

@atachibana added that our big goal is the retirement of Codex. So the required portion should be moved to the Plugin Handbook or appropriately handbook, developer hub or so.

@themiked summarized with a suggestion that he’ll get through the existing content and then slurp it in and eventually get through the existing handbook content, then slurp in the Write a Plugin content.

Handbook Revamp

  1. Facilitating weekly meetings
  1. Reporting an issue workflow
  • @milana_cap shared the link to TrelloTrello Project management system using the concepts of boards and cards to organize tasks in a sane way. This is what the make.wordpress.com/marketing team uses for example: https://trello.com/b/8UGHVBu8/wp-marketing. board: https://trello.com/c/GNXYppYS/44-workflows further added, the second one is not really a draft and requested others to add their items and steps. The idea is to help people report issues for every docs project by following simple step-by-step instructions.
  • @softservenet shared the idea of creating a card for each discussion issue (with the minimum summary information) and posting it in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/., same for new issues. Eventually we’ll work on transferring the information to the actual document. That way, for new issues, we can always direct to the card for required information and we’ll have a better understanding of it hopefully.
  • @bph didn’t report any progress. Except discussing with @jdy68 about reusable blocks in English pages, that don’t show up for translators. Link: https://wordpress.slack.com/archives/C02RP4WU5/p1586119655314100

Open Floor

  • Google Season of the Docs

@kenshino reported that he reached out to @chanthaboune to talk about the Season of Docs and is currently waiting to hear back. He is assuming to maybe get some updates in the coming week. @milana_cap agreed and also added that we wanted to do it last year as well but now it’s a good time for us to get professional help on writing technical docs. Link: https://opensource.googleblog.com/2020/03/announcing-season-of-docs-2020.html @softservenet inquired on what would our suitable position be in this? @milana_cap shared the idea as a reply that the Docs Team to be working with professional technical writers. We will explain to them what WordPress is and how it works and they will help us write better technical docs. @kenshino shared the details with the organization terms. Link:  https://developers.google.com/season-of-docs/terms/organization-terms

  • Categorization

@estelaris was interested to join in the discussion of categorization as she thinks that she has lots of info to provide and we will need help to finish up that part of the project. @softservenet replied, If @milana_cap takes the lead, I’d be willing to accept some type of position in this structure.

  • Mentoring Program Proposal

@sukafia felt the need to have someone who would focus on helping with the on-boarding of new members. That’s instead of everyone focusing on contributing to docs, helping new members settle in and this role should be recognized as a contribution to the Docs team. Updates should be given for new members and they should be followed up until they find a footing. He further added that it was difficult to settle in and had recently discussed with new members who feel the same way. @milana_cap agreed, that we are aware of it and we have been thinking about that problem for years. One solution could be to have mentoring program as suggested. She further added saying, every team repTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. should be mentor for their project but we don’t have enough people to mentor and do the work and if we have one mentor for all, it wouldn’t work. She even requested @sukafia to write a p2 post about that and we can all discuss it there. @kenshino suggested that the person doesn’t have to know everything about all projects – just where they can get started and a general high level understanding would be good enough. @sukafia expressed his interest in volunteering for this role if we decide it’s necessary. @softservenet A newer person would be better in tune with the challenges of getting started. Many of us have the history from meetings and the continual process, so they would better understand that challenge

  • Handbook

@estelaris asked if there is a page in the handbook that discusses the projects that the team is working on? The design team has a FOCUS page only for that. I assume it’s often updated. Here is the page and yes, it is often updated https://make.wordpress.org/design/handbook/focuses/ @milana_cap said that she’ll add this to ‘the to do list’ for Handbook.

Transcript of the meeting can be found here on slack

Thank you all & please stay safe!

#meetings, #notes