Thank you for working to make this happen David -- I don't know how much feedback you get from the community about JDBC/ODBC drivers for Arrow Flight SQL but I am excited, and I have encountered many other people who are similarly excited.
I predict these technologies will be widely used and adopted. Thanks again, Andrew On Fri, Jul 29, 2022 at 8:56 AM David Li <lidav...@apache.org> wrote: > The vote/form are now done [1]. (There were a few points of clarification > required.) > > Up next: I will merge the PR into the branch, then merge master into the > branch. After that we can open a final mega PR for review/merge into master. > > [1]: https://lists.apache.org/thread/fjd4942rlccpcjj0cpz0obcpjqhwobtq > > On Tue, Jul 12, 2022, at 12:13, James Duong wrote: > > Hi David, > > > > The Software Grant has been filled and sent to secret...@apache.org. > > > > Thanks for helping to move this along. > > > > On Tue, Jun 28, 2022 at 1:17 PM David Li <lidav...@apache.org> wrote: > > > >> It appears everyone has submitted an individual CLA. > >> > >> I have committed the outline of the IP clearance form. [1] I think we > can > >> kick off the vote, too. > >> > >> As per the form, please remember to ensure that a Corporate CLA is > >> recorded if such is required to authorize their contributions under > their > >> individual CLA. > >> > >> James, can you get the Software Grant filled? [2] > >> > >> [1]: > >> > https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/arrow-flight-sql-jdbc-driver.xml > >> [2]: https://www.apache.org/licenses/contributor-agreements.html#grants > >> > >> -David > >> > >> On Thu, Apr 7, 2022, at 17:21, David Li wrote: > >> > Thanks James. > >> > > >> > For the CLAs: for Ballista at least it was deemed OK [1][2] since all > >> > remaining contributions were easily replaceable and the project was > >> > always clearly Apache licensed. Likely that applies here too. We can > >> > look over things and I can go find out who we can reach out to to > >> > confirm. > >> > > >> > Also the list of people may include too many people, since (at least > >> > spot checking) one person has only one commit and it appears to be a > >> > long-superseded Flight SQL commit, so it's possible we could prune the > >> > history > >> > > >> > [1]: > https://incubator.apache.org/ip-clearance/arrow-rust-ballista.html > >> > [2]: https://lists.apache.org/thread/khk8b06t5wrsg2xmprcqglb7dl76x20r > >> > > >> > On Thu, Apr 7, 2022, at 17:02, James Duong wrote: > >> >> I have started a PR for merging to the new branch here: > >> >> https://github.com/apache/arrow/pull/12830 > >> >> > >> >> Regarding individual CLAs, are these necessary for people that are no > >> >> longer at Dremio? > >> >> > >> >> > >> >> On Mon, Apr 4, 2022 at 11:52 AM Wes McKinney <wesmck...@gmail.com> > >> wrote: > >> >> > >> >>> A corporate CLA is not required. Individual CLAs are fine. > >> >>> > >> >>> Since Dremio is a US corporation and the IP for the JDBC driver is > >> >>> owned by Dremio (I assume that the contributors all have IP > assignment > >> >>> agreements where their contributions are assigned to the > corporation), > >> >>> it would be best to have a Software Grant. Dremio previously > submitted > >> >>> a Software Grant for Gandiva. > >> >>> > >> >>> On Thu, Mar 31, 2022 at 10:05 PM Sutou Kouhei <k...@clear-code.com> > >> wrote: > >> >>> > > >> >>> > Hi, > >> >>> > > >> >>> > > - 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) > >> >>> > > >> >>> > Oh, I didn't do this for Julia. > >> >>> > I also didn't do this when I donated GLib and Ruby: > >> >>> > > >> >>> > * > >> https://incubator.apache.org/ip-clearance/arrow-ruby-library.html > >> >>> > * > >> https://incubator.apache.org/ip-clearance/arrow-parquet-glib.html > >> >>> > * > >> https://incubator.apache.org/ip-clearance/arrow-parquet-ruby.html > >> >>> > > >> >>> > I just collected individual CLAs for Julia and file an > >> >>> > individual CLA for me for GLib and Ruby. > >> >>> > > >> >>> > I also didn't commit a tarball. I just use pull requests in > >> >>> > GitHub or GitHub repository + commit ID. > >> >>> > > >> >>> > > >> >>> > Other items look OK to me. > >> >>> > > >> >>> > > >> >>> > Thanks, > >> >>> > -- > >> >>> > kou > >> >>> > > >> >>> > In <f57ba3ae-3727-4fbf-b622-b82a297ea...@www.fastmail.com> > >> >>> > "Re: [Flight][Java][JDBC] IP clearance of Flight JDBC Driver" on > >> Wed, > >> >>> 30 Mar 2022 17:26:29 -0400, > >> >>> > "David Li" <lidav...@apache.org> wrote: > >> >>> > > >> >>> > > 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. > >> >>> > >> >> > >> >> > >> >> -- > >> >> > >> >> *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. > >> > > > > > > -- > > > > *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. >
