Hi IPMC,
Von Gosling expressed he wants to become a mentor of HoraeDB and he is an
ASF Member,so I added him to the list of mentors, and the proposal [1] has
been updated.
1.https://cwiki.apache.org/confluence/display/INCUBATOR/HoraeDB+Proposal
tison 于2023年11月24日周五 23:58写道：
> Hi IPMC members,
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
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
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
>> 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
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 于2023年11月29日周三 15:55写道：
>
> > You also have things like this, which was published in the last day. If
> 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
> 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
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
> 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,
> 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]:
Hi Justin,
> From the discussion and proposal, I had understood that the HoraeDB
project still wants to use the CeresDB name in some form. Is this correct
or not?
NO.
The new project will use the name HoraeDB and not refer to CeresDB.
Best,
Chunshao Ren.
Justin Mclean 于2023年11月29日周三 13: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:
> 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
>> 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
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
Updated. You may check and point out any improper mentions.
I use a rule that always refers to the software as HoraeDB in the
proposal (since the rename is happening), unless when referring to its
initial development and open-sourced.
Best,
tison.
tison 于2023年11月28日周二 23:05写道：
>
> > “HoraeDB”
> “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
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
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
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 于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
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
Hi,
> Using a new name to avoid any possible confusion or conflict is reasonable
> I think.
That was not given as the reason.
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands,
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:
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
On Tue, Nov 28, 2023 at 12:12 PM Justin Mclean 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
>
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
> 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
For reference:
* Apache Seatunnel is named as Waterdrop before donation.
* Apache Flink is named as Stratosphere ever.
Best,
tison.
tison 于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
>
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
Perhaps think of an analogy with Docker vs. Moby?
Justin Mclean 于2023年11月28日 周二07:15写道：
> HI,
>
> > This is included in the proposal: Since Ant Group wants to retain the
> brand
> > of CeresDB, we renamed the OSS project as HoraeDB before this proposal.
>
> Why do they want to retrain that
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
> 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
> 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).
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?
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
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 &
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 wrote:
>
> Hi IPMC members,
>
>
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
39 matches
Mail list logo
