Diseased Open Source Software Community - it's about ethics in Code of Conducts

[Marvin]

And Unabomber? He was an anti-capitalist anti-corporation person, what does the woke crowd have against him?

He passionately hated communists and communism.

 

[Kapros]

I had no idea the Unabomber was antisemitic. Neat.

 

[Kendall Motor Oil]

You can't make this shit up. These are the two most permissive licenses. MIT is literally "do what the fuck you want but credit us" in a more appropriate language, BSD depending on the version is the same with the most restrictive extra option being "but don't put our name on advertisements".

So you support pedophiles and George Bush?

 

[Troonos]

A CODE OF CONDUCT VIOLATION. Sonny Piers is now verboten to speak about by janny dictact.

He clearly didn't fellate the tranny cock hard enough.

 

[UERISIMILITUDO]

This tranny shit is gonna be the downfall of open source. At least Microsoft and Apple get pulled back from the brink if it starts affecting profits.

As has been pointed out many times before, the corporations are causing this. They can't get away with assassinating volunteer programmers, so they use subversion instead. They'll do anything except compete. I don't give a fuck about open source anyway, which is just the neutered version of Free Software. Let the people doing free labour for big businesses get fucked into the dirt by those same businesses as thanks.

 

[anustart76]

EBUSSY REPLIES - Emmanuele Bassi - Geek, husband, lover, software developer, Londoner. Not necessarily in that order. - He/him. - DIRECTOR OF THE BOARD

Some ebussy memes, courtesy of /g/

 

[RU486]

The more I look at the governance arrangements for the GNOME foundation, the directors really fucked themselves by putting in place a Code of Conduct committee who then wrote it into the code of conduct that it applied to Directors as well. Typically there will be a board Code of Conduct written separate from the general organizational code, as the role of a director is significantly different to one of a employee or member.

I look forward to seeing what the Code of Conduct Committee reports in their transparency report for this period.

Spoiler: Code of Conduct

Creating a Welcoming Community​

Thank you for being a part of the GNOME project. We value your participation and want everyone to have an enjoyable and fulfilling experience. Accordingly, all participants are expected to follow this Code of Conduct, and to show respect, understanding, and consideration to one another. Thank you for helping make this a welcoming, friendly community for everyone.

If you witness or experience any behavior that violates our Code of Conduct, please do not hesitate to report it to our community moderators. Together, let’s ensure a safe and inclusive environment for all members.

Report an incident

---

Scope​

This Code of Conduct applies to all GNOME community spaces, including, but not limited to:

• Issue tracking systems – bugzilla.gnome.org
• Documentation and tutorials – developer.gnome.org
• Code repositories – git.gnome.org and gitlab.gnome.org
• Mailing lists – mail.gnome.org
• Wikis – wiki.gnome.org
• Chat and forums – irc.gnome.org, discourse.gnome.org, GNOME Telegram channels, and GNOME groups and channels on Matrix.org (including bridges to GNOME IRC channels)
• Community spaces hosted on gnome.org infrastructure
• Any other channels or groups which exist in order to discuss GNOME project activities
• All event venues and associated spaces, including conferences, hackfests, release parties, workshops and other small events
• All areas related to event venues: vendor exhibit halls, staff and meal areas, connecting infrastructure like walkways, hallways, elevators, and stairs
• Sponsor events, either on-site or off-site
• Private events off-site that involve one or more attendees
• Social events around the main event
• Private conversations taking place in official conference hotels

Communication channels and private conversations that are normally out of scope may be considered in scope if a GNOME participant is being stalked or harassed. Social media conversations may be considered in-scope if the incident occurred under a GNOME event hashtag, or when an official GNOME account on social media is tagged, or within any other discussion about GNOME. The GNOME Foundation reserves the right to take actions against behaviors that happen in any context, if they are deemed to be relevant to the GNOME project and its participants.

All participants in GNOME community spaces are subject to the Code of Conduct. This includes GNOME Foundation board members, corporate sponsors, and paid employees. This also includes volunteers, maintainers, leaders, contributors, contribution reviewers, issue reporters, GNOME users, and anyone participating in discussion in GNOME community spaces. For in-person events, this also includes all attendees, exhibitors, vendors, speakers, panelists, organizers, staff, and volunteers.

Reporting an Incident​

If you believe that someone is violating the Code of Conduct, or have any other concerns, please contact the Code of Conduct committee.

Our Standards​

The GNOME community is dedicated to providing a positive experience for everyone, regardless of:

• age
• body size
• caste
• citizenship
• disability
• education
• ethnicity
• familial status
• gender expression
• gender identity
• genetic information
• immigration status
• level of experience
• nationality
• personal appearance
• pregnancy
• race
• religion
• sex characteristics
• sexual orientation
• sexual identity
• socio-economic status
• tribe
• veteran status

Community Guidelines​

Examples of behavior that contributes to creating a positive environment include:

• Be friendly. Use welcoming and inclusive language.
• Be empathetic. Be respectful of differing viewpoints and experiences.
• Be respectful. When we disagree, we do so in a polite and constructive manner.
• Be considerate. Remember that decisions are often a difficult choice between competing priorities. Focus on what is best for the community. Keep discussions around technology choices constructive and respectful.
• Be patient and generous. If someone asks for help it is because they need it. When documentation is available that answers the question, politely point them to it. If the question is off-topic, suggest a more appropriate online space to seek help.
• Try to be concise. Read the discussion before commenting in order to not repeat a point that has been made.

Inappropriate Behavior​

Community members asked to stop any inappropriate behavior are expected to comply immediately.

We want all participants in the GNOME community have the best possible experience they can. In order to be clear what that means, we’ve provided a list of examples of behaviors that are inappropriate for GNOME community spaces:

• Deliberate intimidation, stalking, or following.
• Sustained disruption of online discussion, talks, or other events. Sustained disruption of events, online discussions, or meetings, including talks and presentations, will not be tolerated. This includes ‘Talking over’ or ‘heckling’ event speakers or influencing crowd actions that cause hostility in event sessions. Sustained disruption also includes drinking alcohol to excess or using recreational drugs to excess, or pushing others to do so.
• Harassment of people who don’t drink alcohol or other legal substances. We do not tolerate derogatory comments about those who abstain from alcohol or other legal substances. We do not tolerate pushing people to drink, talking about their abstinence or preferences to others, or pressuring them to drink – physically or through jeering.
• Sexist, racist, homophobic, transphobic, ableist language or otherwise exclusionary language. This includes deliberately referring to someone by a gender that they do not identify with, and/or questioning the legitimacy of an individual’s gender identity. If you’re unsure if a word is derogatory, don’t use it. This also includes repeated subtle and/or indirect discrimination.
• Unwelcome sexual attention or behavior that contributes to a sexualized environment. This includes sexualized comments, jokes or imagery in interactions, communications or presentation materials, as well as inappropriate touching, groping, or sexual advances. Sponsors should not use sexualized images, activities, or other material. Meetup organizing staff and other volunteer organizers should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
• Unwelcome physical contact. This includes touching a person without permission, including sensitive areas such as their hair, pregnant stomach, mobility device (wheelchair, scooter, etc) or tattoos. This also includes physically blocking or intimidating another person. Physical contact or simulated physical contact (such as emojis like “kiss”) without affirmative consent is not acceptable. This includes sharing or distribution of sexualized images or text.
• Violence or threats of violence. Violence and threats of violence are not acceptable – online or offline. This includes incitement of violence toward any individual, including encouraging a person to commit self-harm. This also includes posting or threatening to post other people’s personally identifying information (“doxxing”) online.
• Influencing or encouraging inappropriate behavior. If you influence or encourage another person to violate the Code of Conduct, you may face the same consequences as if you had violated the Code of Conduct.
• Possession of an offensive weapon at a GNOME event. This includes anything deemed to be a weapon by the event organizers.

Safety versus Comfort​

The GNOME community prioritizes marginalized people’s safety over privileged people’s comfort, for example in situations involving:

• “Reverse”-isms, including “reverse racism,” “reverse sexism,” and “cisphobia”
• Reasonable communication of boundaries, such as “leave me alone,” “go away,” or “I’m not discussing this with you.”
• Criticizing racist, sexist, cissexist, or otherwise oppressive behavior or assumptions
• Communicating boundaries or criticizing oppressive behavior in a “tone” you don’t find congenial

The examples listed above are not against the Code of Conduct. If you have questions about the above statements, please read our document on Supporting Diversity.

Outreach and diversity efforts directed at under-represented groups are permitted under the code of conduct. For example, a social event for women would not be classified as being outside the Code of Conduct under this provision.

Basic expectations for conduct are not covered by the “reverse-ism clause” and would be enforced irrespective of the demographics of those involved. For example, racial discrimination will not be tolerated, irrespective of the race of those involved. Nor would unwanted sexual attention be tolerated, whatever someone’s gender or sexual orientation. Members of our community have the right to expect that participants in the project will uphold these standards.

If a participant engages in behavior that violates this code of conduct, the GNOME Code of Conduct committee may take any action they deem appropriate. Examples of consequences are outlined in the Committee Procedures Guide.

Procedure for Handling Incidents​

• Reporter Guide
• Moderator Procedures
• Committee Procedures Guide

Code of Conduct Committee​

The Code of Conduct Committee’s appointed members are:

• Anisa Kuci
• Federico Mena Quintero
• Michael Downey
• Rosanna Yuen

Please see the Committee page for more information.

I liked that they felt that they needed to include veteran status as a demographic which needs protection in the GNOME circles and that they won't even entertain something like 'reverse racism'.

 

[AnOminous]

I liked that they felt that they needed to include veteran status as a demographic which needs protection in the GNOME circles and that they won't even entertain something like 'reverse racism'.

There's no such thing as "reverse racism." It's just plain old racism.

 

[WTBOnlineFather]

GNOME: "We are dedicated to providing a positive experience for everyone regardless of [everything]
Also GNOME:

Safety versus Comfort​

The GNOME community prioritizes marginalized people’s safety over privileged people’s comfort, for example in situations involving:

• “Reverse”-isms, including “reverse racism,” “reverse sexism,” and “cisphobia”
• Reasonable communication of boundaries, such as “leave me alone,” “go away,” or “I’m not discussing this with you.”
• Criticizing racist, sexist, cissexist, or otherwise oppressive behavior or assumptions
• Communicating boundaries or criticizing oppressive behavior in a “tone” you don’t find congenial

The examples listed above are not against the Code of Conduct. If you have questions about the above statements, please read our document on Supporting Diversity.

So basically trannies get to push you around and act belligerent and you don't get to push back because the rules classify getting bullied as a white cissy as a "positive experience." Lmao. Let it all burn

 

[Kola]

I liked that they felt that they needed to include veteran status as a demographic which needs protection in the GNOME circles and that they won't even entertain something like 'reverse racism'.

This is bread and butter in tech corpos. They didn't come up with this shit, just aped it.

 

[innocent jogger]

I would like to laugh and say "Imagine using GNOME in [year]" but my daily driver is a Frankenstein Linux mess that incorporates quite a bit of GNOME software when I need it. The GNOME DE itself is shit imho (even GNOME 2) but there are a lot of good programs. I'm starting to call GNOME "The Windows of Linux"-- Gay, bloated and nothing but bad decisions for a long time now, but has a lot of good programs written by people using it.

As has been pointed out many times before, the corporations are causing this. They can't get away with assassinating volunteer programmers, so they use subversion instead. They'll do anything except compete. I don't give a fuck about open source anyway, which is just the neutered version of Free Software. Let the people doing free labour for big businesses get fucked into the dirt by those same businesses as thanks.

Haha you're the guy who was defending pedos a few days ago. (I can link to it if you want to argue.) Are you a troon? Are your "friends" on your profile page your socks or fellow troons? Inquiring minds want to know...

 

[WhiteNight]

I liked that they felt that they needed to include veteran status as a demographic which needs protection in the GNOME circles and that they won't even entertain something like 'reverse racism'.

The GNOME CoC is basically copied from the Geek Feminism Code of Conduct with only superficial changes:

https://geekfeminismdotorg.wordpress.com/about/code-of-conduct/

https://archive.is/qLKXJ

As might be guessed from the name, it's loaded with social justice tropes, and is one of the absolute worst. Any organization which adopts it has been fully captured.

As an example trope,

There's no such thing as "reverse racism." It's just plain old racism.

They agree that there is no such thing, but not in the same way. They say reverse-isms are not in violation of the CoC because

‘Reverse’ -isms, including ‘reverse racism,’ ‘reverse sexism,’ and ‘cisphobia’ (because these things don’t exist)

You can say "kill whitey" all day and that is not a violation because "reverse racism" doesn't exist. Something about prejudice plus power.


There was pushback in one case. In 2018, the FreeBSD adopted what was basically the GF CoC, although they removed some of the more extreme parts (including the above quoted bit). There was a significant outcry over many of these unhinged clauses, and FreeBSD eventually (in 2020) backed off and switched to a (relatively) normal one.

FreeBSD archives:
Original code of conduct prior to 2018
Geek Feminism based one implemented in 2018
Code of conduct in use since 2020

 

[The Real Slim Shady]

I'm starting to call GNOME "The Windows of Linux"-- Gay, bloated and nothing but bad decisions for a long time now, but has a lot of good programs written by people using it.

This is an astonishingly good comparison. Gnome 2 was like windows 98/XP - not too ugly and functional. Compact interfaces with small icons and a shitton of GUI tool programs. Then they customized the shit out of it and finally made Gnome 3 which looks like Windows 11 - rounded corners, invisible scroll bars and other shit. And It goes without saying, the sheer amount of wasted space on screen. Their paddings are screen-space-positive. Plus size margins. It's as if they all suppose everyone has an at least 2k HiDPI monitor and is happy to fit at most two applications on it at the same time. I would go as far as to say that Gnome 3 is a worse UI than stock Windows 11. It's the shittiest DE I've seen.

I guess that makes Ubuntu Unity correspond to the failed UI experiment, Windows 8.1.

 

[UERISIMILITUDO]

Haha you're the guy who was defending pedos a few days ago. (I can link to it if you want to argue.) Are you a troon? Are your "friends" on your profile page your socks or fellow troons? Inquiring minds want to know...

Make a thread to sperg about me if it's so important, innocent nigger. I won't respond to anything here beyond this.

 

[UERISIMILITUDO]

Russ Cox is stepping down to hand Go over to two other Google employees:
https://groups.google.com/g/golang-dev/c/0OqBkS2RzWw (archive)

Hi all,

Starting September 1, Austin Clements will be taking over as the tech lead of Go: both the Go team at Google and the overall Go project. Austin is currently the tech lead for what we sometimes call the “Go core”, which encompasses compiler toolchain, runtime, and releases. Cherry Mui will be stepping up to lead those areas.

I am not leaving the Go project, but I think the time is right for a change.

It’s important to remember that tech lead—like any position of leadership—is a service role, not an honorary title. I have been leading the Go project for over 12 years, serving all of you, and trying to create the right conditions for all of you to do your best work. Large projects like Go absolutely benefit from stable leadership, but they can also benefit from leadership changes. New leaders bring new strengths and fresh perspectives. For Go, I think 12+ years of one leader is enough stability; it’s time for someone new to serve in this role. In particular, I don’t believe that the “BDFL” (benevolent dictator for life) model is healthy for a person or a project. It doesn’t create space for new leaders. It’s a single point of failure. It doesn’t give the project room to grow. I think Python benefited greatly from Guido stepping down in 2018 and letting other people lead, and I’ve had in the back of my mind for many years that we should have a Go leadership change eventually.

If you haven’t worked on the compiler toolchain or runtime, you may not know Austin or Cherry well. Austin has been working on Go at Google since 2014, Cherry since 2016. Their judgment is superb and their knowledge of Go and the systems it runs on both broad and deep. When I have general design questions or need to better understand details of the compiler, linker, or runtime, I turn to them. I’m very excited that we have such great new leaders available for this change. I have full confidence in Austin and Cherry stepping up, as well as in Roland Shoemaker continuing to lead Go security and Rob Findley and Hana Kim continuing to lead Go tools and IDE support.

I am going to consciously step back from decision making and create space for Austin and the others to step forward, but I am not disappearing. I will still be available to talk about Go designs, review CLs, answer obscure history questions, and generally help and support you all in whatever way I can. I will still file issues and send CLs from time to time, I have been working on a few potential new standard libraries, I will still advocate for Go across the industry, and I will be speaking about Go at GoLab in Italy in November.

I will be shifting my focus to work more on Gaby and Oscar, trying to make useful contributions in the Go issue tracker to help all of you work more productively. I am hopeful that work on Oscar will uncover ways to help open source maintainers that will be adopted by other projects, just like some of Go’s best ideas have been adopted by other projects. At the highest level, my goals for Oscar are to build something useful, learn something new, and chart a path for other projects. These are the same broad goals I’ve always had for our work on Go, so in that sense Oscar feels like a natural continuation.

