Every other Wednesday, the Meltano team meets with our users and community members. The main objectives of this meeting are:
Product leadership will perform the following maintenance:
Up Nexton the Office Hours board in GitHub.
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
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.
Slack is our primary way of providing support for the community and most channels redirect folks to Slack to get help. See the support handbook for information on SLAs and what we monitor.
HubSpot is currently embeded on meltano.com. Users can message us here to receive support and are encouraged to join Slack instead of using HubSpot. At some point this will be used for lead gen instead.
Tickets are currently routed to
Occasionally we’ll do user interviews to gather product/docs feedback. These interviews are added to HubSpot.
If users share an observation about Meltano’s performance and benefits, write down what they say (verbatim) and ask them for permission to use the quote, whether fully attributed or “blinded.” If you hear use case stories, ask if we might be able to interview them and share their story.