...
- Val: re-visit the idea of DCAT working on JIRA tkts – or is being involved in projects like the metadata improvements project as much as we can manage?
- Bram: the value added to JIRA tkts varies - depends on individual's knowledge and time available, Bram works on documentation related JIRA issues
- Maureen: DCAT members could still work on JIRA tkts if we aren't working on other projects
- Elin: Objectives of doing 3 issues per month might have been too much – to much for everyone to read, think about and comment on
- Val: So is it reasonable to re-start JIRA review if we set reasonable objectives - maybe just one JIRA issue for all of DCAT per month? one discussion leader and one issue? (everyone generally agreed)
- Re-post/reminder of tools for JIRA discussions:
- Val: also want to talk at some point about joint mtgs between DCAT and committers - DCAT always welcome to attend cmtr mtgs can certainly get on the formal agenda. Propose putting on the potential mtg topics for OR mtg a proposal to have 4x a year cmtr/dcat mtgs.
Bram's JIRA refresher:
During the last meeting we were talking about DCAT's assistance in dealing with JIRA tickets. Here are a few links and a tidbit of information to explore JIRA if you are not yet really familiar with it.
Just going to http://jira.duraspace.org may be a bit confusing because you will also see the other projects that Duraspace hosts in there.
The following link sends you straight to the "Issues" tab within the DSpace project, I think it really gives a great overview: https://jira.duraspace.org/browse/DS#selectedTab=com.atlassian.jira.plugin.system.project%3Aissues-panel
Here's a reminder about the different stages you can see in "status summary"
Closed - hurray, it's fully handled!
Received - requests that require a first early scan to see whether they contain enough detail or not. If it does, it goes to the "volunteer needed" stage, otherwise it goes back to the submitter in the "more details needed".
More details needed - committers haven't been able to unambiguously interpret tickets in these stage, therefore, additional details are required before a volunteer can be assigned
Volunteer needed - Issues that have been found relevant and/or reproduced (in case of bugs). They are waiting for a volunteer who can come up with a solution
Accepted - There is a volunteer who is currently working on a solution
Code review needed - The volunteer made his solution available and is now waiting for a review before it can get accepted to the DSpace sourcecode.
I think DCAT can really help in the bolded stages:
Received: help to judge whether the incoming tickets contain enough detail
More details needed: try to ask relevant questions in the comments, poking the original submitter to provide more detail
Volunteer needed: There are today 155 issues waiting for a volunteer. You can put some of these tickets in the spotlight by commenting or +1 on them to indicate that they are really important to you.
more info about the process:
https://wiki.duraspace.org/display/DSPACE/JIRA+Workflow+Improvements
An easy example - ticket about documentation for the cleanup script
https://jira.duraspace.org/browse/DS-1545
This is in the "more details needed" phase: where do you think that additional documentation or warnings should be about the fact that content will _only_ be really deleted if you execute the cleanup script.
3) Metadata improvements project
...
Action Item | Assignee | Deadline |
|---|---|---|
| Check on finding time slot for a discussion metadata improvement proposal at both DSUG OR13 and OAI8 DSUG | Val, Bram/Iryna | DONE |
Re-start JIRA reviews 1) Everyone should select a JIRA issue of interest (Bram's recommended view: https://jira.duraspace.org/browse/DS#selectedTab=com.atlassian.jira.plugin.system.project%3Aissues-panel)
2) If the issue you select merits DCAT discussion (you want to confirm the importance of the request, want input on request, want to propose DCAT sending a msg to the listserve to find volunteers, etc.) please schedule the month for which you'd like to hold the discussion on the 2013 DCAT Discussion Schedule. If your JIRA issue doesn't merit a DCAT discussion, use JIRA to follow up directly. 3) Monthly discussion leaders should use the DCAT Discussion Forum to start your discussions with the rest of DCAT. 4) Post links/updates to the JIRA issue (summary of DCAT discussion with links to forum, etc.). | ALL | |
| Create (provocative) questions for community discussions - including brief description of what is planned and potential implications | Metadata Sub-Team: Sarah P., Amy, Maureen | |
| Start discussion on the institutional profile for organizations that should be keenly interested in the metadata improvement project | Val to start |
|
Post JIRA discussion tools
| Val | DONE |