Re: [VOTE] Accept HertzBeat Into the ASF Incubator
+ 1 (binding) As a mentor, I shared apache culture with the init committers. They showed great interest in learning apache culture, and were very willing to pass on the apache culture in China. The apache way is the ours project way. Best wishes! PJ Fanning 于2024年3月29日周五 21:20写道： > > +1 binding - looks like a good candidate for the Apache Incubator > > On Fri, 29 Mar 2024 at 14:17, Sheng Wu wrote: > > > > I am not holding anything. I didn't vote -1. > > > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > > > John D. Ament 于2024年3月29日周五 21:13写道： > > > > > > On Fri, Mar 29, 2024 at 8:41 AM Sheng Wu > > > wrote: > > > > > > > Hi > > > > > > > > Yes, a project doesn't have to separate the repository into two for > > > > both website and source codes, once the license has been reviewed. > > > > Calcite is another TLP, which is guaranteed, so it is on their PMC > > > > oversight. > > > > > > > > My suggestion is based on things that may not be suitable in your > > > > final release, such as logos from other vendors, > > > > https://github.com/dromara/hertzbeat/tree/master/home/static/img/icons. > > > > Those may be available to use on your website, but not available for > > > > source tar. Such as Apple Inc. logo is included currently. > > > > - https://github.com/dromara/hertzbeat/tree/master/home/static/img/icons > > > > - > > > > https://github.com/dromara/hertzbeat/blob/master/home/static/img/icons/ios.svg > > > > > > > > > > > > > > > I don't understand what you're trying to ask the proposed project to do. > > > It seems like you're holding them to a bar that is above what podlings are > > > expected to follow when coming in to even be considered accepted to the > > > ASF. I don't think any of this needs to be resolved before we accept the > > > project, we all know that there's a period between when the project leaves > > > its former home and enters its new home that they are in transition and > > > need to make a large number of changes. > > > > > > None of this blocks acceptance, looks like a great addition > > > +1 from me. > > > > > > John > > > > > > > > > > Sheng Wu 吴晟 > > > > Twitter, wusheng1108 > > > > > > > > Francis Chuang 于2024年3月29日周五 15:47写道： > > > > > > > > > > Thanks, Chao Gong, for addressing those issues in > > > > > > > > > https://github.com/dromara/hertzbeat/commit/1284914c4a2d42c8355417c164810787fb64e588 > > > > > > > > > > Looking at the updated website, the issues raised have been taken care > > > > of. > > > > > > > > > > Regarding keeping the website's source code and project code in the > > > > > project repository, I don't think it's 100% necessary to separate the > > > > > website into a separate repository. > > > > > > > > > > For Calcite, our site is in the same repository as our code: > > > > > https://github.com/apache/calcite/tree/main/site > > > > > > > > > > We include the correct licenses in the LICENSE file when we build a > > > > > release, using a template: > > > > > https://github.com/apache/calcite/blob/main/LICENSE > > > > > > > > > > Francis > > > > > > > > > > On 29/03/2024 6:05 pm, Sheng Wu wrote: > > > > > > Some things should be fixed > > > > > > > > > > > > 1. At the top of the home page, > > > > > GitHub⭐️⭐️> exists, this should be removed. > > > > > > 2. At the top menu, exists, I don't think this project > > > > > > is Huawei, and please don't use another vendor's brand. > > > > > > 3. Similar with <2>, but for OSPP. That is also another org brand. > > > > > > 4. When I first lands on the homepage, there is a pop up box to ask > > > > > > me > > > > > > star on GitHub. This should be removed too. GitHub repository is > > > > > > just > > > > > > a bi-way synced mirror repository. ASF has its own code repository, > > > > > > which is also the main repository to make sure vendor neutral. > > > > > > > > > > > > A thing you should fix later, your website source codes and > > > > > > resources > > > > > > are in the same repository. Those things may not be able to be > > > > > > included considering the license and binaries(png, videos) may be > > > > > > included. In the ASF, website is usually a separate repository. > > > > > > But the in your proposal seems not included. > > > > > > Please > > > > > > reach your mentors and fix the proposal. > > > > > > > > > > > > Sheng Wu 吴晟 > > > > > > Twitter, wusheng1108 > > > > > > > > > > > > Zhang Yonglun 于2024年3月29日周五 14:24写道： > > > > > >> > > > > > >> Hi Incubator, > > > > > >> > > > > > >> Following the discussion [DISCUSS] Incubating Proposal for > > > > HertzBeat[1], > > > > > >> I am starting this official vote for the HertzBeat project. > > > > > >> > > > > > >> Here is their proposal: > > > > > >> > > > > https://cwiki.apache.org/confluence/display/INCUBATOR/HertzBeatProposal > > > > > >> > > > > > >> Please cast your vote: > > > > > >> > > > > > >> [ ] +1, bring into the Incubator > > > > > >> [ ] +0, I don't care either way > > > > > >> [ ] -1, do not bring HertzBeat into the Incubator, b
Re: [IP CLEARANCE] Apache Pekko Connectors AWS SPI
On Mar 29, 2024, at 10:47, John D. Ament wrote: > > On Fri, Mar 29, 2024 at 11:13 AM Craig Russell wrote: > >> I read the IP-Clearance and this seems to be pretty straightforward: >> >> The code has already been partly adjusted to use Pekko - >> https://github.com/pjfanning/aws-spi-pekko-http >> >> It is our intention to bring the code in >> https://github.com/pjfanning/aws-spi-pekko-http into Apache Pekko. The >> code in that repo is forked from >> https://github.com/matsluni/aws-spi-akka-http and Matthias Lüneberg has >> submitted a Software Grant Agreement (SGA) to allow us to use his original >> commits. >> > > So just to confirm - there's no issue from your perspective that the fork > predates the SGA? I believe that's my only actual concern, and being able > to show it clearer is really what I'm trying to say here (but jumping > straight to how to do it instead of properly conveying the problem I see). > > John There are no restrictions on the grant. So to me that means that there is no time box for the grant. The grant should be good before, during, and after the fork. Craig > > >> >> The original code written by Matthias Lüneberg was granted to ASF and PJ >> has forked the project. There are no restrictions in the grant as to what >> commit is being granted. The entire repository is covered by the grant. >> >> I do not see a problem. >> Craig >> >>> On Mar 29, 2024, at 06:42, John D. Ament wrote: >>> >>> On Fri, Mar 29, 2024 at 9:32 AM PJ Fanning wrote: >>> The Software Grant is on file with the ASF Secretary. I don't know where these are checked in but the file is referenced in the grants.txt in the foundation svn repo. The template file makes no reference to commit ids. https://www.apache.org/licenses/software-grant-template.pdf Matthias has basically given us permission to use his Apache licensed code. I am not a lawyer but I think is reasonable to assume that all commits to his repo up the SGA date are covered. I have an iCLA so all my commits to my fork are surely acceptable to the ASF? I don't see why listing commit IDs makes the IP Clearance clearer. I can't see commit IDs in any of the cross section of previous clearance forms I have seen. >>> >>> Commit ID is simply one way it's been done. There's a few examples, I'll >>> list them below. But basically reading your IP form it isn't clear which >>> repo is actually being brought into Pekko, perhaps a PR would work as >>> well? There's a couple of examples like that in this list too. Anything >>> that you feel could be done to make it clearer that it's your repo being >>> brought in but going through IP Clearance/SGA due to the derived work >>> clause (otherwise, it's not clear why you as an officer of the foundation >>> need an IP Clearance to bring in your own work). >>> >>> [1]: https://incubator.apache.org/ip-clearance/arrow-datafusion-comet >>> (Donation PR w/ repo being stood up by us for the target donation) >>> [2]: >> https://incubator.apache.org/ip-clearance/daffodil-vscode-debugger.html >>> (Full original repo and commit ID) >>> [3]: https://incubator.apache.org/ip-clearance/avro-rust-library.html >> (Full >>> original repo and PR) >>> [4]: https://incubator.apache.org/ip-clearance/tinkerpop-gremlint.html >>> (Commit ID) >>> [5]: https://incubator.apache.org/ip-clearance/tika-tika-helm.html (Full >>> original repo pointer) >>> [6]: >>> >> https://incubator.apache.org/ip-clearance/netbeans-dukescript-presenters.html >>> (Commit ID and PR) >>> [7]: https://incubator.apache.org/ip-clearance/pekko-http-cors.html >>> (Original repo and PR) >>> >>> On Fri, 29 Mar 2024 at 14:19, John D. Ament >> wrote: > > On Fri, Mar 29, 2024 at 8:34 AM PJ Fanning >> wrote: > >> Hi John, >> My GitHub repo [1] is a fork of Matthias Lüneberg's repo [2]. His >> original repo was built for Akka. My fork modifies it to use Pekko >> instead. >> So it is my code that is being imported but the SGA is to acknowledge >> that the original code was written by Matthias Lüneberg. >> We can't bring my fork into Apache Pekko itself without Matthias >> Lüneberg's software grant. >> >> [1] https://github.com/pjfanning/aws-spi-pekko-http >> [2] https://github.com/matsluni/aws-spi-akka-http > > > Ok, I see, you previously created a derived work from the original author's > work, and I'm assuming you approached the author about donating to the ASF > via SGA which they did so that you can bring the derived work into >> Pekko. > To make that clearer, I would update the IP Clearance to state that the > code being imported is from your repo at whatever commit hash which was > forked from the original author's work as of whatever commit hash. > > Was the forked repo's commit hash recorded on the SGA? > > >> >>
Re: [IP CLEARANCE] Apache Pekko Connectors AWS SPI
On Fri, Mar 29, 2024 at 11:13 AM Craig Russell wrote: > I read the IP-Clearance and this seems to be pretty straightforward: > > The code has already been partly adjusted to use Pekko - > https://github.com/pjfanning/aws-spi-pekko-http > > It is our intention to bring the code in > https://github.com/pjfanning/aws-spi-pekko-http into Apache Pekko. The > code in that repo is forked from > https://github.com/matsluni/aws-spi-akka-http and Matthias Lüneberg has > submitted a Software Grant Agreement (SGA) to allow us to use his original > commits. > So just to confirm - there's no issue from your perspective that the fork predates the SGA? I believe that's my only actual concern, and being able to show it clearer is really what I'm trying to say here (but jumping straight to how to do it instead of properly conveying the problem I see). John > > The original code written by Matthias Lüneberg was granted to ASF and PJ > has forked the project. There are no restrictions in the grant as to what > commit is being granted. The entire repository is covered by the grant. > > I do not see a problem. > Craig > > > On Mar 29, 2024, at 06:42, John D. Ament wrote: > > > > On Fri, Mar 29, 2024 at 9:32 AM PJ Fanning wrote: > > > >> The Software Grant is on file with the ASF Secretary. I don't know > >> where these are checked in but the file is referenced in the > >> grants.txt in the foundation svn repo. > >> > >> The template file makes no reference to commit ids. > >> > >> https://www.apache.org/licenses/software-grant-template.pdf > >> > >> Matthias has basically given us permission to use his Apache licensed > >> code. I am not a lawyer but I think is reasonable to assume that all > >> commits to his repo up the SGA date are covered. > >> > >> I have an iCLA so all my commits to my fork are surely acceptable to the > >> ASF? > >> > >> I don't see why listing commit IDs makes the IP Clearance clearer. I > >> can't see commit IDs in any of the cross section of previous clearance > >> forms I have seen. > >> > > > > Commit ID is simply one way it's been done. There's a few examples, I'll > > list them below. But basically reading your IP form it isn't clear which > > repo is actually being brought into Pekko, perhaps a PR would work as > > well? There's a couple of examples like that in this list too. Anything > > that you feel could be done to make it clearer that it's your repo being > > brought in but going through IP Clearance/SGA due to the derived work > > clause (otherwise, it's not clear why you as an officer of the foundation > > need an IP Clearance to bring in your own work). > > > > [1]: https://incubator.apache.org/ip-clearance/arrow-datafusion-comet > > (Donation PR w/ repo being stood up by us for the target donation) > > [2]: > https://incubator.apache.org/ip-clearance/daffodil-vscode-debugger.html > > (Full original repo and commit ID) > > [3]: https://incubator.apache.org/ip-clearance/avro-rust-library.html > (Full > > original repo and PR) > > [4]: https://incubator.apache.org/ip-clearance/tinkerpop-gremlint.html > > (Commit ID) > > [5]: https://incubator.apache.org/ip-clearance/tika-tika-helm.html (Full > > original repo pointer) > > [6]: > > > https://incubator.apache.org/ip-clearance/netbeans-dukescript-presenters.html > > (Commit ID and PR) > > [7]: https://incubator.apache.org/ip-clearance/pekko-http-cors.html > > (Original repo and PR) > > > > > >> > >> On Fri, 29 Mar 2024 at 14:19, John D. Ament > wrote: > >>> > >>> On Fri, Mar 29, 2024 at 8:34 AM PJ Fanning > wrote: > >>> > Hi John, > My GitHub repo [1] is a fork of Matthias Lüneberg's repo [2]. His > original repo was built for Akka. My fork modifies it to use Pekko > instead. > So it is my code that is being imported but the SGA is to acknowledge > that the original code was written by Matthias Lüneberg. > We can't bring my fork into Apache Pekko itself without Matthias > Lüneberg's software grant. > > [1] https://github.com/pjfanning/aws-spi-pekko-http > [2] https://github.com/matsluni/aws-spi-akka-http > >>> > >>> > >>> Ok, I see, you previously created a derived work from the original > >> author's > >>> work, and I'm assuming you approached the author about donating to the > >> ASF > >>> via SGA which they did so that you can bring the derived work into > Pekko. > >>> To make that clearer, I would update the IP Clearance to state that the > >>> code being imported is from your repo at whatever commit hash which was > >>> forked from the original author's work as of whatever commit hash. > >>> > >>> Was the forked repo's commit hash recorded on the SGA? > >>> > >>> > > > On Fri, 29 Mar 2024 at 13:14, John D. Ament > >> wrote: > > > > I’m a little confused. You’re referring to a third party Matthias > Luneberg > > but the code reference is pointing to the officer’s personal GitHub > > account. > > > > Which is being imported? >
Re: [VOTE] Release Apache Answer(Incubating) v1.3.0-RC1
+1 non-binding I checked: [x] Download links are valid. [x] Checksums and PGP signatures are validgpg: Signature made Mon Mar 25 11:51:25 2024 CST gpg:using RSA key 5684B6E344546A5F3CE9850D380DCBD5C34934CC gpg: Good signature from "LinkinStar (for apache release create at 20231220) " [ultimate]. [x] Source code distributions have correct names matching the current release. [x] LICENSE and NOTICE files are correct for each Answer repo. [x] All files have license headers if necessary. [x] Can compile on macOS(arm64) nit: I noticed that the email template's checklist doesn't have a "Can compile or not" step, so maybe we could add that. Sincerely, Suyan LinkinStar 于2024年3月29日周五 15:46写道： > > Hello, > > This is a call for vote to release Apache Answer(Incubating) version > v1.3.0-RC1. > > The vote thread: > https://lists.apache.org/thread/8pbh6047ogmdcf3ypdg4kr1k8gzxx6vf > > Vote Result: > https://lists.apache.org/thread/q3d6pgr1rq30ldzfn82gdq1h0qzmgylx > > The release candidates: > > https://dist.apache.org/repos/dist/dev/incubator/answer/1.3.0-incubating-RC1/ > > Release notes: > https://github.com/apache/incubator-answer/releases/tag/v1.3.0-RC1 > > Git tag for the release: > https://github.com/apache/incubator-answer/releases/tag/v1.3.0-RC1 > > Git commit id for the release: > > https://github.com/apache/incubator-answer/commit/9ebf95cacecf49ff466e47f3ff54c180eb67627c > > Keys to verify the Release Candidate: > The artifacts signed with PGP key [C34934CC], corresponding to [ > linkins...@apache.org], that can be found in keys file: > https://dist.apache.org/repos/dist/release/incubator/answer/KEYS > > The vote will be open for at least 72 hours or until the necessary > number of votes are reached. > > Please vote accordingly: > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove with the reason > > Checklist for reference: > > [ ] Download links are valid. > [ ] Checksums and PGP signatures are valid. > [ ] Source code distributions have correct names matching the current > release. > [ ] LICENSE and NOTICE files are correct for each Answer repo. > [ ] All files have license headers if necessary. > [ ] No unlicensed compiled archives bundled in source archive. > > To compile from the source, please refer to: > > https://github.com/apache/incubator-answer#building-from-source > > Thanks, > LinkinStar - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache HugeGraph(Incubating) 1.3.0-rc1
+1 non-binding I checked: [x] Download links are valid [x] Checksums and signatures. apache-hugegraph-ai-incubating-1.3.0-src.tar.gz gpg: Signature made Mon Mar 25 14:40:14 2024 CST gpg:using RSA key 12CEB4C81B4F1E358B8A1A181B75F4C00CAB214C gpg: Good signature from "JackyYang " [ultimate] apache-hugegraph-commons-incubating-1.3.0-src.tar.gz gpg: Signature made Sun Mar 24 17:48:23 2024 CST gpg:using RSA key 12CEB4C81B4F1E358B8A1A181B75F4C00CAB214C gpg: Good signature from "JackyYang " [ultimate] apache-hugegraph-incubating-1.3.0-src.tar.gz gpg: Signature made Sun Mar 24 18:21:51 2024 CST gpg:using RSA key 12CEB4C81B4F1E358B8A1A181B75F4C00CAB214C gpg: Good signature from "JackyYang " [ultimate] apache-hugegraph-incubating-1.3.0.tar.gz gpg: Signature made Sun Mar 24 18:21:52 2024 CST gpg:using RSA key 12CEB4C81B4F1E358B8A1A181B75F4C00CAB214C gpg: Good signature from "JackyYang " [ultimate] apache-hugegraph-toolchain-incubating-1.3.0-src.tar.gz gpg: Signature made Sun Mar 24 18:49:03 2024 CST gpg:using RSA key 12CEB4C81B4F1E358B8A1A181B75F4C00CAB214C gpg: Good signature from "JackyYang " [ultimate] apache-hugegraph-toolchain-incubating-1.3.0.tar.gz gpg: Signature made Sun Mar 24 18:49:05 2024 CST gpg:using RSA key 12CEB4C81B4F1E358B8A1A181B75F4C00CAB214C gpg: Good signature from "JackyYang " [ultimate] [x] LICENSE/NOTICE files exist [x] Can compile from source on macOS(arm64) [INFO] [INFO] Reactor Summary for hugegraph 1.3.0: [INFO] [INFO] hugegraph .. SUCCESS [ 24.163 s] [INFO] hugegraph-server ... SUCCESS [ 14.007 s] [INFO] hugegraph-core . SUCCESS [02:59 min] [INFO] hugegraph-api .. SUCCESS [02:03 min] [INFO] hugegraph-cassandra SUCCESS [01:07 min] [INFO] hugegraph-scylladb . SUCCESS [ 0.824 s] [INFO] hugegraph-rocksdb .. SUCCESS [ 5.175 s] [INFO] hugegraph-mysql SUCCESS [ 2.025 s] [INFO] hugegraph-palo . SUCCESS [ 0.671 s] [INFO] hugegraph-hbase SUCCESS [ 9.450 s] [INFO] hugegraph-postgresql ... SUCCESS [ 2.274 s] [INFO] hugegraph-dist . SUCCESS [ 27.070 s] [INFO] hugegraph-example .. SUCCESS [ 1.459 s] [INFO] hugegraph-test . SUCCESS [ 50.349 s] [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 08:29 min [INFO] Finished at: 2024-03-29T23:30:36+08:00 [INFO] Sincerely, Suyan Jacky Yang 于2024年3月29日周五 10:19写道： > > Hello Incubator Community, > > This is a call for a vote to release Apache HugeGraph(Incubating) > version 1.3.0-rc1 > > The Apache HugeGraph community has voted on and approved a proposal to release > Apache HugeGraph(Incubating) version 1.3.0-rc1 > > We now kindly request the Incubator PMC members review and vote on this > incubator release. > > HugeGraph community vote thread: > • https://lists.apache.org/thread/80t2qqq7tmszm20l7ztosx4fpkhld50l > > Vote result thread: > • https://lists.apache.org/thread/wymh634mxc0l3y0j7vy9jx1bdw48d5g0 > > The release candidate: > • https://dist.apache.org/repos/dist/dev/incubator/hugegraph/1.3.0 > > Git tag for the release: > • https://github.com/apache/incubator-hugegraph/tree/1.3.0 > > Git tag & Commit hash for the release: > • https://github.com/apache/incubator-hugegraph/tree/release-1.3.0 > (6a4041e) > • https://github.com/apache/incubator-hugegraph-toolchain/tree/release-1.3.0 > (0dd2339) > • https://github.com/apache/incubator-hugegraph-commons/tree/release-1.3.0 > (c883f56) > • https://github.com/apache/incubator-hugegraph-ai/tree/release-1.3.0 > (4f48116) > > Keys to verify the Release Candidate: > • https://downloads.apache.org/incubator/hugegraph/KEYS > > The release GPG user ID: JackyYang (yangji...@apache.org) > > > The vote will be open for at least 72 hours or until necessary number > of votes are reached. > > Please vote accordingly: > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove with the reason > > More detail checklist please refer: > • > https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist > > Steps to validate the release，Please refer to: > • > https://hugegraph.apache.org/docs/contribution-guidelines/validate-release/ > (EN) > • > https://hugegraph.apache.org/cn/docs/contribution-guideli
Re: [IP CLEARANCE] Apache Pekko Connectors AWS SPI
I read the IP-Clearance and this seems to be pretty straightforward: The code has already been partly adjusted to use Pekko - https://github.com/pjfanning/aws-spi-pekko-http It is our intention to bring the code in https://github.com/pjfanning/aws-spi-pekko-http into Apache Pekko. The code in that repo is forked from https://github.com/matsluni/aws-spi-akka-http and Matthias Lüneberg has submitted a Software Grant Agreement (SGA) to allow us to use his original commits. The original code written by Matthias Lüneberg was granted to ASF and PJ has forked the project. There are no restrictions in the grant as to what commit is being granted. The entire repository is covered by the grant. I do not see a problem. Craig > On Mar 29, 2024, at 06:42, John D. Ament wrote: > > On Fri, Mar 29, 2024 at 9:32 AM PJ Fanning wrote: > >> The Software Grant is on file with the ASF Secretary. I don't know >> where these are checked in but the file is referenced in the >> grants.txt in the foundation svn repo. >> >> The template file makes no reference to commit ids. >> >> https://www.apache.org/licenses/software-grant-template.pdf >> >> Matthias has basically given us permission to use his Apache licensed >> code. I am not a lawyer but I think is reasonable to assume that all >> commits to his repo up the SGA date are covered. >> >> I have an iCLA so all my commits to my fork are surely acceptable to the >> ASF? >> >> I don't see why listing commit IDs makes the IP Clearance clearer. I >> can't see commit IDs in any of the cross section of previous clearance >> forms I have seen. >> > > Commit ID is simply one way it's been done. There's a few examples, I'll > list them below. But basically reading your IP form it isn't clear which > repo is actually being brought into Pekko, perhaps a PR would work as > well? There's a couple of examples like that in this list too. Anything > that you feel could be done to make it clearer that it's your repo being > brought in but going through IP Clearance/SGA due to the derived work > clause (otherwise, it's not clear why you as an officer of the foundation > need an IP Clearance to bring in your own work). > > [1]: https://incubator.apache.org/ip-clearance/arrow-datafusion-comet > (Donation PR w/ repo being stood up by us for the target donation) > [2]: https://incubator.apache.org/ip-clearance/daffodil-vscode-debugger.html > (Full original repo and commit ID) > [3]: https://incubator.apache.org/ip-clearance/avro-rust-library.html (Full > original repo and PR) > [4]: https://incubator.apache.org/ip-clearance/tinkerpop-gremlint.html > (Commit ID) > [5]: https://incubator.apache.org/ip-clearance/tika-tika-helm.html (Full > original repo pointer) > [6]: > https://incubator.apache.org/ip-clearance/netbeans-dukescript-presenters.html > (Commit ID and PR) > [7]: https://incubator.apache.org/ip-clearance/pekko-http-cors.html > (Original repo and PR) > > >> >> On Fri, 29 Mar 2024 at 14:19, John D. Ament wrote: >>> >>> On Fri, Mar 29, 2024 at 8:34 AM PJ Fanning wrote: >>> Hi John, My GitHub repo [1] is a fork of Matthias Lüneberg's repo [2]. His original repo was built for Akka. My fork modifies it to use Pekko instead. So it is my code that is being imported but the SGA is to acknowledge that the original code was written by Matthias Lüneberg. We can't bring my fork into Apache Pekko itself without Matthias Lüneberg's software grant. [1] https://github.com/pjfanning/aws-spi-pekko-http [2] https://github.com/matsluni/aws-spi-akka-http >>> >>> >>> Ok, I see, you previously created a derived work from the original >> author's >>> work, and I'm assuming you approached the author about donating to the >> ASF >>> via SGA which they did so that you can bring the derived work into Pekko. >>> To make that clearer, I would update the IP Clearance to state that the >>> code being imported is from your repo at whatever commit hash which was >>> forked from the original author's work as of whatever commit hash. >>> >>> Was the forked repo's commit hash recorded on the SGA? >>> >>> On Fri, 29 Mar 2024 at 13:14, John D. Ament >> wrote: > > I’m a little confused. You’re referring to a third party Matthias Luneberg > but the code reference is pointing to the officer’s personal GitHub > account. > > Which is being imported? > > John > > > On Wed, Mar 27, 2024 at 14:04 PJ Fanning >> wrote: > >> Hi everyone, >> >> Apache Pekko is receiving a donation of an AWS SPI. >> The AWS SPI is used to make client calls to AWS APIs and is built >> using Apache Pekko HTTP. We use the AWS SPI in a few of the Apache >> Pekko Connectors. >> >> Please vote to approve this contribution. >> This is a lazy consensus majority vote, per the IP clearance >> process >> [2], open for at least 72 hours. >> >> Thanks, >>
Re: [IP CLEARANCE] Apache Pekko Connectors AWS SPI
On Fri, Mar 29, 2024 at 9:32 AM PJ Fanning wrote: > The Software Grant is on file with the ASF Secretary. I don't know > where these are checked in but the file is referenced in the > grants.txt in the foundation svn repo. > > The template file makes no reference to commit ids. > > https://www.apache.org/licenses/software-grant-template.pdf > > Matthias has basically given us permission to use his Apache licensed > code. I am not a lawyer but I think is reasonable to assume that all > commits to his repo up the SGA date are covered. > > I have an iCLA so all my commits to my fork are surely acceptable to the > ASF? > > I don't see why listing commit IDs makes the IP Clearance clearer. I > can't see commit IDs in any of the cross section of previous clearance > forms I have seen. > Commit ID is simply one way it's been done. There's a few examples, I'll list them below. But basically reading your IP form it isn't clear which repo is actually being brought into Pekko, perhaps a PR would work as well? There's a couple of examples like that in this list too. Anything that you feel could be done to make it clearer that it's your repo being brought in but going through IP Clearance/SGA due to the derived work clause (otherwise, it's not clear why you as an officer of the foundation need an IP Clearance to bring in your own work). [1]: https://incubator.apache.org/ip-clearance/arrow-datafusion-comet (Donation PR w/ repo being stood up by us for the target donation) [2]: https://incubator.apache.org/ip-clearance/daffodil-vscode-debugger.html (Full original repo and commit ID) [3]: https://incubator.apache.org/ip-clearance/avro-rust-library.html (Full original repo and PR) [4]: https://incubator.apache.org/ip-clearance/tinkerpop-gremlint.html (Commit ID) [5]: https://incubator.apache.org/ip-clearance/tika-tika-helm.html (Full original repo pointer) [6]: https://incubator.apache.org/ip-clearance/netbeans-dukescript-presenters.html (Commit ID and PR) [7]: https://incubator.apache.org/ip-clearance/pekko-http-cors.html (Original repo and PR) > > On Fri, 29 Mar 2024 at 14:19, John D. Ament wrote: > > > > On Fri, Mar 29, 2024 at 8:34 AM PJ Fanning wrote: > > > > > Hi John, > > > My GitHub repo [1] is a fork of Matthias Lüneberg's repo [2]. His > > > original repo was built for Akka. My fork modifies it to use Pekko > > > instead. > > > So it is my code that is being imported but the SGA is to acknowledge > > > that the original code was written by Matthias Lüneberg. > > > We can't bring my fork into Apache Pekko itself without Matthias > > > Lüneberg's software grant. > > > > > > [1] https://github.com/pjfanning/aws-spi-pekko-http > > > [2] https://github.com/matsluni/aws-spi-akka-http > > > > > > Ok, I see, you previously created a derived work from the original > author's > > work, and I'm assuming you approached the author about donating to the > ASF > > via SGA which they did so that you can bring the derived work into Pekko. > > To make that clearer, I would update the IP Clearance to state that the > > code being imported is from your repo at whatever commit hash which was > > forked from the original author's work as of whatever commit hash. > > > > Was the forked repo's commit hash recorded on the SGA? > > > > > > > > > > > > > On Fri, 29 Mar 2024 at 13:14, John D. Ament > wrote: > > > > > > > > I’m a little confused. You’re referring to a third party Matthias > > > Luneberg > > > > but the code reference is pointing to the officer’s personal GitHub > > > > account. > > > > > > > > Which is being imported? > > > > > > > > John > > > > > > > > > > > > On Wed, Mar 27, 2024 at 14:04 PJ Fanning > wrote: > > > > > > > > > Hi everyone, > > > > > > > > > > Apache Pekko is receiving a donation of an AWS SPI. > > > > > The AWS SPI is used to make client calls to AWS APIs and is built > > > > > using Apache Pekko HTTP. We use the AWS SPI in a few of the Apache > > > > > Pekko Connectors. > > > > > > > > > > Please vote to approve this contribution. > > > > > This is a lazy consensus majority vote, per the IP clearance > process > > > > > [2], open for at least 72 hours. > > > > > > > > > > Thanks, > > > > > PJ > > > > > > > > > > [1] > > > > > > > > > https://incubator.apache.org/ip-clearance/pekko-connectors-aws-spi.html > > > > > [2] https://incubator.apache.org/ip-clearance/ > > > > > > > > > > > - > > > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > > > > > > > > > - > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
Re: [IP CLEARANCE] Apache Pekko Connectors AWS SPI
The Software Grant is on file with the ASF Secretary. I don't know where these are checked in but the file is referenced in the grants.txt in the foundation svn repo. The template file makes no reference to commit ids. https://www.apache.org/licenses/software-grant-template.pdf Matthias has basically given us permission to use his Apache licensed code. I am not a lawyer but I think is reasonable to assume that all commits to his repo up the SGA date are covered. I have an iCLA so all my commits to my fork are surely acceptable to the ASF? I don't see why listing commit IDs makes the IP Clearance clearer. I can't see commit IDs in any of the cross section of previous clearance forms I have seen. On Fri, 29 Mar 2024 at 14:19, John D. Ament wrote: > > On Fri, Mar 29, 2024 at 8:34 AM PJ Fanning wrote: > > > Hi John, > > My GitHub repo [1] is a fork of Matthias Lüneberg's repo [2]. His > > original repo was built for Akka. My fork modifies it to use Pekko > > instead. > > So it is my code that is being imported but the SGA is to acknowledge > > that the original code was written by Matthias Lüneberg. > > We can't bring my fork into Apache Pekko itself without Matthias > > Lüneberg's software grant. > > > > [1] https://github.com/pjfanning/aws-spi-pekko-http > > [2] https://github.com/matsluni/aws-spi-akka-http > > > Ok, I see, you previously created a derived work from the original author's > work, and I'm assuming you approached the author about donating to the ASF > via SGA which they did so that you can bring the derived work into Pekko. > To make that clearer, I would update the IP Clearance to state that the > code being imported is from your repo at whatever commit hash which was > forked from the original author's work as of whatever commit hash. > > Was the forked repo's commit hash recorded on the SGA? > > > > > > > > On Fri, 29 Mar 2024 at 13:14, John D. Ament wrote: > > > > > > I’m a little confused. You’re referring to a third party Matthias > > Luneberg > > > but the code reference is pointing to the officer’s personal GitHub > > > account. > > > > > > Which is being imported? > > > > > > John > > > > > > > > > On Wed, Mar 27, 2024 at 14:04 PJ Fanning wrote: > > > > > > > Hi everyone, > > > > > > > > Apache Pekko is receiving a donation of an AWS SPI. > > > > The AWS SPI is used to make client calls to AWS APIs and is built > > > > using Apache Pekko HTTP. We use the AWS SPI in a few of the Apache > > > > Pekko Connectors. > > > > > > > > Please vote to approve this contribution. > > > > This is a lazy consensus majority vote, per the IP clearance process > > > > [2], open for at least 72 hours. > > > > > > > > Thanks, > > > > PJ > > > > > > > > [1] > > > > > > https://incubator.apache.org/ip-clearance/pekko-connectors-aws-spi.html > > > > [2] https://incubator.apache.org/ip-clearance/ > > > > > > > > - > > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept HertzBeat Into the ASF Incubator
+1 binding - looks like a good candidate for the Apache Incubator On Fri, 29 Mar 2024 at 14:17, Sheng Wu wrote: > > I am not holding anything. I didn't vote -1. > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > John D. Ament 于2024年3月29日周五 21:13写道： > > > > On Fri, Mar 29, 2024 at 8:41 AM Sheng Wu wrote: > > > > > Hi > > > > > > Yes, a project doesn't have to separate the repository into two for > > > both website and source codes, once the license has been reviewed. > > > Calcite is another TLP, which is guaranteed, so it is on their PMC > > > oversight. > > > > > > My suggestion is based on things that may not be suitable in your > > > final release, such as logos from other vendors, > > > https://github.com/dromara/hertzbeat/tree/master/home/static/img/icons. > > > Those may be available to use on your website, but not available for > > > source tar. Such as Apple Inc. logo is included currently. > > > - https://github.com/dromara/hertzbeat/tree/master/home/static/img/icons > > > - > > > https://github.com/dromara/hertzbeat/blob/master/home/static/img/icons/ios.svg > > > > > > > > > > > I don't understand what you're trying to ask the proposed project to do. > > It seems like you're holding them to a bar that is above what podlings are > > expected to follow when coming in to even be considered accepted to the > > ASF. I don't think any of this needs to be resolved before we accept the > > project, we all know that there's a period between when the project leaves > > its former home and enters its new home that they are in transition and > > need to make a large number of changes. > > > > None of this blocks acceptance, looks like a great addition > > +1 from me. > > > > John > > > > > > > Sheng Wu 吴晟 > > > Twitter, wusheng1108 > > > > > > Francis Chuang 于2024年3月29日周五 15:47写道： > > > > > > > > Thanks, Chao Gong, for addressing those issues in > > > > > > > https://github.com/dromara/hertzbeat/commit/1284914c4a2d42c8355417c164810787fb64e588 > > > > > > > > Looking at the updated website, the issues raised have been taken care > > > of. > > > > > > > > Regarding keeping the website's source code and project code in the > > > > project repository, I don't think it's 100% necessary to separate the > > > > website into a separate repository. > > > > > > > > For Calcite, our site is in the same repository as our code: > > > > https://github.com/apache/calcite/tree/main/site > > > > > > > > We include the correct licenses in the LICENSE file when we build a > > > > release, using a template: > > > > https://github.com/apache/calcite/blob/main/LICENSE > > > > > > > > Francis > > > > > > > > On 29/03/2024 6:05 pm, Sheng Wu wrote: > > > > > Some things should be fixed > > > > > > > > > > 1. At the top of the home page, > > > > GitHub⭐️⭐️> exists, this should be removed. > > > > > 2. At the top menu, exists, I don't think this project > > > > > is Huawei, and please don't use another vendor's brand. > > > > > 3. Similar with <2>, but for OSPP. That is also another org brand. > > > > > 4. When I first lands on the homepage, there is a pop up box to ask me > > > > > star on GitHub. This should be removed too. GitHub repository is just > > > > > a bi-way synced mirror repository. ASF has its own code repository, > > > > > which is also the main repository to make sure vendor neutral. > > > > > > > > > > A thing you should fix later, your website source codes and resources > > > > > are in the same repository. Those things may not be able to be > > > > > included considering the license and binaries(png, videos) may be > > > > > included. In the ASF, website is usually a separate repository. > > > > > But the in your proposal seems not included. Please > > > > > reach your mentors and fix the proposal. > > > > > > > > > > Sheng Wu 吴晟 > > > > > Twitter, wusheng1108 > > > > > > > > > > Zhang Yonglun 于2024年3月29日周五 14:24写道： > > > > >> > > > > >> Hi Incubator, > > > > >> > > > > >> Following the discussion [DISCUSS] Incubating Proposal for > > > HertzBeat[1], > > > > >> I am starting this official vote for the HertzBeat project. > > > > >> > > > > >> Here is their proposal: > > > > >> > > > https://cwiki.apache.org/confluence/display/INCUBATOR/HertzBeatProposal > > > > >> > > > > >> Please cast your vote: > > > > >> > > > > >> [ ] +1, bring into the Incubator > > > > >> [ ] +0, I don't care either way > > > > >> [ ] -1, do not bring HertzBeat into the Incubator, because... > > > > >> > > > > >> The vote will open for one week from today. > > > > >> > > > > >> [1] https://lists.apache.org/thread/snxcdyvqgvhgjdmfv4l192g9tdf8w7rn > > > > >> > > > > >> Best Regards, > > > > >> Zhang Yonglun > > > > >> > > > > >> - > > > > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > > >> For additional commands, e-mail: general-h...@incubator.apache.org > > > > >> > > > > > > > > > >
Re: [IP CLEARANCE] Apache Pekko Connectors AWS SPI
On Fri, Mar 29, 2024 at 8:34 AM PJ Fanning wrote: > Hi John, > My GitHub repo [1] is a fork of Matthias Lüneberg's repo [2]. His > original repo was built for Akka. My fork modifies it to use Pekko > instead. > So it is my code that is being imported but the SGA is to acknowledge > that the original code was written by Matthias Lüneberg. > We can't bring my fork into Apache Pekko itself without Matthias > Lüneberg's software grant. > > [1] https://github.com/pjfanning/aws-spi-pekko-http > [2] https://github.com/matsluni/aws-spi-akka-http Ok, I see, you previously created a derived work from the original author's work, and I'm assuming you approached the author about donating to the ASF via SGA which they did so that you can bring the derived work into Pekko. To make that clearer, I would update the IP Clearance to state that the code being imported is from your repo at whatever commit hash which was forked from the original author's work as of whatever commit hash. Was the forked repo's commit hash recorded on the SGA? > > > On Fri, 29 Mar 2024 at 13:14, John D. Ament wrote: > > > > I’m a little confused. You’re referring to a third party Matthias > Luneberg > > but the code reference is pointing to the officer’s personal GitHub > > account. > > > > Which is being imported? > > > > John > > > > > > On Wed, Mar 27, 2024 at 14:04 PJ Fanning wrote: > > > > > Hi everyone, > > > > > > Apache Pekko is receiving a donation of an AWS SPI. > > > The AWS SPI is used to make client calls to AWS APIs and is built > > > using Apache Pekko HTTP. We use the AWS SPI in a few of the Apache > > > Pekko Connectors. > > > > > > Please vote to approve this contribution. > > > This is a lazy consensus majority vote, per the IP clearance process > > > [2], open for at least 72 hours. > > > > > > Thanks, > > > PJ > > > > > > [1] > > > > https://incubator.apache.org/ip-clearance/pekko-connectors-aws-spi.html > > > [2] https://incubator.apache.org/ip-clearance/ > > > > > > - > > > 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] Accept HertzBeat Into the ASF Incubator
I am not holding anything. I didn't vote -1. Sheng Wu 吴晟 Twitter, wusheng1108 John D. Ament 于2024年3月29日周五 21:13写道： > > On Fri, Mar 29, 2024 at 8:41 AM Sheng Wu wrote: > > > Hi > > > > Yes, a project doesn't have to separate the repository into two for > > both website and source codes, once the license has been reviewed. > > Calcite is another TLP, which is guaranteed, so it is on their PMC > > oversight. > > > > My suggestion is based on things that may not be suitable in your > > final release, such as logos from other vendors, > > https://github.com/dromara/hertzbeat/tree/master/home/static/img/icons. > > Those may be available to use on your website, but not available for > > source tar. Such as Apple Inc. logo is included currently. > > - https://github.com/dromara/hertzbeat/tree/master/home/static/img/icons > > - > > https://github.com/dromara/hertzbeat/blob/master/home/static/img/icons/ios.svg > > > > > > > I don't understand what you're trying to ask the proposed project to do. > It seems like you're holding them to a bar that is above what podlings are > expected to follow when coming in to even be considered accepted to the > ASF. I don't think any of this needs to be resolved before we accept the > project, we all know that there's a period between when the project leaves > its former home and enters its new home that they are in transition and > need to make a large number of changes. > > None of this blocks acceptance, looks like a great addition > +1 from me. > > John > > > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > > > Francis Chuang 于2024年3月29日周五 15:47写道： > > > > > > Thanks, Chao Gong, for addressing those issues in > > > > > https://github.com/dromara/hertzbeat/commit/1284914c4a2d42c8355417c164810787fb64e588 > > > > > > Looking at the updated website, the issues raised have been taken care > > of. > > > > > > Regarding keeping the website's source code and project code in the > > > project repository, I don't think it's 100% necessary to separate the > > > website into a separate repository. > > > > > > For Calcite, our site is in the same repository as our code: > > > https://github.com/apache/calcite/tree/main/site > > > > > > We include the correct licenses in the LICENSE file when we build a > > > release, using a template: > > > https://github.com/apache/calcite/blob/main/LICENSE > > > > > > Francis > > > > > > On 29/03/2024 6:05 pm, Sheng Wu wrote: > > > > Some things should be fixed > > > > > > > > 1. At the top of the home page, > > > GitHub⭐️⭐️> exists, this should be removed. > > > > 2. At the top menu, exists, I don't think this project > > > > is Huawei, and please don't use another vendor's brand. > > > > 3. Similar with <2>, but for OSPP. That is also another org brand. > > > > 4. When I first lands on the homepage, there is a pop up box to ask me > > > > star on GitHub. This should be removed too. GitHub repository is just > > > > a bi-way synced mirror repository. ASF has its own code repository, > > > > which is also the main repository to make sure vendor neutral. > > > > > > > > A thing you should fix later, your website source codes and resources > > > > are in the same repository. Those things may not be able to be > > > > included considering the license and binaries(png, videos) may be > > > > included. In the ASF, website is usually a separate repository. > > > > But the in your proposal seems not included. Please > > > > reach your mentors and fix the proposal. > > > > > > > > Sheng Wu 吴晟 > > > > Twitter, wusheng1108 > > > > > > > > Zhang Yonglun 于2024年3月29日周五 14:24写道： > > > >> > > > >> Hi Incubator, > > > >> > > > >> Following the discussion [DISCUSS] Incubating Proposal for > > HertzBeat[1], > > > >> I am starting this official vote for the HertzBeat project. > > > >> > > > >> Here is their proposal: > > > >> > > https://cwiki.apache.org/confluence/display/INCUBATOR/HertzBeatProposal > > > >> > > > >> Please cast your vote: > > > >> > > > >> [ ] +1, bring into the Incubator > > > >> [ ] +0, I don't care either way > > > >> [ ] -1, do not bring HertzBeat into the Incubator, because... > > > >> > > > >> The vote will open for one week from today. > > > >> > > > >> [1] https://lists.apache.org/thread/snxcdyvqgvhgjdmfv4l192g9tdf8w7rn > > > >> > > > >> Best Regards, > > > >> Zhang Yonglun > > > >> > > > >> - > > > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > >> For additional commands, e-mail: general-h...@incubator.apache.org > > > >> > > > > > > > > - > > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > > > - > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > For additional commands, e-mail:
Re: [VOTE] Accept HertzBeat Into the ASF Incubator
On Fri, Mar 29, 2024 at 8:41 AM Sheng Wu wrote: > Hi > > Yes, a project doesn't have to separate the repository into two for > both website and source codes, once the license has been reviewed. > Calcite is another TLP, which is guaranteed, so it is on their PMC > oversight. > > My suggestion is based on things that may not be suitable in your > final release, such as logos from other vendors, > https://github.com/dromara/hertzbeat/tree/master/home/static/img/icons. > Those may be available to use on your website, but not available for > source tar. Such as Apple Inc. logo is included currently. > - https://github.com/dromara/hertzbeat/tree/master/home/static/img/icons > - > https://github.com/dromara/hertzbeat/blob/master/home/static/img/icons/ios.svg > > > I don't understand what you're trying to ask the proposed project to do. It seems like you're holding them to a bar that is above what podlings are expected to follow when coming in to even be considered accepted to the ASF. I don't think any of this needs to be resolved before we accept the project, we all know that there's a period between when the project leaves its former home and enters its new home that they are in transition and need to make a large number of changes. None of this blocks acceptance, looks like a great addition +1 from me. John > Sheng Wu 吴晟 > Twitter, wusheng1108 > > Francis Chuang 于2024年3月29日周五 15:47写道： > > > > Thanks, Chao Gong, for addressing those issues in > > > https://github.com/dromara/hertzbeat/commit/1284914c4a2d42c8355417c164810787fb64e588 > > > > Looking at the updated website, the issues raised have been taken care > of. > > > > Regarding keeping the website's source code and project code in the > > project repository, I don't think it's 100% necessary to separate the > > website into a separate repository. > > > > For Calcite, our site is in the same repository as our code: > > https://github.com/apache/calcite/tree/main/site > > > > We include the correct licenses in the LICENSE file when we build a > > release, using a template: > > https://github.com/apache/calcite/blob/main/LICENSE > > > > Francis > > > > On 29/03/2024 6:05 pm, Sheng Wu wrote: > > > Some things should be fixed > > > > > > 1. At the top of the home page, > > GitHub⭐️⭐️> exists, this should be removed. > > > 2. At the top menu, exists, I don't think this project > > > is Huawei, and please don't use another vendor's brand. > > > 3. Similar with <2>, but for OSPP. That is also another org brand. > > > 4. When I first lands on the homepage, there is a pop up box to ask me > > > star on GitHub. This should be removed too. GitHub repository is just > > > a bi-way synced mirror repository. ASF has its own code repository, > > > which is also the main repository to make sure vendor neutral. > > > > > > A thing you should fix later, your website source codes and resources > > > are in the same repository. Those things may not be able to be > > > included considering the license and binaries(png, videos) may be > > > included. In the ASF, website is usually a separate repository. > > > But the in your proposal seems not included. Please > > > reach your mentors and fix the proposal. > > > > > > Sheng Wu 吴晟 > > > Twitter, wusheng1108 > > > > > > Zhang Yonglun 于2024年3月29日周五 14:24写道： > > >> > > >> Hi Incubator, > > >> > > >> Following the discussion [DISCUSS] Incubating Proposal for > HertzBeat[1], > > >> I am starting this official vote for the HertzBeat project. > > >> > > >> Here is their proposal: > > >> > https://cwiki.apache.org/confluence/display/INCUBATOR/HertzBeatProposal > > >> > > >> Please cast your vote: > > >> > > >> [ ] +1, bring into the Incubator > > >> [ ] +0, I don't care either way > > >> [ ] -1, do not bring HertzBeat into the Incubator, because... > > >> > > >> The vote will open for one week from today. > > >> > > >> [1] https://lists.apache.org/thread/snxcdyvqgvhgjdmfv4l192g9tdf8w7rn > > >> > > >> Best Regards, > > >> Zhang Yonglun > > >> > > >> - > > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > >> For additional commands, e-mail: general-h...@incubator.apache.org > > >> > > > > > > - > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Accept HertzBeat Into the ASF Incubator
Hi Yes, a project doesn't have to separate the repository into two for both website and source codes, once the license has been reviewed. Calcite is another TLP, which is guaranteed, so it is on their PMC oversight. My suggestion is based on things that may not be suitable in your final release, such as logos from other vendors, https://github.com/dromara/hertzbeat/tree/master/home/static/img/icons. Those may be available to use on your website, but not available for source tar. Such as Apple Inc. logo is included currently. - https://github.com/dromara/hertzbeat/tree/master/home/static/img/icons - https://github.com/dromara/hertzbeat/blob/master/home/static/img/icons/ios.svg Sheng Wu 吴晟 Twitter, wusheng1108 Francis Chuang 于2024年3月29日周五 15:47写道： > > Thanks, Chao Gong, for addressing those issues in > https://github.com/dromara/hertzbeat/commit/1284914c4a2d42c8355417c164810787fb64e588 > > Looking at the updated website, the issues raised have been taken care of. > > Regarding keeping the website's source code and project code in the > project repository, I don't think it's 100% necessary to separate the > website into a separate repository. > > For Calcite, our site is in the same repository as our code: > https://github.com/apache/calcite/tree/main/site > > We include the correct licenses in the LICENSE file when we build a > release, using a template: > https://github.com/apache/calcite/blob/main/LICENSE > > Francis > > On 29/03/2024 6:05 pm, Sheng Wu wrote: > > Some things should be fixed > > > > 1. At the top of the home page, > GitHub⭐️⭐️> exists, this should be removed. > > 2. At the top menu, exists, I don't think this project > > is Huawei, and please don't use another vendor's brand. > > 3. Similar with <2>, but for OSPP. That is also another org brand. > > 4. When I first lands on the homepage, there is a pop up box to ask me > > star on GitHub. This should be removed too. GitHub repository is just > > a bi-way synced mirror repository. ASF has its own code repository, > > which is also the main repository to make sure vendor neutral. > > > > A thing you should fix later, your website source codes and resources > > are in the same repository. Those things may not be able to be > > included considering the license and binaries(png, videos) may be > > included. In the ASF, website is usually a separate repository. > > But the in your proposal seems not included. Please > > reach your mentors and fix the proposal. > > > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > > > Zhang Yonglun 于2024年3月29日周五 14:24写道： > >> > >> Hi Incubator, > >> > >> Following the discussion [DISCUSS] Incubating Proposal for HertzBeat[1], > >> I am starting this official vote for the HertzBeat project. > >> > >> Here is their proposal: > >> https://cwiki.apache.org/confluence/display/INCUBATOR/HertzBeatProposal > >> > >> Please cast your vote: > >> > >> [ ] +1, bring into the Incubator > >> [ ] +0, I don't care either way > >> [ ] -1, do not bring HertzBeat into the Incubator, because... > >> > >> The vote will open for one week from today. > >> > >> [1] https://lists.apache.org/thread/snxcdyvqgvhgjdmfv4l192g9tdf8w7rn > >> > >> Best Regards, > >> Zhang Yonglun > >> > >> - > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > >> For additional commands, e-mail: general-h...@incubator.apache.org > >> > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [IP CLEARANCE] Apache Pekko Connectors AWS SPI
Hi John, My GitHub repo [1] is a fork of Matthias Lüneberg's repo [2]. His original repo was built for Akka. My fork modifies it to use Pekko instead. So it is my code that is being imported but the SGA is to acknowledge that the original code was written by Matthias Lüneberg. We can't bring my fork into Apache Pekko itself without Matthias Lüneberg's software grant. [1] https://github.com/pjfanning/aws-spi-pekko-http [2] https://github.com/matsluni/aws-spi-akka-http On Fri, 29 Mar 2024 at 13:14, John D. Ament wrote: > > I’m a little confused. You’re referring to a third party Matthias Luneberg > but the code reference is pointing to the officer’s personal GitHub > account. > > Which is being imported? > > John > > > On Wed, Mar 27, 2024 at 14:04 PJ Fanning wrote: > > > Hi everyone, > > > > Apache Pekko is receiving a donation of an AWS SPI. > > The AWS SPI is used to make client calls to AWS APIs and is built > > using Apache Pekko HTTP. We use the AWS SPI in a few of the Apache > > Pekko Connectors. > > > > Please vote to approve this contribution. > > This is a lazy consensus majority vote, per the IP clearance process > > [2], open for at least 72 hours. > > > > Thanks, > > PJ > > > > [1] > > https://incubator.apache.org/ip-clearance/pekko-connectors-aws-spi.html > > [2] https://incubator.apache.org/ip-clearance/ > > > > - > > 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: [IP CLEARANCE] Apache Pekko Connectors AWS SPI
I’m a little confused. You’re referring to a third party Matthias Luneberg but the code reference is pointing to the officer’s personal GitHub account. Which is being imported? John On Wed, Mar 27, 2024 at 14:04 PJ Fanning wrote: > Hi everyone, > > Apache Pekko is receiving a donation of an AWS SPI. > The AWS SPI is used to make client calls to AWS APIs and is built > using Apache Pekko HTTP. We use the AWS SPI in a few of the Apache > Pekko Connectors. > > Please vote to approve this contribution. > This is a lazy consensus majority vote, per the IP clearance process > [2], open for at least 72 hours. > > Thanks, > PJ > > [1] > https://incubator.apache.org/ip-clearance/pekko-connectors-aws-spi.html > [2] https://incubator.apache.org/ip-clearance/ > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release Apache HugeGraph(Incubating) 1.3.0-rc1
Hi, Xuanwo Thank you for pointing out the issue. We have made the following fixes: 1. The broken link issue has been fixed and i replaced the git branch to tag Git tag & Commit hash for the release: • https://github.com/apache/incubator-hugegraph/tree/1.3.0 (6a4041e) • https://github.com/apache/incubator-hugegraph-toolchain/tree/1.3.0 (0dd2339) • https://github.com/apache/incubator-hugegraph-commons/tree/1.3.0 (c883f56) • https://github.com/apache/incubator-hugegraph-ai/tree/1.3.0 (4f48116) 2. Bundles swagger related js & css without license will be fixed in https://github.com/apache/incubator-hugegraph/pull/2495 The issue with the file's execute permissions will be resolved shortly. Thanks, JackyYang Xuanwo 于2024年3月29日周五 11:49写道： > > Hi, Jacky Yang > > This release looks good to me over all, but have some small issues to address. > > I believe they can be fixed in next release, so I will give a +1 binding for > this one. > > The checks I performed: > > [x] Download links are valid. > > a small issue: https://github.com/apache/incubator-hugegraph/tree/1.3.0 is a > broken link. > > [x] Checksums and signatures. > > gpg: Signature made Mon 25 Mar 2024 02:40:14 PM CST > gpg:using RSA key 12CEB4C81B4F1E358B8A1A181B75F4C00CAB214C > gpg: checking the trustdb > gpg: marginals needed: 3 completes needed: 1 trust model: pgp > gpg: depth: 0 valid: 25 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 25u > gpg: next trustdb check due at 2024-05-25 > gpg: Good signature from "JackyYang " [ultimate] > apache-hugegraph-ai-incubating-1.3.0-src.tar.gz: OK > gpg: Signature made Sun 24 Mar 2024 05:48:23 PM CST > gpg:using RSA key 12CEB4C81B4F1E358B8A1A181B75F4C00CAB214C > gpg: Good signature from "JackyYang " [ultimate] > apache-hugegraph-commons-incubating-1.3.0-src.tar.gz: OK > gpg: Signature made Sun 24 Mar 2024 06:21:51 PM CST > gpg:using RSA key 12CEB4C81B4F1E358B8A1A181B75F4C00CAB214C > gpg: Good signature from "JackyYang " [ultimate] > apache-hugegraph-incubating-1.3.0-src.tar.gz: OK > gpg: Signature made Sun 24 Mar 2024 06:21:52 PM CST > gpg:using RSA key 12CEB4C81B4F1E358B8A1A181B75F4C00CAB214C > gpg: Good signature from "JackyYang " [ultimate] > apache-hugegraph-incubating-1.3.0.tar.gz: OK > gpg: Signature made Sun 24 Mar 2024 06:49:03 PM CST > gpg:using RSA key 12CEB4C81B4F1E358B8A1A181B75F4C00CAB214C > gpg: Good signature from "JackyYang " [ultimate] > apache-hugegraph-toolchain-incubating-1.3.0-src.tar.gz: OK > gpg: Signature made Sun 24 Mar 2024 06:49:05 PM CST > gpg:using RSA key 12CEB4C81B4F1E358B8A1A181B75F4C00CAB214C > gpg: Good signature from "JackyYang " [ultimate] > apache-hugegraph-toolchain-incubating-1.3.0.tar.gz: OK > > [x] LICENSE/NOTICE files exist > > a small issue: the LICENSE, NOTICE, and DISCLAIMER files all incorrectly have > execute permissions on Linux platforms in apache-hugegraph-incubating-1.3.0. > > .rwxr-xr-x 557 xuanwo 24 Mar 18:19 DISCLAIMER > drwxr-xr-x - xuanwo 29 Mar 11:29 ext > drwxr-xr-x - xuanwo 29 Mar 11:29 lib > .rwxr-xr-x 60k xuanwo 24 Mar 18:19 LICENSE > drwxr-xr-x - xuanwo 29 Mar 11:29 licenses > .rwxr-xr-x 90k xuanwo 24 Mar 18:19 NOTICE > > [-] No unexpected binary files > > apache-hugegraph-incubating-1.3.0 bundles swagger related js & css without > license details. > > I wish this can be addressed in next release. > > [x] All source files have ASF headers > [x] Can compile from source on archlinux x86_64 > > [INFO] Reactor Summary for hugegraph 1.3.0: > [INFO] > [INFO] hugegraph .. SUCCESS [ 0.719 > s] > [INFO] hugegraph-server ... SUCCESS [ 0.245 > s] > [INFO] hugegraph-core . SUCCESS [ 44.684 > s] > [INFO] hugegraph-api .. SUCCESS [02:35 > min] > [INFO] hugegraph-cassandra SUCCESS [01:18 > min] > [INFO] hugegraph-scylladb . SUCCESS [ 0.394 > s] > [INFO] hugegraph-rocksdb .. SUCCESS [ 2.545 > s] > [INFO] hugegraph-mysql SUCCESS [ 0.327 > s] > [INFO] hugegraph-palo . SUCCESS [ 0.320 > s] > [INFO] hugegraph-hbase SUCCESS [ 16.562 > s] > [INFO] hugegraph-postgresql ... SUCCESS [ 1.443 > s] > [INFO] hugegraph-dist . SUCCESS [ 20.348 > s] > [INFO] hugegraph-example .. SUCCESS [ 0.801 > s] > [INFO] hugegraph-test . SUCCESS [ 42.137 > s] > [INFO] > > [INFO] BUILD SUCCESS > [INFO] > > [INFO] Total time: 0
Re: [VOTE] Release Apache Answer(Incubating) v1.3.0-RC1
+1 binding Nice release! [x] Download links are valid. [x] Checksums and signatures. gpg: Signature made Mon 25 Mar 2024 11:51:19 AM CST gpg:using RSA key 5684B6E344546A5F3CE9850D380DCBD5C34934CC gpg: Good signature from "LinkinStar (for apache release create at 20231220) " [ultimate] apache-answer-1.3.0-incubating-bin-darwin-amd64.tar.gz: OK gpg: Signature made Mon 25 Mar 2024 11:51:24 AM CST gpg:using RSA key 5684B6E344546A5F3CE9850D380DCBD5C34934CC gpg: Good signature from "LinkinStar (for apache release create at 20231220) " [ultimate] apache-answer-1.3.0-incubating-bin-darwin-arm64.tar.gz: OK gpg: Signature made Mon 25 Mar 2024 11:51:24 AM CST gpg:using RSA key 5684B6E344546A5F3CE9850D380DCBD5C34934CC gpg: Good signature from "LinkinStar (for apache release create at 20231220) " [ultimate] apache-answer-1.3.0-incubating-bin-linux-amd64.tar.gz: OK gpg: Signature made Mon 25 Mar 2024 11:51:24 AM CST gpg:using RSA key 5684B6E344546A5F3CE9850D380DCBD5C34934CC gpg: Good signature from "LinkinStar (for apache release create at 20231220) " [ultimate] apache-answer-1.3.0-incubating-bin-linux-arm64.tar.gz: OK gpg: Signature made Mon 25 Mar 2024 11:51:24 AM CST gpg:using RSA key 5684B6E344546A5F3CE9850D380DCBD5C34934CC gpg: Good signature from "LinkinStar (for apache release create at 20231220) " [ultimate] apache-answer-1.3.0-incubating-bin-windows-amd64.tar.gz: OK gpg: Signature made Mon 25 Mar 2024 11:51:25 AM CST gpg:using RSA key 5684B6E344546A5F3CE9850D380DCBD5C34934CC gpg: Good signature from "LinkinStar (for apache release create at 20231220) " [ultimate] apache-answer-1.3.0-incubating-src.tar.gz: OK [x] LICENSE/NOTICE files exist [x] No unexpected binary files [x] All source files have ASF headers [x] Can compile from source on archlinux x86-64 :( go build ./... go: downloading golang.org/x/crypto v0.21.0 go: downloading github.com/mojocn/base64Captcha v1.3.6 go: downloading golang.org/x/net v0.21.0 go: downloading golang.org/x/image v0.13.0 go: downloading golang.org/x/text v0.14.0 go: downloading golang.org/x/sys v0.18.0 go build ./... 89.11s user 7.84s system 783% cpu 12.379 total On Fri, Mar 29, 2024, at 15:46, LinkinStar wrote: > Hello, > > This is a call for vote to release Apache Answer(Incubating) version > v1.3.0-RC1. > > The vote thread: > https://lists.apache.org/thread/8pbh6047ogmdcf3ypdg4kr1k8gzxx6vf > > Vote Result: > https://lists.apache.org/thread/q3d6pgr1rq30ldzfn82gdq1h0qzmgylx > > The release candidates: > > https://dist.apache.org/repos/dist/dev/incubator/answer/1.3.0-incubating-RC1/ > > Release notes: > https://github.com/apache/incubator-answer/releases/tag/v1.3.0-RC1 > > Git tag for the release: > https://github.com/apache/incubator-answer/releases/tag/v1.3.0-RC1 > > Git commit id for the release: > > https://github.com/apache/incubator-answer/commit/9ebf95cacecf49ff466e47f3ff54c180eb67627c > > Keys to verify the Release Candidate: > The artifacts signed with PGP key [C34934CC], corresponding to [ > linkins...@apache.org], that can be found in keys file: > https://dist.apache.org/repos/dist/release/incubator/answer/KEYS > > The vote will be open for at least 72 hours or until the necessary > number of votes are reached. > > Please vote accordingly: > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove with the reason > > Checklist for reference: > > [ ] Download links are valid. > [ ] Checksums and PGP signatures are valid. > [ ] Source code distributions have correct names matching the current > release. > [ ] LICENSE and NOTICE files are correct for each Answer repo. > [ ] All files have license headers if necessary. > [ ] No unlicensed compiled archives bundled in source archive. > > To compile from the source, please refer to: > > https://github.com/apache/incubator-answer#building-from-source > > Thanks, > LinkinStar -- Xuanwo - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache HoraeDB(incubating) v2.0.0-RC5 - Incubator Vote Round 1
The Incubator PMC prefers that git commit ids are included in the vote emails because git tags can be moved. Git tags are encouraged but we like to see the Git commit id too. On Thu, 28 Mar 2024 at 12:06, Xuanwo wrote: > > Hi, I have checked the following and found some issues. > > [x] Download links are valid. > [x] Checksums and signatures. > > gpg: Signature made Tue 19 Mar 2024 02:21:30 PM CST > gpg:using RSA key 8BF38B1BBF93AD717DD63948F3EA26DA0F715C7F > gpg: checking the trustdb > gpg: marginals needed: 3 completes needed: 1 trust model: pgp > gpg: depth: 0 valid: 24 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 24u > gpg: next trustdb check due at 2024-05-25 > gpg: Good signature from "chunshao.rcs " [ultimate] > apache-horaedb-incubating-v2.0.0-src.tar.gz: OK > > [x] LICENSE/NOTICE files exist > [-] No unexpected binary files > > I have seen many hidden binary files like > > - ._.asf.yaml > - .asf.yaml > - ._Cargo.lock > - ._Cargo.toml > - ._clippy.toml > - ._CONTRIBUTING.md > - ._DEPENDENCIES.tsv > > Please check the package tool and remove them > > [-] All source files have ASF headers > > I have seen files like "src/components/skiplist/src/key.rs" been excluded from > license check, is there a reason for this? > > By the way, I recommend relying on released tags rather than individual > commits > in github. > > [-] Can compile from source > > cargo build failed for: > > ``` >1470 | return std::move(status); > | ~^~~~ > > /home/xuanwo/.cargo/git/checkouts/rust-rocksdb-a9a28e74c6ead8ef/f04f4dd/librocksdb_sys/rocksdb/db/db_impl/db_impl.cc:1470:19: > note: remove ‘std::move’ call > cc1plus: all warnings being treated as errors > make[3]: *** [CMakeFiles/rocksdb.dir/build.make:555: > CMakeFiles/rocksdb.dir/db/db_impl/db_impl.cc.o] Error 1 > make[2]: *** [CMakeFiles/Makefile2:142: CMakeFiles/rocksdb.dir/all] Error 2 > make[1]: *** [CMakeFiles/Makefile2:149: CMakeFiles/rocksdb.dir/rule] Error 2 > make: *** [Makefile:172: rocksdb] Error 2 > thread 'main' panicked at > /home/xuanwo/.cargo/registry/src/index.crates.io-6f17d22bba15001f/cmake-0.1.50/src/lib.rs:1098:5: > > command did not execute successfully, got: exit status: 2 > ``` > > Maybe we should supress the warnings? > > On Wed, Mar 27, 2024, at 11:47, 任春韶 wrote: > > I'm sorry, there was a problem with the formatting of the email I sent just > > now.😅 > > > > Hello, Incubator Community, > > > > This is a call for a vote to release Apache HoraeDB(incubating) version > > v2.0.0-RC5 > > > > HoraeDB PPMC Vote Thread > > https://lists.apache.org/thread/trvhct3nqgkqkb5mxg4sy26gkn90d31v > > > > HoraeDB PPMC Vote Result > > https://lists.apache.org/thread/p6tkbnvt7wrx956d87h077nbls2yls1r > > > > The release candidate: > > https://dist.apache.org/repos/dist/dev/incubator/horaedb/horaedb/v2.0.0-rc.5 > > > > > > This release has been signed with a PGP available here: > > https://downloads.apache.org/incubator/horaedb/KEYS > > > > Git tag for the release > > https://github.com/apache/incubator-horaedb/releases/tag/v2.0.0-rc.5 > > > > Please download, verify, and test. > > > > The VOTE will pass after got 3 binding approve. > > > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove with the reason > > > > To learn more about Apache HoraeDB, please see https://horaedb.apache.org/ > > > > Checklist for reference: > > > > [ ] Download links are valid. > > [ ] Checksums and signatures. > > [ ] LICENSE/NOTICE files exist > > [ ] No unexpected binary files > > [ ] All source files have ASF headers > > [ ] Can compile from source > > > > Thanks > > > > 任春韶 于2024年3月27日周三 11:38写道： > > > >> Hello, Incubator Community, This is a call for a vote to release Apache > >> HoraeDB(incubating) version v2.0.0-RC5 HoraeDB PPMC Vote Thread > >> https://lists.apache.org/thread/trvhct3nqgkqkb5mxg4sy26gkn90d31v HoraeDB > >> PPMC Vote Result > >> https://lists.apache.org/thread/p6tkbnvt7wrx956d87h077nbls2yls1r The > >> release candidate: > >> https://dist.apache.org/repos/dist/dev/incubator/horaedb/horaedb/v2.0.0-rc.5 > >> This release has been signed with a PGP available here: > >> https://downloads.apache.org/incubator/horaedb/KEYS Git tag for the > >> release: > >> https://github.com/apache/incubator-horaedb/releases/tag/v2.0.0-rc.5 > >> Please download, verify, and test. The VOTE will pass after got 3 binding > >> approve. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove with the reason > >> To learn more about Apache HoraeDB, please see https://horaedb.apache.org/ > >> Checklist for reference: [ ] Download links are valid. [ ] Checksums and > >> signatures. [ ] LICENSE/NOTICE files exist [ ] No unexpected binary files [ > >> ] All source files have ASF headers [ ] Can compile from source Thanks > >> > > -- > Xuanwo > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h.
Re: [VOTE] Release Apache HoraeDB(incubating) v2.0.0-RC5 - Incubator Vote Round 1
> 2. How do you define "binary file"? The files listed are configuration > files and cannot be executed. Hi, please double check this part. They are all hidden files start with ".". For example, "._.asf.yaml" instead of ".asf.yaml". They should not exist. On Fri, Mar 29, 2024, at 16:06, Chunshao Ren wrote: > Thanks for your verification! > > 1. "src/components/skiplist/src/key.rs" is modified from > alatedb(https://github.com/tikv/agatedb), detailed information can be > found at > https://github.com/apache/incubator-horaedb/blob/main/NOTICE#L30 > > 2. How do you define "binary file"? The files listed are configuration > files and cannot be executed. > > 3. Fail to compile from source: > It may be a problem with the gcc version. You can try gcc 8. We will > bump our dependency in the next release to support newer gcc versions. > See https://github.com/apache/incubator-horaedb/issues/1506 for details. > > On 2024/03/28 11:05:49 Xuanwo wrote: >> Hi, I have checked the following and found some issues. >> >> [x] Download links are valid. >> [x] Checksums and signatures. >> >> gpg: Signature made Tue 19 Mar 2024 02:21:30 PM CST >> gpg:using RSA key 8BF38B1BBF93AD717DD63948F3EA26DA0F715C7F >> gpg: checking the trustdb >> gpg: marginals needed: 3 completes needed: 1 trust model: pgp >> gpg: depth: 0 valid: 24 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 24u >> gpg: next trustdb check due at 2024-05-25 >> gpg: Good signature from "chunshao.rcs " [ultimate] >> apache-horaedb-incubating-v2.0.0-src.tar.gz: OK >> >> [x] LICENSE/NOTICE files exist >> [-] No unexpected binary files >> >> I have seen many hidden binary files like >> >> - ._.asf.yaml >> - .asf.yaml >> - ._Cargo.lock >> - ._Cargo.toml >> - ._clippy.toml >> - ._CONTRIBUTING.md >> - ._DEPENDENCIES.tsv >> >> Please check the package tool and remove them >> >> [-] All source files have ASF headers >> >> I have seen files like "src/components/skiplist/src/key.rs" been excluded >> from >> license check, is there a reason for this? >> >> By the way, I recommend relying on released tags rather than individual >> commits >> in github. >> >> [-] Can compile from source >> >> cargo build failed for: >> >> ``` >>1470 | return std::move(status); >> | ~^~~~ >> >> /home/xuanwo/.cargo/git/checkouts/rust-rocksdb-a9a28e74c6ead8ef/f04f4dd/librocksdb_sys/rocksdb/db/db_impl/db_impl.cc:1470:19: >> note: remove ‘std::move’ call >> cc1plus: all warnings being treated as errors >> make[3]: *** [CMakeFiles/rocksdb.dir/build.make:555: >> CMakeFiles/rocksdb.dir/db/db_impl/db_impl.cc.o] Error 1 >> make[2]: *** [CMakeFiles/Makefile2:142: CMakeFiles/rocksdb.dir/all] Error 2 >> make[1]: *** [CMakeFiles/Makefile2:149: CMakeFiles/rocksdb.dir/rule] Error >> 2 >> make: *** [Makefile:172: rocksdb] Error 2 >> thread 'main' panicked at >> /home/xuanwo/.cargo/registry/src/index.crates.io-6f17d22bba15001f/cmake-0.1.50/src/lib.rs:1098:5: >> >> command did not execute successfully, got: exit status: 2 >> ``` >> >> Maybe we should supress the warnings? >> >> On Wed, Mar 27, 2024, at 11:47, 任春韶 wrote: >> > I'm sorry, there was a problem with the formatting of the email I sent just >> > now.😅 >> > >> > Hello, Incubator Community, >> > >> > This is a call for a vote to release Apache HoraeDB(incubating) version >> > v2.0.0-RC5 >> > >> > HoraeDB PPMC Vote Thread >> > https://lists.apache.org/thread/trvhct3nqgkqkb5mxg4sy26gkn90d31v >> > >> > HoraeDB PPMC Vote Result >> > https://lists.apache.org/thread/p6tkbnvt7wrx956d87h077nbls2yls1r >> > >> > The release candidate: >> > https://dist.apache.org/repos/dist/dev/incubator/horaedb/horaedb/v2.0.0-rc.5 >> > >> > >> > This release has been signed with a PGP available here: >> > https://downloads.apache.org/incubator/horaedb/KEYS >> > >> > Git tag for the release >> > https://github.com/apache/incubator-horaedb/releases/tag/v2.0.0-rc.5 >> > >> > Please download, verify, and test. >> > >> > The VOTE will pass after got 3 binding approve. >> > >> > [ ] +1 approve >> > [ ] +0 no opinion >> > [ ] -1 disapprove with the reason >> > >> > To learn more about Apache HoraeDB, please see https://horaedb.apache.org/ >> > >> > Checklist for reference: >> > >> > [ ] Download links are valid. >> > [ ] Checksums and signatures. >> > [ ] LICENSE/NOTICE files exist >> > [ ] No unexpected binary files >> > [ ] All source files have ASF headers >> > [ ] Can compile from source >> > >> > Thanks >> > >> > 任春韶 于2024年3月27日周三 11:38写道： >> > >> >> Hello, Incubator Community, This is a call for a vote to release Apache >> >> HoraeDB(incubating) version v2.0.0-RC5 HoraeDB PPMC Vote Thread >> >> https://lists.apache.org/thread/trvhct3nqgkqkb5mxg4sy26gkn90d31v HoraeDB >> >> PPMC Vote Result >> >> https://lists.apache.org/thread/p6tkbnvt7wrx956d87h077nbls2yls1r The >> >> release candidate: >> >> https://dist.apache.org/repos/dist/dev/incubator/horaedb/horaedb/v2.0.0-rc.5 >> >> This release has
Re: [IP CLEARANCE] Apache Pekko Connectors AWS SPI
+1 from me (binding) On Wed, Mar 27, 2024 at 7:05 PM PJ Fanning wrote: > > Hi everyone, > > Apache Pekko is receiving a donation of an AWS SPI. > The AWS SPI is used to make client calls to AWS APIs and is built > using Apache Pekko HTTP. We use the AWS SPI in a few of the Apache > Pekko Connectors. > > Please vote to approve this contribution. > This is a lazy consensus majority vote, per the IP clearance process > [2], open for at least 72 hours. > > Thanks, > PJ > > [1] https://incubator.apache.org/ip-clearance/pekko-connectors-aws-spi.html > [2] https://incubator.apache.org/ip-clearance/ > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > -- Matthew de Detrich Aiven Deutschland GmbH Immanuelkirchstraße 26, 10405 Berlin Alexanderufer 3-7, 10117 Berlin Amtsgericht Charlottenburg, HRB 209739 B Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen m: +491603708037 w: aiven.io e: matthew.dedetr...@aiven.io - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache HoraeDB(incubating) v2.0.0-RC5 - Incubator Vote Round 1
Thanks for your verification! On 2024/03/29 02:22:28 Suyan wrote: > +1 non-binding > > I checked: > [x] Download links are valid. > [x] Checksums and signatures. > gpg: Signature made Tue Mar 19 14:21:30 2024 CST > gpg:using RSA key 8BF38B1BBF93AD717DD63948F3EA26DA0F715C7F > gpg: checking the trustdb > gpg: marginals needed: 3 completes needed: 1 trust model: pgp > gpg: depth: 0 valid: 20 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 20u > gpg: next trustdb check due at 2024-05-25 > gpg: Good signature from "chunshao.rcs " [ultimate] > > [x] LICENSE/NOTICE files exist > [x] Can compile from source on macOS(arm64) > Finished release [optimized + debuginfo] target(s) in 14m 48s > > Sincerely, > Suyan > > 任春韶 于2024年3月27日周三 11:38写道： > > > > Hello, Incubator Community, This is a call for a vote to release Apache > > HoraeDB(incubating) version v2.0.0-RC5 HoraeDB PPMC Vote Thread > > https://lists.apache.org/thread/trvhct3nqgkqkb5mxg4sy26gkn90d31v HoraeDB > > PPMC Vote Result > > https://lists.apache.org/thread/p6tkbnvt7wrx956d87h077nbls2yls1r The > > release candidate: > > https://dist.apache.org/repos/dist/dev/incubator/horaedb/horaedb/v2.0.0-rc.5 > > This release has been signed with a PGP available here: > > https://downloads.apache.org/incubator/horaedb/KEYS Git tag for the > > release: > > https://github.com/apache/incubator-horaedb/releases/tag/v2.0.0-rc.5 Please > > download, verify, and test. The VOTE will pass after got 3 binding approve. > > [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove with the reason To learn > > more about Apache HoraeDB, please see https://horaedb.apache.org/ Checklist > > for reference: [ ] Download links are valid. [ ] Checksums and signatures. > > [ ] LICENSE/NOTICE files exist [ ] No unexpected binary files [ ] All > > source files have ASF headers [ ] Can compile from source Thanks > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache HoraeDB(incubating) v2.0.0-RC5 - Incubator Vote Round 1
Thanks for your verification! 1. "src/components/skiplist/src/key.rs" is modified from alatedb(https://github.com/tikv/agatedb), detailed information can be found at https://github.com/apache/incubator-horaedb/blob/main/NOTICE#L30 2. How do you define "binary file"? The files listed are configuration files and cannot be executed. 3. Fail to compile from source: It may be a problem with the gcc version. You can try gcc 8. We will bump our dependency in the next release to support newer gcc versions. See https://github.com/apache/incubator-horaedb/issues/1506 for details. On 2024/03/28 11:05:49 Xuanwo wrote: > Hi, I have checked the following and found some issues. > > [x] Download links are valid. > [x] Checksums and signatures. > > gpg: Signature made Tue 19 Mar 2024 02:21:30 PM CST > gpg:using RSA key 8BF38B1BBF93AD717DD63948F3EA26DA0F715C7F > gpg: checking the trustdb > gpg: marginals needed: 3 completes needed: 1 trust model: pgp > gpg: depth: 0 valid: 24 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 24u > gpg: next trustdb check due at 2024-05-25 > gpg: Good signature from "chunshao.rcs " [ultimate] > apache-horaedb-incubating-v2.0.0-src.tar.gz: OK > > [x] LICENSE/NOTICE files exist > [-] No unexpected binary files > > I have seen many hidden binary files like > > - ._.asf.yaml > - .asf.yaml > - ._Cargo.lock > - ._Cargo.toml > - ._clippy.toml > - ._CONTRIBUTING.md > - ._DEPENDENCIES.tsv > > Please check the package tool and remove them > > [-] All source files have ASF headers > > I have seen files like "src/components/skiplist/src/key.rs" been excluded from > license check, is there a reason for this? > > By the way, I recommend relying on released tags rather than individual > commits > in github. > > [-] Can compile from source > > cargo build failed for: > > ``` >1470 | return std::move(status); > | ~^~~~ > > /home/xuanwo/.cargo/git/checkouts/rust-rocksdb-a9a28e74c6ead8ef/f04f4dd/librocksdb_sys/rocksdb/db/db_impl/db_impl.cc:1470:19: > note: remove ‘std::move’ call > cc1plus: all warnings being treated as errors > make[3]: *** [CMakeFiles/rocksdb.dir/build.make:555: > CMakeFiles/rocksdb.dir/db/db_impl/db_impl.cc.o] Error 1 > make[2]: *** [CMakeFiles/Makefile2:142: CMakeFiles/rocksdb.dir/all] Error 2 > make[1]: *** [CMakeFiles/Makefile2:149: CMakeFiles/rocksdb.dir/rule] Error 2 > make: *** [Makefile:172: rocksdb] Error 2 > thread 'main' panicked at > /home/xuanwo/.cargo/registry/src/index.crates.io-6f17d22bba15001f/cmake-0.1.50/src/lib.rs:1098:5: > > command did not execute successfully, got: exit status: 2 > ``` > > Maybe we should supress the warnings? > > On Wed, Mar 27, 2024, at 11:47, 任春韶 wrote: > > I'm sorry, there was a problem with the formatting of the email I sent just > > now.😅 > > > > Hello, Incubator Community, > > > > This is a call for a vote to release Apache HoraeDB(incubating) version > > v2.0.0-RC5 > > > > HoraeDB PPMC Vote Thread > > https://lists.apache.org/thread/trvhct3nqgkqkb5mxg4sy26gkn90d31v > > > > HoraeDB PPMC Vote Result > > https://lists.apache.org/thread/p6tkbnvt7wrx956d87h077nbls2yls1r > > > > The release candidate: > > https://dist.apache.org/repos/dist/dev/incubator/horaedb/horaedb/v2.0.0-rc.5 > > > > > > This release has been signed with a PGP available here: > > https://downloads.apache.org/incubator/horaedb/KEYS > > > > Git tag for the release > > https://github.com/apache/incubator-horaedb/releases/tag/v2.0.0-rc.5 > > > > Please download, verify, and test. > > > > The VOTE will pass after got 3 binding approve. > > > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove with the reason > > > > To learn more about Apache HoraeDB, please see https://horaedb.apache.org/ > > > > Checklist for reference: > > > > [ ] Download links are valid. > > [ ] Checksums and signatures. > > [ ] LICENSE/NOTICE files exist > > [ ] No unexpected binary files > > [ ] All source files have ASF headers > > [ ] Can compile from source > > > > Thanks > > > > 任春韶 于2024年3月27日周三 11:38写道： > > > >> Hello, Incubator Community, This is a call for a vote to release Apache > >> HoraeDB(incubating) version v2.0.0-RC5 HoraeDB PPMC Vote Thread > >> https://lists.apache.org/thread/trvhct3nqgkqkb5mxg4sy26gkn90d31v HoraeDB > >> PPMC Vote Result > >> https://lists.apache.org/thread/p6tkbnvt7wrx956d87h077nbls2yls1r The > >> release candidate: > >> https://dist.apache.org/repos/dist/dev/incubator/horaedb/horaedb/v2.0.0-rc.5 > >> This release has been signed with a PGP available here: > >> https://downloads.apache.org/incubator/horaedb/KEYS Git tag for the > >> release: > >> https://github.com/apache/incubator-horaedb/releases/tag/v2.0.0-rc.5 > >> Please download, verify, and test. The VOTE will pass after got 3 binding > >> approve. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove with the reason > >> To learn more about Apache HoraeDB, please see https://horaedb.apache.org/ > >> Checklist for referenc
Re: [VOTE] Accept HertzBeat Into the ASF Incubator
Thanks, Chao Gong, for addressing those issues in https://github.com/dromara/hertzbeat/commit/1284914c4a2d42c8355417c164810787fb64e588 Looking at the updated website, the issues raised have been taken care of. Regarding keeping the website's source code and project code in the project repository, I don't think it's 100% necessary to separate the website into a separate repository. For Calcite, our site is in the same repository as our code: https://github.com/apache/calcite/tree/main/site We include the correct licenses in the LICENSE file when we build a release, using a template: https://github.com/apache/calcite/blob/main/LICENSE Francis On 29/03/2024 6:05 pm, Sheng Wu wrote: Some things should be fixed 1. At the top of the home page, exists, this should be removed. 2. At the top menu, exists, I don't think this project is Huawei, and please don't use another vendor's brand. 3. Similar with <2>, but for OSPP. That is also another org brand. 4. When I first lands on the homepage, there is a pop up box to ask me star on GitHub. This should be removed too. GitHub repository is just a bi-way synced mirror repository. ASF has its own code repository, which is also the main repository to make sure vendor neutral. A thing you should fix later, your website source codes and resources are in the same repository. Those things may not be able to be included considering the license and binaries(png, videos) may be included. In the ASF, website is usually a separate repository. But the in your proposal seems not included. Please reach your mentors and fix the proposal. Sheng Wu 吴晟 Twitter, wusheng1108 Zhang Yonglun 于2024年3月29日周五 14:24写道： Hi Incubator, Following the discussion [DISCUSS] Incubating Proposal for HertzBeat[1], I am starting this official vote for the HertzBeat project. Here is their proposal: https://cwiki.apache.org/confluence/display/INCUBATOR/HertzBeatProposal Please cast your vote: [ ] +1, bring into the Incubator [ ] +0, I don't care either way [ ] -1, do not bring HertzBeat into the Incubator, because... The vote will open for one week from today. [1] https://lists.apache.org/thread/snxcdyvqgvhgjdmfv4l192g9tdf8w7rn Best Regards, Zhang Yonglun - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Release Apache Answer(Incubating) v1.3.0-RC1
Hello, This is a call for vote to release Apache Answer(Incubating) version v1.3.0-RC1. The vote thread: https://lists.apache.org/thread/8pbh6047ogmdcf3ypdg4kr1k8gzxx6vf Vote Result: https://lists.apache.org/thread/q3d6pgr1rq30ldzfn82gdq1h0qzmgylx The release candidates: https://dist.apache.org/repos/dist/dev/incubator/answer/1.3.0-incubating-RC1/ Release notes: https://github.com/apache/incubator-answer/releases/tag/v1.3.0-RC1 Git tag for the release: https://github.com/apache/incubator-answer/releases/tag/v1.3.0-RC1 Git commit id for the release: https://github.com/apache/incubator-answer/commit/9ebf95cacecf49ff466e47f3ff54c180eb67627c Keys to verify the Release Candidate: The artifacts signed with PGP key [C34934CC], corresponding to [ linkins...@apache.org], that can be found in keys file: https://dist.apache.org/repos/dist/release/incubator/answer/KEYS The vote will be open for at least 72 hours or until the necessary number of votes are reached. Please vote accordingly: [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove with the reason Checklist for reference: [ ] Download links are valid. [ ] Checksums and PGP signatures are valid. [ ] Source code distributions have correct names matching the current release. [ ] LICENSE and NOTICE files are correct for each Answer repo. [ ] All files have license headers if necessary. [ ] No unlicensed compiled archives bundled in source archive. To compile from the source, please refer to: https://github.com/apache/incubator-answer#building-from-source Thanks, LinkinStar
[IP CLEARANCE] Apache Kyuubi - Donation of PyHive
Hi everyone, Apache Kyuubi is receiving a donation of PyHive[1] from DropBox, Inc. PyHive is a popular Python library that allows users to use DB-API and SQLAlchemy interfaces to access Presto, Hive, Trino, also Kyuubi. Please vote to approve this contribution. This is a lazy consensus majority vote, per the IP clearance process[2], open for at least 72 hours. [1] https://incubator.apache.org/ip-clearance/kyuubi-pyhive.html [2] https://incubator.apache.org/ip-clearance/ Thanks, Cheng Pan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept HertzBeat Into the ASF Incubator
Some things should be fixed 1. At the top of the home page, exists, this should be removed. 2. At the top menu, exists, I don't think this project is Huawei, and please don't use another vendor's brand. 3. Similar with <2>, but for OSPP. That is also another org brand. 4. When I first lands on the homepage, there is a pop up box to ask me star on GitHub. This should be removed too. GitHub repository is just a bi-way synced mirror repository. ASF has its own code repository, which is also the main repository to make sure vendor neutral. A thing you should fix later, your website source codes and resources are in the same repository. Those things may not be able to be included considering the license and binaries(png, videos) may be included. In the ASF, website is usually a separate repository. But the in your proposal seems not included. Please reach your mentors and fix the proposal. Sheng Wu 吴晟 Twitter, wusheng1108 Zhang Yonglun 于2024年3月29日周五 14:24写道： > > Hi Incubator, > > Following the discussion [DISCUSS] Incubating Proposal for HertzBeat[1], > I am starting this official vote for the HertzBeat project. > > Here is their proposal: > https://cwiki.apache.org/confluence/display/INCUBATOR/HertzBeatProposal > > Please cast your vote: > > [ ] +1, bring into the Incubator > [ ] +0, I don't care either way > [ ] -1, do not bring HertzBeat into the Incubator, because... > > The vote will open for one week from today. > > [1] https://lists.apache.org/thread/snxcdyvqgvhgjdmfv4l192g9tdf8w7rn > > Best Regards, > Zhang Yonglun > > - > 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
