Re: [VOTE] Release Apache Flagon UserALE.js (Incubating) 2.1.1

Hi, > For a major or minor release I would. This is a patch release, and would like > start wrangling requisite binding votes to shorten release/voting time. I'm sorry but that the process is you need to vote first on your dev list and then here, not following this process take up IPMC when a v

Re: [VOTE] Release Apache TubeMQ (Incubating) 0.8.0-incubating RC2

Hi, > The reference [2] refers to the three different licenses for the three > different products. There are three links to three different license pages. > > https://www.oracle.com/downloads/licenses/berkeleydb-oslicense.html > https://www.oracle.com/downloads/licenses/berkeleydb-jeoslicense.ht

Re: [VOTE] Release Apache TubeMQ (Incubating) 0.8.0-incubating RC2

Hi, > Berkeley DB uses a Category X non-commercial license, which Justin points out > is not an open source license. > > Berkeley DB Java Edition uses a standard Apache License, v2.0 with an > additional license that appears to be the 3-clause BSD license for an > embedded third-party componen

Re: [VOTE] Release Apache TubeMQ (Incubating) 0.8.0-incubating RC2

Hi, My concern is that while it claims it is under the Apache license that is only for non-commercial use. Having a restriction like that means it’s not really under the Apache license. It states on that page [1] "Our open source license is OSI-certified and permits use of Berkeley DB in open

Re: [VOTE] Release Apache TubeMQ (Incubating) 0.8.0-incubating RC2

Hi, > 1. Can we meet the requirements of this open source agreement by > restricting the version of this component to 7.X.Y? > For Berkeley DB JE (Java Edition), this component itself is TubeMQ to store > metadata and switch between active and standby. It is not very deep, but it > need to take so

Re: [VOTE] Release Apache TubeMQ (Incubating) 0.8.0-incubating RC2

Hi, > We should have discussed this issue [1], and in August 2020, I sent an > email to berkeleydb-info...@oracle.com in accordance with the requirements > of [2] to clarify my question, but it not responded to me. And the LICENSE > of we choosed 7.3.7 berkeleydb, is licensed under Apache V2 lice

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

Hi, -1 (binding) I have not checked dates release but teh vote thread shows only one PPMC (and no mentors) vote. Committer votes are not binding on release votes. I would suggest you continue with the vote on your dev listuntill you have enough PPMC votes and then bright it back here again. Th

[DICUSS] Retire Samoa

Hi, My message to the Samoa asking them to consider retirement got no response [1] so I this think it time to discuss their retirement. Are there any objections to returning the project? Thanks, Justin 1. https://lists.apache.org/thread.html/rb513f7ba5cc5dd1ba9adbf9fe8dbbb52db40066f04a9fed9f

Re: [VOTE] Release Apache Livy 0.7.1 (incubating) based on RC1

Hi, +1 (binding) I checked in the source release: - incubating in name - signatures and hashes correct - NOTICE file is incorrect, please don’t say "Copyright 2018 and onwards” but include current year. - LICENSE is missing license for [1][2] (and other font files) - No unexpected binary files

Re: [VOTE] Release Apache TubeMQ (Incubating) 0.8.0-incubating RC2

Hi, Sorry but -1 (binding) due to not able to compile. Also the berkeleydb license issue has not been resolved and is probably category X. [4] This was mention in a previous release vote thread [4] I checked: - incubating in name - signature and hashes fine - DISCLAIMER exists - LICENSE is miss

Re: [RESULT][VOTE] Release Apache Sedona 1.0.0-incubating rc1

Hi, > Action items to be fixed before the next Sedona release: > 1. Report the source of test files e.g. county_small_wkb.tsv [1] and what > license the contents are under. There are other test files that will also need to be looked into. > 2. Update the Zeppelin plugin LICENSE to "Copyright (c)

Re: [VOTE] Release Apache Sedona 1.0.0-incubating rc1

Hi, +1 (binding) I checked: - incubating in name - DISCLAIMER (WIP) exists - LICENSE is missing mention of some 3rd party software [2] - Is year range right in NOTICE? - No unexpected binary files - source files have ASF headers - can compile from source There are some test files I think I like

Re: [DISCUSS] EventMesh Proposal

Hi, On one hand we don’t have a policy that say you must have to have done a name search before becoming a piddling, on the other changing a name does incur a large community cost and Infra would prefer that podlings don’t change names. Most podlings do the name search just before graduation. I

Re: [DISCUSS] Graduate Apache Ratis as TLP

Hi, > Please let me know if we are good to proceed for voting. So, that I can > start the voting thread. Sounds good to me. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional comman

Re: [VOTE] Release Apache Liminal (incubating) 0.0.1rc4-INCUBATING

Hi, > ▶ shasum -c apache-liminal-0.0.1rc4-INCUBATING-source.tar.gz.sha512 > shasum: apache-liminal-0.0.1rc4-INCUBATING-source.tar.gz.sha512: No such file > or directory > > ⍉ > ▶ shasum -a 512 -c apache-liminal-0.0.1r

Re: [VOTE] Release Apache TubeMQ (Incubating) 0.8.0-incubating RC1

Hi, > 1. If the referenced file source has the original version statement, we > should keep it as it is and cannot replace it with the Apache v2 statement? Correct. > 2. If the referenced file source does not have a version statement, but the > project of the file has a version statement, do w

Re: [VOTE] Release Apache TubeMQ (Incubating) 0.8.0-incubating RC1

Hi, > 1. Is it necessary to remove the description of part B in the above > screenshot? I can’t see teh screen shot so not sure what you are asking here sorry. > 2. If the file source itself does not have a LICENSE authorization statement, > but the top level of the project is Apache V2 or oth

Re: [DISCUSS] EventMesh Proposal

Hi, To help trademarks it would bee best if you provided them with some search results as described here. [1] Have a look at a couple of the other recent polling name search JIRAs to get a good idea of what is needed. Thanks, Justin 1. http://incubator.apache.org/guides/names.html

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

Hi, +1 (binding) but only because of WIP DISCLAIMER. LICENSE is not correct and source release contains Category B licensed bits. I checked: - incubating in name - signatures and hashes are fine - DISCLAIMER (WIP) exist but information has not been updated in it - LICENSE looks OK but I’ve not c

Re: [VOTE] Release Apache TubeMQ (Incubating) 0.8.0-incubating RC1

Hi, > - These files seem to have incorrect headers [1][2][3][4][8][9]. ASF headers > should include a copyright line and 3rd part headers need to be kept > unchanged. Sorry that should be "ASF headers should NOT include a copyright line” Thanks, Justin -

Re: [VOTE] Release Apache TubeMQ (Incubating) 0.8.0-incubating RC1

Hi, -1 (binding) due to license and notice issues and possible inclusion of Category X software It unclear to me if the berkeleydb-je licensing issue has been resolved. I can’t find any discussion of it on your mailing list. Can someone tell me what the outcome of this was? I checked: - incub

Re: [VOTE] Release Apache Liminal (incubating) 0.0.1rc4-INCUBATING

Hi, +1 of the source release, but -1 on the whl file. For the source release I checked: - incubating in name - signatures and hashes are fine - DISCLAIMER (WIP) exists but still has "List of known issues goes here”. You need to mention what issue this release has. - LICENSE is good - NOTICE is O

Re: [VOTE] Release Apache Liminal (incubating) 0.0.1-INCUBATING

Hi, > It is a tar that is created as part of the python setup process. > We will not include it in releases going forward But I assume it is released somewhere and if that is the case it still needs to comply with ASF please and distribution policy. Thanks. Justin --

Re: [Vote] Release Apache Weex (Incubating) 0.29.0-RC1

Hi, -1 (binding) due to files with incorrect headers and/or missing license information. It would also be a good idea to remove “com.taobao.weex”. I only see two +1 votes on the dev list but will assume that the person who put the vote forward also voted +1. I checked: - incubating in name - s

Re: [VOTE] Release Apache Hop (incubating) 0.60-rc1

Hi, It's failing for me at: [INFO] Hop Assemblies Plugins Dist FAILURE [ 33.371 s] When I do an “mvn compile” but it works with a “man package”. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr.

Re: [VOTE] Release Apache Hop (incubating) 0.60-rc1

Hi, +1 (binding) it contains Category B source code but is using the WIP disclaimer and what is contains is clearly stated. I checked: - Incubating in name - DISCLAIMER exists - LICENSE and NOTICE look OK - Source files have correct headers - No unexpected binary files - Unable to compile on

Re: [VOTE] Apache Ratis Thirdparty Incubating Release 0.6.0 rc0

Hi, +1 (binding) but the NOTICE file need updating to include “This product includes software developed at…" I checked: - incubating in names - signatures and hashes are file - LICENSE is fine - NOTICE is a bit too minimal please see [1] - all source files have ASF headers - no unexpected bina

Re: [VOTE] Release Apache Liminal (incubating) 0.0.1-INCUBATING

Hi, > We will fix the issues and create a new release candidate. I’m still little confused why you have two release artefacts, if you can explain that it would be helpful. Thanks, Justin - To unsubscribe, e-mail: general-unsubs

Re: [VOTE] Release Apache Liminal (incubating) 0.0.1-INCUBATING

Hi, -1 (binding) until apache-liminal-0.0.1-INCUBATING.tar.gz vs apache-liminal-0.0.1-INCUBATING-source.tar.gz is cleared up. I checked: - incubating in name - signatures and hashes correct - DISCLAIMER exists however here no need for the ASF header in the DISLAIMER file and where is says "Li

Re: [MENTORS] February 2021 Incubator report timeline

Hi, > I did not see bluemarlin here, do we need to submit the report for Feb? You can if you want to and that might be a good idea given the slow bootstrap/number of missed reports. How it's supposed to work is that new podlings report monthly for three months and then quarterly after that. T

[MENTORS] February 2021 Incubator report timeline

Hi, The February 2021 Incubator report timeline is: Wed February 03 -- Podling reports due by end of day Sun February 07 -- Shepherd reviews due by end of day Sun February 07 -- Summary due by end of day Tue February 09 -- Mentor signoff due by end of day Wed February 10 -- Re

Re: [VOTE] Heron Release 0.20.3-incubating Release Candidate 9

Hi, > This isn’t a release page, only a page to select a specific version of the > documentation. The section that points to GitHub is only a link to the repo. Clicking on the link 0.20.2-incubating in the front pages header take me to that page, while it not directly called a download page it

Re: [VOTE] Heron Release 0.20.3-incubating Release Candidate 9

HI, > My apologies. It was an oversight on my part. I've adjusted the page. > https://heron.incubator.apache.org/versions I also add a very big disclaimer to the section marked "Pre-release versions” clearly indicating that this must be used for development use only. Projects can’t distribut

Re: [VOTE] Heron Release 0.20.3-incubating Release Candidate 9

Hi, > I'll also make sure to address your concerns about the docs that are > published that point users to unreleased code. It's not only the docs it’s also the download page. [1] Thanks, Justin 1. http://heron.incubator.apache.org/versions

Re: [MENTORS] missing reports and signoffs

HI, > The Hop podling report is available and has been signed off by our mentors > [1]. > Let me know if you need anything else from us. All good. My script flagged it as you still have "-XX-XX” in the last release date. Thanks, Justin ---

Re: [IP CLEARANCE] OpenWhisk IDE plugins

Hi, > I couldn't find any jar file in the zip file. > Are you mentioning the gradle-wrapper? Yes that is the jar in question. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional comm

Re: Proposed Resolution: Establish Apache Flagon TLP

Hi, > Only thing I see is that two proposed of the PMC members are not signed up to > the private list: >* Laura Mariano >* Steve York These people are still not signed up to the private list. Thanks, Justin

[MENTORS] missing reports and signoffs

Hi, The report will be submitted on Wednesday. The following reports are missing: BlueMarlin brpc Hop Livy PonyMail Wayang Weex The following still need mentor sign off: Liminal Milagro YuniKorn Thanks, Justin - To unsubscrib

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

Hi, Changing my vote to +1 (binding) Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org

Re: [IP CLEARANCE] OpenWhisk IDE plugins

