Skip to Content

Changes for page KIELER Archive

Last modified by Sascha Hoppe on 2025/01/30 09:33
From version 55.1
edited by Alexander Schulz-Rosengarten
on 2019/01/14 14:18
Change comment: There is no comment for this version
To version 42.1
edited by cds
on 2015/02/21 14:12
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.als
1 +XWiki.cds
Content
... ... @@ -1,92 +1,53 @@
1 -= Welcome to the KIELER Project's Wiki! =
1 += (% class="confluence-link" %)**Welcome to the KIELER Project's Wiki!**(%%) =
2 2  
3 -The //Kiel Integrated Environment for Layout Eclipse RichClient//, or short [[//KIELER//>>url:http://rtsys.informatik.uni-kiel.de/~~kieler/kings_of_coding.mp3||shape="rect"]], is a research project about enhancing the graphical model-based design of complex systems. It is developed by the [[Real-Time and Embedded Systems group>>url:http://www.rtsys.informatik.uni-kiel.de/||shape="rect"]] at [[Kiel University>>url:http://www.uni-kiel.de/||shape="rect"]].
3 +The //Kiel Integrated Environment for Layout Eclipse RichClient//, or short [[//KIELER//>>url:http://rtsys.informatik.uni-kiel.de/~~kieler/kings_of_coding.mp3||shape="rect"]], is a research project about enhancing the graphical model-based design of complex systems.
4 4  
5 5  [[image:attach:button.png]][[doc:Downloads]]
6 6  
7 -== Using This Wiki ==
7 +== Finding Your Way Around this Wiki ==
8 8  
9 -The Wiki is structured as follows:
9 +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. The Wiki is structured as follows:
10 10  
11 -(% class="wrapped" %)
12 -|(((
13 -**[[doc:Overview]]**
11 +* **[[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 -)))|(((
16 -**The Different Components of KIELER**
17 -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.
18 -)))|(% class="confluence-link" %)(% class="confluence-link" %)
19 -(((
20 -**[[doc:Development]]**
21 -The development section has our guides on how to start as a new KIELER developer (the [[doc:Guidelines]] are of particular interest; go read them!), some more guidelines and generally acts as a documentation of our daily work, including [[doc:Meetings]].
22 -)))|(((
23 -**[[doc:Processes]]**
13 +* **The Different Components of KIELER**
14 +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 SCCharts]] component and finally there are [[doc:KIELER Demonstrators]].
15 +* **[[doc:Development]]**
16 +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]].
17 +* **[[doc:Processes]]**
24 24  The processes section contains documentation about the processes we use to manage KIELER.
25 -)))
26 26  
27 -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.
20 +== What Else is There? ==
28 28  
29 -== Getting Help ==
22 +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:
30 30  
31 -This Wiki is the main source of documentation for the KIELER project. If you'd like to get in touch with the team, either search the [[group's web page>>url:http://www.informatik.uni-kiel.de/rtsys/kontakt/||shape="rect"]] for e-mail addresses, or use the following channels:
32 -
24 +* [[**The Group Pages**
25 +>>url:http://informatik.uni-kiel.de/rtsys/kieler/||shape="rect"]]The pages of our research group have a section on KIELER that also has [[demos and tutorial videos>>url:http://www.informatik.uni-kiel.de/rtsys/kieler/demos/||shape="rect"]].
26 +* **[[Stash>>url:http://git.rtsys.informatik.uni-kiel.de/||shape="rect"]]**
27 +The web front end to our [[Git>>doc:Using Git]] repositories. Feel free to add your own, private repositories.
28 +* **[[JIRA>>url:http://rtsys.informatik.uni-kiel.de/jira/||shape="rect"]]**
29 +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.
30 +* (((
31 +**[[Bamboo>>url:http://rtsys.informatik.uni-kiel.de/bamboo/allPlans.action||shape="rect"]]**
32 +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.
33 +)))
34 +* **[[FishEye>>url:http://rtsys.informatik.uni-kiel.de/fisheye/||shape="rect"]]**
35 +Our revision-control browser. Use FishEye to browse KIELER's mainline [[Git>>doc:Using Git]] repository.
36 +* **[[Code Ratings>>url:http://rtsys.informatik.uni-kiel.de/%7Ekieler/doc/rating/||shape="rect"]]**
37 +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.
38 +* **[[Extensions Documentation>>url:http://rtsys.informatik.uni-kiel.de/~~kieler/doc/extensions/||shape="rect"]]**
39 +An effort to document the KLighD extension methods found in the {{code language="none"}}...krendering.extensions{{/code}} and {{code language="none"}}...ptolemy.klighd{{/code}} plugins.
33 33  * [[**Announcement Mailing List**>>url:https://lists.informatik.uni-kiel.de/mailman/listinfo/rt-kieler||shape="rect"]]
34 34  KIELER releases and important project updates are sent to this low-traffic mailing list.
35 35  * **[[Developer Mailing List>>url:https://lists.informatik.uni-kiel.de/mailman/listinfo/rt-kieler-devel||shape="rect"]]**
36 36  Every KIELER developer is expected to be on our developer mailing list to stay up to date on announcements and information relevant to developers.
37 -* [[**Questions**>>url:https://rtsys.informatik.uni-kiel.de/confluence/questions||shape="rect"]]
38 -Ask questions regarding KIELER.
44 +* **[[IRC>>url:irc://irc.freenode.net:6667/kieler||shape="rect"]] (Alternativ: [[Webchat>>url:http://webchat.freenode.net?channels=%23kieler&uio=d4||shape="rect"]])**
45 +Try contacting us on the freenode server in the #kieler channel if you have any questions.
39 39  
40 -Also take a look at **[[demos and tutorial videos>>url:http://www.informatik.uni-kiel.de/rtsys/kieler/demos/||shape="rect"]]** we have put together.
47 +== What's New Around Here? ==
41 41  
42 -== Development ==
49 +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 43  
44 -Here's the list of tools we use:
45 -
46 -{{section}}
47 -{{column}}
48 -(% style="text-align: center;" %)
49 -[[~[~[image:attach:code.png~]~]
50 -Source Code>>url:http://git.rtsys.informatik.uni-kiel.de/||shape="rect"]]
51 -{{/column}}
52 -
53 -{{column}}
54 -(% style="text-align: center;" %)
55 -[[~[~[image:attach:bugs.png~]~]
56 -Bug Tracking>>url:http://rtsys.informatik.uni-kiel.de/jira/||shape="rect"]]
57 -{{/column}}
58 -
59 -{{column}}
60 -(% style="text-align: center;" %)
61 -[[~[~[image:attach:build.png~]~]
62 -Automatic Builds>>url:http://rtsys.informatik.uni-kiel.de/bamboo/allPlans.action||shape="rect"]]
63 -{{/column}}
64 -
65 -{{column}}
66 -(% style="text-align: center;" %)
67 -[[~[~[image:attach:reviews.png~]~]
68 -Code Reviews>>url:http://rtsys.informatik.uni-kiel.de/fisheye/||shape="rect"]]
69 -{{/column}}
70 -
71 -{{column}}
72 -(% style="text-align: center;" %)
73 -[[~[~[image:attach:ratings.png~]~]
74 -Code Ratings>>url:http://rtsys.informatik.uni-kiel.de/%7Ekieler/doc/rating/||shape="rect"]]
75 -{{/column}}
76 -
77 -{{column}}
78 -(% style="text-align: center;" %)
79 -[[~[~[image:attach:docs.png~]~]
80 -Extensions Documentation>>url:http://rtsys.informatik.uni-kiel.de/~~kieler/doc/extensions/||shape="rect"]]
81 -{{/column}}
82 -
83 -{{column width="100%"}}
84 -\\
85 -{{/column}}
86 -{{/section}}
87 -
88 -== Wiki Activity ==
89 -
90 90  {{expand title="Click here to see a list of recent changes to the Wiki..."}}
91 91  
92 92  
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -72450056
1 +10751249
URL
... ... @@ -1,1 +1,1 @@
1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/72450056/Home
1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/10751249/Home