RWTHjupyter Community Process
This flow chart describes the process for the implementation of new features in the RWHTjupyter cluster. It aims to allow for contributions by the RWTHjupyter community. The RWTHjuypyter board keeps track of open issues and feature requests and facilitates the collaboration between members of the community. The community can submit change requests for changes to be applied in the cluster. These change requests are evaluated and approved by the board and subsequently implemented by the IT centers LBA group.
flowchart TD
jupyter((Wider Jupyter<br>Community))
community((RWTHjupyter<br>Community))
itc-sd-l1((SD Level 1))
itc-sd-l2((SD Level 2))
itc-lba((LBA Group))
board((RWTHjupyter<br>Board))
interest-group((Interest<br>Group))
feature[Feature<br>Request]
bug[Bug<br>Report]
gitlab[GitLab<br>Issue]
change-request[Change<br>Request]
feature -- submitted --> itc-sd-l1
bug -- submitted --> itc-sd-l1
subgraph ITC ServiceDesk
itc-sd-l1 -- forwarded --> itc-sd-l2
end
itc-lba -- works on --> gitlab
itc-sd-l2 -- creates --> gitlab
board --> gitlab
gitlab -- iterates monthly --> board
board -- forms --> interest-group
community -- joins --> interest-group
jupyter --> community
community -- collaborates --> jupyter
interest-group -- proposes --> change-request
board -- evaluates --> change-request
change-request -- is tracked by --> gitlab
Kommentare
- Vereinfachen -> Linearisieren
- ITC SD als einzellner block
- LBA -> Operations
- Farbig hervorheben: Tools vs. Gruppen
- Feature Requests / Bug -> "SD Ticket"
Edited by Steffen Vogel