GitHub user FelixYBW edited a comment on the discussion: Add a new backend: Bolt

>Gluten still needs to maintain its own use cases, and the proposed community 
>support model raises concerns.
The idea of “assigning” community members sounds more like an internal work 
arrangement rather than participation driven by open-source interest. If those 
three members change roles or priorities in the future, this commitment may no 
longer hold. In that case, the sustainability assumption behind this support 
model would break. This makes the project feel closer to an internal corporate 
project, and it risks losing the essence of an open-source community.

It's actually from my suggestion. I was thinking to refer to current Clickhouse 
backend way that once we have some clickhouse issue during Velox development, 
especially CI issues, we mostly ping @zzcclp to solve or review. Similarly, to 
mostly ease velox and Clickhouse backend's development,  I suggested Bolt 
backend also should have some guys we can ping to get help. The worst case is 
that if no one mentain Bolt backend one day, we will have to remove it or 
freeze it from Gluten. It's the same thing in Velox and Clickhouse backend 
actually. Like no one maintain velox backend, we will have to remove or freeze 
it. 

Also please note there is no fundamental difference of Velox and Bolt, they are 
both corporate projects now, velox is even more closed as cooperate project 
that we can't get any real committers in no matter how much we contributed and 
how hard we tried. On the other side Bolt already WIP to submit Apache 
incubatoring request and build LF foundation on failure of Apache. Bolt welcome 
PRs from outside and would like to join as initial committers.

GitHub link: 
https://github.com/apache/incubator-gluten/discussions/10929#discussioncomment-15777164

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]


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

Reply via email to