8 ms·
Thanks for your comment. My concern is that all the changes introduced by the other project could have been done through pull requests. Also, the other project
by compassios 10y ago
Thanks for your comment. My concern is that all the changes introduced by the other project could have been done through pull requests.
Also, the other project wouldn't exist if my project wasn't there. One thing is being inspired, another one is creating a separate project that is dividing the community effort in two, instead of focusing in one project.
- neurotrace 10y agoThey could have but would removing those 3rd party libraries be in the best interest of your project? It appears that the other developer merely wanted a trimmed down version of what you have. As for possibly dividing the community: first, there's always competition. This is especially true in software where anyone with a keyboard and know-how can create a competitor. Second, if you're really concerned about community division, consider what happened with Node.js[0] and io.js[1]. Initially, io.js provided a slimmer and more frequently updated version of the same framework. Then they got together to discuss how they were dividing the community and decided to bring their projects together. Perhaps you should discuss such a merge with the author of the other project. [0] https://nodejs.org/en/ https://nodejs.org/en/ [1] https://iojs.org/en/ https://iojs.org/en/
- compassios 10y agoThanks for your suggestion! Specially for providing the example. I will take a look at that.
- deleted 10y ago[deleted]
- RubyPinch 10y agoYou are able to take his code (with credit and license) and incorporate it into yours, just as he can do to you.