Skip to content
This repository was archived by the owner on Nov 1, 2023. It is now read-only.
This repository was archived by the owner on Nov 1, 2023. It is now read-only.

Naming convention #87

@sakulstra

Description

@sakulstra

Proposal naming

Currently proposal names are somewhat arbitrary and tend to overlap (especially with the recent mass of cap update proposals). Therefore it might make sense to define a naming schema including:

  • some temporal

  • chain

  • pool? (not sure as a proposal might touch multiple pool)

  • author? (not sure as might be collaborative)

  • topic? (might be complicated when doing multiple things)

  • A schema should be defined and documented on the readme.

Optional Generator:

Probably would make sense to add a generator so it's easier to follow the new convention. Also might make sense to seed generated files with some template. With the new config engine one might even consider a inquirer like prompt to generate proposals.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions