Tag Archives: meetings

noumantech 6:11 am on October 13, 2023
Tags: , meetings,   

Summary of Docs Team Biweekly Meeting (October 3, 2023)

Attendance

@estelaris @leonnugraha @anandau14 @noumantech  @atachibana @devmuhib @marcio-zebedeu @webcommsat @rashiguptaa @webtechpooja @611shabnam @kafleg @huzaifaalmesbah @pekkakortelainen

Housekeeping

Next Meetings Facilitators and Note Takers

Project Checks

@611shabnam shared the progress of #678 and explained that she is working on the issue left.

@noumantech was so busy with projects he couldn’t focus on the #1100. He is committed to completing it in a couple of weeks. @pekkakortelainen shared the progress of #430 and provided details of the size of the revamp. It would take time to finish it. He also showed interest in addressing one of the notes from Sep 19th meeting: about onboarding new contributors.

Open Floor

 @anandau14 will be leading the Documentation team table at 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. Bhopal 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/. on Saturday (October 7, 2023). The Contributors Day can bring some new contributors to the channel 

@webcommsa shared an update on the docs release for 6.4. She explained that avoid adding the Google folder to the public minutes, as two of the cohorts can not access Google Drive to update the documents in there so we have temporarily had to enable it to link access for editing until their access to Google Drive can be solved. She also referred to the statement of @cbringmann” Dev Chat recently, you do not have to be on the squad or in the cohort to get involved in an aspect of the release.”

@estelaris will be leading the docs team at Yoast Contributor Day tomorrow. Will focus on good first issues and the 6.3 task board. @anandau14 showed interest in the contribution to the docs release for 6.4. @webcommsa advised @anandau14 to participate in Yoast Contributor Day with @estelaris

#docs, #meetings, #summary

Anand Upadhyay 10:40 am on October 2, 2023
Tags: , meetings   

Agenda for Docs Team Biweekly Meeting (October 3, 2023)

The schedule of the next meeting is as follows:

When: Tuesday, 03-Oct-2023 14:00 UTC

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

Agenda:

1. Attendance.
2. Selection of a Note-taker and facilitator for the next docs team meeting.
3. Facilitator selection for the next triage.
4. Project check.
5. Open floor.

Please feel free to leave a comment to add to the Open floor discussion

#agenda, #meetings

Sagar Gurnani 7:41 pm on September 1, 2023
Tags: , , meetings   

Agenda for Docs Team Biweekly Meeting (05-Sep-2023)

The next meeting is scheduled with the following details:

When: Tuesday, 05-Sep-2023 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. Open floor.
    • Review of the latest docs redesign in Figma.
    • The proposal for documentation translation/localization.

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

#docs #meetings #agenda

Sagar Gurnani 6:56 pm on August 17, 2023
Tags: , meetings,   

Summary for Docs Team Meeting (15-Aug-2023)

Attendance

@milana_cap @leonnugraha @sagargurnani @ninianepress @marcio-zebedeu @kartiks16 @611shabnam @estelaris @cold-iron-chef @huzaifaalmesbah @shuvo586 @pratikshrestha @noumantech @femkreations (async)

Housekeeping

Find the complete Transcript of the meeting on Slack.

Upcoming Meeting

The next team meeting will be the “Docs Online Contributors Day” as a WCUS followup and would be held on Aug 29, 2023 at 14:00 UTC.

Next week (22-Aug-2023) is supposed to be the Docs Online Contributors Day but is cancelled as it’d the same week as WCUS and Community Summit.

Project Checks

@milana_cap created a new workflow for this 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/ repo.

@sagargurnani completed #935 which was reviewed by @atachibana.

@atachibana reviewed #811, #934, #935. Closed #753, #754, #759,  and is now working on #760.

@611shabnam is working on #678.

@cold-iron-chef is working on #278.

@estelaris mentioned that there would be a x-post regarding the translation of content in the .org. It will be on the polyglots make blog and if anyone contributes to his local translation teams then he should check that post. There are several issues which are needed to be resolved translation is started.

Open Floor

@cold-iron-chef asked about getting the “Documentation Contributor” badge on her profile and @milana_cap helped her out with that.

@estelaris asked the contributors their point of view on topics for the summit and said that the team would do its best to take that point of view to the summit. Discussion topics can be found here.

