2014-3-21 Meeting Notes
Notes for 3-21-2014 concall
User group updates:
UAG structured into subteams:
-feature prioritization committee - creating User Stories, tracked in Pivotal (we may work with them on some of the tech features - tbd)
-documentation committee: dealing with doc from within the application
- will have a helpdesk and monitor questions (listservs)
- reports subcommittee
-product comparison group - evaluate competing products
Conference updates
C4L
UAC will have a meeting at SAA, we are invited to attend
Program Updates (Chris F.):
- AS currently in acceptance phase of last sprint
--mostly focusing on plugin architecture, import/export features
--release likely for Monday next week
- re-evaluating sprint/release timing - may expand cycle
- hudson molonglo work wrapping up, but may be brought back as needed
- Chris F. will participate archival-related preconference workshop at C4L - “archival discovery and use”
Work Plans
Documentation Subgroup:
- main task is to review technical documentation (basecamp, etc)
-- much of basecamp issues are legacy (except migration)
-- what is division of labor btwn. documentation and other groups - there will be overlap
-- general review by next meeting, including dealing with overlap issue
Migration Subgroup:
Main tasks are:
1. identifying outstanding migration issues and enhancements,
2. review migration documentation
-- migration guidelines doc is special, because it is user doc, but fairly technical - the TAC migration subgroup will therefore probably have responsibility for this
-- there is migration documentation in basecamp that needs to be reviewed - the group will get access to this soon.
-- Brad may be putting migration documentation into a new system (?name?). How does this affect the migration group?
3. Review status of legacy finding aid and marc record import - issues and documentation
*Tracking for Migration came up as a major issue during this meeting:
- issues come in on the list; if a bug they get put into Pivotal
- no formal tracking
- we should address migration issue tracking, right now there are 4 places things are tracked, need to centralize
-There are 2 categories of issues, which complicates tracking:
-- AT client migration code
- -import code on the AS side
-Migration group will assist in consolidating issue tracking once Brad is consulted and the group hears something
Architecture Subgroup:
Tasks will be divided into (1) Back-end API and (2) Plugin Analysis
Will take 6 months to review code and figure out how to be most effective
-- the group will come up with a way to monitor progress in a more granular fashion (before the 6 months)
Committer Oversight Subgroup:
two main areas of focus:
1) Clarifying how new developers get set up and contribute code
-Documenting the workflow for code contribution, pull requests, code review.
2) reviewing tickets
- mostly a contributive role, the bulk of work will be by UAC
---
Wrapup:
All groups should come up with a timeframe in the next couple weeks regarding their current tasks
Next call will contain a review of c4l, as well as an update from the subgroups
More formal group documentation will go on confluence (we will hear about login credentials); we can continue to use googledocs for notes and less formal documentation.