Nit and clarification on GroupState
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- documentation
Research direction
The issue concerns the joining section of the explainer in this repository, which uses mls.joinGroup() and also groupJoin(). Make the method name consistent, then rewrite the sentence claiming the new member has the same group state as the creator so it says the Welcome sets the joiner's state at a specific epoch and later messages may be needed to catch up. Done when the section uses one name and the epoch qualification reads correctly.
Written by the indexing model from the issue text.
Description
Nit: The joining section calls mls.joinGroup() and then refers to groupJoin().
The section also says the new member has the same view of group state as the creator. Please qualify this: the Welcome establishes the joiner’s state at a particular epoch, and the client may need to process later messages to catch up.
- Dominant language
- No language data
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from mozilla/mls-webapi-explainer
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
Difficulty 5/5 Over a week Newbie friendliness 18/100
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
All issues in mozilla/mls-webapi-explainer
Similar issues
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
enhancement priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
briandconnelly/amicus#351 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nginxinc/nginx-hugo-theme#498 ·
-
track: content
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
0xAndersen/witness-log#10 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 76/100
w3c/csswg-drafts#14589 ·
Maintainers usually reply within 1 day