40 min | Cross-Council logistics Some items to cover: Cross-Council whole group meetings Are there any sub-teams to consider phasing out or re-envisioning - as themselves or as particularly cross-Council? New and current members - any coordination in onboarding and sub-team assignments? Any coordination in other kinds of messaging? Anything else?
| All | Sub-teams will remain where they are organizationally, but all will be open to members of either Council. Hold two full Council meetings - one at the beginning of the year and one in January. Aiming for the first one to be in mid- to late July if it is feasible, with August as a backup. Introduce the sub-teams at the first meeting, provide a Google form/SurveyMonkey survey for people to make their preferred selections. Put together documentation with tips for successful sub-team and Council leadership and participation. This would go on the wiki in the TAC/UAC Coordinating area. For TAC: worth considering sunsetting Migrations, bringing up a team related to metadata standards. Integrations might be something to evolve down the line. For UAC: worth considering sunsetting Reports, bringing up a team related to Community Engagement and/or Usability or Accessibility Reports needs a defined task to wrap up its work; could convert this area of focus to a task force/working group involving broader community participation. Any new groups would need defined charges and selection of leaders that are likely to succeed in the role. Some broader discussion: What are the essential elements that are intrinsic to TAC and UAC? Does there need to be some retention of separate identities? Concern that TAC shouldn’t drift too far from one of its stated purposes: encouraging an active community of developers. As teams shake out, is there a way to have Integrations, for example, get more involved in this area? Could TAC propose a Coding for Dummies-type workshop on contributing code to fix little annoying things in the application? To what degree can/should Council work evolve into task force-type limited-term work?
|