Big Tech Wants You Trapped. The Open Web Sets You Free
-
No, they're completely right. Destructive, hateful opinions are not "just different opinions", they are actively destroying and bastardizing the discussions and making people feel unwelcome. They are not to be tolerated unless you want all normal people to leave and only the assholes to stay, just like what is happening with Twitter.
Fuck nazis and their sympathizers.
-
The problem is giving them a platform has let the extremists on the Right to come to power in the United States. Hearing differing opinions is one thing, tolerating the attacking of minorities and the destruction of a functioning government is another. How much debate are we supposed to engage in before we say enough is enough?
-
1: we've been waiting for the masses to arrive for about 2 years now, there was a peak, then a significant fall off
2: there is a solution, and we talk about it all the time: simplify onboardingI think you may just not be hanging around in the instance development and community servers if you're not seeing these conversations
-
Yeah but who doesn’t have at least a cell phone these days (unless you’re making many accounts)? They’re useful for 2 factor authentication too.
-
It will be me. You have freedom of speech. I am also free to ignore, mock or ostracize you if you spout hateful nonsense near me.
-
Pretty much everyone has, but that's not the problem here. What if you don't really want to give them a unique identification number like that? What if you don't want them them to know you that well? What if you're not even planning to use your real name at all.
-
What's your normal workflow?
Our designers use Figma and send us a link so we can see the various user flows, leave comments, etc. It's not very FOSS-friendly though, but the workflow is pretty good.
Here are a few options that I think could work:
- wiki - many projects use them for documentation, and you can easily upload images and videos, track revisions, etc; can also be used for project management
- something self-hostable, like penpot - more UX-specific tools, but probably not what you're familiar with
- forum - similar features as GitHub issues!/discussions, but maybe less intimidating? Keeps GitHub focused on implementation details and less chatty
- something else?
What infra do you expect to be there before you jump in? I'm working on a project I'd like to unveil hopefully this year that could really benefit from UX, so I'm genuinely interested in figuring this out.
-
Thanks for the video, it was great!
What frustrated me, though, was that she joined Bevy by keeping at it and going out of her way to prove her worth (i.e. the way devs get into projects), but then suggests devs go out of their way instead to attract project managers (and designers, presumably). That's not very fun to hear, but I guess that's the way it is.
there is a link to “GitHub” in the contact information.
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.
In general, I recommend coming with the intention of being assigned work ("I'm a UX designer and I'd love to help mock up stuff"), but also with ideas on how to improve what's there (e.g. "I found <X> frustrating and would love to show some mockups on how to improve it"). That's the ideal scenario IMO, because it offers to reduce work of existing maintainers without asking for anything in return.
However, that's apparently not happening.
Where’s the contributing guidelines for non-developers?
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?
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'm genuinely interested here because I'm hopefully going to launch a FOSS project this year, and I would like to facilitate that type of discussion, I just don't know how to do that effectively. To me, linking a chat and the repo is enough, but maybe it's not.
-
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.
-
This is a frustrating nut to crack, thanks for your patience.
I'll ask our UX people at work what they'd expect. UX and project management are pretty far down the list of considerations when starting/joining a FOSS project, so thanks for your insights.
-
I am a dev. The example I gave was meant to be a POV, but in hindsight this was not clear. Because of this, I cannot meaningfully answer your question.
This topic still deserves genuine and transparent research. I have no doubt there are people already working on this, but I have not seen any notable results.
[OFF-TOPIC] To be completely frank with you, I've think that our communities (federation and open-source) are too splintered. Not in the sense of head count (this is good) but in terms of duplicating and abandoning work (this is bad). We really need a way to get a community-pulse on what is generally needed/wanted. I am not sure what the solution for this is, but I know there is one.
-
This topic still deserves genuine and transparent research.
Agreed. I'll try asking our UX people and see what they'd expect/want.
(federation and open-source) are too splintered
I think that's a feature, not a bug, at least in the abstract sense.
For example, I think federation is a terrible solution to the general problem we're trying to solve here. It requires too much hosting costs for everyone to self-host, requires too much trust in the admin to properly horizontally scale, and is inherently complex, which scares people away (and some of that complexity seeps through to the user).
However, a lot of people think it's the bees knees, hence why we have Mastodon and Lemmy. I still think it's poorly designed for scale, so my projects aren't federated, but I certainly appreciate the people working on it in the meantime (I see it as a stopgap), and I do contribute fixes here and there (I was somewhat active in fixing bugs when I came to Lemmy).
We really need a way to get a community-pulse
This is tricky because there is no one community. It's better managed as separate communities instead of one large FOSS community.
So maybe projects just need a better way to gather feedback from users other than issue trackers. Projects really should do more polls.
