WGs: Address comments in description & split Core responsibilities

doc/wg/README.md

@@ -6,14 +6,6 @@ particular aspect of Tock.
 
 ## Motivation
 
-Tock relies on contributions from developers across a variety of
-organizations, physical distance, time zones, and engagement. It has
-also grown large in scope. This has resulted in strain on maintainers
-to regularly keep up with contributions while ensuring quality and
-important global policies like safety and security. It has also
-resulted in contributors' work going unaddressed for long periods of
-time.
-
 Tock encompasses a large and varied set of subsystems, architectures,
 focus areas, libraries, ancillary tools, and documentation. Most
 contributors have expertise and stake in a subset of these. Moreover,
@@ -65,10 +57,9 @@ groups make decisions by consensus, have weekly voice calls, make
 meeting notes available publicly, and communicate asynchronously via a
 mailing list.
 
-However, working groups are encouraged to avoid consensus-based
-decision-making as quickly as possible and establish appropriate
-meeting frequency and communication mode for their needs and
-membership.
+However, working groups are encouraged to establish appropriate
+decision-making rules, meeting frequency and communication mode for
+their needs and membership.
 
 ## Core Working Group
 
@@ -85,25 +76,6 @@ groups. The Core Working Group, like other working groups, establishes
 its own rules for deciding how to accept contributions as well as how
 to establish and disband working groups.
 
-The Core Working Group's duties 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.
-
 Existing Working Groups
 -----------------------
 

doc/wg/core/README.md

@@ -3,28 +3,45 @@ Tock Core Working Group (core)
 
 - Working Group Charter
 - Adopted 3/31/2020
+- Amended 3/01/2024
 
 ## Goals
 
 The core team manages and guides the development of Tock. Its responsibilities
-are to:
+are:
 
-- Design, implement, and maintain the Tock kernel and its interfaces, including
-  system calls, hardware interface layers, and internal kernel APIs,
-- Decide when to update the Rust compiler toolchain that Tock uses,
-- Decide on the formation, scope, and lifetime of other Tock working groups,
-- Decide on, articulate, and promote core principles of Tock kernel software and
-  its development,
-- Support any code in the Tock repository that is not supported by another
-  working group.
+
+- 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.
 
 ## Members
 
 - Hudson Ayers, [hudson-ayers](https://github.com/hudson-ayers), Stanford
 - Brad Campbell, [bradjc](https://github.com/bradjc), UVA
 - Branden Ghena, [brghena](https://github.com/brghena), Northwestern
 - Philip Levis, [phil-levis](https://github.com/phil-levis), Stanford
-- Amit Levy (chair), [alevy](https://github.com/alevy), Princeton University
+- Amit Levy (Lead), [alevy](https://github.com/alevy), Princeton University
 - Pat Pannuto, [ppannuto](https://github.com/ppannuto), UCSD
 - Alexandru Radovici [alexandruradovici](https://github.com/alexandruradovici), Politehnica Bucharest & OxidOS
 - Leon Schuermann, [lschuermann](https://github.com/lschuermann), Princeton University
@@ -71,14 +88,3 @@ 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.
-
-## Code Purview
-
-The core working group is in charge of (responsible for reviewing, approving,
-and merging pull requests for) all code directories that are not under the
-purview of another working group. The following directories are expected to
-remain under the sole purview of the core working group:
-
-- `capsules`, although other working groups may have subdirectories
-- `kernel`
-- `libraries`