You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It outlines a process of how we approach work on the website:
We organize our tasks in 3 categories:
in progress
planned
implemented
Then it pulls in various GH issues (via GH API) with the associated labels:
planned: Status: Up Next
in progress Status: In Progress
Then for "implemented" I believe it just pulls in PRs that have been merged.
Overall this is ok but I don't think it accurately reflects our roadmap. e.g. I don't think the Status: Up Next or Status: In Progress issue labels are frequently used.
Describe the solution you'd like
It might be easier & clearer to just:
explain we set our product roadmap on a quarterly basis
link to the most recent product roadmap GH issue (currently Q4 2022 ethereum.org product roadmap #8399), which gives a clear outline of what our priorities are & we're working on
Delete the various Status labels from GH
Describe alternatives you've considered
remove the "Roadmap" section from the page entirely
start using status GH labels on issues/PRs with more discipline
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
We currently have a "Roadmap" section of About page:
https://ethereum.org/en/about/#roadmap
It outlines a process of how we approach work on the website:
Then it pulls in various GH issues (via GH API) with the associated labels:
Status: Up Next
Status: In Progress
Then for "implemented" I believe it just pulls in PRs that have been merged.
Overall this is ok but I don't think it accurately reflects our roadmap. e.g. I don't think the
Status: Up Next
orStatus: In Progress
issue labels are frequently used.Describe the solution you'd like
It might be easier & clearer to just:
Status
labels from GHDescribe alternatives you've considered
Additional context
No response
The text was updated successfully, but these errors were encountered: