I’d say you’re certainly part of the team, Wakefield - PsychoPy is a community effort, not an exclusive club. Anyone can contribute changes to the code or documentation - all it takes is an account at Github. Ideally, your crib sheet would become part of the official documentation. As it is solving pain points for many users, it would be most effective if it had the profile of being with the rest of the documentation.
e.g. the online participant documentation page under discussion is found here on the PsychoPy Github site:
Instructions on becoming a psychoPy developer are here (where being a “developer” includes simply proposing changes to the docs):
And specific info about working with the documentation source files are here:
There is a bit of a learning curve at first, but it is mainly about how to use Git - once you have a handle on that, you’ll be able to make contributions to any open-source project. But for very simple changes (e.g. correcting typos in the docs), you can actually do the changes entirely within the Github site - just fork
psychopy/psychopy to a branch in your own account, and click the “edit” icon to make changes directly in the web browser. You can then submit a pull request to have the change moved from your branch back to the main PsychoPy repository.
This all applies to a relatively old hand like Marc as well. Users learning to do new things are the best people to propose changes to the documentation - developers who are contributing to the code itself are less likely to be poring over the documentation to learn how to do things, so they don’t notice deficiencies or out-of-date content.