Re: [DISCUSS] HoraeDB proposal
Hi,
Yingwen is one of the core early developers of the project, if you
execute `git grep yingwen`, you could see lots of comments written
by him.
However when we open source horaedb on GitHub, we do a git stash
to make the git history clean, so you couldn't see his commits
anymore.
Now he isn't working in AntGroup anymore, but since he contributed
significantly to the early stages of development, so we list him
under initial committers.
On Wed, Nov 29, 2023 at 06:13:42 PM +0800, Yu Xiao wrote:
Hi，
I checked the list of contributors[1], not find initial
Committers
for Yingwen Yang(GitHub ID = evenyag) .
[1] https://github.com/CeresDB/horaedb/graphs/contributors
Best wishes!
tison 于2023年11月29日周三 15:55写道：
> You also have things like this, which was published in the
> last day. If the name has changed,
> why is this still being published under the old name?
> https://github.com/CeresDB/horaedb/pkgs/container/ceresdb-server
If your cornern for asking permission for use CeresDB trademark
is due
to the existing usage, we can evaluate and choose either way:
1. Rename all the artifacts before entering the incubator.
2. Ask for Ant Group to grant a permission to use CeresDB
trademark
for such legacy code reference.
Does this make sense and your concern point?
Anyway, we will stop releasing new artifacts with the name
CeresDB as
prioritize the renaming task.
Best,
tison.
tison 于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: = "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
-
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
>> All of the changes don't need to happen before donation, just meantion how
>> they will be handled, but you do need to respect 3rd party trademarks.
I updated the "Initial Source" section to include the plan[1]. Briefly,
> Overall, all the occurrences except those associated with the org name,
> mainly GitHub address links and GitHub Pages links, will be renamed. Those
> associated with the org name will be modified once the transfer is finished.
... and the subtasks/progresses are tracked by [2].
>> Then why does the code in the code still refer to CeresDB in 100+ places?
I checked for github.com/CeresDB/horaedb,
93 matches for "github.com/CeresDB"
6 matches for "ceresdb.github.io"
3 matches for "docs.ceresdb.io"
1 match for "https://cla-assistant.io/CeresDB/ceresdb;
These will be changed once the repo transfer happens and the CLA
reference will be removed. It's >100 a little bit mainly due to
Cargo.lock and Golang import use "github.com/CeresDB/...".
So occ
Best,
tison.
[1] https://cwiki.apache.org/confluence/display/INCUBATOR/HoraeDB+Proposal
[2] https://github.com/CeresDB/horaedb/issues/1319
Yu Xiao 于2023年11月29日周三 18:14写道：
>
> Hi，
>
> I checked the list of contributors[1], not find initial Committers
> for Yingwen Yang(GitHub ID = evenyag) .
>
> [1] https://github.com/CeresDB/horaedb/graphs/contributors
>
> Best wishes!
>
> tison 于2023年11月29日周三 15:55写道：
> >
> > > You also have things like this, which was published in the last day. If
> > > the name has changed, why is this still being published under the old
> > > name?
> > > https://github.com/CeresDB/horaedb/pkgs/container/ceresdb-server
> >
> > If your cornern for asking permission for use CeresDB trademark is due
> > to the existing usage, we can evaluate and choose either way:
> >
> > 1. Rename all the artifacts before entering the incubator.
> > 2. Ask for Ant Group to grant a permission to use CeresDB trademark
> > for such legacy code reference.
> >
> > Does this make sense and your concern point?
> >
> > Anyway, we will stop releasing new artifacts with the name CeresDB as
> > prioritize the renaming task.
> >
> > Best,
> > tison.
> >
> > tison 于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: = "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
Re: [DISCUSS] HoraeDB proposal
Hi，
I checked the list of contributors[1], not find initial Committers
for Yingwen Yang(GitHub ID = evenyag) .
[1] https://github.com/CeresDB/horaedb/graphs/contributors
Best wishes!
tison 于2023年11月29日周三 15:55写道：
>
> > You also have things like this, which was published in the last day. If 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: = "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
>
-
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
On Wed, Nov 29, 2023 at 5:07 PM PJ Fanning wrote:
>
> 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.
Perhaps in the "building from source" doco, just add a note that the
build has minimal testing on Windows.
> The AddThis license comes from:
> https://github.com/addthis/stream-lib/blob/master/NOTICE.txt
Okay, fair enough. I guess an entity can have any name. :-)
> 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;
> > >
> > >
