--- tags: draft --- # lang team expectations ## Required * Attend triage and design meetings regularly. Provide advance notice when not possible (e.g. vacations or one-time conflict). Work with team on meeting scheduling to avoid recurring conflicts. * Respond promptly to FCP requests, raise concerns as needed, or sign off. * Read T-lang RFCs that are ready for review. * Given current revisions to the MCP/RFC process, this does not yet mean "all T-lang RFCs". * This does include RFCs that come up in triage or design meetings for lang review, or RFCs that have come out of a project group. * Follow through on commitments made (such as to post discussion summaries or other review comments. ## Optional * Serve as liaison for project group(s) * Time permitting, but ideally members should have one active group they're supporting. * In other words, it's not required to serve as a liaison at any given time, and it's fine to say "I'm busy with project X for a while", but it is expected that lang team members will serve as liaisons from time to time, though not necessarily for more than one group at a time. * Serve as a lead or member in project group(s) * Only if interested, and only if not also serving as liaison. * Participate in Zulip conversations * No expectation of real-time responses unless prearranged and agreed, but generally staying abreast of Zulip conversation is useful. * Participate in Github conversations * Here the expectation is lighter. Following up on particular topics of interest is good. Generally keeping up with Github may not be expected ## Job description - build consensus with small groups - extract consensus from technical chaos - why do people nominate things and what do we do in response to it? - resolve small question during triage - decide what lints we want - decide how much breakage is “worth it” given crater runs - decide what features to prioritize - requires assessment of what is best for the language, what is “needed” - design of new features at various scales (e.g., async-await at the largest scale, pattern matching improvements at the other end) - judge soundness and detailed type theory questions - project management — tracking features to completion