Re: [DISCUSS] Gluten proposal

2023-12-31 Thread ShaoFeng Shi
mising project. > > > > And I'm glad to be one of the nominated mentors. > > > > Thanks, > > Kent Yao > > > > On 2023/12/28 03:25:56 ShaoFeng Shi wrote: > > > Hi Justin, > > > > > > Yeah, 12 months is a little tough; I have dis

Re: [DISCUSS] Gluten proposal

2023-12-29 Thread Rakesh Radhakrishnan
oject. Happy to be a mentor on this proposal during the incubation process, if you are interested. Thanks, Rakesh On Thu, Dec 28, 2023 at 6:47 AM ShaoFeng Shi wrote: > Hi Rakesh, > > Yeah, the team aware that, they plan to merge the Trino plugin into the > main repository at some point

Re: [DISCUSS] Gluten proposal

2023-12-29 Thread Yu Li
a year now. It's a promising project. > > And I'm glad to be one of the nominated mentors. > > Thanks, > Kent Yao > > On 2023/12/28 03:25:56 ShaoFeng Shi wrote: > > Hi Justin, > > > > Yeah, 12 months is a little tough; I have discussed this with the team, &

Re: [DISCUSS] Gluten proposal

2023-12-27 Thread Kent Yao
ittle tough; I have discussed this with the team, and > updated the proposal to 18 months. > > Best regards, > > Shaofeng Shi 史少锋 > Apache Kylin PMC, > Apache Incubator PMC, > Email: shaofeng...@apache.org > > Apache Kylin FAQ: https://kylin.apache.org/docs/gettingst

Re: [DISCUSS] Gluten proposal

2023-12-27 Thread ShaoFeng Shi
Hi Justin, Yeah, 12 months is a little tough; I have discussed this with the team, and updated the proposal to 18 months. Best regards, Shaofeng Shi 史少锋 Apache Kylin PMC, Apache Incubator PMC, Email: shaofeng...@apache.org Apache Kylin FAQ: https://kylin.apache.org/docs/gettingstarted/faq.html

Re: [DISCUSS] Gluten proposal

2023-12-27 Thread ShaoFeng Shi
Hi Junping, Thank you for the suggestion. I have discussed this with the team, they agree with this. I have updated abstract part of the proposal. The slogan on the document website will be updated later. Best regards, Shaofeng Shi 史少锋 Apache Kylin PMC, Apache Incubator PMC, Email: shaofeng

Re: [DISCUSS] Gluten proposal

2023-12-27 Thread ShaoFeng Shi
have a plugin > mechanism > > in > > > place to seamlessly integrate with Gluten ? > > > > > > Thanks, > > > Rakesh > > > > > > On Sat, Dec 23, 2023 at 6:13 PM ShaoFeng Shi > > > wrote: > > > > > > &

Re: [DISCUSS] Gluten proposal

2023-12-26 Thread Rakesh Radhakrishnan
erf_numbers, > pullrequest_reference, > > jira_reference etc. Will Flink and Trino already have a plugin mechanism > in > > place to seamlessly integrate with Gluten ? > > > > Thanks, > > Rakesh > > > > On Sat, Dec 23, 2023 at 6:13 PM ShaoFeng Shi > &

Re: [DISCUSS] Gluten proposal

2023-12-26 Thread Venkat Ranganathan
I am currently looking into gluten as well and have been looking ap spark acceleration in general. Available for contribution as well as mentoring. Thanks Venkat On Tue, Dec 26, 2023 at 9:53 PM Justin Mclean wrote: > Hi, > > Looks like a good proposal. Only one thing stood out to

Re: [DISCUSS] Gluten proposal

2023-12-26 Thread Justin Mclean
Hi, Looks like a good proposal. Only one thing stood out to me, while not impossible, planning to graduate in a year might not be easily achievable. Kind Regards, Justn - To unsubscribe, e-mail: general-unsubscr

Re: [DISCUSS] Gluten proposal

2023-12-26 Thread 俊平堵
ators to native engines in > data loading scenarios based on Apache Spark. > > Here is the proposal - > https://cwiki.apache.org/confluence/display/INCUBATOR/GlutenProposal > > I would be the Champion of the project. I will mentor and help the project > through the incubator wit

Re: [DISCUSS] Gluten proposal

2023-12-26 Thread Wenli Zhang
+1 I am delighted to see the proposal for Gluten and honored to be a mentor for this innovative project. I look forward to contributing my insights and helping guide Gluten through the incubation process. Thank you for this opportunity, and I am ready to support the project’s success. Best

Re: [DISCUSS] Gluten proposal

2023-12-26 Thread ShaoFeng Shi
a good question. Actually I asked the same to the team when they > > find me for coaching. > > > > As the proposal mentioned, Gluten is a middle layer between the JVM-based > > SQL engine and native libraries. It connects the two sides, and build > > common services li

Re: [DISCUSS] Gluten proposal

2023-12-25 Thread Rakesh Radhakrishnan
Trino already have a plugin mechanism in place to seamlessly integrate with Gluten ? Thanks, Rakesh On Sat, Dec 23, 2023 at 6:13 PM ShaoFeng Shi wrote: > Hi Enrico, > > This is a good question. Actually I asked the same to the team when they > find me for coaching. > > As the

Re: [DISCUSS] Gluten proposal

2023-12-24 Thread Chunen Ni
dle layer responsible for offloading Apache Spark SQL > queries to native engines. This project aims to address the CPU > computational bottleneck to offload SparkSQL operators to native engines in > data loading scenarios based on Apache Spark. > > Here is the proposal - > https://cw

Re: [DISCUSS] Gluten proposal

2023-12-23 Thread David Zollo
n Kylin dev mail group: dev-subscr...@kylin.apache.org > > > > > Felix Cheung 于2023年12月24日周日 06:00写道: > > > Very interesting. Let me know if I can help as mentor > > > > > > > > On Sat, Dec 23, 2023 at 7:30 AM tison wrote: > > > > > Thanks fo

Re: [DISCUSS] Gluten proposal

2023-12-23 Thread ShaoFeng Shi
...@kylin.apache.org Join Kylin dev mail group: dev-subscr...@kylin.apache.org Felix Cheung 于2023年12月24日周日 06:00写道: > Very interesting. Let me know if I can help as mentor > > > > On Sat, Dec 23, 2023 at 7:30 AM tison wrote: > > > Thanks for driving this proposal S

Re: [DISCUSS] Gluten proposal

2023-12-23 Thread ShaoFeng Shi
group: user-subscr...@kylin.apache.org Join Kylin dev mail group: dev-subscr...@kylin.apache.org tison 于2023年12月23日周六 23:30写道: > Thanks for driving this proposal Shaofeng :D > > +1 to support this project entering the Incuabtor. It's in good shape > to develop an OSS proje

Re: [DISCUSS] Gluten proposal

2023-12-23 Thread Felix Cheung
Very interesting. Let me know if I can help as mentor On Sat, Dec 23, 2023 at 7:30 AM tison wrote: > Thanks for driving this proposal Shaofeng :D > > +1 to support this project entering the Incuabtor. It's in good shape > to develop an OSS project with a diverse grou

Re: [DISCUSS] Gluten proposal

2023-12-23 Thread tison
Thanks for driving this proposal Shaofeng :D +1 to support this project entering the Incuabtor. It's in good shape to develop an OSS project with a diverse group. Hopefully, the Incubator can help it evaluate whether The Apache Way fits in its community and growth. One thing to be notic

Re: [DISCUSS] Gluten proposal

2023-12-23 Thread ShaoFeng Shi
Hi Enrico, This is a good question. Actually I asked the same to the team when they find me for coaching. As the proposal mentioned, Gluten is a middle layer between the JVM-based SQL engine and native libraries. It connects the two sides, and build common services like unified plan

Re: [DISCUSS] Gluten proposal

2023-12-22 Thread Enrico Olivelli
This project aims to address the CPU > computational bottleneck to offload SparkSQL operators to native engines in > data loading scenarios based on Apache Spark. Have you considered making this project a subproject of Apache Spark ? Enrico > > Here is the proposal - > https:/

[DISCUSS] Gluten proposal

2023-12-22 Thread ShaoFeng Shi
in data loading scenarios based on Apache Spark. Here is the proposal - https://cwiki.apache.org/confluence/display/INCUBATOR/GlutenProposal I would be the Champion of the project. I will mentor and help the project through the incubator with Yu Li [l...@apache.org], Kent Yao [y...@apache.org] and

Re: [DISCUSS] OneTable proposal

2023-12-15 Thread Jesus Camacho Rodriguez
y, let me address that part. > > > > > > > > > > Concerning the initial list of committers: While the project > > originated > > > > > from Onehouse (a company whose offering is powered by Apache Hudi), > > > it's > > > > >

Re: [DISCUSS] OneTable proposal

2023-12-15 Thread Carl Steinbach
that there has been an effort to have an > initial > > > > list of committers that work for a diverse range of companies > invested > > in > > > > different table formats, including Onehouse (4 committers), Microsoft > > > (2), > > > > Google (

Re: [DISCUSS] OneTable proposal

2023-12-15 Thread Jesus Camacho Rodriguez
for a diverse range of companies invested > in > > > different table formats, including Onehouse (4 committers), Microsoft > > (2), > > > Google (1), Walmart (1), Adobe (1), Cloudera (1), and Dremio (1). I > > believe > > > this diversity dispels the notion of a lack

Re: [DISCUSS] OneTable proposal

2023-12-15 Thread Ashvin A
e of companies invested in > > different table formats, including Onehouse (4 committers), Microsoft > (2), > > Google (1), Walmart (1), Adobe (1), Cloudera (1), and Dremio (1). I > believe > > this diversity dispels the notion of a lack of representation or an > > outsized

Re: [DISCUSS] OneTable proposal

2023-12-15 Thread Jean-Baptiste Onofré
itters), Microsoft (2), > Google (1), Walmart (1), Adobe (1), Cloudera (1), and Dremio (1). I believe > this diversity dispels the notion of a lack of representation or an > outsized influence from a single group in the community. > > Regarding outreach to other communities: As p

Re: [DISCUSS] OneTable proposal

2023-12-14 Thread Carl Steinbach
ion of a lack of representation or an > > outsized influence from a single group in the community. > > > > Regarding outreach to other communities: As part of the incubation > > proposal, we extended invitations to participate in this discussion and > > contribute to the

Re: [DISCUSS] OneTable proposal

2023-12-14 Thread Jesus Camacho Rodriguez
ersity dispels the notion of a lack of representation or an > outsized influence from a single group in the community. > > Regarding outreach to other communities: As part of the incubation > proposal, we extended invitations to participate in this discussion and > contribute to the project to

Re: [DISCUSS] OneTable proposal

2023-12-13 Thread Jesus Camacho Rodriguez
uence from a single group in the community. Regarding outreach to other communities: As part of the incubation proposal, we extended invitations to participate in this discussion and contribute to the project to members of the communities of the most popular OSS table formats [1][2][3][4]. Resp

Re: [DISCUSS] OneTable proposal

2023-12-13 Thread Jacques Nadeau
/foundation/marks/naming.html#startsearch > > >> > > >> On Wed, Dec 13, 2023 at 2:02 AM Jean-Baptiste Onofré > > > >> wrote: > > >> > > >>> Thanks Jesus > > >>> > > >>> XTable sounds good

Re: [DISCUSS] OneTable proposal

2023-12-13 Thread Carl Steinbach
uring > incubation; we'll update the proposal with the new name soon and share it > in this thread. > > Regarding the name-changing process and your concerns about it, we're > looking for advice based on past experiences. Specifically, we're > considering whether it'

Re: [DISCUSS] OneTable proposal

2023-12-13 Thread Jesus Camacho Rodriguez
> wrote: > >> > >>> Thanks Jesus > >>> > >>> XTable sounds good but we need a name search anyway to be sure it's > >>> suitable. > >>> > >>> Regards > >>> JB > >>> > >>> On We

Re: [DISCUSS] OneTable proposal

2023-12-13 Thread Julian Hyde
ps://www.apache.org/foundation/marks/naming.html#startsearch >> >> On Wed, Dec 13, 2023 at 2:02 AM Jean-Baptiste Onofré >> wrote: >> >>> Thanks Jesus >>> >>> XTable sounds good but we need a name search anyway to be sure it's >>> su

Re: [DISCUSS] OneTable proposal

2023-12-13 Thread Jean-Baptiste Onofré
Jean-Baptiste Onofré > wrote: > > > Thanks Jesus > > > > XTable sounds good but we need a name search anyway to be sure it's > > suitable. > > > > Regards > > JB > > > > On Wed, Dec 13, 2023 at 4:30 AM Jesus Camacho Rodriguez > >

Re: [DISCUSS] OneTable proposal

2023-12-13 Thread Jesus Camacho Rodriguez
2:02 AM Jean-Baptiste Onofré wrote: > Thanks Jesus > > XTable sounds good but we need a name search anyway to be sure it's > suitable. > > Regards > JB > > On Wed, Dec 13, 2023 at 4:30 AM Jesus Camacho Rodriguez > wrote: > > > > I've updated th

Re: [DISCUSS] OneTable proposal

2023-12-13 Thread Jean-Baptiste Onofré
Thanks Jesus XTable sounds good but we need a name search anyway to be sure it's suitable. Regards JB On Wed, Dec 13, 2023 at 4:30 AM Jesus Camacho Rodriguez wrote: > > I've updated the proposal with the new name: XTable. You can review it > here: https://cwiki.apache.org

Re: [DISCUSS] OneTable proposal

2023-12-13 Thread Jean-Baptiste Onofré
acknowledge your concern about the project name. We are working > on selecting a new name for ASF incubation that avoids confusion with any > specific corporation or product in the space. Currently we are doing some due > diligence to minimize the risk of having to change it again during

Re: [DISCUSS] OneTable proposal

2023-12-12 Thread Jesus Camacho Rodriguez
I've updated the proposal with the new name: XTable. You can review it here: https://cwiki.apache.org/confluence/display/INCUBATOR/XTable+Proposal (please also see _Project Name_ subsection) We hope this change addresses the concern that was raised during this discussion, helping to con

Re: [DISCUSS] OneTable proposal

2023-12-11 Thread Jesus Camacho Rodriguez
Thanks Julian. I was mainly considering the code, but, as you mentioned, it's probably not the primary concern. The current proposal aligns with your feedback: The project will go through the vote (and hopefully be accepted into the incubator) using the new name, so all the infra and project

Re: [DISCUSS] OneTable proposal

2023-12-11 Thread Julian Hyde
e space. Currently we are doing some > due diligence to minimize the risk of having to change it again during > incubation; we'll update the proposal with the new name soon and share it > in this thread. > > Regarding the name-changing process and your concerns about it, we&#

Re: [DISCUSS] OneTable proposal

2023-12-11 Thread Jesus Camacho Rodriguez
n with any specific corporation or product in the space. Currently we are doing some due diligence to minimize the risk of having to change it again during incubation; we'll update the proposal with the new name soon and share it in this thread. Regarding the name-changing process and your co

Re: [DISCUSS] OneTable proposal

2023-12-11 Thread Jean-Baptiste Onofré
Of course, it's a big +1 one for me. The purpose is interesting, creating "connection" with other Apache projects. Happy to be a mentor on this proposal and contribute to the project :) Thanks ! Regards JB On Mon, Dec 4, 2023 at 10:23 PM Jesus Camacho Rodriguez wrote: > >

Re: [DISCUSS] OneTable proposal

2023-12-08 Thread Stephen Williams
hared this feedback with Jesus prior to the proposal but would like to do here as well. This project is trying to make multiple open source projects work together. It would be nice to see representation from multiple of those communities. I feel that true success of this project is heavily influen

Re: [DISCUSS] OneTable proposal

2023-12-08 Thread Jacques Nadeau
8:28 AM Jacques Nadeau wrote: > I've shared this feedback with Jesus prior to the proposal but would like > to do here as well. This project is trying to make multiple open source > projects work together. It would be nice to see representation from > multiple of those communi

Re: [DISCUSS] OneTable proposal

2023-12-08 Thread Jacques Nadeau
I've shared this feedback with Jesus prior to the proposal but would like to do here as well. This project is trying to make multiple open source projects work together. It would be nice to see representation from multiple of those communities. I feel that true success of this project is he

Re: [DISCUSS] OneTable proposal

2023-12-08 Thread Ismaël Mejía
or table formats that > > > facilitates interoperability across data processing systems and query > > > engines. Currently, OneTable supports widely adopted open-source table > > > formats such as Apache Hudi, Apache Iceberg, and Delta Lake. > > > > > >

Re: [DISCUSS] OneTable proposal

2023-12-07 Thread 俊平堵
r table formats that > facilitates interoperability across data processing systems and query > engines. Currently, OneTable supports widely adopted open-source table > formats such as Apache Hudi, Apache Iceberg, and Delta Lake. > > Here is the proposal - > https://cwiki.apache

Re: [DISCUSS] OneTable proposal

