Re: [VOTE] Have Amoro join the Incubator

+1 binding On Sun, Mar 3, 2024 at 11:45 AM Justin Mclean wrote: > > Hi, > > Following on from the discussion of the Amoro proposal [1][2], let's vote on > having it join the Incubator. > > Please cast your vote: > > [ ] +1, have it join the Incubator as an incubating project > [ ] +0, I have no

Re: [VOTE] Graduate Apache Pekko (incubating) as a TLP

+1 (binding). Good luck! On Mon, Feb 26, 2024 at 9:25 PM PJ Fanning wrote: > > Hi everyone, > > We have positive feedback on the Pekko Vote thread [1] (result [2]). > > I'd like to start an official Incubator VOTE thread now. > > Below are some facts and project highlights from the incubation

Re: [DISCUSS] Graduate Apache SDAP (Incubating) as a Top Level Project

+1 (binding). Good luck! On Fri, Feb 23, 2024 at 4:02 AM Riley Kuttruff wrote: > > Hi all, > > Apache SDAP joined Incubator in October 2017. In the time since, we've > made significant progress towards maturing our community and our > project and adopting the Apache Way. > > After community

Re: [VOTE] Release Apache Pekko(incubating) Core 1.0.2-RC1

src/main/java/com/clearspring/analytics/stream/frequency/CountMinSketch.java > > > On Wed, 29 Nov 2023 at 00:59, Paul King wrote: > > > > +1 (binding) > > > > [X] Download links are valid. > > [X] Checksums and signatures. > > [X] LICENSE/NOTICE files

Re: [VOTE] Release Apache Pekko(incubating) Core 1.0.2-RC1

+1 (binding) [X] Download links are valid. [X] Checksums and signatures. [X] LICENSE/NOTICE files exist I did notice "Copyright 2016 AddThis" in the LICENSE file wrt MurmurHash3, something to fix for the next release? Given the accompanying explanation in the file, I don't see this as a

Re: [VOTE] Release Apache Pekko(incubating) Core 1.0.2-RC1

I'll take a look. On Mon, Nov 27, 2023 at 11:46 PM PJ Fanning wrote: > > Hi everyone, > > This RC includes a security hardening change. I am wondering if any Pekko > mentors or any other Incubator PMC member might have time to review the RC > artifacts so that we can do a release. > > Thanks,

Re: [VOTE] Retirement of the Apache DataLab

+1 binding On Wed, Aug 9, 2023 at 7:28 PM Ruslan Kulynych wrote: > > Hi all, > > Based on discussion[1], I would like to call for a vote to retire the Apache > DataLab. > > The voting will last for at least one week to ensure that everyone has time > to express their opinions. > > Please vote

Re: [VOTE] Release Apache Wayang (Incubating) v0.7.1 RC3

+1 (binding) I checked LICENSE, NOTICE, DISCLAIMER, checksum and signature. I see Chris has given you useful input on other aspects in the podling vote, so I won't duplicate. "mvn clean install" worked fine on Ubuntu but failed for me on Windows (could be my setup). For the vote email, you

Re: is it ok to modify copyright headers that have no end year?

IANAL, but the advice I've been given informally by IP lawyer friends many years ago is don't change the existing copyright. You could instead amend to something like: Original version: > Copyright (C) since 2016 Lightbend Inc. > Subsequent changes made by the Apache Pekko community: > Copyright

Re: [VOTE] Retire PageSpeed

+1 On Tue, Mar 14, 2023 at 6:47 AM Christian Grobmeier wrote: > Hello, > > as recently discussed, I think the PageSpeed podling is ready for > retirement. > > https://lists.apache.org/thread/jxw7mqmpcfxxp0mnnx28o0k78tym507b > > There has been no activity for a while; there are no signs of

Re: [VOTE] Retire Hivemall from Incubator

+1 to retire (binding) On Sun, Aug 28, 2022 at 4:57 PM Calvin Kirs wrote: > > Hi IPMC, > > Hivemall has been incubating since 2016-09-13. > > From last year, activity has been low and the chances of attracting new > committers and building a vibrant community seem very slim at this point. > >

Re: [VOTE] Release Apache EventMesh(Incubating) 1.5.0-rc0

Yes, the build file is using (just a little) Groovy 3 syntax (new in Gradle 7). You could revert to older style syntax but it would probably be better to have a bootstrap step that downloaded the gradle wrapper and then use the wrapper in all of your instructions. The Groovy build has such a

Re: [VOTE] Graduate Apache InLong(Incubating) as a TLP

+1 (binding) Best of luck going forward! Cheers, Paul. On Wed, May 25, 2022 at 4:33 PM Charles Zhang wrote: > > Dear Apache Incubator Community, > > > The InLong community has a discussion thread [1], passed the community vote > [2], and the vote result is published [3]. We have discussed the

Re: [VOTE] Release Apache NLPCraft (incubating) v 0.9.0

+1 (binding) carrying forward my vote and comments from PPMC vote thread. On Sat, Jul 31, 2021 at 3:34 AM Aaron Radzinski wrote: > > Hello all, > This is a call for a vote to release Apache NLPCraft (incubating) > version 0.9.0. Apache NLPCraft is a library for adding a natural > language

Re: [VOTE] Graduate Apache Pinot as TLP

+1 binding, good luck! On Wed, Jun 23, 2021 at 5:44 AM Mayank Shrivastava wrote: > Dear Incubator Community, > > We have discussed Apache Pinot Podling graduation in the general@incubator > DISCUSS thread [1], and addressed all the questions and concerns brought up > in the thread. Please refer

Re: [VOTE] Release Apache NLPCraft (incubating) v 0.8.0

+1 (binding) carrying over my dev vote Virus-free. www.avast.com

Re: [VOTE] Release Apache NLPCraft - Java Client (incubating) 0.7.5

+1 binding from me, carrying over my vote On Sat, May 22, 2021 at 11:29 AM Aaron Radzinski wrote: > Hello all, > This is a call for a vote to release Apache NLPCraft - Java Client > (incubating) version 0.7.5. Apache NLPCraft is a library for adding a > natural language interface to any

Re: [VOTE] Release Apache NLPCraft (incubating) 0.7.5

+1 carrying forward my dev vote after the license/notice tweaks I don't think there is an issue with the license of the file mentioned, just the appropriate changes to the license/notice wording to ensure the licensing condition is properly understandable. And I think some other tweaks to

Re: [VOTE] Release Apache MXNet (incubating) version 1.8.0.rc3

s, Paul. On Wed, Mar 3, 2021 at 7:34 AM Leonard Lausen wrote: > Thank you Paul for voting on the release. > > On 2021/03/02 03:53:26, Paul King wrote: > > > * LICENSE file mentions 3rdparty/tvm/3rdparty/rang as "Unlicense". It > would > > be good to cla

Re: [VOTE] Release Apache MXNet (incubating) version 1.8.0.rc3

+1 (binding) Checked: - LICENSE and NOTICE seem okay - DISCLAIMER-WIP exists - Incubating in name - Checksum and signature okay - No unexpected binary file - Built shared library using cmake (without CUDA) - Built Java/Scala jars (also works for Groovy) Comments: * As others have noted, please

Re: [DISCUSS] Graduate Apache Daffodil to a top-level project

+1 (binding) Cheers, Paul. On Fri, Feb 5, 2021 at 5:01 AM Mike Beckerle wrote: > Incubator Folks, > > We have completed a vote on our community list d...@daffodil.apache.org as > follows: > > Vote Thread: > >

Re: [DISCUSS] Graduate Apache DolphinScheduler (incubating) as a TLP

+1 (binding) Cheers, Paul. On Fri, Feb 5, 2021 at 9:36 PM Gang Li wrote: > Hi all, > After discussion with the community [1] and [2], and a positive vote > result [3]. > We'd like to bring this to a discussing at the IPMC. > > Please see the proposed resolution below and let us know what do

Re: [VOTE] Release Apache NLPCraft (incubating) 0.7.4

+1 carrying my dev vote forward: https://lists.apache.org/thread.html/reb06a62c04fed54684c993e80fe01cfff849df3631d85f32e7ab1051%40%3Cdev.nlpcraft.apache.org%3E Cheers, Paul. Virus-free.

Re: [VOTE] Release Apache NLPCraft (incubating) 0.7.3

quot;C:\Progra~1\AdoptOpenJDK\jdk-11.0.8.10-hotspot\bin\java -jar "C:\Users\Paul King\AppData\Local\Temp\surefire7851445059229675487\surefirebooter6212500639838130057.jar" "C:\Users\Paul King\AppData\Local\Temp\surefire7851445059229675487" 2021-01-18T18-48-51_629-jvmRun1 surefire

