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

DRAFT - Badges management #116

Open
srenault-meeds opened this issue Jan 4, 2024 · 0 comments
Open

DRAFT - Badges management #116

srenault-meeds opened this issue Jan 4, 2024 · 0 comments

Comments

@srenault-meeds
Copy link
Member

srenault-meeds commented Jan 4, 2024

Rationale

Badges can be added per program only when you are a reward admin
Problem is:

  • Program owners cannot manage it
  • Users cannot see badges related to each program
  • Badges UI / UX are not consistent with latest implementation

1. Functional Requirements

Top User Stories

As a program owner, I can list badges for my contributors
By default, three badges are proposed to make sure I don't start from nothing
These default badges are not listed to users until the program owner confirm it
Then I can add it or update it at my convenience for the program purpose

--

Once badges are confirmed and listed by the program owner
Contributors can start earning it and this can be displayed in the program detail page in the leaderboard and in a personal metrics tab
That way, it is possible to see the progression and to see what to do next to get more badges

--
Once badges are confirmed,
The program owner can set it as a condition to submit a contribution

Impacts

Gamification

Notifications

Analytics

Unified Search

2. Technical Requirements

Expected Volume & Performance

Security

Extensibility

Configurability

Upgradability

Existing Features

Feature Flags

Property Name Default Value Target Audience Functional Behaviour

Other Non Functional Requirements

3. Impacts

Documentation

Training

4. Software Architecture

Security

Access

  • GUI
  • API

Services & processing

  • Ex: Scheduled Jobs

Data and persistence

  • Macro data model
  • Persistence layer
  • Use of caches

Clustering

Multitenancy

Integrations

Migration strategy

5. Annexes

  • Reasoning that explain the technical choices
  • Impacts
  • References
@github-project-automation github-project-automation bot moved this to Open in MIP Board Jan 4, 2024
@srenault-meeds srenault-meeds moved this from Open to Draft in MIP Board May 21, 2024
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

No branches or pull requests

1 participant