2 ms·
I have a similar problem. I recently forked a project to fix some stuff and want to ship another project that will use it as dependency. The owner of the origi
by MildlySerious 10y ago
I have a similar problem. I recently forked a project to fix some stuff and want to ship another project that will use it as dependency.
The owner of the original has been inactive and I can't have a discussion or get my changes merged, so I will have to add a version to my fork. With the changes being backwards incompatible, according to semver this would be version 2.0 and it feels incredibly wrong to release a major version of someone elses project without having talked to them.
How do others handle this and similar situations?
As for legal obligations, that very much depends on the license used by the original project. With the MIT license for example you're allowed to make changes and release those, but aren't allowed to claim the whole thing as your own creation (which makes sense because it's not). Not sure about changing names but iirc that's okay.
- jetti 10y agoI would think there would need to be some sort of name change so that it doesn't interfere with future releases or to dictate differences (such as Jenkins/Hudson). But I'm not sure exactly how that would work