OpenSlides / OpenSlides/openslides-client
New behaviours for LoS and if participants are on there several times
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 35
- Forks
- 52
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 52
Description
Currently:
A new feature allows that one participant can be on a Los several times. The participant is only allowed to put themselves on the LoS once. Only a person with LoS_canmanage can put a participant on the list several times.
Now the LoS needs (potential) more visible information for the user:
-
the user/admin needs a marker to see which contribution was set by themselves use vs a different user
- Question: should the marker (contribution is set by self) determined by the person who sets the contribution or should is be determined whether or not the contribution was added via the 'Add me' button we 'select the speaker box
- The backend probably needs a new field which saves who/where/how/new boolean etc. the contribution was saved
-
We need to discuss:
- how the marker should look
- if the marker should only be visible for contributions which were set by self/others
-
Wanted behaviour?: A participant should always be able to put themselves on the list once and to ONLY remove themselves from the list if they put themselves on there
- does this need a new setting?
Summary:
- add a marker for a contribution (self/other)
- design/UI/UX
- new setting, and new possibilities for the participant
Contributor guide
No contributing guide indexed for this repository
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
The issue names no files or tests. Start by reviewing the existing LoS participant flows, including the “Add me” button and speaker selection, then resolve the open questions about marker meaning, appearance, visibility, and self-removal. Done requires an agreed UI/UX design, participant rules, and any required setting or saved contribution metadata.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- design, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100