-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow configurable fields per CLA #5
Comments
Not sure if "bug" or "enhancement" but if these aren't legally defensible then it's not a valuable product 😄 |
@jasonm we should record a few datapoints. It looks at though we already collect from GH the uid, nickname, email, and name. I'd add additional fields for mailing address and country as well as a confirmation field that requires them to type their name which should match up with their github name. |
That sounds good. I'm curious what people typically collect electronically. Looks like exactly what you recommend here. Tangentially, I've started a list of existing CLAs we can use as reference: https://github.com/jasonm/clahub/wiki/Existing-CLAs |
One note is that, while we attempt to fetch email via GH API, not all GH users populate this. Hence #18 |
Ideally, it would be up to the project maintainer to add whatever fields they need. As much as I'd love to go back in time and change it around so that only a single button-click is necessary, I don't look forward to haggling with lawyers over this ever again. It'd be best to be able to have the same exact form fields and language as our existing CLA. |
wip on branch jm-agreement-fields: |
This is landed on production now. |
Still need to fix #10 so that existing agreement authors may add these fields to existing agreements. |
With 5991214 these additional fields are now also included in the CSV download: |
What should we record upon signature to make the signature more legally defensible? IP address and time? Should the contributor re-type their name or initials? Anything else?
We shall allow agreement authors to include one or more predefined fields:
Implicit
Default to: include on new CLAs, but allow opt-out
Default to: exclude from new CLAs, but allow opt-in
The text was updated successfully, but these errors were encountered: