Summer 2020 Community Sprint Retrospective Meeting

Owned by James Griffin
Last updated: Jun 12, 2020
2 min read

Date: 06/12/20

Time: 12:00 PDT/03:00 EDT -01:00PDT/04:00EDT

Zoom: https://princeton.zoom.us/j/7739591625


Participants


Agenda


Notes

  • James needs to evaluate process and documentation
    • Also samvera.github.io needs to be updated
  • Leading in pairing sessions was extremely valuable
    • This should be given a documented structure
    • "Let's do a release"
    • "How do you upgrade to the latest version of Rails?"
    • Mentorship component is going to assist in inviting other community members to participate
      • There are many points relating to permissions and privileges
        • Working with RubyGems and Jeremy's script
        • GitHub Organization admin privileges which need to be evaluated
        • Rachel and Kait could not interact with Issues properly
      • James needs to ensure that this is no longer the case
    • Proper documentation and consistency for Ruby Gem releases
      • Perhaps this should be a requirement for a Core Component?
      • James will review Bess' documentation
        • Release method incorporates autogenerating a changelog
        • This would be a huge improvement
        • A couple of projects were doing this, but it has been consistent
          • Formatting should be consistent
      • James will try and use the Tech Call
        • Tech Call, followed by a samvera-tech Google Group message, and then the next CCMWG Meeting
      • 80-90% complete with release notes, so much of the labor has already been invested
      • This, too, will ensure that it will be easier to recruit new people into the WG
      • There is always going to be specialized component maintenance, but there is going to need to be security audits, onboarding with a focus upon releases
      • Documented, repeatable process would be extremely valuable for onboarding Product Owners
        • Otherwise, POs don't necessarily have the guidance or support to address this
        • Watching for developers who may know the project quite well, but they aren't always available
        • Releasing on behalf of developers should be straightforward, and Product Owners should be empowered to release without any technical assistance
  • Future Sprints
    • Definitely a desire in looking to contribute to another community sprint
    • The components are smaller and actionable, but we want to ensure that this remains the case; we don't want any items to be too large for 5 days (or less)
    • James will e-mail everyone with a request for monthly availability
      • James' preference would be for one more 5 day sprint before Samvera Connect
  • Final Thoughts and Questions
    • Sense that there was more traction
    • In the past, a very small group of contributors which were trying to fix difficult bugs
      • This sprint was much more focused upon defining an onboarding experience
      • Maintenance Sprint Script
        • Generate a set of tickets
          • Security updates? 
          • Upgraded to the latest style?
          • Checklist for each sprint
          • Generate the issues at the beginning of each sprint, and have someone self-assign for each component
        • Maybe extending or using https://github.com/samvera-labs/huborg in order to provide for this?
  • Meeting adjourned at 12:57 PDT/15:57 EDT