• ma
    • Group members (Mitarbeiter) + sysadmin
  • rtstud
    • Students working in the group (Hilfskräfte) or advised by the group (Bachelor-/Master-/Studien-/Diplomarbeiten)
  • stud
    • Participants in classes (Vorlesungen/Praktika)
  • public


To get an overview of the structure and contents of the repository, you may use  websvn. The following list provides a top-level overview.

  • papers (r: rtstud, w: ma, specific users) - see also the page on how to prepare a paper , in particular the naming conventions
  • bib (as papers) - see also here
  • talks (as papers)
  • lectures (r/w: ma+hiwi)
  • make (r: public, w: ma)
  • latex (r/w: ma)
  • teaching (r/w: ma) - see these naming conventions .
    • sem
    • osem (r:rtstud)
    • prak
  • kieler (r/w: ma + students involved)
  • kep (r/w: ma + students involved)
  • krp
  • images (as papers)
    • people-origs (r/w: ma)
    • people (r/w: ma)
    • kieler
    • krep
    • ...
  • projects
    • decos (r/w: ma)
  • theses (r: ma, w: <login>)
    • <login>-<bt|mt|st|dt|diss> (bachelor thesis, master thesis, study thesis, diploma thesis, dissertation). See also these notes on file naming etc .
    • common/template (r: public, w: ma)
  • personal
    • <login> (r/w: <login>

Naming Conventions

Naming conventions for the papers directory can be found here .

Naming conventions for the sem and osem directory are as follows.

  • sem contains a directory (called "semester directory") for each seminar, named in the format <year>[ss|ws]-<short title>, eg. "09ss-model".
  • Similarly, osem contains a semester directory for each Oberseminar, in the format <year><ss|ws>, eg "09ss".
  • Each semester directory contains one directory per participant (the "participant directory"), in the format <user name>, eg "rvh"
  • Each participant directory "xyz" contains the following files, where <prefix> is a unique identifier for each semester directory of the form [sem|osem]<year>[ss|ws], eg "sem12ss" or "osem12ws":
    • <prefix>-<user name>-talk.tex - the source for the presentation slides (eg "sem12ss-rvh-talk.tex")
    • <prefix>-<user name>-talk.pdf - the slides for the presentation (may contain animations)
    • <prefix>-<user name>-handout.pdf - the slides used for the proceedings and/or for download (no animations, may contain notes). If you use the standard Makefile, <prefix>-<user name>-handout.pdf can be generated automatically from <prefix>-<user name>-talk.tex.
  • If there is an accompanying paper (Ausarbeitung), as is commonly the case for the seminar, the participant directory also contains
    • <prefix>-<user name>.tex - the source for the paper
    • <prefix>-<user name>.pdf - the paper, as to be included in the proceedings
    • <prefix>-<user name>-review-<user name of reviewer>.pdf - a review performed by a reviewer

MIME types and Line Endings

Java source code files need to have the right MIME-type (text/x-java) so that they can be rendered correctly by the Webbrowser. To deal with different operating systems and their different representation of line endings, svn supports another property to automatically convert inappropriate line endings.

See the  KIELER Wiki on how to configure your client (Windows/Linux/Mac).