Joystream / Joystream/joystream

CLI: Memberships management

Open
#282 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

CLI
Dominant language
Rust
Stars
1.4k
Forks
116
PR merge metrics
No merged PRs in 30d

Description

There's a need to manage not only the accounts (keys), but also the available memberships and roles inside the CLI in order to allow the user to specify the membership and role as a context for executing some of the commands that are going be implemented in the future (related to voting and governance).

I already started implementing this with the assumption that each account (pair of keys) always has either one or zero related memberships, so the base memership and available roles can be determined based on the currently selected account, but this may require some more inspection.

Some initial ideas I've had for commands that would need to be included:

  • member:register - create a membership profile for the currently selected account (if it doesn't already exist)
  • member:current - display information about currently used membership (and available roles)
  • member:edit - edit the current membership profile

There are definitely going to be more, but I'm still trying to figure out the correct way to handle this. I will update the issue as I go along.

Some commands for discovering other members will probably also need to exists, like listing, reading other members profiles etc., but I think that can be handled in a separate issue (as this one is focused mostly on how to manage user's own memberships)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the existing CLI account and key-management entry points, then compare the proposed member:register, member:current, and member:edit commands with the membership and role model. Confirm how the selected account relates to memberships before defining the command scope; done means an agreed design for managing the current membership and its available roles.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
blockchain, cli
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.