Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | = **Welcome to the KIELER Project's Wiki!** = | ||
| 2 | |||
| 3 | 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. | ||
| 4 | |||
| 5 | == Where Can I Download KIELER? == | ||
| 6 | |||
| 7 | If you're not here for the Wiki, but just want to download KIELER straight away, please visit [[KIELER's downloads page>>url:http://www.informatik.uni-kiel.de/rtsys/kieler/downloads/||shape="rect"]]. | ||
| 8 | |||
| 9 | == Finding Your Way Around this Wiki == | ||
| 10 | |||
| 11 | We have quite a bit of stuff in this Wiki, so you might wonder where to find things. The Wiki is structured like this: | ||
| 12 | |||
| 13 | * **[[doc:Overview]]** | ||
| 14 | 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. | ||
| 15 | * **The Different Components of KIELER** | ||
| 16 | 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 [[doc:KIELER Layout]] component, the [[doc:KIELER Pragmatics]] component, the [[doc:KIELER Semantics]] component and finally there are [[doc:KIELER Demonstrators]]. | ||
| 17 | * **[[doc:Development]]** | ||
| 18 | The development section has our guides on how to start as a new KIELER developer ([[doc:Getting Started]] is of particular interest; go read it!), some more guidelines and generally acts as a documentation of our daily work, including [[doc:Meetings]]. | ||
| 19 | * **[[doc:Administration]]** | ||
| 20 | The administration section contains documentation about the processes we use to manage KIELER. | ||
| 21 | |||
| 22 | == What Else is There? == | ||
| 23 | |||
| 24 | 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: | ||
| 25 | |||
| 26 | * [[**The Group Pages** | ||
| 27 | >>url:http://informatik.uni-kiel.de/rtsys/kieler/||shape="rect"]]The pages of our research group have a section on KIELER, complete with [[Downloads>>url:http://www.informatik.uni-kiel.de/rtsys/kieler/downloads/||shape="rect"]], [[demo / tutorial videos>>url:http://www.informatik.uni-kiel.de/rtsys/kieler/demos/||shape="rect"]], and more. | ||
| 28 | * **[[Stash>>url:http://git.rtsys.informatik.uni-kiel.de/||shape="rect"]]** | ||
| 29 | The web front end to our [[Git>>doc:Using Git]] repositories. Feel free to add your own, private repositories. | ||
| 30 | * **[[JIRA>>url:http://rtsys.informatik.uni-kiel.de/jira/||shape="rect"]]** | ||
| 31 | 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. | ||
| 32 | * ((( | ||
| 33 | **[[Bamboo>>url:http://rtsys.informatik.uni-kiel.de/bamboo/allPlans.action||shape="rect"]]** | ||
| 34 | Our build server. Whenever you push commits to the mainline [[Git>>doc:Using 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. | ||
| 35 | ))) | ||
| 36 | * **[[FishEye>>url:http://rtsys.informatik.uni-kiel.de/fisheye/||shape="rect"]]** | ||
| 37 | Our revision-control browser. Use FishEye to browse KIELER's mainline [[Git>>doc:Using Git]] repository. | ||
| 38 | * **[[Code Ratings>>url:http://rtsys.informatik.uni-kiel.de/%7Ekieler/rating/||shape="rect"]]** | ||
| 39 | 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. | ||
| 40 | * [[**Announcement Mailing List**>>url:https://lists.informatik.uni-kiel.de/mailman/listinfo/rt-kieler||shape="rect"]] | ||
| 41 | KIELER releases and important project updates are sent to this low-traffic mailing list. | ||
| 42 | * **[[Developer Mailing List>>url:https://lists.informatik.uni-kiel.de/mailman/listinfo/rt-kieler-devel||shape="rect"]]** | ||
| 43 | Every KIELER developer is expected to be on our developer mailing list to stay up to date on announcements and information relevant to developers. | ||
| 44 | * **[[IRC>>url:irc://irc.freenode.net:6667/kieler||shape="rect"]]** | ||
| 45 | Try contacting us on the freenode server in the #kieler channel if you have any questions. | ||
| 46 | * **[[doc:KIELER Project Meetings]]** | ||
| 47 | 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. | ||
| 48 | |||
| 49 | == What's New Around Here? == | ||
| 50 | |||
| 51 | 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. | ||
| 52 | |||
| 53 | {{expand title="Click here to see a list of recent changes to the Wiki..."}} | ||
| 54 | |||
| 55 | |||
| 56 | {{recently-updated max="20" theme="social"/}} | ||
| 57 | {{/expand}} |