/
Committers Call 2013-07-01

Samvera Community Wiki

Committers Call 2013-07-01

Jun 16, 2017

Attendees

  • Moderator:  Mark Bussey (DCE)

  • Notetaker:  Jim Coble (Duke)

  • Adam Wead (RockHall)

  • Mike Stroming (Northwestern)

  • Adam Hallet (Northwestern)

  • Carolyn Cole (Penn State)

  • David Chandek-Stark (Duke)

  • Justin Coyne (DCE)

  • Drew Myers (WGBH)

Agenda

  1. Call for agenda items

  2. Code Acceptance Process

    1. Get a pull request 

    2. Check that the requester has a valid CLA at the  Samvera Licensed Contributors page

      1. YES: merge the pull request if it's sound

      2. NO: Ask the requester if they would be willing to Samvera Community Intellectual Property Licensing and Ownership to cover this and future contributions.

    3. Can the same person issuing the pull request perform the merge?
      Generally better if someone else takes a look and does the merge but, in exceptional cases (e.g., security issue or very minor change), okay for person submitting pull request to go ahead and do the merge.  Use good judgment and see if you can find someone to review the code change after the merge if not before.

  3. Issue 129: DatastreamColletions isn't experimental anymore.  It's for realz y'all.
    Done

  4. ActiveFedora 6.4, Hydra-Head 6.3 – last call for objections
    No objections.  Justin will release in next day or so.

  5. Should/can we release hydra 6 before OR?

    1. Should we just release the last RC, or make a new RC with up to date dependencies?
      Better to include the latest versions if feasible.  Justin will make a new RC with the newest ActiveFedora and HydraHead.  Mark will test running through the "Dive into Hydra" tutorial and, if all goes well, release it.  In preparation for Developer Workshop at OR next Monday afternoon, Mark will verify that the tutorial runs with both Rails 3.2 and 4.0.

  6. Hydra Archives

    1. Option #1 - git subtree - branches are sort of ugly, but keeps committer history: https://github.com/curationexperts/hydra-archive

    2. Option #2 - repos as branches -  branches still ugly?: https://github.com/curationexperts/hydra-archive-branch

    3. Option #3 - zip archives - no example - keeps full history - need to download and unzip to browse

    4. Do we need branches and/or tags?
      Consensus among call participants was that branches and tags need to be preserved and that option #3 (zip archives) is preferable.  Mark will refine the option descriptions and send out question to hydra-tech list.

  7. Next call: July 15 (no call on July 8 due to to OR)

    1. Moderator: Justin Coyne (DCE)

    2. Notetaker: Adam Wead (RockHall)

  8. If you're going to be at OR next Monday and can assist with the Monday workshops (morning and/or afternoon), that would be helpful.  Indicate your availability at Hydra Activities at OR13 .