Skip to content

Roadmap Meeting April 28th 2017 11:30 am AST

Melissa Anez edited this page Apr 28, 2017 · 5 revisions
  • Chair: Rosie LeFaive (for Nick Ruest)
  • Notes: Melissa Anez (for Gabriela Mircea)

Per: Schedule

  • Attending: Mark Jordan, Diego Pino, Will Panting, Rosie LeFaive, Melissa Anez, Carell Jackimiek, Kirsta Stapelfeldt, Bryan Brown, Jonathan Green

Agenda

Old Business

New Business

Interest Group Updates

  • Documentation IG (Melissa)
  • Dev Ops (Gavin)
  • Metadata IG (Jennifer)
  • IR interest group (Bryan)
  • Security Interest Group (Rosie)

CLAW

Islandora Camps

  • Islandoracon
  • iCampEU

Round Table

Next meeting: May 12

  • Chair: Gabriela Mircea
  • Notes: Kirsta Stapelfeldt

Minutes

Old Business

  • Previous meeting notes
  • Islandora 7.x-1.9 release
    • Coming along well. One blocker appeared but has already been fixed.
    • Overall, very positive release experience. Great community support!
  • Islandora Slack
    • poll & community discussion
    • insufficient interest to move ahead on this for now. Leave it open for the future, but as things stand, we will not adopt Slack as something the IF runs.

New Business

  • Old wiki documentation - how far back should we maintain? Balance between helping those who haven't upgraded versus confusing people who stumble on the wrong versions. Each new version requires that the navigation bar in all old versions be updated manually.

    • Old versions go back a long way. This has value, but can be confusing (especially if hitting the docs from Google. Old versions show up frequently over new ones).
    • Don't want to remove the resource. May download old versions as PDF and store on islandora.ca. Need to consult with the community and the DIG about how to move ahead.
  • Proposed Islandora Labs Workflow

    • Roadmap asked Committers to draft a proposed workflow. General community was consulted via the listserv. This the the result.
    • Big change: allows maintainer to set rules, including who merges and how. Really opens up the field for experimentation. Barriers removed.
    • Means that things that want to go into Labs, need a contributing.md to define how development will work.
    • May need a pass through the existing modules to see what should be deprecated or promoted to core.
    • Diego suggests we give it a different name than "Maintainer" because that is a very different role in the core stack. We don't want to confuse expectations. Maybe "Lab Manager?"
    • Jon advocates for Maintainer as something that is easier to recognize for new people.
    • How do things move to core? If the community wants them, then people should speak up and nominate. If the decision comes to Roadmap, how do we decide? Follow existing LSAP and use judgement about the impact it would have on existing users.
    • Vote to adopt workflow: 2 +0, 9 +1
    • Timeline: aim to make transition and get Maintainers by next release.
    • Also look to review & cull module that should be deprecated. Danny will look into this post-conference.
  • Ubuntu Precise 12.04 LTS End of Life

    • Travis CI is deprecating the main box we use. We run our vagrant on 14. They will support for the next year or so, but we'll need to review our process and update.
    • If the group approves, Diego will open a JIRA ticket and starting picking away at this.
    • Jon has done this locally and it went pretty smoothly.
    • PHP 5.3.3 causes issues. We'll need to have a conversation about what we support. Committers Call has had long conversations about this, but we need a solid conclusion.
    • Danny will set up a conversation about this.
  • CoC for Islandoracon

    • Islandoracon Planning Committee is looking at how we'll handle the practicalities of the COC at the conference. Right now it's geared toward digital interactions. Face-to-face is more immediate. Can we allow anonymous reports during the conference? Without the kind of follow-up that we specify in our COC.
    • Planning Committee will wear ribbons to identify as people to approach with concerns or questions. Melissa will write up a plan for how we'll handle it, for the Roadmap to review.

Interest Group Updates

  • Documentation IG (Melissa)
  • Dev Ops (Gavin)
  • Metadata IG (Jennifer)
  • IR interest group (Bryan)
    • Discussions about what to call Scholar in CLAW. How it will change, perhaps become a "layer of ease" to use Islandora as an IR.
  • Security Interest Group (Rosie)

CLAW

  • CLAW development is coming along well. Most recent work is API-X integration. New microservices are getting wired up through API-X.
  • API specification effort has had a nudge from Fedora Leadership to get things going. List of editors has been stripped down to avoid too many cooks. Danny has been asked to become an editor for Islandora, giving us a stronger voice. The way the spec was shaping up was taking a long time and was having serious implications for the reference implementation.
  • Overall, mad dash to get Islandoracon demo in working order.

Islandora Camps

  • Islandoracon
  • iCampEU

Round Table

  • Mark Jordan: Making good progress with MIK, in prep for the workshop at Islandoracon. Diego: Would like folks to have a look at work the the IA Book Reader

⚠️ This wiki is an archive for past meeting notes. For current minutes as well as onboarding materials, click here.

Clone this wiki locally