Hi, tison
https://github.com/apache/incubator-seata-website/pull/872
Thank you for pointing out this issue, I have addressed it via the above PR and
improved the build instructions for macOS ARM platform in Seata official
documentation to prevent others from encountering the same issue.
On 2024/
Hi,PJ
Thanks for pointing out the license issue of existing codes, we will fix it
soon. And I have a question as below.
https://github.com/apache/incubator-seata/pull/1969
https://github.com/open-hand/hzero-starter-parent/commit/01b6dc0468d57f6c80d0624eeaad93504965be3b
According to the timeline of
Hi,Paul
Thank you for your suggestion, and I agree. We should wait for 72 hours. Even
if the final outcome does not result in a successful release, it will help us
identify more issues so that our next vote can proceed more smoothly and in
compliance with the regulations.
On 2024/07/07 00:49:56
> According to the timeline of above links, the _helpers.tpl in
hzero-starter-parent is copied from Seata. And the repo does not belong to
Seata community or any maintainer of Seata community, the repo is owned by
a third-party, we have no control of their behavior. And the copyright of
the file sh
OK, thanks for the suggestion, I'll try to do this.
Jianbin Chen, githubId: funky-eyes
tison 于 2024年7月7日周日 15:43写道：
> > According to the timeline of above links, the _helpers.tpl in
> hzero-starter-parent is copied from Seata. And the repo does not belong to
> Seata community or any maintainer
+1 (non-binding)
Looks interesting, It will be good, if it's extend to xtable( as I
see, it's currently only iceberg).,
On Wed, May 29, 2024 at 11:50 PM Venkat wrote:
>
> +1
>
> Venkat Ranganathan
>
>
> On Tue, May 28, 2024, 9:37 AM Uma Maheswara Rao Gangumalla <
> umaganguma...@gmail.com> wrot
> * You have MIT Licensed code but no mention of it in your LICENSE [1].
> One example [2] but there is another g4 file with the same header.
> * The LICENSE mentions BSD LIcense for Antlr and maybe this relates to
> these MIT Licensed files but this isn't clear
A little bit of confusion, hope to
https://github.com/antlr/grammars-v4/blob/master/sql/mysql/Positive-Technologies/MySqlLexer.g4
has an MIT License.
This must be mentioned in the Seata License.
On Sun, 7 Jul 2024 at 17:44, Min Ji wrote:
>
> > * You have MIT Licensed code but no mention of it in your LICENSE [1].
> > One example
Another case for stating oneself as PMC [1]
[1] https://www.linkedin.com/in/dannycranmer/
Although it may be interpreted as "I'm part of the PMC".
I refer it here to show how widely it's used "exchangeable" ..
Best,
tison.
Dave Fisher 于2024年7月3日周三 12:39写道：
>
>
> > On Jul 3, 2024, at 10:36 A
Hello Incubator Community,
This is a call for a vote to release Apache Uniffle (Incubating) version
0.9.0 RC2
The Apache Uniffle community has voted on and approved a proposal to release
Apache Uniffle (Incubating) version 0.9.0 RC2
We now kindly request the Incubator PMC members review and v
+1 binding
* Downloads ok
* checksums and signatures are valid
* no binaries
* LICENSE/NOTICE/DISCLAIMER ok
* Source headers ok
* maturin build failed on my Macbook
Caused by: Couldn't detect the binding type; Please specify them with
--bindings/-b
I'm no Rust expert but the build made some progr
HI,
> Looks interesting, It will be good, if it's extend to xtable( as I
> see, it's currently only iceberg).
No one that I know of is working on xtable integration, but as we’re now an ASF
incubating project anyone can propose and work on that.
Kind Regards,
Justin
+1 (binding)
I note that Uniffle is still using a DISCLAIMER-WIP and highlighting
that you have yet to complete the work to review the 3rd party source
that you use in Uniffle. It would be great if the PPMC could get
around to completing this work.
* Downloads ok
* src and bin tar.gz files have v
+1 binding
* Download link valid.
* Signature and checksum matches
apache-horaedb-incubating-rust-client-v2.0.0-src.tar.gz
gpg: Signature made 二 6/11 20:05:04 2024 PDT
gpg:using RSA key 6F734AE4297C7F62B6054F91D3026E5C08A0BAB4
gpg: Good signature from "jiacai2...@apache.org" [unk
+1 binding
- incubating in name
- signature and hash fine
- DISCLAIMER-WIP is fine
- LICENSE and NOTICE are fine
- No unexpected binary files
- All source files have ASF headers
- Did not compile from source
On Sun, Jul 7, 2024 at 5:04 PM PJ Fanning wrote:
> +1 (binding)
>
> I note that Uniffl
I have witnessed actual confusion, approximately of the form "a PMC
approved this request". Digging in, it turned out that it was a single
person on a PMC, not the committee approving the request.
So, no ... it isn't just being a pedant. And even if it was: why is it
wrong to correct the use of te
Greg
It isnt wrong to correct improper usage particularly when there is a
specific case that caused actual confusion.
That should be done by the person that was confused and with the person
that caused confusion.
Joe
On Sun, Jul 7, 2024 at 10:31 PM Greg Stein wrote:
> I have witnessed actual
Well, every time I see “PMC” and it appears from the context that one person is
meant, I’m confused, and I have doubts about whether the author knows what they
mean. I applaud Greg for complaining.
What’s wrong with “PMCM” for an individual?
David Jencks
Sent from my iPhone
> On Jul 7, 2024,
> What’s wrong with “PMCM” for an individual?
I'd second the proposal to simply encourage PMCM to be the abbr for PMC
members and spread it among the community. Or MPMC/MPPMC reads better to me
(XD)
Best,
tison.
David Jencks 于2024年7月7日周日 21:47写道：
> Well, every time I see “PMC” and it appears
19 matches
Mail list logo
