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 <wander4...@gmail.com> 于2023年11月29日周三 15:55写道:

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

If your cornern for asking permission for use CeresDB trademark is due
to the existing usage, we can evaluate and choose either way:

1. Rename all the artifacts before entering the incubator.
2. Ask for Ant Group to grant a permission to use CeresDB trademark
for such legacy code reference.

Does this make sense and your concern point?

Anyway, we will stop releasing new artifacts with the name CeresDB as
prioritize the renaming task.

Best,
tison.

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

Reply via email to