Call in details:

• Time: 2:00 PM EDT (UTC -4)
• Location:  https://duraspace.zoom.us/my/fedora
• IRC:
  
  • tech:  Slack Channel
  • Slack sign-up http://slack.fcrepo.org/

Attendees

• Danny Bernstein
• Andrew Woods 
• Ben Pennell
• Jared Whiklo 
• Peter Eichman   
• Mohamed Mohideen Abdul Rasheed  
• Michael Durbin  
• Aaron Birkland  

Resources:

• 2018 Fall Sprints
• Kanban Board
• Release Testing

Discussion

1. Where do we stand right now
2. What will happen by the end of the day
3. What if anything is planning for next week
4. Retrospective: What worked well?  What didn't?
5. Open discussion

Minutes

1. what have we been working on
   1. Peter: WebAC code
   2. Jared: hates JMS; how to send/receive messages at same time
   3. Ben: coding
   4. Andrew: no specific ticket work
   5. Mohamed: WebAC code
   6. Mike: no time to work on anything this week
   7. Danny: working on PRs for CTS, versions UI (FCREPO-2730)
2. what can we finish today
   1. Peter: code review, especially CTS tickets
   2. Jared: intend to set up framework for JMS testing, put on branch
   3. Ben: already finished
   4. Andrew: not in critical path
   5. Mohamed: HTML UI download button
   6. Mike: nothing by end of day
   7. Danny: remaining CTS PRs in scope for 5.0.0
3. what are we doing next week
   1. Peter: not available
   2. Jared: not available
   3. Ben: a little time, can help with review
   4. Andrew: working on VIVO next week, then back to Fedora for sprint 2
   5. Mohamed: not available
   6. Mike: will attend committers call; not much additional time
   7. Danny: will pick up JMS testing work, versions UI
4. FCREPO-2848: just needs some cleanup
5. retrospective:
   1. Peter: productive sprint
   2. Jared: we got a lot done, sprint ran as expected
   3. Ben: productive sprint, some times was unclear because not working on major group effort areas
   4. Andrew: "there is a machine that has been created", let's not become complacent in our successes
   5. Mohamed: productive sprint, needed some ramp-up time first week but feel second sprint will be even more productive
   6. Danny: lots of great work done, good communication; early mornings have been challenging due to school schedule
6. how can we improve sprints?
   1. better job this time in having a steady stream of activities and tickets to keep people from getting blocked
   2. increase upfront organization of work upfront
   3. Danny will take this as an action
7. what are our goals for next sprint?
   1. objective: release candidate by end of sprint 2
   2. what is the RC policy?
      1. wait for all known bugs to be resolved, then issue RC to community
   3. tag RC at end of sprint
      1. spend any extra sprint time doing testing and documentation
      2. we are close
      3. "get it out to the community as soon as possible, but no sooner"; get different eyeballs on it

Notes: 

1. Once the API Alignment EPIC is done, there is be all the other tickets available at

   type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.