Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Mark: We know the tech will change over the time in which we'll be managing the content we have. If we present that we present this as static, it won't be good. Having a mature mechanism for change is a positive thing to put out there.

Next Meeting; Nov 27. 2018Julie: We will have a draft by the next meeting.

Mark: On Governance it was broken into smaller groups for drafting, we could take the same approach here with the whitepaper.

Everyone agrees that this is a good idea.

Mark will do current struggles section, Nabeela and Mark will draft out the community section. This will be next week; we could split off and do the same for the other sections.

Steve: Samvera 2019 roadmap still valid?

Julie: It should be more focused on the actual roadmap, and existing text there could be pulled into the products section.

Jen: We could change the heading.

Steve: What roadmap are we talking about specifically?

Julie: I'm only aware of the Hyrax one. We could build a table. The core components group does maintenance, having that fresh. Hyrax and Hyku are building it out... how do we present it?

Steve: Significant overlap in roadmap section between products represented and community sections.

Mark: Other than the interest groups and working groups, in the roadmap it feels like talking about this group being air traffic control, and our role coordinating and saying out loud: Avalon has a roadmap, Hyrax has a roadmap, core components has a maintenance mechanism. Giving people pointers to those things and saying it's a multi-threaded thing, but it doesn't mean that these things don't have roadmaps, but rather that each thing has its own roadmap which are connected to the others.

Steve: If we want to talk about that it's tied together and we can coordinate. The concern is that people don't read this as "Samvera Roadmap."

Julie: Give it a different header, just don't call it "Governance."

Ben: Hyrax has a roadmap and part of it includes Valkyrie. It would be appropriate for us to say, on the roadmap is some assurance that if you work in Avalon and Hyrax, you're not working with fundamentally different way to use your repository backend. As a community, our roadmap should suggest that the other solution bundles are using the same repository remediation. Saying simple "these products both have the same abstraction that they work from"

Steve: Samvera roadmap: and beyond! If folks could pull things out in the from beyond section, I'll have a better idea of what to include.

Julie: Partners vote has gone out on the roadmap council. We're assuming everyone will say yes.


To Dos:

  • Have a draft done by next meeting


Next Meeting; Dec 11 2018

Facilitator: Mark Bussey

Note taker: Steve Van Tuyl