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

Clarify license/copyright of logo #2

Open
stain opened this issue Aug 15, 2016 · 1 comment
Open

Clarify license/copyright of logo #2

stain opened this issue Aug 15, 2016 · 1 comment

Comments

@stain
Copy link
Member

stain commented Aug 15, 2016

The license in https://github.com/common-workflow-language/logo/blob/master/LICENSE.md says

The Common Workflow Language Logos are (C) Copyright 2016 the Common Workflow Language Project and are released under the terms of the GNU Lesser General Public License, version 3 or any later version, or, at your option, of the Creative Commons Attribution-ShareAlike 3.0 Unported License.

Yet the license of the (smaller) logo at https://github.com/common-workflow-language/common-workflow-language/blob/master/site/CWL-Logo-Header.png is (now) distributed under Apache license 2.0

Is this license mismatch intentional because of the resolution differences or just historic? I assume the actual right holder has independently re-contributed the logo to the Apache licensed PNG.

As far as I know, Common Workflow Language Project is not a legal entity and can't own copyright. So presumably the original contributor of the logo (or their employer) would own the rights. Can this be clarified who are the copyright holders and attribution of the logo?

This affects: apache/incubator-taverna-common-activities#20 which wants to use the low-res PNG.

@mr-c
Copy link
Member

mr-c commented Aug 15, 2016

I've created a pull request to clarify the situation. This repository is the source of the logos, they were not released anywhere else.

ThilinaManamgoda added a commit to ThilinaManamgoda/incubator-taverna-common-activities that referenced this issue Aug 21, 2016
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

2 participants