Welcome to the KIELER Project's Wiki!

We use the Wiki to document the project, its different components, the processes we use to manage it, and whatever else needs documenting. As a KIELER developer, please feel free to add content to the Wiki. If you're unsure about where to add the content to, just ask one of the senior developers – they'll be happy to help. 

Where Can I Download KIELER?

If you're not here for the Wiki, but just want to download KIELER straight away, please visit KIELER's downloads page.

Finding Your Way Around this Wiki

We have quite a bit of stuff in this Wiki, so you might wonder where to find things. The Wiki is structured like this:

• Overview
  The overview section gives you an idea of how KIELER is structured and what parts there are. KIELER has grown quite big, so reading through the overview will help a great deal in finding your bearings around here.
• The Different Components of KIELER
  We have taken care to divide KIELER into several components, which in turn are divided into several projects. This makes the KIELER project a litlte easier to understand, we hope. There is the KIELER Layout component, the KIELER Pragmatics component, the KIELER Semantics component and finally there are KIELER Demonstrators.
• Development
  The development section has our guides on how to start as a new KIELER developer (Getting Started is of particular interest; go read it!), some more guidelines and generally acts as a documentation of our daily work, including Meetings.
• Administration
  The administration section contains documentation about the processes we use to manage KIELER.

What Else is There?

The KIELER project doesn't only have a Wiki – in fact, this is only a small part of what we use. Here is a list of other tools and pages you might be interested in looking at:

• The Group PagesThe pages of our research group have a section on KIELER, complete with Downloads, demo / tutorial videos, and more.
• Stash
  The web front end to our Git repositories. Feel free to add your own, private repositories.
• JIRA
  Our bug tracking system. We encourage all KIELER developers to use the bug tracking system extensively. You get lots of experience using real-world bug tracking systems on a big project, and we get a good overview of the status of the KIELER project.

• Bamboo
  Our build server. Whenever you push commits to the mainline Git repository, Bamboo starts compiling it and runs all the unit tests. If your changes break the build or the tests, you will know it in a matter of 20 minutes.

• FishEye
  Our revision-control browser. Use FishEye to browse KIELER's mainline Git repository.
• Code Ratings
  Our code rating pages are updated as part of the nightly build and give an overview of the code and design review coverage of KIELER.
• Announcement Mailing List
  KIELER releases and important project updates are sent to this low-traffic mailing list.
• Developer Mailing List
  Every KIELER developer is expected to be on our developer mailing list to stay up to date on announcements and information relevant to developers.
• IRC (Alternativ: Webchat)
  Try contacting us on the freenode server in the #kieler channel if you have any questions.
• KIELER Project Meetings
  We have weekly project meetings to stay up to date on what everyone is doing, to discuss problems, and to give demos of cool new features people have developed.

What's New Around Here?

Our Wiki software can show you a list of recent changes to the Wiki. To keep track of what's happening at the KIELER project in general, use JIRA's activity stream widget on its Dashboard. It will show a summary of what people have done, including changes to the Wiki, failed and succeeded builds, pushed commits and more.