Closed barbeau closed 9 years ago
@kalon33 @vreixo Could you both please sign the new electronic ICLA form, which is now linked to in the Readme: https://github.com/CUTR-at-USF/OpenTripPlanner-for-Android/blob/master/CONTRIBUTING.md#individual-contributor-license-agreement-icla
It only takes around 30 seconds to review and submit your contact info.
@ktran9 @marchica If you could both sign for your past contributions as well, that would be greatly appreciated! :)
@barbeau Done :)
----- Mail original -----
De: "Sean Barbeau" notifications@github.com À: "CUTR-at-USF/OpenTripPlanner-for-Android" OpenTripPlanner-for-Android@noreply.github.com Cc: "Nicolas Derive" kalon33@ubuntu.com Envoyé: Mardi 2 Septembre 2014 21:32:05 Objet: Re: [OpenTripPlanner-for-Android] Add ICLA to readme (#400)
@kalon33 @vreixo Could you both please sign the new electronic ICLA form, which is now linked to in the Readme: https://github.com/CUTR-at-USF/OpenTripPlanner-for-Android/blob/master/CONTRIBUTING.md#individual-contributor-license-agreement-icla
It only takes around 30 seconds to review and submit your contact info.
@ktran9 @marchica If you could both sign for your past contributions as well, that would be greatly appreciated! :)
— Reply to this email directly or view it on GitHub .
Thanks @kalon33!
@barbeau done too!
2014-09-02 22:09 GMT+02:00 Sean Barbeau notifications@github.com:
Thanks @kalon33 https://github.com/kalon33!
— Reply to this email directly or view it on GitHub https://github.com/CUTR-at-USF/OpenTripPlanner-for-Android/issues/400#issuecomment-54209870 .
Thanks @vreixo!
@barbeau Done. Looking good! :)
Thanks @marchica! Hope all is going well for you! :)
Since more people are starting to contribute to the app, we need to have some agreement in place that contributors would fill out electronically (i.e., Individual Contributor License Agreement (ICLA)) that confirms they are contributing code to the project, along with all required IP that goes along with the code. This avoids having to extract code from the project in the future if there is a misunderstanding surrounding the terms upon which the contributor is sending the code.
I'll submit a PR for this shortly.