Our iterations and scheduled work are available to the public, and we encourage anyone to submit new issues.
Use the public #product channel to have open discussions about product priorities. Use the private #internal-product channel for non-public product discussions.
Refer to the Guilds section of the handbook for who to reach out to.
You should feel comfortable reaching out to any of us either in issues or on Slack if you have questions about these product areas.
The Product team will review any new issues in the Meltano group on a daily cadence and organize appropriately with labels and priority.
Product is responsible for reaching out to users and talking with them about their experiences with all Meltano properties. This is an important sensing mechanism for understanding how users interact with Meltano and it informs product priorities. We aim for an average of 4 user interviews per month at a minimum.
When evaluating a new major piece of work, we create an exploratory issue and use an opportunity assessment (some people call this “Market Requirement Doc” or MRD) to ask the following questions:
The opportunity assessment was created by Marty Cagan at Silicon Valley Product Group
Each item on the roadmap will be linked to an OKR.
On the first and third monday of the month, the Head of Product and Head of Engineering will meet to validate the current state of the roadmap. This will be a high-level discussion around progress on current items and negotiation on inclusion of items for current and upcoming months. They will also discuss spike-worthy itmes and add the appropriate labels as needed.
Key questions to ask are:
Issues that are related to Roadmap items should have the Roadmap label.
When any work needs to be prioritized that is not specifically a roadmap featue, use the following process.
content reviewneeds-engineeringMarketing PriorityIf you want to make an improvement to Meltano you don’t have to wait for Product approval, kick-off some long convoluted discussion, or worry about stepping on anyone’s toes. Submit a Pull Request (PR) with your proposed changes and we can iterate from there.
Sometimes, it can feel like we are chosing between two important things and this can be painful. However, we take the approach that anything is technically possible to build on the Meltano team so it’s a just a question of the order of operations. On a long enough timeline, we will do everything we put on the roadmap – so keep writing issues and hold onto that “it’s an AND, not OR” mindset.
Meltano uses weekly milestones to track work. They are named for the Friday on which the milestone ends, i.e. Fri: July 9, 2021.
Every Monday we will highlight for the team what the priorities are for the week by posting in #internal-announcements with links to projects and issues where more context can be found and questions can be asked.
In addition, the following should also be done:
This section is dedicated to tracking interesting open source projects that we want to keep an eye on that we don’t already have plans to integrate with. This article from BVP is useful as well.
Additionally, there are many “git for data” tools tracked in this spreadsheet. Project Nessie is another option not listed in the sheet.