Please confirm whether this and the previous complaint was received upon receiving this email.
The previously reported pattern of policy and code of conduct violations has continued, despite a complaint to the person at fault. This is very unfortunate and I deeply regret that a prominent member of the WHATWG has to be reported. Please take immediate action to restore a safe environment and to prevent damage to the WHATWG's image as an open, safe, welcoming and professional environment.
"Whether you're a regular contributor or a newcomer, we care about making this community a safe place for you and we've got your back."
The demeaning comments have continued, while evading the questions in the previous comment. This rude and unprofessional behavior is unacceptable by the code of conduct and WHATWG policies.
- immediately rejecting 2 days' work of investigating the
<search>element's use-cases and implementation constraints with a vague reason that's a gross misrepresentation of the actual discussion. - censorship of unwanted opinion
I'll be closing or marking as off-topic any such discussions outside of this issue.
Since Domenic's first rude response to my tweet ("makes no sense") he's been making it more and more difficult to present this point of view that he doesn't want to hear about.
I myself am not able to invest further time in giving you the same answers repeatedly.
Domenic responded with only 3 short, vague and incongruent opinions:
- twitter: "It makes no sense to propose using "
- github "The form element is quite magical, and duplicating that magic into another element is a huge implementation and spec lift".
- github: "a new element "inheriting from form" is not viable" Now the claim is:
- github: "they will not implement ... as an alias"
Conflating the fundamentally different concepts of duplication, inheritance and aliasing is unprofessional. The time to write all the 3 tweet-length comments is estimated at around 10 minutes, generously. This 10 minutes of "work" was the justification to reject 2 days' work of investigating the <search> element's use-cases and implementation constraints.
I'm sorry that you feel your opinions aren't being respected, or that this community is not open in the way you'd prefer.
I don't blame the community. I've made a complaint only about Domenic's actions.
I'd remind you that oppenness doesn't mean everyone has to agree with you.
Of course it doesn't. I'm trying to achieve mutual understanding. I understand Domenic's arguments, but that goes only one way.
And you have been heard! Repeatedly. And answered, several times. By both implementers and other web developers.
Only scottaohara (editor) and bathos (developer?) responded, who expressed his ambivalent support ("I would be unlikely to employ <search> without <form>"), Domenic avoided answering my questions. Nobody discussed implementation details. Domenic misrepresents this as more contributors to justify his actions.
I'm aware that Domenic is the lead editor of the HTML specificiation and his opinion has great weight. This makes his behavior even more problematic. Censorship, disregarding developer input and developer practices, a lack of understanding the implementation constraints in relation to the proposed element makes this standardization process rushed and unprofessional.
To stop this string of events and to prevent further damage to the WHATWG's image, please take the following actions:
- Domenic should stop making comments to me. The ratio of constructive to rude sentences is about 1:10. After many attempts to establish a respectful technical discussion, there is no further hope for that.
- Domenic should stop taking any actions that affects my work and input, such as censorship.
- Please delete or hide his rude comment to steer the discussion towards technical focus.
- Please reopen the new issue and delete or hide his misleading comment, so implementation details can be discussed there and the original issue can focus on its own concerns, as requested by Domenic.
- Please restore my censored comment.
Please take these actions without delay, by Monday night (PST).
With appreciation,
Kaleidea