-
Notifications
You must be signed in to change notification settings - Fork 252
Please sign the Go CLA #85
Comments
@abustany @henrikedwards @jbowtie indicated they signed at https://codereview.appspot.com/58500043/ |
I've already signed. Francisco Souza franciscossouza@gmail.com Please let me know if I need to sign again using another email. |
@fsouza Just making sure everyone signed. Once is enough :-). Thanks. |
I came here from go_nuts. # Get a list of authors ordered by number of commits
# and remove the commit count column
AUTHORS=$(git --no-pager shortlog -nse | cut -f 2- | sort -f)
if [ -z "$AUTHORS" ] ; then
echo "Authors list was empty"
exit 1
fi
# Display the authors list and write it to the file
echo "$AUTHORS" | tee "$(git rev-parse --show-toplevel)/AUTHORS.TXT" |
I signed the CLA. |
Hi, I have signed the CLA (@tsg / Tudor Golubenco). |
@snoe @Pursuit92 for some reason the commits didn't link to your profiles on GitHub, but I found you now. |
Guessing @robfig Robert Figueiredo already signed, based on the AUTHORS file for Go. |
Signed. Email is jcjoshuachase@gmail.com. I've abandoned the techpursuit.net domain. |
@arnehormann Thanks for the tip. You reminded me that we have a similar thing for our AUTHORS file, which I just updated. Thanks everyone. Just a few people left. |
I have signed the CLA. Case Nelson case.nelson@gmail.com I've abandoned the teammating domain. |
@jbowtie Do you mind sharing the email address you used to sign the CLA? Thanks. |
It was either jbowtie@gmail.com or jbowtie@amathaine.com - not in a position to check right now. Sent from Molto for iPad From: Nathan Youngman @jbowtie Do you mind sharing the email address you used to sign the CLA? Thanks. — |
I will sign. I just have to get to work first. On my way, though!— On Fri, Jan 31, 2014 at 8:53 AM, John C Barstow notifications@github.com
|
BTW, just realized my name is typed wrongly. It's Kelvin Foo |
I have now signed the CLA. Den 31/01/2014 kl. 08.55 skrev Christoffer Buchholz christoffer.buchholz@gmail.com:
|
@jbowtie Thanks. Listing both is fine. Just trying to make it easy for @bradfitz to confirm all these CLA signatures. Even just your name may have been enough. @bronze1man Even though your change was small (running gofmt d78b306), I think it will be simpler if everyone who made a commit has signed the Go CLA. @debrando The same goes for your README change (e26bdc2), even if the README probably won't be copied across to Thanks everyone! |
...any hint on how quickly signing it? I'll like to contribute more in future, but burocratic issues really kills me. :/ |
I've added those first 10 to the Go CONTRIBUTORS and AUTHORS files. @debrando, I don't see your CLA submission in our records. |
@debrando You can read and sign the CLA online. It should only take a few minutes. See the Copyright section at http://golang.org/doc/contribute.html. Thanks @bradfitz. Once this is done and https://codereview.appspot.com/58500043 can be applied to go.exp/fsnotify, I'd like to encourage everyone to report issues at https://code.google.com/p/go/issues/list?q=fsnotify and move all development there. #84 |
I sign the CLA right now. |
Should I do some stuff ,or just say I sign CLA here? |
@bronze1man, thanks. I've processed it. |
Ok, at last I got it! An explicit link to "http://code.google.com/legal/individual-cla-v1.0.html" could have helped silly busy people like me! :) |
Thanks @debrando. |
I've submitted @debrando's CLA to the Go repo. All done now, or do we have more? |
That's everyone. Thanks @bradfitz. |
As part of the transition to
os/fsnotify
everyone who has committed to fsnotify should be sure to sign the contributor license agreement for Go.See the copyright section of http://golang.org/doc/contribute.html
After you sign the CLA or if you've signed in the past, please leave a note (also please mention your name and email if it's not in this list). Thanks!
The following people indicated that they signed (recently):
The following had previously signed the CLA:
Still waiting on the following people:
The text was updated successfully, but these errors were encountered: