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

Editorial: dismissal #747

Closed
mnot opened this issue Apr 30, 2023 · 6 comments
Closed

Editorial: dismissal #747

mnot opened this issue Apr 30, 2023 · 6 comments
Labels
Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion Commenter satisfied/accepting conclusion confirmed as accepted by the commenter, even if not preferred choice Type: Editorial improvements
Milestone

Comments

@mnot
Copy link
Member

mnot commented Apr 30, 2023

In 5.6.2.3., this sentence isn't very helpful:

In order to apply consistent criteria, the potential Council members decide collectively which reasons against service rise to a sufficient level for a potential member to be dismissed.

First, the purpose of dismissal surely isn't to just 'apply consistent criteria', is it?

Also, 'reasons against service' is obscure, especially when the subject of the clause is at the very end of the sentence.

I also suspect that 'potential Council members' (throughout) is an unnecessary phrasing; the use of 'dismissal' suggests that these people are council members, they just leave, so you can just say that dismissal is the first order of business for a new council.

I'd suggest something like:

To address potential conflicts of interest, a Council's first order of business is determining if any of its members should be dismissed.

@mnot
Copy link
Member Author

mnot commented Apr 30, 2023

Also, the following note (regarding the nature of a Council) is very oddly placed; I suspect it should be moved up to the end of 5.6.2.1.

@mnot
Copy link
Member Author

mnot commented Apr 30, 2023

... and, They then consider for each potential member is ambiguous -- who is 'they'?

fantasai added a commit to fantasai/w3process that referenced this issue May 11, 2023
fantasai added a commit to fantasai/w3process that referenced this issue May 11, 2023
@fantasai
Copy link
Collaborator

fantasai commented May 11, 2023

Opened a PR at #757 to address the first and last points here.

I didn't use your wording because dismissal isn't necessarily the first order of business; typically the Council runs several of these prepatory steps in parallel.

Also conflict of interest is only one possible reason for using dismissal; we're deliberately not defining what reasons qualify, only that if the rest of the Council wants you off, you're off.

The note is placed where it is because it's important contextual information for the previous sentence. (Though I agree it feels odd there.)

Wrt “potential Council members” vs “Council member”, it is wordy but it works. I'm open to changing it, but I'd want to hear from others first.

@fantasai fantasai added the Agenda+ Marks issues that are ready for discussion on the call label May 11, 2023
@chrisn
Copy link
Member

chrisn commented May 12, 2023

I think "potential Council members" is fine, as it accurately describes what's happening at that stage of Council formation. The other changes look good.

frivoal pushed a commit that referenced this issue May 25, 2023
Define dismissal before using it. #747
@frivoal
Copy link
Collaborator

frivoal commented May 25, 2023

In response to this issue, the following PR was made and approved https://github.com/w3c/w3process/pull/757/files

@mnot, Please confirm that this outcome is satisfactory.

@frivoal frivoal added Type: Editorial improvements Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion Commenter Response Pending and removed Agenda+ Marks issues that are ready for discussion on the call labels May 25, 2023
@frivoal frivoal added this to the Process 2023 milestone May 25, 2023
@mnot
Copy link
Member Author

mnot commented May 25, 2023

That'll do.

@frivoal frivoal added Commenter satisfied/accepting conclusion confirmed as accepted by the commenter, even if not preferred choice and removed Commenter Response Pending labels May 25, 2023
@frivoal frivoal closed this as completed May 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion Commenter satisfied/accepting conclusion confirmed as accepted by the commenter, even if not preferred choice Type: Editorial improvements
Projects
None yet
Development

No branches or pull requests

4 participants