-
Notifications
You must be signed in to change notification settings - Fork 64
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
Remove chairs from template #261
Conversation
To resolve #259
@samuelweiler Chairs are often something reviewers want to see in evaluating a charter during review, and they're not frequently changed, so I wonder if there's a different way to solve the issue of synchronization. |
Two options:
|
I think we're looking for an API-based way to include chair information in charters and keep it updated. |
I'm with @wseltzer because:
therefore I don't know if it's actually an issue. |
Not only do these changes happen infrequently, we want a record of when they do change. I think that puts us back to "manually update the charter and leave a note in the changelog at the bottom." |
It's about a 10% error rate. I suspect the low frequency of the changes actually contributes to the problem. When you don't do a task (e.g. update chairs) often, you often forget how to do it "right" and miss steps. And when we don't have a definitive list of all the places the chair names appear, we're going to miss some. In addition to a mismatch in the Distributed Tracing WG which I found in May, today I see two other mismatches in our WGs: Accessibility Guidelines Working Group JSON-LD Working Group While the chairs match, I see mismatched team contacts in three WGs: |
I have observed that note not being added, e.g. no note was added to the the Distributed Tracing charter when it was fixed within the last month. |
Additionally, there are chair mismatches in these two IGs: Web Payment Security Interest Group |
I hear you. I'm willing to close this issue and PR, but I do think there is a not-yet-addressed problem. |
... and moved link to GH at the end of the footer. This is to fix part of [Sam's issue](w3c/charter-drafts#261 (comment)) elsewhere.
Thanks for the QA @samweiler!
|
|
I think the problem is that some Team contacts are unaware that they are supposed to update the charter (and append to the history section). The solution seems to be better Team training and/or documentation. I agree with @koalie that AC frequently want to know who will be chairing a newly-proposed group. |
To resolve #259