I am incredibly proud of the work we have all accomplished together, and I am confident in the leaders both on the Go team at Google and in the Go community. You are all doing remarkable work, and I know you will continue to do that.

The exact details of this transition are yet to be decided. Part of the point of this mail is to ensure that we can discuss those details publicly. Austin and I are both committed to making the change seem like a non-event except for the Go project becoming stronger and better. Again, I’m not leaving Go and will still be around and participating as an individual contributor.

Please always feel free to continue to reach out whenever you need anything. And my thanks and congratulations to Austin and Cherry for stepping into their new roles.

Best,
Russ

This Gaby and Oscar project he mentions is some neural network nonsense somehow preferable to removing the drudgery directly:
https://go.googlesource.com/oscar/+/refs/heads/master/README.md (archive)

For those who don't know, the official Go programs spy on the user to serve Google. This is the only innovation from this millennium I believe Go has adopted.

 

[Hồ Chí Minh]

For those who don't know, the official Go programs spy on the user to serve Google.

Eh, what?

 

[mentally retarded user]

Total GNOMEr Death

 

[UERISIMILITUDO]

Eh, what?

The official Go programs contain telemetry mechanisms. Russ Cox promoted the idea here:
https://research.swtch.com/telemetry-intro (archive)

How do software developers understand which parts of their software are being used and whether they are performing as expected?

Thinking is too fucking hard.

The modern answer is telemetry, which means software sending data to answer those questions back to a collection server. This post is about why I believe telemetry is important for open-source projects, and what it might look like to approach telemetry in an open-source-friendly way. That leads to a new design I call transparent telemetry.

This transparent telemetry is transparent because it's opt-out.

He goes on to explain how thinking about the software, receiving bug reports, and asking the users aren't good enough. No, it has to be enabled by default or else it's just not useful:

I believe that the choice between invasive tracking and doing nothing at all is a false dichotomy, and it’s harming open source. Not having basic information about how their software is used and how well it is performing puts open-source developers at a disadvantage compared to commercial software developers.

Hey, being unable to spy on the programmers constantly and control their every move is also a disadvantage, to some people.

To be clear, I am only suggesting that the instrumentation be added to the Go command-line tools written and distributed by the Go team, such as the go command, the Go compiler, gopls, and govulncheck.

• The system is on by default, but opting out is easy, effective, and persistent. [Update, 2023-02-24: The design has been changed to be opt-in.]

That link leads nowhere, and isn't in the WWW archive I checked. Anyway, here's the MicroSoft GitHub issue from last year:
https://github.com/golang/go/issues/58894 (archive)

Here's what I believe to be the current documentation which shows it's still in place, and the system still collects it, but a more careful reading shows that it's technically opt-in now:
https://go.dev/doc/telemetry (archive)

Lastly, I'll only link to this for effect, but at one point the Google employees were calling people who disagreed with this evil violators of the Code of Conduct:
https://circumstances.run/@davidgerard/109848768306100450 (archive)

 

[AnOminous]

Lastly, I'll only link to this for effect, but at one point the Google employees were calling people who disagreed with this evil violators of the Code of Conduct:

That's the whole point of ramming CoCs into everything, so the people who are actually running everything can instantly just declare anyone opposing their spying agenda doubleunplusgood just by accusing them of violating some unintelligible CoC.

Do not let random people ram their CoCs into you.

 

[Hồ Chí Minh]

Lastly, I'll only link to this for effect, but at one point the Google employees were calling people who disagreed with this evil violators of the Code of Conduct:
https://circumstances.run/@davidgerard/109848768306100450 (archive)

David Gerard is a serial liar of Trumpian levels. Never trust anything he says as he will lie just to prove a point and when found out he will just shamelessly lie about his lying. Some of his stuff is covered in other threads there: https://kiwifarms.st/search/26968542/?q=David+Gerard&o=date

The rest of your post is a very long-winded way of saying it's been opt-in for a year and a half, and what you claimed just isn't true.

You seem desperate to turn this into a language sperg thread. every chance you get. Go create a hacker news account or something.