Repository navigation
docs: add proposal to establish Apache Comet as a top-level project - #6817
Merged
andygrove merged 4 commits intoOct 14, 2026
Merged
Conversation
…ject Add the draft board resolution and supporting proposal for promoting Comet from a DataFusion sub-project to a top-level Apache project, so that the community can review it in the open. The initial PMC members and committers are existing DataFusion PMC members and committers; the proposal does not promote anyone. Link the page from the About section, and use colons instead of em dashes in that section's list.
andygrove
marked this pull request as ready for review
October 9, 2026 14:39
github-actions
Bot
added
the
documentation
4 of 11 tasks
alamb
approved these changes
Oct 9, 2026
alamb
left a comment
alamb
left a comment
Contributor
There was a problem hiding this comment.
Thanks @andygrove
Looks good to me
I also wanted to mention to other readers that you posted this proposal to dev@datafusion.apache.org to make sure it has the widest possible visibility. https://lists.apache.org/thread.html/0szsfkrog2jjr2x92zl78201zh131qzq
| it became a sub-project of Apache DataFusion when DataFusion became a top-level project in | ||
| April 2024. Starting as a DataFusion sub-project made sense because of the overlap in contributors. | ||
|
|
||
| Comet is different from the other DataFusion sub-projects, which extend DataFusion: Python and Java |
Contributor
There was a problem hiding this comment.
FWIW I think the most compelling difference is that they have largely distinct and strong communities. The technical differences I think are more nuanced and not as clear ot me
Member
Author
There was a problem hiding this comment.
Agreed, that's the stronger argument. Done in 0c6a529: the paragraph now leads with the communities, and I dropped the comparison with the other sub-projects.
sunchao
approved these changes
Oct 11, 2026
Make the largely distinct DataFusion and Comet communities the main reason for the proposal, and drop the comparison with the other DataFusion sub-projects. Mention that three of the five proposed initial PMC members are ASF Members.
The proposal has consensus with no objections, so present it as the proposal and board resolution to submit. Remove the note that the DataFusion PMC has not voted and the note that the scope is under discussion, and stop calling it a draft on the About page.
andygrove
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
Closes #6791, which is tracked in #6793.
Rationale for this change
The discussion in #5184 supported promoting Comet to a top-level Apache project, and this proposal has consensus on dev@datafusion.apache.org with no objections. Its board resolution is the one to submit to the ASF board. DataFusion's proposal lived in a Google Doc. Keeping Comet's in the repository makes it public and leaves a record of what was proposed.
What changes are included in this PR?
docs/source/about/top_level_project_proposal.md, with the board resolution and supporting proposal, adapted from the one DataFusion used in 2024.The proposed initial chair is Andy Grove. The resolution's scope is "software related to accelerating Apache Spark using native, columnar execution".
The Cryptography section commits the new project to filing the ASF export notification, because Comet's native library includes third-party crates that implement cryptography (rustls and ring). That task is tracked in #6792.
How are these changes tested?
Documentation only. I built the docs with Sphinx and checked that the new page renders, appears in the About section, and adds no new warnings.
prettier --checkpasses.