Hi all, It looks like survey questions submitted have tapered off. Seeking lazy consensus to lock the thread and start curating/editing the final survey based on these questions and feedback starting Monday.
Thanks, -e- Evan Rusackas Preset | preset.io Apache Superset PMC On Aug 28, 2023 at 10:31 AM -0600, Evan Rusackas <e...@preset.io.invalid>, wrote: > Hi all, > > Since we’ve gathered lazy consensus, I’ve gone ahead and unlocked this > discussion: > > https://github.com/apache/superset/discussions/24968 > > Please keep comments general interest and try to add comments/improvements to > existing questions rather than proposing duplicates/alternates. Just… help us > keep this orderly. :D > > Looking forward to going through this with PMC member volunteers when there’s > a critical mass, and putting the survey together! > > Thanks again, > > -e- > > Evan Rusackas > Preset | preset.io > Apache Superset PMC > On Aug 22, 2023 at 1:15 PM -0600, Evan Rusackas <e...@preset.io>, wrote: > > Hello Superset community! > > > > This has come up in may places many times, but I think it’s time that the > > rubber hit the road, and we answer all our burning questions about > > Superset’s usage, and how folks would like to see its roadmap take shape. > > > > To this end, I’d like to propose for lazy consensus the following game plan > > a means by which we can collaboratively build an annual survey by, of, and > > for the Superset community. > > > > 1) Propose the idea of a community-wide annual survey for official > > consensus. DONE! > > 2) Start a Github Discussion where anyone can suggest questions that may > > become part of the survey. Discussions can happen in comments, as can > > advisory voting with thumbs up/down. > > 3) Once things settle down, volunteers from the PMC will > > deduplicate/consolidate/edit the questions > > 4) Questions will be added to a survey, using an appropriately featured > > tool, e.g. SurveyMonkey. Preset is willing to sponsor this expense. > > 5) We will all spread the survey far and wide, seeking as many respondents > > as possible within the usual fora (Slack, dev mailing list, Github, > > Superset Community Newsletter) and opportunistically share in other circles > > as well (LinkedIn, other Slack communities, conferences, etc.). > > 6) To garner participation, Preset will sponsor some degree of prizes > > (Superset swag, and more) for randomly selected participants > > 7) At the end of the survey window (TBD), data will be aggregated and/or > > anonymized as needed, to build a public dataset for all in the community to > > use, and (ideally) build and share Superset dashboards to elucidate > > community demographics, interests, and ambitions. > > > > You’ll note that I’m NOT going into the lines and flows/forks of questions > > here. I’ll propose those on the GitHub discussion to seed things there if > > this general procedure makes sense. > > > > We hope that this process will allow *all* individuals and organizations to > > provide generally-applicable questions that will help us understand > > Superset’s current utilization, and help steer the community’s efforts > > (engineering and otherwise) in the right direction to help both the product > > and it’s user base flourish. > > > > Feel free to discuss, and if nobody objects to this idea, we’ll proceed as > > outlined beginning on Monday. > > > > Thank you, > > > > Evan Rusackas > > Preset | preset.io > > Apache Superset PMC
