Re: [IP CLEARANCE] Maven Wrapper
Dropping private list for previously mentioned reason. In order for us to accept the Takari Maven Plugin, it's currently EPL v1. We allow these to be distributed in binary form. For us to accept the plugin, I would expect an SGA from Takari allowing the relicensing. The Maven Wrapper i think is much clearer. Most of the code was actually written by individuals with ICLAs on file with the ASF. It's already Apache Licensed. It has no declared NOTICES either. To simplify things, perhaps it would be easier to have two IP clearances, one for the wrapper and one for the plugin. They should have different needs. John On Mon, Jan 6, 2020 at 4:30 PM Robert Scholte wrote: > > On 6-1-2020 22:24:09, Justin Mclean wrote: > HI, > > Confirmed IP Clearance from all active committers: > > https://lists.apache.org/thread.html/7c8fc7fa0fc677c24504d948d7d71e6cdebdb952c9ca0a2183460726%40%3Cprivate.maven.apache.org%3E > > https://lists.apache.org/thread.html/bd38cce5904d805b8526593996fcfec17ba4c8b6d8a18d66261d072c%40%3Cprivate.maven.apache.org%3E > > https://lists.apache.org/thread.html/00102361655d35ea939d44e522d9dd1fb4894af20ac418a1ef5973be%40%3Cprivate.maven.apache.org%3E > > https://lists.apache.org/thread.html/7459ee80b46bef0c2f4640700a3ee4bad46ae64bb3dad54f8c7896a3%40%3Cprivate.maven.apache.org%3E > > https://lists.apache.org/thread.html/0a9e690562ffe25ede5b601600e6b7edd5f1c70a2aaffddabbf5f85f%40%3Cprivate.maven.apache.org%3E > with this we have secured all IP for both repositories. > > > Github list 35 contributors for [1], and 7 contributors for [2] without an > SGA I think you would require ICLAs from all significant contributors, not > just current ones. > > *Robert Scholte:* > I did an analysis of all the commits. The 5 mentioned are the only > significant contributors. > Attached (if accepted) an excel sheet with all the details. > > Thanks, > Robert > > > Thanks, > Justin > > 1. https://github.com/takari/maven-wrapper/graphs/contributors > 2. https://github.com/takari/takari-maven-plugin > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org
Re: [IP CLEARANCE] Maven Wrapper
On 6-1-2020 22:24:09, Justin Mclean wrote: HI, Confirmed IP Clearance from all active committers: https://lists.apache.org/thread.html/7c8fc7fa0fc677c24504d948d7d71e6cdebdb952c9ca0a2183460726%40%3Cprivate.maven.apache.org%3E [https://lists.apache.org/thread.html/7c8fc7fa0fc677c24504d948d7d71e6cdebdb952c9ca0a2183460726%40%3Cprivate.maven.apache.org%3E] https://lists.apache.org/thread.html/bd38cce5904d805b8526593996fcfec17ba4c8b6d8a18d66261d072c%40%3Cprivate.maven.apache.org%3E [https://lists.apache.org/thread.html/bd38cce5904d805b8526593996fcfec17ba4c8b6d8a18d66261d072c%40%3Cprivate.maven.apache.org%3E] https://lists.apache.org/thread.html/00102361655d35ea939d44e522d9dd1fb4894af20ac418a1ef5973be%40%3Cprivate.maven.apache.org%3E [https://lists.apache.org/thread.html/00102361655d35ea939d44e522d9dd1fb4894af20ac418a1ef5973be%40%3Cprivate.maven.apache.org%3E] https://lists.apache.org/thread.html/7459ee80b46bef0c2f4640700a3ee4bad46ae64bb3dad54f8c7896a3%40%3Cprivate.maven.apache.org%3E [https://lists.apache.org/thread.html/7459ee80b46bef0c2f4640700a3ee4bad46ae64bb3dad54f8c7896a3%40%3Cprivate.maven.apache.org%3E] https://lists.apache.org/thread.html/0a9e690562ffe25ede5b601600e6b7edd5f1c70a2aaffddabbf5f85f%40%3Cprivate.maven.apache.org%3E [https://lists.apache.org/thread.html/0a9e690562ffe25ede5b601600e6b7edd5f1c70a2aaffddabbf5f85f%40%3Cprivate.maven.apache.org%3E] with this we have secured all IP for both repositories. Github list 35 contributors for [1], and 7 contributors for [2] without an SGA I think you would require ICLAs from all significant contributors, not just current ones. Robert Scholte: I did an analysis of all the commits. The 5 mentioned are the only significant contributors. Attached (if accepted) an excel sheet with all the details. Thanks, Robert Thanks, Justin 1. https://github.com/takari/maven-wrapper/graphs/contributors [https://github.com/takari/maven-wrapper/graphs/contributors] 2. https://github.com/takari/takari-maven-plugin [https://github.com/takari/takari-maven-plugin] maven-wrapper.xlsx Description: MS-Excel 2007 spreadsheet - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [IP CLEARANCE] Maven Wrapper
On 6-1-2020 22:14:39, Justin Mclean wrote: Hi, Can you add the information the IP clearance form please, currently it is incomplete. Distribution rights: https://github.com/takari/maven-wrapper/blob/master/LICENSE.txt [https://github.com/takari/maven-wrapper/blob/master/LICENSE.txt] https://github.com/takari/takari-maven-plugin/blob/master/LICENSE.txt [https://github.com/takari/takari-maven-plugin/blob/master/LICENSE.txt] While the ASF license allows this, we generally want explicit permission from the owners. Robert Scholte: Who are the owners here? We have explicit clearance from all active contributors. IIUC they should at least provide explicit permission. And IIUC takari is only the organisation hosting these repositories, that doesn't make them the owners. The repositories of takari.io [http://takari.io] are owned by Walmart Labs. We had good conversation with them and they were willing to donate. However, they had trouble with the text of the clearance document. Legal@ASF was involved to help, but still without result. That is a concern. Has legal@approved that the code could be transferred to the ASF without that document? Robert Scholte: No they haven't, I'll add them to the thread. Thanks, Justin
Re: [IP CLEARANCE] Maven Wrapper
HI, > Confirmed IP Clearance from all active committers: > https://lists.apache.org/thread.html/7c8fc7fa0fc677c24504d948d7d71e6cdebdb952c9ca0a2183460726%40%3Cprivate.maven.apache.org%3E > https://lists.apache.org/thread.html/bd38cce5904d805b8526593996fcfec17ba4c8b6d8a18d66261d072c%40%3Cprivate.maven.apache.org%3E > https://lists.apache.org/thread.html/00102361655d35ea939d44e522d9dd1fb4894af20ac418a1ef5973be%40%3Cprivate.maven.apache.org%3E > https://lists.apache.org/thread.html/7459ee80b46bef0c2f4640700a3ee4bad46ae64bb3dad54f8c7896a3%40%3Cprivate.maven.apache.org%3E > https://lists.apache.org/thread.html/0a9e690562ffe25ede5b601600e6b7edd5f1c70a2aaffddabbf5f85f%40%3Cprivate.maven.apache.org%3E > with this we have secured all IP for both repositories. Github list 35 contributors for [1], and 7 contributors for [2] without an SGA I think you would require ICLAs from all significant contributors, not just current ones. Thanks, Justin 1. https://github.com/takari/maven-wrapper/graphs/contributors 2. https://github.com/takari/takari-maven-plugin
Re: [DISCUSS] YuniKorn Proposal
Hi Craig, In answer to your question: *If Apache does incubate and graduate Yunikorn as a top level project, we would require Cloudera to commit to recognize Yunikorn as an Apache project in all of its materials. Otherwise, there would be confusion in the market about whether Yunikorn was an Apache project or a Cloudera project. It cannot be both.If Cloudera can commit to not using Yunikorn to describe its own project once it graduates and becomes an Apache project, ok.If not, the Apache project will need to find a new name.* -- Cloudera can commit to using Apache YuniKorn if/when the YuniKorn project graduates. Thank you, Casey *Cassandra L. Valk* | Open Source License Analyst / Sr. Contracts Manager t. (949) 201-3201 NOTICE: Prepared by a member of the Cloudera legal team. This message and any attachments may contain confidential and/or privileged information of Cloudera, Inc. and/or its affiliates. If you have received this communication in error, please advise the sender by reply email and immediately delete this message and any attachments without copying, reviewing, or disclosing the contents. Thank you for your cooperation. On Mon, Jan 6, 2020 at 1:05 PM Wangda Tan wrote: > + @Casey to answer the question since Casey may not > subscribe to incubator emails. > > Thanks > > On Sat, Dec 21, 2019 at 7:01 PM Craig Russell > wrote: > >> Hi Casey, >> >> > On Dec 20, 2019, at 10:31 AM, Casey wrote: >> > >> > Hi Folks, >> > >> > Cloudera does not have a trademark on YuniKorn; we do use the name in a >> few >> > places with a quick look. So there's no trademark assignment needed, >> but >> > if there is something else you'd like us to do related to any ownership >> > interest, please let me know. >> >> If Apache does incubate and graduate Yunikorn as a top level project, we >> would require Cloudera to commit to recognize Yunikorn as an Apache project >> in all of its materials. >> >> Otherwise, there would be confusion in the market about whether Yunikorn >> was an Apache project or a Cloudera project. It cannot be both. >> >> If Cloudera can commit to not using Yunikorn to describe its own project >> once it graduates and becomes an Apache project, ok. >> >> If not, the Apache project will need to find a new name. >> >> Regards >> Craig >> > >> > Regards, >> > Casey >> > >> > *Cassandra L. Valk* | Open Source License Analyst / Sr. Contracts >> Manager >> > t. (949) 201-3201 >> > >> > NOTICE: Prepared by a member of the Cloudera legal team. This message >> and any >> > attachments may contain confidential and/or privileged information of >> Cloudera, >> > Inc. and/or its affiliates. If you have received this communication in >> > error, please advise the sender by reply email and immediately delete >> this >> > message and any attachments without copying, reviewing, or disclosing >> the >> > contents. Thank you for your cooperation. >> > >> > >> > On Fri, Dec 20, 2019 at 1:22 PM Wangda Tan wrote: >> > >> >> Added Casey Valk from Cloudera legal team to the thread to answer the >> >> question regarding trademark of YuniKorn. >> >> >> >> Best, >> >> Wangda >> >> >> >> On Tue, Dec 17, 2019 at 10:56 PM Wangda Tan wrote: >> >> >> >>> Hi Justin/Craig, >> >>> >> >>> Thanks for sharing these information, very helpful. >> >>> >> >>> I think Cloudera doesn’t own the trademark and name. Checking with >> >>> cloudera legal now and will keep the thread posted. >> >>> >> >>> Thanks >> >>> >> >>> On Tue, Dec 17, 2019 at 2:34 PM Justin Mclean < >> jus...@classsoftware.com> >> >>> wrote: >> >>> >> Hi, >> >> Again thanks for your replies. >> >> > *"The initial committers are from several relevant Apache projects >> who >> are >> > interested in YuniKorn and committed to giving guidance, suggestions >> to the >> > project, help to grow the community; and if possible, participants >> in >> code >> > development."* >> > >> > They're aware of the PPMC requirements, I don't think there's any >> surprise >> > to proposed initial committers. >> >> That great. A long way off but just be aware that if these people are >> listed on the graduation proposal for PMC members and they have not >> been >> active in the project that may delay graduation. >> >> > We have already got SGA (Software Grant Agreement) from Cloudera, >> I'm >> not >> > sure if we need to attach the SGA now, before vote or so. Is there >> any >> > additional documentation needed apart from SGA. >> >> No you don’t need to submit an SGA before voting on the proposal, >> what >> we need is a clear indication that your name is unlikely to change >> and that >> it’s Cloudera intent to hand over rights to the name.The name would >> not >> need to be transferred until graduation. >> >> Thanks, >> Justin >> >>> >> >>> >> >> Craig L Russell >> c...@apache.org >> >>
Re: [IP CLEARANCE] Maven Wrapper
Hi, Dropping private@ have a mix of public and private lists can cause issues. > And vote of acceptance > https://lists.apache.org/thread.html/97054be79cede23c792c1db91f0fd73129ce969fea26bd12a1bf38f5%40%3Cprivate.maven.apache.org%3E It seems a little odd this was done on the private list. While only PMC votes are binding, how would you know that no other community members would object to the transfer? Has there been a public discussion about the transfer? Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [IP CLEARANCE] Maven Wrapper
Hi, Can you add the information the IP clearance form please, currently it is incomplete. > Distribution rights: > https://github.com/takari/maven-wrapper/blob/master/LICENSE.txt > https://github.com/takari/takari-maven-plugin/blob/master/LICENSE.txt While the ASF license allows this, we generally want explicit permission from the owners. > The repositories of takari.io are owned by Walmart Labs. We had good > conversation with them and they were willing to donate. > However, they had trouble with the text of the clearance document. Legal@ASF > was involved to help, but still without result. That is a concern. Has legal@approved that the code could be transferred to the ASF without that document? Thanks, Justin
Re: Fwd: [IP CLEARANCE] Maven Wrapper
And vote of acceptance https://lists.apache.org/thread.html/97054be79cede23c792c1db91f0fd73129ce969fea26bd12a1bf38f5%40%3Cprivate.maven.apache.org%3E On 6-1-2020 22:06:52, Robert Scholte wrote: Distribution rights: https://github.com/takari/maven-wrapper/blob/master/LICENSE.txt https://github.com/takari/takari-maven-plugin/blob/master/LICENSE.txt Confirmed IP Clearance from all active committers: https://lists.apache.org/thread.html/7c8fc7fa0fc677c24504d948d7d71e6cdebdb952c9ca0a2183460726%40%3Cprivate.maven.apache.org%3E https://lists.apache.org/thread.html/bd38cce5904d805b8526593996fcfec17ba4c8b6d8a18d66261d072c%40%3Cprivate.maven.apache.org%3E https://lists.apache.org/thread.html/00102361655d35ea939d44e522d9dd1fb4894af20ac418a1ef5973be%40%3Cprivate.maven.apache.org%3E https://lists.apache.org/thread.html/7459ee80b46bef0c2f4640700a3ee4bad46ae64bb3dad54f8c7896a3%40%3Cprivate.maven.apache.org%3E https://lists.apache.org/thread.html/0a9e690562ffe25ede5b601600e6b7edd5f1c70a2aaffddabbf5f85f%40%3Cprivate.maven.apache.org%3E with this we have secured all IP for both repositories. The repositories of takari.io are owned by Walmart Labs. We had good conversation with them and they were willing to donate. However, they had trouble with the text of the clearance document. Legal@ASF was involved to help, but still without result. Walmart Labs is aware of the situation, and said that if needed they could try to get the signatures. I hope this answers your questions. Robert On 6-1-2020 21:37:35, Justin Mclean wrote: forwarding to maven private list as I forgot to CC The IP clearance form is also missing a link to vote of acceptance Begin forwarded message: From: Justin Mclean mailto:jus...@classsoftware.com]> Subject: Re: [IP CLEARANCE] Maven Wrapper Date: 7 January 2020 at 7:32:18 am AEDT To: general@incubator.apache.org [mailto:general@incubator.apache.org] Reply-To: general@incubator.apache.org [mailto:general@incubator.apache.org] Hi, I don’t see that distribution rights have been confirmed. i.e Has takari (see takari.io [http://takari.io]) given permission to do this? I assume that takari is the owner of the code? If not does it belong to all of the contributors? If that’s the case have they aggreed to this? Thanks,. Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org [mailto:general-unsubscr...@incubator.apache.org] For additional commands, e-mail: general-h...@incubator.apache.org [mailto:general-h...@incubator.apache.org]
Re: Fwd: [IP CLEARANCE] Maven Wrapper
Distribution rights: https://github.com/takari/maven-wrapper/blob/master/LICENSE.txt https://github.com/takari/takari-maven-plugin/blob/master/LICENSE.txt Confirmed IP Clearance from all active committers: https://lists.apache.org/thread.html/7c8fc7fa0fc677c24504d948d7d71e6cdebdb952c9ca0a2183460726%40%3Cprivate.maven.apache.org%3E https://lists.apache.org/thread.html/bd38cce5904d805b8526593996fcfec17ba4c8b6d8a18d66261d072c%40%3Cprivate.maven.apache.org%3E https://lists.apache.org/thread.html/00102361655d35ea939d44e522d9dd1fb4894af20ac418a1ef5973be%40%3Cprivate.maven.apache.org%3E https://lists.apache.org/thread.html/7459ee80b46bef0c2f4640700a3ee4bad46ae64bb3dad54f8c7896a3%40%3Cprivate.maven.apache.org%3E https://lists.apache.org/thread.html/0a9e690562ffe25ede5b601600e6b7edd5f1c70a2aaffddabbf5f85f%40%3Cprivate.maven.apache.org%3E with this we have secured all IP for both repositories. The repositories of takari.io are owned by Walmart Labs. We had good conversation with them and they were willing to donate. However, they had trouble with the text of the clearance document. Legal@ASF was involved to help, but still without result. Walmart Labs is aware of the situation, and said that if needed they could try to get the signatures. I hope this answers your questions. Robert On 6-1-2020 21:37:35, Justin Mclean wrote: forwarding to maven private list as I forgot to CC The IP clearance form is also missing a link to vote of acceptance Begin forwarded message: From: Justin Mclean mailto:jus...@classsoftware.com]> Subject: Re: [IP CLEARANCE] Maven Wrapper Date: 7 January 2020 at 7:32:18 am AEDT To: general@incubator.apache.org [mailto:general@incubator.apache.org] Reply-To: general@incubator.apache.org [mailto:general@incubator.apache.org] Hi, I don’t see that distribution rights have been confirmed. i.e Has takari (see takari.io [http://takari.io]) given permission to do this? I assume that takari is the owner of the code? If not does it belong to all of the contributors? If that’s the case have they aggreed to this? Thanks,. Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org [mailto:general-unsubscr...@incubator.apache.org] For additional commands, e-mail: general-h...@incubator.apache.org [mailto:general-h...@incubator.apache.org]
Re: [IP CLEARANCE] Maven Wrapper
Hi, I don’t see that distribution rights have been confirmed. i.e Has takari (see takari.io) given permission to do this? I assume that takari is the owner of the code? If not does it belong to all of the contributors? If that’s the case have they aggreed to this? Thanks,. Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [IP CLEARANCE] Maven Wrapper
On 06.01.20 21:11, Robert Scholte wrote: Apache Maven received a code donation for the Maven Wrapper http://incubator.apache.org/ip-clearance/maven-wrapper.html All sources are under Apache License 2. Most likely most of the maven-wrapper code and some parts of the takari-maven-plugin will end up in Maven (core), so there will no new separate repository for this code. Next all headers will be updated according to ASF standards. Please vote to approve this contribution. Lazy consensus applies. If no -1 votes are cast within the next 72 hours, the vote passes. +1 from me Kind regards Karl Heinz Marbaise Regards, Robert - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[IP CLEARANCE] Maven Wrapper
Apache Maven received a code donation for the Maven Wrapper http://incubator.apache.org/ip-clearance/maven-wrapper.html All sources are under Apache License 2. Most likely most of the maven-wrapper code and some parts of the takari-maven-plugin will end up in Maven (core), so there will no new separate repository for this code. Next all headers will be updated according to ASF standards. Please vote to approve this contribution. Lazy consensus applies. If no -1 votes are cast within the next 72 hours, the vote passes. Regards, Robert
[VOTE] Release Apache Daffodil (incubating) 2.5.0-rc2
Hi all, The Apache Daffodil community has voted and approved the proposed release of Apache Daffodil (incubating) 2.5.0-rc2. We now kindly request the Incubator PMC members review and vote on this incubator release. Daffodil is an open source implementation of the DFDL specification that uses DFDL schemas to parse fixed format data into an infoset, which is most commonly represented as either XML or JSON. This allows the use of well-established XML or JSON technologies and libraries to consume, inspect, and manipulate fixed format data in existing solutions. Daffodil is also capable of the reverse by serializing or "unparsing" an XML or JSON infoset back to the original data format. Vote thread: https://lists.apache.org/thread.html/c8df54668fbcb7b8285f3e2cc524eac7cb82a721fa823ea5ae7edbe3%40%3Cdev.daffodil.apache.org%3E Result thread: https://lists.apache.org/thread.html/r0f67389306e448058dea657c259aa3bc0ab943a27e390071c67d2b04%40%3Cdev.daffodil.apache.org%3E All distribution packages, including signatures, digests, etc. can be found at: https://dist.apache.org/repos/dist/dev/incubator/daffodil/2.5.0-rc2/ Staging artifacts can be found at: https://repository.apache.org/content/repositories/orgapachedaffodil-1012/ This release has been signed with PGP key 36F3494B033AE661, corresponding to slawre...@apache.org, which is included in the KEYS file here: https://www.apache.org/dist/incubator/daffodil/KEYS The release candidate has been tagged in git with v2.5.0-rc2. For reference, here is a list of all closed JIRAs tagged with 2.5.0: https://s.apache.org/daffodil-issues-2.5.0 For a summary of the changes in this release, see: https://daffodil.apache.org/releases/2.5.0/ Please review and vote. The vote will be open for at least 72 hours (Thursday 9 January, 2020, 3:00 PM EST). [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, - Steve - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] YuniKorn Proposal
+ @Casey to answer the question since Casey may not subscribe to incubator emails. Thanks On Sat, Dec 21, 2019 at 7:01 PM Craig Russell wrote: > Hi Casey, > > > On Dec 20, 2019, at 10:31 AM, Casey wrote: > > > > Hi Folks, > > > > Cloudera does not have a trademark on YuniKorn; we do use the name in a > few > > places with a quick look. So there's no trademark assignment needed, but > > if there is something else you'd like us to do related to any ownership > > interest, please let me know. > > If Apache does incubate and graduate Yunikorn as a top level project, we > would require Cloudera to commit to recognize Yunikorn as an Apache project > in all of its materials. > > Otherwise, there would be confusion in the market about whether Yunikorn > was an Apache project or a Cloudera project. It cannot be both. > > If Cloudera can commit to not using Yunikorn to describe its own project > once it graduates and becomes an Apache project, ok. > > If not, the Apache project will need to find a new name. > > Regards > Craig > > > > Regards, > > Casey > > > > *Cassandra L. Valk* | Open Source License Analyst / Sr. Contracts Manager > > t. (949) 201-3201 > > > > NOTICE: Prepared by a member of the Cloudera legal team. This message > and any > > attachments may contain confidential and/or privileged information of > Cloudera, > > Inc. and/or its affiliates. If you have received this communication in > > error, please advise the sender by reply email and immediately delete > this > > message and any attachments without copying, reviewing, or disclosing the > > contents. Thank you for your cooperation. > > > > > > On Fri, Dec 20, 2019 at 1:22 PM Wangda Tan wrote: > > > >> Added Casey Valk from Cloudera legal team to the thread to answer the > >> question regarding trademark of YuniKorn. > >> > >> Best, > >> Wangda > >> > >> On Tue, Dec 17, 2019 at 10:56 PM Wangda Tan wrote: > >> > >>> Hi Justin/Craig, > >>> > >>> Thanks for sharing these information, very helpful. > >>> > >>> I think Cloudera doesn’t own the trademark and name. Checking with > >>> cloudera legal now and will keep the thread posted. > >>> > >>> Thanks > >>> > >>> On Tue, Dec 17, 2019 at 2:34 PM Justin Mclean < > jus...@classsoftware.com> > >>> wrote: > >>> > Hi, > > Again thanks for your replies. > > > *"The initial committers are from several relevant Apache projects > who > are > > interested in YuniKorn and committed to giving guidance, suggestions > to the > > project, help to grow the community; and if possible, participants in > code > > development."* > > > > They're aware of the PPMC requirements, I don't think there's any > surprise > > to proposed initial committers. > > That great. A long way off but just be aware that if these people are > listed on the graduation proposal for PMC members and they have not > been > active in the project that may delay graduation. > > > We have already got SGA (Software Grant Agreement) from Cloudera, I'm > not > > sure if we need to attach the SGA now, before vote or so. Is there > any > > additional documentation needed apart from SGA. > > No you don’t need to submit an SGA before voting on the proposal, what > we need is a clear indication that your name is unlikely to change > and that > it’s Cloudera intent to hand over rights to the name.The name would > not > need to be transferred until graduation. > > Thanks, > Justin > >>> > >>> > > Craig L Russell > c...@apache.org > >
Re: [VOTE] Release Apache IoTDB 0.9.1
+1（binding） I checked Download links are valid, git tag is OK. The kits have incubating in the name. Checksums and PGP signatures are valid. DISCLAIMER is included. LICENSE and NOTICE files are good. There is a incubating in the kits name. No binary file in the source kit. I can build the kits from source kit. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Fri, Jan 3, 2020 at 1:09 PM Lei Rui wrote: > > Hi all, > > > This is a call for vote to release Apache IoTDB (Incubating) version 0.9.1. > > > The Apache IoTDB community has voted on and approved a proposal to release > Apache IoTDB (Incubating) version 0.9.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/2b8ffe042d340001f0f5d7aeb16cb068ddc7b9141a8dd1401283e7cd%40%3Cdev.iotdb.apache.org%3E > Vote: > https://lists.apache.org/thread.html/ee976b92c2a425a3172b840980a59eb2c4dd4361be7c198489010b49%40%3Cdev.iotdb.apache.org%3E > > > The release candidates (RC1): > https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.9.1/rc1 > > > Git tag for the release (RC1): > https://github.com/apache/incubator-iotdb/releases/tag/release%2F0.9.1 > > > Hash for the release tag: > d665690607933db9fdac057ebe250c19c9f63974 > > > Release Notes: > https://github.com/apache/incubator-iotdb/blob/release/0.9.1/RELEASE_NOTES.md > > > The artifacts have been signed with Key: 28662AC6, 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 carry over 1 binding IPMC vote: > +1 from Justin Mclean > > > A minimum of 3 binding +1 votes and more binding +1 than binding -1 are > required to pass. > > > Please vote accordingly: > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove with the reason > > > Lei Rui > Apache IoTDB > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Livy 0.7.0 (incubating) based on RC3
Hi Luciano, I've fixed the license version manually, they'll be solved in next RC cut. But still I cannot find out the license for ldapsdk 4.1, this is a very old library, I doubt there's no license existed. Would you please help to check it? Thanks! And regarding to bootstrap and them files, they do existed in binary distro as a part of Livy Server. Thanks Saisai Luciano Resende 于2020年1月3日周五 上午6:11写道： > On Mon, Dec 30, 2019 at 3:43 AM Saisai Shao > wrote: > > > > The Livy PPMC has voted to release Livy 0.7.0 RC3 as the next Livy > release. > > > > Livy enables programmatic, fault-tolerant, multi-tenant submission of > > Spark jobs from web/mobile apps (no Spark client needed). So, multiple > > users can interact with your Spark cluster concurrently and reliably. > > > > Vote thread: > > > https://lists.apache.org/thread.html/ce78a69fb17b7ae1a04a51cb13949c4f726d03c43c6ebde8bbd0272f%40%3Cdev.livy.apache.org%3E > > > > Result thread: > > > https://lists.apache.org/thread.html/d030023995e4323c32e8ee68de99e48cb4f20761d5ff784ff2aac558%40%3Cdev.livy.apache.org%3E > > > > The RC is based on tag v0.7.0-incubating-rc3: > > > https://github.com/apache/incubator-livy/commit/0cc431a7e9236e313f9904ef121cad5df444d4da > > > > The release files can be found here: > > > https://dist.apache.org/repos/dist/dev/incubator/livy/0.7.0-incubating-rc3/ > > > > The staged maven artifacts can be found here: > > https://repository.apache.org/content/repositories/orgapachelivy-1012 > > > > The list of resolved JIRAs in this release can be found here: > > https://issues.apache.org/jira/projects/LIVY/versions/12345179 > > > > Vote will be open for at least 72 hours. Thanks! > > While looking into the binary distribution, it looks like the > third-party file might have been generated and has more files that > actually the ones being distributed, but my bigger issue is with a > list of dependencies with unknown licenses. > > Unknown license: > > * ASM Core (asm:asm:3.1 - http://asm.objectweb.org/asm/) > * Antlr 3.4 Runtime (org.antlr:antlr-runtime:3.4 - > http://www.antlr.org) > * Java Transaction API (javax.transaction:jta:1.1 - > http://java.sun.com/products/jta) > * Jettison (org.codehaus.jettison:jettison:1.1 - no url defined) > * commons-beanutils (commons-beanutils:commons-beanutils:1.7.0 - > no url defined) > * jsp-api (javax.servlet:jsp-api:2.0 - no url defined) > * ldapsdk (ldapsdk:ldapsdk:4.1 - no url defined) > * oro (oro:oro:2.0.8 - no url defined) > * servlet-api (javax.servlet:servlet-api:2.5 - no url defined) > * transaction-api (javax.transaction:transaction-api:1.1 - no url > defined) > * zookeeper (org.apache.zookeeper:zookeeper:3.4.6 - no url defined) > > Also, the main license lists dependencies (e.g. bootstrap and related > theme files) that I believe is only in source distro. > > I would feel more comfortable approving the release after this is > sorted out, or making this a source release only. > > -- > Luciano Resende > http://twitter.com/lresende1975 > http://lresende.blogspot.com/ > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
