Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

Add LEGAL file #338

Closed
jbenet opened this issue Nov 15, 2014 · 3 comments
Closed

Add LEGAL file #338

jbenet opened this issue Nov 15, 2014 · 3 comments
Labels
exp/novice Someone with a little familiarity can pick up topic/docs-ipfs Topic docs-ipfs

Comments

@jbenet
Copy link
Member

jbenet commented Nov 15, 2014

I'll have a file, called LEGAL, that serves as an entrypoint for understanding go-ipfs licensing, this will include a notice about vendored code.
@jbenet jbenet added this to the OSS Hygiene milestone Nov 15, 2014
@jbenet jbenet removed this from the OSS Hygiene milestone Mar 29, 2015
@RichardLitt RichardLitt added exp/novice Someone with a little familiarity can pick up and removed difficulty: easy labels Feb 2, 2016
@whyrusleeping
Copy link
Member

@jbenet this doesnt appear to be done yet. Do we still need to do this?

@jbenet
Copy link
Member Author

jbenet commented Aug 23, 2016

@whyrusleeping i think so, it can refer to LICENSE and the go style PATENTS (when it's added), and address dependencies. This could be moved to github.com/ipfs/community though as it should happen across repos.

@RichardLitt
Copy link
Member

Closing in favor of ipfs/community#139.

# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
exp/novice Someone with a little familiarity can pick up topic/docs-ipfs Topic docs-ipfs
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jbenet @RichardLitt @whyrusleeping