Re: [VOTE] Accept Wayang into the Apache Incubator

+1 (binding) Virus-free. www.avast.com <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Sat, Dec 12, 2020

Re: [VOTE] Release Apache NLPCraft - Java Client (incubating) 0.7.2

+1 (binding) carrying my vote over from dev list On Tue, Dec 15, 2020 at 12:16 PM Aaron Radzinski wrote: > Hello all, > This is a call for a vote to release Apache NLPCraft - Java Client > (incubating) > version 0.7.2. Apache NLPCraft is a library for adding a natural language > interface to

Re: [VOTE] Release Apache NLPCraft (incubating) 0.7.2

+1 (binding) carrying over my vote On Tue, Nov 24, 2020 at 2:21 PM Aaron Radzinski wrote: > Hello all, > This is a call for a vote to release Apache NLPCraft (incubating) version > 0.7.2. Apache NLPCraft is a library for adding a natural language interface > to any application. > > The Apache

Re: [VOTE] Hop proposal

+1 (binding) Virus-free. www.avast.com <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Wed, Sep 16, 2020

Re: [VOTE] Release Apache NLPCraft (incubating) 0.7.0

+1, carrying my vote over from dev list Virus-free. www.avast.com

Re: [VOTE] Distribution guidelines for platforms

+1 On Mon, Jul 6, 2020 at 11:23 AM Justin Mclean wrote: > Hi, > > This vote is to make this official [1] and move the guidelines to the > website. The guidelines will be placed under the podling guides menu and > linked to from the release section in the Incubator policy page [2] > > The last

Re: [VOTE] Release Apache NLPCraft (Incubating) 0.6.2

