Maybe dumb question but should forks be completely renamed? Is prefixing enough?

github.com/c4social/mastodon/i

@weex I'd say you only keep the name if the fork exists solely for the sake of furthering upstream.

As soon as you intend to go a completely independent direction you should rename. E.g. gogs --> gitea.

There are some shades of grey. For instance a couple of fedi projects forked OAuth2 libs to add some commits that were required but not likely to be merged in upstream soon. They kept original name. Maybe they'd ditch the fork again once upstream fulfills their need.

Follow

@humanetech Even with the shades of grey, that's quite clear. Local-only posts are in and I don't think ever going in upstream so that would point toward a name change.

· · Web · 0 · 0 · 1
Sign in to participate in the conversation
Ecko / c4.social

Creating magic through evolution of the Fediverse. Running Ecko, a community-driven fork of Mastodon managed using the Collective Code Construction Contract (C4) by the Magic Stone Community. C4 is a protocol for asynchronous, non-blocking, distributed, problem-focused software development.