| ... |
... |
@@ -8,35 +8,39 @@ |
| 8 |
8 |
|
| 9 |
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. We have a few areas that might be of interest: |
|
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 |
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 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's the [[doc:Layout]] component, the [[doc:Pragmatics]] component, the [[doc:Semantics]] component, and finally there's [[doc:Other Projects]]. |
|
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:Other Projects]]. |
| 17 |
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]]. |
|
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]]** |
| 20 |
20 |
The administration section contains documentation about the processes we use to manage KIELER. |
| 21 |
21 |
|
| 22 |
22 |
== What Else is There? == |
| 23 |
23 |
|
| 24 |
|
-The KIELER project doesn't only have a Wiki – in fact, this is only a small part of what we use. Here's a list of other tools and pages you might be interested in looking at: |
|
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 |
25 |
|
| 26 |
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 download links, links to demo videos, and more. |
|
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 |
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:Using Git]] repository, Bamboo starts to compile it and run all the unit tests. If your changes break the build or the tests, you'll 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 |
35 |
Use FishEye to browse KIELER's mainline [[Git>>doc: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 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. |
| 36 |
36 |
|
| 37 |
37 |
== What's New Around Here? == |
| 38 |
38 |
|
| 39 |
|
-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. |
|
43 |
+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. |
| 40 |
40 |
|
| 41 |
41 |
{{expand title="Click here to see a list of recent changes to the Wiki..."}} |
| 42 |
42 |
|