+1 carrying my vote over from the dev list Checked hashes and signatures. "maven clean verify" passes (fails for me on Windows JDK8 as per NLPCRAFT-76, passes on Linux JDK11) "maven apache-rat:rat" passes (but it is configured to ignore failures, you can change numUnapprovedLicenses in the pom

Re: [VOTE] Distribution guidelines for platforms

My reading of the wording is that there is now more wiggle room for podlings rather than more restrictions. Cheers, Paul. On Mon, Jul 13, 2020 at 5:51 PM Justin Mclean wrote: > Hi, > > > I think all of these situations can occur with or without the new > incubator policy. > > It possibles yes,

[jira] [Commented] (INCUBATOR-253) Issues with MXNet releases and their distribution

[ https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17142439#comment-17142439 ] Paul King commented on INCUBATOR-253: - Anyone including PPMC members (with hat off) can build

Re: [VOTE] Release Apache NLPCraft (Incubating) 0.6.1

+1 (binding) carrying my dev vote forward. I'll note here for anyone running the test suite under Windows - there seems to be some issues on some systems that are being looked at in parallel and testing using WSL2 seems to avoid the problem. Cheers, Paul. On Sat, Jun 13, 2020 at 4:30 AM Aaron

Re: [VOTE] Accept Apache BlueMarlin in the incubator

+1 (binding) On Mon, May 25, 2020 at 4:27 PM Jean-Baptiste Onofre wrote: > Hi everyone, > > Following the discussion about BlueMarlin, I would like to start a formal > vote to accept BlueMarlin into the incubator. > > As reminder, here’s the proposal: >

Re: [VOTE] Release Apache NLPCraft - Java Client (Incubating) 0.5.0

+1 binding (carrying forward my earlier vote) On Mon, May 25, 2020 at 9:53 AM Aaron Radzinski wrote: > Hello all, > This is a call for a vote to release Apache NLPCraft - Java Client > (incubating) version 0.5.0. > > The Apache NLPCraft community has voted on and approved a proposal to >

Re: [VOTE] Release Apache NLPCraft (Incubating) 0.5.0

+1 (binding) Checked: + DISCLAIMER exists + incubating in name + no unexpected binary files + signature okay (from https://dist.apache.org/repos/dist/release/incubator/nlpcraft/KEYS) + checksum okay + LICENSE okay + NOTICE lines 1-5 correct (remove lines 6-95 for next release, they aren't

Re: [VOTE] Release Apache NLPCraft (Incubating) 0.5.0

oposed as a template in > https://incubator.apache.org/policy/incubation.html#releases > > Thanks, > -- > Nikita Ivanov > > > > On Thu, Apr 23, 2020 at 1:04 AM Paul King wrote: > >> Just on process, the "or until a necessary number of votes are reached&quo

Re: [VOTE] Release Apache NLPCraft (Incubating) 0.5.0

Just on process, the "or until a necessary number of votes are reached" won't apply. You might get 3 +1s straight away and a -1 a couple of days later. If that was the total votes, that would still be counted as a failing vote. Cheers, Paul. On Thu, Apr 23, 2020 at 3:52 PM Aaron Radzinski

Re: [VOTE] Release Apache Daffodil (incubating) 2.6.0-rc2

+1 (but I had some issues noted below which I presume are minor oversights or due to my environment) Checked: - signatures and hashes for src zip okay - incubating in name - DISCLAIMER exists - LICENSE and NOTICE files (root and daffodil-cli variants seem okay) - source files have ASF or

Re: [VOTE] Release Apache Daffodil (incubating) 2.6.0-rc2

-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Thu, Apr 23, 2020 at 5:18 PM Paul King wrote: > +1 (but I had some issues noted below which I presume are minor oversights > or due to my environment) > > Checked: > - signatures and hashes for src zip okay > - incubating in name > - DISCLAIMER ex

Re: [VOTE] Release Apache Superset (incubating) version 0.36.0

+1 (binding) Checked: - signature okay - checksum okay - incubating in name - DISCLAIMER exists - LICENSE and NOTICE seem okay - didn't appear to have any binary files within tarball (apart from images) - builds from source (using RELEASING/test_run_tarball.sh) Comments: - The instructions in

wiki permissions

I don't seem to have wiki permissions. Can someone please enable me? ApacheID: paulk Thanks, Paul.

Re: "Fork Me" on GitHub (was Re: [DISCUSS] Graduate Apache ShardingSphere (incubating) as a TLP)

I would think it is almost ubiquitous now for developers to know that the easiest way for them to create a PR for instance is to fork the project (the source code if you like) on Github. It seems sensible to encourage the use of "Fork me on Github" as it substantially lowers the barrier of

Re: [DISCUSS] Project proposal - Apache Rainbow

I'm probably leaning towards accepting. Given that the closest fit to me seems the DLAB project, I would be keen to see if anyone in that project has an interest in keeping abreast of developments in Rainbow. DLAB is itself also incubating so we wouldn't want to burden them with too many more

Re: [VOTE] Release SAMOA 0.5.0 (incubating) RC3

Looks like under "The developer's version artifacts" you have the sha512 hashes, but under the staging repo you just have sha1/md5. On Wed, Mar 18, 2020 at 7:58 AM Justin Mclean wrote: > HI, > > -1 (binding) because of hash issue - but this is easily fixed without > stopping the vote and

Re: [VOTE] Release SAMOA 0.5.0 (incubating) RC3

+1 (binding) with some caveats. I checked: * Incubating in name * DISCLAIMER exists * LICENSE and NOTICE okay (copyright end year in NOTICE needs a bump I would suspect) * Signatures okay * Checksums okay My understanding is that the KEYS file for your project is expected in:

Re: [VOTE] Apache Tuweni 1.0.0-incubating release

I had the same questions Justin mentioned wrt gossip and relayer but forgot to mention that. One approach could be to have your artifacts split into sources and distributions subdirectories (or similar names). Cheers, Paul. On Sun, Mar 15, 2020 at 5:37 PM Justin Mclean wrote: > Hi, > > +1

Re: [VOTE] Apache Tuweni 1.0.0-incubating release

+1 (binding) I checked: * Incubating in name * DISCLAIMER exists * LICENSE and NOTICE okay * Signatures okay * Checksums okay * Rat checks okay (hacked to make work without .git dir) I noticed two copies of many files within the tgz and zip source archives but this didn't seem to impact

Re: [VOTE] Release Apache Annotator (incubating) version 0.1.0 (-rc.1)

Hi Annotator dev team. Congrats on getting to this exciting stage! I am just checking up on process. Are you following the traditional podling release process: https://incubator.apache.org/policy/incubation.html#releases I.e. first a vote on dev mailing list followed by a subsequent vote from

Double entry for FreeMarker

Hi all, I noticed under Apache Projects: https://projects.apache.org/projects.html That FreeMarker is listed twice (even though they graduated in 2018): - Apache FreeMarker - Apache FreeMarker (Incubating)

Re: [DISCUSS] Project proposal - Apache Rainbow

Indeed, it does sound interesting. I would find it useful if the "existing Apache projects" bit of "Rainbow is in development, leveraging existing Apache projects." could be expanded in any way. I know there is a list of external dependencies later but any further description of how those

Re: [VOTE] Accept NLPCraft into Apache Incubator

+1 (binding) On Mon, Feb 10, 2020 at 7:54 AM Konstantin Boudnik wrote: > Hello. > > As the discussion of NLPCraft proposal [1] has been wrapped up [2] I would > like > to call a VOTE to accept this project into the Apache Incubator. > > Please cast your vote: > > [ ] +1, bring NLPCraft into

Re: [DISCUSS] NLPCraft Proposal

ubator the license will change to plain Apache > License, v2.0. There's no disagreement on this among project members. > Thanks! > -- > Nikita Ivanov > > > On Mon, Feb 3, 2020 at 9:35 PM Paul King wrote: > >> Looks like you have close to a full house for mentors. I c

Re: [DISCUSS] NLPCraft Proposal

Looks like you have close to a full house for mentors. I could certainly put my hat in the ring if you need another, otherwise I will certainly be an interested community member. It seems like an interesting project. I would have a particular interest in Groovy/Micronaut integration. I did notice

Re: [VOTE] Release Apache DataSketches-java 1.2.0-incubating-RC2

understanding correct? > > Lee. > > > > > > On Sat, Jan 25, 2020 at 3:19 PM Paul King wrote: > >> +1 (binding) with one minor comment >> >> Checked: >> * incubating in name >> * DISCLAIMER-WIP exists >> * LICENSE >> * NOTICE (

Re: [VOTE] Release Apache DataSketches-java 1.2.0-incubating-RC2

+1 (binding) with one minor comment Checked: * incubating in name * DISCLAIMER-WIP exists * LICENSE * NOTICE (year bump needed 2019 => 2019-2020 as already noted by Justin) * no unexpected binary files * signatures * hash * mvn clean install (1) * mvn apache-rat:check (1) Works on Linux. On

Re: [VOTE] Myriad retirement

+1 (binding) Cheers, Paul. On Fri, Jan 24, 2020 at 1:14 AM Javi Roman wrote: > Unfortunately, despite an effort to reboot the project about more than one > year, we weren't successful in keeping the existing committers active. At > this point, a decision to retire the podling was taken, and a

Re: [VOTE] Accept YuniKorn into Apache Incubator

+1 (binding) On Sat, Jan 11, 2020 at 3:47 AM Vinod Kumar Vavilapalli wrote: > Hi, > > I'd like to call a vote on accepting YuniKorn into the Apache Incubator. > > Please see the discussion thread [1]. > > Please see the full proposal: >

Re: [VOTE] Release Apache Superset (incubating) version 0.35.2

+1 (binding) with some minor comments below Checked: - incubating in name - checksum - signature - didn't appear to have any binary files within tarball (apart from images) - builds from source (with version change) Comments: - I followed the instructions in RELEASING/README.md to build from

Re: [VOTE] Recommend 'Apache Druid graduation to Top Level Project' resolution to the board

+1 binding Cheers, Paul. On Sun, Dec 8, 2019 at 7:55 AM Gian Merlino wrote: > Earlier this year, Druid voted to graduate to a top level project. The vote > passed in the Druid community and the Incubator, and a resolution was > submitted to the Board, but needed to be shelved at the last

Re: [VOTE] Apache BatchEE leaving the incubator

+1 to join Apache Geronimo On Fri., 6 Dec. 2019, 5:51 pm Romain Manni-Bucau, wrote: > Hi everyone, > > BatchEE community voted to leave the incubator to join Apache Geronimo as a > subproject. > > Here is the vote thread: >

Re: [VOTE] Accept NuttX into the Apache Incubator

+1 binding On Wed, Dec 4, 2019 at 3:30 PM 俊平堵 wrote: > Hi folks, > > > The [DISCUSS] thread on NuttX has died down. > > > Accordingly, I would like to call a VOTE to accept NuttX into the > > Apache Incubator. > > > Please cast your vote: > > > [ ] +1, bring NuttX into the Incubator > > [ ]

Re: Remove PMC incubator page

+1 On Fri, Oct 18, 2019 at 6:59 PM Justin Mclean wrote: > Hi, > > The page here [1] doesn’t really add anything that is not written out > elsewhere and seems redundant. If no-one objects I’ll remove it. > > Thanks, > Justin > > > 1. https://incubator.apache.org/guides/pmc.html >

Re: [VOTE] Recommend Apache Rya graduation to Top Level Project resolution to the Board

+1 On Fri., 6 Sep. 2019, 6:29 pm Adina Crainiceanu, wrote: > The Apache Rya (incubating) community is bringing the attached resolution > to graduate to a Top Level Project up for a formal IPMC VOTE. > > -We completed all the tasks documented in the status file [1] > -The name Apache Rya was

Re: [VOTE] Recommend 'Apache Druid graduation to Top Level Project' resolution to the board

+1 (binding) Good luck! Cheers, Paul. On Tue, Aug 13, 2019 at 5:03 PM Gian Merlino wrote: > The Apache Druid community has recently discussed our readiness for > graduation [1] and voted on it affirmatively [2, 3]. We've also assessed > ourselves against the maturity model [4] and collaborated

Re: [DISCUSS] IPMC votes on releases

Another variation/option for those using the WIP disclaimer might be that since the WIP disclaimer kind of says this release doesn't have "full official" status from an ASF point of view then one way of thinking about it is that perhaps full official IPMC endorsement is less of a requirement so

Re: [MENTORS] IPMC Policy change work in progress disclaimer

Kudos for progressing this idea. I really like it. It should allow improvements from the perspective of both podlings and reviewers. Cheers, Paul. On Fri, Aug 2, 2019 at 12:25 PM Justin Mclean wrote: > Hi, > > The work in progress progress disclaimer (DISCLAIMER-WIP) has been added > to the

Re: [VOTE] Heron Release 0.20.1-incubating Release Candidate 3

+1 (binding) I checked: - incubating in name - DISCLAIMER present - Signature and hashes okay - LICENSE is missing a number of permissive licenses (I didn't check ones Justin had already covered but third_party\python\semver seems to be missing from list of BSD licensed software though it does

Re: [VOTE] Release Apache Rya (Incubating) version 4.0.0 RC1

+1 (binding) I checked: - incubating in name - signatures and hashes okay - DISCLAIMER exists - NOTICE year needs updating as previously noted (fix next release) - LICENSE is okay - No unexpected binary files - Al files have ASF headers - `mvn -DskipTests clean install` passes - `mvn clean

Re: DLab needs help

I've jumped on their dev list as well and can try to help out informally. Let's see how it goes with Furkan helping and I consider a more formal role if they still need help. Cheers, Paul. On Wed, Jul 24, 2019 at 8:37 PM Furkan KAMACI wrote: > Hi, > > Thanks Justin! I've just started to write

Re: Cookbook and duplication of content on incubator site

All sounds good to me too! +1 On Wed, Jul 24, 2019 at 6:26 PM Bertrand Delacretaz < bdelacre...@codeconsult.ch> wrote: > Hi Justin, > > Thank you for addressing this, I was planning to work on this > duplication of content but didn't get to it yet. > > On Wed, Jul 24, 2019 at 8:44 AM Justin

Re: DataSketches needs some help

I have subscribed to their dev list. I'll try to help out a bit informally if I can. If needed I might be able to assist with Mentoring but I don't have a lot of cycles free at the moment. Cheers, Paul. On Wed, Jul 24, 2019 at 10:57 AM Justin Mclean wrote: > Hi, > > DataSketches seems to be

Re: New disclaimer text

+1 for: DISCLAIMER-PERMISSIVE or DISCLAIMER-WIP Virus-free. www.avast.com

Re: [VOTE] Release Apache MXNet (incubating) version 1.5.0.rc2

+1 binding checked signature/checksum/disclaimer license seems very thorough but two possible clarifications are suggested below (*) ran `make lib/libmxnet.so` successfully (opencv was listed as an optional dependency but it seemed to be needed for this to work) ran `make scalapkg` to generate

Re: New disclaimer text

+1 On Sat, Jul 13, 2019 at 10:44 AM Sheng Wu wrote: > +1 from me to have two disclaimers, chosen by podings. > > Also, +1 from me, the one they chosen should stay in website and > announcement. > > Sheng > > Justin Mclean 于2019年7月13日 周六上午9:37写道： > > > Hi, > > > > +1 Works for me. > > > > It

Re: [Discuss] Graduate Apache OpenWhisk (incubating) as a TLP

I have been following some of the OpenWhisk traffic on the mailing list but mostly at arms length, so I thought I would have my first play writing a Groovy action this evening to see if the process would shed any light on the project's graduation readiness. The result (with kudos to Markus Thömmes

Re: [VOTE] Release Apache Flagon (Incubating) v2.0.0

we could manage to get headers in those these build > files resulted in some repetition of headers from various arc files. We’ll > see if we can’t find a better way, but at present we’re leaning on > compliance and functional soundness. > > Joshua Poore > > > >

Re: [VOTE] Release Apache Flagon (Incubating) v2.0.0

+1 (binding) Checked: * incubator in name * LICENSE/NOTICE files * checksums * ASF headers in files (though a few js files in UserAleWebExtension have the header repeated multiple times - not a big deal but probably worth correcting unless these files are generated that way) Cheers, Paul.

Re: Podlings, the Incubator, relationships and Apache

My +1 to the 2nd camp. For me it's about transparency. I don't see an issue if a podling release has some significant flaws. For me, the ideal would be if it is easy for podling members, reviewers, and downstream users to easily determine whether such flaws are known and what they are. It can be

Re: Podling releases and release policy

Perhaps one approach is to maintain a list of "release issues" which are deemed "minor offences". As long as there are bugs raised against such "release issues", then no further permission would be required. Anything outside the "minor offences" would require explicit permission. As others have

Re: [VOTE] Release Apache Zipkin (incubating) version 2.14.0

I'd second Geertjan's comments about how helpful (even though it probably seemed painful at the time) Justin's comments were for Apache Groovy during our incubation. Perhaps it is worth re-reading some of the reasons why The ASF values highly the provenance behind all of the software in its

Re: [VOTE] Recommend 'Apache NetBeans graduation to Top Level Project' resolution to board

+1 (binding) Cheers, Paul. On Tue, Apr 9, 2019 at 8:41 PM Geertjan Wielenga wrote: > Hi all, > > The Apache NetBeans podling community brings the resolution, after > discussion[1], to become a top level Apache project up for the IPMC vote. > The PPMC community vote[2] resulted in 64 +1 votes

Re: [VOTE] Recommend 'Apache SkyWalking graduation to Top Level Project' resolution to board

+1 binding Regards, Paul. On Tue, Mar 19, 2019 at 3:21 PM Mick Semb Wever wrote: > > > After the latest discussion amongst this dev community on this dev mailing > list[1], presenting Sheng Wu as the PMC Chair and the maturity model[2], > and then the discussion again on the incubator

Re: [VOTE] Accept DataSketches into the Apache Incubator

+1 (binding) On Sat, Mar 16, 2019 at 4:30 PM Liang Chen wrote: > Hi > > +1(binding) > > Regards > Liang > > > Kenneth Knowles wrote > > Hi all, > > > > We've discussed the proposal for the DataSketches project in [1] and [2]. > > The > > proposal itself has been put on the wiki [3]. > > > >

Re: [VOTE] Accept Training into the Apache Incubator

+1 On Wed, Feb 13, 2019 at 5:58 PM Lars Francke wrote: > Hi everyone, > > we've discussed the proposal for the Training project in [1] and [2]. The > proposal itself can be found on the wiki[3]. > > According to the Incubator rules[4] I'd like to call a vote to accept the > new "Training"

Re: the case of the maven wrapper

For anyone who is interested from the Gradle side of things, you can look at what we do for the Groovy project. We do include the (Gradle) wrapper files in our git repo but NOT in our source distribution zip. There is one extra step in our build process/line in our README that explains how to

Re: [VOTE] Shut down unused/inactive incubator lists

+1 On Mon, Jan 21, 2019 at 10:12 AM sebb wrote: > The following lists are all but inactive: > > announce@ Last post Jan 2008 > android-interest@ Last post Mar 2011 > dev@ - only general circulars > jaxws-tck@ (private) Last post 2012 > projects@ Last post Jul 2011 > user@ - only general

Re: [DISCUSS] Mandatory relocation of Apache git repositories on git-wip-us.apache.org

+1 On Tue, Dec 11, 2018 at 6:56 AM Roy Lenferink wrote: > Hi all, > > The Apache Incubator is still having a repository on git-wip-us as well > [1]. > > Does anyone have a problem with moving over the incubator repository to > gitbox voluntarily? > This means integrated access and easy PRs

Re: [VOTE] Retire ODF Toolkit

+1 On Sat, Nov 17, 2018 at 5:54 AM Dave Fisher wrote: > The ODF Toolkit community has VOTEd to Retire. > > The thread: > https://lists.apache.org/thread.html/6de81dc33cb8311a38e38b927bfa1df7290c47ba7e7b39311cd06ce6@%3Codf-dev.incubator.apache.org%3E > > The results: >

Re: [PROPOSAL] Changing requirements for IPMC

+1 to both from me too! On Sun, Nov 11, 2018 at 12:22 PM Roman Shaposhnik wrote: > On Wed, Nov 7, 2018 at 1:28 AM Bertrand Delacretaz > wrote: > > > > Hi, > > > > On Tue, Nov 6, 2018 at 9:20 AM Justin Mclean > wrote: > > > ...I propose this: > > > > > > If someone has done several of the

Re: How to review so-called "binary releases"?

I also agree that moving to a different URL would be disruptive. In Apache Groovy, we have a separate directory for the official (source) release as distinct from the convenience binaries which are in a separate directory. I think we copied the approach from Apache Ant. Our release notes stress

Re: Binary file inclusion (was [VOTE] Apache Toree (incubating) 0.1.0-rc4 as 0.1.0)

Just FYI, Groovy had numerous such "test" jars and wrapper files and such initially. It turned out to only be a couple of hours work to remove them and build them on the fly within the build files. While I certainly see both sides of the argument about whether some "binary-like" artifacts might be

Re: [DISCUSS] Significance of Artifact Names

+1 from me too. For Groovy, we had a discussion internally and with our mentors. The src archive and website disclaimer seemed to be the things that were cared about from a legal point of view and so that is what we renamed. For us, "convenience binaries" were something that should be

Re: [DISCUSS] Proposing Griffin for Apache incubator

Just the name worries me a little bit if the griffon project ever wanted to move to Apache but they don't have any plans to do so at the moment. http://griffon-framework.org Cheers Paul On 29 Nov 2016 9:35 PM, "Henry Saputra" wrote: > Seemed like the discussion is

Re: [VOTE] Graduate Groovy from the Incubator

from the Incubator. The vote passed [3] with 12 > +1s > > total, 5 are binding: > > > > Guillaume Laforge > > Cédric Champeau > > Paul King > > Jochen Theodorou > > Pascal Schumacher > > Emmanuel Lécharny (bind

Re: [graduation] Maturity model-based assessment of Groovy for its graduation

I thought I'd comment from Groovy's point of view, being on the "receiving" end of the audit. I felt that the structure the audit provided to discussions about "Are we there yet?" was very valuable. It didn't feel to me like the audit was imposing any new requirement or policy that I hadn't heard

Re: [VOTE] Release Apache Groovy 2.4.5-incubating

On Mon, Sep 21, 2015 at 6:05 PM, Bertrand Delacretaz wrote: > > > Two files do not have the standard Apache license header, changing > those would make future checks easier: > > ./config/codenarc/codenarc.groovy > ./src/spec/test/PrimitiveTest.groovy > > Fixed (for the

Re: [VOTE] Release Apache Groovy 2.4.5-incubating

On Mon, Sep 21, 2015 at 3:37 PM, Jochen Theodorou wrote: > Am 21.09.2015 01:17, schrieb Justin Mclean: > [...] > >> - The file LineColumnCheck.txt looks like it's source code and is missing >> an header. Is it Apache licensed or generated? >> > > The file provides test data.

Re: [VOTE] Release Apache Groovy 2.4.4-incubating

On 14/07/2015 7:00 AM, Justin Mclean wrote: Hi, We don't bundle the source from any of those libraries true, but we do generate sources as part of our build using ANTLR and we do bundle the class files from the ANLTR and ASM projects in some of our jars and we do bundle the jars from some

  1   2   >