PAIR-code / PAIR-code/deliberate-lab
Allow booting participants with a message / explanation
Open
Nobody has claimed this yet.
runtime:participant-ux
stale
wishlist
- Dominant language
- TypeScript
- Stars
- 96
- Forks
- 40
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 20
Description
Sometimes, participants are booted for reasons outside of their control (e.g. someone else left, not enough people to form a cohort, etc.) It may be nice for an experimenter to be able to provide a reason (and perhaps for participants to respond, similar to an alert)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating the participant boot flow and the existing alert or participant-response behavior, then clarify how an experimenter supplies the explanation. Done means participants receive the message when booted and can respond if that remains in scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100