Summary

• Page properties (1 modified, 0 added, 0 removed)
• Objects (1 modified, 0 added, 0 removed)
  • Confluence.Code.ConfluencePageClass[0]

Details

Page properties

Content

...	...	@@ -6,7 +6,7 @@
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	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	12
...	...	@@ -13,7 +13,7 @@
13	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	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:Layout]] component, the [[doc:Pragmatics]] component, the [[doc:Semantics]] component and finally there are [[doc:Demonstrators]].
	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	17	* **[[doc:Development]]**
18	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	19	* **[[doc:Administration]]**
...	...	@@ -33,8 +33,6 @@
33	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	35	Use FishEye to browse KIELER's mainline [[Git>>doc:Using Git]] repository.
36		-* [[**Announcement Mailing List**>>url:https://lists.informatik.uni-kiel.de/mailman/listinfo/rt-kieler||shape="rect"]]
37		-KIELER releases and important project updates are sent to this low-traffic mailing list.
38	38	* **[[Developer Mailing List>>url:https://lists.informatik.uni-kiel.de/mailman/listinfo/rt-kieler-devel||shape="rect"]]**
39	39	Every KIELER developer is expected to be on our developer mailing list to stay up to date on announcements and information relevant to developers.
40	40	* **[[doc:KIELER Project Meetings]]**

Confluence.Code.ConfluencePageClass[0]

Id

...	...	@@ -1,1 +1,1 @@
1		-1540160
	1	+884962

URL

...	...	@@ -1,1 +1,1 @@
1		-https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/1540160/Home
	1	+https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/884962/Home