Re: [IP CLEARANCE] Arrow Flight SQL JDBC Driver
> > Isn't developing on a fork of the project and submitting a PR considered "developed inside the project”? > Sure, but then you usually don’t need a software grant. Ah, but I do. When submitting a PR to an ASF project (e.g., [1]) I have had to either submit an ICLA (which I have) or check a box in my PR that explicitly states that my contribution is AL2.0 licensed which is effectively a "grant" of permission, which you acknowledge: > Why you may not claim it it exists. But the ASF doesn’t mind that as long as we have permission to use it under the Apache license and distribute it. More to the point of this conversation, I included the project's license headers in my contribution, rather than including my own headers and waiting for the maintainers to review my ICLA. > > The only difference here is that there were multiple contributors to that fork, and it is likely that some or all of them did so during working hours or using equipment by a company, which normally claims IP in such conditions; thus the explicit donation/grant. > Right and that is usually sorted out by those people getting permission from their employers and signing ICLAs. Some employers may require CCLAs. Neither you nor I know the internal Open Source contribution requirements of Dremio corporation, nor should we need to do so. We simply need to evaluate whether Dremio, and the individuals involved, have granted ASF sufficient rights. IMO the IP clearance status document [2] makes that clear, with appropriate due diligence to verify its contents. > All I was saying that having ASF headers make checking IP difficult. In this case, "checking IP" is no more difficult than "checking IP" in any pull request, hundreds/thousands of which occur on ASF projects each year, and none of which require a separate license header before the PR is reviewed, and all of which include the project's standard headers. All I am trying to do is point out that the contribution was coordinated with the PMC before it even started (with company representation on the PMC), with the apparent intention of donation throughout, with the majority of changes in already ASF-licensed files and the project's standard header added to any new files. This does not look like a product developed separately and eventually donated; this looks like an intentional open source contribution before a single line of code was written, and a nice paper-trail to back it up. I certainly support due diligence to confirm an ICLA from each contributor and a CCLA from the company which likely paid these developers for their work. I don't think headers matter much here. [1] - https://github.com/apache/maven-compiler-plugin/pull/95/files [2] - https://incubator.apache.org/ip-clearance/arrow-flight-sql-jdbc-driver.html - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache DevLake (Incubating) v0.11.0-rc2
On Mon, 4 Jul 2022 at 17:27, Liang Zhang wrote: > > Hello all, > > This is a call for vote to release Apache DevLake (Incubating) v0.11.0-rc2 > > The Apache DevLake community has voted on and approved a proposal to release > Apache DevLake (Incubating) version v0.11.0-rc1 > > We now kindly request the Incubator PMC members review and vote on this > incubator release. > > Linkis community vote thread: > https://lists.apache.org/thread/8bnm8v1zvc97rxtd5yfsx53p27wjwtyh > > Vote result thread: > https://lists.apache.org/thread/0n0t1mdcs2qkx6w2qlydojj4ptwp0h35 > > The release candidates: > https://dist.apache.org/repos/dist/dev/incubator/devlake/0.11.0-incubating-rc2/ > > Git tag for the release: > https://github.com/apache/incubator-devlake/tree/v0.11.0-rc2 > > Keys to verify the Release Candidate: > https://dist.apache.org/repos/dist/dev/incubator/devlake/KEYS Sorry, but this is not suitable as the KEYS link. The dist/dev tree is ephemeral, and is not what is used by the download page. Please ONLY use https://downloads.apache.org/incubator/devlake/KEYS Also, keys should only be maintained under https://dist.apache.org/repos/dist/release/incubator/devlake/KEYS which is the source of downloads.a.o > > The vote will be open for at least 72 hours or until necessary number of > votes are reached. > > Please vote accordingly: > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove with the reason > > Thanks, > Apache DevLake(Incubating) community > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [ALL] links to KEYS file in VOTE threads and download pages
Please note, this still applies, but several podlings don't seem to have got the message. Thanks! On Mon, 22 Nov 2021 at 11:03, sebb wrote: > > It is vital that the KEYS file is only referred to using a URL of the form > > https://downloads.apache.org/incubator//KEYS [1] > > This applies to VOTE emails as well as download pages. > > Why is this? > > KEYS files must remain available long for as long as a release is > still available from the ASF archives. > > It is also important for the files used in a VOTE to correspond as far > as possible with the ones that will be used by downloaders. > (Obviously, that is not possible for the artifacts themselves as they > cannot be published until after the vote). Furthermore, it is > important that the KEYS file remain available after the vote has > completed, in case there is a need to check any aspects of the vote. > > == > > If your podling uses a template to create the vote email, please check > that it uses the correct URL for the KEYS file, and fix it if not. > Also check any developer docs to ensure the correct URL is used. > > Note: for a podling's first release, it is possible that the relevant > directory under https://dist.apache.org/repos/dist/release/incubator/ > has yet to be created. This will need to be created, and the KEYS file > populated, *before* the vote can begin. [It will be needed anyway once > the vote succeeds] > > Thanks, > Sebb > [1] Some older pages may use > https://www.apache.org/dist/incubator//KEYS > This now redirects to https://downloads.apache.org/incubator//KEYS - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [IP CLEARANCE] Arrow Flight SQL JDBC Driver
Hello, Sorry for some of the confusion here, I'll try to explain. (Apologies if this does not get linked back up correctly to the thread - Pony Mail does not let me login and the mailto: link generates a URL which is too long). I did preemptively ask the contributors to add the Apache license boilerplate before final submission, so apologies for the confusion there. The original files as I recall either had the header or did not have any header. There was a short discussion on the Arrow dev@ list at [1] where we decided to go through the IP clearance process to make sure everything was clear, since when the PR was first submitted, it had been developed for a long time outside the community (with commits dating back to 2020, although the PR was submitted in 2022). I believe Abner submitted an ICLA. I will re-confirm with the authors (I can't appear to view this information myself on the Apache side). [1]: https://lists.apache.org/thread/xytqttpov1d3q9mhd6nrlz7xkl7q5zjp Hopefully this helps, David
Re: [IP CLEARANCE] Arrow Flight SQL JDBC Driver
Thanks for the clarity, David. Given the clear "commit trail" for individual committers and the ICLAs I don't see a problem there. I think the only question that may need a bit more clarity is the relationship of Dremio to the contributions. I know my own employer has boilerplate legal claims on any open source work I do using company equipment or during "working hours" but there is also a process to allow/approve contributions. Can you elaborate on any corporate relationship to the contributions and if there is a process for open source contributions, particularly if the contributors used corporate computers or labor, and whether this is addressed in the CCLA? On 7/17/22, 8:15 PM, "David Li" wrote: Hello, Sorry for some of the confusion here, I'll try to explain. (Apologies if this does not get linked back up correctly to the thread - Pony Mail does not let me login and the mailto: link generates a URL which is too long). I did preemptively ask the contributors to add the Apache license boilerplate before final submission, so apologies for the confusion there. The original files as I recall either had the header or did not have any header. There was a short discussion on the Arrow dev@ list at [1] where we decided to go through the IP clearance process to make sure everything was clear, since when the PR was first submitted, it had been developed for a long time outside the community (with commits dating back to 2020, although the PR was submitted in 2022). I believe Abner submitted an ICLA. I will re-confirm with the authors (I can't appear to view this information myself on the Apache side). [1]: https://lists.apache.org/thread/xytqttpov1d3q9mhd6nrlz7xkl7q5zjp Hopefully this helps, David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
