Re: [VOTE] Graduate Apache AGE (Incubating) as a Top Level Project

Hi, I’m -1 on this as I think there are still some minor outstanding issues and I think the project needs a little more time to work those out. For instance, I’d like to see a discussion on the committer bar and have that clearly documented on your website. But I’m willing to hear from the

Re: [DISCUSS] Graduate Apache AGE Incubating as a Top Level Project

Hi, >> (1) Three of the PPMC members are not subscribed to the private mailing list. > All the PPMC members should now be subscribed to the private mailing list. This is still not the case. >> (3) No one has been added to the PPMC. > We have just added two new PPMC members However they were

Re: [DISCUSS] Graduate Apache AGE Incubating as a Top Level Project

HI, > The community would like to use Apache Dockerhub. Then as per the Infra comment on that JIRA you should discuss it onlist and make sure you have consensus that the community wants that. Kind Regards, Justin - To

Re: [VOTE] Release Apache InLong 0.12.0-incubating RC0

Hi, +1 (binding) I checked: - incubating in name - signatures and hashes are fine - DISCLAIMER (WIP) exits - LICENSE and NOTICE look good - No unexpected binary files - All ASF files have ASF headers - Can compile from source Kind Regards, Justin

Re: [VOTE] Release Apache EventMesh (incubating) 1.3.0 rc0

Hi, +1 (binding) I checked: - incubating in name - signatures and hashes are fine - DISCLAIMER (WIP) exists - LICENSE and NOTICE need work - All ASF files have ASF headers - No unexpected binary files - Unable to compile but that likely my setup/environment Kind Regards, Justin

Re: [VOTE] Release Apache YuniKorn (Incubating) 0.12.1 (RC1)

Hi, +1 (binding) I checked: - incubating in name - DISCLAIMER exists - LICENSE and NOTICE are fine - No unexpected binary fines in the releases - All files have ASF headers - Can't compile but that’s probably my setup (OSX) I did notice a couple of references to cloudera’s JIRA e.g

Re: [DISCUSS] Graduate Apache AGE Incubating as a Top Level Project

Hi, > - A new PPMC member is not being added in the correct way → Are there any > additional steps that need to be taken to complete this process? A NOTICE needs to be sent before adding any new PPMC/PMC member to the roster. [1] > The docker image is available at >

Re: [DISCUSS] Graduate Apache AGE Incubating as a Top Level Project

Hi, > Could you clarify what would be considered too low of a bar for a committer? There isn’t one. Some projects allow you to be a committer by asking and some will vote you in after a couple of PRs. However each project can decide where this is. > I feel that we need good upper and lower

Re: [Mentors] podling report text

Hi, > Let me know if it correct or needs further updates. Thanks for doing that, much appreciated. Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail:

[MENTORS] Podling reporting timeline - reports due January 05

Hi, Reporting timeline is as follows: Wed January 05 Podling reports due by end of day Sun January 09 Shepherd reviews due by end of day Sun January 09 Summary due by end of day Tue January 11 Mentor signoff due by end of day Wed January 12 Report submitted to Board Wed January 19 Board

[Mentors] podling report text

-by: - [ ] (eventmesh) Francois Papon Comments: - [ ] (eventmesh) Junping Du Comments: - [ ] (eventmesh) Jean-Baptiste Onofré Comments: - [ ] (eventmesh) Justin Mclean Comments: - [ ] (eventmesh) Von Gosling Comments: ### IPMC/Shepherd notes

[jira] [Closed] (INCUBATOR-271) SeaTunnel Incubator project request for the GitHub repositories moving service

[ https://issues.apache.org/jira/browse/INCUBATOR-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean closed INCUBATOR-271. --- Resolution: Won't Fix Moved to INFRA. > SeaTunnel Incubator project requ

[jira] [Assigned] (INCUBATOR-271) SeaTunnel Incubator project request for the GitHub repositories moving service

[ https://issues.apache.org/jira/browse/INCUBATOR-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean reassigned INCUBATOR-271: --- Assignee: Justin Mclean > SeaTunnel Incubator project request for the Git

[jira] [Commented] (INCUBATOR-271) SeaTunnel Incubator project request for the GitHub repositories moving service

[ https://issues.apache.org/jira/browse/INCUBATOR-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464307#comment-17464307 ] Justin Mclean commented on INCUBATOR-271: - You'll need to raise an INFRA JIRA

Re: [DISCUSS] Graduate Apache AGE Incubating as a Top Level Project

Hi, I’m seeing some issues here: - Indications that the committer/PPMC bar may be too high and not all forms of contribution recognised. - A new PPMC member not being added in the correct way - Other than that recent addition no other PPMC members added - May be some concern about employment

Re: [DISCUSS] Graduate Apache AGE Incubating as a Top Level Project

Hi, >> Regarding (3), Dehowe Feng was added to the PPMC on 12/6/2021 [1]. > > Oh I see, but he is a BitNine employee. Add increases the concern that AGE is > not a diverse community. He was also added without sending NOTICE to the IPMC. It seems he was added based only on code commits, I

Re: [DISCUSS] Graduate Apache AGE Incubating as a Top Level Project

Hi, > Personally I thought code contributions were mandatory to be considered as > being added to the PPMC team. I would say not, the responsibilities of being a PPMC member includes a lot of things other than code and being good at just the code part doesn’t alway make you a good PPMC

Re: [DISCUSS] Graduate Apache AGE Incubating as a Top Level Project

Hi, > Because of the nature of the project, committers require a broad range of > expertise in several areas including: Database (Postgres and SQL), Graph > Technology and Cyper, C language. While many contributors demonstrated > expertise in some areas, few had expertise in all disciplines. In

Re: BlueMarlin project appears to be inactive

HI, > We are maintaining 2 opensource repositories for Bluemarlin, one is in > Futurewei account and the other in Apache accounts. This needs to stop, you should only be working on the code at the Apache repo and have no others. Please put in place plans to move development across to the ASF

Re: [IP CLEARANCE] Apache Maven - Mvndaemon

Hi, > AFAIK, Guillaume fixed the issue as described in > https://issues.apache.org/jira/browse/LEGAL-586 > > > Nothing blocks now, isn't it? I’m nt aware of anything. > Do we consider the clearance ok as a conclusion, or should we restart a

[mentors] Missing podling reports

Hi there, These reports are currently overdue: AGE Crail Hivemall Kyuubi Livy Nemo PageSpeed SDAP Spot Toree Training Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional

Re: [VOTE] Release Apache Kyuubi(Incubating) v1.4.0-incubating (RC2)

HI, It would be better to use https://downloads.apache.org/incubator/kyuubi/KEYS I believe. Kind Regards, Justin

Re: [DISCUSS] Incubating Proposal of SeaTunnel

HI, If those people have a genuine desire to help the project and the time to do so that’s fine, but what I've seen happen a couple of times is with that many mentors, mentors think that other mentors will will the work and nothing get done. Kind Regards, Justin

Re: [VOTE] Release Apache Wayang (Incubating) 0.6.0-RC8

HI, > There’s no issue with the file headers, other than it just hard to review as > there is a lot of files without headers. On solution is to perhaps put all > the 3rd party code into a folder called “3rdparty” so it’s clearer what is > ASF code and what is not? Sorry Ignore the above I was

Re: [VOTE] Release Apache Wayang (Incubating) 0.6.0-RC8

Hi, There’s no issue with the file headers, other than it just hard to review as there is a lot of files without headers. On solution is to perhaps put all the 3rd party code into a folder called “3rdparty” so it’s clearer what is ASF code and what is not? Re license information you need to

Re: [VOTE] Release Apache Teaclave TrustZone SDK (incubating) v0.2.0-rc.1 (with the correct KEYS link)

Hi, > Basically, there are two issues in the release tar bar: > 1. We are using a customized Rust's standard library and include > modified sources and other upstream code in our codebase. > 2. We also include code of OP-TEE libraries as our vendored > third-party libraries. > > These two

Re: [VOTE] Apache AGE (incubating) Release 0.6.0

Hi, I know you’ve announced the result on this but I also checked it and would have voted +1 (binding). I found: - incubating in name - signatures and hashes are fine - LICENSE and NOTICE are correct - No unexpected binary files - all files have correct headers - can’t compile from source but

Re: [VOTE] Release Apache Wayang (Incubating) 0.6.0-RC8

Hi, Sorry but it’s -1 (binding) from me. You might want to consider using the work in progress disclaimer. I checked: - incubator in name - signatures and hashes are fine - LICENSE is missing info on [1] and about a dozen other files. License information needs to go in the LICENSE file. [3] -

Re: [VOTE] Release Apache Teaclave TrustZone SDK (incubating) v0.2.0-rc.1 (with the correct KEYS link)

Hi, Sorry but -1 (binding) due to incompatible licenses in source release and those licenses not mentioned. A WIP disclaimer isn’t a blanket exception and you need to note what the issues are and inform the used of what licenses are incompatible. Please see [4] When voting on releases, it’s

Re: [VOTE] Release Apache brpc (Incubating) 1.0.0

H, +1 (binding) I checked: - incubating in name - LICENSE and NOTICE are good - signatures and hashes correct - All ASF files have ASF headers - no unexpected binary files - I didn’t try compiling from source A spot check on LICENSE showed a couple of minor issues wth LCENSE e.g "Copyright

Re: About organization/project logos in the "powered by" or "community" page

Hi, > Also, what's the best practice for this? I saw most projects only put > a list of names/links. Some care need to be taken in doing this from a branding perspective and ASF policy view. In general this MUST NOT be on the home page. From a recent email that was sent out: WHY: the ASF is

Re: [DISCUSS] Incubating Proposal of SeaTunnel

Hi, Generally 3 or 4 mentors are enough. Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org

Re: Report template generation changes

Hi, > Did you recently change the template to add text such as the "Are > things..." and "Are 3rd..." in the following? I think that change was made about 2-3 years ago? > I assume that you intend podlings to remove that text. But one of the > podlings I mentor just left the text, and added

Re: Help reviewing Any23 2.6 Release Candidate

Hi Lewis, > Although Any23 is a top level project for some time we can from time to > time struggle to get enough PMC to VOTE on our release candidates. > This is a plea for any IPMC to review the Any23 2.6 release candidate and > provide your response on the dev@any23 mailing list. I can review

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

Hi, Changing my vote to +1 (binding) > 1. Sorry for the confusion on the download page. I just fixed Sedona's > website. Now the download page is at an obvious place: > https://sedona.apache.org/download/ Thanks for fixing up your download page. Look like

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

Hi, I’m -1 (binding) on this release as the project website doesn’t have an obvious download page and they have made previous releases. This has been brought up on this list before and there was no response from the project. For this release: - incubating in name - signatures and hashes are

Re: [VOTE] Release Apache Wayang (Incubating) 0.6.0-RC6

Hi, Sorry but it -1 (binding) from me due to LICENSE and NOTICE issues and 3rd party code having an ASF header. I checked: - incubating in name - signatures and hashes are fine. - DISCLAIMER exists - NOTICE and LICENSE are not correct. Licenses need to be mentioned in LICENSE. If the code has

Re: [MENTORS] December timeline reports due December 1st

Hi, > DataLab was included in report for November. So, is the report failed? > https://cwiki.apache.org/confluence/display/INCUBATOR/November2021 > > https://whimsy.apache.org/board/minutes/DataLab.html >

Re: [VOTE] Release Apache Pegasus (Incubating) 2.3.0-RC2

Hi, +1 (binding) because of WIP disclaimer I checked: - incubating in name - DISCLAIMER exists (WIP) - signatures and hashes are fine - NOTICE looks OK but given the large number of ALv2 code included I would expect some of them to have NOTICE files - From a quick quick LICENSE is missing some

Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

HI, The NOICE file has this: Apache AGE (incubating) Copyright 2019-2020 Bitnine Co., Ltd. Copyright 2020-2021 The Apache Software Foundation Which I don’t think is really correct. Bitnine Co., Ltd. did have copyright but that gave the ASF a grant right? And that original project wouldn’t have

Re: [MENTORS] 2022 Reports

HI, I can generate ISC files for each podling for each podling if anyone would find that useful? Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail:

Re: [MENTORS] 2022 Reports

HI, I’ve also added ISC calendar files to [1] that may be helpful to people. Kind Regards, Justin 1. https://cwiki.apache.org/confluence/display/INCUBATOR/2022 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org

[MENTORS] 2022 Reports

Hi, I’ve upload draft templates for all incubator reports in 2022. [1] You can see the dates they are due for each month and what podlings are expected to report. This may change a little each month due to non reporting podlings, new podlings, podling graduations and mentor changes and this

Report template generation changes

Hi, I just modified the report generation scripts so that individual podlings template can be generated. This means that if for some reason a podling report is missing that report can be generated and added to the wiki. Although it may be just as easy to copy a previous report. I’ve also

[MENTORS] December timeline reports due December 1st

Hi, Here is the report time line for December, please note the reports are due a little earlier than most months. Wed December 01 Podling reports due by end of day Sun December 05 Shepherd reviews due by end of day Sun December 05 Summary due by end of day Tue December 07 Mentor signoff due by

Re: [MENTORS] Podling reports this month

Hi, > Why is the report without apache shenyu？ ShenYu is in group 1 which reports in January, April, July and October. Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional

Re: [VOTE] Release Apache Wayang (Incubating) 0.6.0-RC5

Hi, The issue has been described in detail multiple times. If you don’t understand please talk to you mentors and they can help. Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For

Re: [VOTE] Release Apache Wayang (Incubating) 0.6.0-RC5

Hi, I’ll also note that Alexander’s vote is non binding, best practice to indicate it as such like so “+1 (non-binding)”. It also a good idea to list what was checked in the release rather than just voting “+1". Only IPMC members votes are binding on ASF incubator releases. Kind Regards,

Re: [VOTE] Release Apache Wayang (Incubating) 0.6.0-RC5

Hi, > Agree with Daniel, the node creation is a common technique in the data > science community and does not represent code, it is representing a procedure > to create nodes. Therefore the use of this procedure seems compliant. IMO it is not compliant with ASF policy, no matter how common

Re: [VOTE] Release Apache Wayang (Incubating) 0.6.0-RC5

Hi, > And sure, the image labeled with B and C is based on the non-labeled image > with smiley faces, so I'll concede that image, and even the exact network it > represents, may fall under CC-BY-SA, and thus it was correct to remove the > old code. This main issue I think as the old code

Re: [VOTE] Release Apache Wayang (Incubating) 0.6.0-RC5

Hi, It unclear what has been used from that page, there is text, code and images on it all under different licenses. In general content on wikipedia is not in the public domain and care needs to be taken with is use, also what “public domain” means varies. For how to treat public domain works

Re: [VOTE] Release Apache Wayang (Incubating) 0.6.0-RC5

Hi, +0 on this. while some issues have been fixed, I'm concerned that taking creative common license code and making modifications to it [1] and removing the comment to where it was originally from doesn’t actually change the original license of that code. I checked: - incubating in name -

Re: Poding Report November 2021 missing?

Hi, > I am Kent from Apache Kyuubi (Incubating). I didn't find a place to > add our monthly Poding report for Nov. 2021 as usual. Can any > incubator PMC create it? Any person in the Incubator PMC can create it and they includes your mentors. you can cadd your report to the usual place now. [1]

Re: [MENTORS] Podling reports this month

Hi, The report can be found in the usual place: https://cwiki.apache.org/confluence/display/INCUBATOR/November2021 Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands,

[MENTORS] Podling reports this month

Hi, Report timeline for November is as follows, sorry for the late notice. Wed November 03 -- Podling reports due by end of day Sun November 07 -- Shepherd reviews due by end of day Sun November 07 -- Summary due by end of day Tue November 09 -- Mentor signoff due by end of day

Re: [MENTORS] Download page issues

Hi, The script i used to check teh download pages is here if anyone is interested. [1] Kind Regards, Justin 1. https://github.com/justinmclean/ReleaseChecker - To unsubscribe, e-mail:

Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

Hi, That sounds like a good strategy to me. Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

Hi, > So, my understanding is that for all of our files that have any PostgreSQL > code (anything from a PostgreSQL source file), modified or not, we need their > license and not the ASF license. For work that doesn't have PostgreSQL code, > we need the ASF license. I think inn general that

Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

Hi, > What is the ASF policy for including parts of external source files such as > in functions? There is no explicit policy. However the header policy states that for code developed at the ASF the ASF header should be used. Treatment of 3rd party works [2] covers code not submitted by the

Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

HI, It also doesn’t follow the terms of the PostgreSQL which states: "Permission to use, copy, modify, and distribute this software and its documentation for any purpose, without fee, and without a written agreement is hereby granted, provided that the above copyright notice and this paragraph

Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

Hi, > Can you please confirm that all files in question, with regards to Postgres, > should have the following header. This one way to deal with it, and is probably better than what is beening currently done, however IMO: - "Licensed to the Apache Software Foundation (ASF) under on or more

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

Hi, > We had filed an issue [1] as well as PR[2] addressing the issue. It will be > reflected in the webpage when the Presto team deploys it (perhaps their > next release cycle). > > [1] Presto Issue > [2] Presto PR

Re: [MENTORS] Download page issues

HI, As per [1] mirrors.cgi and closer.cgi scripts have been deprecated and it states a project's download page "must have at least one link to the current release. This link must use the closer.lua utility." Kind Regards, Justin 1.

Re: [MENTORS] Download page issues

Hi, My understanding is that https://www.apache.org/dist/ has been deprecated. So for Pony Mail I would I change these links to go via https://downloads.apache.org/ - https://www.apache.org/dist/incubator/ponymail/KEYS -

Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

Hi, Please change link to https://dist.apache.org/repos/dist/release/incubator/age/0.5.0.rc0/apache-age-0.5.0-incubating-src.tar.gz.sha512 to go via https://downloads.apache.org/ Please change link to

[MENTORS] Download page issues

Hi, A while back we asked projects to correct their download pages, however I’m still seeing a lot of issues. Project with issues seem to include the following. This this is auto generated so there a possibility it may have picked up some false positives. Age links to KEYS are missing

Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

Hi, Also note that the download link to 0.5 is not correct on your web site. Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail:

Re: [VOTE] Release Apache InLong(Incubating) 0.11.0-incubating Candidate 0

Hi, +1 (binding) I checked: - incubating in nam - signatures and hashes are fine - Good LICENSE and NOTICE - DISCLAIMER (WIP) exists - No unexpected binary files - All ASF source files have correct headers - Can compile from source Kind Regards, Justin

Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

Hi, > Most of our code uses or is inspired by PostgreSQL's code, in some modified > form or another. Additionally, we try to have our code work tightly with > their code in order to reduce replication of code. As a core developer, and > from your input, I wouldn't be comfortable with anything

Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

HI, > "Also you need to think about all of the code that has been copied but > probably has incorrect headers." > > Are you referring to a more general case of code other than PG or Bitnine? > Could you expand a bit on this please. I was referring to code from PostgreSQL. Thanks, Justin

Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

Hi, > Basically, keep the PostgreSQL copyright messages intact in all file headers > that it copy/use from the PostgreSQL I would do this. > and just append Bitnine's copyright message to the header along with the > PostgreSQL's message. I would not do this, this is an ASF project not

Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

Hi, > Postgres has not donated anything to our project. Then it probably should not be mentioned in NOTICE in that way. > We generally don't copy Postgres files over. So, no we haven't replaced their > copyright notice. But you’ve not copied it over either, which is slightly problematic.

Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

Hi, > Could we please get some clarification on the following items - > > "- LICENSE is missing information from [1][2]” Sorry my mistake I do see that both copyright statements are in LICENSE. You can ignore this. > "- NOTICE is incorrect. There should be no need for "This product contains

Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

Hi, > Thank you for your feedback. The issue with hashes and Signatures on the > website for each download is fixed. We created a download page and > added the required information as mentioned before: http://age.apache.org/ > It is under the download then versions page.

Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

Hi, > We need to figure out where these files came from. If they originated from > Bitnine, we should keep their original header and mention them in > NOTICE/LICENSE. If they were part of the original grant then I would change the headers to ASF ones and add teh required text to NOTICE. If

Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

Hi, > I see Bitnine is the company that donated the project AGE to Apache, so the > header change seems to make sense? Perhaps? If that is the case then why is that not mentioned in the NOTICE file? If you remove (with permission) a copyright line for a header as part of a SGA then that

Re: [VOTE] Release Apache Wayang (Incubating) 0.6.0

Hi, > Graphchi: Graphchi has an Apache License. The authors didn't mention the > license in the repository of graphchi-java(it is a wrapper of > Graphchi-cpp). Just because Graphchi-cpp is Apache licensed doesn’t mean graphchi-java is or that people understand that they are contributing code

Re: [VOTE] Release Apache Wayang (Incubating) 0.6.0

Hi, -1 (binding) as this release seems to contain 3rd party code incorrectly labeled as ASF code and contains code of unknown and category X licenses. But it’s not 100% clear in all cases. You might want to consider using the work in progress disclaimer while you fix these things. I checked:

Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

Hi, Sorry but it’s -1 (binding) as there is no download page and the download links on the home page do not have hashes and signatures. This was brought up on this list recently and was asked to be corrected. Also see other issues below. In the release: - incubating in name - signatures and

Re: [VOTE] Release Apache Kyuubi(Incubating) v1.3.1-incubating RC0

Hi, > One further question, as we already have such declarations in our NOTICE > file, > does it mean we can eliminate other declarations if we use code from Apache > TLPs? > >> This product includes software developed at >> The Apache Software Foundation (https://www.apache.org/). Yes you inly

Re: [VOTE] Release Apache ShenYu (incubating) 2.4.1

Hi +1 (binding) I checked: - incubating in name - signatures and hashes are fine - disclaimer exists - notice and license look good - all source files have ASF header - no unexpected binary files - can compile from source I’m not 100% sure but there might be some 3rd party code in the release

Re: [VOTE] Release Apache Kyuubi(Incubating) v1.3.1-incubating RC0

Hi, > It is from Spark NOTICE files. > > Because Kyuubi copies some source code from Apache Spark, then we append > the content of Spark NOTICE into the Kyuubi NOTICE file. That’s fine and one may of dealing with it. but you can also only take the relevant parts from the NOTICE file. If

Re: [VOTE] Release Apache Kyuubi(Incubating) v1.3.1-incubating RC0

Hi, +1 (binding) I checked: - incubating in name - signatures and hashes are fine - Disclaimer exists - LICENSE and NOTICE are fine - All source have ASF headers (could the schema files have them?) - No unexpected binary files - Can compile from source Is the statement "This distribution

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

Hi, I look a look at the project and noticed some thing re the PMC makeup: - Some of your proposed PMC members are existing PPMC member but are not signed up to the project private mailing list - The project has not voted any PPMC members. - Could some of the existing committers be consider PMC

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

Hi, +1 (binding) I checked: - incubating in name - signature and hashes are fine - DISCLAIMER (WIP) exists - LICENSE may be missing some information, there seems to be be data from OpenStreetMap and I’m not 100% sure if this is compatible with the Apache license. [1][2] - NOTICE is fine - A

[MENTORS] Report reminder emails

Hi, Sorry to anyone who may be confused as I accidentally send out the reminders for 2020 instead of 2021. The correct reminders have been sent out, you can ignore the ones for 2020. Kind Regards, Justin - To unsubscribe,

[MENTORS] Podling report timeline for October

Hi, Report timeline is as follows: Wed October 06 Podling reports due by end of day Sun October 10 Shepherd reviews due by end of day Sun October 10 Summary due by end of day Tue October 12 Mentor signoff due by end of day Wed October 13 Report submitted to Board Wed October 20 Board

Re: [MENTORS] Download pages and dist area (BRPC, InLong, Kyuubi, Livy, Nemo and Tuweni)

Hi, > Other podlings with no download pages that I could find: > > Liminal > Marvin (no source download I could find) > PageSpeed > SDAP (no releases?) > Sedona > Training (it does have released items) > Wayang This was mentioned in another thread. Also: Age Annotator BlueMarlin Linkis

[MENTORS] Download pages and dist area (BRPC, InLong, Kyuubi, Livy, Nemo and Tuweni)

Hi, Project dist areas should be up to date with the download page. I wrote a script to check some things, again this may have missed some things or it may be incorrect. I can see the following minor issues for BRPC, InLong, Kyuubi, Livy, Nemo and Tuweni. BRPC

[MENTORS] Download links need to use closer.lua not closer.cgi or mirrors.cgi

Hi, Download links should use https://www.apache.org/dyn/closer.lua not closer.cgi or mirrors.cgi Projects that should check this: Doris EventMesh Heron HiveMall Milagro Pegasus PonyMail Shenyu Spot StreamPipes Teaclave Yunikorn Again this is generated by a script so may not be 100% accurate.

[MENTORS] Download pages and links to KEY files

HI, Some projects that may have an issue with the KEYS file: Brpc Crail Doris hHiveMall Livy Milagro MXNet NuttX PonyMail Spot Teaclave This was autogenerated by a script so may not be 100% correct. KEYS url should go via https://downloads.apache.org/ Kind Regards, Justin

[MENTORS] Download pages and links to podling releases

Hi, Can mentors please make themselves familiar with the requirements for download pages and links [1] as we seem to have a number of projects that are not providing downloads in the required manner. In general: - Please use https://www.apache.org/dyn/closer.lua

Re: [VOTE] Release Apache MXNet (incubating) version 1.9.0.rc7

Hi, Regards the headers, perhaps think of it this way. If you leave the headers on, you are respecting the original copyright holder and their license for that code. The license is compatible with the ASF license so there no issue, you just need to list it in you LICENSE file. If you remove

Re: [ANNOUNCE] Release Apache brpc (incubating) 1.0.0-rc02

Hi, A while back I wrote a script to check podling download links and we attempted to get them all corrected. you need to manual list all of the download pages. Things it doesn’t do: - check if the latest release is there - check if the contents match with what is in /dist Might be time to run

Re: [VOTE] Release Apache MXNet (incubating) version 1.9.0.rc7

HI, > It is stated in the `./LICENSE`[1] file that 3rdparty/ctc_include is > `Apache-2.0 license`, > but the file in ctc_include is `NVIDIA CORPORATION` [2]. > I'm not sure if this will be a problem? That looks like an issue to me. Kind Regards, Justin

Re: [VOTE] Release Apache MXNet (incubating) version 1.9.0.rc7

Hi, > Thanks for helping us check. We will do a full review of the licenses of > files (and hopefully find ways for automation for them too). Automation may help but it is no replacement for human eyes. > These files are adapted from numpy with significant modification from mxnet >

Re: [VOTE] Release Apache MXNet (incubating) version 1.9.0.rc7

Hi, -1 (binding) as issues brought up from the last RC have not been fixed, namely: - These files incorrectly have an ASF header [1][2][3] - This is not mentioned in LICENSE [4][5]. A quick search shows about 20 files with a Microsoft copyright (some are listed below). I also checked: -

Re: [VOTE] Release Apache Kyuubi(Incubating) v1.3.0-incubating RC9

Hi, +1 (binding) I checked: - incubating in name - signatures and hashes are fine - DISCLAIMER exists - LICENSE and NOTICE look OK (but see below) - All source files have ASF headers - No unexpected binary files - May be my setup but I was unable to compile Please don’t use "Copyright 2021 and

Re: [IP CLEARANCE] Apache AsterixDB - JDBC Driver

Hi, Changing my vote to +0. Thanks for your answers. I still have some concerns, and looking at the vote thread / your mailing list, I cannot see any discussion about any potential IP issues. It is not possible from the information provided to determine if the PMC has taken the required steps

Re: [VOTE] Release Apache InLong(Incubating) 0.10.0-incubating RC1

Hi, +1 (binding) I checked: - incubating in name - Disclaimer WIP exists - LICENSE and NOTICE are fine - No unexpected binary files - All ASF files have ASF headers - Can compile from source I did have some difficult compiling this and it failed several times, before working but I’m not 100%

<    1   2   3   4   5   6   7   8   9   10   >