{"id":154863,"date":"2026-04-20T18:15:22","date_gmt":"2026-04-20T18:15:22","guid":{"rendered":"https:\/\/make.wordpress.org\/training\/?p=154863"},"modified":"2026-04-20T18:15:22","modified_gmt":"2026-04-20T18:15:22","slug":"office-hours-meeting-recap-18th-april-2026","status":"publish","type":"post","link":"https:\/\/make.wordpress.org\/training\/2026\/04\/20\/office-hours-meeting-recap-18th-april-2026\/","title":{"rendered":"Office Hours Meeting Recap &#8211; 18th April 2026"},"content":{"rendered":"<p class=\"wp-block-paragraph\"><strong>Date:<\/strong> April 18, 2026<br><strong>Time:<\/strong> 14:00\u201315:00 UTC<br><strong>Platform:<\/strong> Zoom<br><strong>Recording:<\/strong> Not recorded<br><strong>Moderator:<\/strong> Rico F. L\u00fcthi (<a href=\"https:\/\/profiles.wordpress.org\/rfluethi\/\">@rfluethi<\/a>)<br><strong>Note-Taker:<\/strong> Rico F. L\u00fcthi (<a href=\"https:\/\/profiles.wordpress.org\/rfluethi\/\">@rfluethi<\/a>)<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Related links:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Meeting agenda: <a href=\"https:\/\/github.com\/WordPress\/Learn\/issues\/3413\" target=\"_blank\" rel=\"noreferrer noopener\">Meeting Agenda \u2013 Office Hours, Saturday, April 18, 2026<\/a><\/li>\n\n\n\n<li>Proposal: <a href=\"https:\/\/make.wordpress.org\/training\/2026\/02\/03\/proposal-monthly-office-hour-meeting-for-make-wordpress-training\/\">Monthly Office Hour Meeting for Make WordPress Training<\/a><\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Meeting Context<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">This was the first meeting of the Training Team\u2019s new Office Hours format. The format replaces the previous Coffee Hours, which generated more than 90 ideas over roughly eight sessions but resulted in very little concrete follow-through. The Office Hours are designed to close that gap: informal in tone, but clearly outcome-oriented, with actionable next steps from meeting to meeting.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">As outlined in the <a href=\"https:\/\/make.wordpress.org\/training\/2026\/02\/03\/proposal-monthly-office-hour-meeting-for-make-wordpress-training\/\">proposal<\/a>, the format initially runs as a three-month pilot phase. The goal of this kick-off was to establish the basic structure, success criteria and organizational approach together, so that future sessions can focus directly on substantive work.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Participants<\/h2>\n\n\n\n<figure class=\"wp-block-table is-style-stripes\"><table><thead><tr><th>Name<\/th><th><span tabindex='0' class='glossary-item-container'>WordPress.org<span class='glossary-item-hidden-content'><span class='glossary-item-header'>WordPress.org<\/span> <span class='glossary-item-description'>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.  <a href=\"https:\/\/wordpress.org\/\">https:\/\/wordpress.org\/<\/a><\/span><\/span><\/span> Profile<\/th><th>Location<\/th><\/tr><\/thead><tbody><tr><td>Rico F. L\u00fcthi<\/td><td><a href=\"https:\/\/profiles.wordpress.org\/rfluethi\/\">@rfluethi<\/a><\/td><td>Switzerland<\/td><\/tr><tr><td>Sumit Singh<\/td><td><a href=\"https:\/\/profiles.wordpress.org\/sumitsingh\/\">@sumitsingh<\/a><\/td><td>India<\/td><\/tr><tr><td>Sonali Prajapati<\/td><td><a href=\"https:\/\/profiles.wordpress.org\/sonaliprajapati\/\">@sonaliprajapati<\/a><\/td><td>India<\/td><\/tr><tr><td>SAndrew<\/td><td><a href=\"https:\/\/profiles.wordpress.org\/andrewssanya\/\">@andrewssanya<\/a><\/td><td>Uganda<\/td><\/tr><tr><td>Rade Jeki\u0107<\/td><td><a href=\"https:\/\/profiles.wordpress.org\/rjekic\/\">@rjekic<\/a><\/td><td>Serbia<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Total:<\/strong> 5 participants<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Voices &amp; Perspectives<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The introductions highlighted the geographic and biographical breadth of the team. Paths into the WordPress community vary widely: from a developer whose first contribution grew out of frustration, to a manager of local language projects, to community supporters and digital skill facilitators. <a href=\"https:\/\/profiles.wordpress.org\/sonaliprajapati\/\">@sonaliprajapati<\/a> shared her experience from the Indian WordPress community. This diversity is relevant to the direction of the Office Hours because it shows the range of needs and perspectives that contributors bring to the format.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Topics Discussed<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">1. 60-Minute Structure<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Discussion:<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">On the question of meeting duration, <a href=\"https:\/\/profiles.wordpress.org\/rjekic\/\">@rjekic<\/a> noted that while 60 minutes should be set as the frame, many meetings would likely end earlier in practice. This point mattered to the group because the format is intended to be distinct from the previous Coffee Hours, which were enjoyable but not outcome-oriented.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"https:\/\/profiles.wordpress.org\/sumitsingh\/\">@sumitsingh<\/a> argued that the real value of the Office Hours lies in the live connection. In <span tabindex='0' class='glossary-item-container'>Slack<span class='glossary-item-hidden-content'><span class='glossary-item-header'>Slack<\/span> <span class='glossary-item-description'>Slack is a Collaborative Group Chat Platform <a href=\"https:\/\/slack.com\/\">https:\/\/slack.com\/<\/a>. The WordPress community has its own Slack Channel at <a href=\"https:\/\/make.wordpress.org\/chat\/\">https:\/\/make.wordpress.org\/chat\/<\/a><\/span><\/span><\/span>, international contributors do not get to know each other personally, which is essential for building trust and long-term commitment to the team. This argument was a key factor in the group\u2019s conscious decision against a purely asynchronous format.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">There was consensus that perfect English should not be a prerequisite. Open exchange with the broader community takes priority.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Outcome:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Duration: 60 minutes, flexible downward<\/li>\n\n\n\n<li>Character: informal in tone, outcome-oriented in output<\/li>\n\n\n\n<li>Linguistic openness as a deliberate principle<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Open questions:<\/strong> None.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">2. Recurring Agenda Items<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Discussion:<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The group developed an agenda structure that gives each meeting a reliable framework without losing the informal character. A central point of discussion was the advance announcement of the main topic: this was introduced specifically so that non-native English speakers can prepare both in terms of content and language. This addresses a real barrier for international contributors.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It was also agreed that moderation and note-taking will rotate among team members in order to distribute responsibility. In addition, at least one <span tabindex='0' class='glossary-item-container'>team rep<span class='glossary-item-hidden-content'><span class='glossary-item-header'>Team Rep<\/span> <span class='glossary-item-description'>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.<\/span><\/span><\/span> should be present at each meeting to ensure overall coordination.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Outcome:<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The following items will be a fixed part of every session:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Welcome &amp; onboarding<\/li>\n\n\n\n<li>Brief introductions<\/li>\n\n\n\n<li>Topic presentation (5\u201310 minutes) on the main topic<\/li>\n\n\n\n<li>Open discussion<\/li>\n\n\n\n<li>Review of open action items from previous meetings<\/li>\n\n\n\n<li>Definition of next steps including responsible persons<\/li>\n\n\n\n<li>Setting the date, moderator and note-taker for the next meeting<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Open questions:<\/strong> None.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">3. Onboarding New Contributors<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Discussion:<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A major focus of the discussion was how to prevent new contributors from dropping off after their initial engagement \u2014 particularly after WordCamps. The team\u2019s experience shows that motivation is often high at first but fades quickly without concrete, low-barrier tasks. Thumbnail creation and translations were cited as examples of suitable entry-level tasks.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This observation led to a broader point: the Training Team needs specialized groups so that both new and existing contributors can get involved and achieve results quickly. Three types were discussed: the existing Guides, topic-specific groups for developing new learning paths, and regional groups for localized learning resources.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Coordination of these groups is to run through the TT-Admins and the Office Hours. An important point raised by the group: transparency is essential so that it remains clear to everyone why particular decisions were made. Without this transparency, the group concluded, the team risks losing touch with the broader community.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Outcome:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Low-barrier entry tasks (thumbnails, translations) as first points of contact<\/li>\n\n\n\n<li>Development of specialized groups: Guides, topic groups, regional groups<\/li>\n\n\n\n<li>Active promotion of these groups within the Training Team<\/li>\n\n\n\n<li>Transparency in coordination as a <span tabindex='0' class='glossary-item-container'>core<span class='glossary-item-hidden-content'><span class='glossary-item-header'>Core<\/span> <span class='glossary-item-description'>Core is the set of software required to run WordPress. The Core Development Team builds WordPress.<\/span><\/span><\/span> principle<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Open questions:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>How will the specialized groups be promoted and coordinated in practice?<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">4. Success Criteria for the Pilot Phase<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Discussion:<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"https:\/\/profiles.wordpress.org\/andrewssanya\/\">@andrewssanya<\/a> proposed an iterative, agile approach: each meeting identifies concrete problems, and progress on their resolution is reviewed in the following meeting. The group adopted this proposal and expanded it into a definition of success criteria.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The decisive point in the discussion was the distinction from pure attendance numbers. The group agreed that even a small but active group justifies the format, as long as topics are demonstrably turned into issues and worked on. This definition is important for the later evaluation of the pilot phase and protects the format from being prematurely judged by quantitative metrics alone.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Outcome:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Success = combination of attendance and concrete project progress<\/li>\n\n\n\n<li>Attendance numbers alone are not a criterion<\/li>\n\n\n\n<li>Progress review from meeting to meeting<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Open questions:<\/strong> None.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">5. Organization via <span tabindex='0' class='glossary-item-container'>GitHub<span class='glossary-item-hidden-content'><span class='glossary-item-header'>GitHub<\/span> <span class='glossary-item-description'>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 \u2018pull request\u2019 where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. <a href=\"https:\/\/github.com\/\">https:\/\/github.com\/<\/a><\/span><\/span><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Discussion:<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The decision to organize via GitHub was unanimous, since the Training Team already works with it and no additional tooling barrier should be introduced. Topic proposals are collected as issues at <a href=\"https:\/\/github.com\/rfluethi\/wpt-office-hours\/issues\" target=\"_blank\" rel=\"noreferrer noopener\">wpt-office-hours \/ issues<\/a>; the respective moderator selects the agenda from these.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"https:\/\/profiles.wordpress.org\/rfluethi\/\">@rfluethi<\/a> encouraged all participants to actively contribute to shaping the repository. Specifically, it was agreed that <a href=\"https:\/\/profiles.wordpress.org\/andrewssanya\/\">@andrewssanya<\/a> and <a href=\"https:\/\/profiles.wordpress.org\/rfluethi\/\">@rfluethi<\/a> will review the existing repository templates and the Training Team\u2019s issue templates for potential improvements.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">After the pilot phase, the repository is to be transferred into the official Training Team structures. This temporary solution was chosen deliberately to allow the pilot to start quickly without waiting for formal processes.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Outcome:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Topic proposals as issues in the pilot repository<\/li>\n\n\n\n<li>Moderator selects the agenda from the issues<\/li>\n\n\n\n<li>Templates to be reviewed (<a href=\"https:\/\/profiles.wordpress.org\/andrewssanya\/\">@andrewssanya<\/a>, <a href=\"https:\/\/profiles.wordpress.org\/rfluethi\/\">@rfluethi<\/a>)<\/li>\n\n\n\n<li>Transfer to the official Training Team repository after the pilot phase<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Open questions:<\/strong> None.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">6. Tracking Open Action Items<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Discussion:<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For tracking action items, the group deliberately opted to use the Training Team\u2019s existing issue system rather than building a parallel tracking structure in the pilot repository. The rationale: Office Hours tasks should not exist in isolation alongside the rest of the team\u2019s work, but be part of it. To still distinguish them from the broader backlog, a dedicated label will be introduced.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Outcome:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Action items are created via <a href=\"https:\/\/github.com\/WordPress\/Learn\/issues\">github.com\/WordPress\/Learn\/issues<\/a><\/li>\n\n\n\n<li>New issues via the form at <a href=\"https:\/\/github.com\/WordPress\/Learn\/issues\/new\/choose\">github.com\/WordPress\/Learn\/issues\/new\/choose<\/a><\/li>\n\n\n\n<li>Dedicated Office Hours label for differentiation<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Open questions:<\/strong> None.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Decisions<\/h2>\n\n\n\n<figure class=\"wp-block-table is-style-stripes\"><table><thead><tr><th>#<\/th><th>Decision<\/th><th>Consensus?<\/th><\/tr><\/thead><tbody><tr><td>1<\/td><td>Office Hours take place monthly for 60 minutes<\/td><td>Yes<\/td><\/tr><tr><td>2<\/td><td>Action items are managed as issues in the repository <a href=\"https:\/\/github.com\/WordPress\/Learn\/issues\">github.com\/WordPress\/Learn\/issues<\/a><\/td><td>Yes<\/td><\/tr><tr><td>3<\/td><td>A dedicated Office Hours issue label will be introduced<\/td><td>Yes<\/td><\/tr><tr><td>4<\/td><td>Moderation and note-taking rotate among team members<\/td><td>Yes<\/td><\/tr><tr><td>5<\/td><td>At least one team rep should be present at each meeting to ensure overall coordination<\/td><td>Yes<\/td><\/tr><tr><td>6<\/td><td>Pilot phase success = combination of attendance and project progress<\/td><td>Yes<\/td><\/tr><tr><td>7<\/td><td>Next Office Hours on May 23, 2026, 14:00 UTC, moderation: <a href=\"https:\/\/profiles.wordpress.org\/rjekic\/\">@rjekic<\/a><\/td><td>Yes<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\"><em>Rationale for Decision 4 (Rotation):<\/em> Rotation was chosen deliberately as a countermodel to fixed moderation, in order to distribute responsibility and give different team members the opportunity to actively shape the format.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><em>Rationale for Decision 6 (Success criteria):<\/em> The proposal came from <a href=\"https:\/\/profiles.wordpress.org\/andrewssanya\/\">@andrewssanya<\/a> as part of an iterative, agile approach. The group explicitly followed the reasoning that even small, active groups justify the format, as long as topics are demonstrably turned into issues.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Action Items<\/h2>\n\n\n\n<figure class=\"wp-block-table is-style-stripes\"><table><thead><tr><th>Issue<\/th><th>Task<\/th><th>Responsible<\/th><th>Status<\/th><\/tr><\/thead><tbody><tr><td><a href=\"https:\/\/github.com\/WordPress\/Learn\/issues\/3413\">#3413<\/a><\/td><td>Create and publish meeting notes<\/td><td><a href=\"https:\/\/profiles.wordpress.org\/rfluethi\/\">@rfluethi<\/a><\/td><td>Done<\/td><\/tr><tr><td><a href=\"https:\/\/github.com\/WordPress\/Learn\/issues\/3414\">#3414<\/a><\/td><td>Update meeting templates in the repository<\/td><td><a href=\"https:\/\/profiles.wordpress.org\/rfluethi\/\">@rfluethi<\/a><\/td><td>Done<\/td><\/tr><tr><td><a href=\"https:\/\/github.com\/WordPress\/Learn\/issues\/3415\">#3415<\/a><\/td><td>Review task documentation template based on the existing issue template<\/td><td><a href=\"https:\/\/profiles.wordpress.org\/andrewssanya\/\">@andrewssanya<\/a><\/td><td>Open<\/td><\/tr><tr><td><a href=\"https:\/\/github.com\/WordPress\/Learn\/issues\/3416\">#3416<\/a><\/td><td>Prepare and publish a poll on preferred meeting time<\/td><td><a href=\"https:\/\/profiles.wordpress.org\/sumitsingh\/\">@sumitsingh<\/a><\/td><td>Open<\/td><\/tr><tr><td><a href=\"https:\/\/github.com\/WordPress\/Learn\/issues\/3417\">#3417<\/a><\/td><td>Publish admin roster post (TT-Admins)<\/td><td><a href=\"https:\/\/profiles.wordpress.org\/sumitsingh\/\">@sumitsingh<\/a><\/td><td>Open<\/td><\/tr><tr><td><a href=\"https:\/\/github.com\/WordPress\/Learn\/issues\/3418\">#3418<\/a><\/td><td>Publish call for Training Table lead at <span tabindex='0' class='glossary-item-container'>WordCamp<span class='glossary-item-hidden-content'><span class='glossary-item-header'>WordCamp<\/span> <span class='glossary-item-description'>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\u2019ve learned throughout the year and share the joy. <a href=\"https:\/\/central.wordcamp.org\/about\/\">Learn more<\/a>.<\/span><\/span><\/span> Europe<\/td><td><a href=\"https:\/\/profiles.wordpress.org\/sumitsingh\/\">@sumitsingh<\/a><\/td><td>Open<\/td><\/tr><tr><td><a href=\"https:\/\/github.com\/WordPress\/Learn\/issues\/3419\">#3419<\/a><\/td><td>Follow up with the <span tabindex='0' class='glossary-item-container'>Meta<span class='glossary-item-hidden-content'><span class='glossary-item-header'>Meta<\/span> <span class='glossary-item-description'>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.<\/span><\/span><\/span> Team regarding the TT-Admins Slack channel<\/td><td><a href=\"https:\/\/profiles.wordpress.org\/rjekic\/\">@rjekic<\/a><\/td><td>Open<\/td><\/tr><tr><td><a href=\"https:\/\/github.com\/WordPress\/Learn\/issues\/3420\">#3420<\/a><\/td><td>Reach out to Nikola and Maria as a fallback option for WordCamp Europe<\/td><td><a href=\"https:\/\/profiles.wordpress.org\/rjekic\/\">@rjekic<\/a><\/td><td>Open<\/td><\/tr><tr><td><a href=\"https:\/\/github.com\/WordPress\/Learn\/issues\/3421\">#3421<\/a><\/td><td>Host and moderate the next Office Hours on May 23, 2026<\/td><td><a href=\"https:\/\/profiles.wordpress.org\/rjekic\/\">@rjekic<\/a><\/td><td>Open<\/td><\/tr><tr><td><a href=\"https:\/\/github.com\/WordPress\/Learn\/issues\/3422\">#3422<\/a><\/td><td>Set up Office Hours issue label in the repository<\/td><td><a href=\"https:\/\/profiles.wordpress.org\/sumitsingh\/\">@sumitsingh<\/a><\/td><td>Done<\/td><\/tr><tr><td><a href=\"https:\/\/github.com\/WordPress\/Learn\/issues\/3423\">#3423<\/a><\/td><td>Add next Office Hours meeting to the Make WordPress Training website<\/td><td><a href=\"https:\/\/profiles.wordpress.org\/sumitsingh\/\">@sumitsingh<\/a><\/td><td>Done<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Follow-up from Previous Meeting<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><em>First meeting \u2014 no entries.<\/em><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Next Meeting<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Date:<\/strong> May 23, 2026<br><strong>Time:<\/strong> 14:00 UTC<br><strong>Moderator:<\/strong> <a href=\"https:\/\/profiles.wordpress.org\/rjekic\/\">@rjekic<\/a><br><strong>Note-Taker:<\/strong> TBD<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Proposed topics:<\/strong> See open issues at <a href=\"https:\/\/github.com\/rfluethi\/wpt-office-hours\/issues\">github.com\/rfluethi\/wpt-office-hours\/issues<\/a><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Other \/ Notes<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Topic proposals for upcoming Office Hours can be submitted at any time as issues at <a href=\"https:\/\/github.com\/rfluethi\/wpt-office-hours\/issues\">github.com\/rfluethi\/wpt-office-hours\/issues<\/a>.<\/li>\n\n\n\n<li>Support for contributing: <a href=\"https:\/\/wordpress.slack.com\/archives\/C02RW657Q\">#training<\/a> channel, <a href=\"https:\/\/make.wordpress.org\/training\/handbook\/getting-started\/\">onboarding program<\/a>, <a href=\"https:\/\/make.wordpress.org\/training\/handbook\/guide-program\/\">Guide program<\/a>.<\/li>\n\n\n\n<li>Additional topics discussed during the meeting that led to action items but are not listed as separate topics above: establishing an admin roster (TT-Admins), scheduling preferences via poll, Training Team representation at the WordCamp Europe <span tabindex='0' class='glossary-item-container'>Contributor Day<span class='glossary-item-hidden-content'><span class='glossary-item-header'>Contributor Day<\/span> <span class='glossary-item-description'>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 <a href=\"https:\/\/make.wordpress.org\/\">https:\/\/make.wordpress.org\/<\/a> There are many teams that people can participate in, each with a different focus. <a href=\"https:\/\/2017.us.wordcamp.org\/contributor-day\/\">https:\/\/2017.us.wordcamp.org\/contributor-day\/<\/a> <a href=\"https:\/\/make.wordpress.org\/support\/handbook\/getting-started\/getting-started-at-a-contributor-day\/\">https:\/\/make.wordpress.org\/support\/handbook\/getting-started\/getting-started-at-a-contributor-day\/<\/a><\/span><\/span><\/span>, and setting up a dedicated TT-Admins Slack channel.<\/li>\n<\/ul>\n<p class=\"o2-appended-tags\"><a href=\"https:\/\/make.wordpress.org\/training\/tag\/meeting-recap\/\" class=\"tag\"><span class=\"tag-prefix\">#<\/span>meeting-recap<\/a>, <a href=\"https:\/\/make.wordpress.org\/training\/tag\/office-hours\/\" class=\"tag\"><span class=\"tag-prefix\">#<\/span>office-hours<\/a>, <a href=\"https:\/\/make.wordpress.org\/training\/tag\/training\/\" class=\"tag\"><span class=\"tag-prefix\">#<\/span>training<\/a>, <a href=\"https:\/\/make.wordpress.org\/training\/tag\/training-team\/\" class=\"tag\"><span class=\"tag-prefix\">#<\/span>training-team<\/a><\/p><nav class='o2-post-footer-actions'><ul class='o2-post-footer-action-row'><li class='o2-post-footer-action'><a href=\"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Ftraining%2F2026%2F04%2F20%2Foffice-hours-meeting-recap-18th-april-2026%2F%23respond&#038;locale=en_US\" title=\"Login to Reply\"  class=\"genericon  genericon-reply\"  data-action=\"login-to-reply\"  data-actionstate=\"default\" >Login to Reply<\/a><\/li><\/ul><div class='o2-post-footer-action-likes'><\/div><ul class='o2-post-footer-action-row'><\/ul><\/nav>","protected":false},"excerpt":{"rendered":"<p>Date: April 18, 2026Time: 14:00\u201315:00 UTCPlatform: ZoomRecording: Not recordedModerator: Rico F. L\u00fcthi (@rfluethi)Note-Taker: Rico F. L\u00fcthi (@rfluethi) Related links: Meeting Context This was the first meeting of the Training Team\u2019s new Office Hours format. The format replaces the previous Coffee Hours, which generated more than 90 ideas over roughly eight sessions but resulted in very [&hellip;]<\/p>\n","protected":false},"author":10240474,"featured_media":0,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[57],"tags":[1067,2290,339,1041],"class_list":["post-154863","post","type-post","status-publish","format-standard","hentry","category-meeting-recap","tag-meeting-recap","tag-office-hours","tag-training","tag-training-team","author-rfluethi"],"revision_note":"","jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/make.wordpress.org\/training\/wp-json\/wp\/v2\/posts\/154863","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/make.wordpress.org\/training\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/make.wordpress.org\/training\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/make.wordpress.org\/training\/wp-json\/wp\/v2\/users\/10240474"}],"replies":[{"embeddable":true,"href":"https:\/\/make.wordpress.org\/training\/wp-json\/wp\/v2\/comments?post=154863"}],"version-history":[{"count":11,"href":"https:\/\/make.wordpress.org\/training\/wp-json\/wp\/v2\/posts\/154863\/revisions"}],"predecessor-version":[{"id":157458,"href":"https:\/\/make.wordpress.org\/training\/wp-json\/wp\/v2\/posts\/154863\/revisions\/157458"}],"wp:attachment":[{"href":"https:\/\/make.wordpress.org\/training\/wp-json\/wp\/v2\/media?parent=154863"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/make.wordpress.org\/training\/wp-json\/wp\/v2\/categories?post=154863"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/make.wordpress.org\/training\/wp-json\/wp\/v2\/tags?post=154863"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}