40 min | Continued discussion of Cross-Council logistics | All | Our overall goal for this year of cross-Council participation is to wade in and try out things, rather than to jump in and change everything all at once. TAC and UAC chairs will send (or have sent) messages to all new members welcoming them and providing a little general information to start. Lydia will create a Doodle poll to send out to all TAC and UAC members to facilitate scheduling the first meeting. Meeting likely to happen in mid-August. Based on the expectations document TAC created last year, Maggie, Ashley, and Lydia, will prepare expectations for all members. This should be sure to stay within the 2-4 hours per week description of workload that the Nominating Committee outlines for people considering volunteering. Identities of the sub-teams should be set (or at least describable) by the time of the first combined meeting Lydia will draft a charge for the Usability sub-team for Christine and Ashley to review. Maggie will work with Christine to put together a charge for the Metadata Standards sub-team. Ashley and Christine will work on the sunsetting of the Reports sub-team.
Based on the Google Form TAC created last year, Maggie, Ashley, and Lydia will finalize the form on which all members indicate their sub-team interests. Anyone can join any team, but the form will make it clear which teams belong to which Councils. We will not strive for balanced representation except for those teams that are explicitly cross-Council responsibilities (Testing and Dev Pri). Members must join at least one team, but can join two if they wish. It will be made clear that different sub-teams require different levels of effort. Maggie, Ashley, and Lydia will work together once the forms have been completed to determine sub-team assignments.
|