Skip to content

Roadmap Meeting March 7 2014 2pm AST

Jump to bottom Edit New page
manez edited this page Mar 7, 2014 · 20 revisions
  • Chair: Donald Moses
  • Note taking: Melissa Anez

Per: https://docs.google.com/document/d/1htjJ_HjZ9r8iv3oIGJ2vdAJwtd4-YAaIRoocvZhcIjM/edit#heading=h.g1pxhux2j7cv

  • Attending: Donald Moses, Melissa Anez, Paul Pound, Greg Colati, Peter Murray, Nigel Banks, Nick Ruest, Kirsta Stapelfeldt, David Wilcox
  • Apologies: Mark Leggott

Old Business

  • 7.x-1.3 Release -

    • Draft responsibilities document - updated to show status in release. Nick has added a column tracking release branches. Still a few modules to go through LSAP. MJ Suhonos will work with Nick to update his Islandora Chef scripts to create a release VM/RC VMs for testing (yay!).
    • Draft list of modules
    • Concern from Committers about how to frame Islandora Sync - it is very different from other Islandora modules.
      • Should be handled via documentation and communication to make sure that users know how it varies from the standard behaviour of Islandora modules. Blog update from Kristian may also help to communicate what Sync is and is not.
    • First Release Team planning meeting was March 6th - tentative timeline in place: code freeze March 17th; release for April 24th.

  • New software offer:

New Business

  • New Software process - Fork or Transfer?

    • Consensus from Roadmap and from other discussions in the community (dev list) is that transfer is the preference. We can still fork in cases where the owner objects to transfer, but transfer should be our standard. It moves GitHub issues over.
    • We will not go back and transfer previous modules, but will apply this standard going forward

  • Committers Calls - coverage during Melissa's leave

    • Kirsta, Peter, Nick, Donald, Paul, and Nigel are willing to rotate the duty between them.

  • Islandora/Fedora 4 Alpha Project

    • UPEI/dgi/IF groups met last Friday to discuss Islandora's future with Fedora 4.
    • Upgrade paths are a major question - how to move from 3 to 4? Migration tool is not slated for 4.0 release; projection/federation is the method for 4.0, which is aimed at greenfield repos, not upgrades.
    • Fedora 4 beta before OR2014; 4.0 in time for OR2014
    • For this group, upgrade is more relevant. May be available in 4.1 release.
    • Possible approach for Islandora: upgrade Tuque (new project called "Trilby), which will allow Islandora 7 to sit on Fedora 4. May only be useable on a few solution packs as a demo, but intended as POC for OR2014.
    • Write up a blog/communication to explain our position/challenges/caveats regarding Fedora 4. Kirsta will start up a stub document to share with Roadmap

  • Discussion: Documentation to Github

    • Nick proposes moving docs to GitHub. Documentation is difficult to follow and becoming contentious on the lists. It was good for 7.x release, but it's falling behind. Islandora wiki already has a bunch of docs - big overarching confluence content could be moved there.
    • Pros:
      • Easier for people to edit, brings more people into GitHub
      • Faster
    • Cons:
    • Melissa will put the idea to the community for discussion.

  • Discussion: Tickets/Issues to Github

    • Should consider our approach to how to encourage people to make tickets. Maybe a FAQ for new users?
    • Similar issues to the documentation move re ease of account creation, etc.
      • Pros
        • If we move docs from Git, we're severing the link between confluence and JIRA (accounts are shared, automated release notes)
      • Cons

  • Discussion: Islandora Interest Groups Proposal - To be discussed in more depth next time.

You may be looking for the islandora-community wiki · new to islandora? · community calendar · interest groups

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

Clone this wiki locally