2023-12-07 Thread larry mccay
an omni-directional converter for table formats that > > > facilitates interoperability across data processing systems and query > > > engines. Currently, OneTable supports widely adopted open-source table > > > formats such as Apache Hudi, Apache Iceberg, and

Re: [DISCUSS] OneTable proposal

2023-12-07 Thread PJ Fanning
ni-directional converter for table formats that > > facilitates interoperability across data processing systems and query > > engines. Currently, OneTable supports widely adopted open-source table > > formats such as Apache Hudi, Apache Iceberg, and Delta Lake. > > > > Here

Re: [DISCUSS] OneTable proposal

2023-12-07 Thread Ismaël Mejía
processing systems and query > engines. Currently, OneTable supports widely adopted open-source table > formats such as Apache Hudi, Apache Iceberg, and Delta Lake. > > Here is the proposal - > https://cwiki.apache.org/confluence/display/INCUBATOR/OneTable+Proposal > > I would

RE: Re: [DISCUSS] Incubating Proposal of Fury

2023-12-07 Thread Shawn Yang
mbers, > > > > I would like to propose a new project to the ASF incubator - Fury. > > > > Fury[1] is a high-performance, multi-language, and automatic > > serialization framework powered by JIT and zero-copy. > > > > Ant Group owns this project, and they have

Re: [DISCUSS] Incubating Proposal of Fury

2023-12-07 Thread tison
by JIT and zero-copy. > > > > Ant Group owns this project, and they have agreed to sign the SGAs and > > CCLAs for the donation. > > > > Here is their proposal - > > https://cwiki.apache.org/confluence/display/INCUBATOR/Fury+Proposal > > > &g

Re: [DISCUSS] OneTable proposal

2023-12-06 Thread Tim Bossenmaier
r table formats that > facilitates interoperability across data processing systems and query > engines. Currently, OneTable supports widely adopted open-source table > formats such as Apache Hudi, Apache Iceberg, and Delta Lake. > > Here is the proposal - > https://cwiki.apache

Re: [DISCUSS] Incubating Proposal of Fury

2023-12-06 Thread Greg Stein
i-language, and automatic > serialization framework powered by JIT and zero-copy. > > Ant Group owns this project, and they have agreed to sign the SGAs and > CCLAs for the donation. > > Here is their proposal - > https://cwiki.apache.org/confluence/display/INCUBATOR/Fury+Proposal > &

Re: [DISCUSS] OneTable proposal

2023-12-06 Thread Nicholas Jiang
OneTable[1] is an omni-directional converter for table formats that > facilitates interoperability across data processing systems and query > engines. Currently, OneTable supports widely adopted open-source table > formats such as Apache Hudi, Apache Iceberg, and Delta Lake. > >

Re: [DISCUSS] Incubating Proposal of Fury

2023-12-06 Thread tison
t; > > > > > Hi IPMC members, > > > > > > I would like to propose a new project to the ASF incubator - Fury. > > > > > > Fury[1] is a high-performance, multi-language, and automatic > > > serialization framework powered by JIT and zero-copy. > &

Re: [DISCUSS] OneTable proposal

2023-12-05 Thread Jesus Camacho Rodriguez
ct to the ASF incubator - > > OneTable. > > > > > > > > > > OneTable[1] is an omni-directional converter for table formats that > > > > > facilitates interoperability across data processing systems and > query > > > > > engines.

Re: [DISCUSS] Incubating Proposal of Fury

2023-12-05 Thread Yu Li
- Fury. > > > > Fury[1] is a high-performance, multi-language, and automatic > > serialization framework powered by JIT and zero-copy. > > > > Ant Group owns this project, and they have agreed to sign the SGAs and > > CCLAs for the donation. > > > > Here is th

Re: [DISCUSS] OneTable proposal

2023-12-04 Thread Yuanbo Liu
n omni-directional converter for table formats that > > > > facilitates interoperability across data processing systems and query > > > > engines. Currently, OneTable supports widely adopted open-source > table > > > > formats such as Apache Hudi, Apache Iceberg, a

Re: [DISCUSS] OneTable proposal

2023-12-04 Thread Jeff Zhang
ject to the ASF incubator - OneTable. > > > > > > OneTable[1] is an omni-directional converter for table formats that > > > facilitates interoperability across data processing systems and query > > > engines. Currently, OneTable supports widely adopted open-sour

Re: [DISCUSS] OneTable proposal

