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

JL-TF charter 2023-2024 #345

Merged
merged 2 commits into from Dec 16, 2022
Merged

JL-TF charter 2023-2024 #345

merged 2 commits into from Dec 16, 2022

Conversation

himorin
Copy link
Contributor

@himorin himorin commented Nov 14, 2022

closes #344

@kidayasuo I believe I've covered all points in the issue.

This PR is still draft for welcoming reviews, comments, and suggestions.
Several open points:

  • should jlreq-d and ruby-t2s-req use Develop instead of Update? - since no draft is out, esp. no document for jlreq-d yet
    1. Participation lists two levels, but README lists three levels. Do we want to align?

@kidayasuo
Copy link
Contributor

Thank you @himorin for proposing changes for me. The proposed changes look good except that as you mentioned jlreq-d will be to develop rather than to update as it has not been completed yet.

Regarding the participation, yes, the charter and README should be aligned. Actually both says the same thing except that the README separates "To contribute content" as a participation level. What does this level mean? As I do not see any participants in this level at jlreq (right?), I guess it can be simplified to two levels like it is described in the charter.

Another inconsistency is how they call the active participant. The readme explains it as "a participant, editor, or chair" and the charter calls it "Task force members". I feel the description in the charter is simpler.

What do you think, @r12a?

@himorin
Copy link
Contributor Author

himorin commented Dec 12, 2022

Talked with Kida-san (@kidayasuo ), and we agreed that charter has a line to notice that TF members and contributors are required to read and agree with CONTRIBUTING.md in Participation section, which makes levels consistent with README. So, keep this draft as is for now.

@himorin himorin changed the title [draft] JL-TF charter 2023-2024 JL-TF charter 2023-2024 Dec 12, 2022
Copy link
Contributor

@kidayasuo kidayasuo left a comment

Choose a reason for hiding this comment

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

Changes look good. Thank you. Approving.

@himorin
Copy link
Contributor Author

himorin commented Dec 16, 2022

https://www.w3.org/2022/12/15-i18n-minutes.html#t05
merging this, to be appeared into github.io.

@himorin himorin merged commit 2e1f85c into w3c:gh-pages Dec 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

build JL-TF charter for next period from 2023/Jan/01
2 participants