Skip to content
This repository has been archived by the owner on Apr 30, 2019. It is now read-only.

Proper attribution in an SDK #132

Closed
pauldambra opened this issue Dec 11, 2014 · 2 comments
Closed

Proper attribution in an SDK #132

pauldambra opened this issue Dec 11, 2014 · 2 comments

Comments

@pauldambra
Copy link

I've a colleague who won't consider using otto because the license requires attribution. We produce an SDK that will be used by others and can't insist on attribution in their app.

I thought a NOTICE file in the SDK was suitable but he thinks not.

Which of us is correct? Or if we're both wrong is there a correct thing to do?

Thanks (apologies if this is the wrong place to ask)

@JakeWharton
Copy link
Member

You will have to consult with a lawyer on your end on what you can or cannot do.

Not only are we (the developers) of this library ill-equipped to answer the question, but any statements we make might undermine or implicitly alter the license that has been applied. This is especially important to avoid since a large chunk of the code is actually copied from Guava which we do not have the rights for altering its license. Sorry I can't be of more help.

@pauldambra
Copy link
Author

Ah, so Otto has the Apache license because it is copied in from Guava?

Thanks...

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants