Versions Compared

Old Version 5

changes.mady.by.user Jenn Colt

Saved on

compared with

New Version Current

changes.mady.by.user Maccabee Levine

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: meeting notes

...

Attendees 


Discussion items

TimeItemWhoNotes
1 minScribeAll
Maccabee Levine is next, followed by Craig McNally

Reminder:  Please copy/paste the Zoom chat into the notes.  If you miss it, this is saved along with the meeting recording, but having it here has benefits.

5-10 minLiaison Updates

Maccabee Levine

Tod Olson

Jakub Skoczen

Craig McNally

Jenn Colt 

  • CC: Maccabee Levine
    • Elections: one day left
    • MOU: CC wants to follow up (sometimes) after TC approval of new modules, how do they know.  I shared the Jira project, possible alerts.  They will raise with co-chairs.
    • Application Formalization: they want to be in the loop more.  Mike Gorrell will join and serve as CC liaison.
  • PC: Tod Olson
  • RMS Group: Jakub Skoczen 
    • Jakub not present
  • Security Team: Craig McNally 
    • Craig not present
  • Tri-council Application Formalization: Jenn Colt  
    • No meeting last week or update. Meet again this week.
1 minUpcoming MeetingsAll
  •   - Dedicated Discussion - RFC RetrospectivePR Templates
    • Jeremy Huff Worth a Wednesday discussion.
      • Craig McNally We did discuss and decided to leave it up to individual teams.  Templates lead to misleading information.  We can make a decision (DL) but people will continue asking.
      • Jeremy Huff If there is a decision log, we can supply a link.
      • Maccabee Levine We invited developers to raise issues and this was one of them, so it's to our credibility that we respond.
      • Tod Olson Part of the templates discussion was having some amount of consistency.  Where are the places we need consistency to remove friction, as opposed to causing it?
      • Marc Johnson Templates being part of a consistent development process; we abandoned that a long time ago, different teams wanted to work different ways.  Teams ignored it; different opinions on why.  Some decisions we don't have enough documentation of; some disagreement on which should be centralized or not.   Should delineate between narrow PR template topic and broader consistency values topic.
      • Jeremy Huff How does TC want to deal with the larger question?  Not in one Wednesday meeting.
  •   - Regular TC Meeting - New Co-Chair
  •   - Dedicated Discussion - Topic TBD RFC Retrospective
  •   - Regular TC Meeting - New Co-Chair
  •   - Dedicated Discussion - Topic TBD
10 -15 minTCR Board ReviewAll
  • We will establish a TCR Round Robin to support the TCs module evaluation responsibilities.
    • Jeremy Huff Simple iterating through the TC members list as we do with scribe?  Outside reviewers also valuable.
    • Marc Johnson Rota will change after TC election, may want to set in new FY.  Also is everyone able / comfortable of doing an eval, or do we need pairs?
    • Maccabee Levine Membership will change in two people.  Agree some people may need help to do a review, but don't think you need to be a developer.  Pairs help reasonable.
    • Jeremy Huff Agree vast majority of criteria can be verified without developer expertise.
    • Florian Gleixner If you don't try, you don't know if you can do it.  It's less digging into the code and mostly liaising with the developers.  Think everyone on the TC can do them.
    • Jenn Colt I did one for the first time a few months ago.  Worthwhile for everyone to get the experience, everyone on TC should understand it.  Just be clear what is expected from the reviewer.
    • Jeremy Huff Ingolf was a lot more thorough than I was, running the module.  Different people bring different strengths to the eval.
    • Owen Stephens As an evaluee, TC members had good technical understanding.  Don't know if that's required but experience would have been different.
    • Jeremy Huff No problem with an evaluator reaching out to people for help with one aspect of it.
    • Maccabee Levine Practically can either do a rota if we think they will be mostly solo reviews, or a table with "last review date" if we think it will be mostly pairs.
    • Jeremy Huff Let's vote to try the round-robin method, modelled after scribe approach for some period of time.  Allows for skipping over someone unable to perform duties, but would be put into rotation as soon as possible.  Can grow into more complicated method if needed.  
      • Quorum voted in favor.
    • Florian Gleixner will do mod-reading-room, Jenn Colt will do ui-reading-room (when she is back from vacation).
5 min

Technical Council Sub-Groups Updates

All

(ran out of time)

1 minRFCs

All

(ran out of time)

5 - 10 minDeveloper Advocate UpdatePatrick Pace

Activities for the month, what's next, challenges.

  • April was mostly getting acclimated to FOLIO.
  • Reviewed FOLIO resources, "things that could be better", attending TC and developer documentation subgroup meetings, Jeremy meetings.
  • Not much one-on-one help this month, still reviewing Slack.  Engaged in what I can.
  • 6m contract with possibility of renewal, so focus to change things that will last beyond me.  I.e. documentation subgroup, how does it continue.
  • Created service board, working with Peter Murray on a permissions issue.
  • Created a developer advocacy confluence space.
  • patrick@folio.org email address now.
  • Developing thoughts on a developer mentorship program, did a survey, just posted Friday but no responses yet.
  • Monthly reports: /wiki/spaces/DA/pages/290947082
  • Next
    • Make service management board available
    • Developer documentation updates
    • Touring environments with developers
  • Challenges
    • Summer
1 minAction Items

Jeremy Huff


1 minDecision LogAll


Time Permitting

Officially Supported Technologies (OST)

All
NAZoom Chat


...