I've gone ahead and resolved as "Won't Fix" 78 stories that had no votes and no recent (2012) activity. Any can be individually reopened if you feel that they shouldn't have been closed.
I appreciate the work of all of you who contributed to the voting and commenting and closing tickets known to be done. We're down to 154 open stories. Still a lot, but definitely better. Thanks especially to those who entered the duplicate ticket number when they found a duplicate; I closed these. I did notice a number of tickets had comments to the effect that they were duplicates but didn't provide the duplicate ticket number. It would be so incredibly helpful if the duplicate ticket number was indicated: I don't think we should close a ticket as a duplicate unless there's a link to the duplicate, so I'm leaving these open for now. Many of them had votes. (Thus, a follow-up cleanup task, which I'm not taking on myself now, is to go thru and resolve open tickets that have duplicates, once those duplicates are found.) For those interested in the voting, here's the list of stories that do have votes, sorted so you can see where the most "demand" is: http://opencast.jira.com/secure/IssueNavigator.jspa?mode=hide&requestId=11269 (I am proud to announce that MH-7088 To work effectivly a team must have coffee. was in the top 3, tied with MH-8912 LDAP/Shibboleth authentication.) Judy On Jun 25, 2012, at 12:19 PM, Judy Stern wrote: > In a continued effort to cleanup Jira, let's focus on user stories. (User > stories are the way we keep track of feature requests.) We have 250 open > story cards, many of which are surely irrelevant at this point, so it's time > to do a mass cleanout. Jira has a voting mechanism, and this seems like a > fairly simple (if imperfect) way to get a sense of which stories are still > relevant. > > Therefore, I request that anybody that is using or intends to use Matterhorn > review the list of open stories > <http://opencast.jira.com/secure/IssueNavigator.jspa?mode=hide&requestId=10589> > and, by July 15th, add a vote to any that are important to your institution. > Adding a vote is a simple matter of selecting "Add Vote" (either from the > gear menu in the Issue Navigator or from the More Actions menu in the ticket > itself). You'll need to have an account on the Matterhorn jira to vote, but > not to review the open stories. (If you want to vote and don't already have > an account, please visit > https://opencast.jira.com/login.jsp?os_destination=%2Fsecure%2FDashboard.jspa > and sign up.) > > After July 15th, I will resolve as Won't Fix each open story card UNLESS it > gets at least one vote OR is currently active (which I'm defining as having > been updated in 2012, or having a fix version of 1.5 or later). > > Please note that there's no absolute guarantee that stories that get lots of > votes will get attention from developers; it *will* help, however, to > highlight to developers what's important to the community and may increase > the chances that such in-demand features will be addressed. And, if you care > about something, voting is the best way to "keep it alive". > > You get extra points (well, you get extra appreciation) if you close a story > because you recognize that it has already been done, or that it's a > duplicate. (Please comment informatively). And, as always, the best thing you > can do is to decide that you will contribute the work to address one of these > tickets! > > Many thanks in advance for your participation in this activity, > Judy Stern > Educational Technology Services > UC Berkeley > _______________________________________________ > Matterhorn mailing list > [email protected] > http://lists.opencastproject.org/mailman/listinfo/matterhorn > > > To unsubscribe please email > [email protected] > _______________________________________________
_______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
