matrix-org / matrix-org/mscbot-python
Add a little FCP to-do list to the tickyboxes comment
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
To transparently tell people what exactly needs to happen in order for FCP to start. The checklist would be slightly different depending on the FCP disposition (merge, close, postpone). For merge, you would have something like:
- [ ] This MSC has one or more implementation(s), or does not need one.
- [ ] There are no open concerns.
- [ ] At least 75% of the Spec Core Team members have approved this MSC.
Existing FCP comments can be updated with this list when they are edited.
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 file or test is named. Start by tracing the code that creates and edits FCP comments, then inspect how the FCP disposition is represented; done means merge, close, and postpone comments each receive the appropriate checklist, including updates to existing comments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100