Elias @eliasr@librem.one

The GNOME Code of Conduct says: Be friendly. Be empathetic. Be respectful.

The GNOME Foundation signed an "open letter" accusing a software freedom activist of being "misogynist, ableist, and transphobic".

Questions:

(1) Is the letter in line with the GNOME Code of Conduct?

(2) Is it okay for the GNOME Foundation, as an organization, to sign something like that?

Personally I lean towards "no" on both questions, but I would like to hear what you think, especially GNOME developers.

#gnome

@lionirdeadman@fosstodon.org

done

@lionirdeadman@fosstodon.org

ok

@trregeagle Wohoo, congratulations!

Prepare yourself for some tinkering. 🙂
I found the forum at https://forums.puri.sm/ very helpful.

@jonarvid Yes, they certainly do take their time with the shipping.

Look on the bright side, though: by the time you get it, there's a good chance these fixes have been upstreamed so MMS can work for you out of the box. 😉

@clacke If you have time, I would be interested to hear what you think about those things (see also above):

- The GNOME Foundation signing the "open letter" as a whole organization, given how it is phrased and how it references inaccurate sources in the appendix.

- The GNOME Foundation signing something that would have been a clear violation of the GNOME code of conduct if posted in their own space.

For me it's hard to understand how they could do that, I really wonder what is behind it.

@libreleah

> pro-virus stance?

Not sure, but maybe @anonymoose is hinting at that some people (not me!) call copyleft licenses "viral" because they tend to spread. 🙂

@clacke

Also, since you mentioned the GNOME Code of Conduct, the "open letter" itself would be a violation of that code of conduct if it had been posted in GNOME community spaces.

The code of conduct says, for example: Be friendly, Be empathetic, Be respectful. The open letter is very far from that.

While I understand that the GNOME Foundation can say the open letter is on Github and thus outside of GNOME community spaces so the code does not apply, to me it still seems inappropriate.

2/2

@clacke

I don't mean that they voice their opinion that RMS behavior is a problem, that is not strange.

What I mean is strange is that the GNOME Foundation does it through that "open letter" given how it is phrased and how it references inaccurate sources in the appendix. I saw you wrote about that earlier so I think you understand what I mean. Otherwise see how the problems with the open letter are explained here: https://edsantos.eu/on-stalman/

1/2

@clacke

> I wanted to dig up a definitive
> reference for when Gnome
> left GNU

Interesting! I hope you succeed.

While you're at it, maybe you could see if there is a reference for when it became acceptable for the GNOME Foundation to actively engage in dishonest personal attacks such as the "open letter"?

Now I'm not talking about individual people signing that, but the fact that GNOME Foundation as an organization signed it. I find that very strange.

@bastian @fribbledom

OK then, thanks for explaining.

@fribbledom So someone decided to no longer give credit to #GNU, and they do that change without explaining in the commit message what the change actually is. The commit message should say "remove GNU" since that is what the commit is doing.

Apparently they don't want the commit message to show what they are actually doing.

Is that supposed to be funny?

This is an excellent statement from the FSF India about the current #RMS controversy:
https://fsf.org.in/news/board-statement-2021/

"Unfortunately many of the arguments made against him were based on misunderstanding and half truths. More dangerous is concerted attack on RMS vilifying him and trying to isolate him. FSF India condemns this action. There is no freedom more important than freedom of thought and expression."

To understand the background, see for example this: https://edsantos.eu/on-stalman/

#freedom #fsf

@IceWolf

> those mobs /do/ exist!
> This totally isn't one of them, though

Excuse me but if you think that, then I really think you should read and think some more about it. I recommend reading this: https://edsantos.eu/on-stalman/

@haskal @mithrandir @tindall@cybre.space

Listening to: John Lennon, Working Class Hero

[...]

When they've tortured and scared you for twenty odd years

Then they expect you to pick a career

When you can't really function you're so full of fear

[...]

Keep you doped with religion and sex and TV

And you think you're so clever and classless and free

But you're still fucking peasants as far as I can see

[...]

@jonarvid Nej, inte jag i alla fall, men kul att det går såklart.

Jag kollade nu, i "Account Settings" hittar jag under "Display Settings" en dropdown-lista med olika språk, fast svenska verkar inte finnas med. Kanske krävs en nyare version för att svenska ska dyka upp där?

@bugaevc@mastodon.technology

For me, being a fan of free software and so on, this seemed like a bad thing with rust. I want to know what the source code is, including source code for compilers. I want to say "here is the rustc source code, now build rustc from source" without any extra downloads being necessary.

Do you understand what I mean?

Is this a real problem or is it just me not understanding? If so, could you explain?

@bugaevc@mastodon.technology

Building everything from source like that worked for everything except rustc, including the compiler gcc used to build most other stuff.

For gcc it was possible to download the source code of gcc and then build gcc from that source code.

That was not possible for rustc because when building rustc it insisted on downloading a bunch of stuff as part of the build process.

(to be continued)

@bugaevc@mastodon.technology

Rust does seem great in many ways but when I was playing around with Linux From Scratch (LFS) it was a pain for me that one package I needed to build was written in Rust. Then I had to build rustc and it turned out that rustc could not be built from source without an internet connection. I had things setup so that I first downloaded all source code I needed, then as a second step I built everything from that source code.

(to be continued)