project milestone issue limit. #4167
Conversation
shankarseal
requested review from
dthaler,
poornagmsft,
Alan-Jowett,
saxena-anurag,
dv-msft,
matthewige and
mtfriesen
as code owners
docs/Governance.md
Outdated
| A maintainer can also merge pull requests. | ||
| This corresponds to the "Write" role in github. | ||
| ### Maintainers | ||
| This corresponds to the "Maintain" role in github. A maintainer can manage repository settings. |
There was a problem hiding this comment.
I'd like to discuss this in the meeting on Monday.
There was a problem hiding this comment.
While I have restored the original roles and updated the codeowner file, let us discuss if we should have separate maintainer and active contributor roles.
docs/Governance.md
Outdated
| This label is used for low priority issues. Issues marked with `P3` label can be set to any future milestone or the `Backlog` milestone. | ||
|
|
||
| ## Milestone Issues Limit | ||
| At most 20 issues can be added to a project milestone. This limit makes it manageable for contributors to address all issues |
There was a problem hiding this comment.
I disagree with a fixed constant hard-coded here, as what is manageable for contributors varies by the number of active contributors, which varies over time. E.g., during a holiday period it will be fewer and during say summer internships or a hackathon (if one is planned) it may be more. It also assumes that all issues are equally difficult, which isn't true.
Also if some tool automatically files issues, say one per instance of some code issue that occurs 20 times, this would cause you to either reject other P1 issues, or go through all the work of combining the issues just to work around this limit.
There was a problem hiding this comment.
I have removed the fixed limit, and made it a soft limit based on capacity of contributors, complexity etc. But I have left a rule of thumb of not having more than (3 x contributors) issues per milestone.
shankarseal
force-pushed
the
policy
branch
2 times, most recently
from
287eb85 to
799e71d
Compare
Description
Describe the purpose of and changes within this Pull Request.
Proposes a new project management policy.
Testing
Do any existing tests cover this change? Are new tests needed?
N/A.
Documentation
Is there any documentation impact for this change?
This is a documentation only change.
Installation
Is there any installer impact for this change?
N/A.