Technology

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 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.