2017-01-31 Meeting Notes

2017-01-31 Meeting Notes

Date

January 31

Call-in Number

1-888-354-0094
Access code is 731627#

Attendees

  • @Mark Custer (Unlicensed)

  • @Gordon Daines (Unlicensed)

  • @Jason Loeffler (Unlicensed)

  • @Kari S. (Unlicensed)

  • @Suzanne Stasiulatis (Unlicensed)

  • @Lydia Tang (Unlicensed)

  • @Sally Vermaaten (Unlicensed)

  • @Christine Di Bella (Lyrasis) and/or

  • @Laney McGlohon (Unlicensed) (Lyrasis)

Discussion Items

Time

Item

Who

Notes

Time

Item

Who

Notes

1

 

Roll Call

Gordon Daines

Gordon Daines is the scheduled notetaker

2

5m

Review of survey results

All

 

3

10m

Update on HM work-in-progress, incl. timeline for next release(s)

Lyrasis rep

HM has delivered code for 1.5.3 release candidate. Expect to announce availability in the next day or two. Anticipated release the week of February 6th.

Next major release is 1.6 and is due the end of March.

4

5m

JIRA board workflow. Which board will HM use to review queue?

All

There are three boards circulating right now. It would be beneficial to have everyone working off the same board.

https://archivesspace.atlassian.net/secure/RapidBoard.jspa?rapidView=1

https://archivesspace.atlassian.net/secure/RapidBoard.jspa?rapidView=11

https://archivesspace.atlassian.net/secure/RapidBoard.jspa?rapidView=4&view=planning.nodetail

The board with #11 is the one that the Development Prioritization group is working with. The other two were created by Laney and Christine for their use.

5

40m

Discussion about role of the development prioritization group

All

Consensus that the role of the Development Prioritization subteam and its associated workflows need to be clarified. Had discussion about the best way to utilize the boards.

Talked about the possibilities of creating one channel for reporting issues to JIRA. It was suggested that a connection should be made between GitHub and JIRA (so that Github issues could flow into Jira, to be prioritized there).

Action Items

  1. Have a small group work to outline procedures and processes for the development prioritization group.

  2. Draft guidance for contributing bugs, features, etc. to JIRA.

  3. Share procedures and processes with the two Advisory Councils.

6

 

Q&A

All

  • Time permitting!

Notes

 

Action Items