- We have a weekly project meeting to discuss KIELER issues and to check up on what everyone else is doing. KIELER developers are expected to attend the meeting, if at all possible. You're also welcome to give a short demo of cool new features you've developed.
- We have a developer mailing list that all KIELER developers are expected to be on. If you haven't signed up for it yet, do so now. The mailing list is used to announce changes that affect other KIELER developers.
- For fast and direct communication we have an XMPP/Jabber server which you are expected to use with your favourite IM client, for example pidgin on our SunRaysthin clients. The server runs on git.rtsys.informatik.uni-kiel.de, username is <login>@git.rtsys.informatik.uni-kiel.de. You should make sure that encrypted connection via TLS/SSL is checked. There is also a common Chatroom "Kieler_devel" to be found on this server. Join and communicate.
- We have an IRC channel that you should join. Point your favourite IRC client (XChat is installed on our thin clients) to the Freenode network (irc.freenode.org) and join #kieler.
- We use Git as source code management system. In order to understand the high-level workflows involving clones and branches, read the Source Code Management page.
- We want our code to be well-designed and well-written. To help ensure that, we have a review process, designed to have other people look at your code and suggest improvements as well as learn from it. Take the opportunity to get some valuable input!
- KIELER is an experimental and fast-changing research project, so we don't document it with anything approaching professional standards. However, there are two sources for information: bachelor / master / diploma / doctoral theses about specific parts of KIELER, and this Wiki. If you have developed some complex feature, please consider adding documentation for it to the Wiki. For development work done as part of a thesis, this is pretty much mandatory and will go into the thesis's appendix.