Re: [DISCUSS] HoraeDB proposal
> 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 于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 于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-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] HoraeDB proposal
> 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 于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-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] HoraeDB proposal
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-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] HoraeDB proposal
> 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 于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 于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-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[RESULT] [VOTE] Release Apache Pekko(incubating) Core 1.0.2-RC1
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 and the review of this release. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Pekko(incubating) Core 1.0.2-RC1
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-lib/blob/master/NOTICE.txt
This was pulled in due to this line:
https://github.com/apache/incubator-pekko/blob/8fefca1c81e13d089ed8db85f375eb3538089c43/remote/src/main/java/org/apache/pekko/remote/artery/compress/CountMinSketch.java#L27
Which has links to
https://github.com/addthis/stream-lib/blob/master/src/main/java/com/clearspring/analytics/stream/frequency/CountMinSketch.java
On Wed, 29 Nov 2023 at 00:59, Paul King wrote:
>
> +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 showstopper for this release.
> [X] No unexpected binary files
> I didn't do an exhaustive check
> [X] Source files have ASF headers
> [-] Can compile from source
> I ran "sbt compile" and "sbt package" but both had errors. A sample:
> [error] bnd: Invalid value for Bundle-Version, HEAD+20231129-0950
> does not match [0-9]{1,9}(\.[0-9]{1,9}(\.[0-9]{1,9}(\.[0-9A-Za-z_-]+)?)?)?
> [error] java.util.zip.ZipException: duplicate entry: META-INF/MANIFEST.MF
> ...
> [error]
> D:\tmp\pekko102\apache-pekko-1.0.2-incubating-src-20231115\actor\src\main\java\org\apache\pekko\util\Unsafe.java:25:23:
> not found: value sun
> [error] public static final sun.misc.Unsafe instance;
> [error] ^
> I rarely run sbt, so this could easily be my local setup. I didn't
> try my linux box. Maybe it would have worked there.
>
> I also tested the artifacts in the staging repo with a simple typed
> actors example in Groovy:
> https://github.com/paulk-asert/groovy-pekko-gpars/tree/main/src/main/groovy/pekko
> I used Groovy 4.0.15, the 1.0.2-RC1 artifacts and the Scala 2.13 runtime.
> It ran without problems.
>
> Cheers, Paul.
>
> On Sat, Nov 18, 2023 at 11:56 PM PJ Fanning wrote:
> >
> > Hello Incubator Community,
> >
> > This is a call for a vote to release Apache Pekko(incubating)
> > Core version 1.0.2-RC1.
> >
> > The discussion thread:
> > https://lists.apache.org/thread/zy84yk5gxp54bkn81ntlj5ps5o2z9w4j
> >
> > Pekko Vote Thread
> > https://lists.apache.org/thread/0ojxypkm650bhk6pf53cp7h8036jgyol
> >
> > Pekko Result:
> > https://lists.apache.org/thread/mh398gtjm751fq4fhss5c0xfwxnvx2xy
> >
> > The release candidate:
> >
> > https://dist.apache.org/repos/dist/dev/incubator/pekko/1.0.2-RC1/
> >
> > This release has been signed with a PGP key, available here:
> >
> > https://dist.apache.org/repos/dist/release/incubator/pekko/KEYS
> >
> > Git branch for the release:
> >
> > https://github.com/apache/incubator-pekko/tree/v1.0.2-RC1
> > Git commit ID: 58fa510455190bd62d04f92a83c9506a7588d29c
> >
> > Release Notes:
> >
> > https://nightlies.apache.org/pekko/docs/pekko/1.0/docs/release-notes/index.html#1-0-2
> >
> > Please download, verify, and test.
> >
> > We have also staged jars in the Apache Nexus Repository. These were
> > built with the same code
> > as appears in this Source Release Candidate. We would appreciate if
> > users could test with these too.
> > If anyone finds any serious problems with these jars, please also
> > notify us on this thread.
> >
> > https://repository.apache.org/content/groups/staging/org/apache/pekko/
> >
> > In sbt, you can add this resolver.
> >
> > resolvers += "Apache Pekko Staging" at
> > "https://repository.apache.org/content/groups/staging";
> >
> >
> > The vote will be left open for at least 72 hours.
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > To learn more about Apache Pekko, please see https://pekko.apache.org/
> >
> > Checklist for reference:
> >
> > [ ] Download links are valid.
> > [ ] Checksums and signatures.
> > [ ] LICENSE/NOTICE files exist
> > [ ] No unexpected binary files
> > [ ] Source files have ASF headers
> > [ ] Can compile from source
> >
> > To compile from the source, please refer to:
> >
> > https://github.com/apache/incubator-pekko/blob/main/README.md#building-from-source
> >
> > Some notes about verifying downloads can be found at:
> >
> > https://pekko.apache.org/download.html#verifying-downloads
> >
> >
> > Here is my +1 (binding).
> >
> > Thanks,
> >
> > PJ Fanning
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For addition
Re: [DISCUSS] HoraeDB proposal
> 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 于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-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [DISCUSS] HoraeDB proposal
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: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
[ANNOUNCE] Apache Answer(Incubating) v1.2.0 available
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.org/incubator/answer/ Release Notes: https://github.com/apache/incubator-answer/releases/tag/v1.2.0 Website: https://answer.apache.org/ Resources: - Issue: https://github.com/apache/incubator-answer/issues - Mailing list: d...@answer.apache.org Best regards, LinkinStar
Re: [DISCUSS] HoraeDB proposal
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...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] HoraeDB proposal
> 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 于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 于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-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > >
[RESULT][VOTE] Release Apache Answer(Incubating) v1.2.0-RC1
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 -1 votes. The vote thread: https://lists.apache.org/thread/yrnl1lqgd64312jg7wc5hop5kymtz43x Thanks for reviewing and voting for our release candidate. We will proceed with publishing the approved artifacts and sending out the announcement soon. Thanks, LinkinStar
Re: [VOTE] Release Apache Paimon(incubating) 0.6.0-incubating rc1
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 AM Yu Li wrote: > > 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/resolve it if you also find this reasonable, or let us know your > thoughts if I miss anything. > > Best Regards, > Yu > > > On Wed, 29 Nov 2023 at 03:08, PJ Fanning wrote: >> >> 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/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 >> > level one is the one that is kept. >> > >> > On Tue, 28 Nov 2023 at 15:50, Yu Li wrote: >> > > >> > > 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: >> > > - >> > > >> > > This project bundles the following dependencies under BSD-2 License ( >> > > https://opensource.org/licenses/BSD-2-Clause). >> > > >> > > You find it under licenses/LICENSE.dnsjava. >> > > >> > > ... >> > > >> > > This project bundles the following dependencies under the MIT ( >> > > https://opensource.org/licenses/MIT) >> > > >> > > You find them under licenses/LICENSE.checker-framework-qualifiers and >> > > licenses/LICENSE.animal-sniffer. >> > > >> > > ... >> > > >> > > This project bundles the following dependencies under the CDDL 1.1 >> > > license. >> > > >> > > You find it under licenses/LICENSE.jaxb. >> > > >> > > ... >> > > - >> > > >> > > I happen to know this since I noticed similar issues and asked the team >> > > to >> > > resolve them in release 0.4.0 [1], so just for your information. >> > > >> > > Since I haven't completed checking this rc yet, it's possible that there >> > > are newly introduced dependencies in the paimon-filesystems module >> > > (especially the paimon-s3 and paimon-s3-impl sub-modules). Would you mind >> > > further checking it and let us know the detailed dependency with license >> > > (notice/file) missing? Thanks. >> > > >> > > And I will also check this carefully when time allows. >> > > >> > > Best Regards, >> > > Yu >> > > >> > > [1] >> > > https://github.com/apache/incubator-paimon/pull/1067#issuecomment-1537338118 >> > > >> > > On Tue, 28 Nov 2023 at 18:10, PJ Fanning wrote: >> > > >> > > > 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/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 are bundled in >> > > > > the jar. >> > > > > >> > > > > The META-INF/NOTICE likewise does not mention anything about the >> > > > > non-ASF classes. >> > > > > >> > > > > >> > > > > On Mon, 27 Nov 2023 at 04:04, Jingsong Li >> > > > wrote: >> > > > > > >> > > > > > Hello Incubator PMC, >> > > > > > >> > > > > > The Apache Paimon community has voted and approved the release of >> > > > > > Apache Paimon(incubating) 0.6.0-incubating rc1. We now kindly >> > > > > > request >> > > > > > the IPMC members review and vote for this release. >> > > > > > >> > > > > > Apache Paimon(incubating) is a streaming data lake platform that >> > > > > > supports high-speed data ingestion, change data tracking and >> > > > > > efficient >> > > > > > real-time analytics. >> > > > > > >> > > > > > Paimon community vote thread: >> > > > > > >> > > > > > https://lists.apache.org/thread/fvzljoyokvs0dp6d24wwvtgdmrczfb3j >> > > > > > >> > > > > > Vote result thread: >> > > > > > >> > >
Re: [VOTE] Release Apache Paimon(incubating) 0.6.0-incubating rc1
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/resolve it if you also find this reasonable, or let us know your thoughts if I miss anything. Best Regards, Yu On Wed, 29 Nov 2023 at 03:08, PJ Fanning wrote: > 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/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 > > level one is the one that is kept. > > > > On Tue, 28 Nov 2023 at 15:50, Yu Li wrote: > > > > > > 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: > > > - > > > > > > This project bundles the following dependencies under BSD-2 License ( > > > https://opensource.org/licenses/BSD-2-Clause). > > > > > > You find it under licenses/LICENSE.dnsjava. > > > > > > ... > > > > > > This project bundles the following dependencies under the MIT ( > > > https://opensource.org/licenses/MIT) > > > > > > You find them under licenses/LICENSE.checker-framework-qualifiers and > > > licenses/LICENSE.animal-sniffer. > > > > > > ... > > > > > > This project bundles the following dependencies under the CDDL 1.1 > license. > > > > > > You find it under licenses/LICENSE.jaxb. > > > > > > ... > > > - > > > > > > I happen to know this since I noticed similar issues and asked the > team to > > > resolve them in release 0.4.0 [1], so just for your information. > > > > > > Since I haven't completed checking this rc yet, it's possible that > there > > > are newly introduced dependencies in the paimon-filesystems module > > > (especially the paimon-s3 and paimon-s3-impl sub-modules). Would you > mind > > > further checking it and let us know the detailed dependency with > license > > > (notice/file) missing? Thanks. > > > > > > And I will also check this carefully when time allows. > > > > > > Best Regards, > > > Yu > > > > > > [1] > > > > https://github.com/apache/incubator-paimon/pull/1067#issuecomment-1537338118 > > > > > > On Tue, 28 Nov 2023 at 18:10, PJ Fanning wrote: > > > > > > > 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/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 are bundled > in > > > > > the jar. > > > > > > > > > > The META-INF/NOTICE likewise does not mention anything about the > > > > > non-ASF classes. > > > > > > > > > > > > > > > On Mon, 27 Nov 2023 at 04:04, Jingsong Li > > > > wrote: > > > > > > > > > > > > Hello Incubator PMC, > > > > > > > > > > > > The Apache Paimon community has voted and approved the release of > > > > > > Apache Paimon(incubating) 0.6.0-incubating rc1. We now kindly > request > > > > > > the IPMC members review and vote for this release. > > > > > > > > > > > > Apache Paimon(incubating) is a streaming data lake platform that > > > > > > supports high-speed data ingestion, change data tracking and > efficient > > > > > > real-time analytics. > > > > > > > > > > > > Paimon community vote thread: > > > > > > > > > > > > https://lists.apache.org/thread/fvzljoyokvs0dp6d24wwvtgdmrczfb3j > > > > > > > > > > > > Vote result thread: > > > > > > > > > > > > https://lists.apache.org/thread/3gsgkk9n0mpmw98f7y2wyfog0pgc58xc > > > > > > > > > > > > The official Apache source release to be deployed to > dist.apache.org: > > > > > > > > > > > > > > > > > https://dist.apache.org/repos/dist/dev/incubator/paimon/paimon-0.6.0-incubating-rc1/ > > > > > > > > > > > > This source release has been signed with a PGP available here > (Apache > > > > > > ID: lzljs3620320): > > > > > > > > > > > > https://downloads.apache.org/inc
Re: [DISCUSS] HoraeDB proposal
>> 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 于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-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Pekko(incubating) Core 1.0.2-RC1
+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 showstopper for this release.
[X] No unexpected binary files
I didn't do an exhaustive check
[X] Source files have ASF headers
[-] Can compile from source
I ran "sbt compile" and "sbt package" but both had errors. A sample:
[error] bnd: Invalid value for Bundle-Version, HEAD+20231129-0950
does not match [0-9]{1,9}(\.[0-9]{1,9}(\.[0-9]{1,9}(\.[0-9A-Za-z_-]+)?)?)?
[error] java.util.zip.ZipException: duplicate entry: META-INF/MANIFEST.MF
...
[error]
D:\tmp\pekko102\apache-pekko-1.0.2-incubating-src-20231115\actor\src\main\java\org\apache\pekko\util\Unsafe.java:25:23:
not found: value sun
[error] public static final sun.misc.Unsafe instance;
[error] ^
I rarely run sbt, so this could easily be my local setup. I didn't
try my linux box. Maybe it would have worked there.
I also tested the artifacts in the staging repo with a simple typed
actors example in Groovy:
https://github.com/paulk-asert/groovy-pekko-gpars/tree/main/src/main/groovy/pekko
I used Groovy 4.0.15, the 1.0.2-RC1 artifacts and the Scala 2.13 runtime.
It ran without problems.
Cheers, Paul.
On Sat, Nov 18, 2023 at 11:56 PM PJ Fanning wrote:
>
> Hello Incubator Community,
>
> This is a call for a vote to release Apache Pekko(incubating)
> Core version 1.0.2-RC1.
>
> The discussion thread:
> https://lists.apache.org/thread/zy84yk5gxp54bkn81ntlj5ps5o2z9w4j
>
> Pekko Vote Thread
> https://lists.apache.org/thread/0ojxypkm650bhk6pf53cp7h8036jgyol
>
> Pekko Result:
> https://lists.apache.org/thread/mh398gtjm751fq4fhss5c0xfwxnvx2xy
>
> The release candidate:
>
> https://dist.apache.org/repos/dist/dev/incubator/pekko/1.0.2-RC1/
>
> This release has been signed with a PGP key, available here:
>
> https://dist.apache.org/repos/dist/release/incubator/pekko/KEYS
>
> Git branch for the release:
>
> https://github.com/apache/incubator-pekko/tree/v1.0.2-RC1
> Git commit ID: 58fa510455190bd62d04f92a83c9506a7588d29c
>
> Release Notes:
>
> https://nightlies.apache.org/pekko/docs/pekko/1.0/docs/release-notes/index.html#1-0-2
>
> Please download, verify, and test.
>
> We have also staged jars in the Apache Nexus Repository. These were
> built with the same code
> as appears in this Source Release Candidate. We would appreciate if
> users could test with these too.
> If anyone finds any serious problems with these jars, please also
> notify us on this thread.
>
> https://repository.apache.org/content/groups/staging/org/apache/pekko/
>
> In sbt, you can add this resolver.
>
> resolvers += "Apache Pekko Staging" at
> "https://repository.apache.org/content/groups/staging";
>
>
> The vote will be left open for at least 72 hours.
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> To learn more about Apache Pekko, please see https://pekko.apache.org/
>
> Checklist for reference:
>
> [ ] Download links are valid.
> [ ] Checksums and signatures.
> [ ] LICENSE/NOTICE files exist
> [ ] No unexpected binary files
> [ ] Source files have ASF headers
> [ ] Can compile from source
>
> To compile from the source, please refer to:
>
> https://github.com/apache/incubator-pekko/blob/main/README.md#building-from-source
>
> Some notes about verifying downloads can be found at:
>
> https://pekko.apache.org/download.html#verifying-downloads
>
>
> Here is my +1 (binding).
>
> Thanks,
>
> PJ Fanning
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] HoraeDB proposal
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-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Pekko(incubating) Core 1.0.2-RC1
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, > PJ > > On 2023/11/24 13:05:48 Matthew de Detrich wrote: > > Carrying over my +1 from > > https://lists.apache.org/thread/skqfzys7g32b4f4hvlby3jjj2fcct261 > > > > Regards > > > > On Sat, Nov 18, 2023 at 2:56 PM PJ Fanning wrote: > > > > > Hello Incubator Community, > > > > > > This is a call for a vote to release Apache Pekko(incubating) > > > Core version 1.0.2-RC1. > > > > > > The discussion thread: > > > https://lists.apache.org/thread/zy84yk5gxp54bkn81ntlj5ps5o2z9w4j > > > > > > Pekko Vote Thread > > > https://lists.apache.org/thread/0ojxypkm650bhk6pf53cp7h8036jgyol > > > > > > Pekko Result: > > > https://lists.apache.org/thread/mh398gtjm751fq4fhss5c0xfwxnvx2xy > > > > > > The release candidate: > > > > > > https://dist.apache.org/repos/dist/dev/incubator/pekko/1.0.2-RC1/ > > > > > > This release has been signed with a PGP key, available here: > > > > > > https://dist.apache.org/repos/dist/release/incubator/pekko/KEYS > > > > > > Git branch for the release: > > > > > > https://github.com/apache/incubator-pekko/tree/v1.0.2-RC1 > > > Git commit ID: 58fa510455190bd62d04f92a83c9506a7588d29c > > > > > > Release Notes: > > > > > > > > > https://nightlies.apache.org/pekko/docs/pekko/1.0/docs/release-notes/index.html#1-0-2 > > > > > > Please download, verify, and test. > > > > > > We have also staged jars in the Apache Nexus Repository. These were > > > built with the same code > > > as appears in this Source Release Candidate. We would appreciate if > > > users could test with these too. > > > If anyone finds any serious problems with these jars, please also > > > notify us on this thread. > > > > > > https://repository.apache.org/content/groups/staging/org/apache/pekko/ > > > > > > In sbt, you can add this resolver. > > > > > > resolvers += "Apache Pekko Staging" at > > > "https://repository.apache.org/content/groups/staging"; > > > > > > > > > The vote will be left open for at least 72 hours. > > > > > > [ ] +1 approve > > > [ ] +0 no opinion > > > [ ] -1 disapprove with the reason > > > > > > To learn more about Apache Pekko, please see https://pekko.apache.org/ > > > > > > Checklist for reference: > > > > > > [ ] Download links are valid. > > > [ ] Checksums and signatures. > > > [ ] LICENSE/NOTICE files exist > > > [ ] No unexpected binary files > > > [ ] Source files have ASF headers > > > [ ] Can compile from source > > > > > > To compile from the source, please refer to: > > > > > > > > > https://github.com/apache/incubator-pekko/blob/main/README.md#building-from-source > > > > > > Some notes about verifying downloads can be found at: > > > > > > https://pekko.apache.org/download.html#verifying-downloads > > > > > > > > > Here is my +1 (binding). > > > > > > Thanks, > > > > > > PJ Fanning > > > > > > - > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > > > -- > > > > Matthew de Detrich > > > > *Aiven Deutschland GmbH* > > > > Immanuelkirchstraße 26, 10405 Berlin > > > > Alexanderufer 3-7, 10117 Berlin > > > > Amtsgericht Charlottenburg, HRB 209739 B > > > > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen > > > > *m:* +491603708037 > > > > *w:* aiven.io *e:* matthew.dedetr...@aiven.io > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Paimon(incubating) 0.6.0-incubating rc1
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/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 > level one is the one that is kept. > > On Tue, 28 Nov 2023 at 15:50, Yu Li wrote: > > > > 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: > > - > > > > This project bundles the following dependencies under BSD-2 License ( > > https://opensource.org/licenses/BSD-2-Clause). > > > > You find it under licenses/LICENSE.dnsjava. > > > > ... > > > > This project bundles the following dependencies under the MIT ( > > https://opensource.org/licenses/MIT) > > > > You find them under licenses/LICENSE.checker-framework-qualifiers and > > licenses/LICENSE.animal-sniffer. > > > > ... > > > > This project bundles the following dependencies under the CDDL 1.1 license. > > > > You find it under licenses/LICENSE.jaxb. > > > > ... > > - > > > > I happen to know this since I noticed similar issues and asked the team to > > resolve them in release 0.4.0 [1], so just for your information. > > > > Since I haven't completed checking this rc yet, it's possible that there > > are newly introduced dependencies in the paimon-filesystems module > > (especially the paimon-s3 and paimon-s3-impl sub-modules). Would you mind > > further checking it and let us know the detailed dependency with license > > (notice/file) missing? Thanks. > > > > And I will also check this carefully when time allows. > > > > Best Regards, > > Yu > > > > [1] > > https://github.com/apache/incubator-paimon/pull/1067#issuecomment-1537338118 > > > > On Tue, 28 Nov 2023 at 18:10, PJ Fanning wrote: > > > > > 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/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 are bundled in > > > > the jar. > > > > > > > > The META-INF/NOTICE likewise does not mention anything about the > > > > non-ASF classes. > > > > > > > > > > > > On Mon, 27 Nov 2023 at 04:04, Jingsong Li > > > wrote: > > > > > > > > > > Hello Incubator PMC, > > > > > > > > > > The Apache Paimon community has voted and approved the release of > > > > > Apache Paimon(incubating) 0.6.0-incubating rc1. We now kindly request > > > > > the IPMC members review and vote for this release. > > > > > > > > > > Apache Paimon(incubating) is a streaming data lake platform that > > > > > supports high-speed data ingestion, change data tracking and efficient > > > > > real-time analytics. > > > > > > > > > > Paimon community vote thread: > > > > > > > > > > https://lists.apache.org/thread/fvzljoyokvs0dp6d24wwvtgdmrczfb3j > > > > > > > > > > Vote result thread: > > > > > > > > > > https://lists.apache.org/thread/3gsgkk9n0mpmw98f7y2wyfog0pgc58xc > > > > > > > > > > The official Apache source release to be deployed to dist.apache.org: > > > > > > > > > > > > > https://dist.apache.org/repos/dist/dev/incubator/paimon/paimon-0.6.0-incubating-rc1/ > > > > > > > > > > This source release has been signed with a PGP available here (Apache > > > > > ID: lzljs3620320): > > > > > > > > > > https://downloads.apache.org/incubator/paimon/KEYS > > > > > > > > > > All artifacts to be deployed to the Maven Central Repository: > > > > > > > > > > > > > https://repository.apache.org/content/repositories/orgapachepaimon-1029/ > > > > > > > > > > Git branch for the release: > > > > > > > > > > > > > https://github.com/apache/incubator-paimon/tree/release-0.6.0-incubating-rc1 > > > > > > > > > > Please download, verify, and test. > > > > > > > > > > The VOTE will pass after 3 binding approve. > > > > > > > > > > [ ] +1 approve > > > > > [ ] +0 no opinion > > > > > [ ] -1 disapprove with the reason > > > > > > > > > > To learn more about apache paimon, please see > > > https://paimon.apache.org/ > > > > > > > > > > Checklist for reference: > > > > >
Re: [VOTE] Release Apache Paimon(incubating) 0.6.0-incubating rc1
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 level one is the one that is kept. On Tue, 28 Nov 2023 at 15:50, Yu Li wrote: > > 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: > - > > This project bundles the following dependencies under BSD-2 License ( > https://opensource.org/licenses/BSD-2-Clause). > > You find it under licenses/LICENSE.dnsjava. > > ... > > This project bundles the following dependencies under the MIT ( > https://opensource.org/licenses/MIT) > > You find them under licenses/LICENSE.checker-framework-qualifiers and > licenses/LICENSE.animal-sniffer. > > ... > > This project bundles the following dependencies under the CDDL 1.1 license. > > You find it under licenses/LICENSE.jaxb. > > ... > - > > I happen to know this since I noticed similar issues and asked the team to > resolve them in release 0.4.0 [1], so just for your information. > > Since I haven't completed checking this rc yet, it's possible that there > are newly introduced dependencies in the paimon-filesystems module > (especially the paimon-s3 and paimon-s3-impl sub-modules). Would you mind > further checking it and let us know the detailed dependency with license > (notice/file) missing? Thanks. > > And I will also check this carefully when time allows. > > Best Regards, > Yu > > [1] > https://github.com/apache/incubator-paimon/pull/1067#issuecomment-1537338118 > > On Tue, 28 Nov 2023 at 18:10, PJ Fanning wrote: > > > 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/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 are bundled in > > > the jar. > > > > > > The META-INF/NOTICE likewise does not mention anything about the > > > non-ASF classes. > > > > > > > > > On Mon, 27 Nov 2023 at 04:04, Jingsong Li > > wrote: > > > > > > > > Hello Incubator PMC, > > > > > > > > The Apache Paimon community has voted and approved the release of > > > > Apache Paimon(incubating) 0.6.0-incubating rc1. We now kindly request > > > > the IPMC members review and vote for this release. > > > > > > > > Apache Paimon(incubating) is a streaming data lake platform that > > > > supports high-speed data ingestion, change data tracking and efficient > > > > real-time analytics. > > > > > > > > Paimon community vote thread: > > > > > > > > https://lists.apache.org/thread/fvzljoyokvs0dp6d24wwvtgdmrczfb3j > > > > > > > > Vote result thread: > > > > > > > > https://lists.apache.org/thread/3gsgkk9n0mpmw98f7y2wyfog0pgc58xc > > > > > > > > The official Apache source release to be deployed to dist.apache.org: > > > > > > > > > > https://dist.apache.org/repos/dist/dev/incubator/paimon/paimon-0.6.0-incubating-rc1/ > > > > > > > > This source release has been signed with a PGP available here (Apache > > > > ID: lzljs3620320): > > > > > > > > https://downloads.apache.org/incubator/paimon/KEYS > > > > > > > > All artifacts to be deployed to the Maven Central Repository: > > > > > > > > > > https://repository.apache.org/content/repositories/orgapachepaimon-1029/ > > > > > > > > Git branch for the release: > > > > > > > > > > https://github.com/apache/incubator-paimon/tree/release-0.6.0-incubating-rc1 > > > > > > > > Please download, verify, and test. > > > > > > > > The VOTE will pass after 3 binding approve. > > > > > > > > [ ] +1 approve > > > > [ ] +0 no opinion > > > > [ ] -1 disapprove with the reason > > > > > > > > To learn more about apache paimon, please see > > https://paimon.apache.org/ > > > > > > > > Checklist for reference: > > > > > > > > [ ] Download links are valid. > > > > [ ] Checksums and signatures. > > > > [ ] LICENSE/NOTICE files exist > > > > [ ] No unexpected binary files > > > > [ ] All source files have ASF headers > > > > [ ] Can compile from source > > > > > > > > Best, > > > > Jingsong > > > > > > > > - > > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > > For additional commands, e-mail: general-h...@incubator.apache.org > > >
Re: [DISCUSS] HoraeDB proposal
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” 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 于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 > > > > 谭睿翔 于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 于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 于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'
Re: [DISCUSS] HoraeDB proposal
> “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 于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 > > 谭睿翔 于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 于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 于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 r
Re: [VOTE] Release Apache Paimon(incubating) 0.6.0-incubating rc1
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: - This project bundles the following dependencies under BSD-2 License ( https://opensource.org/licenses/BSD-2-Clause). You find it under licenses/LICENSE.dnsjava. ... This project bundles the following dependencies under the MIT ( https://opensource.org/licenses/MIT) You find them under licenses/LICENSE.checker-framework-qualifiers and licenses/LICENSE.animal-sniffer. ... This project bundles the following dependencies under the CDDL 1.1 license. You find it under licenses/LICENSE.jaxb. ... - I happen to know this since I noticed similar issues and asked the team to resolve them in release 0.4.0 [1], so just for your information. Since I haven't completed checking this rc yet, it's possible that there are newly introduced dependencies in the paimon-filesystems module (especially the paimon-s3 and paimon-s3-impl sub-modules). Would you mind further checking it and let us know the detailed dependency with license (notice/file) missing? Thanks. And I will also check this carefully when time allows. Best Regards, Yu [1] https://github.com/apache/incubator-paimon/pull/1067#issuecomment-1537338118 On Tue, 28 Nov 2023 at 18:10, PJ Fanning wrote: > 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/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 are bundled in > > the jar. > > > > The META-INF/NOTICE likewise does not mention anything about the > > non-ASF classes. > > > > > > On Mon, 27 Nov 2023 at 04:04, Jingsong Li > wrote: > > > > > > Hello Incubator PMC, > > > > > > The Apache Paimon community has voted and approved the release of > > > Apache Paimon(incubating) 0.6.0-incubating rc1. We now kindly request > > > the IPMC members review and vote for this release. > > > > > > Apache Paimon(incubating) is a streaming data lake platform that > > > supports high-speed data ingestion, change data tracking and efficient > > > real-time analytics. > > > > > > Paimon community vote thread: > > > > > > https://lists.apache.org/thread/fvzljoyokvs0dp6d24wwvtgdmrczfb3j > > > > > > Vote result thread: > > > > > > https://lists.apache.org/thread/3gsgkk9n0mpmw98f7y2wyfog0pgc58xc > > > > > > The official Apache source release to be deployed to dist.apache.org: > > > > > > > https://dist.apache.org/repos/dist/dev/incubator/paimon/paimon-0.6.0-incubating-rc1/ > > > > > > This source release has been signed with a PGP available here (Apache > > > ID: lzljs3620320): > > > > > > https://downloads.apache.org/incubator/paimon/KEYS > > > > > > All artifacts to be deployed to the Maven Central Repository: > > > > > > > https://repository.apache.org/content/repositories/orgapachepaimon-1029/ > > > > > > Git branch for the release: > > > > > > > https://github.com/apache/incubator-paimon/tree/release-0.6.0-incubating-rc1 > > > > > > Please download, verify, and test. > > > > > > The VOTE will pass after 3 binding approve. > > > > > > [ ] +1 approve > > > [ ] +0 no opinion > > > [ ] -1 disapprove with the reason > > > > > > To learn more about apache paimon, please see > https://paimon.apache.org/ > > > > > > Checklist for reference: > > > > > > [ ] Download links are valid. > > > [ ] Checksums and signatures. > > > [ ] LICENSE/NOTICE files exist > > > [ ] No unexpected binary files > > > [ ] All source files have ASF headers > > > [ ] Can compile from source > > > > > > Best, > > > Jingsong > > > > > > - > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [DISCUSS] HoraeDB proposal
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 谭睿翔 于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 于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 于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
Re: [VOTE] Release Apache Answer(Incubating) v1.2.0-RC1
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] 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 > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Answer(Incubating) v1.2.0-RC1
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
Re: [VOTE] Release Apache Answer(Incubating) v1.2.0-RC1
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 referred to there. Best, tison. [1] https://lists.apache.org/thread/08sjn6c96tr2kyztwr5k31gl0km6wghg tison 于2023年11月28日周二 21:01写道： > > 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 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.uber.org/mock/mockgen@latest; > > also, there is a warning fatal: not a git repository (or any of the > > parent directories): .git that may be improved. > > > > nit: You can use https://downloads.apache.org/incubator/answer/KEY > > instead of https://dist.apache.org/repos/dist/dev/incubator/answer/KEYS > > the next time (it should be there once you release the first version > > to https://dist.apache.org/repos/dist/release/incubator/answer) - See > > https://lists.apache.org/thread/g9040zdg0wk5sdl3ovxgnr86wgtr8m04 for > > reference. > > > > Best, > > tison. > > > > Christofer Dutz 于2023年11月28日周二 20:49写道： > > > > > > 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 Apache Answer(Incubating) v1.2.0-RC1 > > > +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. > > > > [OK] Verify the SHA512 hashes. > > > > [OK] Unzip the archive. > > > > [OK] Verify the existence of LICENSE, NOTICE, DISCLAIMER, README files > > > > in > > > > the extracted source bundle. > > > > [OK] Verify the content of LICENSE, NOTICE, DISCLAIMER, README files in > > > > the extracted source bundle. > > > > > > > > * No WIP disclaimer, doing full checks. > > > > [OK] Run RAT externally to ensure there are no surprises. > > > > [OK] Search for Copyright references, and if they are in headers, make > > > > sure these files containing them are mentioned in the LICENSE file. > > > > [SKIPPED] Build the project according to the information in the > > > > README.md > > > > file. > > > > - No guides on how to build the project > > > > > > > > > > > > Von: Justin Mclean > > > > Datum: Sonntag, 19. November 2023 um 22:46 > > > > An: incubator general apache > > > > Betreff: Re: [VOTE] Release Apache Answer(Incubating) v1.2.0-RC1 > > > > Hi, > > > > > > > > +1 (binding) - carrying over my vote from the dev list. > > > > > > > > Kind Regards, > > > > Justin > > > > > > > > - > > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Answer(Incubating) v1.2.0-RC1
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 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.uber.org/mock/mockgen@latest; > also, there is a warning fatal: not a git repository (or any of the > parent directories): .git that may be improved. > > nit: You can use https://downloads.apache.org/incubator/answer/KEY > instead of https://dist.apache.org/repos/dist/dev/incubator/answer/KEYS > the next time (it should be there once you release the first version > to https://dist.apache.org/repos/dist/release/incubator/answer) - See > https://lists.apache.org/thread/g9040zdg0wk5sdl3ovxgnr86wgtr8m04 for > reference. > > Best, > tison. > > Christofer Dutz 于2023年11月28日周二 20:49写道： > > > > 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 Apache Answer(Incubating) v1.2.0-RC1 > > +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. > > > [OK] Verify the SHA512 hashes. > > > [OK] Unzip the archive. > > > [OK] Verify the existence of LICENSE, NOTICE, DISCLAIMER, README files in > > > the extracted source bundle. > > > [OK] Verify the content of LICENSE, NOTICE, DISCLAIMER, README files in > > > the extracted source bundle. > > > > > > * No WIP disclaimer, doing full checks. > > > [OK] Run RAT externally to ensure there are no surprises. > > > [OK] Search for Copyright references, and if they are in headers, make > > > sure these files containing them are mentioned in the LICENSE file. > > > [SKIPPED] Build the project according to the information in the README.md > > > file. > > > - No guides on how to build the project > > > > > > > > > Von: Justin Mclean > > > Datum: Sonntag, 19. November 2023 um 22:46 > > > An: incubator general apache > > > Betreff: Re: [VOTE] Release Apache Answer(Incubating) v1.2.0-RC1 > > > Hi, > > > > > > +1 (binding) - carrying over my vote from the dev list. > > > > > > Kind Regards, > > > Justin > > > > > > - > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Answer(Incubating) v1.2.0-RC1
+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.uber.org/mock/mockgen@latest; also, there is a warning fatal: not a git repository (or any of the parent directories): .git that may be improved. nit: You can use https://downloads.apache.org/incubator/answer/KEY instead of https://dist.apache.org/repos/dist/dev/incubator/answer/KEYS the next time (it should be there once you release the first version to https://dist.apache.org/repos/dist/release/incubator/answer) - See https://lists.apache.org/thread/g9040zdg0wk5sdl3ovxgnr86wgtr8m04 for reference. Best, tison. Christofer Dutz 于2023年11月28日周二 20:49写道： > > 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 Apache Answer(Incubating) v1.2.0-RC1 > +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. > > [OK] Verify the SHA512 hashes. > > [OK] Unzip the archive. > > [OK] Verify the existence of LICENSE, NOTICE, DISCLAIMER, README files in > > the extracted source bundle. > > [OK] Verify the content of LICENSE, NOTICE, DISCLAIMER, README files in > > the extracted source bundle. > > > > * No WIP disclaimer, doing full checks. > > [OK] Run RAT externally to ensure there are no surprises. > > [OK] Search for Copyright references, and if they are in headers, make > > sure these files containing them are mentioned in the LICENSE file. > > [SKIPPED] Build the project according to the information in the README.md > > file. > > - No guides on how to build the project > > > > > > Von: Justin Mclean > > Datum: Sonntag, 19. November 2023 um 22:46 > > An: incubator general apache > > Betreff: Re: [VOTE] Release Apache Answer(Incubating) v1.2.0-RC1 > > Hi, > > > > +1 (binding) - carrying over my vote from the dev list. > > > > Kind Regards, > > Justin > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
AW: [VOTE] Release Apache Answer(Incubating) v1.2.0-RC1
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 Apache Answer(Incubating) v1.2.0-RC1 +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. > [OK] Verify the SHA512 hashes. > [OK] Unzip the archive. > [OK] Verify the existence of LICENSE, NOTICE, DISCLAIMER, README files in > the extracted source bundle. > [OK] Verify the content of LICENSE, NOTICE, DISCLAIMER, README files in > the extracted source bundle. > > * No WIP disclaimer, doing full checks. > [OK] Run RAT externally to ensure there are no surprises. > [OK] Search for Copyright references, and if they are in headers, make > sure these files containing them are mentioned in the LICENSE file. > [SKIPPED] Build the project according to the information in the README.md > file. > - No guides on how to build the project > > > Von: Justin Mclean > Datum: Sonntag, 19. November 2023 um 22:46 > An: incubator general apache > Betreff: Re: [VOTE] Release Apache Answer(Incubating) v1.2.0-RC1 > Hi, > > +1 (binding) - carrying over my vote from the dev list. > > Kind Regards, > Justin > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org >
Re: [DISCUSS] HoraeDB proposal
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 于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 于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 于2023年11月28日周二 18:27写道： > > > > > > On Tue, Nov 28, 2023 at 12:12 PM Justin Mclean < > jus...@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-unsubscr...@incubator.apache.org > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > >
Re: [DISCUSS] HoraeDB proposal
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 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 于2023年11月28日周二 18:27写道： > > > > 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 > 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-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > >
Re: [DISCUSS] HoraeDB proposal
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 于2023年11月28日周二 18:27写道： > > 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 > > 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-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] HoraeDB proposal
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-mail: general-h...@incubator.apache.org
Re: [DISCUSS] HoraeDB proposal
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...@apache.org Apache Kylin FAQ: https://kylin.apache.org/docs/gettingstarted/faq.html Join Kylin user mail group: user-subscr...@kylin.apache.org Join Kylin dev mail group: dev-subscr...@kylin.apache.org tison 于2023年11月28日周二 09:13写道： > 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 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-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > >
Re: [DISCUSS] HoraeDB proposal
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-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] HoraeDB proposal
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 > 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-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] HoraeDB proposal
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 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 于2023年11月28日周二 09:12写道： >> >> Perhaps think of an analogy with Docker vs. Moby? >> >> Justin Mclean 于2023年11月28日 周二07:15写道： >>> >>> HI, >>> This is included in the proposal: Since Ant Group wants to 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-unsubscr...@incubator.apache.org >>> For additional commands, e-mail: general-h...@incubator.apache.org >>> > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Paimon(incubating) 0.6.0-incubating rc1
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/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 are bundled in > the jar. > > The META-INF/NOTICE likewise does not mention anything about the > non-ASF classes. > > > On Mon, 27 Nov 2023 at 04:04, Jingsong Li wrote: > > > > Hello Incubator PMC, > > > > The Apache Paimon community has voted and approved the release of > > Apache Paimon(incubating) 0.6.0-incubating rc1. We now kindly request > > the IPMC members review and vote for this release. > > > > Apache Paimon(incubating) is a streaming data lake platform that > > supports high-speed data ingestion, change data tracking and efficient > > real-time analytics. > > > > Paimon community vote thread: > > > > https://lists.apache.org/thread/fvzljoyokvs0dp6d24wwvtgdmrczfb3j > > > > Vote result thread: > > > > https://lists.apache.org/thread/3gsgkk9n0mpmw98f7y2wyfog0pgc58xc > > > > The official Apache source release to be deployed to dist.apache.org: > > > > https://dist.apache.org/repos/dist/dev/incubator/paimon/paimon-0.6.0-incubating-rc1/ > > > > This source release has been signed with a PGP available here (Apache > > ID: lzljs3620320): > > > > https://downloads.apache.org/incubator/paimon/KEYS > > > > All artifacts to be deployed to the Maven Central Repository: > > > > https://repository.apache.org/content/repositories/orgapachepaimon-1029/ > > > > Git branch for the release: > > > > https://github.com/apache/incubator-paimon/tree/release-0.6.0-incubating-rc1 > > > > Please download, verify, and test. > > > > The VOTE will pass after 3 binding approve. > > > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove with the reason > > > > To learn more about apache paimon, please see https://paimon.apache.org/ > > > > Checklist for reference: > > > > [ ] Download links are valid. > > [ ] Checksums and signatures. > > [ ] LICENSE/NOTICE files exist > > [ ] No unexpected binary files > > [ ] All source files have ASF headers > > [ ] Can compile from source > > > > Best, > > Jingsong > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Paimon(incubating) 0.6.0-incubating rc1
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 are bundled in the jar. The META-INF/NOTICE likewise does not mention anything about the non-ASF classes. On Mon, 27 Nov 2023 at 04:04, Jingsong Li wrote: > > Hello Incubator PMC, > > The Apache Paimon community has voted and approved the release of > Apache Paimon(incubating) 0.6.0-incubating rc1. We now kindly request > the IPMC members review and vote for this release. > > Apache Paimon(incubating) is a streaming data lake platform that > supports high-speed data ingestion, change data tracking and efficient > real-time analytics. > > Paimon community vote thread: > > https://lists.apache.org/thread/fvzljoyokvs0dp6d24wwvtgdmrczfb3j > > Vote result thread: > > https://lists.apache.org/thread/3gsgkk9n0mpmw98f7y2wyfog0pgc58xc > > The official Apache source release to be deployed to dist.apache.org: > > https://dist.apache.org/repos/dist/dev/incubator/paimon/paimon-0.6.0-incubating-rc1/ > > This source release has been signed with a PGP available here (Apache > ID: lzljs3620320): > > https://downloads.apache.org/incubator/paimon/KEYS > > All artifacts to be deployed to the Maven Central Repository: > > https://repository.apache.org/content/repositories/orgapachepaimon-1029/ > > Git branch for the release: > > https://github.com/apache/incubator-paimon/tree/release-0.6.0-incubating-rc1 > > Please download, verify, and test. > > The VOTE will pass after 3 binding approve. > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove with the reason > > To learn more about apache paimon, please see https://paimon.apache.org/ > > Checklist for reference: > > [ ] Download links are valid. > [ ] Checksums and signatures. > [ ] LICENSE/NOTICE files exist > [ ] No unexpected binary files > [ ] All source files have ASF headers > [ ] Can compile from source > > Best, > Jingsong > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] HoraeDB proposal
> 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 于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 于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 于2023年11月28日周二 09:12写道： > > > > > > Perhaps think of an analogy with Docker vs. Moby? > > > > > > Justin Mclean 于2023年11月28日 周二07:15写道： > > >> > > >> HI, > > >> > > >> > This is included in the proposal: Since Ant Group wants to 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-unsubscr...@incubator.apache.org > > >> For additional commands, e-mail: general-h...@incubator.apache.org > > >> - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Answer(Incubating) v1.2.0-RC1
+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. > [OK] Verify the SHA512 hashes. > [OK] Unzip the archive. > [OK] Verify the existence of LICENSE, NOTICE, DISCLAIMER, README files in > the extracted source bundle. > [OK] Verify the content of LICENSE, NOTICE, DISCLAIMER, README files in > the extracted source bundle. > > * No WIP disclaimer, doing full checks. > [OK] Run RAT externally to ensure there are no surprises. > [OK] Search for Copyright references, and if they are in headers, make > sure these files containing them are mentioned in the LICENSE file. > [SKIPPED] Build the project according to the information in the README.md > file. > - No guides on how to build the project > > > Von: Justin Mclean > Datum: Sonntag, 19. November 2023 um 22:46 > An: incubator general apache > Betreff: Re: [VOTE] Release Apache Answer(Incubating) v1.2.0-RC1 > Hi, > > +1 (binding) - carrying over my vote from the dev list. > > Kind Regards, > Justin > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org >
Re: [DISCUSS] HoraeDB proposal
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 > 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 于2023年11月28日周二 09:12写道： > > > > Perhaps think of an analogy with Docker vs. Moby? > > > > Justin Mclean 于2023年11月28日 周二07:15写道： > >> > >> HI, > >> > >> > This is included in the proposal: Since Ant Group wants to 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-unsubscr...@incubator.apache.org > >> For additional commands, e-mail: general-h...@incubator.apache.org > >> - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] HoraeDB proposal
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 于2023年11月28日周二 09:12写道： > > Perhaps think of an analogy with Docker vs. Moby? > > Justin Mclean 于2023年11月28日 周二07:15写道： >> >> HI, >> >> > This is included in the proposal: Since Ant Group wants to 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-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
