DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
...
Pinot entered incubation in 2018 with strong support from LinkedIn.
Most discussions initially took place in Slack and GitHub comments.
Mentors encouraged the team that to make decisions should be made on dev@.
Regular public summaries replaced private chats.
By 2020, contributors from organisations such as Uber and StarTree, as well as several independent developers, were active on the list, and more people joined in release votes.
...
Superset joined the Incubator in 2017. Many There was a growing queue of outside pull requests were waiting for review, a common occurrence for fast-growing projects.
Mentors encouraged regular, open reviews of external work on dev@.
Within a year, contributors from several companies were active, and new committers were added from outside Airbnb.
...
Airflow experienced rapid growth after its founding in 2016.
Mentors saw that votes and decisions were being made in issue comments.
The community adopted strengthened its use of clear [DISCUSS] and [VOTE] threads linked to JIRA issues.
This kept decisions clear and supported healthy growth.
...
ECharts entered incubation in 2018, originating from Baidu, with discussions primarily conducted in Chinese.
Mentors and PPMC members started bilingual documentation and summaries of local chats on dev@.
Contributors were encouraged to post in English, even if imperfectlytheir English was imperfect, and volunteers assisted with translations.
Participation widened to include developers contributors from many multiple regions, reflecting broader community engagement.
Key Point: Inclusion can grow gradually while staying transparent.
What Mentors and PPMCs Can Do: Support bilingual summaries and be patient with contributors learning ASF communication norms.
...
APISIX joined in 2019 with strong support from one company.
Mentors encouraged rotating release managers and inviting outside contributors to lead tasks.
Public planning threads made leadership decision-making and responsibilities more visible.
By graduation, several independent contributors were leading releases and features.
...
Make decisions public
If any issues arise off-list, post a brief public summary and continue the discussion ondev@. (Pinot)Share who leadsworks
Rotate the next vote initiator, release leadmanager, or report author. (APISIX)Welcome new contributors
Post open invitations for small recurring tasks. Thank contributors publicly. (Superset)Support multiple languages and time zones
Post bilingual summaries and encourage contributors to ask for translation help. (ECharts)Keep governance visible
Use mailing lists for all [DISCUSS] and [VOTE] threads, with clear links to issues. (Airflow)Track people, not just commits
Note how many unique names join votes or reports each quarter. Mention this in reports. (Airflow, Superset)Recognise openness
Thank those who bring discussions back todev@and highlight shared effort. (Pinot)
...