viirya commented on issue #16800: URL: https://github.com/apache/datafusion/issues/16800#issuecomment-3085726035
> Shall we file (another) ticket to discuss the process? Yea, as it is not directly related to this change. > One way we could proceed is to document some rough guidelines in the docs site, and then maybe add a label we can use to tag issues with proposals, so the current list is easier for people to find. Sounds good to me. In Spark, SPIPs are conducted through the dev mailing list. But since the DataFusion community seems more accustomed to using GitHub issues for discussions, it might be a good idea to adopt that approach instead. Just wondering — is it possible in GitHub to enforce a specific issue format based on the label? For example, could we require a certain template or structure for issues labeled as "design-proposal"? -- 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-unsubscr...@datafusion.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org For additional commands, e-mail: github-h...@datafusion.apache.org
