[KIEKER-1166] Document workflow for setting up access to Kieker infrastructure for new developers

[rju]

JIRA Issue: KIEKER-1166 Document workflow for setting up access to Kieker infrastructure for new developers Original Reporter: Andre van Hoorn

---

First of all, we'll create a ticket for setting up the new developer's access.

Steps to be covered.

1. Access to [Git repositories|VCSRepositories]:
- Default repos:
1. kieker.git
1. kieker.examples.git
- Developer must attach public SSH key ([learn more|VCSRepositories]) to ticket
1. LDAP user(name):
- For CAU students: e-mail short name
- Others: firstname.<middlename.>lastname

- further required information:

- email:

- duration: e.g. end of SS 14

- function: e.g. student assistant

- advisor/contact person: e.g. avh

- project: e.g. kieker
1. Access to Trac:
- LDAP account required
- permission group: basic
1. Access to Jenkins:
- LDAP account required
- Default jobs:
1. kieker
1. kieker-nightly-release
- Default job permissions: read, build, workspace
1. Add to public mailing lists
1. Add to internal mailing list

[rju]

author Jan Waller -- Tue, 19 Mar 2013 12:31:48 +0100

This should be moved to a wiki page.

[rju]

author André van Hoorn -- Tue, 19 Mar 2013 22:25:09 +0100

Replying to [jwa|comment:6]:
> This should be moved to a wiki page.

Done: DevGuide/InitNewAndRemoveOldDeveloper(also linked from DevGuide)