Add a little FCP to-do list to the tickyboxes comment

Open
#33 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
tooling

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.

Description

enhancement

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.

Dominant language
Python
Stars
7
Forks
2
No merged PRs in 30d

Contributor guide

Open the contributing guide

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 matrix-org/mscbot-python

All issues in matrix-org/mscbot-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.