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

Consolidate discipline-related elements #418

Closed
koalie opened this issue Jun 30, 2020 · 7 comments
Closed

Consolidate discipline-related elements #418

koalie opened this issue Jun 30, 2020 · 7 comments
Labels
Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion DoC This has been referenced from a Disposition of Comments (or predates the use of DoCs)
Milestone

Comments

@koalie
Copy link
Contributor

koalie commented Jun 30, 2020

Hi!

In digging for information relating to discipline, I found two such places in Process 2019:

While the latter needs an update and I have followed-up separately with W3M to do so, I would like to raise the question of consolidating the two Process document places that touch on discipline.

I think it would make more sense to do so in section 3.1 Individual Participation Criteria which is broader than 2.1.1 Rights of Members.

@dwsinger
Copy link
Contributor

Indeed this in 2.1.1:

The rights and benefits of W3C membership are contingent upon conformance to the processes described in this document. The vast majority of W3C Members faithfully follow the spirit as well as the letter of these processes. When serious and/or repeated violations do occur, and repeated attempts to address these violations have not resolved the situation, the Director may take disciplinary action. Arbitration in the case of further disagreement is governed by paragraph 19 of the Membership Agreement. Refer to the Guidelines for Disciplinary Action.

could become

The rights and benefits of W3C membership are contingent upon conformance to the processes described in this document. Arbitration in the case of further disagreement is governed by paragraph 19 of the Membership Agreement. Disciplinary action for anyone participating in W3C activities is described below.

and 3.1 was

Participants in any W3C activity must abide by the terms and spirit of the W3C Code of Ethics and Professional Conduct and the participation requirements described in section 6 of the W3C Patent Policy.
The Director may suspend or remove for cause a participant in any group (including the AB and TAG), where cause includes failure to meet the requirements of this process, the membership agreement, or applicable laws.

and becomes:

Participants in any W3C activity must abide by the terms and spirit of the W3C Code of Ethics and Professional Conduct and the participation requirements described in section 6 of the W3C Patent Policy.

When serious and/or repeated violations do occur, including failure to meet the requirements of this process, the membership agreement, or applicable laws, and repeated attempts to address these violations have not resolved the situation, the Director may take disciplinary action, including suspending or removing for cause a participant in any group (including the AB and TAG). Refer to the Guidelines for Disciplinary Action.

The text in 3.1 before 3.1.1 could usefully have a section title.

@nigelmegitt
Copy link
Contributor

could become

The rights and benefits of W3C membership are contingent upon conformance to the processes described in this document. Arbitration in the case of further disagreement is governed by paragraph 19 of the Membership Agreement. Disciplinary action for anyone participating in W3C activities is described below.

Yes if we remove the text I emphasised in bold above: "in the case of further disagreement". The reasons why arbitration might be needed are hard to write down, and I think are not needed. The point is that there is an arbitration term, and a pointer to it is useful.

What drew me to this was when I read "further disagreement" I couldn't work out what the disagreement was further to. I thought, perhaps this means "unresolved disagreement", but that sounds weird. Maybe "ongoing disagreement" is closer, but how long is "ongoing"? And this wording doesn't give the sense that you don't go for arbitration if you have two mutually incompatible views on some specification wording - it's about something else altogether more serious than that kind of disagreement.

@frivoal
Copy link
Collaborator

frivoal commented Jul 14, 2020

The above makes sense to be. While we're at it, I'm also wondering if the beginning of 3.1 (the 2 paragraphs and the number list before the part that @dwsinger quoted) actually do anything useful. Maybe we can get rid of them while we're at it?

@dwsinger
Copy link
Contributor

I think they are appropriate; they put a responsibility on AC Reps to make sure they send suitable people.

@koalie
Copy link
Contributor Author

koalie commented Jul 17, 2020

(While I'm tuning to related some disciplinary action documentation, I'd like to note this issue is related to #274)

@dwsinger
Copy link
Contributor

Indeed, if there is anything in #274 worth salvaging, we could deal with it at the same time.

frivoal added a commit to frivoal/w3process that referenced this issue Jul 25, 2020
@frivoal
Copy link
Collaborator

frivoal commented Jul 25, 2020

Created a PR doing the things discussed above: #432

I addition, we could:

@frivoal frivoal added the Agenda+ Marks issues that are ready for discussion on the call label Jul 25, 2020
frivoal added a commit to frivoal/w3process that referenced this issue Jul 28, 2020
@dwsinger dwsinger removed the Agenda+ Marks issues that are ready for discussion on the call label Sep 15, 2020
@dwsinger dwsinger added the Agenda+ Marks issues that are ready for discussion on the call label Oct 6, 2020
@frivoal frivoal closed this as completed in cff0589 Dec 9, 2020
@frivoal frivoal added Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion DoC This has been referenced from a Disposition of Comments (or predates the use of DoCs) and removed Agenda+ Marks issues that are ready for discussion on the call labels Dec 9, 2020
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 DoC This has been referenced from a Disposition of Comments (or predates the use of DoCs)
Projects
None yet
Development

No branches or pull requests

4 participants