Technical Council Meetings and Notes

When & Where We Meet

Regular Meetings

Regular Technical Council Meetings are now held Mondays at 11:00 AM Eastern U.S. time (following daylight saving time rules for the Eastern U.S. timezone; see this time in your timezone). Download .ics file to add this meeting to your calendar.

Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/935492890

Or iPhone one-tap:

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

Or Telephone:

Dial (for higher quality, dial a number based on your current location):
US: +1 646 876 9923 or +1 669 900 6833
Meeting ID: 935 492 890
International numbers available: https://zoom.us/u/bP113hkE8

Dedicated Topic Discussions

In addition to our regular weekly meetings, the TC meets on Wednesdays at 11:00 AM Eastern U.S. time if there is a need to dedicate a full hour to a specific topic.  This meeting will only happen as needed.  The Zoom URL above is used for these meetings as well.

ICS file: Technical Council - Dedicated Discussion Time.ics

How Meeting Agendas are Formed

It's currently the responsibility of the chairperson to pull together meeting agendas each week.  If there are topics you'd like to raise, please contact the chairperson, or post in the #technical-council slack channel.

Recently the agenda has taken the form of:

  • Quick status updates on ongoing initiatives.  Ideally these are < 5 minutes and have concrete action items w/ deadlines so we can track progress.
  • A large portion of the meeting spent on a single, essential topic.  The idea is to dedicate sufficient meeting to make significant progress on the most important topic.  If necessary, a topic can be scheduled for a dedicated topic discussion (see above) which happen on an as-needed basis.

How Meetings are Conducted

  • Hand raising will be used to limit interruptions and talking over one another. 
    • The chairperson will call on those with their hands raised, in the order they were raised.
  • Ideally the use of chat should be limited to the current topic of conversation. In particular, chat should not be used to spawn separate topics. 

Action Items

DescriptionDue dateAssigneeTask appears on
  • TC members to review policy guidance in Ramsons OST page and provide feedback
2024-02-05 Meeting notes
  • TC members to review policy guidance in Ramsons OST page and provide feedback
2024-01-29 Meeting notes
  • Craig McNally to create review board for next RFC process retrospective.
Craig McNally2023-07-19 Meeting notes
  • Craig McNally to create review board for next RFC process retrospective.
Craig McNally2023-07-12 Meeting notes
  • Jeremy Huff will add a description of the process for changes to the officially supported technology processes to the top level page
Jeremy Huff2023-05-10 Meeting notes
  • Craig McNally to investigate using Confluence's page restrictions to limit editing of the officially supported technologies lists
Craig McNally2023-05-03 Meeting notes
  • Jeremy Huff will add a description of the process for changes to the officially supported technology processes to the top level page
Jeremy Huff2023-04-12 Meeting notes
  • When we look at RFC process again we should review comm protocols Marc Johnson 
Marc Johnson2023-04-05 Meeting notes
Craig McNally2023-03-29 Meeting notes
  • when we look at RFC process again we should review comm protocols Marc Johnson 
Marc Johnson2023-03-29 Meeting notes

All meeting notes