Skip to content
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

Research and write a privacy policy/opt-in document #1

Open
arokem opened this issue Jul 11, 2015 · 7 comments
Open

Research and write a privacy policy/opt-in document #1

arokem opened this issue Jul 11, 2015 · 7 comments
Assignees
Labels

Comments

@arokem
Copy link
Collaborator

arokem commented Jul 11, 2015

Possible avenues to look:

@arokem arokem changed the title Research and write a privacy policy/opt-in document Policy: research and write a privacy policy/opt-in document Jul 11, 2015
@arokem arokem changed the title Policy: research and write a privacy policy/opt-in document Research and write a privacy policy/opt-in document Jul 11, 2015
@arokem arokem added the policy label Jul 11, 2015
@arokem arokem assigned arokem and unassigned scopatz Jul 11, 2015
@arokem
Copy link
Collaborator Author

arokem commented Jul 11, 2015

What would we be asking from (end) users ?

@arokem
Copy link
Collaborator Author

arokem commented Jul 11, 2015

@jackiekazil

@arokem
Copy link
Collaborator Author

arokem commented Jul 11, 2015

@scopatz

Carreau pushed a commit to Carreau/sempervirens that referenced this issue Jul 12, 2015
@njsmith
Copy link
Owner

njsmith commented Jul 15, 2015

@scopatz wrote a draft of this on the sprint etherpad, which I guess should get moved somewhere else.

@takluyver
Copy link
Collaborator

Do you think we need an end-user info document between the one-sentence question and the privacy policy? I was assuming the privacy policy was going to be fairly legalistic, but so far that looks quite readable.

@scopatz
Copy link
Collaborator

scopatz commented Jul 15, 2015

Documents don't need to be legal jargon to be legally binding. Besides, what we are trying to do here is fairly simple, so it doesn't need a lot of fancy language. I'll open a PR. I am assuming that we don't have NF standing yet....

@njsmith
Copy link
Owner

njsmith commented Jul 15, 2015

We'll probably need to get a lawyer to look it over to be sure, but yeah,
that will have to wait until after NF agrees to take this on (assuming they
do!). Writing an email to them about that now, and IIUC their next board
meeting is this Mon.
.
To answer @takluyver's question, I think we'll also want some sort of
end-user-friendly document (a FAQ?) that explains the project more
generally (what data's being collected, examples of how it will let us do
awesome stuff, how the collection works, etc.)?

On Wed, Jul 15, 2015 at 5:22 PM, Anthony Scopatz [email protected]
wrote:

Documents don't need to be legal jargon to be legally binding. Besides,
what we are trying to do here is fairly simple, so it doesn't need a lot of
fancy language. I'll open a PR. I am assuming that we don't have NF
standing yet....


Reply to this email directly or view it on GitHub
#1 (comment).

Nathaniel J. Smith -- http://vorpus.org

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants