Re: [MENTORS] July reports due today Wednesday 1st July
Hivemall PPMC missed the notification, sorry. Will report next month. Thanks, Makoto 2020年7月2日(木) 10:00 Justin Mclean : > > Hi, > > Report deadline is upon us and still missing are: > > AGE > Annotator > BlueMarlin > Flagon > Liminal > Livy > Warble > Weex > > If these are not submitted in the next 24 hours they will be asked to report > next month. > > Note that the board has a new process for review reports when means that > reports need to be submitted on time well before the board meeting. > > Thanks, > Justin > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > -- Makoto YUI Principal Engineer, Arm Treasure Data. http://myui.github.io/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [RESULT] [VOTE] Release Apache brpc (Incubating) 1.0.0-rc02
Good job, lorin. you have passed the whole process of release in asft. cheer. On Thu, Sep 9, 2021 at 1:46 AM Lorin Lee wrote: > Hello Incubator Community, > > > > Thanks to everyone that participated. The vote to release Apache > > brpc (Incubating) version 1.0.0 Release Candidate 2 in general@incuabator > > is now closed. > > > > Vote thread: > > https://lists.apache.org/thread.html/rfa0b690e7d162b1c8d3bfe69166ee6ec25e4f880329135d7d64f2698%40%3Cgeneral.incubator.apache.org%3E > > > > The vote PASSED with 3 binding +1, 1 non binding +1 and 0 -1 votes: > > > > Binding votes: > > - Xun Liu > > - Juan Pan > > - Zhenxu Ke > > > > Non-binding votes: > > - CalvinKirs > > > > I will be working on publishing the artifacts of Apache brpc > > (Incubating) 1.0.0 and post an announcement. Thanks! > > > > Regards, > > Lorin Lee > > Apache brpc (Incubating) >
[RESULT] [VOTE] Release Apache brpc (Incubating) 1.0.0-rc02
Hello Incubator Community, Thanks to everyone that participated. The vote to release Apache brpc (Incubating) version 1.0.0 Release Candidate 2 in general@incuabator is now closed. Vote thread: https://lists.apache.org/thread.html/rfa0b690e7d162b1c8d3bfe69166ee6ec25e4f880329135d7d64f2698%40%3Cgeneral.incubator.apache.org%3E The vote PASSED with 3 binding +1, 1 non binding +1 and 0 -1 votes: Binding votes: - Xun Liu - Juan Pan - Zhenxu Ke Non-binding votes: - CalvinKirs I will be working on publishing the artifacts of Apache brpc (Incubating) 1.0.0 and post an announcement. Thanks! Regards, Lorin Lee Apache brpc (Incubating)
Re: [VOTE] Release Apache brpc (Incubating) 1.0.0-rc02
Hello Incubator Community, Thanks to everyone that participated. The vote to release Apache brpc (Incubating) version 1.0.0 Release Candidate 2 in general@incuabator is now closed. The vote PASSED with 3 binding +1, 1 non binding +1 and 0 -1 votes: Binding votes: - Xun Liu - Juan Pan - Zhenxu Ke Non-binding votes: - CalvinKirs I will be working on publishing the artifacts of Apache brpc (Incubating) 1.0.0 and post an announcement. Thanks! Regards, Lorin Lee Apache brpc (Incubating) Jerry Tan 于2021年9月6日周一 上午9:08写道： > Hi， Lorin > > the voting time has passed， > you can reply to this mail with the closing vote. > > then you can open a new thread to announce the release. > thanks. > > On 2021/08/31 12:52:40, Lorin Lee wrote: > > Hello IPMC, > > > > > > > > The Apache brpc community has voted and approved the release of Apache > > > > brpc (Incubating) 1.0.0-rc02. We now kindly request the IPMC members > > > > review and vote for this release. > > > > > > > > brpc is an industrial-grade RPC framework with extremely high > performance, > > and it supports multiple protocols, full rpc features, and has many > > convenient tools. The current release provides the first official and > > stable package, resolves all of the license issues, and fixes many bugs. > > > > > > > > brpc community vote thread: > > > > > https://lists.apache.org/thread.html/rcdf94f507621ac72226b848e3c2ff7c1e1509e37f4926011398a7a2b%40%3Cdev.brpc.apache.org%3E > > > > > > > > Vote result thread: > > > > > https://lists.apache.org/thread.html/r04525259b2044b7118d71418c065cf6173e85c149c0125bb99795c8e%40%3Cdev.brpc.apache.org%3E > > > > > > > > The release candidate: > > > > https://dist.apache.org/repos/dist/dev/incubator/brpc/1.0.0-rc02/ > > > > > > > > This release has been signed with a PGP available here: > > > > https://dist.apache.org/repos/dist/dev/incubator/brpc/KEYS > > > > > > > > Git tag for the release: > > > > https://github.com/apache/incubator-brpc/releases/tag/1.0.0-rc02 > > > > > > > > Build guide and get started instructions can be found at: > > > > > https://github.com/apache/incubator-brpc/blob/master/docs/en/getting_started.md > > > > > > > > The vote will be open for at least 72 hours or until the necessary number > > > > of votes is reached. > > > > > > > > Please vote accordingly: > > > > [ ] +1 Approve the release of Apache brpc (Incubating) 1.0.0-rc02 > > > > [ ] +0 > > > > [ ] -1 Do not approve (please specify the reason) > > > > > > > > Regards, > > > > Lorin Lee > > > > Apache brpc (Incubating) > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [IP CLEARANCE] Apache AsterixDB - JDBC Driver
On Wed, Sep 8, 2021 at 11:11 David Jencks wrote: > I’m watching from the sidelines…. > > IIUC you are saying that if AsterixDB started over with a history-free > tarball for this donation this whole question of validating the source > origin would not arise and we’d just trust the SGA? No not at all. If the donation came with the original headers and we knew that the donor had done due diligence when developing the software internally to confirm the source of all lines of code followed regular licensing practices we would have less concern. The big issue is that the donor changed the license headers before donating. There’s actually no usable history in the GitHub repo as best as I can tell. > > While some history is nice to have, I’m not sure it’s worth this > conversation. > > David Jencks > > > On Sep 7, 2021, at 5:42 PM, John D. Ament wrote: > > > > Hi Till > > > > fwiw I think the donation is fine though the AsterixDB PMC will need to > do > > some due diligence in verifying ownership of code before forming a > release. > > This is likely what Justin is trying to refer to as well. > > > > Some background on possible issues…. > > > > Before GitHub became the popular place to do this when a donation was > > received a tar ball without any history was the preferred method to > receive > > it. Since the donation was put on GitHub it leaves some ambiguity with > the > > actual history of the code. The ASF headers already applied create some > > additional cautiousness here - no one can validate 100% that the code > being > > donated can actually be claimed by couchbase. No way to see if some code > > was lifted via stack overflow or taken from a GPL library. > > > > So here’s my +1 with the cautionary note about validating the original > > source of each line of code. > > > > John > > > > > > On Tue, Sep 7, 2021 at 19:01 Till Westmann wrote: > > > >> Hi Justin, > >> > >> On 3 Sep 2021, at 0:46, Justin Mclean wrote: > >> > Please help me understand why > - the software grant from Couchbase and > - the acceptance from the AsterixDB project > are not sufficient to approve this donation. > >>> > >>> Because IMO the information provided doesn’t give sufficient detail > >>> to determine who has contributed to the codebase, the history of > >>> contributions has been hidden, the IP ownership of files can't really > >>> be determined from what has been provided and previous questions by > >>> the IPMC on this donation went unanswered. > >> > >> On our "Contributor Agreements" page [1] we say: > >> > >> "When an individual or corporation [in this case a corporation] decides > >> to donate a body of existing software or documentation to one of the > >> Apache projects, they need to execute a formal Software Grant Agreement > >> (SGA) with the ASF [which has been executed and recorded]. Typically, > >> they do this after negotiating approval with the ASF Incubator or one of > >> the PMCs [in this case the AsterixDB PMC], since the ASF does not accept > >> software unless there is a viable community available to support it as > >> part of a collaborative project." > >> > >> The code has been developed by developers working for Couchbase and the > >> IP is owned by the corporation. Couchbase has executed the SGA and has > >> specified which code is contributed to the ASF under the terms of the > >> SGA. As the AsterixDB PMC has voted to accept the donation it seems that > >> all requirements to accept the donation are met. > >> > >> Wasn't the SGA design for cases like this where a corporation (and not > >> an individual) contributes code to an Apache project? > >> > >> On your questions: > >> Q: Where was this code original developed and who worked on it? There is > >> only a couple of commits in that repro, so it doesn’t seem to have > >> been developed there. > >> A: This code was originally developed by multiple developers working for > >> Couchbase. The names of current and former developers at Couchbase who > >> have worked on it (and who largely do not have an ICLA on file) seem to > >> be immaterial for the IP question as an SGA is recorded. > >> > >> Q: Why does the code have ASF headers on it before being donated? Were > >> any 3rd party headers removed? > >> A: The repository with the Apache license headers was created with the > >> purpose of being donated to the ASF. Couchbase's copyright notices were > >> removed from the source files and corresponding NOTICE files were added. > >> ASF headers were added to files that did not have license headers and > >> regular Apache License headers were replaced with the ASF headers. > >> > >> Q: Have all contributors signed ICLAs and/or do we have a SGA from > >> CouchBase? > >> A: A SGA has been executed and recorded. Not all contributors have > >> signed an ICLA, but that also seems immaterial as the SGA is available. > >> > >> Regards, > >> Till > >> > >> [1] https://www.apache.org/licenses/contributor-agreements.html#grants > >> >
Re: [IP CLEARANCE] Apache AsterixDB - JDBC Driver
I’m watching from the sidelines…. IIUC you are saying that if AsterixDB started over with a history-free tarball for this donation this whole question of validating the source origin would not arise and we’d just trust the SGA? While some history is nice to have, I’m not sure it’s worth this conversation. David Jencks > On Sep 7, 2021, at 5:42 PM, John D. Ament wrote: > > Hi Till > > fwiw I think the donation is fine though the AsterixDB PMC will need to do > some due diligence in verifying ownership of code before forming a release. > This is likely what Justin is trying to refer to as well. > > Some background on possible issues…. > > Before GitHub became the popular place to do this when a donation was > received a tar ball without any history was the preferred method to receive > it. Since the donation was put on GitHub it leaves some ambiguity with the > actual history of the code. The ASF headers already applied create some > additional cautiousness here - no one can validate 100% that the code being > donated can actually be claimed by couchbase. No way to see if some code > was lifted via stack overflow or taken from a GPL library. > > So here’s my +1 with the cautionary note about validating the original > source of each line of code. > > John > > > On Tue, Sep 7, 2021 at 19:01 Till Westmann wrote: > >> Hi Justin, >> >> On 3 Sep 2021, at 0:46, Justin Mclean wrote: >> Please help me understand why - the software grant from Couchbase and - the acceptance from the AsterixDB project are not sufficient to approve this donation. >>> >>> Because IMO the information provided doesn’t give sufficient detail >>> to determine who has contributed to the codebase, the history of >>> contributions has been hidden, the IP ownership of files can't really >>> be determined from what has been provided and previous questions by >>> the IPMC on this donation went unanswered. >> >> On our "Contributor Agreements" page [1] we say: >> >> "When an individual or corporation [in this case a corporation] decides >> to donate a body of existing software or documentation to one of the >> Apache projects, they need to execute a formal Software Grant Agreement >> (SGA) with the ASF [which has been executed and recorded]. Typically, >> they do this after negotiating approval with the ASF Incubator or one of >> the PMCs [in this case the AsterixDB PMC], since the ASF does not accept >> software unless there is a viable community available to support it as >> part of a collaborative project." >> >> The code has been developed by developers working for Couchbase and the >> IP is owned by the corporation. Couchbase has executed the SGA and has >> specified which code is contributed to the ASF under the terms of the >> SGA. As the AsterixDB PMC has voted to accept the donation it seems that >> all requirements to accept the donation are met. >> >> Wasn't the SGA design for cases like this where a corporation (and not >> an individual) contributes code to an Apache project? >> >> On your questions: >> Q: Where was this code original developed and who worked on it? There is >> only a couple of commits in that repro, so it doesn’t seem to have >> been developed there. >> A: This code was originally developed by multiple developers working for >> Couchbase. The names of current and former developers at Couchbase who >> have worked on it (and who largely do not have an ICLA on file) seem to >> be immaterial for the IP question as an SGA is recorded. >> >> Q: Why does the code have ASF headers on it before being donated? Were >> any 3rd party headers removed? >> A: The repository with the Apache license headers was created with the >> purpose of being donated to the ASF. Couchbase's copyright notices were >> removed from the source files and corresponding NOTICE files were added. >> ASF headers were added to files that did not have license headers and >> regular Apache License headers were replaced with the ASF headers. >> >> Q: Have all contributors signed ICLAs and/or do we have a SGA from >> CouchBase? >> A: A SGA has been executed and recorded. Not all contributors have >> signed an ICLA, but that also seems immaterial as the SGA is available. >> >> Regards, >> Till >> >> [1] https://www.apache.org/licenses/contributor-agreements.html#grants >> >> - >> 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: subscibe
Thanks, tison. I'll re-send an email to general-subscribe. tison 于2021年9月8日周三 下午7:26写道： > I guess you should send to the -subscribe address instead. > > Best, > tison. > > > Aloys Zhang 于2021年9月8日周三 下午7:22写道： > >> subscribe >> -- >> Best, >> Aloys. >> > -- Best, Aloys.
Re: subscibe
I guess you should send to the -subscribe address instead. Best, tison. Aloys Zhang 于2021年9月8日周三 下午7:22写道： > subscribe > -- > Best, > Aloys. >
subscibe
subscribe -- Best, Aloys.
Re: [ANNOUNCE] Apache Annotator (incubating) 0.2.0 release
Fixed, thanks for reporting! On 08/09/2021 01.04, sebb wrote: > https://annotator.apache.org/www.apache.org/dist/incubator/annotator/KEYS > is not a valid keys link. > > Looks like someone omitted the 'https://' prefix. > > Please fix. > On Sun, 5 Sept 2021 at 13:57, sebb wrote: >> On Fri, 3 Sept 2021 at 13:43, Gerben wrote: >>> Dear community, >>> >>> The Apache Annotator (incubating) community is pleased to announce the >>> release of Apache Annotator (incubating) 0.2.0. >>> >>> Apache Annotator (incubating) provides libraries to enable annotation >>> related software, with an initial focus on identification of textual >>> fragments in browser environments. >>> >>> These are the main changes since v0.1.0: >>> >>> - all code is converted to TypeScript >>> - the API is documented >>> - many tests have been added >>> - npm package names changed from “@annotator/…” to “@apache-annotator/…” >>> - a meta-package was added that includes all the others in one package >>> - it now supports TextPositionSelector >>> - it now supports CssSelector in both directions (match & describe) >>> - steps were made to apply text matching algorithms to other environments >>> than the DOM >>> - and many small fixes, tweaks and improvements >>> >>> Download links: >>> https://annotator.apache.org/ >> The KEYS link is broken. >> >>> The release tag: >>> https://github.com/apache/incubator-annotator/releases/tag/v0.2.0 >>> >>> With regards on behalf of the team, >>> >>> — Gerben >>>
Re: [VOTE] Release Apache InLong(Incubating) 0.10.0-incubating RC1
Thanks, @Xun Liu The first problem, we have already explained in DISCLAIMER-WIP, and will be fixed in the later version; The second question is that the English are not good enough, we are looking for resources for processing. Xun Liu 于2021年9月8日周三 上午11:18写道： > Hi, Charles > > I have checked the following items: > - Incubating in name > - LICENSE and NOTICE are fine > - DISCLAIMER-WIP exists > - All links are valid > - All ASF files have ASF headers > > But, I have two question, > 1. I see that the incubator-inlong project contains jar package references > for mysql-connect and berkeleydb. [9][10] > As far as I know, if we provide the incubator-inlong.tar.gz package if > these two jar files are included, there should be licene problems. > We can't include these two files in incubator-inlong.tar.gz. There is a way > to solve this problem. > You can let users automatically download these two jar packages when they > run the incubator-inlong server start script. > I want to know how this issue is handled before I can vote. > > 2. In addition, I looked at the incubator-inlong english version website > https://inlong.apache.org/en-us/. > There are some web pages and pictures that mix Chinese and English. [1]~[8] > It may be necessary to gradually unify the description of text and pictures > in the future to reduce user confusion. > This question is not urgent and can be modified next time. > > [1] https://inlong.apache.org/en-us/docs/example.html > [2] https://inlong.apache.org/en-us/docs/modules/manager/user_manual.html > [3] https://inlong.apache.org/en-us/docs/development/how-to-commit.html > [4] https://inlong.apache.org/en-us/docs/development/how-to-subscribe.html > [5] > > https://inlong.apache.org/en-us/docs/development/how-to-become-a-committer.html > [6] > > https://inlong.apache.org/en-us/docs/development/how-to-vote-a-committer-ppmc.html > [7] https://inlong.apache.org/en-us/docs/development/how-to-release.html > [8] https://inlong.apache.org/en-us/docs/development/how-to-verify.html > [9] > > https://github.com/apache/incubator-inlong/blob/master/inlong-tubemq/tubemq-manager/pom.xml#L130 > [10] > > https://github.com/apache/incubator-inlong/blob/master/inlong-tubemq/pom.xml#L87 > > > Best regards > Xun Liu > > On Mon, Sep 6, 2021 at 10:22 AM Charles Zhang > wrote: > > > Hello Incubator Community, > > > > This is a call for a vote to release Apache InLong(Incubating) > version > > 0.10.0-incubating RC1 > > > > The Apache InLong community has voted on and approved a proposal to > > release > > Apache InLong(Incubating) version 0.10.0-incubating RC1 > > > > We now kindly request the Incubator PMC members review and vote on > this > > incubator release. > > > > InLong community vote thread: > > • > > > https://lists.apache.org/thread.html/r196ad2dd2a6c5421b3c618988ed9d3c9e53369c83acee0df6e46ae0c%40%3Cdev.inlong.apache.org%3E > > > > Vote result thread: > > • > > > https://lists.apache.org/thread.html/r97902e0592e439daad192c919b36fab045da9021fe8038a4221a5af0%40%3Cdev.inlong.apache.org%3E > > > > The release candidate: > > • > > > https://dist.apache.org/repos/dist/dev/incubator/inlong/0.10.0-incubating-RC1/ > > > > Git tag for the release: > > • > > https://github.com/apache/incubator-inlong/tree/0.10.0-incubating-RC1 > > > > Release notes: > > • > > > https://github.com/apache/incubator-inlong/releases/tag/0.10.0-incubating-RC1 > > > > The artifacts signed with PGP key A4D4D578, corresponding to > > dockerzh...@apache.org, that can be found in the keys file: > > • https://dist.apache.org/repos/dist/dev/incubator/inlong/KEYS > > > > The vote will be open for at least 72 hours or until a necessary > > number of votes are reached. > > > > Please vote accordingly: > > > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove with the reason > > > > Thanks, > > On behalf of Apache InLong(Incubating) community > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > >
