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

missing copyright statement in select2-bootstrap.css #43

Open
onlyjob opened this issue May 28, 2016 · 7 comments
Open

missing copyright statement in select2-bootstrap.css #43

onlyjob opened this issue May 28, 2016 · 7 comments
Labels

Comments

@onlyjob
Copy link

onlyjob commented May 28, 2016

Please add copyright statement to select2-bootstrap.css.

Thanks.

@fk
Copy link
Member

fk commented Jun 1, 2016

@kevin-brown I guess that explicitly mentioning the license as Select2 itself does in its readme should suffice. If so, could you please check the current select2-bootstrap-theme license and let me know if this is okay like it is or if I should change something?

@fk
Copy link
Member

fk commented Jun 1, 2016

After a second, more thorough read: @onlyjob could you clarify why you need the copyright in select2-bootstrap.css? Not too familiar with the legal things. Would a link to the license (like Select2 itself does) be okay?

@fk fk modified the milestone: 0.1.0-beta.5 Jun 6, 2016
@fk
Copy link
Member

fk commented Jun 6, 2016

I hope this is resolved in v0.1.0-beta.5 with adding the Copyright and License information to the README.

@fk fk closed this as completed Jun 6, 2016
@onlyjob
Copy link
Author

onlyjob commented Jun 6, 2016

why you need the copyright in select2-bootstrap.css

Best practice. This CSS file is often (re-)distributed by other projects. Copyright statement is important to document ownership (i.e. who grants the license).

Do not mistake copyright statement (e.g. Copyright 2015-2016 Florian Kissling <myemail@host.com>) and grant of license.

Would a link to the license (like Select2 itself does) be okay?

No, they are doing it wrong. First of all they call license "MIT" which is ambiguous. FSF recommends calling it "Expat".
Secondly they do not use canonical URL of the license: https://opensource.org/licenses/MIT

Finally text of license is short and it is arguably better to include full text of the license accompanied by copyright statement.

Committed LICENSE file documents copyright and license perfectly. However because CSS file is often bundled with other software I recommend to include copyright statement to CSS file as well.

Thank you.

See more:

@fk fk reopened this Jun 6, 2016
@fk fk modified the milestones: 0.1.0-beta.6, 0.1.0-beta.5 Jun 6, 2016
@fk
Copy link
Member

fk commented Jun 6, 2016

Thanks for the info @onlyjob! Maybe @kevin-brown can chime in and we can fix this for both this and the main Select2 repository?

@kevin-brown
Copy link
Member

This CSS file is often (re-)distributed by other projects. Copyright statement is important to document ownership (i.e. who grants the license).

I'm going to agree that not including a banner in the distributed CSS files was an oversight in the main project which still needs to be fixed. I'm not sure about the need for the copyright statement (though I don't see anything wrong with not including it), as that should ideally be covered in the linked license.

First of all they call license "MIT" which is ambiguous. FSF recommends calling it "Expat".

This ambiguity should be resolved by following the link to the license and verifying the text is accurate and complete. As much as I appreciate the FSF attempting to resolve ambiguity by calling it "Expat", this can be resolved by looking at the license text (which people should be doing anyway).

Secondly they do not use canonical URL of the license: https://opensource.org/licenses/MIT

That's the license template, not the actual license file.

@onlyjob
Copy link
Author

onlyjob commented Jun 6, 2016

That's the license template, not the actual license file.

This is canonical text of the license, contrary to maybe-customised (altered) license file which may not be included. Link to authoritative OSI approved text of the license + copyright statement is the best for situations when including full text of the license is not desirable. Also It may be useful to mention URL of the project (backlink).

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

3 participants