Bugzilla – Full Text Bug Listing
| Summary: | [pmi] Generate default merit statement for elections | ||
|---|---|---|---|
| Product: | Community | Reporter: | Wayne Beaton <wayne.beaton> |
| Component: | Project Management & Portal | Assignee: | Martin Lowe <martin.lowe> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | caniszczyk, chris.guindon, contact, eric.poirier, gunnar, jayjaybillings, konstantin |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | stalebug | ||
| Bug Depends on: | 375895 | ||
| Bug Blocks: | |||
|
Description
Wayne Beaton
I've refined the purpose of this bug to be primarily concerned with generating a default merit statement for an election. This bug is related, but slightly different in intent, to Bug 366433. Consider mining information from Git: git shortlog -nse +1 Something like git-shortlog with a custom format to our liking would probably work well... we could assume that if the person being nominated isn't available in the git-log then something is not right... Or better yet... have the form give an option for you to nominate someone based on who is in the git-log but not a committer yet (if we wanted to get fancy) git shortlog -nse only counts commits, which might not be enough to evaluate the size of the contributions. Taking LOCs into account might be a great addition. Something along those lines might help: - git log --author="John Doe" --oneline --shortstat - https://gist.github.com/234560 My 2 cents... This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. Here's a template that came up in discussing 460734. It roughly goes:
X recently started {as a full time employee on; contributing to; etc.} the {team name} team and has already made an impact on our project. They have addressed several bugs
{Link to bugs}
that {what the bugs address}. They have also {other things they have done}.
For these reasons and the long-term outlook for their involvement on the
team, it is my pleasure to nominate X as a committer on {team name}.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. Hi Wayne, Not sure if this bug is still needed or not? There was work done in the past to add the default message to the nomination form. Example: https://projects.eclipse.org/projects/technology.dash/nominate/CM Let me know if there is still work to be done here. Thanks. |