Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

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


  • No labels