You can make your own alternatives, that’s the difference. If you think the mods/admins of those comms/instances aren’t doing well, then you could do better yourself. That’s the freedom that the fediverse gives you. You could not do the same on Reddit.

Not sure about that one but the following one:

In each language, the words for yes and no never change, regardless of which question they are answering.

This happens in Danish actually. Example:

Kan du lide is? (Do you like ice cream?)
Ja
Kan du ikke lide is? (Do you not like ice cream?)
Jo

So in Danish we have “ja” which means “yes” but “jo” is used instead when answering a negative question, so as to confirm what the negative question asked. This is kind of annoying in English cause if you ask “Do you not like ice cream?” then if you say “yes” does that mean “yes I like ice cream” or does it mean “yes I do not like ice cream”? That’s what “jo” disambiguates.

There’s also a link to Matrix, which I’m guessing is the preferred way to jump in and ask questions about how to contribute.

Yes but asking directly instead of consuming already-written guidelines is a much higher psychological hill to climb and doesn’t feel welcoming. You need to be very passionate to go to Matrix. Also, frankly speaking, UX people are very unlikely to have a user on Matrix or even know what it is or how it works. Developers on the other hand can easily figure this out. You need to be mindful of tech literacy when you’re trying to cater to UX people - they won’t know anything about Matrix probably.

In general, I recommend coming with the intention of being assigned work

I don’t think that’s bad, but for developers this is very easy with all the guidelines and the “good first issues” and all that. For UX people, none of these resources exist.

Where would you naturally look for this? With developers it’s easy, you look for “CONTRIBUTING.md” or similar in the repo, as well as hints from templates in issues and PRs. Some will have extensive style guides and whatnot, but most are pretty bare bones.

Should this go on the main website? Somewhere at the start of the technical docs? In the repo in a special place linked from the root?

At the very least this could be in the contributing guidelines on GitHub, but I think having it on the main website (a place much more familiar and friendly to non-technical people) is much better.

What about tooling? Should projects set up something like penpot (found after a search for FOSS Figma)? Or are designers okay with images on a wiki or something? Is it reasonable to ask them to submit a GitHub issue and engage that way (they could link to something else)?

I don’t know, I’m not a UX person. Ask them when they arrive. But I would think they can probably figure out to interact on GitHub issues if directed to do so. Developers intuitively know “Oh I want to contribute so I’ll need a GitHub account and then need to go look at issues” but UX people don’t know this.

To me, linking a chat and the repo is enough, but maybe it’s not.

I definitely don’t think that’s enough - UX people probably don’t even know what a “repo” is.

What do you mean by “invite”? What would that look like?

I don’t mean a literal invite - I mean that projects are rarely inviting for product managers and designer (let’s call them “UX people”) and rarely do they encourage those people to contribute.

Let’s take a look at Lemmy as an example (and please don’t misunderstand, this is not to bash Lemmy specifically, this happens for so many FOSS projects). Let’s put ourselves in the shoes of a UX person who wants to contribute to Lemmy. How would I (the imaginary UX person) do that?

Well, on join-lemmy.org there’s not really any links to anything to do with contributing but there is a link to “GitHub” in the contact information. As a UX person, I may have a vague idea what git and GitHub is, but obviously that’s not a tool that I use. So then I land on the git repository on GitHub. Oh great, there’s a “Contributing” section! It says:

Read the following documentation to setup the development environment and start coding

Oh. So that’s contributing code and stuff. So that’s not me. But okay since there’s nothing else, let’s try and go to the contributing guidelines anyway. But this just gives a technical overview of the different software components of Lemmy, and then goes into how to setup local development. This is all mumbo-jumbo to me, I know nothing about coding, I am a UX person.

My point is (and again, Lemmy is just an example here), none of these contributing guidelines are helpful unless you are a developer, and the fact that the contributing guidelines only caters to developers makes any UX person feel out of place, as if their expertise is not wanted or needed. This is what I mean when I say it is not very inviting to UX people. It is very inviting to developers though.

That’s how it should work for design as well. Contribute some designs that you think will improve the UX and if they’re desirable, someone will take up implementing them. If it’s easy (e.g. a new logo), it’ll get done right away, and if it’s more involved, it’ll get done as devs get time.

I agree! But how are designers supposed to know where to even start? There are “good first issues”, but those are also only for developers. Where’s the contributing guidelines for non-developers? You say “Designers and product managers are certainly welcome”, but this doesn’t look that welcoming to me!

My perspective of designers and product managers is that they like to own projects.

I think this is a bit of a mischaracterization. I don’t think a product manager has to “own” the project to help and be valuable to a project.

One project that does this quite well is bevy. See this video from one of the product manager contributors to bevy: https://www.youtube.com/watch?v=u3PJaiSpbmc

people good at UX don’t seem to care as much about FOSS and the open web

I’m not sure this is true - at least I have an alternative explanation.

People who do the UX design and all that are rarely invited into the process. Open source projects often look for “maintainers” but this almost exclusively means “developers”.

There’s documentation and contributing guidelines for developers. Where is the same material for product managers or designers?

We don’t get product managers and designers in FOSS because they’ve never been invited.

The major platforms are convenient.

But the open web offers something better: genuine ownership, community governance, and independence.

This has a kind of underlying connotation that the open web can’t be convenient. This is not true.

It is true that lots of platforms on the fediverse (Lemmy included) don’t have the best user experience and user journey flow. But that’s not how it has to be. We don’t have to accept that as a given.

It’s the same problem that Linux faces, where UX issues aren’t prioritised because the user base is technical enough to deal with the bullshit. We can’t let the same thing occur to the fediverse.

Some people are trying: https://github.com/LadybirdBrowser/ladybird

Honestly I kinda wish the Rust devs would rather go and support a project like Redox OS and then maybe we can have less drama about all this.

I like the optimism, but I’d see it before I believe it.

Ultra!

I mean it is censorship. But not all censorship is bad.

But this system still makes airflow right? Just without moving parts.

Yea, definitely. Also just the fact that you’re here says a lot. I don’t think you can find many (if any) of these “normal” users on the fediverse.

Basically, any time a UI hops in front of you and goes ‘Wait! This is important!’ people get annoyed

It honestly baffles me how this keeps being a thing. Not just for OSs but for a lot of websites too. And the wild thing is that most of the time, it’s not even that important and the user does not and should not care about it.

would be a good thing if you could ensure every user would be guaranteed to not be greeted with any issues upon reboot from said update.

Honestly this sounds like it’d be so far in the future that it’s not even realistic to contemplate right now. We’re clearly not even close to this being the reality.

You’re not alone, I’ve been screaming into the void about this for a long time too. People keep saying “Linux is user friendly enough these days for even non techy people” and I’m sorry but it’s totally not.

I think most Linux users just don’t realize how technologically illiterate most people are. Most people can barely use a browser and send emails. They absolutely don’t want to mess with anything related to “updates” that they have no idea wtf is doing to their system anyway.

Downvoted for popular opinion.

Yea this has really big astroturfing vibes.

What do all you guys use these setups for?

most of the cost of [anything] goes to publishers, not the creators

My edit obviously. It does feel like that though. I pay Netflix, not the people making the movie. For games it is at least a bit better - I pay Valve (Steam) and the publisher but at least some of it goes directly to the devs. But it could be better still I suppose. But I’d honestly be okay if we got a Steam-like platform for series and movies where I could buy the ones I want without any subscriptions.