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 th

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 copyrig

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 und

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 ha

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 no

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 there's

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 include

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 m

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 num

[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, e-mai

[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 meeting

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 Trainin

[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 https://dist.apache.org/repos/di

[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 th

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 > contributor

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: - incubati

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% su

Re: [IP CLEARANCE] Apache Maven - Mvndaemon

Hi, > Can we replace the header with the following one instead: > > https://github.com/openjdk/jdk/blob/master/src/java.base/share/native/include/jni.h > > > It is more clearly GPLv2 w/ CPE, so it should be al

[MENTORS] September podling reports due

Hi, Sorry for the delay in posting this, please take a couple of days past these dates to submit. Timeline for September Wed September 01 -- Podling reports due by end of day Sun September 05 -- Shepherd reviews due by end of day Sun September 05 -- Summary due by end of day Tue

Re: [IP CLEARANCE] Apache Maven - Mvndaemon

Hi, While some of that conversation may apply here, and I don’t think there is any issues, please note the conversation is in a slightly different context to a software grant. When contributing to an ASF project it is clear under what terms you are contributing. When contributing to a 3rd party

Re: [IP CLEARANCE] Apache Maven - Mvndaemon

Hi, > Is there any rule written somewhere? Because frankly "significant" > contribution is very subjective…. You’ll note [1] says "All contributors of ideas, code, or documentation to any Apache projects must complete, sign, and submit via email an Individual Contributor License Agreement(ICLA

Re: [IP CLEARANCE] Apache Maven - Mvndaemon

Hi, > looking at this https://github.com/mvndaemon/mvnd/graphs/contributors > except the 2 main > contributors we can't really qualify other contributions as really > significant in terms of code size :) You might want to look at each co

Re: [IP CLEARANCE] Apache Maven - Mvndaemon

Hi, > ?? You mean we need CLAs for every person who contributed a Pull Request to > an Apache License project? No we don’t, but it’s best to have them from everyone who has made a significant contribution. > we need to address the native part. Not sure how ATM You probably need to work this ou

Re: [IP CLEARANCE] Apache Maven - Mvndaemon

Hi, I have a couple of questions: I see we have ICLAs for the two main contributors, do we have ICLAs for any for the the other contributors? The repro includes GPL licensed code how is this going to be handled? (GPL is category X and not compatible with the Apache license). There also seems to

Re: [IP CLEARANCE] Apache AsterixDB - JDBC Driver

Hi, > Please help me understand why > - the software grant from Couchbase and > - the acceptance from the AsterixDB project > are not sufficient to approve this donation. Because IMO the information provided doesn’t give sufficient detail to determine who has contributed to the codebase, the his

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

Hi, > Thanks for the explanation. Do you think it's a blocking issue for > incubator release? No I don’t, other IPMC members however might have a different view. > Or it's not a blocking issue, then I will fix it before the next release. That wold be best I think. Thanks, Justin --

Re: [IP CLEARANCE] Apache AsterixDB - JDBC Driver

Hi, -1 on this until my previous questions on this donation are answered (included again below): Do we have a list of those developers and have they signed an ICLAs or do you have a software grant from Couchbase for this code base? Checking the IP of the donated code is difficult to do if all

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

Hi, I would recommend not doing this and in particular not not adding organisation as could be taken as misrepresenting who owns the project. People must act as individuals in the interest of the project when working on a project and not the company they are working for. Kind Regards, Justin

Re: [IP CLEARANCE] Apache AsterixDB - JDBC Driver

Hi, > This code was originally developed by multiple developers at Couchbase using > the Apache License. No other license headers were removed. Do a) we have a list of those developers and have they signed an ICLAs or do you have a software grant from Couchbase for this code base? > The reposi

Re: [IP CLEARANCE] Apache AsterixDB - JDBC Driver

Hi, A few questions: - Where was this code original developed and who worked on it? There is only a couple of commits in that repro, so it doesn’t seem to have been developed there. - Why does the code have ASF headers on it before being donated? Were any 3rd party headers removed? - Have all c

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

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

Re: [VOTE] Release Apache YuniKorn (Incubating) 0.11.0 (RC2)

Hi, > I have a question. > I did not see the two files `NOTICE` and `DISCLAIMER` in the > [1],[2],[3],[4] repo of incubator-yunikorn. It would be good if they are there, but what matters is if they end up in the release artefacts. Thanks, Justin -

Re: [VOTE] Release Apache YuniKorn (Incubating) 0.11.0 (RC2)

HI, +1 (binding) I checked: - incubating in name - signatures and hashes are good - LICENSE and NOTICE file - no unexpected binary files - all source files have ASF headers - can compile from source Kind Regards, Justin - To un

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

Hi, Is this case the author / copyright owner is probably MATLAB / Math Works as that is where the code was copied from. Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional comm

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

Hi, > With respect to your comments on the `erfinv` header file [1], the file > references [2] as its source which is licensed under the new BSD license here > [3]. Just because someone release a bundle of source under a license doesn’t change the of license terms of 3rd party code included in

Re: [VOTE] Release Apache EventMesh (incubating) 1.2.0 rc1

Hi, +1 (binding) I voted +1 on the dev list and checked all of the usual things I check. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.

Re: [VOTE] Release Apache EventMesh (incubating) 1.2.0 rc1

Hi, It might be a good idea to mention how many IPMC member votes you already have. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.

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

Hi, > no my point is that you should cancel RC4 and create a new vote based on the > same RC4 tag but with updated artifacts. I would call it RC5 to avoid any confusion. Kind Regards, Justin - To unsubscribe, e-mail: general

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

Hi, > Re LGPL issue it is in the DISCLAIMER-WIP (in the tag). With that WIP disclaimer the LGPL issue is fine. Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-m

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

Hi, -1 (binding) as package is missing DISCLAIMER, LICENSE and NOTICE. I can also see that chardet is still a LGPL Category X dependancy. I checked: - incubating in name - disclaimer is missing - no LICENSE or NOTICE file - no binary files - all source files have ASF headers - can compile/instal

Re: [VOTE]: Release Apache DataLab (incubating) 2.5.0

Hi, +1 (binding) I checked: - incubating in name - signature and hashes are fine - DISCLAIMER exists - LICENSE and NTOICE are good - All source files have ASF headers - No unexpected binary fils - Can compile from source You might want to check the license of this file [1] as the contents may no

Re: [VOTE] Release Apache ShenYu (incubating) 2.4.0 [ROUND 2]

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

Re: [VOTE] Release Apache ShenYu (incubating) 2.4.0 [ROUND 2]

Hi, It’s recommend that (P)PMC members write down what they check when voting, but you will see some variation from project to project on this and some TLP don’t do this at all. It also recommended that you encourage your mentors to vote and get mentor votes on your releases, but it’s not a req

Re: [VOTE] Release Apache Hop (incubating) 0.99-rc4

HI, > In the client zip we have a THIRD-PARTY.txt which should list all > dependencies and their licenses [1]. A dependancy list is different to what needs to go in LICENSE, only what is included in the release needs to listed in LICENSE. Kind Regards, Justin ---

Re: [VOTE] Release Apache Hop (incubating) 0.99-rc4

Hi, +1 (binding) but LICENSE needs to be updated and there’s a few piece of 3rd party code who licenses need to be clarified. Please fix these before ether next release. I checked: - incubating in name - signatures and hashes are fine - There is a 3rd party file here [1] that is not mentioned i

[MENTORS] Report timeline for August

Hi, First off apologies for not sorting out the reports last month, as a result of this projects that were expected to report last month will need to report this month. DataLab, InLong and YuniKorn’s reports from last month have been copied over to this month, you can leave them as they are if

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

Hi, > I didn’t see the issues with NOTICE, the wrong header on the file or the > unexpected binary files on your dev list but may have missed it. Sorry ignore that, wrong release. Justin - To unsubscribe, e-mail: general-unsubs

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

Hi, > Agreed, these were called out in our dev@ vote I didn’t see the issues with NOTICE, the wrong header on the file or the unexpected binary files on your dev list but may have missed it. Kind Regards, Justin - To unsubscrib

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

Hi, +1 but only due to work in progress disclaimer. There are serval minor issues that need to be fixed. I checked: - incubating in name - signatures and hashes good - disclaimer exists - license is missing information on a file [6] - NOTICE is not correct. As mentioned on a previous release [1]

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

Hi, +1 (binding) but only because of WIP disclaimer. Normally I would vote -1 due to compiled code in the source release [1] I checked: - incubating in name - signatures and hashes exist - disclaimer exists - LICENSE is missing [2][3] - contains unexpected binary file [1] - A large number of sou

Re: [VOTE] Release Apache YuniKorn (Incubating) 0.11.0

Hi, > the ./web component is in the release but I don't see its dependencies > (even as MIT licensed) listed? Dependancies don’t need to be mentioned in the LICENSE file if they don’t end up in the source release. Kind Regards, Justin

Re: [VOTE] Release Apache YuniKorn (Incubating) 0.11.0

Hi, > The base settings are code generated. The software that generates these base > setting is angular. It shows up as a MIT license [1]. > The file content after the generation is part of the created project which > then gets customised. You might want to double check that. A quick glance th

Re: [VOTE] Release Apache YuniKorn (Incubating) 0.11.0

Hi, > [3] is a settings file. The comments should have been cleaned up when the > settings were customised. Presumably the file (and it comments) are copyright to someone and under some license? Do you know who/what that is? Thanks, Justin

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

Hi, > This file contains some very simple test cases, we assume that they are not > from another project, but just added a wrong license header. We are trying > to contact the contributor who contribute this file to make things clear. > Before he/she respond, we'd like to remove this file to avoid

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

Hi, Look like I hit send too soon there: "Sorry but it -1 binding form me. LICENSE is missing 3rd party license information” Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional comma

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

Hi, -1 (binding) for header and licensing issues There also seems to be an issue with the directories dlpack, dmlc, mshadow ands nnvm under the include directory in the tar file? I checked: - incubating in name - DISCLAIMER exists - LICENSE has issues - NOTICE seems OK - A lot of files have h

Re: [VOTE] Release Apache YuniKorn (Incubating) 0.11.0

Hi, -1 (binding) as there files missing headers and a possible license issue. If the licenses of these files are clarified my vote can change. I checked: - incubating in name - signatures and hashes are fine - DISCLAIMER exists - LICENSE may be OK, except this file? [3] - NOTICE is fine - No un

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

HI, Sorry but it -1 binding form me. LICENSE is missing 3rd I checked: - incubating in name - DISCLAIMER exists - LICENSE is missing some licenses - NOTICE is OK - No unexpected binary files - source files have ASF headers This file [1] has an incorrect header and may be from another project. W

Re: [VOTE] Apache StreamPipes 0.68.0 (incubating) RC1 release

Hi, +1 (binding) I checked: - incubating in name - signatures and hashes are fine - DISCLIAMER exits - LICENSE and NOTICW are good - No unexpected binary files - All source files have ASF headers - Can compile I did notice there is a NOTICE in streampipes-wrapper-python that has an incorrect ye

Re: [VOTE] Release Apache InLong 0.9.0-incubating RC1

Hi, +1 (binding) I checked - incubating in name - signatures and hashes are fine - DISCLAIMER WIP exists and notes possible category X issue - LICENSE and NOTICE look fine. It would be possible to cut NOTICE back a bit as there some duplication and possible some information that is not applicabl

Re: Podling reports for July?

Hi, > I have not seen any mention of the podling reports for July on the mailing > lists. The wiki does not have deadlines set. > I created report for YuniKorn. Is there something I missed? No you haven't missed something, I forgot to send the notifications out this month. I’d like to say it wa

Re: IP clearance officer for accepting Terraform

Hi, Assume we have enough information abut the provanance and they are from the same person/company I think one form is OK, but it may be easier to manage with two forms. Thanks, Justin - To unsubscribe, e-mail: general-unsubs

Re: [IP CLEARANCE] Apache Arrow - experimental arrow donation

Hi, There are several contribtors listed in the repo, that are not mentioned in the IP clearance, have they also given permission for their code to be donated in the way? Kind Regards, Justin - To unsubscribe, e-mail: general-u

Re: [IP CLEARANCE] Apache Arrow - experimental parquet donation

HI, I notice there a 3rd contributor in that repo that not mentioned in the IP clearance. Have they given permission for their code to be donated? Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apac

Re: IP clearance officer for accepting Terraform

Hi, > However, if you compare the changes in above commits against the > repositories being donated the "vendor" directory does not exist now > in both the repositories being donated: > https://github.com/xanzy/go-cloudstack > https://github.com/xanzy/terraform-provider-cloudstack (for example > v

Re: IP clearance officer for accepting Terraform

Hi, > 3. On concern of IP on 3rd party codebase committed by authors - the > codebase/changes are in the vendor directory which is where most of > the (3rd party) code additions/deletions are seen. Is this code clearly marked as 3rd party code and has the correct 3rd party headers? I don’t see

Re: [VOTE] Release Apache EventMesh incubating 1.2.0

Hi, -1 (binding) There is still a jar in the source release [3], this was pointed out on your dev list [2], so I’m not sure why this wasn’t fixed, before bring the vote here. If the artefact was changed you need to cancel the vote and start a new vote on your dev list. Thanks, Justin 1. http

Re: [VOTE] Release Apache EventMesh incubating 1.2.0

HI, I assume the artefacts to vote on are these? https://dist.apache.org/repos/dist/dev/incubator/eventmesh/1.2.0/ Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail

Re: IP Clearance for Apache Druid Helm Chart

Hi there, The PMC needs to collect of the needed documents and information and ask the IPMC for an IP clearance. The process is described here [1] Thanks, Justin 1. http://incubator.apache.org/ip-clearance/ - To unsubscribe, e

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

Hi, > The action item on the Apache Pinot team was to inform the Presto foundation > to fix their website references to Apache Pinot to state the full project > name. This has since been addressed. How has this been addressed? I don’t see any changes to that page. Thanks, Justin --

Re: [VOTE] Graduate Apache Pinot as TLP

+1 all the best with the rest of your journey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org

Re: IP clearance officer for accepting Terraform

Hi, > I've been following this thread and continue to see phrases such as "major > contributors" and "significant contributions”. That may be a bit nebulous depending on the exact contributions involved, but I would expect any one making total commits of 100s, 1,000s or more lines of code majo

Re: IP clearance officer for accepting Terraform

Hi, > Alright, I'll create a Github issue as suggested in the example to track IP > clearance with list of all people and will try to reach out to all > contributors within a limited time period and see if they can agree over > the other legal thread and submit their ICLAs. While having an ICLA i

Re: IP clearance officer for accepting Terraform

Hi, Thanks for the clarifications and history it useful to know all of this. > I started, maintained and build most of both these code bases. And as far as > I know I'm (still) legally both the author and the owner of the IP as the > company I work for (for the last 12 years) has a chapter in t

Re: IP clearance officer for accepting Terraform

Hi, Thanks for the information and history there, that was quite helpful. > My understanding is the plugin was originally started as a repo or work by > Sander > (https://github.com/xanzy/terraform-provider-cloudstack/commits/master?after=5e7ccfea50810303a6b205084fb6f0b3eade33ca+314&branch=mast

Re: IP clearance officer for accepting Terraform

HI, > Justin why do we need Hashicorp? They are not involved or are the owner of > the codebase/repos. My understanding was the work was carried out in their repo and that they are probably the IP owner of the codebase. Is that correct? Also, currently [1] redirects to [2], I can see they host

Re: IP clearance officer for accepting Terraform

Hi, As far as I know this is the situation. If anyone has any information to add please do so. - We have no CCLA or grant from Hashicorp, who probably own the IP. It would be nice to have clarity on who actually does own the IP. - We have one ICLA from a major contributor who has also filled in

Re: IP clearance officer for accepting Terraform

Hi, Please stop mixing public and private lists. Feel free to forward any email to the relevant private list but don’t mix them as it's very easy for something that should only appear on a private list to become public. > The codebases are under Sander's control who also was the original/main

Re: IP clearance officer for accepting Terraform

HI, > The license didn’t change for the other repo. It has always been Apache > License, Version 2. Not sure if that matters? The license for that repo I mentioned has changed in the last couple of days, it was originally Mozilla Public License Version 2.0. [1] Yes this matters as the Mozilla

Re: IP clearance officer for accepting Terraform

Hi, > 3. Paul to update and commit the IP clearance: > https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/cloudstack-terraform.xml > and send an email to general@incubator (/cc to > priv...@cloudstack.apache.org) prefixed [IP CLEARANCE] asking for clearance > to be

Re: IP clearance officer for accepting Terraform

HI, Again I request that you please don’t mix private and public channels. IMO More than just a SGA is needed here, there are several major contributors that AFAIK they have not been contacted and there are unanswered questions about this IP clearance/donation. Originally only one repo was disc

Re: [VOTE] Release Apache Pegasus (Incubating) 2.2.0-RC0

Hi, I’m not talking about the web site repo I’m talking about the code for the Pegasus Java client [1] that is linked to from the front page. This particular issue is probably not a backer for this release but it would IMO be something that may stop the project from graduating. Thanks, Justin

Re: [VOTE] Release Apache Pegasus (Incubating) 2.2.0-RC0

Hi, Looking at the people involved there seems to be some overlap. Why is this being developed outside of the ASF? Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands,

Re: [VOTE] Release Apache Pegasus (Incubating) 2.2.0-RC0

Hi, >> The hover text on the star icon still references https:// htts:// >> github.com/XiaoMi/pegasus, consider also changing it? >> > > Does the start icon matter? I thought only the releases matter. Yes it matters, you are linking to a non ASF product from the front page of an ASF site. [1]

Re: IP clearance officer for accepting Terraform

Hi, > Justin - yes all top 5 major contributors have agreed for it per > https://github.com/svanharmelen/terraform-provider-cloudstack/graphs/contributors. Looking at who has contributed the project I think it needs a little more than those five and I’m not 100% sure who those five are. Have you

Re: IP clearance officer for accepting Terraform

Hi, > As the next step, I was advised by ASF legal and others in the list to > follow the IP clearance process for accepting the codebase. I've already > been in touch with Sander who currently has got the repository transferred > by Hashicorp (https://github.com/svanharmelen/terraform-provider-cl

Re: [VOTE] Release Apache Hop (incubating) 0.99-rc3

Hi, This release has less changes than I expected. I thought the issue discussed in the last release involve 100 or 1000’s of files? Just checking - have all the files from that un-donated repo been removed? Thanks, Justin - To

Re: [VOTE] Release Apache Pegasus (Incubating) 2.2.0-RC0

Hi, +1 but only because of WIP disclaimer Only IPMC votes are binding on releases, projects often like to get 3+ PPMC votes on their releases on their dev list first, but you still need 3 IPMC +1 votes (and more +1s than -1s) to make a release. I’m also concerned about linking to a non ASF rel

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

Hi, +1 (binding) It’s fine that the JSON files are missing ASF headers I checked: - incubating in name - signature and hashes are fine - DISCLAIMER exists - LICENSE and NOTICE are good - no unexpected binary files - all source files have ASF headers - didn’t compile from source Thanks, Justin -

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

Hi, One other thing you might want to correct, all of the download links to previous version are broken on your download page. [1] The previous version are automatically archived and can be found here. [2] You may also want to consider not calling the convenience binary an “offical binary relea

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