2

Say, if I found one of the package in my project adopted GPL license, and I already had published my repository to Github as MIT, I immediately have to;

  1. delete the whole repository.
  2. change the license to GPL.
  3. remove the dependency to maintain MIT license.
  4. No way. I'll be sued for it someday.

Which would be possible choices?

EDIT:

I didn't know the example above is okay. So let me change the assumption.

If I found one of my JS, CSS, HTML or other stuff had been brought from MIT licensed source and I had never put the copyright notice in the file, I have to;

  1. delete the whole repository.
  2. remove the file or substitute another file for it.
  3. No way.
|improve this question
  • There is no general problem with you licensing your work under MIT, even if you include GPL components. See e.g. Can library that took parts of library licensed under GPL with Classpath Exception be licensed under MIT? – Brandin Feb 16 '18 at 12:36
  • Oh I didn't know they are compatible. I referred the example just to explain there's a problem in licensing... I edited the example. – K. Makino Feb 16 '18 at 13:02
  • 2
    If you discover something is missing (license notice), what is wrong with just modifying the file and adding the needed information? If you published the repository publicly along with all commits, in theory someone could go back and get the prior commit that doesn't have this information, but you have to evaluate the risk of this against your options: In most cases, just fix the problem and ignore past commits; if it's critical, use git rebase to squash that commit; if all else fails, the nuclear option is to completely delete the repository. – Brandin Feb 16 '18 at 13:46
  • Hmm so it depends. Thanks for your advice. – K. Makino Feb 16 '18 at 14:11
4

If you find out that you are not fulfilling the obligations that a third-party license puts on you, then you should correct that as soon as possible.

If copyright and/or license information is missing or incorrect, you should update those files so that they contain the correct copyright and license information.

If a third-party dependency, which is not copied into your repository, changes its license to one that is incompatible to your license, then you should first try to pin that dependency to the last (tested) version before the license change.
After that, you can take your time to consider if you can replace that dependency with something that does have a compatible license or if you want to change the license on your project (which can only be done with explicit approval of all contributors).

In any case, these actions show that you are serious about copyright licenses and that you don't try to take advantage of someone's code. Should they try to sue anyway, that will probably be looked upon favorably by the courts.

|improve this answer

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.