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

Adjust the status of Tim Berners-Lee in the TAG #791

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

frivoal
Copy link
Collaborator

@frivoal frivoal commented Oct 12, 2023

This ensures he has permanent access to participate in the TAG, without putting him on the critical path for any vote or quorum that involves TAG members, notably the Council's Unanimous Short Circuit.

More broadly, this also removes him from being part of the Council, as the Council's purpose is to replace his former role as Director in resolving Formal Objections.

This is one possible solution to #784, with #792 and #793 being alternatives.


Preview | Diff

@frivoal frivoal added Director-free: FO/Council Issues realted to the W3C Council and Formal Objection Handling Director-free (all) All issues & pull request related to director-free. See also the topic-branch labels Oct 12, 2023
This ensures he has permanent access to participate in the TAG,
without putting him on the critical path for any vote or quorum that
involves TAG members, notably the Council's Unanimous Short Circuit.

More broadly, this also removes him from being part of the Council,
as the Council's purpose is to replace his former role as Director in
resolving Formal Objections.

See w3c#784
@frivoal frivoal changed the title Adjust the status of Tim Berners Lee in the TAG Adjust the status of Tim Berners-Lee in the TAG Oct 12, 2023
@nigelmegitt
Copy link
Contributor

I like the approach here, but I think merely having a standing invitation to TAG meetings is slightly too weak, in the sense that it needs to be clear that he is invited, but not required, to participate fully in all TAG activities, as well as meetings or sessions.

Copy link
Member

@tantek tantek left a comment

Choose a reason for hiding this comment

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

Why not omit "permanent" from this PR? What does it add?

Or if the intent is a ongoing default, then say "ongoing standing invitation" instead.

Other than that LGTM (and can live with current wording also)

index.bs Outdated Show resolved Hide resolved
@frivoal
Copy link
Collaborator Author

frivoal commented Aug 2, 2024

Another difference this would make is that Timbl would no longer be involved (and therefore not counted when determining the 2/3 marjority) when voting on approving TAG appointments.

index.bs Outdated Show resolved Hide resolved
index.bs Outdated Show resolved Hide resolved
Copy link
Member

@tantek tantek left a comment

Choose a reason for hiding this comment

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

Suggested one typo fix, otherwise additional changes are an improvement. Thanks for this iteration.

Co-authored-by: Tantek Çelik <[email protected]>
Comment on lines +1018 to +1019
As <dfn export>Director Emeritus</dfn>,
Tim Berners-Lee has an ongoing standing invitation
Copy link
Member

Choose a reason for hiding this comment

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

My dfn syntax may be wrong, but my intent should be clear enough to act on.

That said, as I read the documentation, the <dfn> tag should be used where the term (whether Director Emeritus or Directors Emeriti) should be defined, to be referenced from elsewhere — but there is no such definition here, so should perhaps this should be [=Director Emeritus=] with the <dfn> somewhere else?

Suggested change
As <dfn export>Director Emeritus</dfn>,
Tim Berners-Lee has an ongoing standing invitation
Each <dfn data-lt="Directors Emeriti" export>Director Emeritus</dfn>
has an ongoing standing invitation

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

There's no expectation that this ever will be plural (and if it did become plural, that would imply a change in governance large enough to merit thinking about explicitely), so I think it makes sense to keep this in the singular.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

As for using this as a dfn vs a reference to a dfn, "Tim Berners Lee" is effectively the definition of "Director Emeritus" for our purposes, so I think the original phrasing is fine, and actually, removing his name from this definition suggests, incorrectly, that it might apply to more people, which is not intended.

Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
As <dfn export>Director Emeritus</dfn>,
Tim Berners-Lee has an ongoing standing invitation
As the only <dfn export>Director Emeritus</dfn>,
Tim Berners-Lee has an ongoing standing invitation

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I wonder if we should drop line 1018 entirely. While timbl was the Director for the longest time, that word has now taken a new meaning (board member). The "the only" clarification helps, but maybe dropping the line altogether is simpler. Or maybe replace "Director Emeritus" with "founder of W3C", which unambiguously refers to him and him alone.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Suggested change
As <dfn export>Director Emeritus</dfn>,
Tim Berners-Lee has an ongoing standing invitation
As <dfn export>founder of W3C</dfn>,
Tim Berners-Lee has an ongoing standing invitation

Copy link
Member

Choose a reason for hiding this comment

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

Is this missing some articles?

"As the founder of the W3C," or "As founder of the W3C," both work for me. I realize that the usage of the standalone "W3C" in this document often deliberately omits a "the", but that just reads as broken English to this native speaker.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Omitting "the" in front of "W3C" is not limited to this document, it's W3C's official branding guidelines, which we merely follow. Took me a while to get used to, but I've now grown accustomed to it, and it doesn't really strike me as any more strange than the lack of article in front of IBM or NASA.

Copy link
Member

@martinthomson martinthomson left a comment

Choose a reason for hiding this comment

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

This seems fine to me, with any of the alternative spellings of the text. Better than the other option presently on the table (#792). Process needs to reflect reality and this is closer to that reality as I experience it.

Comment on lines +1018 to +1019
As <dfn export>Director Emeritus</dfn>,
Tim Berners-Lee has an ongoing standing invitation
Copy link
Member

Choose a reason for hiding this comment

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

Is this missing some articles?

"As the founder of the W3C," or "As founder of the W3C," both work for me. I realize that the usage of the standalone "W3C" in this document often deliberately omits a "the", but that just reads as broken English to this native speaker.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Director-free (all) All issues & pull request related to director-free. See also the topic-branch Director-free: FO/Council Issues realted to the W3C Council and Formal Objection Handling
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants