Re: [PROPOSAL] sparklyr

[申远]

You could also read the documentation[1] here about what license is allowed
in ASF project.

[1] https://apache.org/legal/resolved.html#category-a

Best Regards,
YorkShen

申远


申远  于2019年10月22日周二 下午2:49写道：

> Base on my experience (wearing my Apache Weex's hat),  GPL/LGPL dependency
> is not compatible with ASF's policy, and you may want to fix the License
> problem at the beginning, even before into Incubator. Otherwise, GPL/LGPL
> dependency will give you a lot of pain than you'd ever expect.
>
> Best Regards,
> YorkShen
>
> 申远
>
>
> Javier Luraschi  于2019年10月22日周二 上午2:55写道：
>
>> Regarding licenses, dplyr is under MIT, see:
>> https://github.com/tidyverse/dplyr/blob/master/LICENSE.md. However, other
>> packages are under GPL2.
>>
>> Here are all the packages that sparklyr currently depends on and their
>> associated license (This was retrieved from
>> https://CRAN.R-project.org/package=, since R package repo
>> (CRAN) requires their license to be clearly defined).
>>
>> assertthat: GPL-3
>> base64enc: GPL-2 | GPL-3
>> config: GPL-3
>> DBI: LGPL-2 | LGPL-2.1 | LGPL-3
>> dplyr: MIT
>> dbplyr: MIT
>> digest: GPL-2 | GPL-3
>> forge: Apache
>> generics: GPL-2
>> httr: MIT
>> jsonlite: MIT
>> openssl: MIT
>> purrr: GPL-3
>> r2d3: BSD-3
>> rappdirs: MIT
>> rlang: GPL-3
>> rprojroot: GPL-3
>> rstudioapi: MIT
>> tibble: MIT
>> tidyr: MIT
>> withr: GPL-2 | GPL-3
>> xml2: GPL-2 | GPL-3
>> ellipsis: GPL-3
>>
>>
>> On Mon, Oct 21, 2019 at 1:12 AM Justin Mclean 
>> wrote:
>>
>> > Hi,
>> >
>> > I also concerned that the initial committer list only contains 3
>> > committers. Why have you not included others in the community that have
>> > made contributions?
>> >
>> > I don’t know if this is an issue or not but bring it up just in case you
>> > not aware. I can see that some of the tidyverse packages are under GPL2,
>> > the GPL license is not compatible with the ALv2. I’m not 100% sure what
>> > license dplyr is under. I can see that sparkly depends on several (10+)
>> GPL
>> > licensed pieces of software. Do you see this causing any issue as GPL
>> code
>> > can’t be included in an Apache source release and can’t be a
>> non-optional
>> > dependancy of an ASF project. Have you discussed this with your
>> champion or
>> > proposed mentors and have they flagged this as a possible issue?
>> >
>> > I can see that one of the proposed mentors is not an IPMC member (which
>> is
>> > required) and another seems not very active in signing off reports or
>> > voting on releases. Did you think the existing mentors will provide your
>> > project with enough support?
>> >
>> > Thanks,
>> > Justin
>> >
>> > 1. https://github.com/tidyverse/dplyr/blob/master/LICENSE
>> > -
>> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> > For additional commands, e-mail: general-h...@incubator.apache.org
>> >
>> >
>>
>

Re: [PROPOSAL] sparklyr

[申远]

Base on my experience (wearing my Apache Weex's hat),  GPL/LGPL dependency
is not compatible with ASF's policy, and you may want to fix the License
problem at the beginning, even before into Incubator. Otherwise, GPL/LGPL
dependency will give you a lot of pain than you'd ever expect.

Best Regards,
YorkShen

申远


Javier Luraschi  于2019年10月22日周二 上午2:55写道：

> Regarding licenses, dplyr is under MIT, see:
> https://github.com/tidyverse/dplyr/blob/master/LICENSE.md. However, other
> packages are under GPL2.
>
> Here are all the packages that sparklyr currently depends on and their
> associated license (This was retrieved from
> https://CRAN.R-project.org/package=, since R package repo
> (CRAN) requires their license to be clearly defined).
>
> assertthat: GPL-3
> base64enc: GPL-2 | GPL-3
> config: GPL-3
> DBI: LGPL-2 | LGPL-2.1 | LGPL-3
> dplyr: MIT
> dbplyr: MIT
> digest: GPL-2 | GPL-3
> forge: Apache
> generics: GPL-2
> httr: MIT
> jsonlite: MIT
> openssl: MIT
> purrr: GPL-3
> r2d3: BSD-3
> rappdirs: MIT
> rlang: GPL-3
> rprojroot: GPL-3
> rstudioapi: MIT
> tibble: MIT
> tidyr: MIT
> withr: GPL-2 | GPL-3
> xml2: GPL-2 | GPL-3
> ellipsis: GPL-3
>
>
> On Mon, Oct 21, 2019 at 1:12 AM Justin Mclean 
> wrote:
>
> > Hi,
> >
> > I also concerned that the initial committer list only contains 3
> > committers. Why have you not included others in the community that have
> > made contributions?
> >
> > I don’t know if this is an issue or not but bring it up just in case you
> > not aware. I can see that some of the tidyverse packages are under GPL2,
> > the GPL license is not compatible with the ALv2. I’m not 100% sure what
> > license dplyr is under. I can see that sparkly depends on several (10+)
> GPL
> > licensed pieces of software. Do you see this causing any issue as GPL
> code
> > can’t be included in an Apache source release and can’t be a non-optional
> > dependancy of an ASF project. Have you discussed this with your champion
> or
> > proposed mentors and have they flagged this as a possible issue?
> >
> > I can see that one of the proposed mentors is not an IPMC member (which
> is
> > required) and another seems not very active in signing off reports or
> > voting on releases. Did you think the existing mentors will provide your
> > project with enough support?
> >
> > Thanks,
> > Justin
> >
> > 1. https://github.com/tidyverse/dplyr/blob/master/LICENSE
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [LAZY][VOTE] Release Apache IoTDB 0.8.1 (a bug-fix version of 0.8.0)

[Xiangdong Huang]

Hi,

Many thanks @Sheng Wu.

So, welcome all IPMCs voting on this thread for checking the release and
helping our incubator project better and better.

Best,
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


Sheng Wu  于2019年10月21日周一 下午5:34写道：

> Hi
> I think you just used the wrong word. (Not LAZY vote)
> I think you mean, you already have 3 +1 IPMC votes, so the vote could pass
> without a new vote.
>
> But in this release case. Other IPMC could find some new issues, and the +1
> you got could be changed to -1.
>
> Sheng Wu 吴晟
>
> Apache SkyWalking
> Apache Incubator
> Apache ShardingSphere, ECharts, DolphinScheduler podlings
> Zipkin
> Twitter, wusheng1108
>
>
> Xiangdong Huang  于2019年10月21日周一 下午6:31写道：
>
> > Hi,
> >
> > So do I need open a new vote? Or just vote on this thread?
> >
> > Best,
> >
> > Justin Mclean 于2019年10月21日 周一下午4:45写道：
> >
> > > Hi,
> > >
> > > Release votes can’t be lazy, all release must be approved by the IPMC
> to
> > > be an offical release.
> > >
> > > Thanks,
> > > Justin
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > > --
> > ---
> > Xiangdong Huang
> > School of Software, Tsinghua University
> >
> >  黄向东
> > 清华大学 软件学院
> >
>

Re: [DISCUSS] TubeMQ Proposal

[Ted Dunning]

JBO,

I agree with your curiosity, but maybe we should take it to another thread.
Comparison to Kafka or Pulsar or ... doesn't really affect the question of
incubation.



On Tue, Oct 22, 2019 at 5:41 AM Jean-Baptiste Onofré 
wrote:

> Hi,
>
> As soon as we have communities, there's no problem.
>
> I think it would just be interesting to have some details about why
> TubeMQ brings something different compare to existing MQ projects
> (Kafka, Pulsar, ActiveMQ, etc).
> The purpose is not to challenge projects each other but have better
> understanding of TubeMQ.
>
> Just my $0.01
>
> Regards
> JB
>
> On 21/10/2019 17:07, Sheng Wu wrote:
> > Hi
> >
> > I don't see the competition among different MQ solutions is an issue.
> This
> > happens among all OSS projects, inside or outside ASF.
> > We are using the Apache Way to help the project to build the community.
> > If(only if) it is not better than Kafka in all fields(an assumption
> only),
> > it will/could end with a lack of contributors/committers. But this should
> > not be a block for starting the incubating process.
> >
> > Sheng Wu 吴晟
> >
> > Apache SkyWalking
> > Apache Incubator
> > Apache ShardingSphere, ECharts, DolphinScheduler podlings
> > Zipkin
> > Twitter, wusheng1108
> >
> >
> > Justin Mclean  于2019年10月21日周一 下午5:31写道：
> >
> >> Hi,
> >>
> >>> The first one is if we are able to mentor the project well enough (old
> >> discussion).
> >>
> >> You might be right about that the project currently I believe there's
> only
> >> one mentor with recent mentoring experience, and while all proposed are
> ASF
> >> members, not all of them are active on the IPMC general list. It might
> be
> >> better for the project to have at least one other mentor with executive
> and
> >> is more active in the IPMC. What do others think?
> >>
> >>> As the project comes from Tencent I assume that the community is mostly
> >> Chinese and due to the language barrier (and probably a different
> culture)
> >> we have seen that these projects tend to be "more challenging" (this
> does
> >> not describe it accurate enough but I hope that readers understand what
> I
> >> mean).
> >>
> >> While projects in this group do have some challenges, I don’t believe
> it’s
> >> anymore than other projects from different background. In some ways the
> ASF
> >> model is a good cultural fit - see Sharan’s thesis on that.
> >>
> >> Thanks,
> >> Justin
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >>
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] TubeMQ Proposal

[Jean-Baptiste Onofré]

Hi,

As soon as we have communities, there's no problem.

I think it would just be interesting to have some details about why
TubeMQ brings something different compare to existing MQ projects
(Kafka, Pulsar, ActiveMQ, etc).
The purpose is not to challenge projects each other but have better
understanding of TubeMQ.

Just my $0.01

Regards
JB

On 21/10/2019 17:07, Sheng Wu wrote:
> Hi
> 
> I don't see the competition among different MQ solutions is an issue. This
> happens among all OSS projects, inside or outside ASF.
> We are using the Apache Way to help the project to build the community.
> If(only if) it is not better than Kafka in all fields(an assumption only),
> it will/could end with a lack of contributors/committers. But this should
> not be a block for starting the incubating process.
> 
> Sheng Wu 吴晟
> 
> Apache SkyWalking
> Apache Incubator
> Apache ShardingSphere, ECharts, DolphinScheduler podlings
> Zipkin
> Twitter, wusheng1108
> 
> 
> Justin Mclean  于2019年10月21日周一 下午5:31写道：
> 
>> Hi,
>>
>>> The first one is if we are able to mentor the project well enough (old
>> discussion).
>>
>> You might be right about that the project currently I believe there's only
>> one mentor with recent mentoring experience, and while all proposed are ASF
>> members, not all of them are active on the IPMC general list. It might be
>> better for the project to have at least one other mentor with executive and
>> is more active in the IPMC. What do others think?
>>
>>> As the project comes from Tencent I assume that the community is mostly
>> Chinese and due to the language barrier (and probably a different culture)
>> we have seen that these projects tend to be "more challenging" (this does
>> not describe it accurate enough but I hope that readers understand what I
>> mean).
>>
>> While projects in this group do have some challenges, I don’t believe it’s
>> anymore than other projects from different background. In some ways the ASF
>> model is a good cultural fit - see Sharan’s thesis on that.
>>
>> Thanks,
>> Justin
>>
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] TubeMQ Proposal

[Ming Wen]

Hi, this is an interesting proposal.

I think the competition among different MQ is not an issue for incubator
stage. Users and developers will have their own choices.

I guess that your challenges during the incubation:
expanding diversity (now committers come from one company),
and dealing with the relationship between the tencent internal version and
the open source version (I guess the two are not consistent, if I am wrong,
please correct me) .

Thanks,
Ming Wen
Twitter: _WenMing


Dave Fisher  于2019年10月22日周二 上午10:38写道：

> Hi -
>
> > On Oct 21, 2019, at 7:26 PM, 俊平堵  wrote:
> >
> > bq. You might be right about that the project currently I believe there's
> > only one mentor with recent mentoring experience, and while all proposed
> are
> > ASF members, not all of them are active on the IPMC general list. It
> might
> > be better for the project to have at least one other mentor with
> executive
> > and is more active in the IPMC. What do others think?
> > +1. Justin, do you have candidate to join the mentor team here?
>
> I’m on the Pulsar PMC with Sijie and know that he was also involved with
> DistributedLog which graduated into Bookkeeper. He will certainly be good
> help as a mentor.
>
> If Justin is good with this initial mix. I’m fine. If not then JBO has
> offered.
>
> Best wishes.
>
> Regards,
> Dave
>
> >
> > Thanks,
> >
> > Junping
> >
> > Justin Mclean  于2019年10月21日周一 下午10:31写道：
> >
> >> Hi,
> >>
> >>> The first one is if we are able to mentor the project well enough (old
> >> discussion).
> >>
> >> You might be right about that the project currently I believe there's
> only
> >> one mentor with recent mentoring experience, and while all proposed are
> ASF
> >> members, not all of them are active on the IPMC general list. It might
> be
> >> better for the project to have at least one other mentor with executive
> and
> >> is more active in the IPMC. What do others think?
> >>
> >>> As the project comes from Tencent I assume that the community is mostly
> >> Chinese and due to the language barrier (and probably a different
> culture)
> >> we have seen that these projects tend to be "more challenging" (this
> does
> >> not describe it accurate enough but I hope that readers understand what
> I
> >> mean).
> >>
> >> While projects in this group do have some challenges, I don’t believe
> it’s
> >> anymore than other projects from different background. In some ways the
> ASF
> >> model is a good cultural fit - see Sharan’s thesis on that.
> >>
> >> Thanks,
> >> 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 Weex (Incubating) 0.28.0-RC1

[Willem Jiang]

+1 （binding)

I checked the staged source and binary bundles.
- Hashes file and signature files are OK
- DISCLAIMER file is there
- LICENSE and NOTICE files are fine

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem


On Thu, Oct 17, 2019 at 8:34 PM 申远  wrote:
>
> Hi, folks
>
> The Apache Weex community has voted and approved the proposal to release
> Apache Weex (Incubating) version 0.28.0-RC1, we now kindly request the
> Incubator PMC members to review and vote on this incubator release.
>
>- Vote thread:
>
> https://lists.apache.org/thread.html/3b56f8ceb75981487de107c90995de27ebfa9ff9acfb0e16ca07cc55@%3Cdev.weex.apache.org%3E
>- Vote result thread:
>
> https://lists.apache.org/thread.html/7df08b9020fc11c0cb01b15faea16207cb791314ef993ab73a9b2721@%3Cdev.weex.apache.org%3
>
> 
>- Git tag for this Release:
>https://github.com/apache/incubator-weex/releases/tag/0.28.0-RC1
>- The source tarball could be found at :
>
> https://dist.apache.org/repos/dist/dev/incubator/weex/0.28.0/RC1/apache-weex-incubating-0.28.0-RC1-src.tar.gz
>- The signature of the source tarball could be found at :
>
> https://dist.apache.org/repos/dist/dev/incubator/weex/0.28.0/RC1/apache-weex-incubating-0.28.0-RC1-src.tar.gz.asc
>- The SHA-512 checksum of the source tarball could be found at :
>
> https://dist.apache.org/repos/dist/dev/incubator/weex/0.28.0/RC1/apache-weex-incubating-0.28.0-RC1-src.tar.gz.sha512
>- The source tarball is signed with
>Key:D7E6B58FFA293FB1AC9E7B624FD8BC09C7E9DB81, which could be found in the
>key file: https://dist.apache.org/repos/dist/release/incubator/weex/KEYS
>- ChangeLog about this version:
>https://github.com/apache/incubator-weex/blob/release/0.28/CHANGELOG.md
>
>
> One can build the binary from source according to
> https://github.com/apache/incubator-weex/blob/release/0.28/HOW-TO-BUILD.md
> with build environment installed.
>
> *FYI: I only test the build scripts on Mac environment, it should also work
> in Linux/Unit platform according to my understanding. But you may get
> problems if you try to build Weex from source on a windows platform.*
>
> This vote will remain open for at least 72 hours, until we get enough
> votes. Please vote on releasing this RC.
>
>-  +1 approve
>-  +0 no opinion
>-  -1 disapprove (and reason why)
>
>
> Best Regards,
> YorkShen
>
> 申远

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] TubeMQ Proposal

[Dave Fisher]

Hi -

> On Oct 21, 2019, at 7:26 PM, 俊平堵  wrote:
> 
> bq. You might be right about that the project currently I believe there's
> only one mentor with recent mentoring experience, and while all proposed are
> ASF members, not all of them are active on the IPMC general list. It might
> be better for the project to have at least one other mentor with executive
> and is more active in the IPMC. What do others think?
> +1. Justin, do you have candidate to join the mentor team here?

I’m on the Pulsar PMC with Sijie and know that he was also involved with 
DistributedLog which graduated into Bookkeeper. He will certainly be good help 
as a mentor.

If Justin is good with this initial mix. I’m fine. If not then JBO has offered.

Best wishes.

Regards,
Dave

> 
> Thanks,
> 
> Junping
> 
> Justin Mclean  于2019年10月21日周一 下午10:31写道：
> 
>> Hi,
>> 
>>> The first one is if we are able to mentor the project well enough (old
>> discussion).
>> 
>> You might be right about that the project currently I believe there's only
>> one mentor with recent mentoring experience, and while all proposed are ASF
>> members, not all of them are active on the IPMC general list. It might be
>> better for the project to have at least one other mentor with executive and
>> is more active in the IPMC. What do others think?
>> 
>>> As the project comes from Tencent I assume that the community is mostly
>> Chinese and due to the language barrier (and probably a different culture)
>> we have seen that these projects tend to be "more challenging" (this does
>> not describe it accurate enough but I hope that readers understand what I
>> mean).
>> 
>> While projects in this group do have some challenges, I don’t believe it’s
>> anymore than other projects from different background. In some ways the ASF
>> model is a good cultural fit - see Sharan’s thesis on that.
>> 
>> Thanks,
>> 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] TubeMQ Proposal

[俊平堵]

Agree. Just like we have different SQL engines in Apache (Hive, Impala,
SparkSQL, Hawq, etc.) - most of them are competitive but have different
design trade-offs and have successful user/developer community. It
shouldn't be a concern for project incubator stage.

Thanks,

Junping

Sheng Wu  于2019年10月21日周一 下午11:07写道：

> Hi
>
> I don't see the competition among different MQ solutions is an issue. This
> happens among all OSS projects, inside or outside ASF.
> We are using the Apache Way to help the project to build the community.
> If(only if) it is not better than Kafka in all fields(an assumption only),
> it will/could end with a lack of contributors/committers. But this should
> not be a block for starting the incubating process.
>
> Sheng Wu 吴晟
>
> Apache SkyWalking
> Apache Incubator
> Apache ShardingSphere, ECharts, DolphinScheduler podlings
> Zipkin
> Twitter, wusheng1108
>
>
> Justin Mclean  于2019年10月21日周一 下午5:31写道：
>
> > Hi,
> >
> > > The first one is if we are able to mentor the project well enough (old
> > discussion).
> >
> > You might be right about that the project currently I believe there's
> only
> > one mentor with recent mentoring experience, and while all proposed are
> ASF
> > members, not all of them are active on the IPMC general list. It might be
> > better for the project to have at least one other mentor with executive
> and
> > is more active in the IPMC. What do others think?
> >
> > > As the project comes from Tencent I assume that the community is mostly
> > Chinese and due to the language barrier (and probably a different
> culture)
> > we have seen that these projects tend to be "more challenging" (this does
> > not describe it accurate enough but I hope that readers understand what I
> > mean).
> >
> > While projects in this group do have some challenges, I don’t believe
> it’s
> > anymore than other projects from different background. In some ways the
> ASF
> > model is a good cultural fit - see Sharan’s thesis on that.
> >
> > Thanks,
> > Justin
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [DISCUSS] TubeMQ Proposal

[俊平堵]

bq. You might be right about that the project currently I believe there's
only one mentor with recent mentoring experience, and while all proposed are
ASF members, not all of them are active on the IPMC general list. It might
be better for the project to have at least one other mentor with executive
and is more active in the IPMC. What do others think?
+1. Justin, do you have candidate to join the mentor team here?

Thanks,

Junping

Justin Mclean  于2019年10月21日周一 下午10:31写道：

> Hi,
>
> > The first one is if we are able to mentor the project well enough (old
> discussion).
>
> You might be right about that the project currently I believe there's only
> one mentor with recent mentoring experience, and while all proposed are ASF
> members, not all of them are active on the IPMC general list. It might be
> better for the project to have at least one other mentor with executive and
> is more active in the IPMC. What do others think?
>
> > As the project comes from Tencent I assume that the community is mostly
> Chinese and due to the language barrier (and probably a different culture)
> we have seen that these projects tend to be "more challenging" (this does
> not describe it accurate enough but I hope that readers understand what I
> mean).
>
> While projects in this group do have some challenges, I don’t believe it’s
> anymore than other projects from different background. In some ways the ASF
> model is a good cultural fit - see Sharan’s thesis on that.
>
> Thanks,
> Justin
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [Vote] Release Apache Weex (Incubating) 0.28.0-RC1

[YorkShen]

Hi, Dave


> Consider adding exclusions for the two sets of files that are in the
> LICENSE file and shown as on-standard in the Rat check output.


This is something I want to fix long time ago, but I didn't find any
documentation about how to add exclusion for RAT.

FYI: I always execute RAT with the following command in my computer, so I
am a little confused about how to add exclusion rules for RAT, maybe adding
something like .gitignore file?

*java -jar apache-rat-0.12.jar $DIRECTORY*


Best Regards,
YorkShen

申远


Dave Fisher  于2019年10月22日周二 上午3:52写道：

> +1 (binding)
>
> Incubating in name
> Signature and Checksum are correct
> LICENSE is good
> NOTICE is good
> DISCLAIMER is good
> Rat check passes. Consider adding exclusions for the two sets of files
> that are in the LICENSE file and shown as on-standard in the Rat check
> output.
>
> Build did fail when it got to Android, but then I did not install an
> Android environment.
>
> Regards,
> Dave
>
> > On Oct 17, 2019, at 5:46 AM, YorkShen  wrote:
> >
> > Forget to send prvious email from Apache email account, sorry for that.
> But
> > let‘s continue voting.
> >
> > Best Regards,
> > YorkShen
> >
> > 申远
> >
> >
> > 申远  于2019年10月17日周四 下午8:33写道：
> >
> >> Hi, folks
> >>
> >> The Apache Weex community has voted and approved the proposal to release
> >> Apache Weex (Incubating) version 0.28.0-RC1, we now kindly request the
> >> Incubator PMC members to review and vote on this incubator release.
> >>
> >>   - Vote thread:
> >>
> https://lists.apache.org/thread.html/3b56f8ceb75981487de107c90995de27ebfa9ff9acfb0e16ca07cc55@%3Cdev.weex.apache.org%3E
> >>   - Vote result thread:
> >>
> https://lists.apache.org/thread.html/7df08b9020fc11c0cb01b15faea16207cb791314ef993ab73a9b2721@%3Cdev.weex.apache.org%3
> >>   <
> https://lists.apache.org/thread.html/7df08b9020fc11c0cb01b15faea16207cb791314ef993ab73a9b2721@%3Cdev.weex.apache.org%3E
> >
> >>   - Git tag for this Release:
> >>   https://github.com/apache/incubator-weex/releases/tag/0.28.0-RC1
> >>   - The source tarball could be found at :
> >>
> https://dist.apache.org/repos/dist/dev/incubator/weex/0.28.0/RC1/apache-weex-incubating-0.28.0-RC1-src.tar.gz
> >>   - The signature of the source tarball could be found at :
> >>
> https://dist.apache.org/repos/dist/dev/incubator/weex/0.28.0/RC1/apache-weex-incubating-0.28.0-RC1-src.tar.gz.asc
> >>   - The SHA-512 checksum of the source tarball could be found at :
> >>
> https://dist.apache.org/repos/dist/dev/incubator/weex/0.28.0/RC1/apache-weex-incubating-0.28.0-RC1-src.tar.gz.sha512
> >>   - The source tarball is signed with
> >>   Key:D7E6B58FFA293FB1AC9E7B624FD8BC09C7E9DB81, which could be found in
> the
> >>   key file:
> >>   https://dist.apache.org/repos/dist/release/incubator/weex/KEYS
> >>   - ChangeLog about this version:
> >>
> https://github.com/apache/incubator-weex/blob/release/0.28/CHANGELOG.md
> >>
> >>
> >> One can build the binary from source according to
> >>
> https://github.com/apache/incubator-weex/blob/release/0.28/HOW-TO-BUILD.md
> >> with build environment installed.
> >>
> >> *FYI: I only test the build scripts on Mac environment, it should also
> >> work in Linux/Unit platform according to my understanding. But you may
> get
> >> problems if you try to build Weex from source on a windows platform.*
> >>
> >> This vote will remain open for at least 72 hours, until we get enough
> >> votes. Please vote on releasing this RC.
> >>
> >>   -  +1 approve
> >>   -  +0 no opinion
> >>   -  -1 disapprove (and reason why)
> >>
> >>
> >> Best Regards,
> >> YorkShen
> >>
> >> 申远
> >>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] TubeMQ Proposal

[Dave Fisher]

Apache Pulsar is doing well and it is competing with Apache Kafka.

Regards,
Dave

Sent from my iPhone

> On Oct 21, 2019, at 3:10 PM, Matt Sicker  wrote:
> 
> Kafka is one of the most well known Apache projects right now; I don’t
> think that’s a fair comparison.
> 
>> On Mon, Oct 21, 2019 at 10:07, Sheng Wu  wrote:
>> 
>> Hi
>> 
>> I don't see the competition among different MQ solutions is an issue. This
>> happens among all OSS projects, inside or outside ASF.
>> We are using the Apache Way to help the project to build the community.
>> If(only if) it is not better than Kafka in all fields(an assumption only),
>> it will/could end with a lack of contributors/committers. But this should
>> not be a block for starting the incubating process.
>> 
>> Sheng Wu 吴晟
>> 
>> Apache SkyWalking
>> Apache Incubator
>> Apache ShardingSphere, ECharts, DolphinScheduler podlings
>> Zipkin
>> Twitter, wusheng1108
>> 
>> 
>> Justin Mclean  于2019年10月21日周一 下午5:31写道：
>> 
>>> Hi,
>>> 
 The first one is if we are able to mentor the project well enough (old
>>> discussion).
>>> 
>>> You might be right about that the project currently I believe there's
>> only
>>> one mentor with recent mentoring experience, and while all proposed are
>> ASF
>>> members, not all of them are active on the IPMC general list. It might be
>>> better for the project to have at least one other mentor with executive
>> and
>>> is more active in the IPMC. What do others think?
>>> 
 As the project comes from Tencent I assume that the community is mostly
>>> Chinese and due to the language barrier (and probably a different
>> culture)
>>> we have seen that these projects tend to be "more challenging" (this does
>>> not describe it accurate enough but I hope that readers understand what I
>>> mean).
>>> 
>>> While projects in this group do have some challenges, I don’t believe
>> it’s
>>> anymore than other projects from different background. In some ways the
>> ASF
>>> model is a good cultural fit - see Sharan’s thesis on that.
>>> 
>>> Thanks,
>>> Justin
>>> 
>>> 
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>> 
>>> 
>> 
> -- 
> Matt Sicker 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] TubeMQ Proposal

[Matt Sicker]

Kafka is one of the most well known Apache projects right now; I don’t
think that’s a fair comparison.

On Mon, Oct 21, 2019 at 10:07, Sheng Wu  wrote:

> Hi
>
> I don't see the competition among different MQ solutions is an issue. This
> happens among all OSS projects, inside or outside ASF.
> We are using the Apache Way to help the project to build the community.
> If(only if) it is not better than Kafka in all fields(an assumption only),
> it will/could end with a lack of contributors/committers. But this should
> not be a block for starting the incubating process.
>
> Sheng Wu 吴晟
>
> Apache SkyWalking
> Apache Incubator
> Apache ShardingSphere, ECharts, DolphinScheduler podlings
> Zipkin
> Twitter, wusheng1108
>
>
> Justin Mclean  于2019年10月21日周一 下午5:31写道：
>
> > Hi,
> >
> > > The first one is if we are able to mentor the project well enough (old
> > discussion).
> >
> > You might be right about that the project currently I believe there's
> only
> > one mentor with recent mentoring experience, and while all proposed are
> ASF
> > members, not all of them are active on the IPMC general list. It might be
> > better for the project to have at least one other mentor with executive
> and
> > is more active in the IPMC. What do others think?
> >
> > > As the project comes from Tencent I assume that the community is mostly
> > Chinese and due to the language barrier (and probably a different
> culture)
> > we have seen that these projects tend to be "more challenging" (this does
> > not describe it accurate enough but I hope that readers understand what I
> > mean).
> >
> > While projects in this group do have some challenges, I don’t believe
> it’s
> > anymore than other projects from different background. In some ways the
> ASF
> > model is a good cultural fit - see Sharan’s thesis on that.
> >
> > Thanks,
> > Justin
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>
-- 
Matt Sicker 

Re: [VOTE] Apache Hudi (incubating) 0.5.0 RC6

[Balaji Varadarajan]

Thanks Dave, The Release notes file is something we had added earlier before we 
started the incubation. We had looked at other incubating projects 
(incubator-gobblin, incubator-heron, ...)  and it did not look like a standard 
mandated.  Hence, we went ahead and removed as we have the current release 
notes from JIRA. But, we will check with our mentors too to see if this is 
necessary. 

Thanks,
Balaji.V


On 2019/10/21 21:30:34, Dave Fisher  wrote: 
> 
> 
> > On Oct 21, 2019, at 2:16 PM, Balaji Varadarajan  wrote:
> > 
> > Thanks Dave. I have addressed your comments related to Confluent packages 
> > and release notes in master with this PR : 
> > https://github.com/apache/incubator-hudi/pull/965
> > 
> > Balaji.V
> > 
> > On 2019/10/21 19:33:03, Dave Fisher  wrote: 
> >> +1 (binding)
> >> 
> >> Incubating in name
> >> Signature and Checksums Validated
> >> DISCLAIMER-WIP is present
> >> LICENSE is good
> >> NOTICE is good
> >> RatCheck confirms proper License Headers
> >> `mvn clean install` inferred as build from pom.xml
> >>This ought to be in the README.md since it runs for a very long time 
> >> and then failed at Hudi-cli where confluent sourced Kafka/avro 
> >> dependencies are not found. Please check to make sure that Confluent has 
> >> not moved these dependencies to “Open Core” - a non OpenSource license.
> >> 
> >> RELEASE_NOTES.md should probably not include author comments since author 
> >> claims can be stifling to new developers.
> 
> My suggestion was not to delete the release notes. It was to not have author 
> ids. This was a suggestion and you should discuss it with your Mentors on 
> your dev@ mailing list.
> 
> Regards,
> Dave
> 
> >> 
> >> Regards,
> >> Dave
> >> 
> >>> On Oct 19, 2019, at 3:04 PM, vbal...@apache.org wrote:
> >>> 
> >>> Dear IPMC,
> >>> 
> >>> Apache Hudi (incubating) (pronounced Hoodie) stands for Hadoop Upserts 
> >>> anD Incrementals. Apache Hudi (incubating) manages storage of large 
> >>> analytical datasets on DFS (Cloud stores, HDFS or any Hadoop FileSystem 
> >>> compatible storage) and provide ability to query them.
> >>> 
> >>> The previous source release candidate 0.5.0-incubating-rc5 had licensing 
> >>> concerns (Please see 
> >>> https://lists.apache.org/thread.html/02d40e3dbababc069c5210928aa4dd335c41ab1837d5a894954f5c9f@%3Cgeneral.incubator.apache.org%3E)
> >>>  .
> >>> 
> >>> We have addressed them in the new source release candidate (RC#6). The 
> >>> Apache Hudi (incubating) community has voted on this new release 
> >>> candidate and approved. The new source release candidate version is 
> >>> 0.5.0-incubating-rc6
> >>> 
> >>> Results: 4 binding +1 votes
> >>> 
> >>> Here is the voting thread:  
> >>> https://lists.apache.org/thread.html/617cad3116308821f845d3be5d71e135fdcbb82b4533c53941a0fda8@%3Cdev.hudi.apache.org%3E
> >>> Here is the voting result email:  
> >>> https://lists.apache.org/thread.html/1587f3d766f6b3536d32630f89ba53b86cb09178d744fce05ae93a03@%3Cdev.hudi.apache.org%3E
> >>> 
> >>> The Apache Hudi community had verified the following aspects of release:
> >>> - verified checksums and signatures [SUCCESS]
> >>> - license header check [SUCCESS]
> >>> - No binaries in source release [SUCCESS]
> >>> - verified RAT check [SUCCESS]
> >>> - built from source release (mvn clean install -DskipTests) [SUCCESS]
> >>> - mvn test from source release [SUCCESS]
> >>> 
> >>> I'd like to call a vote in general to approve the first release of Apache 
> >>> Hudi (incubating). Please review and vote on the release candidate #5 for 
> >>> the version 0.5.0, as follows:
> >>> [ ] +1,  Approve the release
> >>> [ ]  0,  I don't feel strongly about it, but I'm okay with the release
> >>> [ ] -1,  Do not approve the release (please provide specific comments)
> >>> 
> >>> 
> >>> The complete staging area is available for your review, which includes:
> >>> 
> >>> - JIRA release notes [1]
> >>> - The official Apache source release and binary convenience releases to 
> >>> be deployed to dist.apache.org [2], which are signed with the key with 
> >>> fingerprint AF9BAF79D311A3D3288E583F24A499037262AAA4  [3],
> >>> - all artifacts to be deployed to the Maven Central Repository [4]
> >>> - source code tag "release-0.5.0-incubating-rc6" [5]
> >>> 
> >>> [1]  
> >>> https://jira.apache.org/jira/secure/ReleaseNote.jspa?projectId=12322822&version=12346087
> >>> [2]  
> >>> https://dist.apache.org/repos/dist/dev/incubator/hudi/hudi-0.5.0-incubating-rc6/
> >>> [3]  https://dist.apache.org/repos/dist/release/incubator/hudi/KEYS
> >>> [4]  
> >>> https://repository.apache.org/content/repositories/orgapachehudi-1006/
> >>> [5]  
> >>> https://github.com/apache/incubator-hudi/tree/release-0.5.0-incubating-rc6
> >>> 
> >>> A release validation script is available in master for running usual 
> >>> checks. To run this
> >>> 
> >>> - git clone g...@github.com:apache/incubator-hudi.git
> >>> - cd incubator-hudi/scripts
> >>> - ./release/validate_staged_release.sh --rele

Re: [VOTE] Apache Hudi (incubating) 0.5.0 RC6

[Dave Fisher]

> On Oct 21, 2019, at 2:16 PM, Balaji Varadarajan  wrote:
> 
> Thanks Dave. I have addressed your comments related to Confluent packages and 
> release notes in master with this PR : 
> https://github.com/apache/incubator-hudi/pull/965
> 
> Balaji.V
> 
> On 2019/10/21 19:33:03, Dave Fisher  wrote: 
>> +1 (binding)
>> 
>> Incubating in name
>> Signature and Checksums Validated
>> DISCLAIMER-WIP is present
>> LICENSE is good
>> NOTICE is good
>> RatCheck confirms proper License Headers
>> `mvn clean install` inferred as build from pom.xml
>>  This ought to be in the README.md since it runs for a very long time 
>> and then failed at Hudi-cli where confluent sourced Kafka/avro dependencies 
>> are not found. Please check to make sure that Confluent has not moved these 
>> dependencies to “Open Core” - a non OpenSource license.
>> 
>> RELEASE_NOTES.md should probably not include author comments since author 
>> claims can be stifling to new developers.

My suggestion was not to delete the release notes. It was to not have author 
ids. This was a suggestion and you should discuss it with your Mentors on your 
dev@ mailing list.

Regards,
Dave

>> 
>> Regards,
>> Dave
>> 
>>> On Oct 19, 2019, at 3:04 PM, vbal...@apache.org wrote:
>>> 
>>> Dear IPMC,
>>> 
>>> Apache Hudi (incubating) (pronounced Hoodie) stands for Hadoop Upserts anD 
>>> Incrementals. Apache Hudi (incubating) manages storage of large analytical 
>>> datasets on DFS (Cloud stores, HDFS or any Hadoop FileSystem compatible 
>>> storage) and provide ability to query them.
>>> 
>>> The previous source release candidate 0.5.0-incubating-rc5 had licensing 
>>> concerns (Please see 
>>> https://lists.apache.org/thread.html/02d40e3dbababc069c5210928aa4dd335c41ab1837d5a894954f5c9f@%3Cgeneral.incubator.apache.org%3E)
>>>  .
>>> 
>>> We have addressed them in the new source release candidate (RC#6). The 
>>> Apache Hudi (incubating) community has voted on this new release candidate 
>>> and approved. The new source release candidate version is 
>>> 0.5.0-incubating-rc6
>>> 
>>> Results: 4 binding +1 votes
>>> 
>>> Here is the voting thread:  
>>> https://lists.apache.org/thread.html/617cad3116308821f845d3be5d71e135fdcbb82b4533c53941a0fda8@%3Cdev.hudi.apache.org%3E
>>> Here is the voting result email:  
>>> https://lists.apache.org/thread.html/1587f3d766f6b3536d32630f89ba53b86cb09178d744fce05ae93a03@%3Cdev.hudi.apache.org%3E
>>> 
>>> The Apache Hudi community had verified the following aspects of release:
>>> - verified checksums and signatures [SUCCESS]
>>> - license header check [SUCCESS]
>>> - No binaries in source release [SUCCESS]
>>> - verified RAT check [SUCCESS]
>>> - built from source release (mvn clean install -DskipTests) [SUCCESS]
>>> - mvn test from source release [SUCCESS]
>>> 
>>> I'd like to call a vote in general to approve the first release of Apache 
>>> Hudi (incubating). Please review and vote on the release candidate #5 for 
>>> the version 0.5.0, as follows:
>>> [ ] +1,  Approve the release
>>> [ ]  0,  I don't feel strongly about it, but I'm okay with the release
>>> [ ] -1,  Do not approve the release (please provide specific comments)
>>> 
>>> 
>>> The complete staging area is available for your review, which includes:
>>> 
>>> - JIRA release notes [1]
>>> - The official Apache source release and binary convenience releases to be 
>>> deployed to dist.apache.org [2], which are signed with the key with 
>>> fingerprint AF9BAF79D311A3D3288E583F24A499037262AAA4  [3],
>>> - all artifacts to be deployed to the Maven Central Repository [4]
>>> - source code tag "release-0.5.0-incubating-rc6" [5]
>>> 
>>> [1]  
>>> https://jira.apache.org/jira/secure/ReleaseNote.jspa?projectId=12322822&version=12346087
>>> [2]  
>>> https://dist.apache.org/repos/dist/dev/incubator/hudi/hudi-0.5.0-incubating-rc6/
>>> [3]  https://dist.apache.org/repos/dist/release/incubator/hudi/KEYS
>>> [4]  https://repository.apache.org/content/repositories/orgapachehudi-1006/
>>> [5]  
>>> https://github.com/apache/incubator-hudi/tree/release-0.5.0-incubating-rc6
>>> 
>>> A release validation script is available in master for running usual 
>>> checks. To run this
>>> 
>>> - git clone g...@github.com:apache/incubator-hudi.git
>>> - cd incubator-hudi/scripts
>>> - ./release/validate_staged_release.sh --release=0.5.0 --rc_num=6
>>> 
>>> The vote will be open for at least 72 hours. The vote will pass if a 
>>> majority of at least three +1 IPMC votes are cast
>>> 
>>> Thanks,
>>> Balaji.V
>>> (on behalf of Apache Hudi PPMC)
>>> 
>>> -
>>> 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] Apache Hudi (incubating) 0.5.0 RC6

[Balaji Varadarajan]

Thanks Dave. I have addressed your comments related to Confluent packages and 
release notes in master with this PR : 
https://github.com/apache/incubator-hudi/pull/965

Balaji.V

On 2019/10/21 19:33:03, Dave Fisher  wrote: 
> +1 (binding)
> 
> Incubating in name
> Signature and Checksums Validated
> DISCLAIMER-WIP is present
> LICENSE is good
> NOTICE is good
> RatCheck confirms proper License Headers
> `mvn clean install` inferred as build from pom.xml
>   This ought to be in the README.md since it runs for a very long time 
> and then failed at Hudi-cli where confluent sourced Kafka/avro dependencies 
> are not found. Please check to make sure that Confluent has not moved these 
> dependencies to “Open Core” - a non OpenSource license.
> 
> RELEASE_NOTES.md should probably not include author comments since author 
> claims can be stifling to new developers.
> 
> Regards,
> Dave
> 
> > On Oct 19, 2019, at 3:04 PM, vbal...@apache.org wrote:
> > 
> > Dear IPMC,
> > 
> > Apache Hudi (incubating) (pronounced Hoodie) stands for Hadoop Upserts anD 
> > Incrementals. Apache Hudi (incubating) manages storage of large analytical 
> > datasets on DFS (Cloud stores, HDFS or any Hadoop FileSystem compatible 
> > storage) and provide ability to query them.
> > 
> > The previous source release candidate 0.5.0-incubating-rc5 had licensing 
> > concerns (Please see 
> > https://lists.apache.org/thread.html/02d40e3dbababc069c5210928aa4dd335c41ab1837d5a894954f5c9f@%3Cgeneral.incubator.apache.org%3E)
> >  .
> > 
> > We have addressed them in the new source release candidate (RC#6). The 
> > Apache Hudi (incubating) community has voted on this new release candidate 
> > and approved. The new source release candidate version is 
> > 0.5.0-incubating-rc6
> > 
> > Results: 4 binding +1 votes
> > 
> > Here is the voting thread:  
> > https://lists.apache.org/thread.html/617cad3116308821f845d3be5d71e135fdcbb82b4533c53941a0fda8@%3Cdev.hudi.apache.org%3E
> > Here is the voting result email:  
> > https://lists.apache.org/thread.html/1587f3d766f6b3536d32630f89ba53b86cb09178d744fce05ae93a03@%3Cdev.hudi.apache.org%3E
> > 
> > The Apache Hudi community had verified the following aspects of release:
> > - verified checksums and signatures [SUCCESS]
> > - license header check [SUCCESS]
> > - No binaries in source release [SUCCESS]
> > - verified RAT check [SUCCESS]
> > - built from source release (mvn clean install -DskipTests) [SUCCESS]
> > - mvn test from source release [SUCCESS]
> > 
> > I'd like to call a vote in general to approve the first release of Apache 
> > Hudi (incubating). Please review and vote on the release candidate #5 for 
> > the version 0.5.0, as follows:
> > [ ] +1,  Approve the release
> > [ ]  0,  I don't feel strongly about it, but I'm okay with the release
> > [ ] -1,  Do not approve the release (please provide specific comments)
> > 
> > 
> > The complete staging area is available for your review, which includes:
> > 
> >  - JIRA release notes [1]
> >  - The official Apache source release and binary convenience releases to be 
> > deployed to dist.apache.org [2], which are signed with the key with 
> > fingerprint AF9BAF79D311A3D3288E583F24A499037262AAA4  [3],
> >  - all artifacts to be deployed to the Maven Central Repository [4]
> >  - source code tag "release-0.5.0-incubating-rc6" [5]
> > 
> >  [1]  
> > https://jira.apache.org/jira/secure/ReleaseNote.jspa?projectId=12322822&version=12346087
> >  [2]  
> > https://dist.apache.org/repos/dist/dev/incubator/hudi/hudi-0.5.0-incubating-rc6/
> >  [3]  https://dist.apache.org/repos/dist/release/incubator/hudi/KEYS
> >  [4]  https://repository.apache.org/content/repositories/orgapachehudi-1006/
> >  [5]  
> > https://github.com/apache/incubator-hudi/tree/release-0.5.0-incubating-rc6
> > 
> > A release validation script is available in master for running usual 
> > checks. To run this
> > 
> >  - git clone g...@github.com:apache/incubator-hudi.git
> >  - cd incubator-hudi/scripts
> >  - ./release/validate_staged_release.sh --release=0.5.0 --rc_num=6
> > 
> > The vote will be open for at least 72 hours. The vote will pass if a 
> > majority of at least three +1 IPMC votes are cast
> > 
> > Thanks,
> > Balaji.V
> > (on behalf of Apache Hudi PPMC)
> > 
> > -
> > 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 Weex (Incubating) 0.28.0-RC1

[Jan Piotrowski]

+1 looks good to me

Am Mo., 21. Okt. 2019 um 21:52 Uhr schrieb Dave Fisher :
>
> +1 (binding)
>
> Incubating in name
> Signature and Checksum are correct
> LICENSE is good
> NOTICE is good
> DISCLAIMER is good
> Rat check passes. Consider adding exclusions for the two sets of files that 
> are in the LICENSE file and shown as on-standard in the Rat check output.
>
> Build did fail when it got to Android, but then I did not install an Android 
> environment.
>
> Regards,
> Dave
>
> > On Oct 17, 2019, at 5:46 AM, YorkShen  wrote:
> >
> > Forget to send prvious email from Apache email account, sorry for that. But
> > let‘s continue voting.
> >
> > Best Regards,
> > YorkShen
> >
> > 申远
> >
> >
> > 申远  于2019年10月17日周四 下午8:33写道：
> >
> >> Hi, folks
> >>
> >> The Apache Weex community has voted and approved the proposal to release
> >> Apache Weex (Incubating) version 0.28.0-RC1, we now kindly request the
> >> Incubator PMC members to review and vote on this incubator release.
> >>
> >>   - Vote thread:
> >>   
> >> https://lists.apache.org/thread.html/3b56f8ceb75981487de107c90995de27ebfa9ff9acfb0e16ca07cc55@%3Cdev.weex.apache.org%3E
> >>   - Vote result thread:
> >>   
> >> https://lists.apache.org/thread.html/7df08b9020fc11c0cb01b15faea16207cb791314ef993ab73a9b2721@%3Cdev.weex.apache.org%3
> >>   
> >> 
> >>   - Git tag for this Release:
> >>   https://github.com/apache/incubator-weex/releases/tag/0.28.0-RC1
> >>   - The source tarball could be found at :
> >>   
> >> https://dist.apache.org/repos/dist/dev/incubator/weex/0.28.0/RC1/apache-weex-incubating-0.28.0-RC1-src.tar.gz
> >>   - The signature of the source tarball could be found at :
> >>   
> >> https://dist.apache.org/repos/dist/dev/incubator/weex/0.28.0/RC1/apache-weex-incubating-0.28.0-RC1-src.tar.gz.asc
> >>   - The SHA-512 checksum of the source tarball could be found at :
> >>   
> >> https://dist.apache.org/repos/dist/dev/incubator/weex/0.28.0/RC1/apache-weex-incubating-0.28.0-RC1-src.tar.gz.sha512
> >>   - The source tarball is signed with
> >>   Key:D7E6B58FFA293FB1AC9E7B624FD8BC09C7E9DB81, which could be found in the
> >>   key file:
> >>   https://dist.apache.org/repos/dist/release/incubator/weex/KEYS
> >>   - ChangeLog about this version:
> >>   https://github.com/apache/incubator-weex/blob/release/0.28/CHANGELOG.md
> >>
> >>
> >> One can build the binary from source according to
> >> https://github.com/apache/incubator-weex/blob/release/0.28/HOW-TO-BUILD.md
> >> with build environment installed.
> >>
> >> *FYI: I only test the build scripts on Mac environment, it should also
> >> work in Linux/Unit platform according to my understanding. But you may get
> >> problems if you try to build Weex from source on a windows platform.*
> >>
> >> This vote will remain open for at least 72 hours, until we get enough
> >> votes. Please vote on releasing this RC.
> >>
> >>   -  +1 approve
> >>   -  +0 no opinion
> >>   -  -1 disapprove (and reason why)
> >>
> >>
> >> Best Regards,
> >> YorkShen
> >>
> >> 申远
> >>
>
>
> -
> 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 Weex (Incubating) 0.28.0-RC1

[Dave Fisher]

+1 (binding)

Incubating in name
Signature and Checksum are correct
LICENSE is good
NOTICE is good
DISCLAIMER is good
Rat check passes. Consider adding exclusions for the two sets of files that are 
in the LICENSE file and shown as on-standard in the Rat check output.

Build did fail when it got to Android, but then I did not install an Android 
environment.

Regards,
Dave

> On Oct 17, 2019, at 5:46 AM, YorkShen  wrote:
> 
> Forget to send prvious email from Apache email account, sorry for that. But
> let‘s continue voting.
> 
> Best Regards,
> YorkShen
> 
> 申远
> 
> 
> 申远  于2019年10月17日周四 下午8:33写道：
> 
>> Hi, folks
>> 
>> The Apache Weex community has voted and approved the proposal to release
>> Apache Weex (Incubating) version 0.28.0-RC1, we now kindly request the
>> Incubator PMC members to review and vote on this incubator release.
>> 
>>   - Vote thread:
>>   
>> https://lists.apache.org/thread.html/3b56f8ceb75981487de107c90995de27ebfa9ff9acfb0e16ca07cc55@%3Cdev.weex.apache.org%3E
>>   - Vote result thread:
>>   
>> https://lists.apache.org/thread.html/7df08b9020fc11c0cb01b15faea16207cb791314ef993ab73a9b2721@%3Cdev.weex.apache.org%3
>>   
>> 
>>   - Git tag for this Release:
>>   https://github.com/apache/incubator-weex/releases/tag/0.28.0-RC1
>>   - The source tarball could be found at :
>>   
>> https://dist.apache.org/repos/dist/dev/incubator/weex/0.28.0/RC1/apache-weex-incubating-0.28.0-RC1-src.tar.gz
>>   - The signature of the source tarball could be found at :
>>   
>> https://dist.apache.org/repos/dist/dev/incubator/weex/0.28.0/RC1/apache-weex-incubating-0.28.0-RC1-src.tar.gz.asc
>>   - The SHA-512 checksum of the source tarball could be found at :
>>   
>> https://dist.apache.org/repos/dist/dev/incubator/weex/0.28.0/RC1/apache-weex-incubating-0.28.0-RC1-src.tar.gz.sha512
>>   - The source tarball is signed with
>>   Key:D7E6B58FFA293FB1AC9E7B624FD8BC09C7E9DB81, which could be found in the
>>   key file:
>>   https://dist.apache.org/repos/dist/release/incubator/weex/KEYS
>>   - ChangeLog about this version:
>>   https://github.com/apache/incubator-weex/blob/release/0.28/CHANGELOG.md
>> 
>> 
>> One can build the binary from source according to
>> https://github.com/apache/incubator-weex/blob/release/0.28/HOW-TO-BUILD.md
>> with build environment installed.
>> 
>> *FYI: I only test the build scripts on Mac environment, it should also
>> work in Linux/Unit platform according to my understanding. But you may get
>> problems if you try to build Weex from source on a windows platform.*
>> 
>> This vote will remain open for at least 72 hours, until we get enough
>> votes. Please vote on releasing this RC.
>> 
>>   -  +1 approve
>>   -  +0 no opinion
>>   -  -1 disapprove (and reason why)
>> 
>> 
>> Best Regards,
>> YorkShen
>> 
>> 申远
>> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Apache Hudi (incubating) 0.5.0 RC6

[Dave Fisher]

+1 (binding)

Incubating in name
Signature and Checksums Validated
DISCLAIMER-WIP is present
LICENSE is good
NOTICE is good
RatCheck confirms proper License Headers
`mvn clean install` inferred as build from pom.xml
This ought to be in the README.md since it runs for a very long time 
and then failed at Hudi-cli where confluent sourced Kafka/avro dependencies are 
not found. Please check to make sure that Confluent has not moved these 
dependencies to “Open Core” - a non OpenSource license.

RELEASE_NOTES.md should probably not include author comments since author 
claims can be stifling to new developers.

Regards,
Dave

> On Oct 19, 2019, at 3:04 PM, vbal...@apache.org wrote:
> 
> Dear IPMC,
> 
> Apache Hudi (incubating) (pronounced Hoodie) stands for Hadoop Upserts anD 
> Incrementals. Apache Hudi (incubating) manages storage of large analytical 
> datasets on DFS (Cloud stores, HDFS or any Hadoop FileSystem compatible 
> storage) and provide ability to query them.
> 
> The previous source release candidate 0.5.0-incubating-rc5 had licensing 
> concerns (Please see 
> https://lists.apache.org/thread.html/02d40e3dbababc069c5210928aa4dd335c41ab1837d5a894954f5c9f@%3Cgeneral.incubator.apache.org%3E)
>  .
> 
> We have addressed them in the new source release candidate (RC#6). The Apache 
> Hudi (incubating) community has voted on this new release candidate and 
> approved. The new source release candidate version is 0.5.0-incubating-rc6
> 
> Results: 4 binding +1 votes
> 
> Here is the voting thread:  
> https://lists.apache.org/thread.html/617cad3116308821f845d3be5d71e135fdcbb82b4533c53941a0fda8@%3Cdev.hudi.apache.org%3E
> Here is the voting result email:  
> https://lists.apache.org/thread.html/1587f3d766f6b3536d32630f89ba53b86cb09178d744fce05ae93a03@%3Cdev.hudi.apache.org%3E
> 
> The Apache Hudi community had verified the following aspects of release:
> - verified checksums and signatures [SUCCESS]
> - license header check [SUCCESS]
> - No binaries in source release [SUCCESS]
> - verified RAT check [SUCCESS]
> - built from source release (mvn clean install -DskipTests) [SUCCESS]
> - mvn test from source release [SUCCESS]
> 
> I'd like to call a vote in general to approve the first release of Apache 
> Hudi (incubating). Please review and vote on the release candidate #5 for the 
> version 0.5.0, as follows:
> [ ] +1,  Approve the release
> [ ]  0,  I don't feel strongly about it, but I'm okay with the release
> [ ] -1,  Do not approve the release (please provide specific comments)
> 
> 
> The complete staging area is available for your review, which includes:
> 
>  - JIRA release notes [1]
>  - The official Apache source release and binary convenience releases to be 
> deployed to dist.apache.org [2], which are signed with the key with 
> fingerprint AF9BAF79D311A3D3288E583F24A499037262AAA4  [3],
>  - all artifacts to be deployed to the Maven Central Repository [4]
>  - source code tag "release-0.5.0-incubating-rc6" [5]
> 
>  [1]  
> https://jira.apache.org/jira/secure/ReleaseNote.jspa?projectId=12322822&version=12346087
>  [2]  
> https://dist.apache.org/repos/dist/dev/incubator/hudi/hudi-0.5.0-incubating-rc6/
>  [3]  https://dist.apache.org/repos/dist/release/incubator/hudi/KEYS
>  [4]  https://repository.apache.org/content/repositories/orgapachehudi-1006/
>  [5]  
> https://github.com/apache/incubator-hudi/tree/release-0.5.0-incubating-rc6
> 
> A release validation script is available in master for running usual checks. 
> To run this
> 
>  - git clone g...@github.com:apache/incubator-hudi.git
>  - cd incubator-hudi/scripts
>  - ./release/validate_staged_release.sh --release=0.5.0 --rc_num=6
> 
> The vote will be open for at least 72 hours. The vote will pass if a majority 
> of at least three +1 IPMC votes are cast
> 
> Thanks,
> Balaji.V
> (on behalf of Apache Hudi PPMC)
> 
> -
> 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: [PROPOSAL] sparklyr

[Javier Luraschi]

Regarding licenses, dplyr is under MIT, see:
https://github.com/tidyverse/dplyr/blob/master/LICENSE.md. However, other
packages are under GPL2.

Here are all the packages that sparklyr currently depends on and their
associated license (This was retrieved from
https://CRAN.R-project.org/package=, since R package repo
(CRAN) requires their license to be clearly defined).

assertthat: GPL-3
base64enc: GPL-2 | GPL-3
config: GPL-3
DBI: LGPL-2 | LGPL-2.1 | LGPL-3
dplyr: MIT
dbplyr: MIT
digest: GPL-2 | GPL-3
forge: Apache
generics: GPL-2
httr: MIT
jsonlite: MIT
openssl: MIT
purrr: GPL-3
r2d3: BSD-3
rappdirs: MIT
rlang: GPL-3
rprojroot: GPL-3
rstudioapi: MIT
tibble: MIT
tidyr: MIT
withr: GPL-2 | GPL-3
xml2: GPL-2 | GPL-3
ellipsis: GPL-3


On Mon, Oct 21, 2019 at 1:12 AM Justin Mclean 
wrote:

> Hi,
>
> I also concerned that the initial committer list only contains 3
> committers. Why have you not included others in the community that have
> made contributions?
>
> I don’t know if this is an issue or not but bring it up just in case you
> not aware. I can see that some of the tidyverse packages are under GPL2,
> the GPL license is not compatible with the ALv2. I’m not 100% sure what
> license dplyr is under. I can see that sparkly depends on several (10+) GPL
> licensed pieces of software. Do you see this causing any issue as GPL code
> can’t be included in an Apache source release and can’t be a non-optional
> dependancy of an ASF project. Have you discussed this with your champion or
> proposed mentors and have they flagged this as a possible issue?
>
> I can see that one of the proposed mentors is not an IPMC member (which is
> required) and another seems not very active in signing off reports or
> voting on releases. Did you think the existing mentors will provide your
> project with enough support?
>
> Thanks,
> Justin
>
> 1. https://github.com/tidyverse/dplyr/blob/master/LICENSE
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE} Apache Hudi (incubating) 0.5.0 RC6

[Thomas Weise]

+1 (binding)

(forward from dev@)

On Sat, Oct 19, 2019 at 3:04 PM  wrote:

> Dear IPMC,
>
> Apache Hudi (incubating) (pronounced Hoodie) stands for Hadoop Upserts anD
> Incrementals. Apache Hudi (incubating) manages storage of large analytical
> datasets on DFS (Cloud stores, HDFS or any Hadoop FileSystem compatible
> storage) and provide ability to query them.
>
> The previous source release candidate 0.5.0-incubating-rc5 had licensing
> concerns (Please see
> https://lists.apache.org/thread.html/02d40e3dbababc069c5210928aa4dd335c41ab1837d5a894954f5c9f@%3Cgeneral.incubator.apache.org%3E)
> .
>
> We have addressed them in the new source release candidate (RC#6). The
> Apache Hudi (incubating) community has voted on this new release candidate
> and approved. The new source release candidate version is
> 0.5.0-incubating-rc6
>
> Results: 4 binding +1 votes
>
> Here is the voting thread:
> https://lists.apache.org/thread.html/617cad3116308821f845d3be5d71e135fdcbb82b4533c53941a0fda8@%3Cdev.hudi.apache.org%3E
> Here is the voting result email:
> https://lists.apache.org/thread.html/1587f3d766f6b3536d32630f89ba53b86cb09178d744fce05ae93a03@%3Cdev.hudi.apache.org%3E
>
> The Apache Hudi community had verified the following aspects of release:
> - verified checksums and signatures [SUCCESS]
> - license header check [SUCCESS]
> - No binaries in source release [SUCCESS]
> - verified RAT check [SUCCESS]
> - built from source release (mvn clean install -DskipTests) [SUCCESS]
> - mvn test from source release [SUCCESS]
>
> I'd like to call a vote in general to approve the first release of Apache
> Hudi (incubating). Please review and vote on the release candidate #5 for
> the version 0.5.0, as follows:
> [ ] +1,  Approve the release
> [ ]  0,  I don't feel strongly about it, but I'm okay with the release
> [ ] -1,  Do not approve the release (please provide specific comments)
>
>
> The complete staging area is available for your review, which includes:
>
>   - JIRA release notes [1]
>   - The official Apache source release and binary convenience releases to
> be deployed to dist.apache.org [2], which are signed with the key with
> fingerprint AF9BAF79D311A3D3288E583F24A499037262AAA4  [3],
>   - all artifacts to be deployed to the Maven Central Repository [4]
>   - source code tag "release-0.5.0-incubating-rc6" [5]
>
>   [1]
> https://jira.apache.org/jira/secure/ReleaseNote.jspa?projectId=12322822&version=12346087
>   [2]
> https://dist.apache.org/repos/dist/dev/incubator/hudi/hudi-0.5.0-incubating-rc6/
>   [3]  https://dist.apache.org/repos/dist/release/incubator/hudi/KEYS
>   [4]
> https://repository.apache.org/content/repositories/orgapachehudi-1006/
>   [5]
> https://github.com/apache/incubator-hudi/tree/release-0.5.0-incubating-rc6
>
> A release validation script is available in master for running usual
> checks. To run this
>
>   - git clone g...@github.com:apache/incubator-hudi.git
>   - cd incubator-hudi/scripts
>   - ./release/validate_staged_release.sh --release=0.5.0 --rc_num=6
>
> The vote will be open for at least 72 hours. The vote will pass if a
> majority of at least three +1 IPMC votes are cast
>
> Thanks,
> Balaji.V
> (on behalf of Apache Hudi PPMC)
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [PROPOSAL] sparklyr

[larry mccay]

This looks interesting to me.
I would be willing to contribute, if you would like to add me to the
initial list of committers.


On Mon, Oct 21, 2019 at 10:50 AM Matt Sicker  wrote:

> A lot of core R libraries seem to be under GPL. If we build more R
> projects at Apache, it seems like we may need more Apache-licensed (or
> compatible) libraries in R.
>
> On Mon, 21 Oct 2019 at 03:12, Justin Mclean 
> wrote:
> >
> > Hi,
> >
> > I also concerned that the initial committer list only contains 3
> committers. Why have you not included others in the community that have
> made contributions?
> >
> > I don’t know if this is an issue or not but bring it up just in case you
> not aware. I can see that some of the tidyverse packages are under GPL2,
> the GPL license is not compatible with the ALv2. I’m not 100% sure what
> license dplyr is under. I can see that sparkly depends on several (10+) GPL
> licensed pieces of software. Do you see this causing any issue as GPL code
> can’t be included in an Apache source release and can’t be a non-optional
> dependancy of an ASF project. Have you discussed this with your champion or
> proposed mentors and have they flagged this as a possible issue?
> >
> > I can see that one of the proposed mentors is not an IPMC member (which
> is required) and another seems not very active in signing off reports or
> voting on releases. Did you think the existing mentors will provide your
> project with enough support?
> >
> > Thanks,
> > Justin
> >
> > 1. https://github.com/tidyverse/dplyr/blob/master/LICENSE
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
>
> --
> Matt Sicker 
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [LAZY][VOTE] Release Apache IoTDB 0.8.1 (a bug-fix version of 0.8.0)

[Sheng Wu]

Hi
I think you just used the wrong word. (Not LAZY vote)
I think you mean, you already have 3 +1 IPMC votes, so the vote could pass
without a new vote.

But in this release case. Other IPMC could find some new issues, and the +1
you got could be changed to -1.

Sheng Wu 吴晟

Apache SkyWalking
Apache Incubator
Apache ShardingSphere, ECharts, DolphinScheduler podlings
Zipkin
Twitter, wusheng1108


Xiangdong Huang  于2019年10月21日周一 下午6:31写道：

> Hi,
>
> So do I need open a new vote? Or just vote on this thread?
>
> Best,
>
> Justin Mclean 于2019年10月21日 周一下午4:45写道：
>
> > Hi,
> >
> > Release votes can’t be lazy, all release must be approved by the IPMC to
> > be an offical release.
> >
> > Thanks,
> > Justin
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> > --
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>

Re: [LAZY][VOTE] Release Apache IoTDB 0.8.1 (a bug-fix version of 0.8.0)

[Xiangdong Huang]

Hi,

So do I need open a new vote? Or just vote on this thread?

Best,

Justin Mclean 于2019年10月21日 周一下午4:45写道：

> Hi,
>
> Release votes can’t be lazy, all release must be approved by the IPMC to
> be an offical release.
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
> --
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院

Re: [DISCUSS] TubeMQ Proposal

[Sheng Wu]

Hi

I don't see the competition among different MQ solutions is an issue. This
happens among all OSS projects, inside or outside ASF.
We are using the Apache Way to help the project to build the community.
If(only if) it is not better than Kafka in all fields(an assumption only),
it will/could end with a lack of contributors/committers. But this should
not be a block for starting the incubating process.

Sheng Wu 吴晟

Apache SkyWalking
Apache Incubator
Apache ShardingSphere, ECharts, DolphinScheduler podlings
Zipkin
Twitter, wusheng1108


Justin Mclean  于2019年10月21日周一 下午5:31写道：

> Hi,
>
> > The first one is if we are able to mentor the project well enough (old
> discussion).
>
> You might be right about that the project currently I believe there's only
> one mentor with recent mentoring experience, and while all proposed are ASF
> members, not all of them are active on the IPMC general list. It might be
> better for the project to have at least one other mentor with executive and
> is more active in the IPMC. What do others think?
>
> > As the project comes from Tencent I assume that the community is mostly
> Chinese and due to the language barrier (and probably a different culture)
> we have seen that these projects tend to be "more challenging" (this does
> not describe it accurate enough but I hope that readers understand what I
> mean).
>
> While projects in this group do have some challenges, I don’t believe it’s
> anymore than other projects from different background. In some ways the ASF
> model is a good cultural fit - see Sharan’s thesis on that.
>
> Thanks,
> Justin
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [PROPOSAL] sparklyr

[Matt Sicker]

A lot of core R libraries seem to be under GPL. If we build more R
projects at Apache, it seems like we may need more Apache-licensed (or
compatible) libraries in R.

On Mon, 21 Oct 2019 at 03:12, Justin Mclean  wrote:
>
> Hi,
>
> I also concerned that the initial committer list only contains 3 committers. 
> Why have you not included others in the community that have made 
> contributions?
>
> I don’t know if this is an issue or not but bring it up just in case you not 
> aware. I can see that some of the tidyverse packages are under GPL2, the GPL 
> license is not compatible with the ALv2. I’m not 100% sure what license dplyr 
> is under. I can see that sparkly depends on several (10+) GPL licensed pieces 
> of software. Do you see this causing any issue as GPL code can’t be included 
> in an Apache source release and can’t be a non-optional dependancy of an ASF 
> project. Have you discussed this with your champion or proposed mentors and 
> have they flagged this as a possible issue?
>
> I can see that one of the proposed mentors is not an IPMC member (which is 
> required) and another seems not very active in signing off reports or voting 
> on releases. Did you think the existing mentors will provide your project 
> with enough support?
>
> Thanks,
> Justin
>
> 1. https://github.com/tidyverse/dplyr/blob/master/LICENSE
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>


-- 
Matt Sicker 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [LAZY][VOTE] Release Apache IoTDB 0.8.1 (a bug-fix version of 0.8.0)

[Justin Mclean]

Hi,

Release votes can’t be lazy, all release must be approved by the IPMC to be an 
offical release.

Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [LAZY][VOTE] Release Apache IoTDB 0.8.1 (a bug-fix version of 0.8.0)

[Willem Jiang]

+1 (binding).
Carrying my vote here.


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Mon, Oct 21, 2019 at 1:47 PM Xiangdong Huang  wrote:
>
> Hello all,
>
> This is a call for vote to release Apache IoTDB (Incubating) version 0.8.1,
> which is a bug-fix Release of 0.8.0 for the IoTDB Project.
>
> The Apache IoTDB community has voted on and approved a proposal to release
> Apache IoTDB (Incubating) version 0.8.1.
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Apache IoTDB (incubating) (Database for Internet of Things) is an
> integrated data management engine designed for timeseries data. It provides
> users with services for data collection, storage and analysis.
>
> IoTDB community vote and result thread:
> Result:
> https://lists.apache.org/thread.html/3773662919c65fb997322f7c1a5fd54560da079b912846ccb1a56b2e@%3Cdev.iotdb.apache.org%3E
>
> Vote:
> https://lists.apache.org/thread.html/0b2153f07af8f2a0f7ac13b8005c67f2d511bc30a9a2e20a461d60f4@%3Cdev.iotdb.apache.org%3E
> (and one vote is at
> https://lists.apache.org/thread.html/741fc778f75607d58f8e814c9f7297bcdc7098b96f65d4abd299da7e@%3Cdev.iotdb.apache.org%3E
> )
>
> The release candidates (RC3):
> https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.8.1/rc3
>
> Git tag for the release (RC3):
> https://github.com/apache/incubator-iotdb/releases/tag/release%2F0.8.1
>
> Hash for the release tag:
> 4b8d46f9861e12bbe4a1d952bede7c9293b90b46
>
> Release Notes:
> https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.8.1/rc3/RELEASE_NOTES.md
>
> The artifacts have been signed with Key : 2206EF8F64C35889, which can be
> found in the keys file:
> https://dist.apache.org/repos/dist/dev/incubator/iotdb/KEYS
>
> Look at here for how to verify this release candidate:
> https://cwiki.apache.org/confluence/display/IOTDB
> /Validating+a+staged+Release
>
> The vote will be open for at least 72 hours.
>
> From the PPMC Vote we cary over 3 binding IPMC Votes:
>
> +1 from Justin McLean,
> +1 from Christofer Dutz,
> +1 from Kevin A. McGrail
>
> Thus, I took the freedom to declare the Vote as Lazy as no futher positive
> votes are necessary and only a -1 Vote could cancel the vote.
>
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Best,
>
> Xiangdong Huang
> Apache IoTDB
>
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [Vote] Release Apache Weex (Incubating) 0.28.0-RC1

[Justin Mclean]

Hi,

It might help to use the subject like [VOTE] rather than [Vote] as I completely 
missed this.

Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] TubeMQ Proposal

[Justin Mclean]

Hi,

> The first one is if we are able to mentor the project well enough (old 
> discussion).

You might be right about that the project currently I believe there's only one 
mentor with recent mentoring experience, and while all proposed are ASF 
members, not all of them are active on the IPMC general list. It might be 
better for the project to have at least one other mentor with executive and is 
more active in the IPMC. What do others think?

> As the project comes from Tencent I assume that the community is mostly 
> Chinese and due to the language barrier (and probably a different culture) we 
> have seen that these projects tend to be "more challenging" (this does not 
> describe it accurate enough but I hope that readers understand what I mean).

While projects in this group do have some challenges, I don’t believe it’s 
anymore than other projects from different background. In some ways the ASF 
model is a good cultural fit - see Sharan’s thesis on that.

Thanks,
Justin


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [Vote] Release Apache Weex (Incubating) 0.28.0-RC1

[YorkShen]

Hi, community

I understood this is a very busy mailing list, and it's a little disturbing
to resend the same email as before. But I'm really appreciated if it's
possible for individuals from IPMC to vote on this thread.

*FYI: As we remove the bundling of JSC, the build speed of Weex Release
will be 5 to 10 times faster than before.*

Best Regards,
YorkShen

申远


YorkShen  于2019年10月17日周四 下午8:46写道：

> Forget to send prvious email from Apache email account, sorry for that.
> But let‘s continue voting.
>
> Best Regards,
> YorkShen
>
> 申远
>
>
> 申远  于2019年10月17日周四 下午8:33写道：
>
>> Hi, folks
>>
>> The Apache Weex community has voted and approved the proposal to release
>> Apache Weex (Incubating) version 0.28.0-RC1, we now kindly request the
>> Incubator PMC members to review and vote on this incubator release.
>>
>>- Vote thread:
>>
>> https://lists.apache.org/thread.html/3b56f8ceb75981487de107c90995de27ebfa9ff9acfb0e16ca07cc55@%3Cdev.weex.apache.org%3E
>>- Vote result thread:
>>
>> https://lists.apache.org/thread.html/7df08b9020fc11c0cb01b15faea16207cb791314ef993ab73a9b2721@%3Cdev.weex.apache.org%3
>>
>> 
>>- Git tag for this Release:
>>https://github.com/apache/incubator-weex/releases/tag/0.28.0-RC1
>>- The source tarball could be found at :
>>
>> https://dist.apache.org/repos/dist/dev/incubator/weex/0.28.0/RC1/apache-weex-incubating-0.28.0-RC1-src.tar.gz
>>- The signature of the source tarball could be found at :
>>
>> https://dist.apache.org/repos/dist/dev/incubator/weex/0.28.0/RC1/apache-weex-incubating-0.28.0-RC1-src.tar.gz.asc
>>- The SHA-512 checksum of the source tarball could be found at :
>>
>> https://dist.apache.org/repos/dist/dev/incubator/weex/0.28.0/RC1/apache-weex-incubating-0.28.0-RC1-src.tar.gz.sha512
>>- The source tarball is signed with
>>Key:D7E6B58FFA293FB1AC9E7B624FD8BC09C7E9DB81, which could be found in the
>>key file:
>>https://dist.apache.org/repos/dist/release/incubator/weex/KEYS
>>- ChangeLog about this version:
>>https://github.com/apache/incubator-weex/blob/release/0.28/CHANGELOG.md
>>
>>
>> One can build the binary from source according to
>> https://github.com/apache/incubator-weex/blob/release/0.28/HOW-TO-BUILD.md
>> with build environment installed.
>>
>> *FYI: I only test the build scripts on Mac environment, it should also
>> work in Linux/Unit platform according to my understanding. But you may get
>> problems if you try to build Weex from source on a windows platform.*
>>
>> This vote will remain open for at least 72 hours, until we get enough
>> votes. Please vote on releasing this RC.
>>
>>-  +1 approve
>>-  +0 no opinion
>>-  -1 disapprove (and reason why)
>>
>>
>> Best Regards,
>> YorkShen
>>
>> 申远
>>
>

Re: Leaving the incubator

[Justin Mclean]

Hi,
Just a lazy vote is fine with me.
Thanks,
Justin

On Mon, 21 Oct 2019, 14:03 Julian Feinauer, 
wrote:

> Hi all,
>
> as already discussed before the Podling Edgent is “too dead” to be revived.
> The PPMC has thus voted to leave the incubator [1,2] and we will move the
> project to GitHub, perhaps some interest will stay.
>
> What are the next (formal) steps. Do we hold a Vote for the IPMC?
>
> Thanks!
> Julian
>
> [1]
> https://lists.apache.org/thread.html/034c26b8c54a1467e2e2f5903c8b984b7037364e27aa36cd2c34794b@%3Cdev.edgent.apache.org%3E
> [2]
> https://lists.apache.org/thread.html/c1e4834fbee2634ed3dac8626739c00357ed427f261e3c4f678637c8@%3Cdev.edgent.apache.org%3E
>

Leaving the incubator

[Julian Feinauer]

Hi all,

as already discussed before the Podling Edgent is “too dead” to be revived.
The PPMC has thus voted to leave the incubator [1,2] and we will move the 
project to GitHub, perhaps some interest will stay.

What are the next (formal) steps. Do we hold a Vote for the IPMC?

Thanks!
Julian

[1] 
https://lists.apache.org/thread.html/034c26b8c54a1467e2e2f5903c8b984b7037364e27aa36cd2c34794b@%3Cdev.edgent.apache.org%3E
[2] 
https://lists.apache.org/thread.html/c1e4834fbee2634ed3dac8626739c00357ed427f261e3c4f678637c8@%3Cdev.edgent.apache.org%3E

Re: [DISCUSS] TubeMQ Proposal

[Jean-Baptiste Onofré]

Hi David,

Very interesting proposal.

How do you compare with Apache Kafka or Pulsar ?
It sounds to address the same use cases, right ?

I would be interested to be mentor on the proposal if you are looking
for an additional one.

Regards
JB

On 21/10/2019 11:54, David Nalley wrote:
> Greetings folks:
> 
> Please consider the following proposal, which is also on the wiki[1].
> I look forward to hearing feedback.
> 
> TubeMQ
> 
> =Abstract=
> 
> TubeMQ is a distributed messaging queue (MQ) system developed by
> Tencent Big Data since 2013. It focuses on high-performance storage
> and transmission of massive data in big data scenarios.After nearly
> seven years of massive data precipitation, TubeMQ has certain
> advantages in production practice (stability + performance) and low
> cost compared to many open source MQ projects.
> 
> =Proposal=
> 
> TubeMQ is suitable for high concurrency, massive data and tolerates a
> small amount of data loss scenarios under abnormal conditions, such as
> massive log collection, indicator statistics and monitoring, etc.
> TubeMQ does not support highly reliable data transmission services
> yet. It could be on a future project roadmap, as many other MQs. but
> not today.
> 
> =Rationale=
> 
> Just like other message queue systems, TubeMQ is built on the
> publish-subscribe pattern, aka pub-sub.
> In this pattern, producers publish messages to topics while consumers
> subscribe to those topics. After incoming messages get proceeded,
> consumers send an acknowledgement back to producer. Once a
> subscription has been created, all messages will be tracked and
> retained by TubeMQ, even if the consumer go offline for some reasons.
> Retained messages will be discarded only when a consumer acknowledges
> that they've been successfully processed.
> 
> Portal is responsible for interact with user and admin system which
> include two parts: API and web portal.
> 
> Master is controller of the cluster, which include one or multiple
> master node(s) which is responsible for managing state of cluster,
> resource scheduling, authentication check and maintaining of metadata.
> As a reliable system, TubeMQ provides HA solution for master node.
> 
> Broker is responsible for data store which include a cluster of broker
> nodes. Every broker node is managing a set of topics, include: append,
> delete, update, query of topic information. In TubeMQ, these brokers
> can be horizontal scaled and can be very large size for massive data
> case.
> 
> Client is responsible for producing and consuming messages. When a
> pub-sub topic get setup, we can support two ways (push and pull) for
> delivering message from producers to consumers.
> 
> Zookeeper is for storing offset of messages which is used to recover
> topic during some components get failed.
> 
> 
> =Initial Goals=
> 
> The initial goal will be to move the current codebase in github’s
> repository under Tencent account to Apache and integrate with the
> Apache development process and infrastructure.
> A primary goal of incubation will be to grow and diversify the TubeMQ
> community. We are well aware that the project community is largely
> comprised of individuals from a single company. We aim to change that
> during incubation.
> 
> =Current Status=
> 
> As previously mentioned, TubeMQ is under active development at
> Tencent, and is being used in processing large volumes of data for
> most services and products.
> 
> =Meritocracy=
> 
> We value meritocracy and we understand that it is the basis for an
> open community that encourages multiple companies and individuals to
> contribute and be invested in the project’s future. We will encourage
> and monitor participation and make sure to extend privileges and
> responsibilities to all contributors.
> 
> =Community=
> 
> TubeMQ is currently being used by developers at Tencent and a growing
> number of users are actively using it in production environments.
> TubeMQ has received contributions from developers working outside of
> Tencent since it was open sourced on github in September 2019 By
> bringing TubeMQ to Apache we aim to assure current and future
> contributors that the TubeMQ community is neutral, meritocratic, and
> open, in order to broaden and diversity the user and developer
> community.
> 
> =Core Developers=
> 
> TubeMQ was initially developed at Tencent and is under active
> development. We believe Tencent will be of interest to a broad range
> of users and developers and that incubating the project at the ASF
> will help us build a diverse, sustainable community.
> 
> =Alignment=
> 
> TubeMQ utilizes other Apache projects such as Hadoop, HBase and
> Zookeeper. We anticipate integration with additional Apache projects
> as the TubeMQ community and interest in the project grows.
> 
> =Known Risks=
> 
> ==Orphaned Products==
> 
> Tencent is committed to the future development of TubeMQ and
> understands that graduation to a TLP, while preferable, is not the
> only positive ou

Re: [DISCUSS] TubeMQ Proposal

[Julian Feinauer]

Hi David,

thanks for the nice proposal.
I think it was already introduced a bit at the ApacheCon NA so it may already 
be known a bit to some folks.
The proposal reads quite nice and TubeMQ seems to be a really nice project and 
has some impressive capabilities and USPs.

Although, those who know me know that I tend to be concerned a lot. The two 
main concerns I see here are not really related to the project in detail but 
rather to two general questions.

The first one is if we are able to mentor the project well enough (old 
discussion). As the project comes from Tencent I assume that the community is 
mostly Chinese and due to the language barrier (and probably a different 
culture) we have seen that these projects tend to be "more challenging" (this 
does not describe it accurate enough but I hope that readers understand what I 
mean).

Aside from that I have the impressions that Messaging and Pub/Sub is the new 
"JS Frontend" thing and we get new Projects each week. I am not too deep into 
the topic (only used Kafka and MQTT) but especially at the last ACNA I got the 
impression that Pulsar is doing a lot to catch up with Kafka and in our 
industrial environment MQTT is pretty set.
But overall we have many Messaging solutions in the ASF all with different 
aspects and USPs yes but overall also with tons of overlap. Which is bad then 
when it comes to "too much" competition and brain-split.

So maybe for someone deeply involved in the field my concerns sound 
unreasonable but this is the impression I have. And I don’t know if we already 
had such a situation but as the foundation is kind of the "bracket" which keeps 
all projects and PMCs together we should also keep this in mind a bit.

I am interested to hear what others think.

Julian

Am 21.10.19, 11:54 schrieb "David Nalley" :

Greetings folks:

Please consider the following proposal, which is also on the wiki[1].
I look forward to hearing feedback.

TubeMQ

=Abstract=

TubeMQ is a distributed messaging queue (MQ) system developed by
Tencent Big Data since 2013. It focuses on high-performance storage
and transmission of massive data in big data scenarios.After nearly
seven years of massive data precipitation, TubeMQ has certain
advantages in production practice (stability + performance) and low
cost compared to many open source MQ projects.

=Proposal=

TubeMQ is suitable for high concurrency, massive data and tolerates a
small amount of data loss scenarios under abnormal conditions, such as
massive log collection, indicator statistics and monitoring, etc.
TubeMQ does not support highly reliable data transmission services
yet. It could be on a future project roadmap, as many other MQs. but
not today.

=Rationale=

Just like other message queue systems, TubeMQ is built on the
publish-subscribe pattern, aka pub-sub.
In this pattern, producers publish messages to topics while consumers
subscribe to those topics. After incoming messages get proceeded,
consumers send an acknowledgement back to producer. Once a
subscription has been created, all messages will be tracked and
retained by TubeMQ, even if the consumer go offline for some reasons.
Retained messages will be discarded only when a consumer acknowledges
that they've been successfully processed.

Portal is responsible for interact with user and admin system which
include two parts: API and web portal.

Master is controller of the cluster, which include one or multiple
master node(s) which is responsible for managing state of cluster,
resource scheduling, authentication check and maintaining of metadata.
As a reliable system, TubeMQ provides HA solution for master node.

Broker is responsible for data store which include a cluster of broker
nodes. Every broker node is managing a set of topics, include: append,
delete, update, query of topic information. In TubeMQ, these brokers
can be horizontal scaled and can be very large size for massive data
case.

Client is responsible for producing and consuming messages. When a
pub-sub topic get setup, we can support two ways (push and pull) for
delivering message from producers to consumers.

Zookeeper is for storing offset of messages which is used to recover
topic during some components get failed.


=Initial Goals=

The initial goal will be to move the current codebase in github’s
repository under Tencent account to Apache and integrate with the
Apache development process and infrastructure.
A primary goal of incubation will be to grow and diversify the TubeMQ
community. We are well aware that the project community is largely
comprised of individuals from a single company. We aim to change that
during incubation.

=Current Status=

As previously mentioned, TubeMQ is u

[DISCUSS] TubeMQ Proposal

[David Nalley]

Greetings folks:

Please consider the following proposal, which is also on the wiki[1].
I look forward to hearing feedback.

TubeMQ

=Abstract=

TubeMQ is a distributed messaging queue (MQ) system developed by
Tencent Big Data since 2013. It focuses on high-performance storage
and transmission of massive data in big data scenarios.After nearly
seven years of massive data precipitation, TubeMQ has certain
advantages in production practice (stability + performance) and low
cost compared to many open source MQ projects.

=Proposal=

TubeMQ is suitable for high concurrency, massive data and tolerates a
small amount of data loss scenarios under abnormal conditions, such as
massive log collection, indicator statistics and monitoring, etc.
TubeMQ does not support highly reliable data transmission services
yet. It could be on a future project roadmap, as many other MQs. but
not today.

=Rationale=

Just like other message queue systems, TubeMQ is built on the
publish-subscribe pattern, aka pub-sub.
In this pattern, producers publish messages to topics while consumers
subscribe to those topics. After incoming messages get proceeded,
consumers send an acknowledgement back to producer. Once a
subscription has been created, all messages will be tracked and
retained by TubeMQ, even if the consumer go offline for some reasons.
Retained messages will be discarded only when a consumer acknowledges
that they've been successfully processed.

Portal is responsible for interact with user and admin system which
include two parts: API and web portal.

Master is controller of the cluster, which include one or multiple
master node(s) which is responsible for managing state of cluster,
resource scheduling, authentication check and maintaining of metadata.
As a reliable system, TubeMQ provides HA solution for master node.

Broker is responsible for data store which include a cluster of broker
nodes. Every broker node is managing a set of topics, include: append,
delete, update, query of topic information. In TubeMQ, these brokers
can be horizontal scaled and can be very large size for massive data
case.

Client is responsible for producing and consuming messages. When a
pub-sub topic get setup, we can support two ways (push and pull) for
delivering message from producers to consumers.

Zookeeper is for storing offset of messages which is used to recover
topic during some components get failed.


=Initial Goals=

The initial goal will be to move the current codebase in github’s
repository under Tencent account to Apache and integrate with the
Apache development process and infrastructure.
A primary goal of incubation will be to grow and diversify the TubeMQ
community. We are well aware that the project community is largely
comprised of individuals from a single company. We aim to change that
during incubation.

=Current Status=

As previously mentioned, TubeMQ is under active development at
Tencent, and is being used in processing large volumes of data for
most services and products.

=Meritocracy=

We value meritocracy and we understand that it is the basis for an
open community that encourages multiple companies and individuals to
contribute and be invested in the project’s future. We will encourage
and monitor participation and make sure to extend privileges and
responsibilities to all contributors.

=Community=

TubeMQ is currently being used by developers at Tencent and a growing
number of users are actively using it in production environments.
TubeMQ has received contributions from developers working outside of
Tencent since it was open sourced on github in September 2019 By
bringing TubeMQ to Apache we aim to assure current and future
contributors that the TubeMQ community is neutral, meritocratic, and
open, in order to broaden and diversity the user and developer
community.

=Core Developers=

TubeMQ was initially developed at Tencent and is under active
development. We believe Tencent will be of interest to a broad range
of users and developers and that incubating the project at the ASF
will help us build a diverse, sustainable community.

=Alignment=

TubeMQ utilizes other Apache projects such as Hadoop, HBase and
Zookeeper. We anticipate integration with additional Apache projects
as the TubeMQ community and interest in the project grows.

=Known Risks=

==Orphaned Products==

Tencent is committed to the future development of TubeMQ and
understands that graduation to a TLP, while preferable, is not the
only positive outcome of incubation.

Should the TubeMQ project be accepted by the Incubator, the
prospective PPMC would be willing to agree to a target incubation
period of 2 years or less, knowing that every Incubator project incurs
a certain cost in terms of ASF infrastructure and volunteer time.

==Inexperience with Open Source==

Three of the initial committers are Apache Members and Incubator PMC
Members. This will help acclimate the community members to working in
the Apache Way.

==Homogenous Developers==

The major

[RESULT][IP CLEARANCE] Apache NetBeans - dukescript presenters

[Eric Barboni]

Hi,

72 hours passed,  no -1 vote.

 

According to the lazy consensus rules, The vote [1] passed successfully.

 

Best Regards

Eric

[1]

https://lists.apache.org/thread.html/e7e13899ff2ac177cd5142612c75e2fa8361ad2
a0ee74293cf1525cb@%3Cgeneral.incubator.apache.org%3E

 

Re: [PROPOSAL] sparklyr

[Justin Mclean]

Hi,

I also concerned that the initial committer list only contains 3 committers. 
Why have you not included others in the community that have made contributions?

I don’t know if this is an issue or not but bring it up just in case you not 
aware. I can see that some of the tidyverse packages are under GPL2, the GPL 
license is not compatible with the ALv2. I’m not 100% sure what license dplyr 
is under. I can see that sparkly depends on several (10+) GPL licensed pieces 
of software. Do you see this causing any issue as GPL code can’t be included in 
an Apache source release and can’t be a non-optional dependancy of an ASF 
project. Have you discussed this with your champion or proposed mentors and 
have they flagged this as a possible issue?

I can see that one of the proposed mentors is not an IPMC member (which is 
required) and another seems not very active in signing off reports or voting on 
releases. Did you think the existing mentors will provide your project with 
enough support?

Thanks,
Justin

1. https://github.com/tidyverse/dplyr/blob/master/LICENSE
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Podling Echarts Report Reminder - November 2019

[Justin Mclean]

Hi,

> Can brpc be put into this group, together with Echarts/doris.
> So I can reminder them and me to finish the pod report at the same time.

If a project wants to change group in reports in the request needs to come from 
the PMC. IMO it’s probably not a good idea to have all three projects reporting 
at the same time.

Thanks,
Justin



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org