Skip to content
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

[Policy Proposal] Roles and responsibilities within the WG/IG #1117

Open
sebastiankb opened this issue Aug 8, 2023 · 5 comments
Open

[Policy Proposal] Roles and responsibilities within the WG/IG #1117

sebastiankb opened this issue Aug 8, 2023 · 5 comments

Comments

@sebastiankb
Copy link
Collaborator

sebastiankb commented Aug 8, 2023

We should define the different roles and responsibilities in the WoT WG and IG. That should include editors (REC and Note), task force leads, co-chairs, team contacts, liaison contacts person, and invited experts.

Such an overview is useful, especially when new members join the WoT WG/IG.

@mmccool
Copy link
Contributor

mmccool commented Aug 9, 2023

Should refer (link) to policies and discussion about roles of chairs. As @ashimura noted, that MD file already includes some discussion about task force leaders and editors as well.

@sebastiankb sebastiankb changed the title [Policy Proposal] Roles and responsibilities [Policy Proposal] Roles and responsibilities within the WG/IG Nov 22, 2023
@sebastiankb
Copy link
Collaborator Author

just a record, there are some inputs provided in this PR https://www.w3.org/2023/11/22-wot-minutes.html

@sebastiankb
Copy link
Collaborator Author

sebastiankb commented Jan 24, 2024

@sebastiankb
Copy link
Collaborator Author

from today's WG planning session:

@mjkoster
Copy link
Contributor

mjkoster commented Sep 27, 2024

9/27/2024 TPAC agreed to follow W3C guidance on everything except there is still guidance needed for task force leads. We can extend the chairs policy md we made last year.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants