-
Hey @izyumkin and @htmlprogrammist Just wanted to point out that one of you may need to reference the other project, as yours MCEmojiPicker and EmojiPicker seem to be almost identical (the readmes are 99% identical word-by-word). |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 11 replies
-
Lol that is quite the copy paste, good eye! |
Beta Was this translation helpful? Give feedback.
-
Hey! Yes, it's very funny! Finally someone noticed it. You can look in the commit history EmojiPicker who and when really made this library. In addition, I wrote an article in several languages about how I developed this library, and this person copied it and also participated in competitions with it... If you know what I can do with this, I would be very happy! |
Beta Was this translation helpful? Give feedback.
-
Hello, guys, In this whole story, @izyumkin misses the fact that he had the opportunity to develop together, no one "just copied" this project, a pull request was opened so that all developers could develop an open source library and an MIT license together – #7 He could also tell me that he would not like to output this project as a package, then we would just close the pull request, delete everything and that's it. But instead he decided to copy everything from my work without any modification. Let’s look through the readme, for example, as @nalexn pointed out: Mine updates and others: htmlprogrammist/EmojiPicker@7592f8a#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5 https://github.com/htmlprogrammist/EmojiPicker/commits/main/README.md His updates ea01387 (check commit comments here. And date. Immediately after my comment, he closed the pull request) Flags in localization (check dates) The author of the written code was admitted since the first commit of working on this project htmlprogrammist/EmojiPicker@80990c2#diff-94c67287601e99038cfdf11ed6bea8cb2edacea630b249a3b42e44bc0fadd67b and then I opened pull request |
Beta Was this translation helpful? Give feedback.
-
@htmlprogrammist you absolutely have the right to fork a project and continue the development independently - open source community works this way. Just as @izyumkin has the right to not accept PRs. MIT licence just requires the project that appeared second to keep the copyright notice in the existing files of the project and leave a link to the original. Just mention it was inspired by that library, but now is developed independently |
Beta Was this translation helpful? Give feedback.
-
@htmlprogrammist , yes, indeed our approaches are slightly different and that's why I closed your PR. But undoubtedly you have written good documentation for my library. At that time, I didn't know how to accept only one file from the pull request, and therefore I added the changes separately myself. If you want, you can make a new pull request with some changes in the readme file to "stay in the commit history" or suggest how I can still add your changes to the readme from a closed PR. What do you think about this? |
Beta Was this translation helpful? Give feedback.
-
@izyumkin To do what is fair, now I see options like this: reopen PR, accept changes, resolve all conflicts in your favor. But in this case maybe (maybe not) we will have to fix something later, for example, adding some now superfluous file. And the second option is simpler: mention me as the author of the documentation in the "About" of readme.md, for example, "Thanks to @htmlprogrammist for writing the documentation" |
Beta Was this translation helpful? Give feedback.
@htmlprogrammist you absolutely have the right to fork a project and continue the development independently - open source community works this way. Just as @izyumkin has the right to not accept PRs. MIT licence just requires the project that appeared second to keep the copyright notice in the existing files of the project and leave a link to the original. Just mention it was inspired by that library, but now is developed independently