> 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 trac
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
> 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.
The vote carries with 3 +1s (all binding).
Vote Thread
https://lists.apache.org/thread/8fxdmj1rjw6x6x5p9w09vn5g43wm6lzp
Votes
Paul King
Matthew de Detrich
PJ Fanning
I will proceed with the release and announcements over the next few
days. Thanks to everyone who participated in the development a
Thanks Paul. I'm not sure if the build works on Windows. The CI is
Linux based. Most developers on the Pekko project use MacOS or Linux
to build. I'll log an issue in the hope that someone with a Windows
computer could look at it.
The AddThis license comes from:
https://github.com/addthis/stream-l
> 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]:
Gr
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写道：
Hello everyone,
The Apache Answer(Incubating) v1.2.0 has been released!
Apache Answer is a Q&A platform software for teams at any scale.
Whether it's a community forum, help center, or knowledge management
platform, you can always count on Apache Answer.
Download Links: https://downloads.apache.
HI,
From the discussion and proposal, I had understood that the HoraeDB project
still wants to use the CeresDB name in some form. Is this correct or not?
Kind Regards,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incub
> 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 inc
Hello Incubator PMC and Community,
The vote to release Apache Answer(Incubating) v1.2.0-RC1 has passed
with 3 +1 binding and 1 +1 non-binding votes, no +0 or -1 votes.
3 (+1 binding)
Justin McLean
Christofer Dutz
tison
1 (+1 non-binding)
Feng Dong
no further 0 or
Hi PJ and Yu,
Thanks for the careful checking and suggestions. I've opened [1] to
track the issue and we will resolve it in the next release, if you
also don't think this is a release blocker.
[1] https://github.com/apache/incubator-paimon/issues/2413
Best,
Jingsong
On Wed, Nov 29, 2023 at 8:33
I agree that the current organization of the jar is a little bit confusing.
It would be better to keep a single META-INF directory at the root level,
and introduce no additional "paimon-plugin-s3" directory in the dir tree.
@Jingsong Li and team: please take a look here and
open an issue to track
>> 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
+1 (binding)
[X] Download links are valid.
[X] Checksums and signatures.
[X] LICENSE/NOTICE files exist
I did notice "Copyright 2016 AddThis" in the LICENSE file wrt
MurmurHash3, something to fix for the next release?
Given the accompanying explanation in the file, I don't see this
as a sh
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 on
I'll take a look.
On Mon, Nov 27, 2023 at 11:46 PM PJ Fanning wrote:
>
> Hi everyone,
>
> This RC includes a security hardening change. I am wondering if any Pekko
> mentors or any other Incubator PMC member might have time to review the RC
> artifacts so that we can do a release.
>
> Thanks,
>
I've also never seen the multi-release classes in a dir like
paimon-plugin-s3/META-INF/versions/ - I've only ever seen them in
META-INF/versions dir (ie no paimon-plugin-s3 dir in the dir tree).
On Tue, 28 Nov 2023 at 20:03, PJ Fanning wrote:
>
> Why is there a META-INF dir and a paimon-plugin-s3
Why is there a META-INF dir and a paimon-plugin-s3/META-INF dir with
revival license files?
I must admit to finding this confusing. Is there any way to only have
one META-INF dir. Most people expect META-INF at the root level - so
if we consolidate the 2 META-INF dirs then I'd prefer if the root
l
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” i
> “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
Hi PJ,
Thanks for the notice.
It seems to me that in the META-INF/NOTICE file bundled in the
paimon-s3-0.6.0-incubating.jar files, there're license disclaimers about
the dependencies, with references to the location of the relative license
file (under the nested "licenses" directory), such as:
--
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 c
Thanks for your reference. Then it's not a blocker. Although I may
prefer name the folder as "apache-answer-1.2.0-incubating-src", it's
not required.
Restate +1 (binding)
Best,
tison.
Justin Mclean 于2023年11月28日周二 21:16写道：
>
> Hi,
>
> The release artefacts include incubating in their names [1] a
Hi,
The release artefacts include incubating in their names [1] as Incubator policy
requires [2].
Kind Regards,
Justin
1. https://dist.apache.org/repos/dist/dev/incubator/answer/1.2.0-incubating-RC1/
2. https://incubator.apache.org/policy/incubation.html#releases
Wait a minute, this may be a -1 reason:
We just publish the RC artifacts as is, so the formal release that
users will get is a tarball that is unzipped to
"incubator-answer-1.2.0-RC1".
The folder/file name is once a concern[1] although it's a missing
"incubating" in the tarball name that is refer
The unzipped folder is named as "incubator-answer-1.2.0-RC1", this can
be improved also - keep the same as
"apache-answer-1.2.0-incubating-src".
Best,
tison.
tison 于2023年11月28日周二 21:00写道：
>
> +1 (binding)
>
> I checked -
> [x] Download links valid
> [x] apache & incubating in name
> [x] LICENSE
+1 (binding)
I checked -
[x] Download links valid
[x] apache & incubating in name
[x] LICENSE and NOTICE present
[x] Checksum and GPG sign matches
[x] DISCLAIMER present
[x] Can compile from source with `make ui; make build`
note: for building, you may need to install mockgen first: go install
go
Would be cool, if one more IPMC member would be willing to give this release a
vote…. Admittedly it’s in really good shape and therefore just a minimal bit of
work.
Chris
Von: Feng Dong
Datum: Dienstag, 28. November 2023 um 10:41
An: general@incubator.apache.org
Betreff: Re: [VOTE] Release A
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 t
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 of
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 incub
Hi,
> Using a new name to avoid any possible confusion or conflict is reasonable
> I think.
That was not given as the reason.
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-
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: shaofeng...@a
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 noth
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 associat
There is a META-INF/DEPENDENCIES file in
paimon-s3-0.6.0-incubating.jar but it lists only a small fraction of
the external jars that are bundled into
paimon-s3-0.6.0-incubating.jar.
On Tue, 28 Nov 2023 at 11:05, PJ Fanning wrote:
>
> I had a look at this jar:
>
> https://repository.apache.org/con
I had a look at this jar:
https://repository.apache.org/content/repositories/orgapachepaimon-1029/org/apache/paimon/paimon-s3/0.6.0-incubating/paimon-s3-0.6.0-incubating.jar
It has a META-INF/LICENSE file but this file is a generic ASF license
and has no details about all the non-ASF classes that
> 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 o
+1 (non-binding)
On Mon, Nov 20, 2023 at 5:31 PM Christofer Dutz
wrote:
> +1 (binding)
>
> Chris
>
> [OK] Download all staged artifacts under the url specified in the release
> vote email.
> [OK] Verify the signature is correct.
> [OK] Check if the signature references an Apache email address.
>
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
> as
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 pos
44 matches
Mail list logo
