8000 wg: Add DOC Working Group by bradjc · Pull Request #3815 · tock/tock · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

wg: Add DOC Working Group #3815

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 3 commits into from
Feb 2, 2024
Merged

wg: Add DOC Working Group #3815

merged 3 commits into from
Feb 2, 2024

Conversation

bradjc
Copy link
Contributor
@bradjc bradjc commented Jan 24, 2024

Pull Request Overview

This pull request would establish a new working group focused on documentation.

TODO or Help Wanted

Is anyone interested in joining?

Is the scope correct?

Documentation Updated

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

Formatting

  • Ran make prepush.

The DOC working group maintains:

- https://github.com/tock/book
- https://github.com/tock/tock/tree/master/doc
Copy link
Member
@lschuermann lschuermann Jan 24, 2024

Choose a reason for hiding this comment

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

Should this exclude normative documentation like TRDs? I don't foresee this being a problem in practice, but it might technically create a conflict in purview of those between Core and DOC WGs.

Copy link
Member

Choose a reason for hiding this comment

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

Adding to this, that last folder also contains documentation of other working groups (such as call notes). I'm not sure whether the burden of maintaining that should be placed on a DOC WG as well.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Should this exclude normative documentation like TRDs?

Yes I think so.

contains documentation of other working groups (such as call notes). I'm not sure whether the burden of maintaining that should be placed on a DOC WG as well.

I agree this should be more narrowly scoped.

@brghena
Copy link
Contributor
brghena commented Jan 24, 2024

I'm interested

@lschuermann lschuermann requested a review from a team January 26, 2024 17:27
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.

Approved by attendees on the core team call today. Adopted date would need to be updated.

@bradjc bradjc requested a review from a team February 1, 2024 16:22
@lschuermann lschuermann added this pull request to the merge queue Feb 2, 2024
Merged via the queue into master with commit c5661f9 Feb 2, 2024
@lschuermann lschuermann deleted the wg-doc branch February 2, 2024 18:32
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.

5 participants
0