JIRA Review
Categorize feature request:
1) Determine relevancy: Is this feature useful or relevant to other repository mgrs? Does it impact a lot of repository mgrs? If it is unclear it may require clarification from requester.
2) Determine priority (if relevant) - how important is this request - high, medium, low priority. High priority-make or break DSpace (meets immediate and widely prevalent need), Medium (would eliminate some frustration), Low-not that urgent (would fix an annoying issue)
3) Brainstorm on whether or not there are any known stakeholders for the feature development. If priority is "high", someone from DGOC to send a message out to the mailing list about the feature and see if anyone in the community would like to add feedback to JIRA or discuss collaborating on solution
4) Post DGOC categorization notes in JIRA issue
Examples:
Relevant, High Priority: "Relevant, High Priority: After reviewing this issue, the DGOC believes there may be broad interest in the community in this issue. It would seem to address a very significant need and would be a high priority to explore further. There are no known stakeholders, but an email was/will be sent on 10/15/10 to the general & tech mailing lists to solicit discussion. "
Not relevant, Low Priority: "The DGOC has reviewed this request and based on the information provided we do not believe there is broad enough interest in the community to pursue work on this issue." Reviewer to write a personal email to requester to explain/describe.
Other notes that DGOC may want to include in JIRA:
- identify any basic, minimum requirements
- need clarification / more info from requester before issue can be categorized by DGOC
- need input from committers/developers
- other recommended course of action
Logistics
-suggested time limit for DGOC discussion is no longer than 10 min per issue
-DGOC to primarily spend review time on "unassigned" "new feature" issues only
-review "assigned" issues just to make sure committers/developers don't need help from the larger community and to see if DGOC agrees w/implementation (don't need ratings, but can pose questions or provide feedback)
-following mtg, DOGC to provide summary to community for feedback/discussion
-skip the review of developer centric/back end/technical new feature requests
