You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by tison <wa...@gmail.com> on 2023/11/24 15:56:28 UTC

[DISCUSS] HoraeDB proposal

Hi IPMC members,

I would like to propose a new project to the ASF incubator - HoraeDB.

HoraeDB[1] is a high-performance, distributed, cloud-native time-series
database that explicitly handles high-cardinality time-series data and
provides native distributed capabilities.

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/HoraeDB+Proposal

I would be the Champion of the project.

I will mentor and help the project through the incubator with Shaofeng Shi [
shaofengshi@apache.org] and Gang Li [lgcareer@apache.org].

We are open to hearing the feedback from the incubator.

Best,
tison.

[1] https://github.com/CeresDB/horaedb

Re: [DISCUSS] HoraeDB proposal

Posted by li gang <lg...@apache.org>.
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 <wa...@gmail.com> 于2023年11月24日周五 23:58写道:

> Hi IPMC members,
>
> I would like to propose a new project to the ASF incubator - HoraeDB.
>
> HoraeDB[1] is a high-performance, distributed, cloud-native time-series
> database that explicitly handles high-cardinality time-series data and
> provides native distributed capabilities.
>
> 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/HoraeDB+Proposal
>
> I would be the Champion of the project.
>
> I will mentor and help the project through the incubator with Shaofeng Shi
> [
> shaofengshi@apache.org] and Gang Li [lgcareer@apache.org].
>
> We are open to hearing the feedback from the incubator.
>
> Best,
> tison.
>
> [1] https://github.com/CeresDB/horaedb
>


-- 


------------------------------
Best Regards
Gang Li 李岗

lgcareer@apache.org

Re: [DISCUSS] HoraeDB proposal

Posted by tison <wa...@gmail.com>.
> It is provable - take a look at the trademarks list.

My quote issue. I mean that whether this project will go into the referred
concern is
neither provable nor unfalsifiable. So we focus on resolving the concrete
explicit issue, and evaluate/mentor this "PPMC" follows trademark policy
during incubation.

tison <wa...@gmail.com>于2023年11月29日 周三08:11写道:

> >> This is an issue as a company still owns the brand and trademark
>
> The doc site will be taken down once the transfer happens.
> Like Ignite's docs won't be http://www.gridgain.org/documentation/
> after its transfer[1].
>
> I intend to explain why it's _currently_ under ceresdb.github.io, but
> it causes further confusion.
> I'm sorry for this.
>
> >>  In other cases e.g. Wth Flex, permission was given by Adobbe to use
> the trademark.
> > The doc site will 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 included in the
> proposal.
> N/A
>
> >> IMO CeresDB is not used where it should be, giving a false impression
> I updated the proposal as stated above. The changeset can be found at[2].
>
> >>I think the proposal needs some improvements as mentioned above.
> Thanks for pointing out concrete concerns and issues - they are replied.
>
> Best,
> tison.
>
> [1] https://cwiki.apache.org/confluence/display/INCUBATOR/IgniteProposal
> [2]
> https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=278466865&selectedPageVersions=10&selectedPageVersions=9
>
> Best,
> tison.
>
>
> Justin Mclean <ju...@classsoftware.com> 于2023年11月29日周三 07:21写道:
> >
> > 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 the name change only
> happened a couple of weeks ago.
> >
> > > The org name is where it leaves now and shall not to change. This is
> > > the same as datafuselabs/opendal doesn't change its org name before
> > > proposing for incubation.
> >
> > There is precedent for keeping the org if it already has widespread use
> and would harm the community with its change. However, it is strongly
> recommended that the name be changed to the new one. The proposal should
> state which direction the project will go in.
> >
> > > The same for its doc site ceresdb.github.io/docs
> >
> > This is an issue as a company still owns the brand and trademark. In
> other cases e.g. Wth Flex, permission was given by Adobbe to use the
> trademark. Has the company given permission to use their trademark? If so,
> how is it allowed to be used? This should be included in the proposal.
> >
> > > Also, I don't think the time itself is an issue but the trust and
> > > certainty, because Pekko renames all its references to Akka after
> > > entering the incubator.
> >
> > Pekko was forced to rename due to a hostile license change and they
> didn't own the name. The proposal stated that they would do this.
> >
> > > So, Justin, your comment is not a reason also, but a suspect for
> > > uncertainty if "some entities have taken unfair advantage of this".
> > > This is neither provable nor unfalsifiable.
> >
> > It is provable - take a look at the trademarks list. I did not want to
> highlight any particular project and sidetrack the discussion.
> >
> > I think the proposal needs some improvements as mentioned above.
> >
> > Kind Regards,
> > Justin
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
>

Re: [DISCUSS] HoraeDB proposal

Posted by tison <wa...@gmail.com>.
> The only reference to GridGain is the happened history[2]:

Well, also include some GridGain services/binaries as stated
explicitly 3rd-party provisions, while it's also dual branding.

For HoraeDB[1], there would not be such references even (the
binary/envvar name will be renamed).

Best,
tison.

[1] https://ceresdb.github.io/docs/?search=ceresdb

tison <wa...@gmail.com> 于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 GridGain In-Memory Platform under the new name Ignite and now it's a TLP.
>
> The only reference to GridGain is the happened history[2]:
>
> GridGain donates the core of its in-memory computing platform to the Apache Software Foundation under the name of "Apache Ignite"
>
> Note that before entering the incubator, the docs of ignite is hosted at
> http://www.gridgain.org/documentation. But now they're dual branding properly.
>
> [1]
> https://cwiki.apache.org/confluence/display/INCUBATOR/IgniteProposal
> [2]
> https://ignite.apache.org/our-community.html
>
> Justin Mclean <ju...@classsoftware.com>于2023年11月29日 周三13:24写道:
>>
>> 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-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [DISCUSS] HoraeDB proposal

Posted by tison <wa...@gmail.com>.
> 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 history[2]:

GridGain donates the core of its in-memory computing platform to the Apache
Software Foundation under the name of "Apache Ignite"

Note that before entering the incubator, the docs of ignite is hosted at
http://www.gridgain.org/documentation. But now they're dual branding
properly.

[1]
https://cwiki.apache.org/confluence/display/INCUBATOR/IgniteProposal
[2]
https://ignite.apache.org/our-community.html

Justin Mclean <ju...@classsoftware.com>于2023年11月29日 周三13:24写道:

> 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-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

Re: [DISCUSS] HoraeDB proposal

Posted by tison <wa...@gmail.com>.
>> 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.

I updated the "Initial Source" section to include the plan[1]. Briefly,

> Overall, all the occurrences except those associated with the org name, mainly GitHub address links and GitHub Pages links, will be renamed. Those associated with the org name will be modified once the transfer is finished.

... and the subtasks/progresses are tracked by [2].

>> Then why does the code in the code still refer to CeresDB in 100+ places?

I checked for github.com/CeresDB/horaedb,
93 matches for "github.com/CeresDB"
6 matches for "ceresdb.github.io"
3 matches for "docs.ceresdb.io"
1 match for "https://cla-assistant.io/CeresDB/ceresdb"

These will be changed 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.com/CeresDB/horaedb/issues/1319

Yu Xiao <xi...@apache.org> 于2023年11月29日周三 18:14写道:
>
> Hi,
>
> I checked the list of contributors[1],  not find  initial Committers
> for  Yingwen Yang(GitHub ID = evenyag) .
>
> [1] https://github.com/CeresDB/horaedb/graphs/contributors
>
> Best wishes!
>
> tison <wa...@gmail.com> 于2023年11月29日周三 15:55写道:
> >
> > > You also have things like this, which was published in the last day. If the name has changed, why is this still being published under the old name?
> > > https://github.com/CeresDB/horaedb/pkgs/container/ceresdb-server
> >
> > If your cornern for asking permission for use CeresDB trademark is due
> > to the existing 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.
> >
> > 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 <wa...@gmail.com> 于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 before donation, just meantion how they will be handled,  but you do need to respect 3rd party trademarks.
> > >
> > > Thanks for your reply. This is tracked in [1] and we will elaborate
> > > the actions and integrate it in the proposal. Renaming code/text is
> > > happening so the references will be reduced down.
> > >
> > > > My previous question regards whether the project has been given permission to use the CeresDB trademark has still not been answered.
> > > >> 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 included in the proposal.
> > > >>N/A
> > >
> > > So the answer for "whether" is no for no need.
> > >
> > > Best,
> > > tison.
> > >
> > > [1] https://github.com/CeresDB/horaedb/issues/1319
> > >
> > > Justin Mclean <ju...@classsoftware.com> 于2023年11月29日周三 15:34写道:
> > > >
> > > > HI,
> > > >
> > > > > project still wants to use the CeresDB name in some form. Is this correct
> > > > > or not?
> > > > > NO.
> > > >
> > > > Then why does the code in the code still refer to CeresDB in 100+ places?
> > > >
> > > > for instance, the source path is:
> > > > /horaedb/src/ceresdb
> > > >
> > > > looking at horaedbsrc/ceresdb/bin/ceresdb-server.rs it contains things like:
> > > > const NODE_ADDR: &str = "CERESDB_SERVER_ADDR”;
> > > > use ceresdb:
> > > > println!("CeresDB server tries starting with config:{config:?}”);
> > > >
> > > > in src/ceresdb/Cargo.toml
> > > > [package]
> > > > name = "ceresdb"
> > > >
> > > > Dockerfile
> > > > COPY . /ceresdb
> > > > WORKDIR /ceresdb## CeresDBCOPY --from=build /ceresdb/target/release/ceresdb-server /usr/bin/ceresdb-server
> > > > RUN chmod +x /usr/bin/ceresdb-serverCOPY ./docs/minimal.toml /etc/ceresdb/ceresdb.toml
> > > >
> > > > And as mentioned, 100+ other instances.
> > > >
> > > > You also have things like this, which was published in the last day. If the name has changed, why is this still 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 will be handled,  but you do need to respect 3rd party trademarks.
> > > >
> > > > My previous question regards whether the project has been given permission to use the CeresDB trademark has still not been answered.
> > > >
> > > > Kind Regards,
> > > > Justin
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > > > For additional commands, e-mail: general-help@incubator.apache.org
> > > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [DISCUSS] HoraeDB proposal

Posted by Jiacai Liu <he...@liujiacai.net>.
Hi,

Yingwen is one of the core early developers of the project, if you 
execute `git grep yingwen`, you could see lots of comments written 
by him.
However when we open source horaedb on GitHub, we do a git stash 
to make the git history clean, so you couldn't see his commits 
anymore.

Now he isn't working in AntGroup anymore, but since he contributed 
significantly to the early stages of development, so we list him 
under initial committers.

On Wed, Nov 29, 2023 at 06:13:42 PM +0800, Yu Xiao wrote:

> Hi,
>
> I checked the list of contributors[1],  not find  initial 
> Committers
> for  Yingwen Yang(GitHub ID = evenyag) .
>
> [1] https://github.com/CeresDB/horaedb/graphs/contributors
>
> Best wishes!
>
> tison <wa...@gmail.com> 于2023年11月29日周三 15:55写道:
>>
>> > You also have things like this, which was published in the 
>> > last day. If the name has changed,
>> > why is this still being published under the old name?
>> > https://github.com/CeresDB/horaedb/pkgs/container/ceresdb-server
>>
>> If your cornern for asking permission for use CeresDB trademark 
>> is due
>> to the existing 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.
>>
>> 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 <wa...@gmail.com> 于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 before 
>> > > donation, just meantion how they
>> > > will be handled, but you do need to respect 3rd party 
>> > > trademarks.
>> >
>> > Thanks for your reply. This is tracked in [1] and we will 
>> > elaborate
>> > the actions and integrate it in the proposal. Renaming 
>> > code/text is
>> > happening so the references will be reduced down.
>> >
>> > > My previous question regards whether the project has been 
>> > > given permission to use the CeresDB
>> > > trademark has still not been answered.
>> > >> 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 
>> > >>> included in the proposal.
>> > >>N/A
>> >
>> > So the answer for "whether" is no for no need.
>> >
>> > Best,
>> > tison.
>> >
>> > [1] https://github.com/CeresDB/horaedb/issues/1319
>> >
>> > Justin Mclean <ju...@classsoftware.com> 于2023年11月29日周三 
>> > 15:34写道:
>> > >
>> > > HI,
>> > >
>> > > > project still wants to use the CeresDB name in some 
>> > > > form. Is this correct
>> > > > or not?
>> > > > NO.
>> > >
>> > > Then why does the code in the code still refer to CeresDB 
>> > > in 100+ places?
>> > >
>> > > for instance, the source path is:
>> > > /horaedb/src/ceresdb
>> > >
>> > > looking at horaedbsrc/ceresdb/bin/ceresdb-server.rs it 
>> > > contains things like:
>> > > const NODE_ADDR: &str = "CERESDB_SERVER_ADDR”;
>> > > use ceresdb:
>> > > println!("CeresDB server tries starting with 
>> > > config:{config:?}”);
>> > >
>> > > in src/ceresdb/Cargo.toml
>> > > [package]
>> > > name = "ceresdb"
>> > >
>> > > Dockerfile
>> > > COPY . /ceresdb
>> > > WORKDIR /ceresdb## CeresDBCOPY --from=build 
>> > > /ceresdb/target/release/ceresdb-server
>> > > /usr/bin/ceresdb-server
>> > > RUN chmod +x /usr/bin/ceresdb-serverCOPY 
>> > > ./docs/minimal.toml /etc/ceresdb/ceresdb.toml
>> > >
>> > > And as mentioned, 100+ other instances.
>> > >
>> > > You also have things like this, which was published in the 
>> > > last day. If the name has changed,
>> > > why is this still 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
>> > > will be handled, but you do need to respect 3rd party 
>> > > trademarks.
>> > >
>> > > My previous question regards whether the project has been 
>> > > given permission to use the CeresDB
>> > > trademark has still not been answered.
>> > >
>> > > Kind Regards,
>> > > Justin
>> > > ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: 
>> > > general-unsubscribe@incubator.apache.org
>> > > For additional commands, e-mail: 
>> > > general-help@incubator.apache.org
>> > >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: 
>> general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: 
>> general-help@incubator.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: 
> general-help@incubator.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [DISCUSS] HoraeDB proposal

Posted by tison <wa...@gmail.com>.
Hi IPMC,

Is there any concern left before initializing the vote? I hope we have
addressed most before the start.

I can see the HoraeDB project is open to learning more about the
ASF culture in the incubating process. And they do react to the
comments above and take action.

It is not perfect and fully compatible with ASF yet - this is the point
of the whole incubating.

Best,
tison.

Jiacai Liu <he...@liujiacai.net> 于2023年11月30日周四 16:24写道:
>
>
> Hi,
>
> Yingwen is one of the core early developers of the project, if you
> execute `git grep yingwen`, you could see lots of comments written
> by him.
> However when we open source horaedb on GitHub, we do a git stash
> to make the git history clean, so you couldn't see his commit
> anymore.
>
> Now he isn't working in AntGroup anymore, but since he contributed
> significantly to the early stages of development, so we list him
> under initial committers.
>
> On Wed, Nov 29, 2023 at 06:13:42 PM +0800, Yu Xiao wrote:
>
> > Hi,
> >
> > I checked the list of contributors[1],  not find  initial
> > Committers
> > for  Yingwen Yang(GitHub ID = evenyag) .
> >
> > [1] https://github.com/CeresDB/horaedb/graphs/contributors
> >
> > Best wishes!
> >
> > tison <wa...@gmail.com> 于2023年11月29日周三 15:55写道:
> >>
> >> > You also have things like this, which was published in the
> >> > last day. If the name has changed,
> >> > why is this still being published under the old name?
> >> > https://github.com/CeresDB/horaedb/pkgs/container/ceresdb-server
> >>
> >> If your cornern for asking permission for use CeresDB trademark
> >> is due
> >> to the existing 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.
> >>
> >> 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 <wa...@gmail.com> 于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 before
> >> > > donation, just meantion how they
> >> > > will be handled, but you do need to respect 3rd party
> >> > > trademarks.
> >> >
> >> > Thanks for your reply. This is tracked in [1] and we will
> >> > elaborate
> >> > the actions and integrate it in the proposal. Renaming
> >> > code/text is
> >> > happening so the references will be reduced down.
> >> >
> >> > > My previous question regards whether the project has been
> >> > > given permission to use the CeresDB
> >> > > trademark has still not been answered.
> >> > >> 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
> >> > >>> included in the proposal.
> >> > >>N/A
> >> >
> >> > So the answer for "whether" is no for no need.
> >> >
> >> > Best,
> >> > tison.
> >> >
> >> > [1] https://github.com/CeresDB/horaedb/issues/1319
> >> >
> >> > Justin Mclean <ju...@classsoftware.com> 于2023年11月29日周三
> >> > 15:34写道:
> >> > >
> >> > > HI,
> >> > >
> >> > > > project still wants to use the CeresDB name in some
> >> > > > form. Is this correct
> >> > > > or not?
> >> > > > NO.
> >> > >
> >> > > Then why does the code in the code still refer to CeresDB
> >> > > in 100+ places?
> >> > >
> >> > > for instance, the source path is:
> >> > > /horaedb/src/ceresdb
> >> > >
> >> > > looking at horaedbsrc/ceresdb/bin/ceresdb-server.rs it
> >> > > contains things like:
> >> > > const NODE_ADDR: &str = "CERESDB_SERVER_ADDR”;
> >> > > use ceresdb:
> >> > > println!("CeresDB server tries starting with
> >> > > config:{config:?}”);
> >> > >
> >> > > in src/ceresdb/Cargo.toml
> >> > > [package]
> >> > > name = "ceresdb"
> >> > >
> >> > > Dockerfile
> >> > > COPY . /ceresdb
> >> > > WORKDIR /ceresdb## CeresDBCOPY --from=build
> >> > > /ceresdb/target/release/ceresdb-server
> >> > > /usr/bin/ceresdb-server
> >> > > RUN chmod +x /usr/bin/ceresdb-serverCOPY
> >> > > ./docs/minimal.toml /etc/ceresdb/ceresdb.toml
> >> > >
> >> > > And as mentioned, 100+ other instances.
> >> > >
> >> > > You also have things like this, which was published in the
> >> > > last day. If the name has changed,
> >> > > why is this still 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
> >> > > will be handled, but you do need to respect 3rd party
> >> > > trademarks.
> >> > >
> >> > > My previous question regards whether the project has been
> >> > > given permission to use the CeresDB
> >> > > trademark has still not been answered.
> >> > >
> >> > > Kind Regards,
> >> > > Justin
> >> > > ---------------------------------------------------------------------
> >> > > To unsubscribe, e-mail:
> >> > > general-unsubscribe@incubator.apache.org
> >> > > For additional commands, e-mail:
> >> > > general-help@incubator.apache.org
> >> > >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail:
> >> general-unsubscribe@incubator.apache.org
> >> For additional commands, e-mail:
> >> general-help@incubator.apache.org
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail:
> > general-help@incubator.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [DISCUSS] HoraeDB proposal

Posted by Jiacai Liu <he...@liujiacai.net>.
Hi,

Yingwen is one of the core early developers of the project, if you 
execute `git grep yingwen`, you could see lots of comments written 
by him.
However when we open source horaedb on GitHub, we do a git stash 
to make the git history clean, so you couldn't see his commit 
anymore.

Now he isn't working in AntGroup anymore, but since he contributed 
significantly to the early stages of development, so we list him 
under initial committers.

On Wed, Nov 29, 2023 at 06:13:42 PM +0800, Yu Xiao wrote:

> Hi,
>
> I checked the list of contributors[1],  not find  initial 
> Committers
> for  Yingwen Yang(GitHub ID = evenyag) .
>
> [1] https://github.com/CeresDB/horaedb/graphs/contributors
>
> Best wishes!
>
> tison <wa...@gmail.com> 于2023年11月29日周三 15:55写道:
>>
>> > You also have things like this, which was published in the 
>> > last day. If the name has changed,
>> > why is this still being published under the old name?
>> > https://github.com/CeresDB/horaedb/pkgs/container/ceresdb-server
>>
>> If your cornern for asking permission for use CeresDB trademark 
>> is due
>> to the existing 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.
>>
>> 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 <wa...@gmail.com> 于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 before 
>> > > donation, just meantion how they
>> > > will be handled, but you do need to respect 3rd party 
>> > > trademarks.
>> >
>> > Thanks for your reply. This is tracked in [1] and we will 
>> > elaborate
>> > the actions and integrate it in the proposal. Renaming 
>> > code/text is
>> > happening so the references will be reduced down.
>> >
>> > > My previous question regards whether the project has been 
>> > > given permission to use the CeresDB
>> > > trademark has still not been answered.
>> > >> 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 
>> > >>> included in the proposal.
>> > >>N/A
>> >
>> > So the answer for "whether" is no for no need.
>> >
>> > Best,
>> > tison.
>> >
>> > [1] https://github.com/CeresDB/horaedb/issues/1319
>> >
>> > Justin Mclean <ju...@classsoftware.com> 于2023年11月29日周三 
>> > 15:34写道:
>> > >
>> > > HI,
>> > >
>> > > > project still wants to use the CeresDB name in some 
>> > > > form. Is this correct
>> > > > or not?
>> > > > NO.
>> > >
>> > > Then why does the code in the code still refer to CeresDB 
>> > > in 100+ places?
>> > >
>> > > for instance, the source path is:
>> > > /horaedb/src/ceresdb
>> > >
>> > > looking at horaedbsrc/ceresdb/bin/ceresdb-server.rs it 
>> > > contains things like:
>> > > const NODE_ADDR: &str = "CERESDB_SERVER_ADDR”;
>> > > use ceresdb:
>> > > println!("CeresDB server tries starting with 
>> > > config:{config:?}”);
>> > >
>> > > in src/ceresdb/Cargo.toml
>> > > [package]
>> > > name = "ceresdb"
>> > >
>> > > Dockerfile
>> > > COPY . /ceresdb
>> > > WORKDIR /ceresdb## CeresDBCOPY --from=build 
>> > > /ceresdb/target/release/ceresdb-server
>> > > /usr/bin/ceresdb-server
>> > > RUN chmod +x /usr/bin/ceresdb-serverCOPY 
>> > > ./docs/minimal.toml /etc/ceresdb/ceresdb.toml
>> > >
>> > > And as mentioned, 100+ other instances.
>> > >
>> > > You also have things like this, which was published in the 
>> > > last day. If the name has changed,
>> > > why is this still 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
>> > > will be handled, but you do need to respect 3rd party 
>> > > trademarks.
>> > >
>> > > My previous question regards whether the project has been 
>> > > given permission to use the CeresDB
>> > > trademark has still not been answered.
>> > >
>> > > Kind Regards,
>> > > Justin
>> > > ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: 
>> > > general-unsubscribe@incubator.apache.org
>> > > For additional commands, e-mail: 
>> > > general-help@incubator.apache.org
>> > >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: 
>> general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: 
>> general-help@incubator.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: 
> general-help@incubator.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [DISCUSS] HoraeDB proposal

Posted by Yu Xiao <xi...@apache.org>.
Hi,

I checked the list of contributors[1],  not find  initial Committers
for  Yingwen Yang(GitHub ID = evenyag) .

[1] https://github.com/CeresDB/horaedb/graphs/contributors

Best wishes!

tison <wa...@gmail.com> 于2023年11月29日周三 15:55写道:
>
> > You also have things like this, which was published in the last day. If the name has changed, why is this still being published under the old name?
> > https://github.com/CeresDB/horaedb/pkgs/container/ceresdb-server
>
> If your cornern for asking permission for use CeresDB trademark is due
> to the existing 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.
>
> 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 <wa...@gmail.com> 于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 before donation, just meantion how they will be handled,  but you do need to respect 3rd party trademarks.
> >
> > Thanks for your reply. This is tracked in [1] and we will elaborate
> > the actions and integrate it in the proposal. Renaming code/text is
> > happening so the references will be reduced down.
> >
> > > My previous question regards whether the project has been given permission to use the CeresDB trademark has still not been answered.
> > >> 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 included in the proposal.
> > >>N/A
> >
> > So the answer for "whether" is no for no need.
> >
> > Best,
> > tison.
> >
> > [1] https://github.com/CeresDB/horaedb/issues/1319
> >
> > Justin Mclean <ju...@classsoftware.com> 于2023年11月29日周三 15:34写道:
> > >
> > > HI,
> > >
> > > > project still wants to use the CeresDB name in some form. Is this correct
> > > > or not?
> > > > NO.
> > >
> > > Then why does the code in the code still refer to CeresDB in 100+ places?
> > >
> > > for instance, the source path is:
> > > /horaedb/src/ceresdb
> > >
> > > looking at horaedbsrc/ceresdb/bin/ceresdb-server.rs it contains things like:
> > > const NODE_ADDR: &str = "CERESDB_SERVER_ADDR”;
> > > use ceresdb:
> > > println!("CeresDB server tries starting with config:{config:?}”);
> > >
> > > in src/ceresdb/Cargo.toml
> > > [package]
> > > name = "ceresdb"
> > >
> > > Dockerfile
> > > COPY . /ceresdb
> > > WORKDIR /ceresdb## CeresDBCOPY --from=build /ceresdb/target/release/ceresdb-server /usr/bin/ceresdb-server
> > > RUN chmod +x /usr/bin/ceresdb-serverCOPY ./docs/minimal.toml /etc/ceresdb/ceresdb.toml
> > >
> > > And as mentioned, 100+ other instances.
> > >
> > > You also have things like this, which was published in the last day. If the name has changed, why is this still 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 will be handled,  but you do need to respect 3rd party trademarks.
> > >
> > > My previous question regards whether the project has been given permission to use the CeresDB trademark has still not been answered.
> > >
> > > Kind Regards,
> > > Justin
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > > For additional commands, e-mail: general-help@incubator.apache.org
> > >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [DISCUSS] HoraeDB proposal

Posted by tison <wa...@gmail.com>.
> You also have things like this, which was published in the last day. If the name has changed, why is this still being published under the old name?
> https://github.com/CeresDB/horaedb/pkgs/container/ceresdb-server

If your cornern for asking permission for use CeresDB trademark is due
to the existing 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.

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 <wa...@gmail.com> 于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 before donation, just meantion how they will be handled,  but you do need to respect 3rd party trademarks.
>
> Thanks for your reply. This is tracked in [1] and we will elaborate
> the actions and integrate it in the proposal. Renaming code/text is
> happening so the references will be reduced down.
>
> > My previous question regards whether the project has been given permission to use the CeresDB trademark has still not been answered.
> >> 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 included in the proposal.
> >>N/A
>
> So the answer for "whether" is no for no need.
>
> Best,
> tison.
>
> [1] https://github.com/CeresDB/horaedb/issues/1319
>
> Justin Mclean <ju...@classsoftware.com> 于2023年11月29日周三 15:34写道:
> >
> > HI,
> >
> > > project still wants to use the CeresDB name in some form. Is this correct
> > > or not?
> > > NO.
> >
> > Then why does the code in the code still refer to CeresDB in 100+ places?
> >
> > for instance, the source path is:
> > /horaedb/src/ceresdb
> >
> > looking at horaedbsrc/ceresdb/bin/ceresdb-server.rs it contains things like:
> > const NODE_ADDR: &str = "CERESDB_SERVER_ADDR”;
> > use ceresdb:
> > println!("CeresDB server tries starting with config:{config:?}”);
> >
> > in src/ceresdb/Cargo.toml
> > [package]
> > name = "ceresdb"
> >
> > Dockerfile
> > COPY . /ceresdb
> > WORKDIR /ceresdb## CeresDBCOPY --from=build /ceresdb/target/release/ceresdb-server /usr/bin/ceresdb-server
> > RUN chmod +x /usr/bin/ceresdb-serverCOPY ./docs/minimal.toml /etc/ceresdb/ceresdb.toml
> >
> > And as mentioned, 100+ other instances.
> >
> > You also have things like this, which was published in the last day. If the name has changed, why is this still 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 will be handled,  but you do need to respect 3rd party trademarks.
> >
> > My previous question regards whether the project has been given permission to use the CeresDB trademark has still not been answered.
> >
> > Kind Regards,
> > Justin
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [DISCUSS] HoraeDB proposal

Posted by tison <wa...@gmail.com>.
> 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 for your reply. This is tracked in [1] and we will elaborate
the actions and integrate it in the proposal. Renaming code/text is
happening so the references will be reduced down.

> My previous question regards whether the project has been given permission to use the CeresDB trademark has still not been answered.
>> 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 included in the proposal.
>>N/A

So the answer for "whether" is no for no need.

Best,
tison.

[1] https://github.com/CeresDB/horaedb/issues/1319

Justin Mclean <ju...@classsoftware.com> 于2023年11月29日周三 15:34写道:
>
> HI,
>
> > project still wants to use the CeresDB name in some form. Is this correct
> > or not?
> > NO.
>
> Then why does the code in the code still refer to CeresDB in 100+ places?
>
> for instance, the source path is:
> /horaedb/src/ceresdb
>
> looking at horaedbsrc/ceresdb/bin/ceresdb-server.rs it contains things like:
> const NODE_ADDR: &str = "CERESDB_SERVER_ADDR”;
> use ceresdb:
> println!("CeresDB server tries starting with config:{config:?}”);
>
> in src/ceresdb/Cargo.toml
> [package]
> name = "ceresdb"
>
> Dockerfile
> COPY . /ceresdb
> WORKDIR /ceresdb## CeresDBCOPY --from=build /ceresdb/target/release/ceresdb-server /usr/bin/ceresdb-server
> RUN chmod +x /usr/bin/ceresdb-serverCOPY ./docs/minimal.toml /etc/ceresdb/ceresdb.toml
>
> And as mentioned, 100+ other instances.
>
> You also have things like this, which was published in the last day. If the name has changed, why is this still 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 will be handled,  but you do need to respect 3rd party trademarks.
>
> My previous question regards whether the project has been given permission to use the CeresDB trademark has still not been answered.
>
> Kind Regards,
> Justin
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [DISCUSS] HoraeDB proposal

Posted by Justin Mclean <ju...@classsoftware.com>.
HI,

> project still wants to use the CeresDB name in some form. Is this correct
> or not?
> NO.

Then why does the code in the code still refer to CeresDB in 100+ places?

for instance, the source path is:
/horaedb/src/ceresdb

looking at horaedbsrc/ceresdb/bin/ceresdb-server.rs it contains things like:
const NODE_ADDR: &str = "CERESDB_SERVER_ADDR”;
use ceresdb:
println!("CeresDB server tries starting with config:{config:?}”);

in src/ceresdb/Cargo.toml
[package]
name = "ceresdb"

Dockerfile
COPY . /ceresdb
WORKDIR /ceresdb## CeresDBCOPY --from=build /ceresdb/target/release/ceresdb-server /usr/bin/ceresdb-server
RUN chmod +x /usr/bin/ceresdb-serverCOPY ./docs/minimal.toml /etc/ceresdb/ceresdb.toml

And as mentioned, 100+ other instances.

You also have things like this, which was published in the last day. If the name has changed, why is this still 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 will be handled,  but you do need to respect 3rd party trademarks. 

My previous question regards whether the project has been given permission to use the CeresDB trademark has still not been answered.

Kind Regards,
Justin
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [DISCUSS] HoraeDB proposal

Posted by 任春韶 <ch...@gmail.com>.
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 <ju...@classsoftware.com> 于2023年11月29日周三 13:24写道:

> 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-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

Re: [DISCUSS] HoraeDB proposal

Posted by Justin Mclean <ju...@classsoftware.com>.
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-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [DISCUSS] HoraeDB proposal

Posted by tison <wa...@gmail.com>.
>> This is an issue as a company still owns the brand and trademark

The doc site will be taken down once the transfer happens.
Like Ignite's docs won't be http://www.gridgain.org/documentation/
after its transfer[1].

I intend to explain why it's _currently_ under ceresdb.github.io, but
it causes further confusion.
I'm sorry for this.

>>  In other cases e.g. Wth Flex, permission was given by Adobbe to use the trademark.
> The doc site will 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 included in the proposal.
N/A

>> IMO CeresDB is not used where it should be, giving a false impression
I updated the proposal as stated above. The changeset can be found at[2].

>>I think the proposal needs some improvements as mentioned above.
Thanks for pointing out concrete concerns and issues - they are replied.

Best,
tison.

[1] https://cwiki.apache.org/confluence/display/INCUBATOR/IgniteProposal
[2] https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=278466865&selectedPageVersions=10&selectedPageVersions=9

Best,
tison.


Justin Mclean <ju...@classsoftware.com> 于2023年11月29日周三 07:21写道:
>
> 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 the name change only happened a couple of weeks ago.
>
> > The org name is where it leaves now and shall not to change. This is
> > the same as datafuselabs/opendal doesn't change its org name before
> > proposing for incubation.
>
> There is precedent for keeping the org if it already has widespread use and would harm the community with its change. However, it is strongly recommended that the name be changed to the new one. The proposal should state which direction the project will go in.
>
> > The same for its doc site ceresdb.github.io/docs
>
> This is an issue as a company still owns the brand and trademark. In other cases e.g. Wth Flex, permission was given by Adobbe to use the trademark. Has the company given permission to use their trademark? If so, how is it allowed to be used? This should be included in the proposal.
>
> > Also, I don't think the time itself is an issue but the trust and
> > certainty, because Pekko renames all its references to Akka after
> > entering the incubator.
>
> Pekko was forced to rename due to a hostile license change and they didn't own the name. The proposal stated that they would do this.
>
> > So, Justin, your comment is not a reason also, but a suspect for
> > uncertainty if "some entities have taken unfair advantage of this".
> > This is neither provable nor unfalsifiable.
>
> It is provable - take a look at the trademarks list. I did not want to highlight any particular project and sidetrack the discussion.
>
> I think the proposal needs some improvements as mentioned above.
>
> Kind Regards,
> Justin
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [DISCUSS] HoraeDB proposal

Posted by Justin Mclean <ju...@classsoftware.com>.
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 the name change only happened a couple of weeks ago.

> The org name is where it leaves now and shall not to change. This is
> the same as datafuselabs/opendal doesn't change its org name before
> proposing for incubation.

There is precedent for keeping the org if it already has widespread use and would harm the community with its change. However, it is strongly recommended that the name be changed to the new one. The proposal should state which direction the project will go in.

> The same for its doc site ceresdb.github.io/docs

This is an issue as a company still owns the brand and trademark. In other cases e.g. Wth Flex, permission was given by Adobbe to use the trademark. Has the company given permission to use their trademark? If so, how is it allowed to be used? This should be included in the proposal.

> Also, I don't think the time itself is an issue but the trust and
> certainty, because Pekko renames all its references to Akka after
> entering the incubator.

Pekko was forced to rename due to a hostile license change and they didn't own the name. The proposal stated that they would do this.

> So, Justin, your comment is not a reason also, but a suspect for
> uncertainty if "some entities have taken unfair advantage of this".
> This is neither provable nor unfalsifiable.

It is provable - take a look at the trademarks list. I did not want to highlight any particular project and sidetrack the discussion.

I think the proposal needs some improvements as mentioned above.

Kind Regards,
Justin
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [DISCUSS] HoraeDB proposal

Posted by tison <wa...@gmail.com>.
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 <wa...@gmail.com> 于2023年11月28日周二 23:05写道:
>
> > “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.
>
> Best,
> tison.
>
> tison <wa...@gmail.com> 于2023年11月28日周二 22:12写道:
> >
> > Among the conversations above, there is no policy violation, but
> > uncertainty for the company that donates its software.
> >
> > To overcome uncertainty, IMO, time and stories help. @tanruixiang
> > share one, and I'll talk a bit about others.
> >
> > > “HoraeDB” is used, whereas “CeresDB” should be used in several cases.
> >
> > I don't see if anywhere “CeresDB” should be used. If so, HoraeDB will change.
> > The org name is where it leaves now and shall not to change. This is
> > the same as datafuselabs/opendal doesn't change its org name before
> > proposing for incubation.
> > The same for its doc site ceresdb.github.io/docs, this is associated
> > with GitHub org.
> > Others will be changed and is tracked at
> > https://github.com/CeresDB/horaedb/issues/1319.
> >
> > For why not change the license header, it's my fault that I suppose to
> > rename it into ASF license header after entering the incubator, so
> > that we don't introduce twice large license header changeset. But the
> > rename is decided so we can move forward anyway.
> >
> > > It looks like the rename was only done a couple of weeks ago.
> >
> > Also, I don't think the time itself is an issue but the trust and
> > certainty, because Pekko renames all its references to Akka after
> > entering the incubator.
> >
> > The story is that, if Ant Group doesn't want to donate the software,
> > there is no necessity to change the name. Ant Group approved to donate
> > the software, @chunshao90 and @jiacai2050 started to rename the repo,
> > text occurrence, and dependencies.
> >
> > @jiacai2050 asked me if we should change the name in the license
> > header, and I regarded it can be a post-donate action as stated above.
> >
> > I went through the incubator proposals and found IgniteProposal[1]
> > chose a new name before it was donated by GridGain Systems, Inc. which
> > is internally known as "GridGain In-Memory Computing Platform".
> >
> > I know there are a few companies/individuals just use Ignite and/or
> > contribute and few people know that Ignite has some relationship with
> > GridGain Systems, Inc.
> >
> > > That was not given as the reason.
> >
> > So, Justin, your comment is not a reason also, but a suspect for
> > uncertainty if "some entities have taken unfair advantage of this".
> > This is neither provable nor unfalsifiable.
> >
> > I may understand your suspect, and I choose to trust the initial
> > group. And if you find any concerns that may hurt the "Daul branding",
> > point them out and let the "PPMC" correct it (just like a few people
> > pointed out "Answer Cloud" issue).
> >
> > Best,
> > tison.
> >
> > [1] https://cwiki.apache.org/confluence/display/INCUBATOR/IgniteProposal
> >
> > 谭睿翔 <ta...@apache.org> 于2023年11月28日周二 20:33写道:
> >
> > >
> > > Hi Justin, I am a student from Zhejiang University, one of the initial
> > > committers of HoraeDB. I just want to talk about my feelings. I've been
> > > involved in the HoraeDB community for more than half a year now. In the
> > > process of participating in HoraeDB community, I have been respected and
> > > helped by the community. In the process of participation, I can easily get
> > > the contextual information of Issue or pr, and I didn't encounter the
> > > so-called private pr only within the company. I think the maintainers of
> > > HoraeDB community are working very hard to make the community more
> > > diversified, and my being nominated as the initial committer as a student
> > > is an example of that. I believe that the maintainers of HoraeDB are
> > > passionate about open source and I don't see them doing anything that would
> > > be harmful to the community. This is how I feel about my involvement in
> > > HoraeDB.
> > >
> > > Best Regards,
> > > Ruixiang Tan.
> > >
> > > tison <wa...@gmail.com> 于2023年11月28日周二 19:30写道:
> > >
> > > > To be clear, when I wrote "I worked with", it doesn't mean we're
> > > > colleagues. But I work with other initial committers in the community.
> > > >
> > > > tison <wa...@gmail.com>于2023年11月28日 周二19:15写道:
> > > >
> > > > > Thanks for your reply, Justin. Now I understand your concern more
> > > > > concretely.
> > > > >
> > > > > I'll share three points here:
> > > > >
> > > > > 1. First of all, the trademark policy must be followed for the new
> > > > > PPMC. The PPMC will protect the trademark with the guide of trademark
> > > > > policy[1][2]. It's part of the road during the incubation.
> > > > >
> > > > > 2. I worked with the people for a while, and I trust their motivation
> > > > > for running a diverse community. It's impossible to prove, but we can
> > > > > do a few exercises as your new reply.
> > > > >
> > > > > > whereas “CeresDB” should be used in several cases
> > > > >
> > > > > **This is a concern. I'll check it with the initial group, resolve it,
> > > > > and then go back 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 some
> > > > > others from 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/marks/policies
> > > > > [3] https://github.com/CeresDB/horaedb/issues/1319
> > > > > [4]
> > > > >
> > > > https://github.com/apache/incubator-answer-website/commit/e807a7af5e48b3dfb505854f029753daf480362f
> > > > >
> > > > > Roman Shaposhnik <ro...@shaposhnik.org> 于2023年11月28日周二 18:27写道:
> > > > > >
> > > > > > On Tue, Nov 28, 2023 at 12:12 PM Justin Mclean <
> > > > justin@classsoftware.com>
> > > > > wrote:
> > > > > > >
> > > > > > > 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 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 future is a concern.
> > > > > >
> > > > > > While I agree that having a clear reason stated would be helpful, I
> > > > > > think I have a different take on the risks you are outlining here.
> > > > > >
> > > > > > We have tons of examples here in the ASF of project Foo being used to
> > > > > > power commercial product Bar (Geode/Gemfire, Ignite/GridGain,
> > > > > > Kafka/Confluent, and many, many more). So this kind of dual branding
> > > > > > is nothing new -- there's no community fork involved per se.
> > > > > >
> > > > > > It would be nice if the original name of the open source project (as
> > > > > > it existed on Github) was donated to ASF and the new name for a
> > > > > > commercially developed product was picked. But even if it is the other
> > > > > > way around -- I actually don't see any risks for the foundation in
> > > > > > this approach (as long as it is clearly understood that the branding
> > > > > > guidelines on both sides need to be honored).
> > > > > >
> > > > > > Thanks,
> > > > > > Roman.
> > > > > >
> > > > > > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > > > > > For additional commands, e-mail: general-help@incubator.apache.org
> > > > > >
> > > > >
> > > >

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [DISCUSS] HoraeDB proposal

Posted by tison <wa...@gmail.com>.
> “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.

Best,
tison.

tison <wa...@gmail.com> 于2023年11月28日周二 22:12写道:
>
> Among the conversations above, there is no policy violation, but
> uncertainty for the company that donates its software.
>
> To overcome uncertainty, IMO, time and stories help. @tanruixiang
> share one, and I'll talk a bit about others.
>
> > “HoraeDB” is used, whereas “CeresDB” should be used in several cases.
>
> I don't see if anywhere “CeresDB” should be used. If so, HoraeDB will change.
> The org name is where it leaves now and shall not to change. This is
> the same as datafuselabs/opendal doesn't change its org name before
> proposing for incubation.
> The same for its doc site ceresdb.github.io/docs, this is associated
> with GitHub org.
> Others will be changed and is tracked at
> https://github.com/CeresDB/horaedb/issues/1319.
>
> For why not change the license header, it's my fault that I suppose to
> rename it into ASF license header after entering the incubator, so
> that we don't introduce twice large license header changeset. But the
> rename is decided so we can move forward anyway.
>
> > It looks like the rename was only done a couple of weeks ago.
>
> Also, I don't think the time itself is an issue but the trust and
> certainty, because Pekko renames all its references to Akka after
> entering the incubator.
>
> The story is that, if Ant Group doesn't want to donate the software,
> there is no necessity to change the name. Ant Group approved to donate
> the software, @chunshao90 and @jiacai2050 started to rename the repo,
> text occurrence, and dependencies.
>
> @jiacai2050 asked me if we should change the name in the license
> header, and I regarded it can be a post-donate action as stated above.
>
> I went through the incubator proposals and found IgniteProposal[1]
> chose a new name before it was donated by GridGain Systems, Inc. which
> is internally known as "GridGain In-Memory Computing Platform".
>
> I know there are a few companies/individuals just use Ignite and/or
> contribute and few people know that Ignite has some relationship with
> GridGain Systems, Inc.
>
> > That was not given as the reason.
>
> So, Justin, your comment is not a reason also, but a suspect for
> uncertainty if "some entities have taken unfair advantage of this".
> This is neither provable nor unfalsifiable.
>
> I may understand your suspect, and I choose to trust the initial
> group. And if you find any concerns that may hurt the "Daul branding",
> point them out and let the "PPMC" correct it (just like a few people
> pointed out "Answer Cloud" issue).
>
> Best,
> tison.
>
> [1] https://cwiki.apache.org/confluence/display/INCUBATOR/IgniteProposal
>
> 谭睿翔 <ta...@apache.org> 于2023年11月28日周二 20:33写道:
>
> >
> > Hi Justin, I am a student from Zhejiang University, one of the initial
> > committers of HoraeDB. I just want to talk about my feelings. I've been
> > involved in the HoraeDB community for more than half a year now. In the
> > process of participating in HoraeDB community, I have been respected and
> > helped by the community. In the process of participation, I can easily get
> > the contextual information of Issue or pr, and I didn't encounter the
> > so-called private pr only within the company. I think the maintainers of
> > HoraeDB community are working very hard to make the community more
> > diversified, and my being nominated as the initial committer as a student
> > is an example of that. I believe that the maintainers of HoraeDB are
> > passionate about open source and I don't see them doing anything that would
> > be harmful to the community. This is how I feel about my involvement in
> > HoraeDB.
> >
> > Best Regards,
> > Ruixiang Tan.
> >
> > tison <wa...@gmail.com> 于2023年11月28日周二 19:30写道:
> >
> > > To be clear, when I wrote "I worked with", it doesn't mean we're
> > > colleagues. But I work with other initial committers in the community.
> > >
> > > tison <wa...@gmail.com>于2023年11月28日 周二19:15写道:
> > >
> > > > Thanks for your reply, Justin. Now I understand your concern more
> > > > concretely.
> > > >
> > > > I'll share three points here:
> > > >
> > > > 1. First of all, the trademark policy must be followed for the new
> > > > PPMC. The PPMC will protect the trademark with the guide of trademark
> > > > policy[1][2]. It's part of the road during the incubation.
> > > >
> > > > 2. I worked with the people for a while, and I trust their motivation
> > > > for running a diverse community. It's impossible to prove, but we can
> > > > do a few exercises as your new reply.
> > > >
> > > > > whereas “CeresDB” should be used in several cases
> > > >
> > > > **This is a concern. I'll check it with the initial group, resolve it,
> > > > and then go back 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 some
> > > > others from 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/marks/policies
> > > > [3] https://github.com/CeresDB/horaedb/issues/1319
> > > > [4]
> > > >
> > > https://github.com/apache/incubator-answer-website/commit/e807a7af5e48b3dfb505854f029753daf480362f
> > > >
> > > > Roman Shaposhnik <ro...@shaposhnik.org> 于2023年11月28日周二 18:27写道:
> > > > >
> > > > > On Tue, Nov 28, 2023 at 12:12 PM Justin Mclean <
> > > justin@classsoftware.com>
> > > > wrote:
> > > > > >
> > > > > > 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 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 future is a concern.
> > > > >
> > > > > While I agree that having a clear reason stated would be helpful, I
> > > > > think I have a different take on the risks you are outlining here.
> > > > >
> > > > > We have tons of examples here in the ASF of project Foo being used to
> > > > > power commercial product Bar (Geode/Gemfire, Ignite/GridGain,
> > > > > Kafka/Confluent, and many, many more). So this kind of dual branding
> > > > > is nothing new -- there's no community fork involved per se.
> > > > >
> > > > > It would be nice if the original name of the open source project (as
> > > > > it existed on Github) was donated to ASF and the new name for a
> > > > > commercially developed product was picked. But even if it is the other
> > > > > way around -- I actually don't see any risks for the foundation in
> > > > > this approach (as long as it is clearly understood that the branding
> > > > > guidelines on both sides need to be honored).
> > > > >
> > > > > Thanks,
> > > > > Roman.
> > > > >
> > > > > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > > > > For additional commands, e-mail: general-help@incubator.apache.org
> > > > >
> > > >
> > >

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [DISCUSS] HoraeDB proposal

Posted by tison <wa...@gmail.com>.
Among the conversations above, there is no policy violation, but
uncertainty for the company that donates its software.

To overcome uncertainty, IMO, time and stories help. @tanruixiang
share one, and I'll talk a bit about others.

> “HoraeDB” is used, whereas “CeresDB” should be used in several cases.

I don't see if anywhere “CeresDB” should be used. If so, HoraeDB will change.
The org name is where it leaves now and shall not to change. This is
the same as datafuselabs/opendal doesn't change its org name before
proposing for incubation.
The same for its doc site ceresdb.github.io/docs, this is associated
with GitHub org.
Others will be changed and is tracked at
https://github.com/CeresDB/horaedb/issues/1319.

For why not change the license header, it's my fault that I suppose to
rename it into ASF license header after entering the incubator, so
that we don't introduce twice large license header changeset. But the
rename is decided so we can move forward anyway.

> It looks like the rename was only done a couple of weeks ago.

Also, I don't think the time itself is an issue but the trust and
certainty, because Pekko renames all its references to Akka after
entering the incubator.

The story is that, if Ant Group doesn't want to donate the software,
there is no necessity to change the name. Ant Group approved to donate
the software, @chunshao90 and @jiacai2050 started to rename the repo,
text occurrence, and dependencies.

@jiacai2050 asked me if we should change the name in the license
header, and I regarded it can be a post-donate action as stated above.

I went through the incubator proposals and found IgniteProposal[1]
chose a new name before it was donated by GridGain Systems, Inc. which
is internally known as "GridGain In-Memory Computing Platform".

I know there are a few companies/individuals just use Ignite and/or
contribute and few people know that Ignite has some relationship with
GridGain Systems, Inc.

> That was not given as the reason.

So, Justin, your comment is not a reason also, but a suspect for
uncertainty if "some entities have taken unfair advantage of this".
This is neither provable nor unfalsifiable.

I may understand your suspect, and I choose to trust the initial
group. And if you find any concerns that may hurt the "Daul branding",
point them out and let the "PPMC" correct it (just like a few people
pointed out "Answer Cloud" issue).

Best,
tison.

[1] https://cwiki.apache.org/confluence/display/INCUBATOR/IgniteProposal

谭睿翔 <ta...@apache.org> 于2023年11月28日周二 20:33写道:

>
> Hi Justin, I am a student from Zhejiang University, one of the initial
> committers of HoraeDB. I just want to talk about my feelings. I've been
> involved in the HoraeDB community for more than half a year now. In the
> process of participating in HoraeDB community, I have been respected and
> helped by the community. In the process of participation, I can easily get
> the contextual information of Issue or pr, and I didn't encounter the
> so-called private pr only within the company. I think the maintainers of
> HoraeDB community are working very hard to make the community more
> diversified, and my being nominated as the initial committer as a student
> is an example of that. I believe that the maintainers of HoraeDB are
> passionate about open source and I don't see them doing anything that would
> be harmful to the community. This is how I feel about my involvement in
> HoraeDB.
>
> Best Regards,
> Ruixiang Tan.
>
> tison <wa...@gmail.com> 于2023年11月28日周二 19:30写道:
>
> > To be clear, when I wrote "I worked with", it doesn't mean we're
> > colleagues. But I work with other initial committers in the community.
> >
> > tison <wa...@gmail.com>于2023年11月28日 周二19:15写道:
> >
> > > Thanks for your reply, Justin. Now I understand your concern more
> > > concretely.
> > >
> > > I'll share three points here:
> > >
> > > 1. First of all, the trademark policy must be followed for the new
> > > PPMC. The PPMC will protect the trademark with the guide of trademark
> > > policy[1][2]. It's part of the road during the incubation.
> > >
> > > 2. I worked with the people for a while, and I trust their motivation
> > > for running a diverse community. It's impossible to prove, but we can
> > > do a few exercises as your new reply.
> > >
> > > > whereas “CeresDB” should be used in several cases
> > >
> > > **This is a concern. I'll check it with the initial group, resolve it,
> > > and then go back 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 some
> > > others from 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/marks/policies
> > > [3] https://github.com/CeresDB/horaedb/issues/1319
> > > [4]
> > >
> > https://github.com/apache/incubator-answer-website/commit/e807a7af5e48b3dfb505854f029753daf480362f
> > >
> > > Roman Shaposhnik <ro...@shaposhnik.org> 于2023年11月28日周二 18:27写道:
> > > >
> > > > On Tue, Nov 28, 2023 at 12:12 PM Justin Mclean <
> > justin@classsoftware.com>
> > > wrote:
> > > > >
> > > > > 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 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 future is a concern.
> > > >
> > > > While I agree that having a clear reason stated would be helpful, I
> > > > think I have a different take on the risks you are outlining here.
> > > >
> > > > We have tons of examples here in the ASF of project Foo being used to
> > > > power commercial product Bar (Geode/Gemfire, Ignite/GridGain,
> > > > Kafka/Confluent, and many, many more). So this kind of dual branding
> > > > is nothing new -- there's no community fork involved per se.
> > > >
> > > > It would be nice if the original name of the open source project (as
> > > > it existed on Github) was donated to ASF and the new name for a
> > > > commercially developed product was picked. But even if it is the other
> > > > way around -- I actually don't see any risks for the foundation in
> > > > this approach (as long as it is clearly understood that the branding
> > > > guidelines on both sides need to be honored).
> > > >
> > > > Thanks,
> > > > Roman.
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > > > For additional commands, e-mail: general-help@incubator.apache.org
> > > >
> > >
> >

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [DISCUSS] HoraeDB proposal

Posted by 谭睿翔 <ta...@apache.org>.
Hi Justin, I am a student from Zhejiang University, one of the initial
committers of HoraeDB. I just want to talk about my feelings. I've been
involved in the HoraeDB community for more than half a year now. In the
process of participating in HoraeDB community, I have been respected and
helped by the community. In the process of participation, I can easily get
the contextual information of Issue or pr, and I didn't encounter the
so-called private pr only within the company. I think the maintainers of
HoraeDB community are working very hard to make the community more
diversified, and my being nominated as the initial committer as a student
is an example of that. I believe that the maintainers of HoraeDB are
passionate about open source and I don't see them doing anything that would
be harmful to the community. This is how I feel about my involvement in
HoraeDB.

Best Regards,
Ruixiang Tan.

tison <wa...@gmail.com> 于2023年11月28日周二 19:30写道:

> To be clear, when I wrote "I worked with", it doesn't mean we're
> colleagues. But I work with other initial committers in the community.
>
> tison <wa...@gmail.com>于2023年11月28日 周二19:15写道:
>
> > Thanks for your reply, Justin. Now I understand your concern more
> > concretely.
> >
> > I'll share three points here:
> >
> > 1. First of all, the trademark policy must be followed for the new
> > PPMC. The PPMC will protect the trademark with the guide of trademark
> > policy[1][2]. It's part of the road during the incubation.
> >
> > 2. I worked with the people for a while, and I trust their motivation
> > for running a diverse community. It's impossible to prove, but we can
> > do a few exercises as your new reply.
> >
> > > whereas “CeresDB” should be used in several cases
> >
> > **This is a concern. I'll check it with the initial group, resolve it,
> > and then go back 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 some
> > others from 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/marks/policies
> > [3] https://github.com/CeresDB/horaedb/issues/1319
> > [4]
> >
> https://github.com/apache/incubator-answer-website/commit/e807a7af5e48b3dfb505854f029753daf480362f
> >
> > Roman Shaposhnik <ro...@shaposhnik.org> 于2023年11月28日周二 18:27写道:
> > >
> > > On Tue, Nov 28, 2023 at 12:12 PM Justin Mclean <
> justin@classsoftware.com>
> > wrote:
> > > >
> > > > 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 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 future is a concern.
> > >
> > > While I agree that having a clear reason stated would be helpful, I
> > > think I have a different take on the risks you are outlining here.
> > >
> > > We have tons of examples here in the ASF of project Foo being used to
> > > power commercial product Bar (Geode/Gemfire, Ignite/GridGain,
> > > Kafka/Confluent, and many, many more). So this kind of dual branding
> > > is nothing new -- there's no community fork involved per se.
> > >
> > > It would be nice if the original name of the open source project (as
> > > it existed on Github) was donated to ASF and the new name for a
> > > commercially developed product was picked. But even if it is the other
> > > way around -- I actually don't see any risks for the foundation in
> > > this approach (as long as it is clearly understood that the branding
> > > guidelines on both sides need to be honored).
> > >
> > > Thanks,
> > > Roman.
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > > For additional commands, e-mail: general-help@incubator.apache.org
> > >
> >
>

Re: [DISCUSS] HoraeDB proposal

Posted by tison <wa...@gmail.com>.
To be clear, when I wrote "I worked with", it doesn't mean we're
colleagues. But I work with other initial committers in the community.

tison <wa...@gmail.com>于2023年11月28日 周二19:15写道:

> Thanks for your reply, Justin. Now I understand your concern more
> concretely.
>
> I'll share three points here:
>
> 1. First of all, the trademark policy must be followed for the new
> PPMC. The PPMC will protect the trademark with the guide of trademark
> policy[1][2]. It's part of the road during the incubation.
>
> 2. I worked with the people for a while, and I trust their motivation
> for running a diverse community. It's impossible to prove, but we can
> do a few exercises as your new reply.
>
> > whereas “CeresDB” should be used in several cases
>
> **This is a concern. I'll check it with the initial group, resolve it,
> and then go back 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 some
> others from 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/marks/policies
> [3] https://github.com/CeresDB/horaedb/issues/1319
> [4]
> https://github.com/apache/incubator-answer-website/commit/e807a7af5e48b3dfb505854f029753daf480362f
>
> Roman Shaposhnik <ro...@shaposhnik.org> 于2023年11月28日周二 18:27写道:
> >
> > On Tue, Nov 28, 2023 at 12:12 PM Justin Mclean <ju...@classsoftware.com>
> wrote:
> > >
> > > 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 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 future is a concern.
> >
> > While I agree that having a clear reason stated would be helpful, I
> > think I have a different take on the risks you are outlining here.
> >
> > We have tons of examples here in the ASF of project Foo being used to
> > power commercial product Bar (Geode/Gemfire, Ignite/GridGain,
> > Kafka/Confluent, and many, many more). So this kind of dual branding
> > is nothing new -- there's no community fork involved per se.
> >
> > It would be nice if the original name of the open source project (as
> > it existed on Github) was donated to ASF and the new name for a
> > commercially developed product was picked. But even if it is the other
> > way around -- I actually don't see any risks for the foundation in
> > this approach (as long as it is clearly understood that the branding
> > guidelines on both sides need to be honored).
> >
> > Thanks,
> > Roman.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
>

Re: [DISCUSS] HoraeDB proposal

Posted by tison <wa...@gmail.com>.
Thanks for your reply, Justin. Now I understand your concern more concretely.

I'll share three points here:

1. First of all, the trademark policy must be followed for the new
PPMC. The PPMC will protect the trademark with the guide of trademark
policy[1][2]. It's part of the road during the incubation.

2. I worked with the people for a while, and I trust their motivation
for running a diverse community. It's impossible to prove, but we can
do a few exercises as your new reply.

> whereas “CeresDB” should be used in several cases

**This is a concern. I'll check it with the initial group, resolve it,
and then go back 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 some
others from 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/marks/policies
[3] https://github.com/CeresDB/horaedb/issues/1319
[4] https://github.com/apache/incubator-answer-website/commit/e807a7af5e48b3dfb505854f029753daf480362f

Roman Shaposhnik <ro...@shaposhnik.org> 于2023年11月28日周二 18:27写道:
>
> On Tue, Nov 28, 2023 at 12:12 PM Justin Mclean <ju...@classsoftware.com> wrote:
> >
> > 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 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 future is a concern.
>
> While I agree that having a clear reason stated would be helpful, I
> think I have a different take on the risks you are outlining here.
>
> We have tons of examples here in the ASF of project Foo being used to
> power commercial product Bar (Geode/Gemfire, Ignite/GridGain,
> Kafka/Confluent, and many, many more). So this kind of dual branding
> is nothing new -- there's no community fork involved per se.
>
> It would be nice if the original name of the open source project (as
> it existed on Github) was donated to ASF and the new name for a
> commercially developed product was picked. But even if it is the other
> way around -- I actually don't see any risks for the foundation in
> this approach (as long as it is clearly understood that the branding
> guidelines on both sides need to be honored).
>
> Thanks,
> Roman.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [DISCUSS] HoraeDB proposal

Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,

> We have tons of examples here in the ASF of project Foo being used to
> power commercial product Bar (Geode/Gemfire, Ignite/GridGain,
> Kafka/Confluent, and many, many more). So this kind of dual branding
> is nothing new -- there's no community fork involved per se.

"Daul branding" is nothing new, but recently, some entities have taken unfair advantage of this (including one you mentioned), and I feel the Incubator should take care that others do not also do this.

> It would be nice if the original name of the open source project (as
> it existed on Github) was donated to ASF and the new name for a
> commercially developed product was picked. But even if it is the other
> way around -- I actually don't see any risks for the foundation in
> this approach (as long as it is clearly understood that the branding
> guidelines on 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	


1. https://github.com/CeresDB/horaedb/commit/7de05192d7fa6d96cdd49ffab4a4fd4754d64b68


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [DISCUSS] HoraeDB proposal

Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
On Tue, Nov 28, 2023 at 12:12 PM Justin Mclean <ju...@classsoftware.com> wrote:
>
> 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 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 future is a concern.

While I agree that having a clear reason stated would be helpful, I
think I have a different take on the risks you are outlining here.

We have tons of examples here in the ASF of project Foo being used to
power commercial product Bar (Geode/Gemfire, Ignite/GridGain,
Kafka/Confluent, and many, many more). So this kind of dual branding
is nothing new -- there's no community fork involved per se.

It would be nice if the original name of the open source project (as
it existed on Github) was donated to ASF and the new name for a
commercially developed product was picked. But even if it is the other
way around -- I actually don't see any risks for the foundation in
this approach (as long as it is clearly understood that the branding
guidelines on both sides need to be honored).

Thanks,
Roman.

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [DISCUSS] HoraeDB proposal

Posted by Justin Mclean <ju...@classsoftware.com>.
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 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 future is a concern.

Kind Regards,
Justin

> On 28 Nov 2023, at 8:29 pm, tison <wa...@gmail.com> wrote:
> 
> Let me be clear on the reason for keeping the name:
> 
> 1. Ant Group registered the trademark CeresDB and did marketing work
> associated with the product. They want to keep the result under Ant
> Group corp even if the software source code is donated to ASF
> incubator.
> 2. Ant Group wants to retain the possibility of providing a product
> with the name "CeresDB", although there is not on-going plan now.
> 
> These are all the concert reasons that the name is changed to HoraeDB
> for donating. And I don't think we have some policies to prevent a
> to-be-donated project for doing so - it's effectively the same as Ant
> Group donates a project named HoraeDB which shares the same code with
> their codebase internally named "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 <wa...@gmail.com> 于2023年11月28日周二 09:12写道:
>> 
>> Perhaps think of an analogy with Docker vs. Moby?
>> 
>> Justin Mclean <ju...@classsoftware.com>于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 retrain that brand? They are not using an internal version of the project currently. Do they intend to fork the project?
>>> 
>>> Kind Regards,
>>> Justin
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [DISCUSS] HoraeDB proposal

Posted by tison <wa...@gmail.com>.
> their codebase internally named
>  Do they intend to fork the project?

No.

> They are not using an internal version of the project currently.

Yes.

> Ant Group wants to retain the possibility of providing a product

Be careful of "retain the possibility", it doesn't mean any internal
fork or on-going plan for biz products.

 Best,
tison.

tison <wa...@gmail.com> 于2023年11月28日周二 17:36写道:
>
> For reference:
>
> * Apache Seatunnel is named as Waterdrop before donation.
> * Apache Flink is named as Stratosphere ever.
>
> Best,
> tison.
>
> tison <wa...@gmail.com> 于2023年11月28日周二 17:29写道:
> >
> > Let me be clear on the reason for keeping the name:
> >
> > 1. Ant Group registered the trademark CeresDB and did marketing work
> > associated with the product. They want to keep the result under Ant
> > Group corp even if the software source code is donated to ASF
> > incubator.
> > 2. Ant Group wants to retain the possibility of providing a product
> > with the name "CeresDB", although there is not on-going plan now.
> >
> > These are all the concert reasons that the name is changed to HoraeDB
> > for donating. And I don't think we have some policies to prevent a
> > to-be-donated project for doing so - it's effectively the same as Ant
> > Group donates a project named HoraeDB which shares the same code with
> > their codebase internally named "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 <wa...@gmail.com> 于2023年11月28日周二 09:12写道:
> > >
> > > Perhaps think of an analogy with Docker vs. Moby?
> > >
> > > Justin Mclean <ju...@classsoftware.com>于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 retrain that brand? They are not using an internal version of the project currently. Do they intend to fork the project?
> > >>
> > >> Kind Regards,
> > >> Justin
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > >> For additional commands, e-mail: general-help@incubator.apache.org
> > >>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [DISCUSS] HoraeDB proposal

Posted by tison <wa...@gmail.com>.
For reference:

* Apache Seatunnel is named as Waterdrop before donation.
* Apache Flink is named as Stratosphere ever.

Best,
tison.

tison <wa...@gmail.com> 于2023年11月28日周二 17:29写道:
>
> Let me be clear on the reason for keeping the name:
>
> 1. Ant Group registered the trademark CeresDB and did marketing work
> associated with the product. They want to keep the result under Ant
> Group corp even if the software source code is donated to ASF
> incubator.
> 2. Ant Group wants to retain the possibility of providing a product
> with the name "CeresDB", although there is not on-going plan now.
>
> These are all the concert reasons that the name is changed to HoraeDB
> for donating. And I don't think we have some policies to prevent a
> to-be-donated project for doing so - it's effectively the same as Ant
> Group donates a project named HoraeDB which shares the same code with
> their codebase internally named "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 <wa...@gmail.com> 于2023年11月28日周二 09:12写道:
> >
> > Perhaps think of an analogy with Docker vs. Moby?
> >
> > Justin Mclean <ju...@classsoftware.com>于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 retrain that brand? They are not using an internal version of the project currently. Do they intend to fork the project?
> >>
> >> Kind Regards,
> >> Justin
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >> For additional commands, e-mail: general-help@incubator.apache.org
> >>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [DISCUSS] HoraeDB proposal

Posted by tison <wa...@gmail.com>.
Let me be clear on the reason for keeping the name:

1. Ant Group registered the trademark CeresDB and did marketing work
associated with the product. They want to keep the result under Ant
Group corp even if the software source code is donated to ASF
incubator.
2. Ant Group wants to retain the possibility of providing a product
with the name "CeresDB", although there is not on-going plan now.

These are all the concert reasons that the name is changed to HoraeDB
for donating. And I don't think we have some policies to prevent a
to-be-donated project for doing so - it's effectively the same as Ant
Group donates a project named HoraeDB which shares the same code with
their codebase internally named "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 <wa...@gmail.com> 于2023年11月28日周二 09:12写道:
>
> Perhaps think of an analogy with Docker vs. Moby?
>
> Justin Mclean <ju...@classsoftware.com>于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 retrain that brand? They are not using an internal version of the project currently. Do they intend to fork the project?
>>
>> Kind Regards,
>> Justin
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [DISCUSS] HoraeDB proposal

Posted by Justin Mclean <ju...@classsoftware.com>.
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-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [DISCUSS] HoraeDB proposal

Posted by ShaoFeng Shi <sh...@apache.org>.
Using a new name to avoid any possible confusion or conflict is reasonable
I think. Just like PALO changed to Doris when it was contributed to ASF, as
the name PALO has already been used in Baidu internal.

Best regards,

Shaofeng Shi 史少锋
Apache Kylin PMC,
Apache Incubator PMC,
Email: shaofengshi@apache.org

Apache Kylin FAQ: https://kylin.apache.org/docs/gettingstarted/faq.html
Join Kylin user mail group: user-subscribe@kylin.apache.org
Join Kylin dev mail group: dev-subscribe@kylin.apache.org




tison <wa...@gmail.com> 于2023年11月28日周二 09:13写道:

> Perhaps think of an analogy with Docker vs. Moby?
>
> Justin Mclean <ju...@classsoftware.com>于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 retrain that brand? They are not using an internal
> > version of the project currently. Do they intend to fork the project?
> >
> > Kind Regards,
> > Justin
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
> >
>

Re: [DISCUSS] HoraeDB proposal

Posted by tison <wa...@gmail.com>.
Perhaps think of an analogy with Docker vs. Moby?

Justin Mclean <ju...@classsoftware.com>于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 retrain that brand? They are not using an internal
> version of the project currently. Do they intend to fork the project?
>
> Kind Regards,
> Justin
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

Re: [DISCUSS] HoraeDB proposal

Posted by Justin Mclean <ju...@classsoftware.com>.
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 retrain that brand? They are not using an internal version of the project currently. Do they intend to fork the project?

Kind Regards,
Justin
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [DISCUSS] HoraeDB proposal

Posted by Justin Mclean <ju...@classsoftware.com>.
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 retrain that brand? They are not using an internal version of the project currently. Do they intend to fork the project?

Kind Regards,
Justin
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [DISCUSS] HoraeDB proposal

Posted by tison <wa...@gmail.com>.
> There are many communication channels e.g. Slack, WeChat, DingTalk. What
will happen to these in the future and who controls them? Will control of
these be transferred to the PMC?

These channels are not included in the proposal and we're going to remove
the entries from README or other content during the entering stage.

For users channel, we plan to maintain (1) GitHub Discussions & Issues (2)
dev@ mailing list. (1) will be redirected to the list with INFRA set up.
For a user@ list, we may create one if it is necessary. Other IM channels,
during the project building experience, it's less active. So the PMC may
not maintain it or advertise it. If we later find a necessity to run those
channels under the PMC brand, we'll start a discussion then.

> ring is licensed

FYI - https://github.com/briansmith/ring/issues/1827

Also, this is a widely used Rust basic crate that I assume most of the Rust
code released from ASF projects can suffer the same concern. I have
optimistic assumptions that all the ecosystems affected by these concerns
should be able to work out a solution/resolution.

Best,
tison.


tison <wa...@gmail.com> 于2023年11月27日周一 09:38写道:

> > The ring license seems to include BSD-style licenses with advertising
> clauses. These are considered category X.
>
> This is once discovered in [1] and the description is:
>
> ring is licensed under a mix of [MIT, ISC, and OpenSSL’s licenses](
> https://github.com/briansmith/ring/blob/main/LICENSE). OpenSSL itself is
> licensed under [Apache 2.0](
> https://www.openssl.org/source/apache-license-2.0.txt). So ring is Apache
> 2.0 compatible.
>
> You're right that the LICENSE file contains some sentences about the advertising
> clauses, but that may not be correct. I'll contact the upstream to see if
> we can revise the license terms.
>
> > I‘m curious about the name change and why the original name is being
> kept. How you provide a bit more detail on this?
>
> 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.
>
> I suppose it's what happened in the other direction for the Answer podling
> story.
>
> > Looking at the existing governance, I see that 2/3 of existing PMC
> members are needed to vote for a new PMC member. I assume this requirement
> will be dropped?
>
> Yep. Simply follow the basic ASF governance as a start is expected.
>
> Best,
> tison.
>
> [1] https://lists.apache.org/thread/px7wjcjy3rd4s59d4d3ll1x6y11d240r
>
>
> Justin Mclean <ju...@classsoftware.com> 于2023年11月27日周一 07:30写道:
>
>> Hi,
>>
>> Looking at the existing governance, I see that 2/3 of existing PMC
>> members are needed to vote for a new PMC member. I assume this requirement
>> will be dropped?
>>
>> There are many communication channels e.g. Slack, WeChat, DingTalk. What
>> will happen to these in the future and who controls them? Will control of
>> these be transferred to the PMC?
>>
>> I‘m curious about the name change and why the original name is being
>> kept. How you provide a bit more detail on this?
>>
>> Kind Regards,
>> Justin
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>

Re: [DISCUSS] HoraeDB proposal

Posted by tison <wa...@gmail.com>.
> The ring license seems to include BSD-style licenses with advertising
clauses. These are considered category X.

This is once discovered in [1] and the description is:

ring is licensed under a mix of [MIT, ISC, and OpenSSL’s licenses](
https://github.com/briansmith/ring/blob/main/LICENSE). OpenSSL itself is
licensed under [Apache 2.0](
https://www.openssl.org/source/apache-license-2.0.txt). So ring is Apache
2.0 compatible.

You're right that the LICENSE file contains some sentences about the
advertising
clauses, but that may not be correct. I'll contact the upstream to see if
we can revise the license terms.

> I‘m curious about the name change and why the original name is being
kept. How you provide a bit more detail on this?

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.

I suppose it's what happened in the other direction for the Answer podling
story.

> Looking at the existing governance, I see that 2/3 of existing PMC
members are needed to vote for a new PMC member. I assume this requirement
will be dropped?

Yep. Simply follow the basic ASF governance as a start is expected.

Best,
tison.

[1] https://lists.apache.org/thread/px7wjcjy3rd4s59d4d3ll1x6y11d240r


Justin Mclean <ju...@classsoftware.com> 于2023年11月27日周一 07:30写道:

> Hi,
>
> Looking at the existing governance, I see that 2/3 of existing PMC members
> are needed to vote for a new PMC member. I assume this requirement will be
> dropped?
>
> There are many communication channels e.g. Slack, WeChat, DingTalk. What
> will happen to these in the future and who controls them? Will control of
> these be transferred to the PMC?
>
> I‘m curious about the name change and why the original name is being kept.
> How you provide a bit more detail on this?
>
> Kind Regards,
> Justin
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

Re: [DISCUSS] HoraeDB proposal

Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,

Looking at the existing governance, I see that 2/3 of existing PMC members are needed to vote for a new PMC member. I assume this requirement will be dropped?

There are many communication channels e.g. Slack, WeChat, DingTalk. What will happen to these in the future and who controls them? Will control of these be transferred to the PMC?

I‘m curious about the name change and why the original name is being kept. How you provide a bit more detail on this?

Kind Regards,
Justin
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [DISCUSS] HoraeDB proposal

Posted by Justin Mclean <ju...@classsoftware.com>.
HI,

The ring license seems to include BSD-style licenses with advertising clauses. These are considered category X. [1]

Kind Regards,
Justin

1. https://www.apache.org/legal/resolved.html#category-x

Re: [DISCUSS] HoraeDB proposal

Posted by tison <wa...@gmail.com>.
Hi PJ.

Thanks for pointing that out! It's handled with [1] that most of them are
internal crates which should use the same Apache License 2.0 but forget to
fill the license field so that the tool doesn't spot it.

After [1], only these deps are "unlicensed"

*  librocksdb_sys@0.1.0 & libtitan_sys@0.0.1 - from
https://github.com/tikv/rust-rocksdb, we can use it under Apache License
2.0.
* obkv-table-client-rs@0.1.0 - MulanPSL2, An OSI-approved "permission"
license. Should be in category A.
* ring@0.16.20 - https://github.com/briansmith/ring/blob/main/LICENSE a bit
complex, but the conclusion is we can use it.

Best,
tison.

[1] https://github.com/CeresDB/horaedb/pull/1317


PJ Fanning <fa...@gmail.com> 于2023年11月25日周六 03:37写道:

> The proposal looks good to me. One item that concerns me is the list
> of Unlicensed Cargo crates (as opposed to licensed under the
> Unlicense). Most of these unlicensed crates have 'alpha' versions.
>
> Search for: Unlicensed (59)
>
>
>
> On Fri, 24 Nov 2023 at 16:57, tison <wa...@gmail.com> wrote:
> >
> > Hi IPMC members,
> >
> > I would like to propose a new project to the ASF incubator - HoraeDB.
> >
> > HoraeDB[1] is a high-performance, distributed, cloud-native time-series
> > database that explicitly handles high-cardinality time-series data and
> > provides native distributed capabilities.
> >
> > 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/HoraeDB+Proposal
> >
> > I would be the Champion of the project.
> >
> > I will mentor and help the project through the incubator with Shaofeng
> Shi [
> > shaofengshi@apache.org] and Gang Li [lgcareer@apache.org].
> >
> > We are open to hearing the feedback from the incubator.
> >
> > Best,
> > tison.
> >
> > [1] https://github.com/CeresDB/horaedb
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

Re: [DISCUSS] HoraeDB proposal

Posted by PJ Fanning <fa...@gmail.com>.
The proposal looks good to me. One item that concerns me is the list
of Unlicensed Cargo crates (as opposed to licensed under the
Unlicense). Most of these unlicensed crates have 'alpha' versions.

Search for: Unlicensed (59)



On Fri, 24 Nov 2023 at 16:57, tison <wa...@gmail.com> wrote:
>
> Hi IPMC members,
>
> I would like to propose a new project to the ASF incubator - HoraeDB.
>
> HoraeDB[1] is a high-performance, distributed, cloud-native time-series
> database that explicitly handles high-cardinality time-series data and
> provides native distributed capabilities.
>
> 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/HoraeDB+Proposal
>
> I would be the Champion of the project.
>
> I will mentor and help the project through the incubator with Shaofeng Shi [
> shaofengshi@apache.org] and Gang Li [lgcareer@apache.org].
>
> We are open to hearing the feedback from the incubator.
>
> Best,
> tison.
>
> [1] https://github.com/CeresDB/horaedb

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org