-
Notifications
You must be signed in to change notification settings - Fork 7
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
conduct issue #55
Comments
Could you please clarify you reasoning why a tension between specific members of broad Solid community should affect Solid WG moving forward?
Could you provide more details on how this situation would impact all what you are mentioning? |
@elf-pavlik we've both known Michiel for over 10 years and know that his reports are credible:
See also the quote in the thread from Emelia:
The issues raised extend beyond isolated incidents or private matters. In fact, additional community members have come forward to corroborate a pattern of bullying that has, regrettably, driven some away and contributed to an unhealthy environment. As we are on the verge of launching a new Working Group, it's absolutely critical that these serious allegations are addressed collectively. Leaving such concerns unaddressed risks casting a long shadow over the future and integrity of the project. |
I think the only situation when this incident could affect formation of WG would be a case when the person with misconduct allegation was proposed as a WG chair. Based on the latest WG draft from https://www.w3.org/2023/09/proposed-solid-wg-charter.html (also PRd in #56) this doesn't seem to be the case. I propose that we will bring this issue (#55) on the WG charter during next CG meeting and resolve it right away. I would also like to ask @michielbdejong if he thinks that this situation should affect process of WG creation in any way. |
@elf-pavlik the chairs are certainly a big consideration. I didnt know that the two chairs had been published on the w3.org site. Thank you for the info. |
Just seeing this issue now - fully agree with @elf-pavlik that it's unrelated to the current WG charter and the currently proposed co-chairs. |
@melvincarvalho given all the feedback, could you consider closing this issue? |
@elf-pavlik regarding the comments from the public institution Imec:
Would you agree that this conduct is unacceptable? What steps have been taken? Edit: would appreciate if you were able to share the relevant meeting minutes. |
https://hackmd.io/7hxOQtEmRwmbF_WwOYzjEg#conduct-issue Soon also archived in: solid/specification#591 |
@elf-pavlik could you and those that wish to close this first answer the two questions posed, regarding the comments from the public institution Imec
Alternatively, I'd also appreciate an opinion @pchampin I'd further point out this comment:
|
I agree that we can do better and I understand that the person who have written the harsh words also agreed in retrospective (an apology) I also would like to notice that the conduct happened in private (direct) email exchange. Besides that the contention point was related to an open source software which is not a direct work item of the CG. Last but not least, the person who was directly targeted with the harsh word agrees that this incident shouldn't affect process of WG creation
As I mentioned, a public apology was issued for the words said over a private conversation. Other than empathizing even stronger the Code of Conduct published by the CG, I don't see any further actions that need to be taken.
There is a very strong rough consensus that in no way this incident grants such a drastic reaction. I believe that there might be even a full consensus among all the active CG participants
Please keep in mind that Solid WG will operate under W3C Process: https://www.w3.org/2023/Process-20230612/#discipline
If you don't have trust in current W3C Process, please consider raising an issue upstream. @melvincarvalho based on the further responses to the linked mailing list thread I understood that you have personal history and possible resent which resonated with this situation. While everyone's emotional well being is important, please reflect if possibly an old personal grudge might be playing a role in motivating your reaction represented in this issue.
I believe that @pchampin as W3C Team Contact should have a the final word and let's all commit to trusting in his judgement. |
👍 |
|
This issue was opened on 2023-09-28 and the CG has deliberated on the proposal to "[c]onsider pausing the WG charter until this credible conduct issue is resolved". In the 2023-11-01 CG meeting, the group agreed to close this issue. @pchampin or the W3C Team in general can indeed have the "final word" as they're now aware of @melvincarvalho 's request. That said, any or further consideration on changing the progress status of the proposed charter is out of scope for this repository, as I've mentioned in the 2023-11-01 meeting. |
As I have been "summoned"... I don't have much to add to @elf-pavlik's very good summary above. Without minimizing the importance of good conduct in general, nor of this misconduct in particular, I believe it does not justify hindering the chartering process. |
Consider pausing the WG charter until this credible conduct issue is resolved, as it affects, test suite, reference implementations, reputation of the project, and the potential structure of the WG
https://forum.solidproject.org/t/migrating-from-nss-to-css/6856/5
The text was updated successfully, but these errors were encountered: