You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I feel that DataFusion's community (users, contributors, stakeholders) has grown to a point where we may need to devote some more time ("resources") to more explicit organization to support that growth.
There are several factors that are driving growth
More users!
More systems "in critical production" in the sense that even small changes in behavior can be perceived as regressions for existing users
More contributors and parallel work, which increases the need for explicit roadmap and coordination.
This is my attempt to gather a meta summary of challenges related to growth in one place.
I don't always think it is easy for people to find ways to help and the PR review queue backlog is growing. For example, if I have some time to review PRs, which one would be the most helpful?
Communication channels and “where should this conversation happen?” are a source of friction.
Possibly related to above, As @neilconway recently told me, the current DataFusion communication system seems a bit "everything everywhere all the time" in the sense that there is discord, github discussions, github issues, github pull requests, slack the website, and the weekly sync call and it is not always clear how to make sure you see relevant conversations
Activity