Summary for Docs Team Meeting : July 14, 2020


Attendance: @crstauf, @chaion07, @collinsmbaka, @prubhtej, @milana_cap, @atachibana, @timohaver, @glorialchemica, @saiftheboss7, @tacitonic, @tomf, @bph, @MakeWebBetter, @cristiano.zanca, @sasiddiqui, @mkaz, @theMikeD, @Kenshino, @Manik, @sukafia, @estelaris, @manthanadmane, @Rakib, @thisisyeasin, @khushbu1983

Agenda: For reference, you may view the meeting agenda post for 7-13-2020 

Note-taker: @prubhtej

Notes Reviewed by: @chaion07

Facilitator: @tacitonic

Facilitator for Next Meeting: @chaion07

Follow the docs team meeting on the Making WordPress Slack Channel for Documentation

Find the complete Transcript of the meeting on Slack.

Project Updates

@atachibana reported that for the migration and re-routing of Codex to Code Reference for Functions, 1033 of 1070 (96.5% <- 95.5%) pages have been completed. He thanked @stevenlinx for the contribution with open tickets. He also mentioned that we have to wait until version 5.5 release and enhancement of document fixes to Code Reference for 100%.

@makewebbetter offered to volunteer for working on migrating hooks.

@bph updated on the Bee-Docs (Block Editor End-user):

  • Bee-Docs Meeting Participants: @collinsmbaka @tacitonic @khushbu1983 @manthanadmane @MakeWebBetter  
  • @tacitonic has been reviewing posts with new contributors.
  • We are looking at WordPress.com to fill gaps in WordPress.org documentation
  • The Trello board finds more usage now that we have more team members on board.
  • @collinsmbaka will connect with the core-editors regarding plans for Hulu and Photobucket embeds blocks, if they are abandoned or if we should file issues for them.
  • WordPress 5.5 is coming fast now. Gutenberg plugin versions 8.5 and lower will come to core. Including the import button for external images. So we can keep drafting and collaborating on Google Docs and copy/paste for publishing. The button appears on each image block, and just needs click to get the image into the media library of wordpress.org
  • Also shared the beta-tester plugin with the team in case they want to do some peek preview. We’ll keep and eye out for the denotes, too.
  • good news/bad news: We ran out of tasks for new contributors:
  • Homework for next week for all:  thinking about new tasks for  new contributors early wins. 

The Bee-Docs team meets each Monday at 14:00 UTC in the #meta-helphub channel over Slack.

@Prubhtej_9 reported that he completed the Scribd block editor documentation earlier that week & thanked @tacitonic for reviewing the doc.

@christiano.zanca reported that @glorialchemica started testing italian helphub translation. The Italian Team is providing support to this ticket to onboard more contributors.

Categorization Project

@estelaris reminded that we can still leave comments on the p2 post and this agenda item will be on hold until the finalization of Technical Writers for this project on the Season of Docs.

@bph suggested that we might need to review how block editor end user documentation is presented. It’s kind of buried, and probably needs a separate entrance and TOC.

External Linking Policy

We’ve witnessed vivid discussion on this agenda item.

@milana_cap proposed the following:

  • Anyone with a WordPress.org username can propose the link (as equivalent to anyone with a WordPress.org account can edit Codex). We could have a Google form or airtable or something similar. They need to fill out following fields (all mandatory):
  • External link
  • Placement link at wp.org (where this external link should be added to)
  • Short description (why this link is a good fit)
  • WordPress.org username
  • Consent (“I read the external linking policy rules…” checkbox)

If the proposed domain name appears to not follow the rules 3 times, the domain name gets on the “banned” list.

Review Process:

To make the review process less confusing, we can prepare the set of questions to which all answers have to be “yes” in order to allow a link.

  • 3 members of docs team completes a review (to avoid bias)
  • The review results are published on #docs team blog
  • domain name gets 5 links approved get the “trusted” status and we add them to the public list of trusted resources
  • If one allowed external link gets changed after being approved in a way that is against the rules, all links from that domain get removed, domain name loses its “trusted” status (with possibility to land on “banned” list perhaps?)

The Rules: (Brainstorming Ideas)

  • The content (article/tutorial) must not include any plugin, theme, service (hosting and similar) that is not bundled with WordPress clean install (which can be downloaded at WordPress.org)
  • The content, in its entirety or parts, must not be behind the payment or any sort of compensation from the reader (like, share etc)
  • The page where the content is can not contain visible ads for paid products and services (link in menu is OK but banners are not)

@kenshino suggested When people submit links, one of 2 things can happen

  • The link is added directly
  • The content is copied because it’s really good and they get attributed

The discussion centered from trusted links to commercial blogs, tutorials, promoting products, banners, attribution and even GPL licensing.

The entire conversation can be found here: https://wordpress.slack.com/archives/C02RP4WU5/p1594653710205500 

We request input from everyone. There are many aspects to policy making. Please join the conversation on the respective p2 post on commercial blogs and  trusted sources.

New Member Mentor Training

@Prubhtej_9 reported that for the month of July 22 new members had joined & 13 new members had joined #docs in the past week.

Due to the unavailability of @sukafia & @tomf the discussion on #docs-help channel was postponed to next week.

Monthly coffee break

@chaion07 reported that he’s still in the process of writing a p2 post, which he had volunteered for. @sukafia is assisting with the p2 post.

Google Season of Docs

@Kenshino(jon) suggested that the ‘Documentation Team’ badge be given to the selected Technical Writers and Mentors for Google Season of Docs. He also mentioned that @ChloéBringmann along with the Mentors are finalizing the selection of the Technical Writers which needs to be reviewed by Google as well.

Open Floor

@tacitonic reported that @Lucila Stancatohad contacted him regarding the following matter:https://wordpress.slack.com/archives/C02RP4WU5/p1594123868113500

@chaion07 offered to make a specific Meeting Summary and Meeting Agenda Document Template in Google Docs so that anyone as a New Contributor can find a direct guideline to assist with the Note taking process & requested to write a p2 post for the same.

@kenshino(jon) also reported that he had shut down the wp-helphub.com server.

#meeting-notes, #meetings