Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

MPS priority conventions aren't public #142

Open
rptb1 opened this issue Feb 2, 2023 · 1 comment · May be fixed by #198
Open

MPS priority conventions aren't public #142

rptb1 opened this issue Feb 2, 2023 · 1 comment · May be fixed by #198
Assignees
@rptb1
Labels
documentation essential Will cause failure to meet customer requirements. Assign resources. git-migration Project migration from Ravenbrook internal Perforce infrastructure to public git repo manageability Affects the cost of managing the MPS project process To do with process or procedure

Comments

@rptb1
Copy link
Member

rptb1 commented Feb 2, 2023 •
edited

Throughout the MPS documentation, issue database, etc. we use conventions for expressing priority, based on a four-level keyword system: critical, essential, optional, nice. This corresponds to the variant MoSCoW method (but has more precise defintions) and to RFC 2199 keywords for requirements. We also distinguish "importance" from "urgency".

With #98 and GitHub migration these keywords are creeping into other places, like GitHub labels.

We need some clear public definition and guidelines so that people:

  1. can interpret what documents, issues, etc. mean
  2. contribute and communicate priority

See also #98 (comment) about migrating the Perforce "jobspec", which relies on this.
@rptb1 rptb1 added documentation process To do with process or procedure labels Feb 2, 2023
@rptb1 rptb1 added this to the Perforce Divorce milestone Feb 2, 2023
@rptb1 rptb1 added the git-migration Project migration from Ravenbrook internal Perforce infrastructure to public git repo label Feb 2, 2023
@rptb1
Copy link
Member Author

rptb1 commented Feb 3, 2023

We should use label descriptions https://github.com/Ravenbrook/mps/labels to connect priority labels to their definition somehow, even if just by a tag. They don't seem to be linkable.

@thejayps thejayps added the essential Will cause failure to meet customer requirements. Assign resources. label Feb 13, 2023
@rptb1 rptb1 mentioned this issue Feb 17, 2023
Open
@rptb1 rptb1 added the manageability Affects the cost of managing the MPS project label Feb 23, 2023
@rptb1 rptb1 self-assigned this Mar 12, 2023
@rptb1 rptb1 linked a pull request Mar 13, 2023 that will close this issue
Open
@rptb1 rptb1 removed this from the Perforce Divorce milestone Mar 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rptb1 rptb1

Labels
documentation essential Will cause failure to meet customer requirements. Assign resources. git-migration Project migration from Ravenbrook internal Perforce infrastructure to public git repo manageability Affects the cost of managing the MPS project process To do with process or procedure
Projects
Migrate the MPS from Perforce to Git
Status: No status
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Documentation of importance Ravenbrook/mps
2 participants
@rptb1 @thejayps