Proposal for #docs Channel Extension

*this is a cumulative doc/proposal from the Docs Onboard Team

Purpose

To create an area away from the high traffic active postings in the main channel that new and existing Contributors can go for assistance and support. Members can also ask a quick question in the new channel. This would declutter the existing #docs channel from error reports and questions, while distinguishing it exclusively for docs related discussions.

The idea is to is to have a combination of:

-On Demand Lists (ie: /newcontributor-tasks, /specific-itemlinks, /handbook-sections)

 *returns info we setup

—>> using Slackbot for the lists

-Live in Channel Support (General Operating/Convention QA, Orientation Hub)

Naming

Some ideas for possible naming convention:

#docs-help

#docs-support

—————————————

Reason

At this point, we’ve been direct messaging people and working with them one on one to get started, but this would allow us to have a hub to do so, while information supplied to others could also be of benefit as reference.

Presently, we’ve noticed (especially in the case of new contributors), they tend to get overwhelmed and also intimidated by asking for information in the channel.  We’re also duplicating quite a bit of human effort in the case where we have potential solutions to make this process more efficient.

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 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 reported that for the migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. 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 hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same..

@bph updated on the Bee-Docs (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):

  • Bee-Docs Meeting Participants: @collinsmbaka @tacitonic @khushbu1983 @manthanadmane @MakeWebBetter  
  • @tacitonic has been reviewing posts with new contributors.
  • We are 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/ to fill gaps in WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ documentation
  • 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 finds more usage now that we have more team members on board.
  • @collinsmbaka will connect with the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-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. 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/ 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 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 betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process.-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 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. 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