- Working Group Charter
- Adopted 3/31/2020
- Amended 3/01/2024
The core team manages and guides the development of Tock. Its responsibilities are:
-
Managing and overseeing code, documentation, testing, and releases for the Tock project.
-
Defining and communicating overall project goals and direction.
-
Establishing and delegating responsibility over components and subprojects to working groups.
-
Ensuring that working groups have the people and resources needed to accomplish their work.
-
Ensuring working groups are accountable to their delegated responsibilities and the project as a whole.
-
Coordinating decisions including (but not limited to) code, documentation, testing, and releases that affect purviews delegated to more than one working group.
-
Facilitating communication channels and consensus among working groups.
-
Coordinating project-wide changes to teams, structures, or processes.
- Hudson Ayers, hudson-ayers, Stanford
- Brad Campbell, bradjc, UVA
- Branden Ghena, brghena, Northwestern
- Philip Levis, phil-levis, Stanford
- Amit Levy (Lead), alevy, Princeton University
- Pat Pannuto, ppannuto, UCSD
- Alexandru Radovici alexandruradovici, Politehnica Bucharest & OxidOS
- Leon Schuermann, lschuermann, Princeton University
- Johnathan Van Why, jrvanwhy, Google
The core working group membership is a subset of the people who have commit (pull request merge) permissions on the Tock repository. It is intended to be a smaller group that represents the major perspectives and issues, rather than a complete group. Contributors who actively help develop Tock will be considered to join the core team. Generally, a core team member:
- Understands the core design principles of Tock and is capable of judging the effect new code contributions will have on Tock's adherence to those principles.
- Understands the code style and structure of Tock and can help ensure a reasonably consistent code base.
- Understands Tock's various stakeholders and can judge how a change to Tock might affect various users of Tock.
A core team member is expected to:
- Help review a percentage of new pull requests to the Tock code base.
- Provide opinions and input on substantial design decisions or major changes to Tock.
- Help test Tock prior to releases.
To join the core team, a contributor must be nominated by an existing core team member. The nominator will open a pull request updating this document with the new core team member in the list above. That pull request will undergo the usual pull request review, and the member will be added to the core team if the pull request is merged.
The group has a weekly teleconference call. All working group members are invited to participate in the call. Other people may be invited to participate to help contribute to particular topics or on-going discussions. The working group chair decides who beyond the working group members may participate in the call.
The working group publishes detailed notes of its calls. These will be posted within a week of a call. This delay is to give participants an opportunity to correct any errors or better explain points that came up. They are intended to be a communication mechanism of the group, its discussions, the technical issues, and decisions, not a literal transcription of what is said.