2023-12-04 Thread Felix Cheung
engines. Currently, OneTable supports widely adopted open-source table > > formats such as Apache Hudi, Apache Iceberg, and Delta Lake. > > > > Here is the proposal - > > https://cwiki.apache.org/confluence/display/INCUBATOR/OneTable+Proposal > > > > I would be the

Re: [DISCUSS] OneTable proposal

2023-12-04 Thread Austin Bennett
e[1] is an omni-directional converter for table formats that > facilitates interoperability across data processing systems and query > engines. Currently, OneTable supports widely adopted open-source table > formats such as Apache Hudi, Apache Iceberg, and Delta Lake. > > Here is the proposa

[DISCUSS] OneTable proposal

2023-12-04 Thread Jesus Camacho Rodriguez
such as Apache Hudi, Apache Iceberg, and Delta Lake. Here is the proposal - https://cwiki.apache.org/confluence/display/INCUBATOR/OneTable+Proposal I would be the Champion of the project. I will mentor and help the project through the incubator with Hitesh Shah [hit...@apache.org], Stamatis

Re: [DISCUSS] HoraeDB proposal

2023-12-04 Thread li gang
Hi IPMC, Von Gosling expressed he wants to become a mentor of HoraeDB and he is an ASF Member,so I added him to the list of mentors, and the proposal [1] has been updated. 1.https://cwiki.apache.org/confluence/display/INCUBATOR/HoraeDB+Proposal tison 于2023年11月24日周五 23:58写道: > Hi IPMC memb

Re: [DISCUSS] Incubating Proposal of Fury

2023-12-03 Thread jun liu
I would like to propose a new project to the ASF incubator - Fury. > > Fury[1] is a high-performance, multi-language, and automatic > serialization framework powered by JIT and zero-copy. > > Ant Group owns this project, and they have agreed to sign the SGAs and > CCLAs for the dona

Re: [DISCUSS] Incubating Proposal of Fury

2023-12-01 Thread tison
, > > > > > > I would like to propose a new project to the ASF incubator - Fury. > > > > > > Fury[1] is a high-performance, multi-language, and automatic > > > serialization framework powered by JIT and zero-copy. > > > > > > Ant Group owns

Re: [DISCUSS] Incubating Proposal of Fury

2023-12-01 Thread Enrico Olivelli
gt; > > Ant Group owns this project, and they have agreed to sign the SGAs and > > CCLAs for the donation. > > > > Here is their proposal - > > https://cwiki.apache.org/confluence/display/INCUBATOR/Fury+Proposal > > > > I would be the Champion of the project.

Re: [DISCUSS] Incubating Proposal of Fury

2023-12-01 Thread Huajie Wang
, and automatic > serialization framework powered by JIT and zero-copy. > > Ant Group owns this project, and they have agreed to sign the SGAs and > CCLAs for the donation. > > Here is their proposal - > https://cwiki.apache.org/confluence/display/INCUBATOR/Fury+Proposal > &

[DISCUSS] Incubating Proposal of Fury

2023-12-01 Thread tison
. Here is their proposal - https://cwiki.apache.org/confluence/display/INCUBATOR/Fury+Proposal I would be the Champion of the project. I will mentor and help the project through the incubator with PJ Fanning [fannin...@apache.org] Yu Li [l...@apache.org] Xin Wang [xinw...@apache.org] We are open to

Re: [DISCUSS] HoraeDB proposal

2023-11-30 Thread tison
g usage, we can evaluate and choose either way: > >> > >> 1. Rename all the artifacts before entering the incubator. > >> 2. Ask for Ant Group to grant a permission to use CeresDB > >> trademark > >> for such legacy code reference. > >> > >> D

Re: [DISCUSS] HoraeDB proposal

2023-11-30 Thread Jiacai Liu
r Ant Group to grant a permission to use CeresDB trademark for such legacy code reference. Does this make sense and your concern point? Anyway, we will stop releasing new artifacts with the name CeresDB as prioritize the renaming task. Best, tison. tison 于2023年11月29日周三 15:45写道: > > > The

Re: [DISCUSS] HoraeDB proposal

2023-11-29 Thread Jiacai Liu
r Ant Group to grant a permission to use CeresDB trademark for such legacy code reference. Does this make sense and your concern point? Anyway, we will stop releasing new artifacts with the name CeresDB as prioritize the renaming task. Best, tison. tison 于2023年11月29日周三 15:45写道: > > > The

Re: [DISCUSS] HoraeDB proposal

2023-11-29 Thread tison
once the repo transfer happens and the CLA reference will be removed. It's >100 a little bit mainly due to Cargo.lock and Golang import use "github.com/CeresDB/...". So occ Best, tison. [1] https://cwiki.apache.org/confluence/display/INCUBATOR/HoraeDB+Proposal [2] https://github

Re: [DISCUSS] HoraeDB proposal

2023-11-29 Thread Yu Xiao
ew artifacts with the name CeresDB as > prioritize the renaming task. > > Best, > tison. > > tison 于2023年11月29日周三 15:45写道: > > > > > The proposal doesn't address these naming issues; please update it to > > > include how these will be handled. All of the

Re: [DISCUSS] HoraeDB proposal

2023-11-28 Thread tison
asing new artifacts with the name CeresDB as prioritize the renaming task. Best, tison. tison 于2023年11月29日周三 15:45写道: > > > The proposal doesn't address these naming issues; please update it to > > include how these will be handled. All of the changes don't need to happen

Re: [DISCUSS] HoraeDB proposal

2023-11-28 Thread tison
> The proposal doesn't address these naming issues; please update it to include > how these will be handled. All of the changes don't need to happen before > donation, just meantion how they will be handled, but you do need to respect > 3rd party trademarks. Thanks f

Re: [DISCUSS] HoraeDB proposal

2023-11-28 Thread Justin Mclean
ill being published under the old name? https://github.com/CeresDB/horaedb/pkgs/container/ceresdb-server The proposal doesn't address these naming issues; please update it to include how these will be handled. All of the changes don't need to happen before donation, just meantion how they w

Re: [DISCUSS] HoraeDB proposal

2023-11-28 Thread tison
t, tison. [1] https://ceresdb.github.io/docs/?search=ceresdb tison 于2023年11月29日周三 14:56写道: > > > that the HoraeDB project still wants to use the CeresDB name in some form > > No. > > We found the Ignite proposal a good sample to follow. [1] > > GridGain donates its Gr

Re: [DISCUSS] HoraeDB proposal

2023-11-28 Thread tison
> that the HoraeDB project still wants to use the CeresDB name in some form No. We found the Ignite proposal a good sample to follow. [1] GridGain donates its GridGain In-Memory Platform under the new name Ignite and now it's a TLP. The only reference to GridGain is the happened h

Re: [DISCUSS] HoraeDB proposal

2023-11-28 Thread 任春韶
Hi Justin, > From the discussion and proposal, I had understood that the HoraeDB project still wants to use the CeresDB name in some form. Is this correct or not? NO. The new project will use the name HoraeDB and not refer to CeresDB. Best, Chunshao Ren. Justin Mclean 于2023年11月29日周三 13:2

Re: [DISCUSS] HoraeDB proposal

2023-11-28 Thread Justin Mclean
HI, From the discussion and proposal, I had understood that the HoraeDB project still wants to use the CeresDB name in some form. Is this correct or not? Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr

Re: [DISCUSS] HoraeDB proposal

2023-11-28 Thread tison
l be taken down once the transfer happens. > > So it's not an issue that - > >> Has the company given permission to use their trademark? > No or N/A. The HoraeDB website won't use CeresDB trademarks. > > >> If so, how is it allowed to be used? This should be

Re: [DISCUSS] HoraeDB proposal

2023-11-28 Thread tison
en permission to use their trademark? No or N/A. The HoraeDB website won't use CeresDB trademarks. >> If so, how is it allowed to be used? This should be included in the proposal. N/A >> IMO CeresDB is not used where it should be, giving a false impression I updated the proposal as st

Re: [DISCUSS] HoraeDB proposal

2023-11-28 Thread Justin Mclean
Hi, > I don't see if anywhere “CeresDB” should be used. If so, HoraeDB will change. In the proposal, IMO CeresDB is not used where it should be, giving a false impression. e.g. "HoraeDB has been open-sourced on GitHub for over a year.” that is not correct as it was CeresDB as th

Re: [DISCUSS] HoraeDB proposal

2023-11-28 Thread tison
Updated. You may check and point out any improper mentions. I use a rule that always refers to the software as HoraeDB in the proposal (since the rename is happening), unless when referring to its initial development and open-sourced. Best, tison. tison 于2023年11月28日周二 23:05写道: > > >

