The act of closing an issue should be a thing: Achievements

Open
#31 1 comment 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
frontend

Research direction

No files, tests, or entry points are identified in the issue. Start by mapping the existing issue-closing, achievement, profile/history, and sharing flows, then clarify the achievement model, reward sizes, and chat-sharing behavior before defining completion criteria.

Written by the indexing model from the issue text.

Description

The act of closing an issue should be a thing which can be used to accumulate kudos and provide rewards.
What to call it?
An achievement. A Done That. A check mark. A crossing off the list.

We should design the system so that people get dopamine shots from these, both from getting them, and from sharing them, and possibly from others applauding them.

You should be able to look back on the week and see all the issues you -- or your team --- have closed.

Make them big/medium/small? Yes I think we have icons elephants mice etc.

You should be able to drop an achievement into a chat for example to get encouragement.

Dominant language
JavaScript
Stars
7
Forks
3
Avg merge
7m
Merged PRs (30d)
3

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.

More from SolidOS/issue-pane

All issues in SolidOS/issue-pane

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.