Time/Place
- Friday, Sept 27, 2019
- Time: 9:30 am Eastern Daylight Time US (UTC-4)
- Audio/Video Conference Link: https://lyrasis.zoom.us/my/fedora
- Dial-in:
+1 408 638 0968
+1 646 876 9923
+1 669 900 6833
Meeting ID:
812 835 3771
- Dial-in:
Join fedora-project.slack.com on the "sprints" channel
Attendees
- Danny Bernstein
- Andrew Woods
- Ben Pennell
- Peter Eichman
- Jared Whiklo
- Mohamed Mohideen Abdul Rasheed
- Aaron Birkland
- Youn Noh
- Dan Field
- Jenny A'Brook
- Richard Williams
- Michal Dulinski
- Remigiusz Malessa
Agenda
- Note taker?
- Retrospective
- What worked
- What did you find challenging
- what you would change
- Outstanding tickets
- What can we present to the community vis-a-vis the sprint?
- Inter-sprint availability
- Wrap up
Notes
- What worked.
- Aaron Birkland
- Slack worked very well, being able to ping people.
- Creating and sharing examples with Gists and Google docs for fleshing out details.
- The Open questions page.
- Andrew Woods
- Lot of engagement, people felt open to talking about the various topics related to the sprint.
- Design effort of the first week
- Time zones are challenging, but having a point person locally being empowered to move the work forward without a bottleneck.
- Dan Field
- collaborative technologies, esp JIRA
- Discrete units of work ( ie migration utils project structure) made it clear what needed to be done.
- Mohamed Rashed
- Slack
- Pennell
- Documents for working out problems
- PR to demonstrate what something might look like
- Jared Whiklo
- I agree
- Bernstein
- Communication was good.
- Design effort was good.
- Aaron Birkland
- What did you find challenging
- Aaron Birkland Local schedule
- Andrew Woods
- Available time
- Didn't seem able to kick start documentation effort.
- Dan Field
- New codebase. Jumping into the deep-end.
- New technologies (OCFL, Github).
- Took longer to get up to speed then expected.
- Hard to do documentation until you have a tool to work with.
- Mohamed Rashed
- Getting up to speed with the plan.
- Took a bit to get pieces in place before really getting to flesh out tickets.
- Pennell
- Dropped the hole backend and trying to re-implement which brought up more and more design decisions
- Some text exchanges could get hard to follow.
- OCFL stuff seems a little up in the air.
- Jared Whiklo :
- it took a long time to understand the codebase and now we're revamping everything.
- Requires rethinking everything.
- Bernstein
- Lots of discussion/planning
- Getting the tickets to flow
- What would I change
- Pennell
- Do more implementation.
- Helpful to put stand-up messages in a separate Slack channel to avoid other messages getting buried.
- Pennell
Suggestions for improvement:
- Daily summaries of major discussions on slack so people can get the essence of the back and forth without having to read through all the slack communication.
- Separate channel for daily summaries of key conversations
- Separate channel for standups.
- When decisions are taken in face to face discussions of PRs, it is good to capture that decision in a PR comment at or around the related lines of code.
What to present to the community?
A one-page summary and 5 minute video highlighting what was accomplished. Andrew Woods and Danny Bernstein to collaborate on it with sound bites from the team members.