Guide board
This page lists the guides the Open Terms Archive Core Team created for itself, in the form of a Guide Board.
In order to ease reviews and thus decrease cycle time, we extract refactors in their own commits in the same branch, starting their message with “Refactor” to highlight them for reviewers.
In order to minimise change requests and thus decrease cycle time, we extract changes that are not related to the story the branch is supposed to implement into their own pull request.
- Inform our partners of the intention to apply.
- Obtain application details before starting to apply.
- Explain the responsibility of porting.
15 minutes of drafting committee per day: 11:45 -> 12:00.
Apply the usual writing rules to the cases:
- Corrections after reviews.
- Merge via GitHub.
Add fixup!commits and rebase and force push only after approval
- Apply a tag.
- Open an issue for not transient cases.
Only update dependencies when they solve a functional problem or provide a functionality required from a business point of view.
Use the merge upstream + merge strategy in case of conflicts on an PR.
Only use the `suggestion' feature in PR reviews if they can actually be committed.
Explore cases of error in the proposals issued for the RFC before its closure.