Governance
Governance of git.nrw
The governance of git.nrw is carried out through unified structures, including an advisory board composed of representatives from various stakeholder groups, including students, CIOs/CTOs, academic staff, data protection officers, and the DH.NRW office.
Responsibilities of the Advisory Board
The advisory board supports the git.nrw project in several key areas:
- Advising the management board on prioritization of work packages
- Quality assurance of the project through continuous support
- Active risk management through early risk identification and appropriate countermeasures
Members of the Advisory Board
| Stakeholder Group | Member | Institution |
|---|---|---|
| Students | Lorenzo Conti | University of Bonn |
| IT Security | Mergim Ademi | University of Cologne |
| Technical/Administrative Staff | Bastian Doht | Bielefeld University |
| CIO/CTO | Dr. Thomas Eifert | RWTH Aachen |
| Academic Staff | Alexander Dobrynin | TH Köln |
| Data Protection Officer | Oliver Hinte | FernUniversität in Hagen |
| Staff Council | Dr. Damian Bucher | University of Münster |
| DH.NRW | Dr. Martin Jungwirth | DH.NRW Office |
git.nrw User Group and User Meeting
The User Group comprises all users of git.nrw. These may include students, lecturers and staff. There is no limit on the size of the group. For this reason, anyone interested in joining must also register for the user meetings. Members are actively involved in the project, for example by being included in the decision-making process, expressing their wishes, and providing feedback on the project’s current status. They can also nominate and elect people to the project advisory board. To this end, user meetings are held at regular intervals.
Networking within the git.nrw community
A wide range of interests and perspectives have come together within the project, resulting in the formation of networks between different groups. In order to facilitate collaboration between these groups and to ensure the effective communication of feedback and requirements to the project team, two large and one smaller exchange format have been developed. Results relevant to all groups are distributed via the appropriate communication channels.
The objective is to establish an open exchange to consolidate the git.nrw community. Those interested in participating can do so by joining the Mattermost community or subscribing to the mailing list. The table below provides an overview of the various groups and their associated communication channels.
| Type | Advisory Board | User Meeting | git.nrw Coffee | Mailing list |
|---|---|---|---|---|
| Objective | The aim is to support the git.nrw project in several key areas. It comprises representatives from various stakeholder groups | Any organisation using the central system may send representatives. These representatives can nominate and elect members of the Advisory Board and actively participate in the decision-making process | Open virtual coffee session for interested parties and users of git.nrw | Exchange with interested parties and users regarding project development and milestones achieved. Please register via this link |
| Frequency | Twice a year | Twice a year | 4 fixed dates, further dates in planning | As required |