Skip to Content

Changes for page KIELER Archive

Last modified by Sascha Hoppe on 2025/01/30 09:33
From version 12.1
edited by cds
on 2012/03/29 18:25
Change comment: There is no comment for this version
To version 7.1
edited by cds
on 2012/03/23 14:23
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -6,17 +6,17 @@
6 6  
7 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 8  
9 -== Finding Your Way Around this Wiki ==
9 +== Finding You Way Around this Wiki ==
10 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:
11 +We have quite a bit of stuff in this Wiki, so you might wonder where to find things. We have a few areas that might be of interest:
12 12  
13 -* **[[doc:KIELER.Overview]]**
13 +* **[[doc:Overview]]**
14 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:KIELER.Development]]**
18 -The development section has our guides on how to start as a new KIELER developer ([[doc:KIELER.Getting Started]] is of particular interest; go read it!), some more guidelines and generally acts as a documentation of our daily work, including [[doc:KIELER.Meetings]].
19 -* **[[doc:KIELER.Administration]]**
15 +* **The different component pages**
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:Layout]] component, the [[doc:Pragmatics]] component, the [[doc:Semantics]] component and finally there are [[doc:Other Projects]].
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 20  The administration section contains documentation about the processes we use to manage KIELER.
21 21  
22 22  == What Else is There? ==
... ... @@ -26,17 +26,13 @@
26 26  * [[**The Group Pages**
27 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 / turorial videos>>url:http://www.informatik.uni-kiel.de/rtsys/kieler/demos/||shape="rect"]], and more.
28 28  * **[[Gitorious>>url:https://git.rtsys.informatik.uni-kiel.de||shape="rect"]]**
29 -The web front end to our [[Git>>doc:KIELER.Using Git]] repositories. Feel free to add your own, private repositories.
29 +The web front end to our [[Git>>doc:Using Git]] repositories. Feel free to add your own, private repositories.
30 30  * **[[JIRA>>url:http://rtsys.informatik.uni-kiel.de/jira/||shape="rect"]]**
31 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 32  * **Bamboo**
33 -Our build server. Whenever you push commits to the mainline [[Git>>doc:KIELER.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.
33 +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.
34 34  * **[[FishEye>>url:http://rtsys.informatik.uni-kiel.de/fisheye/||shape="rect"]]**
35 -Use FishEye to browse KIELER's mainline [[Git>>doc:KIELER.Using Git]] repository.
36 -* **[[Developer Mailing List>>url:https://lists.informatik.uni-kiel.de/mailman/listinfo/rt-kieler-devel||shape="rect"]]**
37 -Every KIELER developer is expected to be on our developer mailing list to stay up to date on announcements and information relevant to developers.
38 -* **[[doc:KIELER.KIELER Project Meetings]]**
39 -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.
35 +Use FishEye to browse KIELER's mainline [[Git>>doc:Using Git]] repository.
40 40  
41 41  == What's New Around Here? ==
42 42  
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -885053
1 +884874
URL
... ... @@ -1,1 +1,1 @@
1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/885053/Home
1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/884874/Home