DEV Community

Discussion on: What's the proper etiquette for forking an abandoned repo?

Collapse
 
jacoby profile image
Dave Jacoby • Edited

There used to be a command-line tool for Twitter, named TTYtter, but the maintainer dropped it. A friend took it over, renaming it Oysttyer.

Requirements were that the new project had to keep the (non-standard) license and change the name. It looks like it's called "fork" in the README but the git history starts fresh at the switchover. (Or I'm reading it wrong.)

That makes sense to me. The contributions exist under the license, and so they should be continued forward under the same terms. I recall that there are things in the Linux kernel that they'd like to change, but they'd have to get sign-off by hundreds of people, many of which are identified only by email addresses corresponding to long-dead hosts.

The name is different. When the maintainers of MySQL left Oracle to go back to how it was before, they could take the code but they couldn't take the name, and thus MariaDB.

So, NewCode is a project that does something, forked from OldCode, a module by PrevCoder with all appropriate links seems like the responsible place to start.

Collapse
 
ben profile image
Ben Halpern

Thanks for the input