Skip to content

Roadmap Meeting September 29th 2017 11:30 am AST

Jump to bottom Edit New page
kim pham edited this page Oct 4, 2017 · 7 revisions
  • Chair: Kim Pham
  • Notes: Mark Baggett

Per: Schedule

  • Attending:
    • Danny Lamb
    • David Keiser-Clark
    • Melissa Anez
    • Mark Jordan
    • Mark Baggett
    • Kim Pham
    • Kirsta Stapelfeldt
    • Diego Pino
    • Bryan Brown
    • Anna St. Onge
    • Rosie Le Faive
    • Carrel Jackimiek

Agenda

Old Business

New Business

Interest Group Updates

  • Documentation IG (Melissa)
  • Dev Ops (Gavin)
  • Metadata IG (Rosie)
  • IR interest group (Bryan)
  • Security Interest Group (Rosie)
  • Oral Histories Interest Group (Kim)
  • UI Interest Group (Rosie?)

CLAW

Islandora Camps

Round Table

Next meeting October 13th

  • Chair: Mark Baggett
  • Notes: Donald Moses

Minutes

  • Islandora 7.x-1.110 Update
    • Had a short blocker that's been addressed. P.R will be merged today.
    • Machine will be released Tuesday
    • Kim proposed a testing sheet that testers will be using.
  • ISLE Updates
  • TAG
    • It's Underway
    • Here is a link to the Terms of Reference
    • Membership
      • Jared
      • Will
      • Bryan * Rosie * Derek * Jon
    • Initial meeting hasn't happened yet
    • Danny will be blasting out stuff to the list to get people organized.
    • Meeting notes will go to the same place the Coordinating Committee's notes will go.
  • Islandora Organization Chart
    • Have a couple of drafts to look at
    • Complex
    • Mark Jordan: Suggestion: If it's not direct, use a dotted line to represent.
    • Committers don't have a direct
    • Rights and responsibilities of committers are spelled out here.
    • This chart is for people inside the community to understand who to talk to, what mechanisms can they take advantage of. Also for outsiders to understand how things are structued, how decisions are made, how work gets done.
    • If you can't draw a line between 2 boxes on chart, why can't we. It's a useful exercise.
    • Simple chart includes only direct relationship, but it's too simple. It should minimally include committers so people understand how code gets written and bugs get fixed.
    • Kirsta: I think a network with a description of the modes of interaction (similar to the current "Advises" arrow) would be more descriptiveSent on:10:45 amFrom:Kirsta Stapelfeldt More like a "communication" chart
    • Rosie: Always seemed that Melissa played a big role in the coordinating committee. It's not explicitly in policy documents, but maybe the chart should have a simliar drawing as Danny and TAG. Maybe not exacly.
    • Melissa welcomes others to take a stab at this but is happy to readdress.
    • Mark: Do people think dotted lines are a bad idea for committers?
      • Not off the table
      • Collapse both boxes
        • 1 box for both 7.x and CLAW committers
      • Think showing relationships (dotted lines) between committers and TAG and corrdinating committee and Danny will better express how things get done.
    • Suggestion: Change complex chart should go side to side.
      • Community is why we do this.
      • Committers write the code.
      • Some people pay more or contribute more to take care of the garden.
      • Turn on side or upside down is better.
      • A more community focused picture.
    • Suggestion: Put the whole chart inside a bubble called community
      • Coordinating Committee still controls LSAP
      • Maybe codebase should be on this chart
        • Mark J.: Don't agree. About community around a code base.
    • Suggestion: Call out terms of reference without adding more to chart
    • Suggestion: Add code base as a bubble
    • There will be a legend. Haven't had the time.
    • Suggestion: Call the code software.
      • Would like to see where the software fits in this chart.
    • Coordinating committee still has a say in the software. Committers most directly contribute to it. Tech lead can make some big decisions. TAG doesn't make direct decisions. It recommends or advises. If a question is asked, TAG will respond.
      • Danny: i get asked to make a decision. some are simple and just need an answer. some are complex and can't please everyone. so TAG is there to make sure the cross section of prominent members is consulted before making a decision, because someone's going be cranky no matter what I decide.
      • Melissa: The TAG, is intended and so far as it’s being treated by a few community groups, is a place to kick those technical discussions that can/have gone in circles without decisions. It doesn’t make decisions, but it can hopefully hone the conversation down and focus on a solid recommendation.
      • TAG advises Danny, reports to Board of Directors, but Danny makes decision.
      • Coordinating approves LSAPs, not TAG.
        • Melissa: The TAG can make strong recommendations. So can Danny. But the LSAP decision belongs to this group.
    • Diego: concerned that complexity can affect momentum.
    • Who asked for chart?
      • Diego, but community and people interested in the community needs this.
    • David: Would it help to add a dotted line to Danny from coordinating committee?
    • Carrel:
      • Why does the board want to hear from both TAG and Tech Lead?
        • Tech Lead because they report to the board.
        • Wanted a group of people to advise Danny when he needs it.
          • When should we stop reporting PHP 5.3?
        • Some decisions are easy to make, some are not.
    • Diego: is TAG from wide community? or member institutions?
      • Melissa, any member institution, elected by the board.
    • Melissa: I’d like to revisit all of this in a year or so, too. See how the TAG ends up fitting into the community processes in practice, and re-evaluate our documentation and policies to make sure we’re doing what makes sense when we have some experience.
    • Melissa: We need more time to work on this, review, and reflect, and further discuss so we put forward the best chart that we can.
    • Melissa: Would like to have some suggestions for homework brought forward.
    • Melissa: We might also need a box for because they have voting authority as wel.
    • Kirsta: Try to put the most important part in the middle
    • Diego: having doubts and having space to speak about this speaks good about our community
    • Rosie: what is the connection between Melissa and the coordinating committee.
      • In practice, Melissa is on the committee.
      • Not sure it's explicit on terms of reference.
      • Melissa: In terms of the chart.. I’m a member, but I also consult this group on things relating to my direct duties, such as camp locations.
    • David: adding links would help people be able to locate the Terms of Reference that describe what these groups do.
    • Kirsta: Someone from the outside may not understand how TAG vs. Coordinating Committee
    • Mark J.: Important to note that you can get on coordinating committee by paying money. Must be elected to TAG.
    • Diego: maybe a circular chart (a graph) with distances to board of directors (at center) to define the organizational structure could help define it? . And then pie like background colors that define “community affairs”, “tech decisions”, and there “topics == colors” could be overlapped..etc!
    • Mark J: Are there other ways to indicate the importance of Coordinating Committee.
    • Kim: Do we want feedback now or table until next roadmap?
  • Code of Conduct
    • DuraSpace's new one is heavily modeled after Islandora's.
    • They make a point that if you make a complaint, it states who will see them.
    • Melissa: proposes that we add "employees of the Islandora Foundation" to who is monitoring complaints.
    • David: Need to update "Roadmap Committee" references in CoC
  • Interest Group Updates
    • Documentation Interest Group
    • DevOps:
      • CLAW install sprint updates
      • Reviewed GitHub Issue Queue
      • Group project reivew
      • ISLE update
      • Notes
    • Metadata:
      • Exploring more complex graph
      • Dcterms
    • IR:
    • Security
      • Nothing to Report
    • Oral Histories
      • Nothing to Report
    • UI
      • Nothing to Report
  • CLAW
    • Been very active last few weeks
    • Activity has been around wrapping up things from Ansible install sprint.
    • 1 thing left and we'll have Ansible playbooks for CLAW install for 1 server.
    • Targeting early November for next Sprint.
      • RedHat based or multiple servers.
    • Nat from UTSC has worked through a rough solution pack for videos
      • Paving the way for others to do the same for more simple ones.
      • Wrote great documentation too.
  • Next meeting
    • Mark B. - Chair
    • Donald - Notes
  • Asynchronous Round Table:

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