8000 New provisions for what Core WG vs other WGs do by alevy · Pull Request #3894 · tock/tock · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

New provisions for what Core WG vs other WGs do #3894

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Mar 4, 2024

Conversation

alevy
Copy link
Member
@alevy alevy commented Mar 1, 2024

Pull Request Overview

This pull request codifies the high-level responsibilities of the Core
WG relative to other working groups as originally proposed
here
and discussed on the Core WG 2024-03-01.

TODO or Help Wanted

Copy editing suggestion welcome

Documentation Updated

  • Updated the relevant files in /docs, or no updates are required.

Formatting

  • Ran make prepush.

@alevy alevy requested a review from a team March 1, 2024 19:47
@alevy
Copy link
Member Author
alevy commented Mar 1, 2024

Example new working groups and purviews:

  • Core
  • Kernel
    • The kernel crate (minus things like HILs)
  • Networking
    • capsules/src/extra/net
    • capsules/src/extra/ieee802154
    • capsules/src/extra/ble*
    • capsules/src/extra/usb
    • capsules/src/extra/can[.rs]
  • RISC-V (FKA OpenTitan)
    • chips/ibex
    • chips/lowrisc
    • boards/opentitan
    • boards/litex
    • arch/rv32i
    • Userspace support for RISC-V
  • Documentation
    • tock-book
    • doc/
  • User-space libraries
    • libtock-c
    • libtock-rs
    • libtock-[whatever-is-next]
  • Testing and development infrastructure
    • tockloader
    • CI and test infra
    • tools/
  • Cryptography
    • Capsules and HILs for AES, digests, signatures... you know... crypto stuff
  • Peripherals
    • Most of the rest of capsules, but specifically peripheral busses
      (i2c, spi, etc..), sensors, etc

lschuermann
lschuermann previously approved these changes Mar 1, 2024
Copy link
Member
@lschuermann lschuermann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree with this generally.

I would still like to see some brief statement about conflict resolution and/or escalation procedures for when there is a contribution to subsystems under purview of multiple working groups, or working groups propose contributions that are in conflict on a technical or conceptual level.

doc/wg/README.md Outdated
Comment on lines 10 to 15
organizations, physical distance, timezones, 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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this text is helpful in this PR description, but the goal is for this to become incorrect, which makes it awkward to add to the README. I think either we don't need it or it could be phrased as what we want to avoid, rather than what is currently happening.

doc/wg/README.md Outdated
Comment on lines 68 to 69
However, working groups are encouraged to avoid consensus-based
decision making as quickly as possible and establish appropriate
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure what this is supposed to imply exactly. WGs are supposed to not converge to a consensus?

doc/wg/README.md Outdated
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:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Specifying these here is in conflict with the core WG charter.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK, you're right. I'll move these to doc/wg/core/README.md

@alevy alevy force-pushed the core_wg_proposal branch from 0889cd6 to 89d87ff Compare March 2, 2024 02:38
@alevy
Copy link
Member Author
alevy commented Mar 2, 2024

I would still like to see some brief statement about conflict resolution and/or escalation procedures for when there is a contribution to subsystems under purview of multiple working groups, or working groups propose contributions that are in conflict on a technical or conceptual level.

@lschuermann, done.

I think I addressed @bradjc's comments as well.

@alevy alevy added this pull request to the merge queue Mar 4, 2024
Merged via the queue into tock:master with commit e73556f Mar 4, 2024
@alevy alevy deleted the core_wg_proposal branch March 4, 2024 18:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants
0