PIP-10: Naming convention & acronyms adjustments to differentiate EPNS Protocol Improvements from Push Governance Improvements

Link to Draft Proposal (Proposal Phase)

Background:

This proposal aims to add more specificity to the acronyms and naming conventions used for EPNS Protocol Improvement Proposals, against the PUSH Governance-specific proposals.

The goal is to use PIP for Push Protocol Improvement Proposals, and PGIP for Push Governance Improvement Proposals

Proposal Description

At present, PIPs or Push Improvement Proposals are mainly used to refer to proposals on governance. As we grow closer to making EPNS a DAO, it becomes imperative to involve the community in technical decisions.

The web3 developer community is very familiar with the Ethereum Improvement Proposals (EIPs). So following similar standards, it is proposed to use Push Improvement Proposals (PIPs) to describe the technical standards/improvements of the EPNS protocol.

Proposals on the Governance side will then take on a new name of PGIP i.e, Push Governance Improvement Proposal.

Conclusion

If the feedback from the community is affirmative, this proposal would be promoted to the Discussion Phase and then to formal voting. If ratified PIPs will be used to describe technical standards/improvements and PGIPs will be the go-to place for Governance proposals.

This proposal is eligible to get promoted to Snapshot via the Fast Tracking Route after the discussions in the Proposal Phase.

Proposal is up for voting on Snapshot for 3 days
https://snapshot.org/#/epns.eth/proposal/0x8c44b949f2b3d9963a82991e0f8e98afb1e3d4df241683ed53c925dad62b222e