Tag Archives: summary

Leonardus Nugraha 2:53 am on November 14, 2023
Tags: , , summary   

Summary for Docs Team Meeting (7-Nov-2023)

Attendance

@milana_cap @leonnugraha @sagargurnani @ninianepress @anandau14 @webcommsat @rashiguptaa @zunaid321. Async: @nalininonstopnewsuk, @611shabnam, @femkreations

Housekeeping

Find the complete Transcript of the meeting on Slack.

Upcoming Meeting

Project Checks

@milana_cap had created 48 good first issues for WordPress 6.4 documentation and ran 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/ roles onboarding session. The recording is uploaded to wordpress.tv but not published yet.

@webcommsat gave an update on WordPress 6.4 release documentation:

(Update – link to full update in the meeting and how contributors can help, including working on or reviewing screenshots, video, new explanations. Highlighted the value of docs in this area to the end user.)

  • Documentation tracker for 6.4
  • Dev notes: one additional dev note has been added to the Editor Miscellaneous Dev Notes today
  • There is one remaining Dev Note which will be done after the release by one of the committers
  • Call for contributors to work on HelpHub
  • Props for all those who had contributed by the beginning of last week have been collated, checked against the main list, and submitted
  • A further props update will be sent once the End User docs (HelpHub) have been updated
  • Ongoing outreach and promotion, particularly the HelpHub end user docs
  • Onboarding / support to cohort and additional volunteers
  • Following up work on End User docs.

@atachibana reviewed one issue #1204, and tackled high priority 6.4 issue #1204, the Site Editor Pattern.

@anandau14 worked on one high-priority task and has 2 more assigned.

Open Floor

@webcommsat raised from experience of the last couple of releases and involvement in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., Marketing, Docs, and Training, a resource to help meetups devote a session to helping with User docs would be very useful and raise awareness about docs. More on this suggestion, what has been started in 6.4, and the fuller discussion in 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/.. (link to Slack discussion added)

The ideas included to get meetups and companies to sign-up to help earlier in the release cycle, show how fun it can be, and promote our contributor events.

#docs, #meetings, #summary

Sagar Gurnani 11:53 am on November 7, 2023
Tags: , , summary   

Summary for Docs Team Meeting (31-Oct-2023)

Attendance

@milana_cap @leonnugraha @sagargurnani @ninianepress @anandau14 @huzaifaalmesbah @femkreations

Housekeeping

Find the complete Transcript of the meeting on Slack.

Upcoming Meeting

Project Checks

@milana_cap had created:
1. Good first issues templates https://github.com/WordPress/Documentation-Issue-Tracker/issues/new/choose.
2. New good first issues, the real ones https://github.com/WordPress/Documentation-Issue-Tracker/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22+label%3A6.4.
3. A page about good first issues https://make.wordpress.org/docs/handbook/get-involved/getting-started-at-a-contributor-day/good-first-issues/.
4. A video for checking ALT attributes for the page in the link above.

@anandau14 had worked on #1206 from 6.4 board.

@leonnugraha had reviewed, updated, and closed #1207. He had also reviewed and updated #491 but because there’s still one item needs to be done, so he has not closed the issue.

@femkreations had looked through approximately 150 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/ Pull Requests (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/) that were labeled “Need User Documentation” and identified 34 tasks that need to be worked on, for 6.4 in the end-user documentation. She had also completed adding those tasks to this Project Board. The tasks were then divided into: High Priority, Medium Priority and Good First Issues. She also wrote a Call for Volunteers to help out with the update.

Open Floor

@milana_cap discussed about new GitHub roles i.e. issue coordinator and reviewer. Both of these roles could be performed by anyone, regardless the experience with docs or WordPress and which would require about 1 hour per week or may be less.

Issues Triage

This was the 5th week meeting which turned out to be a combination of the weekly triage and the regular weekly meeting. To look at the issues in WordPress 6.4 High Priority Issues click here.

#docs, #meetings, #summary

Jenni McKinnon 4:14 pm on October 21, 2023
Tags: , , summary   

Summary of Docs Team meeting October 17, 2023

Attendance

@ninianepress @milana_cap @atachibana @cold-iron-chef @kafleg @huzaifaalmesbah @leonnugraha @anandau14 @huzaifaalmesbah @devmuhib @rashiguptaa @pekkakortelai @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 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/.

Next triage meeting

  • Where: #docs channel on Slack
  • When: Docs Team triage meeting Oct. 31, 2023 at 2 PM UTC
  • Triage facilitator: @leonnugraha

Next team meeting

Please note: Daylight Saving Time (DST) will end on Oct. 29 for Europe and Nov. 5 for North America; the date may differ depending on your location. However, the meeting times will remain the same at 2 PM UTC.

Project checks

