Re: [DISCUSS] TubeMQ Proposal
เมื่อ 30 ต.ค. 2019 12:06 PM "Jean-Baptiste Onofré" เขียนว่า > Thanks David ! > > Regards > JB > > On 30/10/2019 02:40, David Nalley wrote: > >> On Mon, Oct 21, 2019 at 7:50 AM Jean-Baptiste Onofré >> wrote: >> >>> 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. >>> >>> Thanks for offering. We'll happily take you up on the offer. >> >> Thanks, >> >> --David >> >> - >> 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] Graudate Apache Weex (Incubating) as a Top Level Project
เมื่อ 30 ต.ค. 2019 7:52 PM "申远" เขียนว่า > FYI: If the initial committers really matter, maybe we could ask secretary > to help us find out how many individuals signed the ICLA when Weex entered > the Incubator. > > Best Regards, > YorkShen > > 申远 > > > ซ่อยค่อย ลืมเขาแน่ <0989132858...@gmail.com> 于2019年10月30日周三 下午8:35写道： > > > เมื่อ 30 ต.ค. 2019 7:16 PM "申远" เขียนว่า > > > > > > > > > > The PPMC needs to protect their brand in particular from their own > > > company. > > > > > > > > > Agree with that, and this is exactly why I am persuading project like > > > Weex-UI [1] donated to ASF instead of making them changing their name > to > > > "XXX powered by Apache Weex" and then pretend there is no problem. > > > > > > Anyone on the Initial list are committers I assume you mean they see > not > > > > contributing? > > > > > > > > > > No, some [2] of them are never committers of Weex according to our > > whimsy. > > > For example, the top 2 names on the initial developer list are not > > > committers of Weex according to whimsy and they didn't contribute, of > > > course. Some of other names, like me, are also on the initial developer > > > list, but I was actually elected as Weex committer four months after it > > > into incubator. There is a vote for nominating me as a Weex committer > > [3]. > > > I don't know what happened here, as I am not the initial committer in > > fact. > > > But the initial developer list [2] is incorrect, I'm sure about that. > > > > > > [1] > > > https://lists.apache.org/thread.html/ab1cdf009697ac261e10c8963ed9ad > > > fe226edeee056f0c7dabb780c0@%3Cdev.weex.apache.org%3E > > > [2] > > > https://lists.apache.org/thread.html/b53537fea384f1d75c9921f71e13d1 > > > 7780381504cff971e5f18bda96@%3Cgeneral.incubator.apache.org%3E > > > [3] > > > https://lists.apache.org/thread.html/8ebbd2fb5fb85c1da4328685859ae1 > > > bb365a8b6253772c9e06940a39@%3Cprivate.weex.apache.org%3E > > > > > > Best Regards, > > > YorkShen > > > > > > 申远 > > > > > > > > > Justin Mclean 于2019年10月30日周三 下午7:32写道： > > > > > > > Hi, > > > > > > > > It seems like there are two concerns around Weex, branding and > > > independent > > > > > community. > > > > > > > > > > > > > I'd still like to hear what your mentors think. Are they active? > > > > > > > > For branding part, I understand this is a serious issue, and it takes > > me > > > > > months to solve this kinds of issues > > > > > > > > > > > > > This needs to be the PPMC not just you. I chose some of those links > on > > > > purpose as they belong to the company they belong to. The PPMC needs > to > > > > protect their brand in particular from their own company. > > > > > > > >- Though there are 13 committers according to the initial proposal > > > [5], > > > > >but many of them are not committers today. > > > > > > > > > > > > Anyone on the Initial list are committers I assume you mean they see > > not > > > > contributing? > > > > > > > > Just take the committers on the initial proposal as an inacurrate > > > records, > > > > > there are some mistakes on this list. > > > > > > > > > > > > This seems concerning. > > > > > > > > > > > > > >- There are developers out of the comany make their own tools > > around > > > > >Weex > > > > > > > > > > > > > Which is great but they are external to the project. Whats the > barriers > > > (if > > > > any) that stopped them from doing this development inside the > project? > > > > > > > > Thanks, > > > > Justin > > > > > > > > > >
Re: [VOTE] Graudate Apache Weex (Incubating) as a Top Level Project
เมื่อ 30 ต.ค. 2019 7:16 PM "申远" เขียนว่า > > > > The PPMC needs to protect their brand in particular from their own > company. > > > Agree with that, and this is exactly why I am persuading project like > Weex-UI [1] donated to ASF instead of making them changing their name to > "XXX powered by Apache Weex" and then pretend there is no problem. > > Anyone on the Initial list are committers I assume you mean they see not > > contributing? > > > > No, some [2] of them are never committers of Weex according to our whimsy. > For example, the top 2 names on the initial developer list are not > committers of Weex according to whimsy and they didn't contribute, of > course. Some of other names, like me, are also on the initial developer > list, but I was actually elected as Weex committer four months after it > into incubator. There is a vote for nominating me as a Weex committer [3]. > I don't know what happened here, as I am not the initial committer in fact. > But the initial developer list [2] is incorrect, I'm sure about that. > > [1] > https://lists.apache.org/thread.html/ab1cdf009697ac261e10c8963ed9ad > fe226edeee056f0c7dabb780c0@%3Cdev.weex.apache.org%3E > [2] > https://lists.apache.org/thread.html/b53537fea384f1d75c9921f71e13d1 > 7780381504cff971e5f18bda96@%3Cgeneral.incubator.apache.org%3E > [3] > https://lists.apache.org/thread.html/8ebbd2fb5fb85c1da4328685859ae1 > bb365a8b6253772c9e06940a39@%3Cprivate.weex.apache.org%3E > > Best Regards, > YorkShen > > 申远 > > > Justin Mclean 于2019年10月30日周三 下午7:32写道： > > > Hi, > > > > It seems like there are two concerns around Weex, branding and > independent > > > community. > > > > > > > I'd still like to hear what your mentors think. Are they active? > > > > For branding part, I understand this is a serious issue, and it takes me > > > months to solve this kinds of issues > > > > > > > This needs to be the PPMC not just you. I chose some of those links on > > purpose as they belong to the company they belong to. The PPMC needs to > > protect their brand in particular from their own company. > > > >- Though there are 13 committers according to the initial proposal > [5], > > >but many of them are not committers today. > > > > > > Anyone on the Initial list are committers I assume you mean they see not > > contributing? > > > > Just take the committers on the initial proposal as an inacurrate > records, > > > there are some mistakes on this list. > > > > > > This seems concerning. > > > > > > > >- There are developers out of the comany make their own tools around > > >Weex > > > > > > > Which is great but they are external to the project. Whats the barriers > (if > > any) that stopped them from doing this development inside the project? > > > > Thanks, > > Justin > > >
Re: [VOTE] Accept TubeMQ into the Apache Incubator
เมื่อ 30 ต.ค. 2019 9:49 AM "Scheduler dolphin" เขียนว่า > +1 (non-binding). > good luck！ > > — > > *DolphinScheduler(Incubator) *PPMC > *Lidong Dai * > > lidong@outlook.com > > — > > On Wed, Oct 30, 2019 at 10:30 AM Saisai Shao > wrote: > > > +1 (non-binding). > > > > Thanks > > Saisai > > > > Sheng Wu 于2019年10月30日周三 上午10:03写道： > > > > > +1 binding > > > Good luck. > > > > > > Dave Fisher 于2019年10月30日 周三上午7:30写道： > > > > > > > +1 (binding) > > > > > > > > Go TubeMQ. > > > > > > > > Regards, > > > > Dave > > > > > > > > Sent from my iPhone > > > > > > > > > On Oct 29, 2019, at 6:48 PM, David Nalley wrote: > > > > > > > > > > Hi folks, > > > > > > > > > > The [DISCUSS] thread on TubeMQ has died down. > > > > > > > > > > Accordingly, I would like to call a VOTE to accept TubeMQ into the > > > > > Apache Incubator. > > > > > > > > > > Please cast your vote: > > > > > > > > > > [ ] +1, bring TubeMQ into the Incubator > > > > > [ ] +0, I don't care either way > > > > > [ ] -1, do not bring TubeMQ into the Incubator, because... > > > > > > > > > > The vote will open at least for 72 hours and only votes from the > > > > > Incubator PMC are binding, but votes from everyone are welcome. > > > > > > > > > > =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
Re: [RESULT][VOTE] Release Apache Doris 0.11.0-incubating-rc01
เมื่อ 29 ต.ค. 2019 1:13 PM "Zhao Chun" เขียนว่า > Hi all, > > Thanks to everyone, and the vote for releasing Apache Doris > 0.11.0-incubating-rc01 is now closed. > > It has passed with 3 +1 (binding) votes and no 0 or -1 votes. > > Binding: > +1 Dave Fisher > +1 Dave Meikle > +1 Willem Jiang > > The vote thread: > https://lists.apache.org/thread.html/d1cd04315b948e66a9f30b5102335a > c0770c8a9c62d0aab5cb50e0dc@%3Cgeneral.incubator.apache.org%3E > > Thanks, > Zhao Chun >
Re: [VOTE] Graudate Apache Weex (Incubating) as a Top Level Project
เมื่อ 28 ต.ค. 2019 2:42 PM "Justin Mclean" เขียนว่า > Hi, > > > How can third party web sites be a "branding/trademark issue" for an > > Apache project? > > (P)PMC members are responsible for the project brands and that includes > making sure that 3rd parties use that brands and trademarks correctly. > > I suggest you read https://www.apache.org/foundation/marks/resources. > https://www.apache.org/foundation/marks/responsibility > https://www.apache.org/foundation/marks/guide > https://www.apache.org/foundation/marks/faq/ > > At ApacheCon Shane gavse a version of this talk which also may help: > http://shaneslides.com/fossbackstage/Who-Owns-That-FOSS-Brand.pdf > > (There was an updated version of this given at Apache EU last week) > > Thanks, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [jira] [Updated] (INCUBATOR-247) IP clearance for ServiceComb osa-validator
เมื่อ 29 ต.ค. 2019 3:36 PM "Willem Jiang (Jira)" เขียนว่า > > [ https://issues.apache.org/jira/browse/INCUBATOR-247? > page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] > > Willem Jiang updated INCUBATOR-247: > --- > Description: > [chanjarster|https://github.com/NewCapec-Institute/oas- > validator/commits?author=chanjarster] is contributing the oas-validator > to Apache ServiceComb. > > The clearance tasks are in progress and recorded at: [ > https://incubator.apache.org/ip-clearance/servicecomb- > osa-validator.html|https://incubator.apache.org/ip- > clearance/servicecomb-osa-validator.html] > > This issue is partly to track that and primarily to provide an official > record of the code drop contribution. The contributed code is attached to > this issue as oas-validator-apache.zip. > > MD5 (oas-validator-apache.zip) = d2e12edf4cbe0024a48b647757367851 > > Github repo [https://github.com/NewCapec-Institute/oas-validator] > > Git commit SHA for donated software: eb073aea2a80ccfe7abecdd34f62e7 > d2182d7199 > > > > > > was: > [chanjarster|https://github.com/NewCapec-Institute/oas- > validator/commits?author=chanjarster] is contributing the oas-validator > to Apache ServiceComb. > > The clearance tasks are in progress and recorded at: [ > https://incubator.apache.org/ip-clearance/servicecomb- > osa-validator.html|https://incubator.apache.org/ip- > clearance/servicecomb-toolkit.html] > > This issue is partly to track that and primarily to provide an official > record of the code drop contribution. The contributed code is attached to > this issue as oas-validator-apache.zip. > > MD5 (oas-validator-apache.zip) = d2e12edf4cbe0024a48b647757367851 > > Github repo [https://github.com/NewCapec-Institute/oas-validator] > > Git commit SHA for donated software: eb073aea2a80ccfe7abecdd34f62e7 > d2182d7199 > > > > > > > > IP clearance for ServiceComb osa-validator > > -- > > > > Key: INCUBATOR-247 > > URL: https://issues.apache.org/jira/browse/INCUBATOR-247 > > Project: Incubator > > Issue Type: Task > >Reporter: Willem Jiang > >Priority: Major > > Attachments: oas-validator-apache.zip > > > > > > [chanjarster|https://github.com/NewCapec-Institute/oas- > validator/commits?author=chanjarster] is contributing the oas-validator > to Apache ServiceComb. > > The clearance tasks are in progress and recorded at: [ > https://incubator.apache.org/ip-clearance/servicecomb- > osa-validator.html|https://incubator.apache.org/ip- > clearance/servicecomb-osa-validator.html] > > This issue is partly to track that and primarily to provide an official > record of the code drop contribution. The contributed code is attached to > this issue as oas-validator-apache.zip. > > MD5 (oas-validator-apache.zip) = d2e12edf4cbe0024a48b647757367851 > > Github repo [https://github.com/NewCapec-Institute/oas-validator] > > Git commit SHA for donated software: eb073aea2a80ccfe7abecdd34f62e7 > d2182d7199 > > > > > > > > -- > This message was sent by Atlassian Jira > (v8.3.4#803005) > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release Apache Doris 0.11.0-incubating-rc01
เมื่อ 27 ต.ค. 2019 8:46 AM "Dave Meikle" เขียนว่า > On Wed, 23 Oct 2019 at 10:11, Zhao Chun wrote: > > > The artifacts (source, signature and checksum) corresponding to this > > release > > candidate can be found here: > > https://dist.apache.org/repos/dist/dev/incubator/doris/0.11.0-rc1/ > > > > This has been signed with PGP key 983C9560, corresponding to > > zh...@apache.org. > > > > The vote will be open for at least 72 hours. > > > > From the PPMC Vote we cary over 1 binding IPMC Votes: > > > > +1 from Dave Fisher > > > > [ ] +1 Approve the release > > [ ] +0 No opinion > > [ ] -1 Do not release this package because ... > > > > > +1 (binding). I checked; name, sig and hashes, notice, license, source > headers, compiles from source (using Docker environment). > > As noted by Dave Fisher on the dev list - it is worth adding licence > headers to the markdown files. > > Cheers, > Dave >
Re: [DISCUSS] Maven account for publishing convience binary
เมื่อ 30 ก.ย. 2019 4:55 PM "申远" เขียนว่า > Hi, folks > > Recently, I am trying to publish convenience library of Weex to JCenter, a > seperate maven repositories for Android developers. I’d like to know > whether there is an Apache-wide JCenter account for publishing connivence > binary. It seems like each Apache project is allowed to create their own > Jcenter account [1] and publish convenience library as long as the account > is shared by PMC/PPMC. > > Please correct me if I am wrong, otherwise I shall create a jcenter > accounts shared by Weex PPMC. > > [1] https://bintray.com/cordova/maven/cordova-android > [2] https://bintray.com/bintray/jcenter/org.apache.commons:commons-lang3 > > Best Regards, > YorkShen > > 申远 >
Re: [IP CLEARANCE] ServiceComb toolkit contribution
เมื่อ 28 ต.ค. 2019 8:11 AM "Willem Jiang" เขียนว่า > 72 hours passed. We got none -1 vote. > > Based on lazy consensus, this vote passed. I will update the > ip-clearance page for the vote information. > > Willem Jiang > > On behalf of ServiceComb PMC. > > On Thu, Oct 24, 2019 at 9:58 AM Willem Jiang > wrote: > > > > Hi Incubator PMC, > > > > The TLP Apache ServiceComb toolkit[1] has been donated code for > > OpenAPI Specific Validator being referred to as > > `servicecomb-oas-validator`, old hostsd at [2]. > > > > This is the formal request for IP clearance to be checked as per [3]. > > The donated code can be found at [4] . > > > > Please check the ip-clearance filed here[5] for more information. > > The PMC has voted and passed to accept this donation[6]. > > The ICLA of major contributors, Daniel Qian has been filed. > > The SGA from NewCapec Institute has been filed. > > > > Please vote to approve this contribution. > > > > This majority vote is open for at least 72 hours and as usual lazy > > consensus applies. > > > > [1]https://github.com/apache/servicecomb-toolkit > > [2]https://github.com/NewCapec-Institute/oas-validator > > [3]https://incubator.apache.org/ip-clearance/ip-clearance- > template.html#form-filling > > [4]https://issues.apache.org/jira/browse/INCUBATOR-247 > > [5]https://incubator.apache.org/ip-clearance/servicecomb- > oas-validator.html > > [6]https://lists.apache.org/thread.html/704967302e2f3c093441bf197bfe83 > b7aee34c210e0c3bb3898d4170@%3Cdev.servicecomb.apache.org%3E > > > > Willem Jiang > > > > On behalf of ServiceComb PMC. > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] release datasketches-postgresql 1.3.0-incubating-rc2
เมื่อ 27 ต.ค. 2019 3:50 PM "Justin Mclean" เขียนว่า > Hi, > > +1 binding > > I checked: > - incubating in name > - signature and hashes correct > - No binary files in release > - DISCLAIMER exists > - LICENCE and NOTICE file are good > - This file is missing an ASF header [1] > - unable to compile on OSX but probably because I may not have right > environment setup or version of PostgreSQL installed > > Compile error is: > src/kll_float_sketch_c_adapter.cpp:26:10: fatal error: 'kll_sketch.hpp' > file not > found > #include > > Thanks, > Justin > > 1. apache-datasketches-postgresql-1.3.0-incubating-src/package.sh > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [ANNOUNCE] Apache Doris (incubating) 0.11.0 Release
เมื่อ 29 ต.ค. 2019 2:29 PM "Zhao Chun" เขียนว่า > Hi All, > > We are pleased to announce the release of Apache Doris 0.11.0-incubating. > > Apache Doris (incubating) is an MPP-based interactive SQL data warehousing > for reporting and analysis. > > The release is available at: > http://www.apache.org/dist/incubator/doris/ > > Thanks to everyone who has contributed to this release, and the release > note can be found here: > https://github.com/apache/incubator-doris/issues/1891 > > Best Regards, > On behalf of the Doris team, > Zhao Chun > > > DISCLAIMER: > Apache Doris(incubating) is an effort undergoing incubation at The Apache > Software Foundation (ASF), sponsored by the Apache Incubator. Incubation is > required of all newly accepted projects until a further review indicates > that > the infrastructure, communications, and decision making process have > stabilized > in a manner consistent with other successful ASF projects. While incubation > status is not necessarily a reflection of the completeness or stability of > the > code, it does indicate that the project has yet to be fully endorsed by the > ASF. >
Re: [VOTE] Accept TubeMQ into the Apache Incubator
เมื่อ 30 ต.ค. 2019 8:48 AM "David Nalley" เขียนว่า > Hi folks, > > The [DISCUSS] thread on TubeMQ has died down. > > Accordingly, I would like to call a VOTE to accept TubeMQ into the > Apache Incubator. > > Please cast your vote: > > [ ] +1, bring TubeMQ into the Incubator > [ ] +0, I don't care either way > [ ] -1, do not bring TubeMQ into the Incubator, because... > > The vote will open at least for 72 hours and only votes from the > Incubator PMC are binding, but votes from everyone are welcome. > > =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
Re: [DISCUSS] TubeMQ Proposal
เมื่อ 30 ต.ค. 2019 8:41 AM "David Nalley" เขียนว่า > On Mon, Oct 21, 2019 at 7:50 AM Jean-Baptiste Onofré > wrote: > > > > 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. > > > > Thanks for offering. We'll happily take you up on the offer. > > Thanks, > > --David > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release Apache ECharts (incubating) 4.3.0 (release candidate 1)
ในวันที่ พฤ. 5 ก.ย. 2019 15:01 SHUANG SU เขียนว่า: > I am pleased to be calling this vote for the release of Apache ECharts > (incubating) 4.3.0 (release candidate 1). > > Apache ECharts community has voted and approved the release. > > Vote thread: > > https://lists.apache.org/thread.html/e17e9a8d94c81019b073ef7f5cee9075d6921f01cdd8840f9618b012@%3Cdev.echarts.apache.org%3E > > Results thread: > > https://lists.apache.org/thread.html/0d52c6ed1e5d1b6bc72b56e1b240063577fde4d9cc3c227d33396caa@%3Cdev.echarts.apache.org%3E > > The release candidate to be voted over is available at: > https://dist.apache.org/repos/dist/dev/incubator/echarts/4.3.0-rc.1/ > > The release candidate is signed with a GPG key available at: > https://dist.apache.org/repos/dist/dev/incubator/echarts/KEYS > > The Git commit for this release is: > > https://gitbox.apache.org/repos/asf?p=incubator-echarts.git;a=commit;h=b62ab99 > > The Release Note is available in: > > https://dist.apache.org/repos/dist/dev/incubator/echarts/4.3.0-rc.1/RELEASE_NOTE.txt > > Some shell commands for validating the release: > > ```shell > # Download the release: > curl > > https://dist.apache.org/repos/dist/dev/incubator/echarts/4.3.0-rc.1/apache-echarts-4.3.0-rc.1-incubating-src.zip > -o apache-echarts-4.3.0-rc.1-incubating-src.zip > unzip apache-echarts-4.3.0-rc.1-incubating-src.zip -d > apache-echarts-4.3.0-rc.1-incubating-src > /dev/null > > # Rebuild the project (Node.js environment is required): > cd "apache-echarts-4.3.0-rc.1-incubating-src" && npm install && cd .. > node "apache-echarts-4.3.0-rc.1-incubating-src/build/build.js" --release > # (See help: `node > "apache-echarts-4.3.0-rc.1-incubating-src/build/build.js" --help`) > ``` > > > Please vote on releasing this package as: > Apache ECharts (incubating) 4.3.0 (release candidate 1) > by "2019-09-08T08:57:30.519Z". > > [ ] +1 Release this package > [ ] 0 I don't feel strongly about it, but don't object > [ ] -1 Do not release this package because... > > Anyone can participate in testing and voting, not just committers, please > feel free to try out the release candidate and provide your votes. > > A checklist for reference: > > https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist > > Thanks, > -- > Su Shuang (100pah) > -- >
Re: [PROPOSAL] MetaObjects for Apache Incubator
ในวันที่ ศ. 6 ก.ย. 2019 01:25 Nygard, Carl J เขียนว่า: > > > > > Hi, > > > > Cengage wishes to donate the code to Apache, but is unable to do so > until the project is accepted as an Incubator project. > > > Could you expand a little on why is that? > > Perhaps it is an issue of understanding the path to Incubator and trying > to deal with the corporate policies regarding open-source donation. > Donation to Apache seems to be the clearest path with the least number of > obstacles. > > > > The Apache community members looking to approve the project > understandably would like to better understand what they are approving and > so would like to get access to the code which is to be donated. > > > I don’t see this a being a big issue, the other code can be donated > later, but may complicate things in terms of SGAs, ICLAs and IP provenance. > > Can you expand on this? Is there a different process for donating a large > body of work to an existing Incubator project? > > --carl > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [Discuss] Graduate Apache SINGA (incubating) as a TLP
ในวันที่ พฤ. 5 ก.ย. 2019 06:13 Justin Mclean เขียนว่า: > Hi, > > I just took a look at the Sign incubator report and it needs some > improvement. If you were a TLP if and a report like this was submitted to > the board, it would likely be rejected, or attract questions. I suggest you > add a bit more meaningful detail to the report. > > Thanks, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [Discuss] Graduate Apache SINGA (incubating) as a TLP
ในวันที่ ส. 31 ส.ค. 2019 17:48 Moaz Reyad เขียนว่า: > Dear Alan, > > The copyright section in the project page [1] has the following item : > > Date: 2015-03-31 > Item: Check and make sure that the papers that transfer rights to the ASF > been received. It is only necessary to transfer rights for the package, the > core code, and any new code produced by the project. > > I believe this answers your question about the transfer rights of the code. > Please let me know if there is anything else required. > > We will proceed to vote if no one objects. > > Thank you, > Moaz > > [1] http://incubator.apache.org/projects/singa.html > > On Tue, Aug 27, 2019 at 8:48 PM Alan Gates wrote: > > > Sorry, I brought this up earlier on the dev list but didn't follow up. I > > can't find a copy of the code grant for the code that Singa brought into > > the Incubator. When I look at the Secretary's page[1] that lists all of > > the code grants I don't see one for Singa. Per the initial proposal[2] > > there was code imported from an existing github repo [3], which means we > > need to have a code grant from whom ever owned that code (National > > University of Singapore would be my guess). > > > > We need to clear this up before Singa graduates to assure that the ASF > has > > the right to this code. > > > > Alan. > > > > [1] https://incubator.apache.org/ip-clearance/index.html > > [2] https://cwiki.apache.org/confluence/display/INCUBATOR/SingaProposal > > [3] https://github.com/nusinga/singa > > > > On Tue, Aug 27, 2019 at 1:34 AM Moaz Reyad wrote: > > > > > Hi all, > > > > > > In the four and a half years that Apache SINGA (incubating) has > > > been a part of the Apache incubator, the community has grown, > > diversified, > > > and adapted to the Apache Way. We believe that the project is ready to > > > graduate to a TLP. > > > > > > As a community, we have discussed [1] and voted [2] to graduate to a > > > TLP, we have worked through the maturity model [3], notified the IPMC > > that > > > we have the intention to graduate [4] and proposed PMC chair [5]. > > > > > > Please see the draft resolution appended below and provide any > > > comments or feedback you have on it. > > > > > > We would like to continue the graduation process and hereby ask you > > > all for your opinion on this. The discussion is open for 72 hours, > after > > > which we will start a [VOTE] on graduation here. > > > > > > Thanks, > > > > > > --moaz > > > on behalf of the Apache SINGA PPMC > > > > > > [1] > > > > > > > > > https://lists.apache.org/thread.html/fd2fe639f3314ff22d2e47d39bd6d4126d61d10e8628fa26f71ef01d@%3Cdev.singa.apache.org%3E > > > [2] > > > > > > > > > https://lists.apache.org/thread.html/cb40b73b3fd685b44a129601abd5967e4150db245b3fc6552f106faf@%3Cdev.singa.apache.org%3E > > > [3] > > > > > > https://cwiki.apache.org/confluence/display/SINGA/Maturity+model+assessment > > > [4] > > > > > > > > > https://lists.apache.org/thread.html/5b5ebefe705084e0a9d67cfaf56f17ff27518273366f8088be19273e@%3Cgeneral.incubator.apache.org%3E > > > [5] > > > > > > > > > https://lists.apache.org/thread.html/2903ea94da1b862acf8d706dd4f7cd9ecbc434166d4381d170be731f@%3Cprivate.singa.apache.org%3E > > > > > > Proposed Resolution for the Apache SINGA project for the ASF Board: > > > > > > X. Establish the Apache SINGA Project > > > > > > WHEREAS, the Board of Directors deems it to be in the best > > > interests of the Foundation and consistent with the > > > Foundation's purpose to establish a Project Management > > > Committee charged with the creation and maintenance of > > > open-source software, for distribution at no charge to > > > the public, related to a distributed deep learning platform. > > > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management > > > Committee (PMC), to be known as the "Apache SINGA Project", > > > be and hereby is established pursuant to Bylaws of the > > > Foundation; and be it further > > > > > > RESOLVED, that the Apache SINGA Project be and hereby is > > > responsible for the creation and maintenance of software > > > related to a distributed deep learning platform; > > > and be it further > > > > > > RESOLVED, that the office of "Vice President, Apache SINGA" be > > > and hereby is created, the person holding such office to > > > serve at the direction of the Board of Directors as the chair > > > of the Apache SINGA Project, and to have primary responsibility > > > for management of the projects within the scope of > > > responsibility of the Apache SINGA Project; and be it further > > > > > > RESOLVED, that the persons listed immediately below be and > > > hereby are appointed to serve as the initial members of the > > > Apache SINGA Project: > > > > > > * Thejas Nair ( the...@apache.org ) > > > * Alan Gates ( ga...@apache.org ) > > > * Ted Dunning ( tdunn...@apache.org ) > > > * Beng Chin Ooi ( oo...@apache.org ) > > > * Wang Wei ( wang...@apache.org ) > > > * Anh Dinh ( dinh...@apache.org ) > > > * Chen
Re: [VOTE] Release Apache Milagro (incubating) Crypto Libraries v1.0.0
แสดข้อความที่ยกมา เมื่อ 25 ส.ค. 2019 08:56 "ซ่อยค่อย ลืมเขาแน่" <0989132858...@gmail.com> เขียนว่า > > เมื่อ 25 ส.ค. 2019 05:06 "Justin Mclean" > เขียนว่า > >> Hi, >> >> > All of the code was either written from scratch >> >> Thanks for that. I just thought it would be a little odd to do given the >> standard nature of some of the algorithms in there (calculating hashes and >> the like). >> >> 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 Milagro (incubating) Crypto Libraries v1.0.0
เมื่อ 25 ส.ค. 2019 05:06 "Justin Mclean" เขียนว่า > Hi, > > > All of the code was either written from scratch > > Thanks for that. I just thought it would be a little odd to do given the > standard nature of some of the algorithms in there (calculating hashes and > the like). > > Thanks, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: Podlings, the Incubator, relationships and Apache
ในวันที่ ศ. 21 มิ.ย. 2019 23:22 Alex Harui เขียนว่า: > It all makes sense to me. I think there are two key points that are > driving all of this discussion: > > "5. Disclaimers generally don't remove liability" > > IANAL so I don't know if that's true or not. For sure there are lots of > disclaimers in the world. I do not know the history of the current > DISCLAIMER (and labeling of releases with -incubating). What was the > DISCLAIMERs original purpose? Should it be modified to cover > less-than-perfect podling releases, especially around CatX inclusions? Who > gets to make that call? > > " It's not perfect compliance vs. failure. > IMO, the IPMC has been delegated the decision making process, and may > often find themselves making the business decision that an imperfect > release is better than a community stalled for months or years. Don't > let the perfect be the enemy of the good." > > I think several "prominent" ASF members are saying this same thing, but > nobody really wants to make it official. The responsibility seems to have > been passed around between IPMC, Board, and VP Legal. How can the ASF get > closure on this topic? > > My 2 cents, > -Alex > > On 6/20/19, 10:04 AM, "David Nalley" wrote: > > There's been a lot of discussion in various threads about bureaucracy, > whether podlings are part of the ASF, etc. As a result of that I've > spent a good deal of time reading resolutions and older discussions > and organizing those thoughts from a legal and community perspective. > I've also read a number of conversations from the more august members > of our body about this subject. Altogether it has somewhat changed > some of my opinions and assumptions. I've also sensed that there is a > community/business/legal disconnect in our conversations. We're using > the same words to mean very different things in each of those > contexts. That said I am but one member of the IPMC, but maybe this > will be helpful to someone else - I've tried to avoid my assumptions > in this. > > The IPMC's first 'job'[1] is "accepting new products into the > Foundation" The second 'job' of the IPMC is to "provide guidance and > support to ensure that the Incubator's sub-projects[2] develop > products according to the Foundation's philosophy and guidelines". The > final 'job' is evaluating the products and determining whether they > should be abandoned, continue to receive guidance and support, or be > promoted to "full project status". > > So there are several realizations I gained from this from the > Incubator perspective. > 1. Acceptance into the Incubator is acceptance of the product into the > Foundation. > 2. That product is then a sub-project of the Incubator. > 3. The IPMC has the "primary responsibility for the management of > those subprojects". > > From the Foundation's perspective there are a number of things that > come to mind: > 1. We aren't a github/sourceforge/google code type platform where > random people can upload/post what they want. > 2. We do not have DMCA Safe Harbor protection - e.g. we are > responsible for everything that we publish or distribute. With the > exception of wikis and bug trackers anyone who can put something up on > an Apache property has some form of legal relationship with the > Foundation. This could be as simple as an ICLAs where you've > contractually said you won't contribute anything you don't have rights > to. > 3. Most of the project's who have come to us aren't entities in and of > themselves. E.g. the 'project' doesn't truly exist from a legal entity > perspective - and even those who do are at best an unincorporated > association of individuals. From a legal perspective - projects can't > make or distribute a release - they don't exist - only the ASF and the > individual(s) doing the work. Given that one of the explicit reasons > the Foundation was created was to[5]: "provide a means for individual > volunteers to be sheltered from legal suits"; we want them to create > and distribute releases as the Foundation. > 4. Whether we like it or not - the Foundation is judged on the output > from our projects and subprojects. We have a reputation of having > clean IP, permissively licensed open source code, with clear > provenance. Many people explicitly copy our standards, guidelines, and > policies because they are the gold standard for good open source > governance. > 5. Disclaimers generally don't remove liability, and even if they did, > our disclaimer talks about the maturity of our projects. - And it > certainly doesn't remove the public's expectations from us - frankly - > losing the publics trust is as scary as the potential legal liability. > 6. The Board has delegated the responsibility of managing and ensuring
Re: No access to dist.apache.org
ในวันที่ ส. 22 มิ.ย. 2019 03:45 leerho เขียนว่า: > 1) I asked INFRA how to setup the proper structures in dist.a.o. > INFRA tells me that IPMC members create the proper folders in dist/dev and > dist/release directories and once created the PPMC should have access. > > 2) There is also no "Staging Profile" in Apache Nexus Repository for > datasketches. When does that get set up? > > > > I have been held up for a full week now in making any progress in migrating > to ASF. I need to create the first Release Candidate artifact so that it > can be referenced as a dependency by our other repositories. I keep > running into roadblocks where the basic infrastructure has not be set up > that would allow me to make progress. > > I would be really grateful if someone could help guide me through this > first "release" process steps. > > Specifically: > a) Review our POM file for correct setup for a release to Apache (at least > a release candidate) > b) Guide me through the required Maven or command-line commands to get this > first release created. > > Thank you! > > > > > > > > On Fri, Jun 21, 2019 at 11:08 AM leerho wrote: > > > 1) I am trying to create our first podling release candidate and need > > access to dist.apache.org to record PGP keys, etc. There is no listing > > for our podling project datasketches and I have no write access to that > > site. How can I make progress? > > > > 2) I would like to create a temporary landing page for our website at > > datasketches.apache.org. > > How do I do that? > > > > Lee. > > >
Re: [VOTE] Release Apache Druid (incubating) 0.15.0 [RC2]
ในวันที่ ส. 22 มิ.ย. 2019 04:21 Gian Merlino เขียนว่า: > > I'll leave that to others to decide, but if I were release manager, I > > would fix them before release. > > Thanks for taking the time to inspect our release! > > I'm not the release manager here, but my thoughts are that for issues such > as this, it makes sense to fix them for the next release rather than the > current one. The reason is just that the cycle time is quite long for > cutting RCs (72 hour vote on the project list + 72 hour vote on the > Incubator list, the latter of which often takes longer than 72 hours due to > IPMC folks being a busy bunch). > > On Fri, Jun 21, 2019 at 3:02 AM sebb wrote: > > > On Fri, 21 Jun 2019 at 02:12, Jihoon Son wrote: > > > > > > Thank you for your detailed review! > > > > > > We will address your comments on signing keys in the future votes. > > > > > > Regarding the commit id, "44c9323" is the correct commit id for the > tag. > > > Maybe the link is not valid. > > > Is https://github.com/apache/incubator-druid/commits/44c9323 or > > > > > > https://github.com/apache/incubator-druid/tree/druid-0.15.0-incubating-rc2 > > more > > > valid one? > > > > The first one is immutable but not obvious, the second is not > > guaranteed immutable. > > > > However you could use: > > > > > https://github.com/apache/incubator-druid/tree/druid-0.15.0-incubating-rc2 > > (44c9323 > > < > https://github.com/apache/incubator-druid/tree/druid-0.15.0-incubating-rc2(44c9323 > > > > ) > > > > > Finally, would you elaborate more on what looks wrong to you in NOTICE > > and > > > NOTICE.BINARY files? > > > > NOTICE files should contain only what is strictly required for the > > files actually contained in the bundle to which they apply. > > See: > > [1] > > > http://www.apache.org/dev/licensing-howto.html#assembling-license-and-notice > > > > The header looks OK, but most of the rest looks unnecessary. > > > > No need to mention Apache Licensed code unless the bit you have copied > > has a required notice in its NOTICE file. > > > > In the case of the other products, they may or may not require entries > > in NOTICE. > > That depends on their license. > > As per [1], generally BSD and MIT code does not require an entry in > NOTICE. > > > > The last section (JetS3t) does not make sense. > > > > Similar considerations apply to NOTICE.BINARY > > In the case of commons-codec-1.7.jar, does the binary bundle actually > > include the file > > DoubleMetaphoneTest ? It seems unlikely -- if not present, the entry > > is not required. > > > > The LICENSE file likewise is generally OK (assuming it corresponds > > with the software that is in the source bundle). It's good that the > > software versions are mentioned. However the license pointer is > > missing for the Porter Stemmer. It can be guessed from the previous > > entry, so that is not a blocker. > > > > > We will fix them if necessary for this release. > > > > I'll leave that to others to decide, but if I were release manager, I > > would fix them before release. > > > > > Jihoon > > > > > > On Thu, Jun 20, 2019 at 9:46 AM sebb wrote: > > > > > > > On Thu, 20 Jun 2019 at 03:39, Jihoon Son > wrote: > > > > > > > > > > Hi IPMC, > > > > > > > > > > The Apache Druid community has voted on and approved a proposal to > > > > release > > > > > Apache Druid (incubating) 0.15.0 (rc2). > > > > > > > > > > We now kindly request the Incubator PMC members review and vote on > > this > > > > > incubator release. > > > > > > > > > > Apache Druid (incubating) is a high performance analytics data > store > > for > > > > > event-driven data. > > > > > > > > > > The community voting thread can be found here: > > > > > > > > > > > > https://lists.apache.org/thread.html/f4b1b708bcb7e6ec08e6a9cfcb2c0dfcb565fab353ccbb8c5f362218@%3Cdev.druid.apache.org%3E > > > > > > > > > > The release notes are available here: > > > > > https://github.com/apache/incubator-druid/issues/7854 > > > > > > > > > > The release candidate has been tagged in GitHub as > > > > > druid-0.15.0-incubating-rc2 (44c9323), available here: > > > > > > > > > > > > https://github.com/apache/incubator-druid/releases/tag/druid-0.15.0-incubating-rc2 > > > > > > > > I'm not sure that's the correct URL for the tag; it points to a > couple > > > > of archives. > > > > > > > > I would expect a pointer to the source code. > > > > This should use the commit id that corresponds to the release > > > > candidate tag, i.e. the commit id that corresponds to > > > > > > > https://github.com/apache/incubator-druid/tree/druid-0.15.0-incubating-rc2 > > > > AIUI only commit ids are truly immutable > > > > > > > > The NOTICE and NOTICE.BINARY files look wrong to me; they have a lot > > > > of superfluous text. > > > > > > > > > The artifacts to be voted on are located here: > > > > > > > > > > > > https://dist.apache.org/repos/dist/dev/incubator/druid/0.15.0-incubating-rc2/ > > > > > > > > > > A staged Maven repository is available for review at: > > > >
Re: Incubator PMC report timeline for July 2019
ในวันที่ ส. 22 มิ.ย. 2019 09:44 Justin Mclean เขียนว่า: > Hi, > > Here’s the timeline for the next incubator report [1] > > Wed July 03 - Podling reports due by end of day > Sun July 07 - Shepherd reviews due by end of day > Sun July 07 - Summary due by end of day > Tue July 09 - Mentor signoff due by end of day > Wed July 10 - Report submitted to Board > Wed July 17 - Board meeting > > Continuing on from last month and from this point on the report will be in > markdown format. > > Thanks, > Justin > > 1. https://cwiki.apache.org/confluence/display/INCUBATOR/July2019 > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: LGPL dependency
ในวันที่ ศ. 21 มิ.ย. 2019 15:37 申远 เขียนว่า: > Sorry for my late reply, I have open a JIRA issue[1] for this problem. > > I'm really appreciated your help here, thank you all. > > [1] https://issues.apache.org/jira/browse/LEGAL-464 > > Best Regards, > YorkShen > > 申远 > > > 申远 于2019年6月18日周二 下午8:08写道： > > > Thanks for help. > > > > I will bring this to legal-jira this weeks later. > > > > Best Regards, > > YorkShen > > > > 申远 > > > > > > Myrle Krantz 于2019年6月17日周一 下午8:07写道： > > > >> Thank you all, > >> > >> YorkShen, I think at this point the best thing to do is to open a > "legal" > >> ticket at this Jira (https://issues.apache.org/jira/browse/LEGAL). I > >> suspect that if you're only including the BSD-licensed headers, that > Weex > >> will only be dependent on BSD-licensed code. It's possible that the > >> "runtime" argument will work in this case too. > >> > >> But this discussion hasn't made me feel confident in either statement, > and > >> there are other Apache projects for which this question may be relevant. > >> I'd like a final answer and the legal committee can provide that. > >> > >> Let me know if you need help formulating the ticket. > >> > >> Best Regards, > >> Myrle > >> > >> On Fri, Jun 14, 2019 at 7:13 PM Alex Harui > >> wrote: > >> > >> > Some things I don't think have been mentioned in this thread so far: > >> > > >> > 1) Even if you make Webkit optional by offering V8, I believe the ASF > >> > criteria for "optional" includes "less than half of your users will > use > >> > that option" and so if Webkit offers better performance and most of > the > >> > users select Webkit over V8, it won't really qualify Webkit as > optional. > >> > 2) AIUI, the ASF does not care about the licensing of RUNTIMES (my > >> > emphasis) your project's code runs on. Otherwise, no ASF project > could > >> run > >> > on Windows or OSX. Apache Flex runs on Adobe Flash/AIR runtimes. > >> > 3) I could not quickly find a direct quote for this, but I believe the > >> ASF > >> > does not care about the licensing of BUILD TOOLS (emphasis mine) used > to > >> > manipulate the source in the source release as long as the license of > >> those > >> > tools does not constrain usage of that code (like some non-commercial > >> > restriction, or even a "no evil" restriction. > >> > > >> > AIUI, the whole purpose of these restrictions is to not place > >> restrictions > >> > on modifications to source or use of source when that source is > >> eventually > >> > executed (whether interpreted or compiled or other). > >> > > >> > So, if I've made that clear so far, the question I have for Weex is: > >> How > >> > is Webkit used in Weex? Is it just a runtime and libraries for that > >> > runtime? If so, then I believe it is ok to have a dependency on LGPL > >> > Webkit, but I would recommend that you find a way to not bundle Webkit > >> in > >> > the release artifacts. Have it downloaded or make it a "prerequisite" > >> just > >> > like I think every ASF Java-based project says you must install a Java > >> JDK > >> > and don't bundle Java JDKs. > >> > > >> > Other questions to ask relative to whether Webkit is a runtime or > build > >> > tool: > >> > > >> > A) Will anybody realistically want to modify the Webkit sources in > order > >> > to use Weex? If no, that's great, and another reason to not bundle > >> those > >> > header files with your sources. > >> > B) Will use of the WebKit header files and other binaries you depend > on > >> > create a restriction on use? If no, that's great as well, and I think > >> if > >> > the answer to A and B are both "no", the IPMC should consider Webkit > to > >> be > >> > a runtime/build-tool dependency and let it go. > >> > > >> > HTH, > >> > -Alex > >> > > >> > > >> > On 6/14/19, 5:09 AM, "York Shen" wrote: > >> > > >> > It depends on the definition of optional dependency. Weex targets > >> iOS, > >> > Android and Browser environment and Webkit header files and shared > >> library > >> > are only bundled for Android environment. As for other environments, > >> the OS > >> > or browser itself has exposed enough API for Weex. > >> > > >> > PS: I am pretty sure that the iOS system itself uses almost the > same > >> > code of Webkit as Weex does to build its WKWebView. It’s really > strange > >> > that’s ok for Weex iOS and not ok for Weex Android. > >> > > >> > > 在 2019年6月14日，19:17，Justin Mclean 写道： > >> > > > >> > > Hi, > >> > > > >> > >> Well, what if Weex copies some BSD header files in Webkit then > >> run > >> > on Webkit? IMHO, the Webkit is also an environment for Weex in this > >> case. > >> > > > >> > > You still didi not answer if this is an optional dependancy? But > >> > again either way I suggest you ask on legal discuss. > >> > > > >> > > Thanks, > >> > > Justin > >> > > > >> > > > >> > > > >> > > > >> - > >> > > To unsubscribe,
