Big Tech designed their platforms to keep you trapped. YouTube, X, Instagram, and TikTok aren't neutral spaces. They're businesses built on capturing your attention and data. Their algorithms, notification systems, and content policies all serve one purpose: keeping you engaged on their terms. And their terms alone. There's no freedom
  • SorteKanin@feddit.dkEnglish
    2·
    5 hours ago

    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.

    • sugar_in_your_tea@sh.itjust.worksEnglish
      2·
      5 hours ago

      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.