Minutes 2014-06-25

Owned by Esmé Cowles (Unlicensed)
Last updated: Sept 25, 2014

Minutes of 06/25/2014 meeting

 

Attendees:

  • Esmé Cowles

  • Michael Giarlo

  • Katherine Kott

 

Agenda

  1. Licensing progress: ready for legal review?  What’s the process?

  2. Hackfest attendee outreach

  3. Brainstorming next steps

 

Discussion

  1. Licensing

    1. Katherine checked in with the board about licensing.  Ready for legal review once we’ve decided on what to ask about hackfest contributions.

    2. If we allow people to participate in hackfests, but require iCLAs/cCLAs to be signed, usable code may be in limbo if there is a delay.

    3. We should setup a separate github organization (archivespace-labs) to hold contributed code.  It would be a place to hold contributions until licensing issues are resolved.

    4. Look at Hydra community’s processes around navigating the boundary between the ArchivesSpace GitHub org and the new ArchivesSpace Labs GitHub org. The goal here is to provide an open space for hackfest participants to use without having to delve into the CLA process.  (“Contribute now, license later.”)  Process of moving from one to the other should be lightweight.

  2. Outreach

    1. We should get licensing issues resolved before doing serious outreach.

    2. Send email to the lists to solicit developer participation, rather than focusing on Code4Lib hackfest attendees.

  3. Brainstorming

    1. Next steps: revisit Work Plan and flesh out sections that have less detail into an overall draft set of recommendations for TAC/UAC around developer community

      1. Code style, testing, documentation -- these are guidelines that exist for a lot of other projects, and we can link to them instead of reinventing the wheel.

      2. Continuous integration is infrastructure that needs to be setup.

        1. We want CI to cover not just the core, but also contributed modules, plugins, labs, etc.

      3. Developer docs -- we should each setup ArchivesSpace locally and identify any issues with the documentation.

    2. Longer term: recruiting developers

      1. Hosting full-day or multiple-day hackfests with a higher expectation of actually writing code.

      2. Possibly in conjunction with a conference or other meeting to reduce travel costs.

      3. Possibly paying for shared housing (budget for stuff like this?)