Tag Archives: meetings

Jenni McKinnon 6:00 am on January 9, 2023
Tags: , meetings,   

Summary for Docs Team meeting, January 10, 2023

Attendance

@ninianepress @milana_cap @leonnugraha @femkreations @atachibana @thisisyeasin @estelaris @wigno @vanpariyar @kartiks16 @samanthaxmunoz @ninthcoder @daisyo @webtechpooja @onlykawshar

Housekeeping

Find the complete Transcript of the meeting on Slack.

Moving HelpHub to the New Site

@estelaris is working with the 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. team to replace the /support site with the /documentation site. The new URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org is expected to be ready after January 17, 2023. In the meantime, contributors should refrain from adding, editing, or publishing content on the /support site as they will be lost.

Read this post for more information.

Project Checks

@leonnugraha – Reviewed and published #234 and #314

@milana_cap – Almost completed the Team roles page(s)

@ninianepress – Finishing an update that was supposed to be done by the end of 2022

@wigno – Completed #506, and it’s now ready for review. Will plan to work on #508 and #502 this week

Topics for the 2023 WordPress Community Summit

We should think, as a team, of possible topics for the Community Summit. What are the Documentation team needs that can, in full or partially, be solved in an environment where all other teams are present? 

@estelaris proposed the following topic: How will we collaborate with polyglots to translate the documentation and help them create the new sitemap? We need to push for translations. Otherwise, a lot of our work will stagnate as an English version only

@ninianepress wants to submit a topic that @milana_cap mentioned during last year’s WCEU – about a waterfall solution across teams for everyone to be able to collaborate on projects across all teams. @milana_cap added an example that the Training/Learning team has been discussing for a long time with the Docs team on how to make a tool that would help us all communicate better about release changes.

@atachibana pointed out several workflow issues for the HelpHub that can be improved. Through the discussions, we agreed that we could discuss these issues internally within the Docs team.

Open Floor

@wigno volunteered to review and publish documentation content. @leonnugraha will help him to get going.

@milana_cap has an idea for three little tools that should help with some workflows and will build something to test out:

  • Meeting agenda generator
  • Meeting summary generator
  • New contributor orientation tool/onboarding tool

@estelaris will ask the meta team about the users’ access when the /documentation site is live.

Props to @leonnugraha for writing this meeting summary.

#docs, #meetings, #summary

Jenni McKinnon 10:09 pm on January 4, 2023
Tags: , meetings   

Agenda for Docs Team Bi-Weekly January 10, 2023

The next meeting is scheduled with the following details:

When: Tuesday, 10 January, 2023, 02:00 PM UTC

Where: #docs channel on Slack

Agenda:

  1. Attendance
  2. Note-taker and facilitator selection for next meeting
  3. Facilitator selection for next triage meeting
  4. Projects checks
  5. Collaborate on topics to submit for the 2023 WordPress Community Summit
  6. Open floor

If there’s anything you’d like to discuss on the open floor, please leave the comment below.

#agenda, #meetings

Jenni McKinnon 1:05 pm on December 13, 2022
Tags: , meetings   

Agenda for Docs Team Bi-Weekly Meeting December 13, 2022

The next meeting is scheduled with the following details:

When: Tuesday, 13 December, 2022, 02:00 PM UTC

Where: #docs channel on Slack

Agenda:

  1. Attendance
  2. Projects checks
  3. Documentation team holiday schedule
  4. Note-taker and facilitator selection for next meeting
  5. Open floor

If there’s anything you’d like to discuss on the open floor, please leave the comment below.

#agenda, #meetings

Estela Rueda 9:18 pm on November 14, 2022
Tags: , meetings   

The next meeting is scheduled with the following details:

When: Tuesday, 15 November, 2022, 04:00 PM GMT+1

Where: #docs channel on Slack

Agenda:

  1. Attendance
  2. Note-taker & Facilitator selection for Next Meeting
  3. Projects checks
  4. Alterations on HelpHub design pages to sync with new WP.org template
    • Changelog is a collapsible item
    • Changelog and Feedback form switched placement
    • Adding descriptions to categories & subcategories on landing page, will affect mobile length
    • Adding description to articles in categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. page (no description on subcategory) – will affect mobile length
    • Article content switch sides, long content to the left and article TOC to the right
    • Figma i1 vs i4
  5. First iteration for DevHub new design
    • Content review (landing page: what goes, what stays?)
    • Improvements only to articles not inside handbooks
    • Design in general
  6. Open floor

If there’s anything you’d like to discuss on the open floor, please leave the comment below.

#agenda, #meetings

Niels Lange 2:24 pm on November 2, 2022
Tags: , meetings,   

Summary of Docs Team Meeting November 1, 2022

Housekeeping

Attendance: @milana_cap, @chaion07, @atachibana, @nielslange, @kafleg, @leonnugraha, @lucp, Malcolm, @femkreations, @colorful-tones, @dpknauss, @bph, and @estelaris
Where: #docs channel 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/.. Find the complete transcript of the meeting on Slack.
Agenda: n/a
Meeting Facilitator: @milana_cap,
Note Taker: @nielslange
Next Meeting Facilitator (in two weeks): @femkreations
Next Triage Meeting Facilitator (next week): TBD

Project updates

  • @nielslange fixed broken code formats of the theme-related docs (see https://github.com/WordPress/Documentation-Issue-Tracker/issues/531).
  • @femkreations worked on WordPress 6.1 pages (see https://wordpress.slack.com/archives/C02RP4WU5/p1667311973175699).
  • @colorful-tones created a Trac ticket related to Block Patterns (see [#6556: Consider allowing Make teams to create block patterns](https://meta.trac.wordpress.org/ticket/6556) ).
  • @leonnugraha is planning to work on [HelpHub Remove redundant block name from “settings” panels · Issue #513 · WordPress/Documentation-Issue-Tracker · GitHub](https://github.com/WordPress/Documentation-Issue-Tracker/issues/513).
  • @femkreations mentioned that 44 pages of [6.1](https://github.com/orgs/WordPress/projects/45/views/2) and 14 pages of [6.0](https://github.com/orgs/WordPress/projects/28/views/11) have the status `Todo` if all issues for 6.0 should be moved to 6.1. @milana_cap then raised the question if the issues can be merge theme seamlessly.
  • @nielslange mentioned that a few issues of 6.0, that are in `Todo` should be in `Ready for Review` and volunteered moving the corresponding issues to the correct column.
  • @milana_cap mentioned that the [Yoast Contributor Day](https://yoast.com/about-us/events/yoast-contributor-day-november-2022/) will take place on November 3rd, 2022.
  • @estelaris mentioned that @ninianepress finished adding terms to the docs glossary project in GitHub (see https://wordpress.slack.com/archives/C02RP4WU5/p1667313612480669 and https://github.com/orgs/WordPress/projects/20/views/1).

Open Floor

  • @nielslange asked about how to follow-up after working on a doc and `Save it for later`. @milana_cap suggested to pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” the corresponding team lead.
  • @milana_cap mentioned that she saw the docs team small, then big, then small and now growing again and that she’s very happy with the current documentarians that are very dedicated.
  • @estelaris and @milana_cap had a brief discussion about the Handbook’s Glossary and @estelaris mentioned the link to [WordPress Glossary update](https://github.com/orgs/WordPress/projects/20/views/1).

#docs, #meetings, #summary

Sam Munoz 5:04 pm on October 11, 2022
Tags: , meetings,   

Summary of Docs Team Meeting October 11, 2022

Housekeeping

Attendance: @ninianepress @femkreations @milana_cap @colorful-tones @atachibana @estelaris @samanthaxmunoz @mayankgupta @webcommsat @bph
Where: #docs channel 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/.. Find the complete transcript of the meeting on Slack.
Agenda: https://make.wordpress.org/docs/2022/10/10/agenda-for-docs-team-bi-weekly-october-11-2022/
Meeting Facilitator: @ninianepress
Note Taker: @samanthaxmunoz
Next Meeting Facilitator (in two weeks): @estelaris
Next Triage Meeting Facilitator (next week): @ninianepress

Project Updates

It was a busy week for the 6.1 release cycle – many dev notes are published and some are still in review.

Release candidateRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. 1 is ready today as reported by @milana_cap.

@samanthaxmunoz has been working on a 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. pattern for Block Documentation and the pattern is ready for review before it is added and documented – see Issue #474.

@femkreations reviewed 333 closed PRs in 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/ from 13.1 through 14.1 with the User Documentation label and created 78 issues in GitHub for 6.1 User Documentation.

@femkreations also reviewed the About page draft and listed top priority tasks for the November 1st release. There are 25 items to do that ideally will be completed before the release of WordPress 6.1. The list is pinned to the #docs Slack channel.

Reclassification of End User Documentation

The reclassification of end user documentation has been finalized and there are now articles ready for content review.

In summary, the goal of the reclassification project is to re-organize the end user documentation and remove “too technical” content from end user documentation and/or merge it into developer docs.

An inventory of technical parts from end user documentation can be found here.

Related, 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/ Support is being renamed to Documentation – more information about that is available here, “Renaming WordPress.org Support to Documentation”.

Equal priority should be given to WordPress 6.1 documentation and the reclassification project.

Process in Project Boards Discussion

The team discussed the process for documentation project boards at length. As it stands there are only 2 columns, “In Progress” and “Review”, which are not clear and were discussed last week.

Various ideas were suggested about how to organize the project boards including separating into “new documentation” and “existing documentation”.

A consideration is that during Contributor Days often issues get screenshots and content updates in the comments of the issue, but the articles are not updated or assigned.

New columns have been added with temporary names such as “Text in progress” and “Screenshots in progress” but will likely continue to be refined.

The discussion will continue asynchronously or during the next meeting.

Open Floor

An Online Contributors Day for the Docs Team was discussed and will take place on October 25th starting at 10 am UTC.

@mayankgupta mentioned that DesktopServer has been discontinued yet is referenced in several documentation articles and has created an issue where mentions of DesktopServer are being noted.

#docs, #meetings, #summary

Jenni McKinnon 12:44 pm on September 14, 2022
Tags: , , meetings   

Agenda for Docs Team Bi-Weekly Meeting 27 September 2022

The next meeting is scheduled with the following details:

When: Tuesday, September 27, 2022, 04:00 PM GMT+2

Where: #docs channel on Slack

Agenda:

  • Attendance
  • Note-taker & Facilitator selection for Next Meeting
  • Projects checks
  • Do we add FAQs to HelpHub or not? See issue #426 (This requires @milana_cap and @femkreations to make a decision.)
  • Open floor

If there’s anything you’d like to discuss on the open floor, please leave the comment below.

#agenda, #meeting-agenda, #meetings

Jenni McKinnon 12:43 pm on September 14, 2022
Tags: meetings,   

Summary of Docs Team Meeting September 13, 2022

Housekeeping

Attendance: @estelaris @ninianepress @femkreations @robinwpdeveloper @leonnugraha @colorful-tones @samanthaxmunoz @chaion07 @javiercasares
Where: #docs channel on Slack. 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/..
Agenda: https://make.wordpress.org/docs/2022/09/12/agenda-for-docs-team-bi-weekly-meeting-13-september-2022/
Meeting Facilitator: @estelaris
Note Taker: @ninianepress
Next Meeting Facilitator (in two weeks): @ninianepress
Next Note Taker (in two weeks): TBD
Next Triage Meeting Facilitator (next week): @milana_cap

Project Updates

WCUS 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/.

@femkreations shared contributor day successes at WCUS which was on September 11, 2022:

WCNL Contributor Day

Yoast hosted a WCNL contributor’s day on September 14, 2022 at 10 AM – 4:30 PM UTC +2. It was available to join in-person, or online.

Open Floor

Issue When Editing Docs

@samanthaxmunoz pointed out that there’s an issue when you edit documentation pages in the back end:

  • Many pages are displaying the error message: “This 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. contains unexpected or invalifd content.”
  • The error is also displayed for pages that have recently been updated.
  • If you continue seeing this issue, please open a ticket in Meta.

There was also an issue brought up by @emmaht:

  • Some documentation has the block name italicized, while others don’t. (Post Author Block vs Post Author Block)
  • There doesn’t appear to be an answer in the Documentation Style Guide.

Answers are awaiting upon @femkreations’s return.

Reclassification Project

@estelaris let new contributors know that part of the redesign of end-user documentation (HelpHub) is removing any articles that are for developers and/or to remove any developer jargon that is in the articles. These such articles are being reclassified into categories that make more sense and migrating others to DevHub or developer documentation.

@javiercasares spoke about successes with the Advanced Administration Handbook over WCUS Contributor’s Day online over the past weeked:

  • @javiercasares opened 38 tickets, and 20 pages were formatted.
  • Content is being copied in HTMLHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites. from the HelpHub index, then created in markdown, and redirected to the Advanced Admin Handbook.

@javiercasares noted that the process for this is as follows:

  1. Create the structure. (empty files)
  2. Copy the original content into the new files, (using markdown) while changing the least amount as possible.
  3. Check all the pages for links, and old content, and try to renew it.
  4. Launch the new Handbook.

Noting that old pages in HelpHub will be redirected to the new ones in the Advanced Admin Handbook.

#meetings, #summary

Abha Thakor 11:30 am on August 17, 2022
Tags: meetings,   

Summary of Docs Team Biweekly Meeting August 16, 2022

Housekeeping

Attendance: @milana_cap, @chaion07, @javiercasares, @ashiquzzaman, @atachibana, @femkreations, @greenshady, @piermario, @brightemeka, @krupalpanchal, @emmaht. Asynchronous updates from @lucp and @estelaris.
Where: #docs channel 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/.. Find the complete transcript of the meeting on Slack.
Agenda: https://make.wordpress.org/docs/2022/08/16/agenda-for-docs-team-meeting-16-august-2022/
Meeting Facilitator: @chaion07
Note Taker: @webcommsat. Review: @milana_cap and @femkreations
Next Meeting Facilitator (in two weeks): @brightemeka
Next Note Taker (in two weeks): @greenshady
Next Triage Meeting Facilitator (next week): @milana_cap

Project Updates

Documentation Issue Tracker Updates

@milana_cap shared: there have been a lot of updates for Team roles tickets. This is hoped to be completed by end of next week: GitHub ticket #385

WordPress 6.1 release

WordPress 6.1 release has started, docs focus folks working in triage and collecting tickets for documentation.

Useful links for documentation

Anyone who wants to join in or learn how a release is documented, can contact @milana_cap in the documentation release team. She will pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” contributors once there is work available. Currently, everything is being prepared. A checklist is being created. An additional volunteers tracker for WordPress 6.1 release docs contributors has been set up too.

The post from the first meeting of the WordPress 6.1 release docs team: @bph, @milana_cap, @femkreations, @webcommsat, @mburridge. YouTube video from the meeting.

Project boards updates

@femkreations shared an update from the projects boards:

Reclassification project

@estelaris: no new updates

Other updates

@emmaht: we are working on (waiting to be reviewed)

The following items should be finished next week

@femkreations: highlighted contributions from @wigno and @leonnugraha who have been doing a great job with the 6.0 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 documentation. Thanks for their contributions.

@themiked: fixed a few minor issues, found a problem with the GitHub importer and logged it.

Collaborations between docs and hosting team

@javiercasares: last week Milana was on the #hosting-community channel explaining this new project / handbook / documentation about separating some of the most technical documentation from the Hubs.

There is a new label in the Issue Tracker ‘advanced administration’.

Initial check of the tickets, first idea on categorization can be found in this Google doc. This is a first “structure” with all the links and everything I found on those tickets. As this is a first idea, it will probably change a lot.

Thanks to @JavierCasares for structuring the new handbook.

First pull request for the Advanced Administration Handbook

#1 Create a first possible File Structure – a first level possible structure, with the “big categories”. This may change as we start creating and updating content, but this is a place to start.

Second pull request (technical one, for the #meta team)

#2 First Manifest file – a first manifest file, created manually because we will need to have the WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/ https://make.wordpress.org/cli/ software configured… but we will have that when 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. creates it.

Those files will help us start creating new content and migrating the actual one. Then sync everything with the site automatically (so every time we do a merge, the content will be updated). These are first ideas, help and suggestions welcome.

@lcup sent an update to the meeting:
– added articles to move from HelpHub to DevHub docs for the new advanced administration handbook in: Documentation Issue Tracker, ticket 388 in GitHub. Thanks to @estelaris and @femkreationsfor doing all of the look-up work on this.

@milana_cap shared context: parts of “too technical” docs from HelpHub will end up in this new handbook. 

Open Floor

Updates on the Five for the Future program and proposed improvements – post from July 28, 2022.

@shetheliving shared async: wanted some additional views on Documentation Issue Tracker issue on Tidy up suggested object caching plugins #410, for @tillkruess and the Performance team.

#meetings, #summary

Ahmed Chaion 11:09 am on August 16, 2022
Tags: , , meetings   

Agenda for Docs Team Meeting 16 August 2022

Our next Team meeting is scheduled with the following details:

When: Tuesday, August 16, 2022, 14:00 UTC

Where: #docs channel on Slack.

Meeting Agenda

#agenda, #meeting-agenda, #meetings