Update office hours docs (#412)

Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>

src/_engineering/team-practices/index.md

@@ -37,42 +37,3 @@ On a weekly basis (generally Thursdays), Engineering and Product leadership meet
 - ping engineers on Slack for any needed follow-up
 
 During the process of creating engineering assignments for the coming week, Product and Engineering leadership will take care that each engineer is assigned at least one small or medium-sized work item (`<=4` weight) _in addition_ to any larger long-running work items. This is to that ensure every engineer has the ability to ship at least one work item in the coming week, per the Engineering team's standard practice - and that at any time if an engineer becomes blocked on a larger work item (waiting for code review feedback, for instance), they can immediately fall back to the smaller item as needed.
-
-### Weekly Office Hours
-
-Every Wednesday, the Meltano team meets with our users and community members. The main objectives of this meeting are:
-
-1. To gain outside perspective on product direction. Feedback can corroborate our direction and intuitions, but it can also show us perspectives which we may not yet have considered.
-2. To share internal deliberations with the community. The goal here is to spread awareness while gaining benefit of insight from external perspectives.
-3. To hear directly and "face to face" from community members on topics they care about. We invite every Meltano community member to openly share any pressing topics or questions they might have.
-
-#### Sourcing Contributors
-
-- Within the week or two leading up to the office hours, look out for at least one or two community members and corresponding topics which can benefit from synchronous communication.
-- Prep a list of contributor names so we can call them out during the session as time allows. (Use a dedicated slide with their names or aliases if warranted.)
-- Timebox rotating topics and set expectations ahead of time in the slides: e.g. 15 minutes for dedicated topic, 45 minutes for questions, debugging, AMA, etc.
-
-#### Best Practices
-
-- When discussions are in progress, drop the screenshare in order to give participants more face time.
-- Be aware that the owner's view layout (gallery or otherwise) also changes the view for others.
-- Share any relevant links in the zoom chat.
-
-#### Office Hours Planning
-
-During the weekly Thursday sync between Engineering and Product leadership, Product and Engineering leadership will perform the following maintenance:
-
-1. Move those topics on the [Office Hours board](https://github.com/orgs/meltano/projects/9) in GitHub into the "Discussed" column, effectively resetting the "Up Next" list for the upcoming week.
-2. For any upcoming, in-progress, or recently released features that need discussion or refinement:
-   1. Move into `Up Next` on the [Office Hours board](https://github.com/orgs/meltano/projects/9) in GitHub.
-   2. Tag an engineer or another team member on the issue, requesting grooming of the description - or any other needed prep, per the engineer's discretion.
-
-If fewer than 3 topics are selected as candidates for discussion in the upcoming week, and/or if one or more topics require community member attendance, then Engineering or Product leadership will raise these concerns as new threads in the `#office-hours-planning` channel.
-
-#### Office Hours Content Escalations
-
-Our goal is to have 3 medium-sized topics for each office hours, roughly 30-45 minutes of internally-curated content in order to make the most of our attendees' valuable time.
-
-In cases where there is an expected shortage of Office Hours content, reach out to community members who have raised topics or opened MRs with us recently. Especially relevant are contributors who have proposed net-new functionality, including new plugins, new capabilities, and other feature improvements which are relevant for team discussion. Community members with long-running or outstanding MRs also make good invitees, in hopes that a face-to-face conversation could unblock or otherwise assist the contributor's MR to progress forward.
-
-We will not cancel Office Hours sessions for lack of content, but may opt to conclude the session early, any time after 10 minutes elapsed. Sessions will always be held open for 10 minutes minimum, to allow time for community members to join and offer proposed topics or questions.

src/_marketing/community.md

@@ -4,6 +4,46 @@ title: "Community"
 weight: 2
 ---
 
+## Office Hours
+
+Every other Wednesday, the Meltano team meets with our users and community members. The main objectives of this meeting are:
+
+1. To gain outside perspective on product direction. Feedback can corroborate our direction and intuitions, but it can also show us perspectives which we may not yet have considered.
+2. To share internal deliberations with the community. The goal here is to spread awareness while gaining benefit of insight from external perspectives.
+3. To hear directly and "face to face" from community members on topics they care about. We invite every Meltano community member to openly share any pressing topics or questions they might have.
+
+### Sourcing Contributors
+
+- Within the week or two leading up to the office hours, look out for at least one or two community members and corresponding topics which can benefit from synchronous communication.
+- Prep a list of contributor names so we can call them out during the session as time allows. (Use a dedicated slide with their names or aliases if warranted.)
+- Timebox rotating topics and set expectations ahead of time in the slides: e.g. 15 minutes for dedicated topic, 45 minutes for questions, debugging, AMA, etc.
+
+### Best Practices
+
+- When discussions are in progress, drop the screenshare in order to give participants more face time.
+- Be aware that the owner's view layout (gallery or otherwise) also changes the view for others.
+- Share any relevant links in the zoom chat.
+
+### Office Hours Planning
+
+Product leadership will perform the following maintenance:
+
+1. Move those topics on the [Office Hours board](https://github.com/orgs/meltano/projects/9) in GitHub into the "Discussed" column, effectively resetting the "Up Next" list for the upcoming week.
+2. For any upcoming, in-progress, or recently released features that need discussion or refinement:
+   1. Move into `Up Next` on the [Office Hours board](https://github.com/orgs/meltano/projects/9) in GitHub.
+   2. Tag an engineer or another team member on the issue, requesting grooming of the description - or any other needed prep, per the engineer's discretion.
+
+If fewer than 3 topics are selected as candidates for discussion in the upcoming week, and/or if one or more topics require community member attendance, then Engineering or Product leadership will raise these concerns as new threads in the `#office-hours-planning` channel.
+
+### Office Hours Content Escalations
+
+Our goal is to have 3 medium-sized topics for each office hours, roughly 30-45 minutes of internally-curated content in order to make the most of our attendees' valuable time.
+
+In cases where there is an expected shortage of Office Hours content, reach out to community members who have raised topics or opened MRs with us recently. Especially relevant are contributors who have proposed net-new functionality, including new plugins, new capabilities, and other feature improvements which are relevant for team discussion. Community members with long-running or outstanding MRs also make good invitees, in hopes that a face-to-face conversation could unblock or otherwise assist the contributor's MR to progress forward.
+
+We will not cancel Office Hours sessions for lack of content, but may opt to conclude the session early, any time after 10 minutes elapsed. Sessions will always be held open for 10 minutes minimum, to allow time for community members to join and offer proposed topics or questions.
+
+
 ## Community Support Tools
 
 ### Slack

src/_marketing/index.md

@@ -7,40 +7,21 @@ permalink: /marketing/
 
 Welcome to Meltano marketing.
 
-## Weekly Community Activities
+## Community Activities
 
 The Meltano convenes regularly to generate content for community and learning purposes.
 
 These items include:
 
-- **Office Hours**: Community meeting for discussion about upcoming features and general Q&A
-- **Demo Day**: Community meeting every other Thursday showing off what has shipped, demonstrated by each authoring participant as available
+- **Office Hours**: Every 2 week community meeting for discussion about upcoming features and general Q&A
 - **Meltano / SDK Release**: the actual software release, which generates a changelog, version number, and all of the previous content for the week
 
-Each item (linked below) has a corresponding guide to promoting that activity. Each week should roughly follow the following content schedule:
-
-| Day       | Content                                                   |
-| --------- | --------------------------------------------------------- |
-| Monday    | Release blog & promotion |
-| Tuesday   | Social promotion of weekly activity                       |
-| Wednesday | Social promotion of weekly activity                       |
-| Thursday  | Thursday release blog & promotion, weekly newsletter      |
-| Friday    | Demo day blog & promotion                                 |
-
---
-
-Meltano is the infrastructure for the modern data stack that enables you to install, configure, manage, and deploy the tools of your choice, such as Singer, dbt, Airflow, Great Expectations, with Lightdash and Superset. Meltano also natively offers software engineering best practices to the stack by version controlling everything, enabling cross-pluging runs and testing, and isolated environments for dev and prod.
-
 ### GET STARTED WITH MELTANO
  - **Project Home**: https://meltano.com
- - **GitHub**: https://gitlab.com/meltano/meltano
+ - **GitHub**: https://github.com/meltano/meltano
  - **Install Meltano**: https://github.com/meltano/meltano
  - **Tutorials**: https://meltano.com/tutorials/
  - **Join Us On Slack**: https://meltano.com/slack
  - **Blog**: https://meltano.com/blog/
  - **Twitter**: https://twitter.com/meltanodata
  - **SUBSCRIBE for more videos**: http://www.youtube.com/subscription_center?add_user=meltano
-
-```
-
-```

src/_product/index.md

@@ -14,15 +14,9 @@ Use the private [#internal-product](https://meltano.slack.com/archives/C02MBDUHC
 
 ### Who to contact
 
-For each Meltano property, we have a primary point of contact:
+Refer to the [Guilds](/guilds) section of the handbook for who to reach out to.
 
-- Meltano - Taylor & Will Da Silver
-- Meltano SDK - Edgar & Ken
-- MeltanoHub - Taylor
-- MeltanoLabs - Pat
-- Handbook / Website - Douwe
-
-You should feel comfortable reaching out to each of us either in issues or on Slack if you have questions or concerns about any of these.
+You should feel comfortable reaching out to any of us either in issues or on Slack if you have questions about these product areas.
 
 ## Responsibilities