Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rebrand to Checker Node #676

Open
7 of 10 tasks
juliangruber opened this issue Feb 6, 2025 · 0 comments · May be fixed by #677
Open
7 of 10 tasks

Rebrand to Checker Node #676

juliangruber opened this issue Feb 6, 2025 · 0 comments · May be fixed by #677
Assignees

Comments

@juliangruber
Copy link
Member

juliangruber commented Feb 6, 2025

  • Decide on project name
    • Checker Core
    • Checker Node
    • Checker
      • simplest
      • intuitive: The networks consists of many checkers
      • matches CLI name chosen
  • Decide on CLI name
    • checker
      • previously was station
      • checkernetwork is too long and doesn't describe the CLI better
  • Rename CLI command
  • Change configuration defaults
  • Rename NPM page
  • Fix any remaining notion of "Station" or "Core"
  • Change "module" to "subnet"
  • Rename repository
  • Publish new npm package
  • Deprecate old npm package
@juliangruber juliangruber self-assigned this Feb 6, 2025
juliangruber added a commit that referenced this issue Feb 7, 2025
@juliangruber juliangruber linked a pull request Feb 7, 2025 that will close this issue
4 tasks
@juliangruber juliangruber changed the title Rebrand to Checker Network Rebrand to Checker Node Feb 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant