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)
It’s okay if you don’t have an update for the first meeting of term. Use this time to ask any start-of-term questions you may have, and if you have neither updates nor questions, that’s cool! But you will have to say something in September 🥴
📆 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.
Council-wide meetings occur monthly beginning in August. TAC typically switches to bi-monthly meeting after January. Often the December or January meeting is cancelled.
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.
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
Subteam Leads/Vice Leads Group
Goals for the term:
Make monthly meetings more engaging and value-added
Strengthen community of current and former Advisory Council members