You are viewing a plain text version of this content. The canonical link for it is here.

Posted to github@arrow.apache.org by GitBox <gi...@apache.org> on 2022/05/11 05:43:20 UTC

[GitHub] [arrow-datafusion] tustvold commented on issue #2502: [EPIC] Move Ballista to new arrow-ballista repo

tustvold commented on issue #2502:
URL: https://github.com/apache/arrow-datafusion/issues/2502#issuecomment-1123209315

   No objections from me, but I'm possibly not the right person to ask... As you allude to, we will need to be more careful making breaking changes to DataFusion, but nothing insurmountable.
   
   > Reduce issue tracking and PR review burden for DataFusion maintainers who are not as interested in Ballista
   
   We will need to ensure there is still sufficient review capacity for Ballista to thrive, I don't have a good feel for if this is a concern or not.
   
   > Allow each project to have top-level documentation and user guides that are targeting the appropriate audience
   
   I like this a lot, the audiences for the projects are likely rather different :+1:


-- 
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: github-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org