andygrove opened a new issue, #6789:
URL: https://github.com/apache/datafusion-comet/issues/6789

   ### What is the problem the feature request solves?
   
   The board resolution defines what the new project is responsible for, and 
the proposal lists the repositories that move to it. We need to agree on both 
before the DataFusion PMC votes on the proposal.
   
   ### Describe the potential solution
   
   **Scope statement**
   
   DataFusion's resolution says "software related to an extensible query 
engine". Options for Comet:
   
   1. "software related to accelerating Apache Spark using native, columnar 
execution"
   2. "software related to Spark-compatible native query execution", which 
would also cover Spark-compatible components that are not part of the Spark 
plugin
   
   **Repositories and content**
   
   - [ ] Move apache/datafusion-comet in full and rename it to apache/comet. 
GitHub redirects the old URLs, as it did when the DataFusion repositories were 
renamed.
   - [ ] Decide whether any other code moves. In #5184, @comphead suggested 
moving the `datafusion-spark` crate from apache/datafusion to Apache Comet. 
That crate is released with DataFusion and Comet depends on it, so a move needs 
agreement from the DataFusion community. Code can move between ASF projects 
after the new project exists, so this decision does not need to block the 
resolution.
   - [ ] Decide what happens to the Comet content that DataFusion hosts, such 
as the documentation at https://datafusion.apache.org/comet and the Comet posts 
on the DataFusion blog.
   
   ### Additional context
   
   Discussion: #5184
   
   When DataFusion graduated from Arrow, the repositories were discussed in a 
[separate 
thread](https://lists.apache.org/thread/ob3n0d9ky0bgrryl3xn39w9k566bq00q).
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to