Date
29 November 2016
Call-in Number
1-888-354-0094
Access code is 731627#
Attendees
Discussion Items
| | | | |
|---|
| 1 |
| Roll Call | Suzanne Stasiulatis | Chris Prom is scheduled note taker. Suzanne filled in for Chris. Thanks, Suzanne!
|
| 2 | 5m | Review of survey results | All | - Results went out to AUG, et al. last week; any next steps?
- All of the community has seen the results. Nobody has responded. The team discussed whether we should solicit responses. The team decided that this was more about transparency and the uptick in epics.
|
| 3 | 10m | Update on HM work-in-progress | James Bullen | - Status report on stories documented here
- HM addressed the top 12 or so items on the list in this release. They are working on different sources. They are able to get to the pull requests and the easy ones first. They realize there is still a long list and will be working through it for the next round.
- AR1595-AR1604 – 1st half are related to running imports and large imports.
- The group discussed JIRA and GitHub and what should be posted on which site. The group discussed whether these two sites could be integrated with links, etc. This will be discussed more in the Roadmap working group meeting this week. Version tagging was discussed. HM noted that JIRA is more useful for those observing than those using it. This will be discussed more in the future.
|
| 4 | 5m | Community support for AR-1592 | All | - Assessing whether this is a critical issue
- AR-1592 deals with having a large number of tree objects. Sally reported the issue.
- This may be dealt with for the next release but is too big for 1.5.2. It is possible that it could get worked into the next major release in March.
- This will require significant reworking of how trees are handled in the front end. Drag and drop isn’t the best option with 10,000 siblings.
- Jason stated that he believes the interface itself should be revisited.
- There is a local workaround using the API.
|
| 5 | 10m | Roadmap working group | Laurie Arp | - Brief synopsis of planned activity; first meeting this Thursday (12/1)
- Laurie stated there is a lot of interest to create a roadmap. It will act as the core underneath things.
Timeframe – 3-4 major releases a year and minor releases in between. This could include upgrades and maintenance. A roadmap also allows for transparency. It allows for communication. It will be a living document. The team includes Laurie Arp (Lyrasis), James Bullen (HM), Jason Loeffler (Development Prioritization Sub-team), and Mark Cooper (Lyrasis). In the future, the team will also include the new Tech Lead. The first meeting is Thursday. Information will be shared with Sally and Gordon from this group. We discussed the benefits of being able to point people to documentation and information about the roadmap. We discussed how contributions from the community could factor into the roadmap. We also discussed that 4 plus releases a year might be too much for some smaller (or larger) (hosted or self-hosted) members of ArchivesSpace. Often, an institution may need IT resources, planning, and training for each release. - Sally talked about doing temperature checks with the community closer to March. Laurie said that was a good point, because not everything will be from the survey. We discussed finding agile ways to get feedback. We could just ask the listserve what they want next out of a few options in a survey.
|
| 6 | 10m | 1.5.2 release schedule | All | - What/when to expect; public beta testing begins this week?
Everyone was encouraged to test the new release. If your institution isn’t upgrading just yet, you can use the test server. Jason noted that the release notes are very good. There is an issue with the display of two report options. This will be submitted for a fix. HM wants good, timely issues like the one they got on the call. The Reports Sub-committee is still working on the reports. HM stated they haven’t had a chance to work on the reports yet. This might be much farther down the road.
- We can follow up with Christine if there are any other issues. HM noted that JIRA might be the way to report issues or go through Christine.
|
| 7 | 10m | 1.5.3 planning | All | - Work plan for re-evaluating backlog and icebox
This release will be in conjunction with the roadmap and the prioritization survey. The Development Prioritization group will continue to go through the icebox and groom stories for the next release. James wants to push out minor releases every month or so, but he was hearing on the call that the group may want fewer releases. 1.5.3 could be mid-February. 1.6 could be the end of March. HM questioned if we should just go to 1.6? HM would prefer more frequent releases. The group thinks it’s important to tell the community that they don’t need to do all the releases. We should decide whether we want updates every month or every quarter. Archivematica (which has AS integration) will be going through an upgrade. It is not on the HM roadmap to make sure integrations work. Testing will be left up to the institutions who use Archivematica. HM is not talking to any of the companies and groups. However, we may get feedback in the JIRA log. - The Development Prioritization Group will meet semi-monthly for an hour to review epics and the icebox. The order we will go in is TBD. The group will then push the stories to HM.
|
| 8 |
| Q&A | All | |
Notes
AR-1592
-
Getting issue details...
STATUS
Action Items