findepi commented on issue #16886: URL: https://github.com/apache/datafusion/issues/16886#issuecomment-3158692489
> I have seen several projects that start as vague statements of goal and then various people provide parts of the implementation / writeups / tickets, etc and it ends up being completed (utf8view being one, porting all functions to be UDFs is another, the most recent Parquet metadata cache from [@nuno-faria](https://github.com/nuno-faria) is shaping up to be similar as well) Those are examples of implementation projects. These can span unforeseeable amount of time, depending on interested of contributors. I think DIP is a different category. DIP process should run to an end in bounded time, even if this means "timeout => rejection". There is no point in starting a DIP in 2019 and all of the sudden deciding on it in 2026. > Since all communications are public, I think any stakeholder who is interested in a feature already has the opportunity to discover and participate That works provided that all potential stakeholder are listening on a communication channel where DIPs are announced. What would be such a channel? -- 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
