Attendance
@kenshino, @wpza, @sasiddiqui, @atachibana, @milana_cap, @felipeloureirosantos, @bph, @leogermani, @estelaris, @nobnob, @sukafia, @tomf, @marcio-zebedeu
Facilitator: @kenshino
Note taker: @valentinbora
Actionable points
- @everyone to review and give feedback on the Handbook refresh efforts here
- @leogermani to spearhead Handbook refresh efforts, @milana_cap to help with feedback
- @leogermani to open a ticket on Trac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. regarding #meta statistics and invite @kenshino to draw attention from the appropriate stakeholders
- @tomf to audit content for outdated or irrelevant WordPress.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/ links and compile a list
- @estelaris to write up notes from the WCVienna working session on classifying docs and post them on this site
Next meeting
Monday, February 24, 2020, 15:00 UTC on Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. #docs (follow here)
Handbook refresh
For the detailed document, see @leogermani‘s New Handbook pages on Google Docs.
@leogermani gave an update on the Handbook refresh effort and found out that the “Welcome box” is really outdated with confusing links, so he started a proposal to change that as well as give the Handbook a new home page with a short overview and links to more detailed pages
@leogermani also raised the issue about our internal codenames such as DevHub and HelpHub which can be confusing for end-users, so instead he decided in favor of using developer.wordpress.org and wordpress.org/support, respectively
@kenshino agreed we should stop using codenames in public information and address them by their URL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org only or both codename + url.
@milana_cap mentioned that we might still want to explain our codenames on specific detail pages in order to help users find the appropriate Components on the Meta Trac when they wanted to raise issues
WordPress.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/ vs. WordPress.com
@sukafia raised the WordPress.org vs. WordPress.com issue again (reminder: people confuse the two when looking for help, documentation)
@tomf added that they had the same issue during content migration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. where they noticed some content linking to WordPress.com docs when it shouldn’t have (we’re only concerned with WordPress.org here)
@kenshino asked whether we had a list of content that contains outdated or irrelevant WordPress.com links and @tomf answered that we didn’t. As such, @tomf agreed to lead the effort to audit content and compile a list
Open Floor
@leogermani was tasked with reaching out to #meta for statistics but didn’t receive anything back yet and doesn’t know who to specifically reach out to. @kenshino suggested to have a ticket open on Trac to help make it happen
@estelaris organized an interactive session at WCVienna this past weekend and together reviewed a series of articles and classified them with proper categories and subcategories
For context, there is an ongoing effort to reorganize WordPress.org documentation. For details, see Working File – HelpHub Article Categories
@estelaris mentioned that some articles didn’t have proper titles, other articles were (very) outdated and finally some articles were redundant in that they only linked to other pages
@estelaris agreed to @kenshino‘s invitation to write up some notes from the working session and post them on this site
@kenshino observed the efforts of @estelaris (Categorization) and @tomf (Content Audit) to be complementary and recommended they worked together
@kenshino mentioned that @coffee2code updated everyone with the appropriate Team and Contributor badges. Also, there’s a list of people that shouldn’t be holding a Team badge anymore due to inactivity
Transcript
https://wordpress.slack.com/archives/C02RP4WU5/p1581951613217400
#docs, #meetings, #summary
