Here are my notes from our first meetup yesterday on tagging/taxonomy for EIPs. Feel free to add to this or change if I misinterpreted anything from the discussion. Hopefully with our next discussion, we can get closer to having an MVP for the taxonomy
EIPs Taxonomy Discussion
4 types of tagging/taxonomy categories for each EIP:
Status: At what stage of review or implementation is this EIP? Examples - submitted, read, finalized, rejected, etc.This category already exists in the EIP repository.
Context - What is the subject matter of this EIP/what aspect of the technology is this EIP addressing? Examples - Wallet, Security, Token, UI, etc. We could subsequently create a link to the community(ies) that are most impacted by this EIP (FEM Wallet Ring, Gitter Communities, etc.)
Impact : At what technical criticality will this EIP require if implemented? Examples - Hard Fork, Asthetic Design Only, etc.
Notification Level: For the stakeholders affected, what type of notification should they receive? Example: Notification to update code base, awareness notification only, etc. Note - we would need to include a list of which stakeholders are impacted.
3 Groups As Targets for Understanding this taxanomy for EIPs:
- Editors from Core Devs
- Supporting Groups
Note - most of the taxanomy, specifically for the Context category, can be derived from supporting communities to then notify the communities involved on if they are impacted, However, the tags themselves should be stored centrally on the EIPs Github.
Editors should decide and add high level tags, interested supporting groups/communities can add further granular tags for their interest.
Example: EIP editor adds a tag “Security” to an EIP, an FEM Security Ring member adds a tag for “User Facing” to that EIP.
- How do the analyze which tags are most used so that they get mass adoption? Do they need to be promoted i.e a system of “liking” a tag? Or will the natural order progress them already?
- Who will have access to create tags? The entire community? Just Editors?