Show last authors
author | version | line-number | content |
---|---|---|---|
1 | = (% class="confluence-link" %)**Welcome to the KIELER Project's Wiki!**(%%) = | ||
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. | ||
4 | |||
5 | [[image:attach:button.png]][[doc:Downloads]] | ||
6 | |||
7 | == Finding Your Way Around this Wiki == | ||
8 | |||
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 | |||
11 | |((( | ||
12 | **[[doc:Overview]]** | ||
13 | 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. | ||
14 | )))|((( | ||
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. | ||
17 | )))|((( | ||
18 | **[[doc:Development]]** | ||
19 | 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]]. | ||
20 | )))|((( | ||
21 | **[[doc:Processes]]** | ||
22 | The processes section contains documentation about the processes we use to manage KIELER. | ||
23 | ))) | ||
24 | |||
25 | == What Else is There? == | ||
26 | |||
27 | 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: | ||
28 | |||
29 | * [[**The Group Pages** | ||
30 | >>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"]]. | ||
31 | * **[[Stash>>url:http://git.rtsys.informatik.uni-kiel.de/||shape="rect"]]** | ||
32 | The web front end to our [[Git>>doc:Using Git]] repositories. Feel free to add your own, private repositories. | ||
33 | * **[[JIRA>>url:http://rtsys.informatik.uni-kiel.de/jira/||shape="rect"]]** | ||
34 | 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. | ||
35 | * ((( | ||
36 | **[[Bamboo>>url:http://rtsys.informatik.uni-kiel.de/bamboo/allPlans.action||shape="rect"]]** | ||
37 | 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. | ||
38 | ))) | ||
39 | * **[[FishEye>>url:http://rtsys.informatik.uni-kiel.de/fisheye/||shape="rect"]]** | ||
40 | Our revision-control browser. Use FishEye to browse KIELER's mainline [[Git>>doc:Using Git]] repository. | ||
41 | * **[[Code Ratings>>url:http://rtsys.informatik.uni-kiel.de/%7Ekieler/doc/rating/||shape="rect"]]** | ||
42 | 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. | ||
43 | * **[[Extensions Documentation>>url:http://rtsys.informatik.uni-kiel.de/~~kieler/doc/extensions/||shape="rect"]]** | ||
44 | 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. | ||
45 | * [[**Announcement Mailing List**>>url:https://lists.informatik.uni-kiel.de/mailman/listinfo/rt-kieler||shape="rect"]] | ||
46 | KIELER releases and important project updates are sent to this low-traffic mailing list. | ||
47 | * **[[Developer Mailing List>>url:https://lists.informatik.uni-kiel.de/mailman/listinfo/rt-kieler-devel||shape="rect"]]** | ||
48 | Every KIELER developer is expected to be on our developer mailing list to stay up to date on announcements and information relevant to developers. | ||
49 | * **[[IRC>>url:irc://irc.freenode.net:6667/kieler||shape="rect"]] (Alternativ: [[Webchat>>url:http://webchat.freenode.net?channels=%23kieler&uio=d4||shape="rect"]])** | ||
50 | Try contacting us on the freenode server in the #kieler channel if you have any questions. | ||
51 | |||
52 | == What's New Around Here? == | ||
53 | |||
54 | 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. | ||
55 | |||
56 | {{expand title="Click here to see a list of recent changes to the Wiki..."}} | ||
57 | |||
58 | |||
59 | {{recently-updated max="20" theme="social"/}} | ||
60 | {{/expand}} |