Re: [DISCUSS] HoraeDB proposal

2023-11-28 Thread tison
> “HoraeDB” is used, whereas “CeresDB” should be used in several cases. IIUC you mean that when the project is still named as CeresDB, we should name it as CeresDB. I'll check and update the proposal content when the project referred is with the name "CeresDB" at that moment. B

Re: [DISCUSS] HoraeDB proposal

2023-11-28 Thread tison
ack to the list. I hope this is a signal that the project > > > is actively reacting to this concern,**[3] > > > > > > ... although I may regard it as a post-donate action (Answer Cloud is > > > removed after entering the incubator[4]. I did it, followed by so

Re: [DISCUSS] HoraeDB proposal

2023-11-28 Thread 谭睿翔
> > > ... although I may regard it as a post-donate action (Answer Cloud is > > removed after entering the incubator[4]. I did it, followed by some > > others from Answer's committers). > > > > > some entities have taken unfair advantage of this > > > >

Re: [DISCUSS] HoraeDB proposal

2023-11-28 Thread tison
er's committers). > > > some entities have taken unfair advantage of this > > It's also unfair to judge a new incubator proposal to assume, in > advance, that they will do something evil. > > Best, > tison. > > [1] https://www.apache.org/foundation/marks/

Re: [DISCUSS] HoraeDB proposal

2023-11-28 Thread tison
rom Answer's committers). > some entities have taken unfair advantage of this It's also unfair to judge a new incubator proposal to assume, in advance, that they will do something evil. Best, tison. [1] https://www.apache.org/foundation/marks/ [2] https://www.apache.org/foundation/m

Re: [DISCUSS] HoraeDB proposal

2023-11-28 Thread Justin Mclean
Hi, > Using a new name to avoid any possible confusion or conflict is reasonable > I think. That was not given as the reason. Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-

Re: [DISCUSS] HoraeDB proposal

2023-11-28 Thread ShaoFeng Shi
t; Justin Mclean 于2023年11月28日 周二07:15写道: > > > HI, > > > > > This is included in the proposal: Since Ant Group wants to retain the > > brand > > > of CeresDB, we renamed the OSS project as HoraeDB before this proposal. > > > > Why do they want to re

Re: [DISCUSS] HoraeDB proposal

2023-11-28 Thread Justin Mclean
both sides need to be honored). After reading the proposal, I’m not 100% sure the branding guidelines are understood. “HoraeDB” is used, whereas “CeresDB” should be used in several cases. It looks like the rename was only done a couple of weeks ago. Kind Regards, Justin

Re: [DISCUSS] HoraeDB proposal

2023-11-28 Thread Roman Shaposhnik
to know about and > should be mentioned in the proposal. Having a brand closely associated with a > project and owned by a single corporate entity is a risk to the project. Why > a company would be unwilling to give up that brand or trademark just because > it may be convenient in the

Re: [DISCUSS] HoraeDB proposal

2023-11-28 Thread Justin Mclean
Hi, We need to know the reasons for the name change and why the company is willing to donate the code but not the name. The possibility of having them forking the community later is a risk the Incubator needs to know about and should be mentioned in the proposal. Having a brand closely

Re: [DISCUSS] HoraeDB proposal

2023-11-28 Thread tison
CeresDB". I wrote it in the > > background to explain why https://github.com/CeresDB/horaedb has its > > name, but it can be unrelated to the donation (forget "CeresDB" and > > nothing changes). > > > > Best, > > tison. > > > > tison

Re: [DISCUSS] HoraeDB proposal

2023-11-28 Thread tison
Best, > tison. > > tison 于2023年11月28日周二 09:12写道: > > > > Perhaps think of an analogy with Docker vs. Moby? > > > > Justin Mclean 于2023年11月28日 周二07:15写道: > >> > >> HI, > >> > >> > This is included in the proposal: Since Ant Group

Re: [DISCUSS] HoraeDB proposal

2023-11-28 Thread tison
eresDB" and nothing changes). Best, tison. tison 于2023年11月28日周二 09:12写道: > > Perhaps think of an analogy with Docker vs. Moby? > > Justin Mclean 于2023年11月28日 周二07:15写道: >> >> HI, >> >> > This is included in the proposal: Since Ant Group wants to reta

<    1   2   3   4   5   6   7   8   9   10   >