Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IPIP numbering #303

Open
thibmeu opened this issue Aug 2, 2022 · 2 comments
Open

IPIP numbering #303

thibmeu opened this issue Aug 2, 2022 · 2 comments
Labels
need/community-input Needs input from the wider community P1 High: Likely tackled by core team if no one steps up

Comments

@thibmeu
Copy link
Contributor

thibmeu commented Aug 2, 2022

Similar to RFC or EIP, it would be good to refer to IPIP with a number as soon as they pass a "consideration" threshold.
At the moment, issues and PRs are opened with a title "IPIP ". Having some sort of number assignment would help to consistently reference IPIP.

For instance, the IPIP defining IPIP would be IPIP-1, and follows. At first, this could be pruned by the steward team, or chosen by the IPIP proposer (if there are some particular number that appeal).

IPIP-1 should be revised accordingly

@thibmeu thibmeu added the need/triage Needs initial labeling and prioritization label Aug 2, 2022
@guseggert guseggert added P1 High: Likely tackled by core team if no one steps up need/community-input Needs input from the wider community and removed need/triage Needs initial labeling and prioritization labels Oct 6, 2022
@guseggert
Copy link
Contributor

We'll bring this up at the next IPFS implementers sync.

@lidel
Copy link
Member

lidel commented Oct 26, 2022

Discussed this in Lisbon, and we are considering going with a very simple convention: use the PR number from github.

  • allows us to immediatelly have number for every proposal
  • does not require any coordination and guarantees there will be no conflict
  • typing "ipfs specs " in address bar will immediatelly point people at the right PR

Is there a better way?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need/community-input Needs input from the wider community P1 High: Likely tackled by core team if no one steps up
Projects
None yet
Development

No branches or pull requests

3 participants