CCMWG - 06/18/18

Attending

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

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

Participants

• Trey Pendragon  (Princeton University Library)
  
• bess  (Data Curation Experts)
  
• Noah Botimer (University of Michigan Library)
  
• Benjamin Armintor  (Columbia University Libraries)
• James Griffin (Princeton University Library)
  

Agenda

• Review the Maintenance Waffle Board
  
  • https://waffle.io/samvera-labs/maintenance
    
    • Colors for issues on the board?
  • https://docs.google.com/spreadsheets/d/1IICaXpwzxSFPB_G7k4jzUiPMTmT5OulUQKtF0jSYqvM/edit#gid=0
• Deprecating Outstanding Projects
  • om
  • jetty-wrapper
  • hydra-jetty
• Deprecating Samvera Projects without Maintenance Plans
  
  • Sufia
  • Curation Concerns
• Revisiting the Scheduling of Sprints
  • Sprint Availability
• Additional Agenda Items?

Notes

• Action Item:
• Provide permissions for other users to edit the Confluence Pages for Samvera
• Which kind of issues should be made
  • Botimer
    • ActiveFedora
      • License is there, Apache 2
      • Copyright statement from 2011 for Stanford and MediaShelf
      • Do we want to continue to update the dates on the copyrights?
      • No proper legal entity to hold the IP
      • One retains copyright to the code itself (not transferred with Apache for foundations)
      • Community-distributed copyright is held by all new code
  • Pendragon
    • Create a ticket with the maintenance label
    • Our responsibility is finished if product owner needs to determine if the license statement is accurate
  • Botimer
    • This group might be expected to resolve licensing questions
  • Pendragon
    • That may be more appropriate for Steering to determine
  • Botimer
    • Is it worth creating an issue in active_fedora?
  • Pendragon
    • Only go as far as asking the product owners if it is okay
  • Armintor
    • Samvera is not an organization which can hold rights
    • Governance WG: Do CLAs have an obligation regarding rights statements?
      • Are the licenses in line with the contributor CLAs?
    • E-mailed Steering
  • Gemnasium
    • Does not exist anymore
    • ActiveFedora has a badge for this service
    • Should we explore GitLab auditing?
    • Create an issue for that?
    • Pendragon
      • Created a ticket to remove it
      • GitHub audits for free (it is no longer necessary)
    • Create an issue to remove it
  • Documentation links to Dive into Hydra
    • Should suffice in place of installation instructions
  • Documentation point 11
    • Contributors...have they all signed the CLAs?
    • Is this WG responsible for doing those checks?
  • Pendragon
    • Contributor list is public
    • Always check the CLA...it's been socially enforced
  • Botimer
    • There is a CLA bot for GitHub
    • Might be at the level of individual repositories
  • Sadler had to leave at 03:17 EDT
  • If someone did not have permission, we should contact that contributor privately
  • We should still check it