Skip to content

Non-headliner scoping interface for client teams to input preferences. #118

@abcoathup

Description

@abcoathup

For the Hegotá upgrade can Forkcast include an interface for client teams to input preferences.

Each team would use the same rating scheme and be input into a single source of data. Ideally this would include text fields where they could supply more information/reasoning. Similar to the thoughts: https://ethereum-magicians.org/t/2025-upgrade-process-retrospective/27082/2#p-65496-non-headliner-eips-12
We wouldn't have data collation headaches and having to compare rating scales.

All core devs could then use https://forkcast.org/priority to help reach rough consensus faster. Though we need to be careful not to lose rough consensus to voting/vetos.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions