You have chosen to visit this page. GREAT! We are happy about everybody contributing to the X2Go project. May the contribution be documentation, translation, communication, coding & bugfixing or core development.

To get an idea on who-is-who in the project please take a look at the X2Go project's organigram.

Your apprenticeship as an X2Go contributor/developer could look like this:

1. Get a wiki account, while discovering X2Go, become aware of lacking documentation, doc-bugs, etc. → help us fixing those
2. Feed us with bug reports. How to report X2Go (upstream) bugs is documented here.
3. Show up on IRC or Matrix
4. Checkout the pages in the development namespace of this wiki.
5. Make sure that you know how to use Git (VCS software), if you have questions contact me (Mike) on this list, Reinhard and Morty are also very familiar with Git issues
6. Set up your local development workspace.
7. Make sure you understand the code structure and the session ,,handshake'', study the code!!!
8. Whenever you find a bug, an improvement, try to fix it, try to implement it. what you come up with → Send it as a patch to the developers' mailing list for reviewing.
9. If your patches and ideas prove to be generic and community suitable (we cannot serve special use cases in X2Go upstream(!!!), the community version of X2Go aims to be generic and adaptable to local setups), then you may get write access to the code repository some time in the future.

If you have any further questions about becoming an X2Go contributor (or even developer), please contact us on our developers' mailing list.