jhs commented on issue #53: bring follow library under Nano's wing URL: https://github.com/apache/couchdb-nano/pull/53#issuecomment-318181786 Hi, Joan and Glynn. I authored Follow and I am already a CouchDB committer. Does that help smooth the process? On Tue, Jul 18, 2017 at 11:56 AM, Joan Touzet <[email protected]> wrote: > @glynnbird <https://github.com/glynnbird> FYI, any new code to be brought > under an ASF repository (and thus ownership) directly must go through the > code clearance process as outlined here: > > https://incubator.apache.org/guides/ip_clearance.html > > It's not just a matter of "they licensed it AL v2.0 so we can just bring > it into our repo." That may be true of dependencies (we can depend on > compatibly licensed code with no extra paperwork) but it's not true when > that code is going to live in our repositories. > > Now, that said, if Cloudant people have "maintained out" most of the > original developers' changes, i.e. "git blame" doesn't show their > contributions as still being in place, then we can waive that process under > the outstanding Cloudant CCLA + jhs's outstanding ICLA. You'll need to do > the legwork here to ensure that is the case. > > - Joan with her "PMC hat" on. > > ? > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <https://github.com/apache/couchdb-nano/pull/53#issuecomment-316110105>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AABEp6CPgN8faNSXMjcT2zfpl7bIDJIiks5sPNWPgaJpZM4ObOSt> > . > ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
With regards, Apache Git Services
