Antoine Pitrou <[email protected]> writes: > For the record, I don't think I've ever received any postal mail from > the ASF. > > So if you were to make a mistake in your postal address, it would > probably remain unnoticed. >
Trust me, faking an address was the first thing the Indian within me thought of. I disagree on the *principle* of mandating an address. As a maintainer, I think it's beyond my limits to request contributors to disclose their address, or to suggest that they fake one. -- bp > Regards > > Antoine. > > > Le 13/05/2026 à 03:47, Benjamin Philip a écrit : >> Hi, >> >> I requested all the contributors to sign the CLA. Two of them (José >> Valim and Paulo Valente) declined to sign it because they were not >> comfortable disclosing their address. Apart from this, they have no >> objections to signing the CLA. Since they only made trivial changes, both >> of them suggested removing their Co-author trailers from the git >> history. Would this be acceptable? >> >> Alternatively, would an ICLA with address field left blank be accepted >> by the ASF secretary? I don't see why a postal address is necessary to >> sign a CLA. >> >> -- bp >> >> Benjamin Philip <[email protected]> writes: >> >>> Sutou Kouhei <[email protected]> writes: >>> >>>> Hi, >>>> >>>>> 1. In the Project info section of the IP clearance, whom do I put as the >>>>> officer >>>>> managing the donation? >>>> >>>> Could you use me ("Sutou Kouhei") like >>>> https://incubator.apache.org/ip-clearance/arrow-julia-library2.html >>>> ? >>>> >>>>> 2. In the Copyright section of the IP clearance, it mentions that the >>>>> new ASF copyright must be reflected. I've not yet changed the >>>>> copyright. Do I update the copyright before or after the grant? >>>> >>>> Before. >>>> >>>> Also, >>>>> do I have to add the license header to all files to update the >>>>> copyright? >>>> >>>> Yes. >>>> >>> >>> I've put you as the managing officer, and updated the copyright in both >>> the repository, as well as in the IP clearance. >>> >>>>> 3. In the LICENSOR section of the Software Grant, I'm not sure if Title >>>>> refers to my honorific (Mr.) or my designation (Student). >>>> >>>> Hmm. I'm not sure... I think that Software Grant isn't >>>> needed if you use Individual CLA: >>>> >>>> https://incubator.apache.org/ip-clearance/ip-clearance-template.html >>>> >>>>> Either an Individual CLA or Corporate CLA is preferred to >>>>> a Software Grant. >>>> >>>> I think that I used only Individual CLA when I donated the >>>> Ruby bindings...: https://github.com/apache/arrow/pull/1990 >>>> >>> >>> I'll drop the Software Grant then. Should I send the completed ICLA to >>> the ASF Secretary or should it be submitted along with the IP Clearance >>> by you? >>> >>>> >>>> Could you also check contributions from others? It seems >>>> that there are some contributors: >>>> >>>> $ git shortlog -sn --group=author --group=trailer:co-authored-by | cat >>>> 54 Benjamin Philip >>>> 2 José Valim >>>> 1 Matthew Pope >>>> 1 Paulo Valente >>>> 1 Tristan Sloughter >>>> >>>> If there are contributors who contributed some non trivial >>>> changes, they also need to sign Individual CLA. >>>> >>> >>> José Valim, Tristan Sloughter and Paulo Valente only contributed trivial >>> changes (LOC in the single digits) when they reviewed some PRs. Matthew >>> Pope contributed some minor changes in a PR, but in the final committed >>> version almost all of his changes were overwritten by mine. However, >>> because I squash and commit, git does over-attribute how many lines >>> they've (Co-)authored: >>> >>> $ git ls-files | xargs -n1 git blame --line-porcelain | grep -oE >>> "^[0-9a-f]{40}" \ >>> | xargs -n1 git show -s --format="%an >>> %n%(trailers:key=Co-authored-by,valueonly,separator='%n')" \ >>> | sed '/^$/d' | sed 's/<[^>]*>//g' | sort -f | uniq -ic | sort -nr >>> >>> >>> >>> 7344 Benjamin Philip >>> 498 José Valim >>> 481 Tristan Sloughter >>> 235 Paulo Valente >>> 90 Matthew Pope >>> >>> The real numbers can probably be found by looking through the various >>> GitHub PRs. >>> >>> Do you still think individual CLAs are necessary? I can probably get >>> them, but it may take a few weeks. Also, the IP Clearance only mentions >>> "active committers", and I'm the only committer. >>> >>> -- bp >>> >>> <?xml version="1.0" encoding="UTF-8"?> >>> <document> >>> <properties> >>> <title>Apache Arrow Erlang Library Codebase Intellectual Property (IP) >>> Clearance Status</title> >>> </properties> >>> <body> >>> <section >>> id="arrow-erlang+Codebase+Intellectual+Property+%28IP%29+Clearance+Status"> >>> <title>Apache Arrow Erlang Codebase Intellectual Property (IP) >>> Clearance Status</title> >>> </section> >>> <section id="Description"> >>> <title>Description</title> >>> <p>Apache Arrow Erlang is an implementatition of the Apache Arrow >>> project >>> for the Erlang programming language and other BEAM languages.</p> >>> </section> >>> <section id="Project+info"> >>> <title>Project info</title> >>> <ul> >>> <li>Which PMC will be responsible for the code</li> >>> >>> The Apache Arrow PMC will be responsible. >>> </ul> >>> <ul> >>> <li>Into which existing project/module</li> >>> >>> Into the Apache Arrow project, but as a new repository. >>> </ul> >>> <ul> >>> <li>Officer or member managing donation:</li> >>> >>> Sutou Kouhei (Apache Arrow PMC Member) >>> </ul> >>> <p> >>> <em>Completed tasks are shown by the completion date >>> (YYYY-MM-dd).</em> >>> </p> >>> <section id="Identify+the+codebase"> >>> <title>Identify the codebase</title> >>> <table> >>> <tr> >>> <th>date</th> >>> <th>item</th> >>> </tr> >>> <tr> >>> <td>2026-04-28</td> >>> <td>Trademark and Google Search found no use of name as >>> software product.</td> >>> </tr> >>> </table> >>> <p> >>> Origin: https://github.com/Benjamin-Philip/arrow-erlang as at commit ID >>> 926bad3e4d9acfd7ec230dbde2a42bfa4f5edeee. >>> </p> >>> <section id="Copyright"> >>> <title>Copyright</title> >>> <table> >>> <tr> >>> <th>date</th> >>> <th>item</th> >>> </tr> >>> <tr> >>> <td>....-..-..</td> >>> <td>Check and make sure that the papers that transfer rights >>> to >>> the ASF been received. It is only necessary to transfer >>> rights for the package, the core code, and any new code >>> produced by the project.</td> >>> </tr> >>> <tr> >>> <td>2026-05-06</td> >>> <td>Check and make sure that the files that have been donated >>> have been updated to reflect the new ASF copyright.</td> >>> </tr> >>> </table> >>> <p> >>> Identify name recorded for software grant: <em>the name of the grant as >>> recorded >>> in the foundation/officers area, in either grants.txt or cclas.txt, so that >>> the >>> grant can be easily identified. If recorded in the grants.txt document, use >>> the >>> "for" or title. If recorded in the cclas.txt document, use the company name >>> (field 2 without submitter name) and the "form on file" name (field 4, >>> without >>> any people's names).</em> >>> </p> >>> </section> >>> <section id="Verify+distribution+rights"> >>> <title>Verify distribution rights</title> >>> <p> >>> Corporations and individuals holding existing distribution rights: >>> </p> >>> <ul> >>> <li> >>> <em>For individuals, use the name as recorded on the committers page</em> >>> </li> >>> </ul> >>> <table> >>> <tr> >>> <th>date</th> >>> <th>item</th> >>> </tr> >>> <tr> >>> <td>....-..-..</td> >>> <td>Check that all active committers have a signed CLA on >>> record.</td> >>> </tr> >>> <tr> >>> <td>2026-04-28</td> >>> <td>Remind active committers that they are responsible for >>> ensuring that a Corporate CLA is recorded if such is >>> required to authorize their contributions under their >>> individual CLA.</td> >>> </tr> >>> <tr> >>> <td>2026-04-28</td> >>> <td>Check and make sure that for all items included with the >>> distribution that is not under the Apache license, we >>> have >>> the right to combine with Apache-licensed code and >>> redistribute.</td> >>> </tr> >>> <tr> >>> <td>2026-04-28</td> >>> <td>Check and make sure that all items depended upon by the >>> project is covered by one or more of the following >>> approved >>> licenses: Apache, BSD, Artistic, MIT/X, MIT/W3C, MPL >>> 1.1, or >>> something with essentially the same terms.</td> >>> </tr> >>> </table> >>> <p>Generally, the result of checking off these items will be a >>> Software Grant, CLA, and Corporate CLA for ASF licensed code, >>> which must have no dependencies upon items whose licenses that >>> are incompatible with the Apache License.</p> >>> </section> >>> </section> >>> <section >>> id="Organizational+acceptance+of+responsibility+for+the+project"> >>> <title>Organizational acceptance of responsibility for the project >>> </title> >>> <p> >>> Related VOTEs: >>> </p> >>> <ul> >>> <li><em>The VOTE thread accepting the donation may happen either >>> before or after IP clearance. Adoption by lazy concensus is acceptable but >>> not recommended.</em></li> >>> </ul> >>> </section> >>> </section> >>> </body> >>> </document> >>> >>>> FYI: Here is the log for this process of Apache Arrow Julia: >>>> https://github.com/apache/arrow-julia/issues/265 >>>> >>>> >>>> Thanks, >>>> -- >>>> kou >>>> >>>> In <CAMEXYWcWx_AXoK=oZK4r42Xwg6_oQ4wTuuokNfp73=pco0s...@mail.gmail.com> >>>> "[DISCUSS][Erlang] Arrow Erlang's Grant Documents" on Tue, 28 Apr 2026 >>>> 06:37:03 -0700, >>>> Benjamin Philip <[email protected]> wrote: >>>> >>>>> Hi all, >>>>> >>>>> I've finally filled the IP Clearance template, the Individual >>>>> Contributor License Agreement and the Software Grant template following >>>>> our previous discussion (though I'm yet to send these files to anyone). >>>>> However, there are a few fields which I am unsure about: >>>>> >>>>> 1. In the Project info section of the IP clearance, whom do I put as the >>>>> officer >>>>> managing the donation? >>>>> >>>>> 2. In the Copyright section of the IP clearance, it mentions that the >>>>> new ASF copyright must be reflected. I've not yet changed the >>>>> copyright. Do I update the copyright before or after the grant? Also, >>>>> do I have to add the license header to all files to update the >>>>> copyright? >>>>> >>>>> 3. In the LICENSOR section of the Software Grant, I'm not sure if Title >>>>> refers to my honorific (Mr.) or my designation (Student). >>>>> >>>>> Please have a look at the documents I've attached. If they look good, >>>>> I'll send icla.pdf and software-grant.pdf as well their signatures >>>>> icla.pdf.asc and software-grant.pdf.asc to [email protected]. >>>>> >>>>> What are the next steps after this? >>>>> >>>>> -- bp
