Attendees

Steering Group Members

Dean B. Krafft, Julia Trimmer,  Andi Ogier,  Lauren Gala, Eric Meeks,  Alex Viggio, Dong Joon (DJ) Lee,  Mark Newton, Paul Albert (star)

(star)= note taker

Project Staff

debra hanken kurtz, Andrew Woods

Regrets

 Mike Conlon

Connection Information

Join from PC, Mac, Linux, iOS or Android: 

https://duraspace.zoom.us/my/vivo1

(New call-in numbers were corrected on 5/10/2018)

Or iPhone one-tap :

    US: +16468769923,,9358074182#  or +16699006833,,9358074182# 

Or Telephone:

    Dial(for higher quality, dial a number based on your current location): 

        US: +1 646 876 9923  or +1 669 900 6833  or +1 408 638 0968  or +1 408 638 0986  or +1 646 558 8665 

    Meeting ID: 935 807 4182

    International numbers available: https://zoom.us/u/cex8G1kjQ

Agenda and notes

  1. Draft Sprint Schedule — Andrew  (See https://wiki.duraspace.org/pages/viewpage.action?pageId=96997619)
    1. Andrew: it's helpful to have dates on the calendar for institutions to commit resources
    2. There is some reluctance about having all of these sprints.
    3. Each sprint represents 2 weeks of work and another week of cleanup.
    4. Andrew: I could commit for one sprint during 2018 and another during 2019.
    5. Dean: I like the idea of limiting the number of sprints to quarterly in the hopes that it's less chaotic.
    6. Dean: I would send out the possible dates to the Developer list and getting feedback.
    7. DJ and Andi: agree
    8. Alex: I like the idea of not putting the sprint dates too far into the future.
  2. Conference update – Paul, Eric
    1. We have 21-22 presentations, a couple of panels, a couple keynotes, and a couple of competing schedules.
    2. Two options:
      1. Long and skinny - Two presentations at a time, and Thursday afternoon we have an unconference on the side competing with the sessions. Friday we continue to do unconference or we shut it off.
      2. Short and fat - Three track option where we do three presentations at a time and then we have a couple of hours of dedicated unconference. Then we go back to dedicated session times.
    3. Dean: how do you propose to set up the unconference topic? Eric: Alex has been volunteered to explain this during a dedicated time.
    4. Dean: my vote would be to do the long skinny unconference. Let people choose. It feels like you could have a better have a better set of choices. 
    5. Mark: as a conference goer, I would be concerned about understanding.
    6. Eric: I think the long and skinny is better, because there's less likelihood of competing presentations.
    7. Andi: I prefer long and skinny. I prefer to move in and out of sessions.
    8. Alex: Mike said he wanted four slots for the ontology
    9. DJ: I'm leaning to long and skinny.
    10. Eric: long and skinny it is!
    11. Mark: will the program be published? Alex: yes - this will be done by this weekend. Email will go out on Tuesday.
  3. Leadership Group meeting processes:
    1. LG meetings are every 4 weeks.
    2. How do we help the group succeed?
    3. How should the meetings be run differently from the Steering meetings?
      1. Should we adopt the Fedora model? In that group topics are introduced at the SG and if there is “loose agreement,” then they add the issue to the LG agenda. The issue is proposed to the LG and everyone gives their reaction. Following the meeting, the question is asked via the email list. Everyone replies to the list with questions and/or votes as +1, 0 (no opinion) or -1 (veto which shuts down the vote).
      2. Andrew: it seems the chair would play a critical role in shaping the agenda. It's also important to share what's going on at your institution, what are your concerns, what's the cool stuff you're doing, etc.
      3. Julia: for Fedora, the chair meets with the tech lead ahead of meetings
      4. Dean: I think we should take this discussion to the Leadership Group and see what their feedback is.
      5. Mark: this seems fairly rushed.
    4. What should we propose for the first meeting of the new LG on May 25? Should we propose the following process, which is used by the Fedora group?
      1. Fedora elects new Leadership members in May and terms start July 1.
      2. Leadership elects new Steering members in September.
      3. The Steering members select (usually someone volunteers) a chair who serves for a year.
  4. Additions and walk-on items


\

  • No labels

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.