With The Good Suite being an open source project, you might decide that you want to contribute to the project. On this page you will find the resources related to this.
The first logical step is to join the different community aspects of The Good Suite. These can be found on the Community page. That is to say, they will be once they are present, which they aren't yet right now.
The next thing to know about is the Issue Tracker. We use the issue tracker provided by github. Once you're sure your problem is a bug (or a feature/enhancement request) that's the place to report it. You should search it if the issue has been raised before to avoid filing duplicate issues.
It should be noted that you should read the note for the git repository before you just find it from the github page.
The git repository can also be found on github. However, it should be noted that github is mainly used as a host for our central git repository (and the issue tracker) and not much more than that. Github is used in a more traditional fashion from the command line (despite working on Windows a lot of the time) and contributions should adhere to standards that aren't enforced by git such as the line length of commit messages.
The aim is to respond to merge requests on github, but the content itself should be of good quality even when not viewed through the lense of github.
Alongside the normal repository and tracker, there's also the Good Samples repository and issue tracker, in which govern the Good Samples, which are a second product of The Good Suite.
Any code contributions will need to be under the MIT license the code is released under, with the exception that the copyright notice can be changed (because the current isn't too liked and it might be changed in the future).
A statement to this effect will have to be sent through email (to avoid using specific services as much as possible).