Standardized nomenclature for feature requests

Hi there,

Q: Is there a reason why Pharo (as a project) doesn't follow a
standardized nomenclature for features/request as other communities does?

So for instance something like PFR-005 (Pharo Feature Request) could be
"Truly headless images", PFR-006 "Pharo Bootstrapping", etc.

I can't really tell whether this would improve to the overall process,
but I wanted to know if this was already debated by the board and
dismissed, if it is something that wasn't considered at all, of if we
have something equivalent and what it is.


Regards,

Language examples:
JSR (Java Specification Requests) https://www.jcp.org/en/jsr/all
PEP (Python Enhancement Proposals) https://www.python.org/dev/peps/
RFC (Rust, Request for Comments) https://github.com/rust-lang/rfcs

Technologies:
BIP (Bitcoin Improvement Proposal) https://github.com/bitcoin/bips
EIP (Ethereum Improvement Proposal) https://eips.ethereum.org/










--
Esteban A. Maringolo