Re: PMC is a committee
And, we can all be tired, overworked, or lazy and say the wrong
thing *or*
get into bad habits.
Thank John for your kindly understanding.
Also as a non-native English speaker, when I see abbreviation like
PMC,
my first insight is this word could be used on its own, `PMC
member` looks a little redundancy for me...
on Wed, Jul 03, 2024 at 08:50:45 AM +0800, John Gemignani wrote:
My 2 cents as being a PMC member and once part of incubation,...
To be honest, I've never really paid much attention when someone
stated
they're a PMC. I knew what was meant and just auto corrected it
in my head.
I have used, without fully thinking about it, PMC as, "I am a
PMC" as well.
When I meant, or should have meant, "I am a PMC member", and I'm
a native
English speaker.
As was mentioned, people from different cultures might have
different ways
of using a term like PMC. I just don't feel that getting upset
over,
arguably an innocuous misuse, engenders community.
And, we can all be tired, overworked, or lazy and say the wrong
thing *or*
get into bad habits.
Again, my 2 cents.
john
On Tue, Jul 2, 2024 at 5:33 PM Dave Fisher
wrote:
Hi Tison,
I’m sympathetic as well.
> On Jul 2, 2024, at 5:11 PM, tison
> wrote:
>
> Hi Greg,
>
> I saw this kind of thread many times, and I also corrected it
> dozens
> of times. Actually, this is part of the reason for [1]
> ("Maintainer"
> as an alias of PMC Member?).
>
> [1]
> https://lists.apache.org/thread/xsjojmksqtnsdjcg0yf4vz0xy82llhmw
That quickly turned into a not very sympathetic response from
most. An
easy what to name the Bikeshed. I think that most of our group
are people
whose second language is python, java, or fortran and their
first language
is some version of English.
>
> Somehow, I share the sympathy for non-native speakers to make
> an
> analogy between committer and "PMC" since they're all
> one-word
> phrases.
Maybe explain it from your perspective as a speaker of Mandarin
(or
Cantonese?). How does the phrase Committee Member translate
compared to
Committee.
Best,
Dave
>
> Best,
> tison.
>
> Greg Stein 于2024年7月2日周二 17:05写道：
>>
>> Hello all,
>>
>> I am getting really tired of seeing people refer to
>> *MEMBERS* of a PMC
as
>> "PMCs".
>>
>> PMC stands for Project Management Committee.
>>
>> You have MEMBERS of that PMC.
>>
>> People are never to be called a PMC, nor a group of them as
>> PMCs. People
>> are not committees. The acronym "PMC" is short for a
>> committee, not a
>> person.
>>
>> Please stop the confusion. Teach the community how to use
>> the proper
terms.
>>
>> Thanks,
>> Greg
>
> -
> 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
[VOTE] Release Apache HoraeDB(Incubating) rust client v2.0.0-rc.1
Hello, This is a call for a vote to release Apache HoraeDB(incubating) rust client version v2.0.0. The tag to be voted on is v2.0.0-rc.1 The vote thread: https://lists.apache.org/thread/yr6plq4176d5xyh1v0h2pjtgt61rkrb6 Vote Result: https://lists.apache.org/thread/nvnpxnbf96b7dj05lwdp9knv2d3wklws The release candidate: https://dist.apache.org/repos/dist/dev/incubator/horaedb/horaedb-rust-client/v2.0.0-rc.1/ Keys to verify the release candidate: https://downloads.apache.org/incubator/horaedb/KEYS Git tag for the release: https://github.com/apache/horaedb-client-rs/releases/tag/v2.0.0-rc.1 Git commit id for the release: https://github.com/apache/horaedb-client-rs/commit/c011a7ef4726272fe73026a96583d0271fce6f3d The vote will be open for at least 72 hours or until the necessary number of votes are reached. Please vote accordingly: [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove with the reason Checklist for reference: [ ] Download links are valid. [ ] Checksums and PGP signatures are valid. [ ] Source code distribution has correct names matching the current release. [ ] LICENSE/NOTICE files exist and are correct. [ ] No unexpected binary files bundled in the source archive. [ ] All source files have ASF headers. [ ] Can compile from source. Tips to verify the release, please refer to: https://github.com/apache/horaedb/wiki/ASF-review-guide How to Build HoraeDB Rust client, please refer to: https://horaedb.apache.org/dev/sdk_develop.html#rust Best, Jiacai Liu - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
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 commit
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
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
