We have decided to use Github for this purpose.
If a service is tracked in other source control platform or is not open source (?), we can still create an empty repository in our Github organization and track related issues there.
In case of problems accessing our Github organization, please contact Allan (OU) or Michal (PSNC).
The right places to report on particular components are the following:
- SSO - https://github.com/up2university/single-sign-on/issues
- Moodle - https://github.com/up2university/docker-moodle/issues
- CERNBox and SWAN - https://github.com/up2university/kuboxed/issues
- eduOER - https://github.com/up2university/eduoer/issues
- SeLCont - https://github.com/up2university/selcont/issues
- Knockplop (WebRTC) - https://github.com/up2university/knockplop/issues
- Multiparty meeting - https://github.com/up2university/multiparty-meeting/issues
- DSpace - https://github.com/up2university/DSpace/issues
- LearningLocker (LRS) - https://github.com/up2university/learninglocker2/issues
- PODDIUM (Personal Recorder) - https://github.com/teltek/PuMuKIT2-up2u-pr-bundle/issues
- OpenEdX - https://github.com/up2university/OpenEdX/issues
See also Domain name conventions for the list of tool&service instances that are already in place.