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.

Sign up for GitHub

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

Should we include a copyright statement in the files? #51

Closed
claucece opened this issue Feb 2, 2018 · 1 comment
Closed

Should we include a copyright statement in the files? #51

claucece opened this issue Feb 2, 2018 · 1 comment
Assignees
@olabini
Labels
API question

Comments

@claucece
Copy link
Member

claucece commented Feb 2, 2018

No description provided.

@claucece claucece added the API label Mar 17, 2018
@olabini
Copy link
Contributor

olabini commented Apr 4, 2018

There are a few different parts to this issue. First one is to decide on a license - we have decided on LGPL for the library code, since this matches the previous libotr implementation.

We will have something in all source files. I will work on putting everything in the repo that we need.

@olabini olabini closed this as completed in 4ffecc2 Apr 5, 2018
@deniscostadsc deniscostadsc mentioned this issue Jul 16, 2018
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@olabini olabini

Labels
API question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@olabini @claucece