Summary

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

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.cds
	1	+XWiki.msp

Content

...	...	@@ -2,10 +2,6 @@
2	2
3	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	4
5		-{{tip title="Survey on KIELER Layout"}}
6		-The KIELER team is conducting a [[survey on automatic layout>>url:http://www.informatik.uni-kiel.de/rtsys/kieler/survey/||shape="rect"]]. Please support our research by participating.
7		-{{/tip}}
8		-
9	9	== Where Can I Download KIELER? ==
10	10
11	11	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"]].
...	...	@@ -14,13 +14,13 @@
14	14
15	15	We have quite a bit of stuff in this Wiki, so you might wonder where to find things. The Wiki is structured like this:
16	16
17		-* **[[doc:KIELER.Overview]]**
	13	+* **[[doc:Overview]]**
18	18	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.
19	19	* **The Different Components of KIELER**
20		-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.KIELER Layout]] component, the [[doc:KIELER.KIELER Pragmatics]] component, the [[doc:KIELER.KIELER Semantics]] component and finally there are [[doc:KIELER.KIELER Demonstrators]].
21		-* **[[doc:KIELER.Development]]**
22		-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]].
23		-* **[[doc:KIELER.Administration]]**
	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]]**
24	24	The administration section contains documentation about the processes we use to manage KIELER.
25	25
26	26	== What Else is There? ==
...	...	@@ -30,15 +30,15 @@
30	30	* [[**The Group Pages**
31	31	>>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.
32	32	* **[[Stash>>url:http://git.rtsys.informatik.uni-kiel.de/||shape="rect"]]**
33		-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.
34	34	* **[[JIRA>>url:http://rtsys.informatik.uni-kiel.de/jira/||shape="rect"]]**
35	35	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.
36	36	* (((
37	37	**[[Bamboo>>url:http://rtsys.informatik.uni-kiel.de/bamboo/allPlans.action||shape="rect"]]**
38		-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.
	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.
39	39	)))
40	40	* **[[FishEye>>url:http://rtsys.informatik.uni-kiel.de/fisheye/||shape="rect"]]**
41		-Our revision-control browser. Use FishEye to browse KIELER's mainline [[Git>>doc:KIELER.Using Git]] repository.
	37	+Our revision-control browser. Use FishEye to browse KIELER's mainline [[Git>>doc:Using Git]] repository.
42	42	* **[[Code Ratings>>url:http://rtsys.informatik.uni-kiel.de/%7Ekieler/rating/||shape="rect"]]**
43	43	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.
44	44	* [[**Announcement Mailing List**>>url:https://lists.informatik.uni-kiel.de/mailman/listinfo/rt-kieler||shape="rect"]]
...	...	@@ -45,7 +45,7 @@
45	45	KIELER releases and important project updates are sent to this low-traffic mailing list.
46	46	* **[[Developer Mailing List>>url:https://lists.informatik.uni-kiel.de/mailman/listinfo/rt-kieler-devel||shape="rect"]]**
47	47	Every KIELER developer is expected to be on our developer mailing list to stay up to date on announcements and information relevant to developers.
48		-* **[[doc:KIELER.KIELER Project Meetings]]**
	44	+* **[[doc:KIELER Project Meetings]]**
49	49	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.
50	50
51	51	== What's New Around Here? ==

Confluence.Code.ConfluencePageClass[0]

Id

...	...	@@ -1,1 +1,1 @@
1		-7700587
	1	+7700767

URL

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