You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 30, 2019. It is now read-only.
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)
The text was updated successfully, but these errors were encountered:
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.
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)
The text was updated successfully, but these errors were encountered: