Summary for Docs Team Meeting (19-March-2024)

Attendance

@estelaris @milana_cap @leonnugraha @sagargurnani @hellosatya @marcio-zebedeu @lighthouse79 @atachibana @anandau14 @noumantech @sheebaabraham @matteoenna @lumiblog  @Calolan

Housekeeping

Find the complete Transcript of the meeting on Slack.

Upcoming Biweekly Meeting

Project Checks

 @sagargurnani completed #430 and #935 and waiting for the review of #954.

@leonnugraha reviewed the drafts of the dev notes and published the Miscellaneous Editor changes in WordPress 6.5.

 @Calolan shared the progress of #1308 and #1476.

@milana_cap shared the update on the CloudFest hackathon contribution but could not contribute to docs projects.

 @sheebaabraham shared the progress of #1371 and showed commitment to complete it soon.

@estelaris started the user documentation for the 6.5 release and needs help from new contributors to get screenshots and a small video

@lumiblog shared the list of in-review issues (#1299, #1313, #1281, and #1280) and closed issues.

Open Floor

@estelaris shared the list of open issues for the 6.5 release – HelpHub: #1490, #1491, and #1492. He would also open more issues.  @sagargurnani and @estelaris discussed the March 5, 2024 updates post; @sagargurnani responded that he contacted Adam to help him document the playground.

@estelaris explained that two main items need help: users’ and developers’ perspectives in the documentation and review on the last item to improve the changelog in the articles. He also plans to write end-user cases after I finish the 6.5 release docs.

@sagargurnani asked a question about a few articles that have change logs and a few haven’t. @milana_cap explained that Changelogs were made when @bph ran 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 docs, and she had them in an article template. The rest of the docs never caught up. @estelaris said changes are happening at design side, will look into it later.

#docs, #meetings, #summary

Agenda for Docs Team Biweekly Meeting (19-Mar-2024)

The next meeting is scheduled with the following details:

WhenTuesday, 19-Mar-2024 14:00 UTC

Where#docs channel on Slack

Agenda:

  1. Attendance.
  2. Note-taker and facilitator selection for the next docs team meeting.
  3. Facilitator selection for the next triage.
  4. Project check.
  5. Estela’s (@estelaris) updates
  6. Open floor.

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

#agenda, #docs, #meetings

Summary for Docs Team Meeting (20-Feb-2024)

Attendance

@estelaris @milana_cap @leonnugraha @sagargurnani @ninianepress @atachibana @anandau14 @noumantech @rcreators @ranjanrakesh @kafleg @hellosatya @marcio-zebedeu @lighthouse79 @matteoenna @ashishsthanp @devmuhib (async)

Housekeeping

Find the complete Transcript of the meeting on Slack.

Upcoming Meeting

The next Docs Team Bi-weekly meeting which is supposed to be held on 05-Mar-2024 has been cancelled due to WCAsia 2024. So, the next Bi-weekly meeting would held on 19-Mar-2024 instead.

Project Checks

@milana_cap had updated the WordPress Versions Page.

@sagargurnani had completed #958.

@leonnugraha had completed and closed #958. He also gathered 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/ PRs for 6.5 that require dev notes and created a tracking issue for it.

@atachibana had completed and closed on #291.

@noumantech had completed #1332 and is waiting to get it reviewed.

Estela’s Updates

  1. She (@estelaris) had mentioned that @ninianepress, @anandau14 and herself were chosen as mentors for the mentorship program cohort 2.
  2. She would be mentoring 2 new contributors from Italy and will teach them documentation so they can get involved in translation. She had added them (@lighthouse79 and @matteoenna) to the #docs channel too.
  3. She had shared and requested everyone to read the documentation redesign post and leave comments, if any.
  4. She had also mentioned, It was suggested that the team identifies the documentation as “Docs for Non-Devs” or something similar. Apparently, developers click on the Help Hub documentation and get frustrated to find out it is not what they are looking for.
    • @leonnugraha suggested that it can be called something like – “Help Centre”, “User Guide” or “Intro Copy”.
    • @estelaris suggested – “Documentation – If you don’t code, this is for you” and said the “Help Centre” can be confused with the Support or Forum.

Open Floor

  1. @anandau14 mentioned that he will be guiding 2 mentees on contributing to docs. And, he added them (@ashishsthanp and @ranjanrakesh) to the #docs channel.

#docs, #meetings, #summary

Agenda for Docs Team Biweekly Meeting (February 20, 2024)

The next meeting is scheduled with the following details:

WhenTuesday, 20 February 2024, 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. Project check
  5. @estelaris‘ updates
  6. Open floor

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

#agenda, #meetings

Summary for Docs Team Meeting (11-Feb-2024)

Attendance

@estelaris @milana_cap @leonnugraha @sagargurnani @ninianepress @atachibana @anandau14 @noumantech @cold-iron-chef @stevenlinx @kafleg @hellosatya (async) @iamasadpolash (async)

Housekeeping

Find the complete Transcript of the meeting on Slack.

Upcoming Meeting

Project Checks

@milana_cap had updated the WordPress Versions Page.

@sagargurnani had worked on the following issues:

  1. Needs Review – #430.
  2. In progress – #954 and #958.
  3. Ready to be published – #935.
  4. Closed – #430.

@leonnugraha had completed and closed #1241 and #1347.

@atachibana is working on #291.

@ninianepress had submitted an amplification request to the #marketing team for February 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/. #363.

@anandau14 had updated #1332 by adding screenshots and is waiting for it to get reviewed.

Open Floor

@estelaris discussed the following 4 points:

  1. Proposal: An update to the Field Guide: During last dev chat the future of the proposal was discussed in which the team had suggested that other teams should also get involved. The #docs team now needs to decide whether to accept the proposal or to suggest changes.
  2. Feedback on the Wishlist for the redesign of /documentation/ were provided. The #docs team must give suggestions now.
  3. Figma file: At the bottom of the landing page, there is a field that only links to “Support Forums” and “Developers”. The docs team needs to provide ideas on how to utilize that space better.
  4. She also asked us to provide our thoughts on WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. for Docs (24 hours online), to include talks and working sessions. This is the document with her Initial Suggestions. Almost, everyone in the team liked the idea.

@sagargurnani asked whether the contributors can close the issues by themselves, to which @estelaris and @leonnugraha answered that the issue assignees can close the issues by themselves but only when it is reviewed and approved by the issue reviewer, otherwise they should request the issue owner or the #docs 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. to close the issue.

#docs, #meetings, #summary

Agenda for Docs Team meeting February 6, 2024

The next meeting is scheduled with the following details:

WhenTuesday, 6 February 2024, 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. Project check
  5. @estelaris‘ updates
  6. Open floor

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

#agenda, #meetings

Summary of Docs Team meeting January 23, 2024

Attendance

@ninianepress @milana_cap @leonnugraha @atachibana @anandau14 @sagargurnani @psykro @hellosatya @devmuhib @estelaris

Housekeeping

Find the complete Transcript of the meeting on Slack.

Upcoming meetings

Here’s a shortlist of the upcoming Docs Team meetings with facilitators and note takers detailed below:

Next team meeting

Next triage meeting

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

Project checks

@milana_cap cleaned up HelpHub feedback and made new issues from valid ones:

  • List of newly created issues on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/
  • List of new issues created for the Advanced Administration Handbook

@milana_cap also re-uploaded missing images and completed updates for 6.1 and for #278.

@sagargurnani finished:

@anandau14 reviewed and suggested edits for #716.

@leonnugraha reviewed and closed #1203 as well as reviewed and suggested for #491.

Open floor

@leonnugraha and @estelaris were announced as the 6.5 Release Squad with @sagargurnani learning and assisting. Congratulations from the Docs Team! 🎉🍪

@anandau14 shared their experience of WCNepal Contributors Day on 12 Jan. 2024 as the Docs Team Table Lead: Over 50+ attendees joined and it was an amazing experience.

@ninianepress opened an issue in GitHub to create an onboarding message when someone joins the 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/.. Please contribute ideas and copy through #1440.

Also, the call for mentors and mentees is open for the Q1 WordPress Mentorship Program. You still have time to sign up to onboard new contributors or sign up to be a mentee and be onboarded. If you’re interested at all, please take a look at the post about it: Call for Mentees & Mentors: Contributor Mentorship Program Cohort #2 (2024 Q1).

@psykro started running WordPress developer livestreams focused on contributing to WordPress and wanted to run a live stream, taking part in a Docs Team Online Contributor Day, and wanted to check if it was okay. The Docs Team welcomed the idea.

@estelaris mentioned issues that needed to be discussed:

  • “Importing content information” should it be under Advanced Admin handbook or under support docs? Issue #1439
    • Please see the corresponding GitHub issues for updates and to contribute.
  • We need to have a wish list of items that we would like for the redesign of /documentation/ site; we want to build something like this.
    • Items were discussed and added to the wish list document for further discussion. Please add your comments there.

#docs, #meetings, #summary

Agenda for Docs Team meeting January 23, 2024

The next meeting is scheduled with the following details:

WhenTuesday, 23 January 2024, 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. Project check
  5. Open floor

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

#agenda, #meetings

Agenda for Docs Team meeting January 9, 2024

The next meeting is scheduled with the following details:

WhenTuesday, 9 January 2024, 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. Project check
  5. Open floor

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

#agenda, #meetings

Summary of Docs Team meeting December 5, 2023

Attendance

@leonnugraha @milana_cap @ninianepress @zunaid321 @ashiquzzaman @atachibana @rashiguptaa @anandau14 @webcommsat @kenshino @javiercasares

Housekeeping

Find the complete Transcript of the meeting on Slack.

Proposed holiday schedule

The team discussed time off for the end of the year for the Documentation Team. Two options were voted on:

  • 2 weeks in December, 1 week in January
  • 1 week in December, 2 weeks in January

The first option was most popular, but the team decided to vote again at the. following week’s triage meeting to give more members a chance to vote asynchronously.

The facilitator for the next meeting will also be decided on in the new year.

Project checks

@atachibana responded the comment of #1204, wrote a draft page for #1214 and reviewed 7 issues (1241, 1248, 1273, 1292, 1347, 1348, and 1342).

@leonnugraha reviewed and closed #1204 and #1206.

Open floor

@webcommsat mentioned a few issues that need to be worked on:

  • Issue 1228, 1248 and 1216 need reviews
  • Issue 1203 is waiting for a technical review for 6.4 end user documentation

@javiercasares mentioned that both Plugins Team Reps are from Spain, and they all talked and decided to start moving their handbooks with Trac ticket 7358.

Their handbook is available on GitHub for information purposes. Their DevHub documentation has been moved to GitHub and the content review is in progress. Once completed, it will be migrated to 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/.

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 Team Reps will lead the Handbook and @javiercasares has offered to help with administration.

#docs, #meetings, #summary