Skip to end of banner
Go to start of banner

2021-12-01 Meeting notes

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Date

Attendees

Discussion items

TimeItemWhoNotes
1 minScribeAll

Marc Johnson is next in the list, followed by Steffen Köhler 

5 min

Review outstanding action itemsAll


5-10 minGoogle developer documentation style guideAll

From Jenn Colt :

Hi tech council - I would like to request that the inclusive documentation guidelines from the Google developer documentation style guide be followed as part of writing documentation on the FOLIO wiki. (link: https://developers.google.com/style/inclusive-documentation?hl=en )This style guide is what is used for the FOLIO docs site, but the FOLIO wiki is a very public, visible representation of the project and its values, and it is referenced much more than the docs site right now. Adding a link to the inclusive guidelines to the onboarding links could be a place to start.But the request is basically that these guidelines be a standard and that when documentation falls outside of these guidelines, requests for correction will be accepted and implemented. The assumption is that mistakes will be made but that these guidelines give us a goal to aim for. Thanks for your consideration. Let me know what else might need to be done to move this forward or to discuss it more.

Goal:  Make a formal decision on adopting the Google developer documentation style guide for all technical documentation in FOLIO, and clearly define the expectations.

5-10 minTCR Board ReviewAll

Any new submissions?

3 minCouncil Goals/ObjectivesAll

Previous notes:

5-10 min

New Module Technical Evaluation

Previously: "External Code Submissions"

Craig McNally

Tod Olson 

Marc Johnson 

Quick update from the sub-group?

Quick update from the cross-council group for defining the end-to-end process? 

  • No update yet, still organizing. Probably a few weeks before the first meeting.
  • Related: PC is sort of facing the same issue(s) that caused delay for TC .
20 min (Depending on attendance)

Technical Decision Making Process

Jakub Skoczen

This is a carry-over from last week.

  • The tech leads group not being a decision making body
  • Whether it's realistic and/or desirable for the TC to make every technical decision
    • There was some overlap here with the external code submission topic

Additional Context: 

For Today:

  • We had homework to review Jakub Skoczen's document and provide feedback/questions/comments.
    • Does the RFC proposal meet the purpose outlined here in this document?
    • Are there other proposals for a decision making process (maybe that borrow parts of the RFC process)?
  • Last time discussed:  "need some feedback, will come back next week".  Skipped last week due to low attendance.

Postponing, need more feedback on document.

20 min

(Depending on attendance)

Participation and Attendance ExpectationsAll
  • Low attendance/participation from some members is becoming concerning - it's probably worth aligning on expectations.  
  • Use of proxies?
  • How to handle low attendance
    • Cancel the meeting?
    • Still meet and make progress on things that don't require decisions to be made, e.g. review proposals and provide feedback, at least go through the usual updates
  • ...

Discussion:

  • Strong preferences for not cancelling meetings.
  • Comments in favor of leaning on proxies, but not too much.
    • Some projects (e.g. NPM) have minimal requirements for attendance, not clear we want to formalize this.
  • Need more participation outside of meeting, there is more to be done than 1 hour per week in meeting.
  • How to set expectations about participation?
    • Probably best to set vague expectations to promote useful participation.
    • Examples of participation might be useful
    • Setting metrics is probably neither practical nor has the right tone.
  • Baseline
    • Encouragement at all meetings is encouraged, and if cannot make a meeting send a proxy
    • Happy to use half-plus-one to make decisions, and lean on lazy consensus unless there is a call for a vote
    • Homework!
  • Ideas for broad expectations:

Time permitting



  • Another meeting rules thing: should we have a formal policy/discussion about attendance, discussion, and decision making when attendance is low/less than half? 

Action items

  •  
  • No labels