I don't know if forks of this repo got the same notification, but I wanted to inform you that this library has been reported for copyright infringement by the original library I had forked, lots of lines and commits ago: the successful CameraKit-Android
.
I am sure you know this, because a link to that repo has always been pretty evident in our README
. In a few words, guys at CameraKit-Android
are complaining about me not reporting info of their license. Sadly, that's true - a long time ago I had relicensed the repo to Apache in order to be consistent with other libraries of mine, without thinking that I should have kept the original MIT too.
That was made out of distraction and was not a smart move, but hey, we learn from errors. I am deeply sorry that the original authors felt this as an offense to their work, and have fixed it with #68 (relicensed this repo to MIT as well, for simplicity).
GitHub policies give us about approximately 24 hours (sic) to fix the infringement, and the copyright owner has to agree that the issue is fixed. If they don't, GitHub will shutdown this repo immediately without checks. Bintray will probably follow, so the library won't be available anymore in gradle. I have done what I could, and now it's up to guys there.
The report I got seemed very angry and targeted the whole repository. Again, this is just, and we were wrong. But that's sad too - if they had just filed an issue here, I would have acknowledged my error and added back their license. It looks clear to me that we never wanted or aimed at hiding our parent repo - it has always been the first link in our README
file. We were in good faith.
Today we got to 400 stars, which makes me happy, but we are far from being as successful as them, and there's a lot of work to do. We clearly have taken different directions - the two repos share about 5% of meaningful lines, and that number can only decrease over time. I would like to keep this going, but if the guys there decide to proceed, there is not much I can do.
I have tried to get in touch with them but currently had no response. I hope I will have one so we can figure out what's wrong together. But if you come and find this closed, well, I'm sorry.