Hello Apache Superset community! As you may have already heard, the Superset community is attempting to reshape parts of how we tackle certain administrative tasks in our project, via what we’re calling the Superset Operational Model. It provides an opportunity to tackle a number of tasks as a set of “working groups” that will meet periodically. These groups will take input from—and report back to—this mailing list and other community touchpoints. All working groups (and their work) is completely open to all here who wish to be involved. We encourage you to participate, synchronously or asynchronously, on upcoming email threads (more info below), the Slack workspace or in these gatherings announced below. All of the action items discussed in these meetings will be tracked on this Github Project board.
All events are posted on the Superset Community Calendar. Also note that if you wish to add a Superset-related event to this calendar, just send an invitation to [email protected]. The next Operational Roundup is taking place this Thursday 2/17 at 9:00am Pacific time. You can access the notes here, to add a technical or non-technical agenda item. Each meeting will also cover what’s happening in these working groups, and more information on how you can participate. The zoom link is on the calendar - please feel free to join if you’re able! The Operational Roundup notes below contain a brief accounting of what was discussed in these recent syncs, but we’ll continue to echo these updates to the dev@ list as well. While this initial version is a bit of a digest edition, we’ll be sending these updates out individually in the future to be as timely as possible. ************************************************ Operational Model Roundup Last met: 1/20 Next meeting: 2/17 Updates: see all historical notes and upcoming agenda items available here. ************************************************ Communication Group Last met: 2/9 Next meeting: 2/23 Slack channel: #operational-model-communication Updates: • Issue triage — Feature requests, and support questions, etc. have been moved from Issues to Discussions. Will schedule an issue triage/tagging bash in Feb. Email Srini if interested (committer access would be very helpful to actually DO the work). • Public calendar • Needs to be addedng to docs/wiki/readme/etc. • Having an event? Just invite [email protected] • PMC/Committers can get access as-needed to manage • SIP board • Srini/Grace/Evan went through and bumped everything into its proper status. We can go through and try to move each to the next step in another sweep • Gathering/sharing roadmaps - hoping to publish mid-Feb. All are welcome to share your organization’s roadmap. March 1st. Doc TBD • Building announcement templates/process for working groups to keep the community informed/involved • Github issues processing - moving things to Discussions, labelling/triaging - now with stats! ************************************************ Developer Experience Last met: 2/10 Next meeting: 2/22 Slack channel: #operational-model-developer-experience Updates: • New co-chairs selected! • Loading up known tasks onto the project board by fleshing out personas and gathering tasks from the initial doc • Discussed a working session to get some action items finished + have standup/reporting meeting to strictly discuss progress on these tasks/projects • Hugh to split out project workflow big tickets into smaller tasks to allow anyone to take ownership ************************************************ Security Last met: 12/15 Next meeting: 2/16 Slack channel: #operational-model-security Updates: • N/a - haven’t sync'd since last Operational Roundup ************************************************ Quality Last met: 1/12 Next meeting: 2/16 Slack channel: #operational-model-quality Updates: • N/a - haven’t sync'd since last Operational Roundup ************************************************ Management Track Last met: 2/2 Next meeting: 3/2 Slack channel: #operational-model-management Updates: • Rejiggered community calendar to align all working group events • Set up X.0 working group, and invited a few initial folks. More welcome! • Set up Chairs meeting (monthly) - open to anyone, visible on community calendar • PMC membership standards SIP vote passed ************************************************ X.0 Last met: 2/10 Next meeting: 2/17 Slack channel: #operational-model-x-dot-0 Updates: • Planning to release an update to Celery asap - 2.0 coming pronto! • Also deprecate Superset CLI as a supported interface? • Aligned on some items for the project board leading to a SIP-74 proposal • Attempting to align on “reasonable” major release timing (TBD) • No more than X per year • No more than one every X weeks • Discussion of potentially breaking changes historically sliding through. • We should narrow our definition of supported interfaces, to allow a more controllable semver lifecycle • Conclusions/Actions: • Open the vote for SIP-74 ASAP. Move any additional proposals to a 3.0 plan, and start working on that. • Cut a 1.5 LTS branch/release at the time that SIP-74 passes, and consider Master to be breaking, and on the road to a 2.0 RC ************************************************ Please note that ALL of these discussions and their findings/actions, will be brought up in the Superset Operational Roundup, where we can freely discuss next steps, as well as any other open-floor discussions (technical and non-technical). We’ll continue to dial in this process, optimizing for transparency and inclusion as we go. We all look forward working with you to help this community and project flourish! Thank you, Evan Rusackas Preset, Inc. • preset.io Apache Superset PMC
