Skip to content

Minimal rename of go-ipfs in 2022Q2 #8959

Closed
@lidel

Description

@lidel

This is part of ipfs/ipfs#470, read that first.

What

IPFS Stewards are renaming go-ipfs to something else ❄️

👉 Feel free to comment in ipfs/ipfs#471 with name (and logo like one in #8958).

Note: we reserve the right to ignore every instance of Boaty McBoatface.

Why

This is part of a wider, long ecosystem epic (see ipfs/ipfs#470) where we clarify that IPFS is a set of interoperable protocols and conventions, and not a specific implementation, like go-ipfs.

tl;dr:

  • go-ipfs will stop squatting "IPFS" name
  • we want to encourage people to create their own implementations
  • makes it easier to think in terms of "IPFS protocol, libraries and specs" and "IPFS implementations" that are built with the former

When

This will take time, but we want to do the basic rename of project / repo (scope tbd) before July 2022

How

The scope is TBD, we are identifying potential breakage in #8958.

Current proposal is to:

🟢 Rename before July

👍 👎 🤔 Need analysis and decision

🛑 Keep or rename at a later date

Things that use go-ipfs name, that we don't plan breaking at this time:


WANT TO PROPOSE THE NEW NAME?

👉 Feel free to comment in ipfs/ipfs#471 with name (and logo like one in #8958).

Metadata

Metadata

Assignees

Labels

effort/weeksEstimated to take multiple weeksexp/expertHaving worked on the specific codebase is importantneed/analysisNeeds further analysis before proceedingneed/community-inputNeeds input from the wider communityneed/maintainers-inputNeeds input from the current maintainer(s)

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions