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

Jump to bottom

Organizational risks in (consuming and) contributing to open source #199

Open

quaid opened this issue Jan 14, 2021 · 1 comment

Assignees

Labels

Avoiding Pitfalls

Projects

Guidebook editorial

Milestone

Collaborator

quaid commented Jan 14, 2021

Patent portfolios, etc.

quaid created this issue from a note in Guidebook editorial (To Assign)

quaid added this to the 2.1 milestone

quaid added the Avoiding Pitfalls label

quaid assigned quaid and dneary

dneary commented Jan 14, 2021

We can focus on the contribution side here - and it's possible that this topic would align closely with the "legal aspects of community" chapter.

The contribution considerations are:

What are best practices around contribution policies for employees?
Should I have a CLA or DCO for my project?
How do open source contributions potentially impact my company's patent portfolio?
What should I do if an employee publishes code without permission?
Can I be sued for copyright or patent infringement for work that other people contribute to a project I work with?

quaid removed their assignment

quaid moved this from To Assign to Assigned in Guidebook editorial

quaid moved this from Assigned to Drafting in Guidebook editorial

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment