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

Legal Complexities, Open Source Code #62

Open
plantarum opened this issue Dec 4, 2017 · 2 comments
Open

Legal Complexities, Open Source Code #62

plantarum opened this issue Dec 4, 2017 · 2 comments

Comments

@plantarum
Copy link
Contributor

This is not a risk, this is a requirement. Our legal staff need to understand OSS licenses. That's their job, just as it's their job to understand plant breeder's rights, or patent law, or anything else. We shouldn't be presenting this as if it were categorically different from issues that lawyers are expected to deal with.

@mgifford
Copy link
Contributor

Having a clear public statement from Justice would make sense to me. Not sure who government legal staff generally defer to. It needs to be something that is easy to get to via Google & that is easy enough to understand that you don't need to be a lawyer to do so.

@Acasovan
Copy link
Contributor

I've reached out to colleagues at DOJ to discuss this issue. This will get added to the comms section. Having spoken with several other colleagues, the issue related to using open tools (not just software) goes beyond our legal team, but they are a great groups to start with. A couple of years ago, we did an Open Gov 101 with the legals team leads for each department, we can organize the same type of thing!

That said, we need to focus on finishing the paper (with the help of legal) before we can communicate! So this will come, just can't promise that it will be the next step.

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

No branches or pull requests

3 participants