Repository navigation
Agree on the initial PMC, committers, and chair for Apache Comet #6788
Description
What is the problem the feature request solves?
Part of #6793.
The board resolution that establishes Apache Comet names the initial PMC members and the chair, who becomes "Vice President, Apache Comet". The proposal also lists the initial committers. We need to agree on these before the DataFusion PMC votes on the proposal.
Describe the potential solution
When DataFusion graduated from Arrow, the initial PMC and committers were existing Arrow PMC members and committers (thread). We propose the same for Comet:
- Initial PMC: existing DataFusion PMC members who contribute to Comet and want to serve. We also propose Andrew Lamb, the DataFusion PMC chair and an ASF Member, who has taken part in the release vote for nearly every Comet release. DataFusion's initial PMC included an experienced ASF Member from Arrow in the same way.
- Initial committers: existing DataFusion committers who have contributed to Comet and want to continue.
- Chair: Andy Grove, a former chair of the Apache Arrow PMC. The chair submits the board reports, which are due monthly for the first three months and quarterly after that.
- Everyone named confirms that they want to serve before the lists are final.
Nobody is promoted as part of this process. Once Apache Comet is established, its PMC will vote on new committers and PMC members. Making it easier to recognize Comet contributors was one of the main reasons given for this proposal in #5184.
Joining Apache Comet does not change anyone's role in DataFusion.
Things to keep in mind:
- Comet releases currently rely on binding votes from the DataFusion PMC, so the new PMC needs enough active members to approve releases on its own (at least three binding votes).
- The board looks for a PMC that is not dominated by a single employer.
Tasks:
- Agree on the approach in this issue
- Confirm with each person
- Add the final lists to the proposal (Draft the Apache Comet proposal and board resolution #6791)
Additional context
Discussion: #5184
Activity