Re: [IP CLEARANCE] Apache Celix - Websocket pubsub admin
Hi, > For Celix is it okay to continue if we update the NOTICE file and add the > following statement?: > > This product includes software developed at > Thales Nederland B.V. (https://www.thalesgroup.com/nl). That sounds fine to me, but it depends on the original headers of on those files or if the original source had it own NOTICE file, with a PR like this missing that information I cannot really answer that question. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [IP CLEARANCE] Apache Celix - Websocket pubsub admin
Hi, > Thanks for reviewing. Isn't this actually part of the IP clearance form > which describes the following: >> Check and make sure that the files that have been donated have been > updated to reflect the new ASF copyright. I believe the intention is that you fill in the date when it is done, not do it before ether donation. [1] Otherwise is hard to work out from a PR what was actually donated and if any of it belonged to the ASF before hand. changing i after the donation gives a clear commit you can point to which may be useful if the IP history ever needs to be looked at. Thanks, Justin 1. https://incubator.apache.org/ip-clearance/ip-clearance-template.html - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [IP CLEARANCE] Apache Celix - Websocket pubsub admin
Hi Justin, Thanks for reviewing. Isn't this actually part of the IP clearance form which describes the following: > Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright. Having a look at other IP clearances they are more or less doing the same (just picked 2 random ones): For Apache Arrow: http://incubator.apache.org/ip-clearance/arrow-gandiva.html which matches with pull request: https://github.com/apache/arrow/pull/2558 For Apache Beam: http://incubator.apache.org/ip-clearance/beam-zetasql-translator.html which matches with pull request: https://github.com/apache/beam/pull/9210 I noticed that Beam its NOTICE file already contained the statement that the project includes source code developed by Google. For Celix is it okay to continue if we update the NOTICE file and add the following statement?: This product includes software developed at Thales Nederland B.V. (https://www.thalesgroup.com/nl). Thanks, Roy Op wo 21 aug. 2019 om 06:06 schreef Justin Mclean : > Hi, > > > The pull request containing the donation can be found at: > > https://github.com/apache/celix/pull/39 > > I can see that the copyright owner / headers have been replaces by ASF > ones. This is best done after accepting the donation and then adding that > copyright to NOTICE. > > Thanks, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release Apache ShardingSphere (Incubating) 4.0.0-RC2
I have put the wrong link of Maven 2 staging repository, now it's updated to: Maven 2 staging repository: https://repository.apache.org/content/repositories/orgapacheshardingsphere-1022/org/apache/shardingsphere/ Zhang Yonglun 于2019年8月20日周二 下午6:16写道： > Hello all, > > This is a call for vote to release Apache ShardingSphere (Incubating) > version 4.0.0-RC2. > > The Apache ShardingSphere community has voted on and approved a proposal > to release Apache ShardingSphere (Incubating) version 4.0.0-RC2. > > We now kindly request the Incubator PMC members review and vote on this > incubator release. > > ShardingSphere is an open-source ecosystem consisted of a set of > distributed database middleware solutions, including 2 independent > products, Sharding-JDBC & Sharding-Proxy. > > Sharding-JDBC is an enhanced JDBC driver that provides in-process > transparent distributed database by connecting to multiple database back > ends. It supports many ORM frameworks and database connection pools and > supports many back end databases that have JDBC interfaces: MySQL, Oracle, > SQLServer and PostgreSQL. > > Sharding-Proxy is a database proxy that runs in a separate process and > appears as a database server to multiple back end databases. It supports > multiple client front ends such as MySQL Command Client, MySQL Workbench, > Navicat etc. Current support is for MySQL and PostgreSQL. > > ShardingSphere community vote and result thread: > > https://lists.apache.org/thread.html/4b29490f433dd26cc85d0e00340def3bd0f7b64e4bd2f3512e568bcd@%3Cdev.shardingsphere.apache.org%3E > > Release notes: > > https://github.com/apache/incubator-shardingsphere/blob/dev/RELEASE-NOTES.md > > The release candidates: > https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.0-RC2/ > > Maven 2 staging repository: > > https://repository.apache.org/content/repositories/staging/org/apache/shardingsphere/ > > Git tag for the release: > https://github.com/apache/incubator-shardingsphere/tree/4.0.0-RC2 > > Release Commit ID: > > https://github.com/apache/incubator-shardingsphere/commit/85f2ff877a7aaf122998964a0d03f7c9b2830e36 > > Keys to verify the Release Candidate: > https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/KEYS > GPG username: zhangyonglun > > Look at here for how to verify this release candidate: > https://shardingsphere.apache.org/community/en/contribute/release/ > > 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 > > Checklist for reference: > > [ ] Download links are valid. > > [ ] Checksums and PGP signatures are valid. > > [ ] DISCLAIMER is included. > > [ ] Source code artifacts have correct names matching the current release. > > [ ] LICENSE and NOTICE files are correct for each ShardingSphere repo. > > [ ] All files have license headers if necessary. > > [ ] No compiled archives bundled in source archive. > > -- > Zhang Yonglun > Apache ShardingSphere > -- Zhang Yonglun Apache ShardingSphere
Re: [VOTE] Release Apache Flagon UserALE.js (Incubating) v2.0.2
Ok. Thanks for guidance and clarification. > On Aug 21, 2019, at 12:45 AM, Justin Mclean wrote: > > Hi, > >> I asked you about this after you caught the missing disclaimer, but didn’t >> hear back inside of 24 hours so I made a judgement call—I hope I did the >> right thing. > > Well it not the wrong thing, it just something that I don;t think has > happened before. > >> My logic in this case was that because our Disclaimer was in src, and there >> were no issues with the Disclaimer itself, repackaging the RC with the >> Disclaimer in the .bin files would not have required any new commits to >> files. +1s from dev@ (especially Binding) would have indicated approval of >> the Disclaimer as well. > > Change the binary changes the signatures and hashes, if teh project was a TLP > IMO that would require another vote. > >> We had +3 IPMC VOTES on dev@, however, to date we only have +2 on general@. >> Do I need one more on general@? > > You can carry over the IPMC votes. > > Thanks, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Flagon UserALE.js (Incubating) v2.0.2
Hi, > I asked you about this after you caught the missing disclaimer, but didn’t > hear back inside of 24 hours so I made a judgement call—I hope I did the > right thing. Well it not the wrong thing, it just something that I don;t think has happened before. > My logic in this case was that because our Disclaimer was in src, and there > were no issues with the Disclaimer itself, repackaging the RC with the > Disclaimer in the .bin files would not have required any new commits to > files. +1s from dev@ (especially Binding) would have indicated approval of > the Disclaimer as well. Change the binary changes the signatures and hashes, if teh project was a TLP IMO that would require another vote. > We had +3 IPMC VOTES on dev@, however, to date we only have +2 on general@. > Do I need one more on general@? You can carry over the IPMC votes. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [MENTORS] Mentor guidance document
Hi, Sone thoughts inline. > Documentation does not solve the problem. I agree it doesn’t solve the whole problem. But it may give time poor mentors more time to do other things if they can easily reference collective knowledge on these issues. > If someone doesn't already "get" this stuff then they should not be mentoring. We have had on occasion people who are mentoring who may not get this stuff but were passionate supports of their projects, should we exclude them? Some of this is down to inexperience, and mentoring is one of the good ways to improve this knowledge and become a better mentor. Even if you have gone though incubation and mentored a project before you may of not come across the same situation and it’s not always obvious how to apply the values, especially in case where there’s conflict between those values (or ASF policies). > Having a document does not replace for selecting good mentors who have the > time to do the job right. 1-2 years (or more in some cases) a long commitment and life sometime changes things, replacement mentors can’t in all cases be found, so even if the initial condition is true, it may not be a year into teh project. I had thought of making up a mentor capability / score card to help podlings elect mentors if they don’t already have one. But haven't suggested it previously as it would probably be unpopular and could be used unproductively. > It's a good effort in the broader context, but doesn't solve the problem I > see in the IPMC (insufficient high quality mentoring coupled with too much > application of rules in the process). Is that because you think don’t we have enough high quality mentors? Or the ones we do have are spread a little too thin? Or that we have these people but they are not mentoring projects? > How would I solve the problem? If I were championing another project into the > ASF I would carefully select mentors, just as I have in the past. Being here along time and your previous / current positions would make it easy for to be able to get the best mentors we have that are a good fit for the project. I’m not sure that all new incubating projects are able to do that. > I don't mean to say the effort you are putting in is wasted effort. Clarity > in what is expected can help the podlings, Do any other mentors want to contribute to this or think it’s an idea worth perusing? If not I’ll drop it and focus on something else. > I don't see how this can really help those people I would already trust to be > good mentors i.e. People who have a vested interest in the success of the > project and already know how to apply the Apache Way to new communities so > that they might flourish in their own way. I not sure we actually have enough mentors with those abilities and knowledge for all of the 50 odd podlings we have or a pool of idle mentors than new projects can select from. Thanks,. Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Flagon UserALE.js (Incubating) v2.0.2
Hi Justin, Thanks for the attention on this VOTE. I asked you about this after you caught the missing disclaimer, but didn’t hear back inside of 24 hours so I made a judgement call—I hope I did the right thing. Would appreciate any guidance on my logic here. My logic in this case was that because our Disclaimer was in src, and there were no issues with the Disclaimer itself, repackaging the RC with the Disclaimer in the .bin files would not have required any new commits to files. +1s from dev@ (especially Binding) would have indicated approval of the Disclaimer as well. Were it the case that I needed to modify file content for compliance, I would have had to change the commit stream and push tags forward. In the case, I would have certainly kicked back to dev@ to VOTE again. Also, a little confused about Dave Fisher’s response in our VOTE thread. He said, "You have enough IPMC votes from your mentors. I think you are good.” We had +3 IPMC VOTES on dev@, however, to date we only have +2 on general@. Do I need one more on general@? Josh > On Aug 21, 2019, at 12:09 AM, Justin Mclean wrote: > > Hi, > > It's a little unusual as they voted before the binary was changed so this > really should have been two seperate vote threads. But I ‘m fine if you count > them this time. > > Thanks, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org >
Re: [VOTE] Release Apache Flagon UserALE.js (Incubating) v2.0.2
Hi, It's a little unusual as they voted before the binary was changed so this really should have been two seperate vote threads. But I ‘m fine if you count them this time. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [IP CLEARANCE] Apache Celix - Websocket pubsub admin
Hi, > The pull request containing the donation can be found at: > https://github.com/apache/celix/pull/39 I can see that the copyright owner / headers have been replaces by ASF ones. This is best done after accepting the donation and then adding that copyright to NOTICE. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release 1.1.0-incubating-RC2
Hi, +1 (binding) I checked: - incubating in name - signatures and hashes fine - DISCLAIMER exists and uses the WIP text. you also might want to fill in #Podling-Name# - LICENSE is OK. Do you know what is missing? - NOTICE is fine - NO binary files in release - All source files have ASF header - Can compile from source There’s some very minor issues: - I assume that some of the files may have an incorrect header? [1][2][3][4][6][7][8]. 3rd party headers should probably not be replaced with ASF ones [9] unless they have been extensively modified. This shod be mentioned in the DISCLAIMER. - In LICENSE there is probably no need to mention the java files that use the Gettysburg address. - "lee...@users.noreply.github.com” is probably not the best email to sign the release with, please use an apache one in future. - It’s nicer if the source unzips into a directory Thanks, Justin 1. src/main/java/org/apache/datasketches/memory/AccessByteBuffer.java 2. src/main/java/org/apache/datasketches/memory/XxHash64.java 3. src/test/java/org/apache/datasketches/memory/XxHash64Test.java 4. src/test/java/org/apache/datasketches/memory/XxHash64LoopingTest.java 5. src/main/java/org/apache/datasketches/memory/Utf8.java 6. src/test/java/org/apache/datasketches/memory/Utf8Test.java 7 src/test/java/org/apache/datasketches/memory/IsValidUtf8TestUtil.java 8 src/main/java/org/apache/datasketches/memory/XxHash64.java 9 https://www.apache.org/legal/src-headers.html#3party - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache ShardingSphere (Incubating) 4.0.0-RC2
Hi, +1 (binding) I checked: - incubating in name - signatures and hashes correct - DISCLAIMER exists - LICENSE and NOTICE file (no 3rd party software included) - No binary files - All source files have ASF headers - Can compile from source This is as about as simple as it get to review :-) Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Myriad 0.4.0 (incubating) [rc1]
Hi, +1 (binding) I checked: - incubating in name - signatures and hashes fine - DISCLAIMER exists - LICENSE and NOTICE fine (but see below) - All source files have ASF header - No unexpected binary files - Can compile from source I think you may have the wrong license in LICENSE for bootstrap as the css file [1] refers to the Apache licensed version copyright twitter not the MIT licensed version? Thanks, Justin 1. ./myriad-scheduler/src/main/resources/webapp/css/bootstrap-myriad.css - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Superset (incubating) 0.34.0 [RC1]
Hi, +1 (binding) I checked: - incubating in name - signatures and hashes fine - DISCLAIMER exists, although you may want to use the DISCLAIMER_WIP [8] - LICENSE is probably missing a few things (se below) - NOTICE is fine - No unexpected binary files - I didn’t check compiling from source LiCENSE is missing: - This BSD licensed file [1] The file also has an incorrectly has an ASF header on it. - This file in not mentioned [2] and I think is licensed like so [3] If so that may be problematic [4]. However I seem to recall this was discussed before so there may of been some conclusion about it? I also note that .*geojson are explicitly listed in your rat excludes so I assume there a reason for that. (Comments in the rat exclusion file could help here). - This file [5] looks to contain the Monokai theme from [6] I’m unsure how this is licensed. The pro version seems to require a commercial license. It might of come from here [7]? which is MIT licensed. Thanks, Justin 1. ./superset/extract_table_names.py 2 ./assets/src/visualizations/CountryMap/countries/india.geojson 3. ./licenses/LICENSE-diva-gis.txt 4. https://apache.org/legal/resolved.html#cc-by 5. superset/assets/src/components/FilterableTable/FilterableTable.jsx 6. https://www.monokai.nl 7 https://packagecontrol.io/packages/Monokai%20JSON%2B 8 https://incubator.apache.org/policy/incubation.html#disclaimers - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Showcase your project at ApacheCON at a Podling's Shark Tank
On Thu, Aug 15, 2019 at 8:06 AM Supun Kamburugamuve wrote: > > We are thinking about proposing a project to the incubator. Would this be > open to such a project? Given that we're already oversubscribed -- we can only allow existing podlings at this point. Thanks, Roman. > > Best, > Supun.. > > On Thu, Aug 15, 2019 at 10:05 AM Antoine Toulme wrote: > > > Hello Roman, > > > > The Tuweni podling is interested. I am attending ApacheCon EU and would > > like a chance to present. > > > > Cheers, > > > > Antoine > > > > > On Aug 14, 2019, at 1:45 PM, Roman Shaposhnik wrote: > > > > > > Hi Podlings! > > > > > > in less than a month we're going to have our first > > > ApacheCON this year -- the one in Las Vegas. In > > > about two month there will be one more in Berlin. > > > > > > These are not your regular ApacheCONs -- these are > > > 20th Anniversary of ASF ApacehCONs! In other words, > > > these are not to be missed! > > > > > > And even if your talk didn't get accepted -- you still > > > get an opportunity to highlight your project to, what's > > > likely going to be the biggest audience attending. > > > > > > Here's how: if you (or any community member who's > > > passionate about your project) are going to be at either > > > of those ApacheCONs consider signing up for > > >Podling's Shark Tank > > > events: > > >https://www.apachecon.com/acna19/s/#/scheduledEvent/1038 > > >https://aceu19.apachecon.com/session/podlings-shark-tank > > > > > > Each project presenting will get ~10 min for the pitch and ~5 min > > > of panel grilling them on all sorts of things. Kind of like this ;-) > > > https://www.youtube.com/watch?v=wmenN7NEdBc > > > > > > You've got nothing to lose (in fact, the opposite: you're likely to get > > > a prize!) and you will get a chance to receive feedback that might > > > actually help you grow your community and ultimately graduate to the > > > TLP status. And! Given our awesome panel of judges: > > > * Myrle Krantz > > > * Justin Mclean > > > * Craig Russel > > > * Shane Curcuru > > > We guarantee this to be a fun and useful event for your community! > > > > > > We will be tracking signups over here: > > > https://wiki.apache.org/apachecon/ACNA19PodlingSharkTank > > > https://wiki.apache.org/apachecon/ACEU19PodlingSharkTank > > > but for now: > > > > > > SIMPLY REPLY TO THIS EMAIL if you're interested. > > > > > > It is first come, first serve -- so don't delay -- sign up today! > > > > > > Thanks, > > > Roman. > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@tuweni.apache.org > > > For additional commands, e-mail: dev-h...@tuweni.apache.org > > > > > > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > -- > Supun Kamburugamuve, PhD > Digital Science Center, Indiana University > Member, Apache Software Foundation; http://www.apache.org > E-mail: supun@apache.o rg; Mobile: +1 812 219 2563 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Showcase your project at ApacheCON at a Podling's Shark Tank
Hi All! thanks a million for this tremendous interest in Podling's Shark Tank. We now have: ApacheCON NA in Las Vegas: Daffodil ShardingSphere Heron DLab IoTDB Daffodil Ratis DataSketches ApacheCON EU in Berlin: MorphL ShardingSphere DLab IoTDB Tuweni We now have full schedule of podlings for both events and I will be following up with individuals (and individual communities) who volunteered for both. Thanks, Roman. On Wed, Aug 14, 2019 at 1:45 PM Roman Shaposhnik wrote: > > Hi Podlings! > > in less than a month we're going to have our first > ApacheCON this year -- the one in Las Vegas. In > about two month there will be one more in Berlin. > > These are not your regular ApacheCONs -- these are > 20th Anniversary of ASF ApacehCONs! In other words, > these are not to be missed! > > And even if your talk didn't get accepted -- you still > get an opportunity to highlight your project to, what's > likely going to be the biggest audience attending. > > Here's how: if you (or any community member who's > passionate about your project) are going to be at either > of those ApacheCONs consider signing up for > Podling's Shark Tank > events: > https://www.apachecon.com/acna19/s/#/scheduledEvent/1038 > https://aceu19.apachecon.com/session/podlings-shark-tank > > Each project presenting will get ~10 min for the pitch and ~5 min > of panel grilling them on all sorts of things. Kind of like this ;-) > https://www.youtube.com/watch?v=wmenN7NEdBc > > You've got nothing to lose (in fact, the opposite: you're likely to get > a prize!) and you will get a chance to receive feedback that might > actually help you grow your community and ultimately graduate to the > TLP status. And! Given our awesome panel of judges: > * Myrle Krantz > * Justin Mclean > * Craig Russel > * Shane Curcuru > We guarantee this to be a fun and useful event for your community! > > We will be tracking signups over here: > https://wiki.apache.org/apachecon/ACNA19PodlingSharkTank > https://wiki.apache.org/apachecon/ACEU19PodlingSharkTank > but for now: > > SIMPLY REPLY TO THIS EMAIL if you're interested. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [OFFER] Offer to Mentor one or two podlings
At Apache Myriad we need some help, our more active mentor is really busy right now. Myriad => Hadoop YARN (Big Data) and the awesome Mesos, what else! ;-) -- Javi Roman Twitter: @javiromanrh GitHub: github.com/javiroman Linkedin: es.linkedin.com/in/javiroman Big Data Blog: dataintensive.info Apache Id: javiroman On Tue, Aug 20, 2019 at 5:42 PM John D. Ament wrote: > > Julian, > > Apache Tamaya could use help. My activity has been reduced pretty heavily as > of late. > > John > > On 2019/08/13 06:21:54, Julian Feinauer wrote: > > Hi, > > > > this goes to the IPMC as well as to podlings watching this list. > > I just recently became IPMC member and am currently pretty active in the > > IoTDB Project as “informal mentor” (started there before becoming IPMC > > member) together with 3 other pretty active mentors. > > As I received a lot of help from mentors and learned a lot about the Apache > > Way since I joined incubating projects, I think its time now to give > > something back. I could join one or two other podlings as Mentor if I am > > needed. > > > > I gained a reasonable amount of “podling” experience hands-on during the > > last 2 years after joining the PLC4X project and moving from release 0.1 to > > TLP and am active in other Podlings. > > My main interest is in the IoT, Big Data and analytics area (I’m active in > > PLC4X, Edgent, IoTDB and sometimes in Calcite) and mostly on the JVM. So > > this is the area where I could help most, I guess. > > > > So if someone has an idea where I can help, feel free to contact me! > > > > Julian > > > > - > 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: [OFFER] Offer to Mentor one or two podlings
Julian, Apache Tamaya could use help. My activity has been reduced pretty heavily as of late. John On 2019/08/13 06:21:54, Julian Feinauer wrote: > Hi, > > this goes to the IPMC as well as to podlings watching this list. > I just recently became IPMC member and am currently pretty active in the > IoTDB Project as “informal mentor” (started there before becoming IPMC > member) together with 3 other pretty active mentors. > As I received a lot of help from mentors and learned a lot about the Apache > Way since I joined incubating projects, I think its time now to give > something back. I could join one or two other podlings as Mentor if I am > needed. > > I gained a reasonable amount of “podling” experience hands-on during the last > 2 years after joining the PLC4X project and moving from release 0.1 to TLP > and am active in other Podlings. > My main interest is in the IoT, Big Data and analytics area (I’m active in > PLC4X, Edgent, IoTDB and sometimes in Calcite) and mostly on the JVM. So this > is the area where I could help most, I guess. > > So if someone has an idea where I can help, feel free to contact me! > > Julian > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [IP CLEARANCE] Apache Celix - Websocket pubsub admin
+1 On Tue, 20 Aug 2019 at 00:39, Furkan KAMACI wrote: > > Hi, > > +1 > > Kind Regards, > Furkan KAMACI > > 20 Ağu 2019 Sal, saat 08:04 tarihinde Roy Lenferink > şunu yazdı: > > > Hi all, > > > > Apache Celix received a donation which adds an additional pubsub admin > > to Celix. This pubsub admin uses websockets as communication technique > > and can be used next to the existing ZeroMQ, TCP or UDP multicast pubsub > > admins. No new third party dependencies are added. > > > > The IP clearance form can be found at: > > http://incubator.apache.org/ip-clearance/celix-pubsub-admin-websocket.html > > > > The pull request containing the donation can be found at: > > https://github.com/apache/celix/pull/39 > > > > Please vote to approve this contribution. Lazy consensus applies: > > if no -1 votes are being cast within the next 72 hours, the vote passes. > > > > Greetings, > > Roy > > -- Matt Sicker - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release 1.1.0-incubating-RC2
+1 - code compiles - incubating in name - LICENSE, NOTICE is fine - No unexpected binary files Thanks, William On Tue, Aug 20, 2019 at 10:30 PM Roman Leventov wrote: > +1 > > On Tue, 20 Aug 2019 at 17:05, Furkan KAMACI > wrote: > > > Hi, > > > > +1 from me. > > > > I checked: > > > > - Incubating in name > > - LICENSE is fine > > - NOTICE is fine > > - No unexpected binary files > > - Code compiles and tests successfully run > > > > One objection: DISCLAIMER file should be renamed to DISCLAIMER-WIP and > link > > at content should point to datasketches. > > > > Kind Regards, > > Furkan KAMACI > > > > On Mon, Aug 19, 2019 at 11:46 PM leerho wrote: > > > > > Hello Apache DataSketches IPMC and Community, > > > > > > 1. This is a call for vote to release Apache DataSketches-memory > version: > > > 1.1.0-incubating-RC2 > > > > > > NOTE 1: This is one component of the DataSketches library that provides > > > high-performance access > > > to off-heap memory for Java applications. These are low-level functions > > > that are used by other > > > DataSketches components. It does not provide any command-line interface > > or > > > GUI. > > > > > > NOTE 2: This release contains some critical performance improvements > for > > > Apache Druid. > > > > > > NOTE 3: This particular component has been split out from the rest of > the > > > DataSketches > > > code because there have been a number of requests from platform > projects > > > that are interested in > > > these high-performance functions independently of the remainder of the > > > DataSketches library. > > > > > > NOTE 4: This RC2 fixes some problems in the structure of the POM file > of > > > RC1. There are no other changes. > > > > > > A. Results from the PPMC vote (open for 140 hours (including the > > > weekend)) > > > > > > - 3 votes were cast. All of the votes were (+1). Two of the votes > > were > > > from Mentors. > > > > > > - The vote thread can be found at: > > > > > > https://mail-archives.apache.org/mod_mbox/datasketches-dev/201907.mbox/browser > > > > > > > > > B. Testing/actions/votes performed by the voters: > > > > > > - Gian Merlino: (+1) > > > - .asc and .sha512 look good. > > > - git.properties looks good. > > > - Ran "mvn package" without issue. > > > - Source tarball contents match the tag. > > > > > > Gian made several suggestions for improvements for next > release: > > > - have the zip unpack in its own directory not the current > > > directory > > > - DISCLAMER > > > - should be renamed DISCLAMER-WIP > > > - links to > > > http://incubator.apache.org/project/#Podling-Name#.html, but it should > > be > > > https://incubator.apache.org/projects/datasketches.html. > > > (fill in project name, > > > 'projects' instead of 'project', http would work but > https > > > is nicer.) > > > - Vote procedure: > > > - Clarify sentence to require not just 3 (+1) votes, but a > > > majority of (+1s) vs (-1s). > > > - When cancelling a vote use subject [CANCEL][VOTE] ... > > > > > > - Liang Chen (+1 binding) > > > - no comments > > > > > > - Furkan Kamaci (+1 binding) > > > - Incubating in name > > > - LICENSE is fine > > > - NOTICE is fine > > > - No unexpected binary files > > > - Code compiles and tests successfully run > > > - One objection: DISCLAIMER file should be renamed to > > DISCLAIMER-WIP > > > and link > > > at content should point to datasketches. > > > > > > 2. The release candidate: > > > > > > > > > https://dist.apache.org/repos/dist/dev/incubator/datasketches/memory/1.1.0-incubating-RC1/apache-datasketches-memory-1.1.0-incubating-src.zip > > > > > > 3. Source repository: > > > https://github.com/apache/incubator-datasketches-memory > > > > > > Git Tag for this release: > > > > > > > > > https://github.com/apache/incubator-datasketches-memory/tree/1.1.0-incubating-RC1 > > > on branch 1.1.X-incubating > > > > > > Git HashId for this release starts with: 32de195 > > > > > > The artifacts have been signed with --keyid-format SHORT : 8CD4A902 > > > > > > 4. Repository: dist.apache.org repository: > > > > > > The public signing key can be found in the KEYS file: > > > https://dist.apache.org/repos/dist/dev/incubator/datasketches/KEYS > > > > > > 5. Repository: Maven Central (repository.apache.org): > > > > > > The Jar artifacts can be found at > > > > > > > > > https://repository.apache.org/content/groups/staging/org/apache/datasketches/datasketches-memory/1.1.0-incubating/ > > > > > > 6. Build & Test Guide: > > > > > > The DataSketches-memory component is pure Java and is structured as a > > > Maven project. You must compile using JDK 8. > > > There is one run-time dependency for logging and, of course, a number > of > > > test and Maven plugin dependencies, > > > all of which can be resolved by Maven. > > > > > >
Re: [VOTE] Release 1.1.0-incubating-RC2
+1 On Tue, 20 Aug 2019 at 17:05, Furkan KAMACI wrote: > Hi, > > +1 from me. > > I checked: > > - Incubating in name > - LICENSE is fine > - NOTICE is fine > - No unexpected binary files > - Code compiles and tests successfully run > > One objection: DISCLAIMER file should be renamed to DISCLAIMER-WIP and link > at content should point to datasketches. > > Kind Regards, > Furkan KAMACI > > On Mon, Aug 19, 2019 at 11:46 PM leerho wrote: > > > Hello Apache DataSketches IPMC and Community, > > > > 1. This is a call for vote to release Apache DataSketches-memory version: > > 1.1.0-incubating-RC2 > > > > NOTE 1: This is one component of the DataSketches library that provides > > high-performance access > > to off-heap memory for Java applications. These are low-level functions > > that are used by other > > DataSketches components. It does not provide any command-line interface > or > > GUI. > > > > NOTE 2: This release contains some critical performance improvements for > > Apache Druid. > > > > NOTE 3: This particular component has been split out from the rest of the > > DataSketches > > code because there have been a number of requests from platform projects > > that are interested in > > these high-performance functions independently of the remainder of the > > DataSketches library. > > > > NOTE 4: This RC2 fixes some problems in the structure of the POM file of > > RC1. There are no other changes. > > > > A. Results from the PPMC vote (open for 140 hours (including the > > weekend)) > > > > - 3 votes were cast. All of the votes were (+1). Two of the votes > were > > from Mentors. > > > > - The vote thread can be found at: > > > https://mail-archives.apache.org/mod_mbox/datasketches-dev/201907.mbox/browser > > > > > > B. Testing/actions/votes performed by the voters: > > > > - Gian Merlino: (+1) > > - .asc and .sha512 look good. > > - git.properties looks good. > > - Ran "mvn package" without issue. > > - Source tarball contents match the tag. > > > > Gian made several suggestions for improvements for next release: > > - have the zip unpack in its own directory not the current > > directory > > - DISCLAMER > > - should be renamed DISCLAMER-WIP > > - links to > > http://incubator.apache.org/project/#Podling-Name#.html, but it should > be > > https://incubator.apache.org/projects/datasketches.html. > > (fill in project name, > > 'projects' instead of 'project', http would work but https > > is nicer.) > > - Vote procedure: > > - Clarify sentence to require not just 3 (+1) votes, but a > > majority of (+1s) vs (-1s). > > - When cancelling a vote use subject [CANCEL][VOTE] ... > > > > - Liang Chen (+1 binding) > > - no comments > > > > - Furkan Kamaci (+1 binding) > > - Incubating in name > > - LICENSE is fine > > - NOTICE is fine > > - No unexpected binary files > > - Code compiles and tests successfully run > > - One objection: DISCLAIMER file should be renamed to > DISCLAIMER-WIP > > and link > > at content should point to datasketches. > > > > 2. The release candidate: > > > > > https://dist.apache.org/repos/dist/dev/incubator/datasketches/memory/1.1.0-incubating-RC1/apache-datasketches-memory-1.1.0-incubating-src.zip > > > > 3. Source repository: > > https://github.com/apache/incubator-datasketches-memory > > > > Git Tag for this release: > > > > > https://github.com/apache/incubator-datasketches-memory/tree/1.1.0-incubating-RC1 > > on branch 1.1.X-incubating > > > > Git HashId for this release starts with: 32de195 > > > > The artifacts have been signed with --keyid-format SHORT : 8CD4A902 > > > > 4. Repository: dist.apache.org repository: > > > > The public signing key can be found in the KEYS file: > > https://dist.apache.org/repos/dist/dev/incubator/datasketches/KEYS > > > > 5. Repository: Maven Central (repository.apache.org): > > > > The Jar artifacts can be found at > > > > > https://repository.apache.org/content/groups/staging/org/apache/datasketches/datasketches-memory/1.1.0-incubating/ > > > > 6. Build & Test Guide: > > > > The DataSketches-memory component is pure Java and is structured as a > > Maven project. You must compile using JDK 8. > > There is one run-time dependency for logging and, of course, a number of > > test and Maven plugin dependencies, > > all of which can be resolved by Maven. > > > > There are two types of tests: normal unit tests and tests run by the > > strict profile. To run normal unit tests: > > > > $ mvn clean test > > > > To run the strict profile tests: > > > > $ mvn clean test -P strict > > > > To install jars in your local .m2 repository: > > > > $ mvn clean install > > > > 7. Documentation: The documentation for the DataSketches Memory component > > is part of the website. > > > > Overview documentation: > > - https://datasketches.gith
Re: [VOTE] Release 1.1.0-incubating-RC2
Hi, +1 from me. I checked: - Incubating in name - LICENSE is fine - NOTICE is fine - No unexpected binary files - Code compiles and tests successfully run One objection: DISCLAIMER file should be renamed to DISCLAIMER-WIP and link at content should point to datasketches. Kind Regards, Furkan KAMACI On Mon, Aug 19, 2019 at 11:46 PM leerho wrote: > Hello Apache DataSketches IPMC and Community, > > 1. This is a call for vote to release Apache DataSketches-memory version: > 1.1.0-incubating-RC2 > > NOTE 1: This is one component of the DataSketches library that provides > high-performance access > to off-heap memory for Java applications. These are low-level functions > that are used by other > DataSketches components. It does not provide any command-line interface or > GUI. > > NOTE 2: This release contains some critical performance improvements for > Apache Druid. > > NOTE 3: This particular component has been split out from the rest of the > DataSketches > code because there have been a number of requests from platform projects > that are interested in > these high-performance functions independently of the remainder of the > DataSketches library. > > NOTE 4: This RC2 fixes some problems in the structure of the POM file of > RC1. There are no other changes. > > A. Results from the PPMC vote (open for 140 hours (including the > weekend)) > > - 3 votes were cast. All of the votes were (+1). Two of the votes were > from Mentors. > > - The vote thread can be found at: > https://mail-archives.apache.org/mod_mbox/datasketches-dev/201907.mbox/browser > > > B. Testing/actions/votes performed by the voters: > > - Gian Merlino: (+1) > - .asc and .sha512 look good. > - git.properties looks good. > - Ran "mvn package" without issue. > - Source tarball contents match the tag. > > Gian made several suggestions for improvements for next release: > - have the zip unpack in its own directory not the current > directory > - DISCLAMER > - should be renamed DISCLAMER-WIP > - links to > http://incubator.apache.org/project/#Podling-Name#.html, but it should be > https://incubator.apache.org/projects/datasketches.html. > (fill in project name, > 'projects' instead of 'project', http would work but https > is nicer.) > - Vote procedure: > - Clarify sentence to require not just 3 (+1) votes, but a > majority of (+1s) vs (-1s). > - When cancelling a vote use subject [CANCEL][VOTE] ... > > - Liang Chen (+1 binding) > - no comments > > - Furkan Kamaci (+1 binding) > - Incubating in name > - LICENSE is fine > - NOTICE is fine > - No unexpected binary files > - Code compiles and tests successfully run > - One objection: DISCLAIMER file should be renamed to DISCLAIMER-WIP > and link > at content should point to datasketches. > > 2. The release candidate: > > https://dist.apache.org/repos/dist/dev/incubator/datasketches/memory/1.1.0-incubating-RC1/apache-datasketches-memory-1.1.0-incubating-src.zip > > 3. Source repository: > https://github.com/apache/incubator-datasketches-memory > > Git Tag for this release: > > https://github.com/apache/incubator-datasketches-memory/tree/1.1.0-incubating-RC1 > on branch 1.1.X-incubating > > Git HashId for this release starts with: 32de195 > > The artifacts have been signed with --keyid-format SHORT : 8CD4A902 > > 4. Repository: dist.apache.org repository: > > The public signing key can be found in the KEYS file: > https://dist.apache.org/repos/dist/dev/incubator/datasketches/KEYS > > 5. Repository: Maven Central (repository.apache.org): > > The Jar artifacts can be found at > > https://repository.apache.org/content/groups/staging/org/apache/datasketches/datasketches-memory/1.1.0-incubating/ > > 6. Build & Test Guide: > > The DataSketches-memory component is pure Java and is structured as a > Maven project. You must compile using JDK 8. > There is one run-time dependency for logging and, of course, a number of > test and Maven plugin dependencies, > all of which can be resolved by Maven. > > There are two types of tests: normal unit tests and tests run by the > strict profile. To run normal unit tests: > > $ mvn clean test > > To run the strict profile tests: > > $ mvn clean test -P strict > > To install jars in your local .m2 repository: > > $ mvn clean install > > 7. Documentation: The documentation for the DataSketches Memory component > is part of the website. > > Overview documentation: > - https://datasketches.github.io/docs/Memory/MemoryPackage.html > - https://datasketches.github.io/docs/Memory/MemoryPerformance.html > > Javadocs: > - https://datasketches.github.io/api/memory/snapshot/apidocs/index.html > > 8. This vote is the 2nd stage vote: >- This voting process will remain open for at least 72 hours > and until at least 3 (+1) IPMC votes or a majori
[VOTE] Release Apache ShardingSphere (Incubating) 4.0.0-RC2
Hello all, This is a call for vote to release Apache ShardingSphere (Incubating) version 4.0.0-RC2. The Apache ShardingSphere community has voted on and approved a proposal to release Apache ShardingSphere (Incubating) version 4.0.0-RC2. We now kindly request the Incubator PMC members review and vote on this incubator release. ShardingSphere is an open-source ecosystem consisted of a set of distributed database middleware solutions, including 2 independent products, Sharding-JDBC & Sharding-Proxy. Sharding-JDBC is an enhanced JDBC driver that provides in-process transparent distributed database by connecting to multiple database back ends. It supports many ORM frameworks and database connection pools and supports many back end databases that have JDBC interfaces: MySQL, Oracle, SQLServer and PostgreSQL. Sharding-Proxy is a database proxy that runs in a separate process and appears as a database server to multiple back end databases. It supports multiple client front ends such as MySQL Command Client, MySQL Workbench, Navicat etc. Current support is for MySQL and PostgreSQL. ShardingSphere community vote and result thread: https://lists.apache.org/thread.html/4b29490f433dd26cc85d0e00340def3bd0f7b64e4bd2f3512e568bcd@%3Cdev.shardingsphere.apache.org%3E Release notes: https://github.com/apache/incubator-shardingsphere/blob/dev/RELEASE-NOTES.md The release candidates: https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.0-RC2/ Maven 2 staging repository: https://repository.apache.org/content/repositories/staging/org/apache/shardingsphere/ Git tag for the release: https://github.com/apache/incubator-shardingsphere/tree/4.0.0-RC2 Release Commit ID: https://github.com/apache/incubator-shardingsphere/commit/85f2ff877a7aaf122998964a0d03f7c9b2830e36 Keys to verify the Release Candidate: https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/KEYS GPG username: zhangyonglun Look at here for how to verify this release candidate: https://shardingsphere.apache.org/community/en/contribute/release/ 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 Checklist for reference: [ ] Download links are valid. [ ] Checksums and PGP signatures are valid. [ ] DISCLAIMER is included. [ ] Source code artifacts have correct names matching the current release. [ ] LICENSE and NOTICE files are correct for each ShardingSphere repo. [ ] All files have license headers if necessary. [ ] No compiled archives bundled in source archive. -- Zhang Yonglun Apache ShardingSphere
[Remind] [Result][VOTE] Accept MesaTEE into Apache Incubator
I think this proposal should be hold a little longer. The champion of this proposal is not a member of IPMC yet. Sheng Wu 吴晟 Apache SkyWalking, Apache ShardingSphere(Incubating), Zipkin Twitter, wusheng1108 Zhijie Shen 于2019年8月20日周二 下午2:24写道： > Hi folks, > > With 7 +1 binding votes, 1 +1 non-binding votes and no +0 or -1 votes, this > VOTE passes. > > Thanks to everyone who voted! Bellow is a voting tally (* is binding): > > Stian Soiland-Reyes* > Matt Sicker* > Luciano Resende* > Furkan KAMACI* > Kenneth Knowles* > Wei Mingzhi > Byung-Gon Chun* > Daniel Dai* > > The vote thread: > > https://lists.apache.org/thread.html/46dc067c4f4d58e947767a8450c11060f671e68a51f47fca6f0b553b@%3Cgeneral.incubator.apache.org%3E > > Thanks, > Zhijie >
Re: [VOTE] Release Apache Myriad 0.4.0 (incubating) [rc1]
Hi, +1 from me. I checked: - Incubating in name - DISCLAIMER exists - LICENSE and NOTICE are fine - No unexpected binary files - Checked PGP signatures - Checked Checksums - Code compiles and tests successfully run One objection: you should fix the binary versions at next release as Javi Roman suggested at your vote thread of incubator list. Kind Regards, Furkan KAMACI On Tue, Aug 20, 2019 at 9:58 AM Oscar Fernandez wrote: > Dear all, > > The Apache Myriad incubator community has voted on and approved a proposal > to release Apache Myriad (Incubating) version 0.4.0. > > We now kindly request the Incubator PMC members review and vote on this > incubator release. > > Apache Myriad (incubating) enables co-existence of Apache Hadoop YARN and > Apache Mesos together on the same cluster and allows dynamic resource > allocations. > > By running Hadoop YARN as a Mesos framework, YARN applications and Mesos > frameworks can run side-by-side, dynamically sharing cluster resources > (Hadoop YARN as a Service). > > 1. Apache Myriad PPMC vote thread: > > https://lists.apache.org/thread.html/8a51eafe1015ff152df1db3dcdc9f618c38ec437417ebfb76f82b74d@%3Cdev.myriad.apache.org%3E > > 2. Apache Myriad PPMC vote result: > > https://lists.apache.org/thread.html/27b5c569b7e5f14237fee21e1c602ab53bea529867e53e2f1220c797@%3Cdev.myriad.apache.org%3E > > 3. Here’s the release notes: > https://github.com/apache/incubator-myriad/blob/master/CHANGELOG.md > > 4. The commit to be voted upon is tagged with "myriad-0.4.0-incubating-rc1" > and is available here: > > https://gitbox.apache.org/repos/asf?p=incubator-myriad.git;a=commit;h=019fba2be3e310302cd60a25d7d71f1310c9d5a5 > > 5. The artifacts to be voted upon are located below. Please note that this > is a Source Release: > > https://dist.apache.org/repos/dist/dev/incubator/myriad/myriad-0.4.0-incubating-rc1/ > > 6. Release artifacts are signed with the following key: > https://people.apache.org/keys/committer/oscarfmdc.asc > > 7. Please note that the release tar ball does not include the gradlew > script to build. You need to generate one in order to build: > $ gradle wrapper --gradle-version 5.5 > $ ./gradlew build > > We request the permission of IPMC to publish the above release candidate as > Apache Myriad 0.4.0-incubating. Please try out the package and vote. > > The vote is open for a minimum of 72 hours or until the necessary number of > votes (3 binding +1s) is reached. > > [ ] +1 Release this package as Apache Myriad 0.4.0-incubating > [ ] 0 I don't feel strongly about it, but I'm okay with the release > [ ] -1 Do not release this package because... > > Many thanks! > > (Volunteer Release Manager of Apache Myriad, incubating 0.4.0 on behalf on > the Apache Myriad PPMC) >
