So the process is at [1]. I think the following needs to happen:
- James, can you create a PR with the current state of the driver, but targeted against the `flight-sql-jdbc` branch [2]? Please make sure to update files to have the Apache license preamble. We'll use this as the subject of the clearance process - All contributors need to file an individual CLA; also, if necessary for Dremio, a Corporate CLA (I'll check for the individual CLAs soon, and make a checklist on the PR) - I will fill out the outline form linked above (and validate licenses of dependencies, etc) - We can hold the Arrow vote for acceptance - We submit a grant [3]. I believe James & co. do this (this is step 3/4 in [1]) - is this correct, @Kou? (Since you recently handled Julia.) And then we commit a tarball in the incubator drop area (though, I don't quite see how to do this, need to dig around) - We complete the form and hold the IP clearance vote - Finally we can merge the PR into the branch, and target future PRs against that branch. (Development can continue in the meantime, since I see that it's now proceeding on the current GitHub PR, but I think we just need a stable target to merge for the IP clearance) [1]: https://incubator.apache.org/ip-clearance/ip-clearance-template.html [2]: https://github.com/apache/arrow/tree/flight-sql-jdbc [3]: https://www.apache.org/licenses/contributor-agreements.html On Wed, Mar 30, 2022, at 16:37, James Duong wrote: > Following up on today's sync-up: > > We're looking to start IP clearance of the JDBC driver in > https://github.com/apache/arrow/pull/12254 > > I believe we discussed merging the PR into a branch to start the process. > What else is involved in this process? > > -- > > *James Duong* > Lead Software Developer > Bit Quill Technologies Inc. > Direct: +1.604.562.6082 | jam...@bitquilltech.com > https://www.bitquilltech.com > > This email message is for the sole use of the intended recipient(s) and may > contain confidential and privileged information. Any unauthorized review, > use, disclosure, or distribution is prohibited. If you are not the > intended recipient, please contact the sender by reply email and destroy > all copies of the original message. Thank you.
