Dial by your location • +1 253 215 8782 US (Tacoma) • +1 301 715 8592 US (Washington DC) • +1 312 626 6799 US (Chicago) • +1 346 248 7799 US (Houston) • +1 646 558 8656 US (New York) • +1 669 900 6833 US (San Jose)
📆 Yearly Timeline of Council Activities : this page in the Council Handbook gives a month-by-month breakdown of Council activities, as well as who is responsible for those activities.
Terms begin in July and end in June. In June and July there is typically little Council work outside of the Chair’s responsibilities.
Joint TAC/UAC meetings are held twice a year, once early in the term (usually September) and again towards the end of the term.
Workplans are due and presented at the first joint meeting in September.
Quarterly reports to the Governance Board in August, October, January, and May
Cancel December or January meeting?
Online member forum in the spring – Council participation is strongly encouraged.
Most Council work wraps up in June. Sub-teams complete a retrospective and work to make term-to-term transition as easy as possible.
Sub-teams usually meet monthly, although this can vary based on the work and needs of the sub-team (e.g., Testing).
Atlassian accounts for Confluence and JIRA, and Google Drive permissions should be up-to-date; if you or a member of your team do not have access to something you should, let me know!
Expectations for sub-teams:
Hold first meeting, if you have not already
Craft workplan for the term, to be presented at the TAC/UAC meeting in September
Identify sub-team Vice Leads
Expectations for all:
⏰ Attendance and Engagement:
Attendance and/or contributions to Council meetings. Participation in discussions.
Attendance and/or contributions to sub-team meetings. Communication with your sub-team lead(s) if you cannot attend or complete tasks.