Hi, I assume the .jar in the zip file is not part of the donation? Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Graduate Apache Gobblin (Incubating) as a TLP

Hi, Thanks for doing that - everything looks OK to me. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Heron Release 0.20.3-incubating Release Candidate 9

HI, +1 (binding) I checked: - incubating in name - signatures and hashes correct - LICENSE and NOTICE good - al source files have ASF headers - no unexpected binary files - I didn’t build as I don’t have the prerequisites installed I’m not sure why the BUILD file is empty. Int would be good to h

[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&focusedCommentId=17258034#comment-17258034 ] Justin Mclean commented on INCUBATOR-253: - LEGAL-516 has been resolve

Re: [DISCUSS] Graduate Apache Gobblin (Incubating) as a TLP

HI, > 4. Regarding docker, per policy [1] I thought unreleased tags are fine (ie. > if its nightly or snapshot), where-as the *latest* tag should point to an > (approved) released code. Seems like my understanding was incorrect, so I > will remove the unreleased tags from there as well. You're co

Re: Link to a page that seems to be missing

Hi, Here is the last version of that page (from 2017): https://web.archive.org/web/20170629200901/http://incubator.apache.org/facilities.html I can see facilities.xml in the old Incubator/content content area but no facilities.ad in the new area. Perhaps it was not converted? I couldn’t find a

Re: [DISCUSS] Graduate Apache Gobblin (Incubating) as a TLP

HI, > 1. 3rd party logos being eaten by pacman on the homepage: We have removed > this animation, and created a ticket to follow-up with Trademarks for > future usage of that animation. There are still trademarks on that page that are not mentioned in the footer disclaimer. You might also have t

Re: NOTICE file for binary release

Hi, Without access to a release it is a little hard to confirm, but it looks reasonable to me. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incub

Re: [VOTE] Release Apache Hop (incubating) 0.50-rc2

HI, Sorry but it’s -1 (binding) as it contains Category B source code and header issues and is not using the WIP disclaimer. [1] I suggest you use the work in progress disclaimer, and in it list the issues that need to be fixed before graduation. Fixing some of teh header issues would make it

Re: [VOTE] Release Apache Hop (incubating) 0.50-rc2

Hi, > Hop plans to fix these issues in a later incubating release. I hope that > exceptions to release policy can be made for these and similar issues in this > early-stage incubating release. If you have used the work in progress DISCLAIMER and listed the potential issues in that file this is

Re: [DISCUSS] Graduate Apache Ratis as TLP

Hi, I notice you use [1]. Are the conversations there being brought back to the mailing list? There doesn’t seem to be a lot of conversation happening on your mailing list other than GitHub traffic, have you considered moving the GitHub traffic off the dev list? I notice the download links on

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

Hi, -1 (binding) due to docker and trademark issues, but happy to change my vote to +1 once those are on teh way to bee corrected. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional

Re: [DISCUSS] Graduate Apache Gobblin (Incubating) as a TLP

Hi, I suggest you run your home page past trademarks. There's a large number of 3rd party logos used without attribution there and I’m not sure how some of those trademark owners would feel about a pacman eating their logos. You also have links on your home page to various commercial entires wi

Issue with clutch2report

Hi, I just had an issue with clutch2report and for some unknown reason it was trying to use a podling that has graduated (TVM). The podlings.xml file is correct as far as I can see and it doesn’t appear in the current clutch report. I put in a work around, but if someone want to try and fix wha

[MENTORS] Podling reporting timeline for January

Hi, Here is the time line for the reports for this month. Wed January 06 Podling reports due by end of day Sun January 10 Shepherd reviews due by end of day Sun January 10 Summary due by end of day Tue January 12 Mentor signoff due by end of day Wed January 13 Report submitted to Board Wed J

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

Hi, > I closed the vote after 72 hours of starting the vote (which was after 72 > hours of discussion time). Are you recommending adding more time to the > vote? 72 hours is just a guideline for release votes not for graduation. Generally you want to get consensus from the entire IPMC and your m

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

Hi, You might want to give the IPMC a little more time to have a look at the project and give some more feedback. It would be unfortunate if an issue was found that prevented the project from graduating. Thanks, Justin - To u

Re: NOTICE file for binary release

Hi, > Last release we had feedback that the NOTICE file for the binary release > needs to show the licenses of the depdendencies distributed alongside the > code. In general the NOTICE file does not do this, license information goes in the LICENSE file. Please see [1] If some of the code in i

Re: [LAZY CONSENSUS] Re: [incubator] branch master updated: Update incubation.ad

Hi, I have no objections to most of the changes. This has changed the DISCLAIMER text, would we require all podlings to update their DISCLAIMERS to match? Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.a

Re: Trying to become incubator project..

Hi, In order to be accepted as an incubating project you need to put together a proposal. The Incubator PMC would also have to agree that the project is a good fit for the ASF. I would suggest you take a look at this [1] and some other incubator proposals [2] (newer ones are at the top). If y

Re: [VOTE] Heron Release 0.20.3-incubating Release Candidate 8

Hi, >> LICENSE is also missing the license for the trykker font and may be missing >> other things. > > Good catch as that file was in the .rat-excludes. This font is Class B and > should not be included. Heron will need to find another Serif Font. > > https://scripts.sil.org/cms/scripts/page.

Re: [VOTE] Heron Release 0.20.3-incubating Release Candidate 8

HI, -1 (binding) due to license and notice issues I checked: - incubating in name - LICENSE has issues (see below) - NOTICE has wrong year - DISCLAIMER exists (not WIP one) - no unexpected binary files - ASF files have ASF headers I’m a little confused by the LICENSE file. First off it uses UR

Re: [VOTE] Apache Gobblin 0.15.0 release RC2

Hi, Might be best to close this one and ask people to vote in the other thread for less confusion. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@i

Re: [VOTE] Apache Gobblin 0.15.0 release RC2

Hi, Is this the same as the other vote thread? Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Apache Gobblin 0.15.0 release RC2

Hi, +1 (binding) I checked: - incubating in name - LICENSE and NOTICE are fine - DISCLAIMER exists - No unexpected binary files in release - All files have ASF headers - I was not able to compile at first but managed to get (see below) This is the error I get when building via ./gradlew build: D

Re: [DISCUSS] Wayang Proposal

Hi, > Right now, there are 3 people signed up as mentors, however knowing that not > always are all mentors available at every given time, it would be cool if we > could find 1-2 more to help out. In no way reflecting on the mentors who have volunteered and I’m sure they will do a good job In

Re: [VOTE] Release Apache NuttX (Incubating) 10.0.0 [RC0]

Hi, +1 (binding) but a lot more needs to be done on the LICENSE and headers I checked: - incubating in name - DISCLAIMER exists - a good start have been made on LICENSE - NOTICE looks fine - No unexpected binary files - More work needs to be done on adding ASF headers I not sure that using key w

Re: [LAZY CONSENSUS] Suitable Name Search Documentation

Hi, I think the issue may be more clarifying and simplifying the original policy language. Perhaps that can be done at the some time? Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional co

Re: svn commit: r1883912 - /incubator/public/trunk/content/shepherd_assignments.json

HI, > Superset and TVM graduated and that’s not reflected in your report > preparation. Sorry I has assumed that the new projects had taken care of that. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.ap

[MENTORS] Report timeline

Hi, The time line is as follows: Wed December 02 Podling reports due by end of day Sun December 06 Shepherd reviews due by end of day Sun December 06 Summary due by end of day Tue December 08 Mentor signoff due by end of day Wed December 09 Report submitted to Board Wed December 16 Board mee

Re: [VOTE] Release Apache Weex (Incubating) 0.29.0-RC1

HI, I also see only 1 +1 vote in the thread in your dev list normally you need 3 +1 votes from PPMC members before bring it t the IPMC to vote on. I suggest you ask your mentors and other PPMC to vote on the dev list and cancel this vote here on the incubator list. Thanks, Justin -

Re: [VOTE] Graduate Apache ECharts as TLP (round 2)

Hi, > The description of [1] is generated from GitHub release, so it will be > updated with our next release, which is expected to happen in a few more days. Good to hear. > The description of [2] is generated from GitHub description. We can update > the GitHub description, adding "Apache EChart

Re: [VOTE] Graduation of Apache DataSketches Project to TLP

Hi, +1 (binding) All the best! Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release the Apache Pegasus 2.1.0

Hi, +1 (binding) but it would be good to see progress on adding all license information / fixing all headers I checked: - incubating in name - DISCLAIMER (WIP) exists - LICENSE is missing some licenses - NOTICE seems OK - Unclear if all ASF source files have ASF headers. It would be best to have

Re: [VOTE] Release Apache ECharts (incubating) 5.0.0 (release candidate 3)

Hi, +1 (binding) I checked: - signatures and hashes are fine - incubating in name - DISCLAIMER exists - LICENSE and NOTICE fine - All source files have ASF headers - No unexpected binary files Thanks, Justin - To unsubscribe,

Re: Where to get feedback on a project before formulating a proposal

Hi, > The idea was first brought up over a year ago by a member of the community, > although it's been me dragging my feet. They are actually an ASF member. Being an ASF member that can be a mentor or the champion. Have you asked them if they would be willing to do that? Thanks, Justin ---

Re: [VOTE] Graduate Apache ECharts as TLP (round 2)

Hi, +0 I think a little more attention needs to given to branding and trademarks e.g. [1][2][3][4] The last ones in particular are concerning as they come from Baidu and there seem to be others as well [8] Thanks, Justin 1. https://www.npmjs.com/package/echarts 2. https://www.jsdelivr.com/

Re: Missing graduation resolutions

Hi, > The Superset graduation resolution was already submitted to the board. In > fact it made the agenda at the last board meeting but was tabled to give > the board more time for due diligence. Let me know if it needs to be > resubmitted or anything. I’ve resubmitted it so it should be fine for

Re: Missing reports from Incubator report

Hi, > There's been some confusion over annotator's reporting schedule. > It seems several team members had a (presumably mistaken?) > recollection of having reported in October. It did report in October, but didn’t get sign off from any of the mentors. Thanks, Justin ---

Missing reports from Incubator report

Hi, I’ve just submitted the board report [1] and we were missing the follow reports: - Annotator - BlueMarlin - Livy - S2Graph - Toree - Warble Thanks, Justin 1. https://whimsy.apache.org/board/agenda/2020-11-18/Incubator

Missing graduation resolutions

Hi, Several projects have discussed graduation but I’m not seeing any proposals submitted. [1] It best to get them in early so board members can review them in time. I think we should have proposals for: - TVM - Superset - Flagon - ECharts? I’ve added Superset. Thanks, Justin 1. https://

Re: [MENTORS] Incubator report timeline for November 2020

Hi, > How can I edit the following page? I am the owner of Blue Marlin project and > would like to submit my report. > > https://cwiki.apache.org/confluence/display/INCUBATOR/November2020 > he permissions for your PPMC had not

Re: Proposed Resolution: Establish Apache Flagon TLP

Hi, Everything looks fine to me. Only thing I see is that two proposed of the PMC members are not signed up to the private list: * Laura Mariano * Steve York And i would be nice to have you logo here [1] Thanks, Justin 1. https://apache.org/logos/?#flagon ---

Re: [VOTE] Apache StreamPipes 0.67.0 (incubating) release

Hi, +1 (binding) This is an easy release to check I checked: - incubating in name - signatures and hashes are fine - LICENS and NOTICE are fine - no binary files - all source files have ASF headers It not immediately clear have you can compile from the instructions included within the release

[MENTORS] Incubator report timeline for November 2020

Hi, Here’s the reporting timeline. Report as usual can be entered on the Wiki [1] Wed November 4th Podling reports due by end of day Sun November 8th Shepherd reviews due by end of day Sun November 8th Summary due by end of day Tue November 10th Mentor signoff due by end of day Wed November 1

Re: [VOTE] Release the Apache Pegasus 2.1.0

Hi, +1 (binding) Both the issues of the missing header and licensing is mentioned in the DISCLAIMER so I think that’s OK, but progress will need to be made on these in the next release. I checked: - incubating in name - signatures and hashes are fine - DISCLAIMER_WIP exists and contains what n

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

HI, > Thanks, Justin. After removing stale issues and adding the statement on GPU > license, assuming we address any other license issue in the next rc, should > we name it as simply DISCLAIMER instead of DISCLAIMER-WIP? When all issue have been resolved then I would name it DISCLAIMER, probab

Podling termination by the IPMC

Hi, As requested by Dave. IMO This is going to happen infrequently and possibly never. I can only think of a couple of occasions when this has been discussed in the last five years. Things generally work out one way or another before this step needs to be taken. The current IPMC policy[1] stat

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

Hi, > Let’s discuss outside the immediate context of MxNet reasons for the IPMC to > suspend a podling. Sure, it would be best to start a seperate thread for that. I think however it would be so infrequent and each situation different that it would be hard to come up with some that would work

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

Hi, > If NVIDIA changes the license then it must be very soon. If so then the issue > is gone. And the issue may not be gone unless the license change is retroactive. Currently the project has maven artefacts in the Apache repo that contain category X code. [1] Thanks, Justin 1. https://issu

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

HI, > Don’t make a noncompliant binary release. The project is (sadly) already doing this [1], they are hoping the licensing issue can be sorted, but its taken more than 5 months and little visible progress on that seems to have been done. NVIDIA is considering changing, but to what we don’t

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

HI, Is there anything from the known issues in [1] that needs to be added? Justin 1. https://issues.apache.org/jira/browse/INCUBATOR-253 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional command

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

Hi, Re the licensed files missing from LICENSE here are some examples[1][2][3][4], but I haven’t done a full check so there are probably more. Thanks, Justin 1. ./3rdparty/onnx-tensorrt/third_party/onnx/third_party/pybind11/tests/test_gil_scoped.cpp 2. ./3rdparty/onnx-tensorrt/third_party/onn

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

Hi, > Thanks for the vote. It looks like we forgot to remove the mentions of the > resolved issues in the DISCLAIMER-WIP. Checking the linked issues, all of > them have been resolved in 1.8. Is this still a blocking issue if the actual > issues that the DISCLAIMER-WIP links to are addressed? T

Re: [VOTE] Graduate Apache Superset (incubating) as a Top Level Project

Hi, The resolution was put on the board agenda, but given it was received less than 24 hours before the board meeting it was decided to postpone it till next month, to give board members time to properly consider the proposal. Thanks, Justin -

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

Hi, -1 (binding) Please see [1] and note which sort of issues need to be fixed before making a new release. While it does include the WIP declaimers, it includes several knows issues that have been outstanding for several releases. It also fails to mention teh issue with Nvidia licensing and i

Re: [VOTE] Graduate Apache Superset (incubating) as a Top Level Project

HI, +1 (binding) Thanks for addressing everything I brought up here and on your private list. There's still a little more to do, but it’s being dealt with, so I’m all good with you graduating. Do keep an eye on how you are handling those synchronous meetings and try to make sure everyone can c

Re: Is there a check list for podling renames?

Hi, > I could not find one; seems to me it would be useful to document > everything that has to be done by the podling and what is done by > Infra. There is not one that I know of. Hopefully they are rare, as they cause a bit of work for Infra. Thanks, Justin -

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

Hi, > I’ve stuck to the basic directions in [2] of sending a “friendly” email (AND > Slack message, in our case), in private, to the community member. That is certainly the best first step with dealing with something like this. Thanks, Justin --

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

Hi, > I hope that everyone is now subscribed after the last round of nagging, but I > still have no way to confirm who’s not on the list. Daniel Gaspar is still not subscribed, but all others have, I don’t see that as a blocker to graduation. > After taking this up with our mentors, we’ve seem

Re: Some instructions are misleading on mentor page

Hi, I agree this could be clearer: "Mentors MUST be on the IPMC. This should be checked prior to beginning incubation. Any prospective Mentors who are not yet on the IPMC should ask to be added (by election). Email the application to priv...@incubator.apache.org.” How about this: "Mentors MUS

<    3   4   5   6   7   8   9   10   11   12   >