@milana_cap mentioned that she went through all of the issues with documentation that didn’t have a label [Status]and added the appropriate label to them.

@atachibana checked out two articles,  #679, #719, closed two articles #760, #761, and requests a review for article #772.

@femkreations completed:

  • Triaging all the closed pull requests (PRs) 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/ (GB) 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/ (GH) for 6.4 and labeled the required PRs with the “Needs User Documentation” label.
  • Created a 6.4 Documentation Project board from template #141.
  • Created two videos that show how the GB PRs are triaged for a release in a GH and how to find all the PRs labeled “Needs User Documentation” for each milestone.

Open floor

@leonnugraha volunteered to write and publish next week’s contributor day post and the corresponding GitHub issue.

@estelaris is planning on implementing a triage hour with the Spanish team, probably twice a month, to write and review the style guide. She is also reaching out to the Brazilian team that wants to start working on translations, and she’ll begin by creating a style guide in Portuguese.

Props to @rashiguptaa for writing this meeting summary. 🍪

#docs, #meetings, #summary

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

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

noumantech 7:44 pm on September 6, 2023
Tags: , , summary   

Summary of Docs Team Biweekly Meeting (September 05, 2023)

Attendance

@noumantech @cold-iron-chef  @sagargurnani @marcio-zebedeu @leonnugraha @milana_cap  @estelaris @611shabnam @javiercasares @devmuhib @jyolsna @atachibana 

Housekeeping

Find the complete Transcript of the meeting on Slack.

Next Meetings Facilitators and Note Takers

Project Checks

@milana_cap added contributing docs and Serbian language to the new HelpHub repo. She has also started working on #1102 and started retiring old articles that are moved to the Advanced Administration Handbook. @milana_cap created a new project board for inventory of end user docs and collected all HelpHub articles and categories via REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/.

@sagargurnani completed the #935, self-assigned #203, and asked @milana_cap about the status of #935.

@611shabnam is still working on #678 and her progress is slow due to deadlines in the current month.

@leonnugraha shared the progress of US Contributors Day. He completed and closed #694, #973, #947, #936, #937, #941, and #975.

@jyolsna completed #974 by updating the screenshots.

@marcio-zebedeu is working on #978 and needs more time to complete it.

@cold-iron-chef is behind on one issue and will complete it by next week.

@estelaris shared his plans to start work on Future plans for HelpHub, the documentation team handbook, and finish the WP End-user docs inventory. @milana_cap and @estelaris discussed the schedule to collaborate on various days on these tasks.

Open Floor

@estelaris shared the Figma design for the proposed design of HH’s landing page and asked the Docs Team to have a discussion for approval. Matt is not happy with the design and needs improvement in fonts and spacing. @milana_cap raised a concern about the wasting of space in the categories section of the landing page design.

@leonnugraha shared screenshots from the Figma design and suggested an increase in the font size of headings. @estelaris mentioned that the current heading font size in the template should be suitable for all languages. @cold-iron-chef supported the point of general rules for different languages by sharing her experience with French/English Websites.

@estelaris asked everyone to leave comments on the Figma File and told team members to Click on the :speech_balloon: icon if anyone has a problem leaving comments.

@estelaris shared another proposal for the translation and localization of docs for review. The design is not final and it will be published on the next day after the meeting.

#docs, #meeting, #summary

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

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

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

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: , , summary   

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

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

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

Jenni McKinnon 1:37 pm on May 16, 2023
Tags: , , summary   

Summary for Docs Team meeting, May 2, 2023

Attendance

@ninianepress @milana_cap @hilayt24 @chaion07 @femkreations @sereedmedia @medesigngood @leonnugraha @kafleg @sonalithakkar @ninthcoder @estelaris

Housekeeping

Find the complete Transcript of the meeting on Slack.

Project checks

@milana_cap closed 7 issues.

@femkreations completed issue 485.

@leonnugraha reviewed #695.

@larassattidn and 281.

Reminder about Docs Team 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/.

For all those that attended the last Docs Team Contributor Day, please be sure to comment on the corresponding GitHub issue with what you worked on that day.

The next Docs Team Contributor Day is May 23, 2023 from 1 PM UTC to 4 PM UTC.

Open floor

@milana_cap asked if there was any feedback from our last Contributor Day.

@ninianepress suggested breakout rooms in Zoom so that contributors who need it can be onboarded. At the next contributor meeting, we will ask if any one is in need of onboarding, then open a breakout room, as needed.

The team decided to continue with a 3-hour long Contributor Day and that the fifth Tuesday in May will be a triage meeting, following the week after our next Contributor Day.

@estelaris wrote Explorations for a notification form between documentation and Rosetta sites and would love contributor feedback in the comments.

#docs, #meeting, #summary