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

Expand 'sustained disruption of discussion' text to explicitly call out concern trolling, sealioning, gish galloping, and argumentum ad nauseam. #171

Merged
merged 5 commits into from
Jun 8, 2021

Conversation

hober
Copy link
Member

@hober hober commented May 28, 2021

An attempt at addressing #150.


Preview | Diff

…ut concern trolling, sealioning, gish galloping, and argumentum ad nauseam.
@hober hober requested a review from wareid May 28, 2021 00:10
@jwrosewell
Copy link

This modification is an attempt to stifle debate and increase the imbalance of power between group chairs and participants. In particular it discriminates against new members who can not understand from the documents how a group reached a position. It discourages diversity by promoting group think. If a group is insufficiently confident in its position to engage in debate supported by evidence, then its position is likely in need of modification rather than the PWETF.

As an example. Issue “Supply chains can be trusted - expand document to consider this possibility” in relation to the Security and Privacy Questionnaire is likely to be considered by the proposer and supporters of this change to be illustrative of some of the issues they perceive need addressing. TAG have done nothing to justify the position of that document, and then banned me without justification as I was progressing a pull request to that document. I believe this pull request is an attempt to retrospectively provide the justification they seek.

In relation to the text of this pull request, I have the following initial questions and concerns.

  1. How does the “bad faith” label get assigned? Is it just the assumption of a motive that the chair considers to be in some way incompatible with their definition of “good”? I don’t have to agree with someone to accept that from their position they are debating in good faith.
  2. How do we prevent the PWETF from being used to intimidate new members who lack the history of a document and can’t find the evidence to support the position of the group but need such information to engage in the debate or understand the proposal? Without such information a new participant can not propose changes to a document from a position of understanding.
  3. How is motive assigned to a question? If someone can not understand the position of the group, then they will be discouraged from asking to find the information they need. They will retract and become disenfranchised.
  4. If an argument is weak then the group should be easily able to expose it as such quickly. What it the group’s position is exposed as weak but the chairs and long-standing group participants are committed to maintaining it?

If the issue is use of people’s time and a concern that new participants questions may take time from the group or chairs to resolve, then there are other ways of handling this. These include.

  1. Ensuring all documents have supporting evidence and a background section that summarises the history of the document and its position. Many W3C documents do not contain such information and operate from the position of “everyone knows”.
  2. Where there are contentious issues that lack consensus, then drop them. As a consensus-based organisation without consensus we can’t move forward. As W3C participation increases and more diverse views are advanced then this many be hard for long time W3Cs to accept, but it is the reality of the W3C’s model. More time will be needed for debate.

I would much prefer TAG members focused their talents on providing the evidence needed for new participants to understand their position than avoid debate by making discriminatory proposals such as this one.

I would prefer W3C focused on changes to increase participation and break out of the current group think bubble. The web is for everyone.

index.html Outdated Show resolved Hide resolved
Copy link
Collaborator

@torgo torgo left a comment

Choose a reason for hiding this comment

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

Fully support these additions.

@TzviyaSiegman
Copy link
Collaborator

@jwrosewell thanks for your questions. As with all matters in a code of conduct, we have to find the right balance between trusting those who implement the code to interpret it and over-defining it so that it is too constrained to be meaningful. When identifying unacceptable behaviors among humans, it is often situational. That is why terms like "bad faith" are used. We obviously encourage new participants to ask questions and get up to speed.
The goal of this addition is to discourage people who intentionally slow down progress by doing things like asking unnecessary questions, which takes time away from building implementations or writing spec language. We are open to revising the language if you have suggestions.

Copy link
Collaborator

@AdaRoseCannon AdaRoseCannon left a comment

Choose a reason for hiding this comment

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

This makes sense to me, I do not share the concerns about it being used to prevent new people from becoming engaged since the PWETF is applied by people who can make judgement calls about when a participant is being genuinely inquisitive or disruptive.

Especially since common forms of disruption happen under the guise of 'just asking questions' or 'just having concerns' where both parties know it is trolling but the person being disruptive can pretend to be sincere to a casual onlooker.

@jwrosewell
Copy link

@TzviyaSiegman I will propose modifications next week as you suggest. In the meantime I ask that you do not merge this pull request until I have been given the opportunity to do so.

@hober hober requested a review from TzviyaSiegman June 1, 2021 17:33
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.

LGTM

index.html Outdated Show resolved Hide resolved
@hober hober linked an issue Jun 2, 2021 that may be closed by this pull request
Co-authored-by: Martin Thomson <mt@lowentropy.net>
@jwrosewell
Copy link

jwrosewell commented Jun 7, 2021

@hober I have created a PR which reduces the proposed addition to the following.

  • Wasting others time.
  • Repeating statements which have been shown to be false.
  • Re-raising questions that have already been answered.

This has the following advantages.

  1. Focus on the outcome which is the wasting of others time.
  2. Removed the references to "concern trolling", "sealioning”" "gish galloping", and "ad nauseam" as these are all terms that are not common in plain English and require the reader to research them to understand the document requiring unnecessary time on the part of the reader. They risk also being defined by reference which I would prefer to avoid.
  3. The terms will be harder to understand for those where English is not their first language.
  4. I have tested both the original text and the proposed replacement at https://app.readable.com/text/?demo. The original text is ranked as D and the replacement A.
  5. A weak argument is easy to dismiss otherwise it would not be weak and therefore is covered by "shown to be false".
  6. The "basic concepts" statement is concerning as it would discourage participation. The charter for a group should explain the expected level of understanding of the participants and provide guidance on any prior reading or history to help them. If the participant has not read this material then the chair can bring this to their attention.
  7. Motive is hard to determine and therefore statements like "disingenuously", "attempt" or "bad faith" need to be avoided. Raising the same question can easily be identified based on a simple analysis of the question. Clarifying questions should be welcomed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Should there be explicit language in the CEPC Regarding "Sea Lioning"?
10 participants