Team information and roles are available on the homepage.
G System development has lots of different aspects, not just writing code. Thus what team members do varies greatly, but still everything is necessary in the end to make the project complete. The team has so far been very stable, which means there is hardly any team member fluctuation.
The G System develops slowly but consistently. There is usually not tons of code changed every day. Rather, actual changes are well thought about and sometimes there is no code change for weeks. Thus, code that is written hardly gets thrown away later, as it is well thought about in the first place. Thus, our way of developing the G System is slow, but steady and consistent.
It is important for us not just to write the code, but also to make sure the project as a whole is well documented, that the web page is maintained and so on. So there is lots of things going on not reflected in the code itself.
Anton Melser created the documentation infrastructure and writes some documentation as well as various parts of the source code.
Gerald Degeneve is the webmaster. He did all the website design and implementation (three times, we owe him a lot). Apart from mastering the web he writes some source code, in particular physics agent design and implementation. He's also the main graphics artist.
Martin Reinsprecht handles all the infrastructure for the project: web and project servers, mailinglists and so on.
Raphael Langerhorst does most of the project coordination and architectural design and writes lots of code and documentation.
We mainly use mailing lists to communicate with each other, although often we directly communicate via instant messaging, telephone or personal meetings.
Everyone that wants to contact us is encouraged to sign up on one of our mailing lists which are separated for various topics. Simply choose the one where you think your issue or topic fits best, sign up and send a mail to it. If you are unsure which list to use, then you should use the users mailing list.