You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 6
Next »
Date
Monday, November 21
2:00 - 3:00 PM ET, 1:00 - 2:00 PM CT, 12:00 - 1:00 PM MT, 11:00 PM - 12:00 PM PT
Call-in info is:
Number: 888-354-0094
Access code: 731627
Notetaker: Esmé Cowles (Unlicensed)
Attendees:
Not able to attend:
Goals:
- Update from sub-teams, in particular on 2016 - 2017 workplans
- Two discussion topics:
- Request to re-think Instance types
- Thoughts on a potential by-law change?
- Update from Program Manager
Agenda items:
Time | Item | Who | Notes |
5 min | Roll call and actions from previous meetings | All | Actions: - All TAC members - encouraged to review the draft FAQ document and share your thoughts. Team is still keen for feedback particularly on platform.
- Sally Vermaaten (Unlicensed) to move 15/16 TAC files to 'historical files' section of wiki
- Subteams to try to complete workplans by Nov meeting so others on TAC can review if interested.
|
5 min | Thanks to TAC members for recent listserv contributions: - Listserv
- Code, documentation and bug reporting
| | |
5 min | Program update | |
|
15 min | Committer Oversight sub-team update |
|
|
Technical documentation sub-team update | |
|
Dev Prioritization sub-team update | |
|
Testing sub-team update | |
|
Migration sub-team update | |
|
Integrations sub-team update | |
|
15 min | 3 discussion questions: - Request to re-think Instance types
- Should we propose a by-law change?
- Performance when working with AOs with large numbers of direct children
| | Three discussion questions:
- Request to re-think Instance types
- We've received a request to re-think how ArchivesSpace handles Instance Types. The rationale is that Instance Types are semantically meaningless (e.g. exports as a top container "label") but potentially misleads users into thinking this it's a place to record format/genre information.
- Would any sub-teams have interest in looking into this issue further?
- Should we propose a by-law change?
The Technical Advisory Council also partners and with other community members to help with TAC initiatives. The roles of these other contributors include: - Invited affiliate contributors - External contributor with expertise relevant to particular TAC topic and/or task. These members are asked join a particular TAC sub-team for a period of time to help with a specific task, project or work area. These members are added by the Technical Advisory Council Chair and relevant subteam Lead.
- Program liaison - ArchivesSpace Program staff who work is funded by Membership Fees are encouraged to collaborate with the Councils and join relevant sub-team meetings as a means of ensuring the work of the Program, Council, and community align and are mutually supportive and beneficial.
- defining process for handling out of cycle vacancies (in Article V Section 2)
- Also potentially the bullet in Article V Section 4 that calls out the responsibility of TAC to "review functional enhancements and priorities identified by the Users’ Advisory Council." → but maybe we leave this one for further reflection
- Listserv discussion re. application performance when working with AOs with large numbers of direct children
|
| Next meeting time |
| Jan 16, 2017 - Patrick Galligan (Unlicensed) on deck to take notes. |