Date
9-10:30am PT / 12-1:30pm ET
Call-info
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/619789499
Or iPhone one-tap: US: +16468769923 (619789499#) or +16699006833 (619789499#)
Or Telephone:
Dial(for higher quality, dial a number based on your current location):
US: +1 6468769923 or +1 6699006833 or +1 4086380968
Meeting ID: 619 789 499
International numbers available: https://zoom.us/zoomconference?m=lfJNhr4XU-I8p7oRrXXwebNlh57Ti7kq
Participants
Goals
Prioritize new and awaiting more info tickets
Links
Kanban boards:
New bug reports: https://archivesspace.atlassian.net/secure/RapidBoard.jspa?rapidView=15
New feature requests: https://archivesspace.atlassian.net/secure/RapidBoard.jspa?rapidView=16
Link to ArchivesSpace sandbox: http://test.archivesspace.org/
Discussion topics
Item | Presenter | Tickets | Notes | Decision |
---|---|---|---|---|
Roll call and announcements | ||||
Review of initial survey results | Around 120 responses. Strongest responses for:
Lydia planning to create a summarizing blog post for ArchivesSpace in January/February | |||
Ticket tags | “Metadata” tag (Link to board) conflates tickets that deal with metadata with tickets where we want MS sub-team to weigh in. Could we create a new tag for the sub-team? Does Usability have a similar situation? Another idea is to add another column to the Kanban boards for “For Subteam Review” where someone from Dev. Pri. comments on the ticket which subteam needs to view it, and once the ticket is ready for Dev. Pri. again, the subteam person comments on the ticket and the original Dev. Pri. person adds it to the next agenda. | |||
Tickets | Ticket theme for today’s meeting: Mostly bug tickets, with “older” Awaiting More Info feature request tickets | |||
| ||||
| ||||
| ||||
| ||||
|