This document is for maintainers.
It is a work in progress and suggestions are welcome.
A issue or PR should only be assigned to someone if they would be actively working on it or would be working on it shortly. This avoids the scenario when we think everything is being addressed when that is not the case, particularly when people are busy, which may cause issues to invisibly languish.
The maintainer for a particular technique is responsible for that technique.
Github PRs
- The maintainers should watch out for PRs, filtered by the corresponding technique label. For example, the label for quantization-aware training is here. This labeling is automated here.
Github Issues
- The maintainers should skim through issues and attach the appropriate technique label. This has not been automated yet.
- Use other labels as needed, according to CONTRIBUTING.md.
Ensure that contributions adhere to the guidelines suggested in CONTRIBUTING.md. Comments that are frequently made in PRs should be added there.
If there are public API changes, please attach the "api-review" label for a closer look from the TFMOT team.
Once you think a PR is ready to merge, apply the "ready to pull" label and someone will merge it.