#docs, #meetings, #summary

Leonardus Nugraha 6:11 am on August 15, 2023
Tags: , meetings   

Agenda for Docs Team bi-weekly meeting August 15, 2023

The next meeting is scheduled with the following details:

When: Tuesday, 15 August 2023, 02:00 PM UTC

Where: #docs channel on Slack

Agenda:

  1. Attendance
  2. Upcoming meeting and Docs 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/. schedule
  3. Note-taker and facilitator selection for the next meeting
  4. Facilitator selection for the next triage meeting
  5. Project check
  6. Open floor

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

#agenda, #meetings

Mushrit Shabnam 9:31 am on August 4, 2023
Tags: , meetings,   

Summary for Docs Team meeting, August 1, 2023

Attendance

@leonnugraha @milana_cap @femkreations @sagargurnani @anandau14
@bph @themiked @estelaris @atachibana @611shabnam @rashiguptaa
@cold-iron-chef @JoMinney (async)

Housekeeping

Project Checks

@atachibana and @Alvaro Gómez /mrfoxtalbot  fixed this issue.

@leonnugraha tagged all 6.3 user docs issues with tracking issue and new document labels accordingly.

@611shabnam completed #687 and #282 and @femkreations closed those tickets.

@anandau14 prepared the draft of Page List 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., received the access of docs site, will publish the prepared docs soon.

@milana_cap created few new issues from HelpHub feedback, added another workflow for GH (applying developer label one other devhub labels are applied), finished and published post for core dev blog, did onboarding session with @ninianepress

@femkreations 1st and 2nd reviewed #687 and #282 and scheduled the articles for publishing, 1st reviewed #676, reviewed all the pages under #899 for replacing the Reusable blocks to Patterns and closed. Did a 2nd review of #949 and closed it. Onboarded a new contributor for #986 and created tracker for consolidating More rich text editing options #986. Moved few more tasks to the 6.3 from 6.2 board

@cold-iron-chef is working on #161

@femkreations mentioned we still have work to be done before August 8th. The tasks have been sorted into medium priority tasks and high priority tasks on the 6.3 project board. If you are new to the Docs team, you can select from the list of good first issues.

Question: How to open an issue

@cold-iron-chef noticed there’s no Vimeo Block documentation at all and asked how she can open issues. @estelaris informed she should go to this link and confirmed no permission is required. Later @cold-iron-chef confirmed she will be adding that link to the list of embeds.

Question: Move closed tasks automatically to the Done column in 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/

@milana_cap mentioned it should work automatically but @femkreations mentioned it is not possible to do so in 6.3 board. So cold-iron-chef mentioned that if we tag the pull request with closes #
 it will close the issue when that’s merged.

@milana_cap mentioned @stevenlinx created the board, so may be he can take a look. Also she mentioned closing the tickets from repository should move the tickets automatically.

@femkreations confirmed that the problem exists even when the tickets are closed from repository and it only exists for 6.3

@estelaris jumped in and asked if we shall create a page in the handbook with instructions on how to create boards with all the bells and whistles you like, for release leads? @milana_cap and @femkreations agreed on this. So, @estelaris asked if @femkreations can open the issue and add the bells and whistles. @femkreations confirmed she will do that.

@femkreations created this issue in response and @stevenlinx chimed in after the meeting and mentioned he added the features as needed. It’s in Workflows of the Project: when an item is closed or a PR is merged, set Status to Done. He asked @femkreations to check. @femkreations confirmed the issue is fixed and the issue moves automatically to the Done column.

@femkreations made some updates to the 6.3 Project board columns. We now have a new Edit after 1st Review  which means waiting for the content edits after the 1st Review. Makes it easy to see the progress at a glance.

Open Floor

It was birthday of @estelaris and she was in Venice! Happy Birthday @estelaris!

@femkreations said: “Big thanks to @atachibana @Alvaro Gómez /mrfoxtalbot @Leonardus Nugraha @611shabnam @Anand @poena for working on the 6.3 tasks for the upcoming release. We still have work to be done before August 8th. Please check out the 6.3 project board. The tasks have been sorted into medium priority tasks and high priority tasks. If you are new to the Docs team, you can select from the list of good first issues.

#docs #meetings #summary

Jenni McKinnon 10:19 pm on August 1, 2023
Tags: , meetings,   

Summary for Docs Team meeting, Jul 18, 2023

Attendance

@ninianepress @milana_cap @leonnugraha @jominney @611shabnam @jyolsna @atachibana @femkreations @sumitsingh

Housekeeping

Find the complete Transcript of the meeting on Slack.

Upcoming meetings

The next team meeting will be the monthly online Contributor Day which will be held on Jul 25, 2023 at 13:00 UTC.

Project checks

@milana_cap:

  • helped a bit with WordPress 6.3 docs
  • working on nonces coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. dev blog post

@femkreations:

@leonnugraha:

  • Has been wrangling, reviewing, and publishing WordPress 6.3 dev notes, mainly for 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/ with @milana_cap and @bph‘s help

@611shabnam:

  • Completed #282

@jyolsna:

  • Reviewed a 6.3 doc

Open floor

There were a few mentions and discussions on important issues:

Meeting adjustments for August

As WCUS is coming up in August, the team decided to adjust some meeting dates to accommodate team contributors who will be in attendance.

As such, the meeting on Tuesday, 22 August, 2023 will be an asynchronous meeting in the #docs channel on Slack for 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/..

The monthly online Docs Team Contributor Day that was previously scheduled for August 22 has now been moved to Tuesday, 29 August, 2023 from 13:00-16:00 UTC.

Call for volunteers announcement and amplification

@femkreations almost has the announcement post calling for volunteers to work on the 6.3 Documentation Project Board.

She requests that once the post has been published, that the team shares it to help spread the word to get more contributors.

Headings and bold text in articles

@611shabnam noticed that some articles have headings that are bold instead of actually being formatted as headings and asked for the protocol.

@femkreations and @leonnugraha answered:

  • Generally, we use headings H1 through H3
  • Bold is used for 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. names or to describe screen names and such

#docs, #meetings, #summary

Leonardus Nugraha 2:33 am on August 1, 2023
Tags: , meetings   

Agenda for Docs Team bi-weekly meeting August 1, 2023

The next meeting is scheduled with the following details:

When: Tuesday, 1 August 2023, 02:00 PM UTC

Where: #docs channel on Slack

Agenda:

  1. Attendance
  2. Note-taker and facilitator selection for the next meeting
  3. Facilitator selection for the 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

Jenni McKinnon 9:33 am on July 18, 2023
Tags: , meetings   

Agenda for Docs Team bi-weekly meeting July 18, 2023

The next meeting is scheduled with the following details:

When: Tuesday, 18 July 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. 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

Sagar Gurnani 11:44 am on July 6, 2023
Tags: , meetings,   

Summary for Docs Team Meeting, Jul 04, 2023

Attendance

@milana_cap @femkreations @leonnugraha @sagargurnani @ninianepress @jominney @cold-iron-chef @krupalpanchal @sumitsingh @chaion07 @atachibana @thisisyeasin @611shabnam @mrfoxtalbot @tobifjellner

Housekeeping

Find the complete Transcript of the meeting on Slack.

Upcoming Meeting

The next team meeting will be the issues triage which would be held on Jul 11, 2023 at 14:00 UTC.

Project Checks

@milana_cap configured a few automation for the Documentation repo #882, and she had also created 12 new issues in the end user documentation.

@atachibana fixed 2 issues in the End User Documentation #753 and #754.

@leonnugraha completed #871 by adding the 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/ demo links to the 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.

@611shabnam completed reviewing #672 the second time.

@cold-iron-chef contributed to #714.

Posting Schedule for 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/. Announcement

@ninianepress volunteered to schedule Contributor Day posts at the beginning of each month so as many people as possible are informed. Maybe even xpost to other teams we work with often. She will also post the corresponding GH issue a week before at the latest with the reminder post.

List of Teams to Xpost:

  1. Training
  2. Marketting
  3. Community
  4. Support
  5. CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.

Open Floor

@estelaris brought up a discussion regarding content duplication (#910) and mentioned about checking the onboarding videos and also mentioned that it happens when a new contributor gains access to update articles. And, suggested for making a better job of explaining the workflow instead of creating more work for everyone.

@leonnugraha suggested that there should be a handbook page clarifying publishing and/or updating workflows, to which @milana_cap agreed.

#docs, #meetings, #summary