IT Tickets issueshttps://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues2020-09-14T14:19:54+02:00https://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/27Need a domain for the preview of the new blog for oseg2020-09-14T14:19:54+02:00Bastian Menningenbastian.menningen@ose-germany.deNeed a domain for the preview of the new blog for osegDomainname: blogprev.opensourceecology.de
IP: 136.243.88.111
I need this by Monday because I want to do the survey for the SSO access via a WP plugin on the preview blog.Domainname: blogprev.opensourceecology.de
IP: 136.243.88.111
I need this by Monday because I want to do the survey for the SSO access via a WP plugin on the preview blog.Maintenance Cycle 2020-09https://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/25Transfer Trello boards into this repository2020-10-18T19:32:02+02:00Andre LehmannTransfer Trello boards into this repositoryCurrently we use Trello for project management. We want to consolidate our issues/projects into this central management repository to simplify the organizational aspects.
**Tasks:**
- [x] Create issue template for gitlab like the one u...Currently we use Trello for project management. We want to consolidate our issues/projects into this central management repository to simplify the organizational aspects.
**Tasks:**
- [x] Create issue template for gitlab like the one used in Gitea
- [x] Transfer Trello content here
- [x] Close the Trello boardMaintenance Cycle 2020-09Andre LehmannAndre Lehmannhttps://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/24Gitlab: reactivate the wiki function not works2020-10-12T10:25:00+02:00Bastian Menningenbastian.menningen@ose-germany.deGitlab: reactivate the wiki function not worksIf you have deactivated the wiki function in one repo then it isn't possible to reactivate it again.
Here is the ticket on the official website: https://gitlab.com/gitlab-org/gitlab/-/issues/241619If you have deactivated the wiki function in one repo then it isn't possible to reactivate it again.
Here is the ticket on the official website: https://gitlab.com/gitlab-org/gitlab/-/issues/241619Maintenance Cycle 2020-09Andre LehmannAndre Lehmannhttps://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/44Traefik Bug2020-12-10T21:15:33+01:00Andre LehmannTraefik Bug<!---
PLEASE READ THIS!
This is the template for describing a BUG (problem; unexpected behavior). If
your intention is to file a feature request or something else, please use the
appropriate template for that instead.
Before creating ...<!---
PLEASE READ THIS!
This is the template for describing a BUG (problem; unexpected behavior). If
your intention is to file a feature request or something else, please use the
appropriate template for that instead.
Before creating a new ticket, please search for existing tickets that match your
issue description, to avoid creating a duplicate.
--->
### Summary
<!-- Summarize the bug encountered concisely. -->
The Traefik logs contain an error, which matches the message captured in this [bug report on Github](https://github.com/traefik/traefik/issues/7250). The issue seems to be [fixed](https://github.com/traefik/traefik/pull/7230) in the new version of Traefik.
### Context/Logs
<!--- Provide context that might help us to come up with a solution. If you have
relevant logs use Markdown code blocks (```) to format them. -->
Error Log:
```
time="2020-11-12T08:58:37+01:00" level=error msg="Stack: goroutine 98049 [running]:
github.com/containous/traefik/v2/pkg/middlewares/recovery.recoverFunc(0x2ec3a60, 0xc000d87da0, 0x2eb97e0, 0xc0002fa8c0, 0xc000a53800)
/go/src/github.com/containous/traefik/pkg/middlewares/recovery/recovery.go:47 +0x1db
panic(0x24c0be0, 0xc00099c270)
/usr/local/go/src/runtime/panic.go:969 +0x166
github.com/containous/traefik/v2/pkg/middlewares/pipelining.(*writerWithoutCloseNotify).Hijack(0xc000b27510, 0x7fa8856fb9e0, 0xc0009950e0, 0x2eb97a0, 0xc0009950e0, 0x1)
/go/src/github.com/containous/traefik/pkg/middlewares/pipelining/pipelining.go:69 +0x47
net/http/httputil.(*ReverseProxy).handleUpgradeResponse(0xc0005ec640, 0x2ea76a0, 0xc000b27510, 0xc000a53e00, 0xc000475200)
/usr/local/go/src/net/http/httputil/reverseproxy.go:530 +0x309
net/http/httputil.(*ReverseProxy).ServeHTTP(0xc0005ec640, 0x2ea76a0, 0xc000b27510, 0xc000a53d00)
/usr/local/go/src/net/http/httputil/reverseproxy.go:268 +0xf07
github.com/containous/traefik/v2/pkg/middlewares/pipelining.(*pipelining).ServeHTTP(0xc000b7a6d0, 0x2ea7660, 0xc000879f40, 0xc000a53d00)
/go/src/github.com/containous/traefik/pkg/middlewares/pipelining/pipelining.go:36 +0xe7
github.com/containous/traefik/v2/pkg/middlewares/accesslog.(*FieldHandler).ServeHTTP(0xc000724c40, 0x2ea7660, 0xc000879f40, 0xc000a53d00)
/go/src/github.com/containous/traefik/pkg/middlewares/accesslog/field_middleware.go:29 +0x18d
github.com/vulcand/oxy/roundrobin.(*RoundRobin).ServeHTTP(0xc00025ebd0, 0x2ea7660, 0xc000879f40, 0xc000a53c00)
/go/pkg/mod/github.com/vulcand/oxy@v1.1.0/roundrobin/rr.go:147 +0x13d
github.com/containous/traefik/v2/pkg/middlewares/emptybackendhandler.(*emptyBackend).ServeHTTP(0xc000b7a700, 0x2ea7660, 0xc000879f40, 0xc000a53c00)
/go/src/github.com/containous/traefik/pkg/middlewares/emptybackendhandler/empty_backend_handler.go:31 +0x168
github.com/containous/traefik/v2/pkg/middlewares/tracing.(*forwarderMiddleware).ServeHTTP(0xc0006598f0, 0x2ea7660, 0xc000879f40, 0xc000a53c00)
/go/src/github.com/containous/traefik/pkg/middlewares/tracing/forwarder.go:38 +0x609
github.com/containous/traefik/v2/pkg/middlewares/headers.secureHeader.ServeHTTP.func1(0x2ea7660, 0xc000879ef0, 0xc000a53c00)
/go/src/github.com/containous/traefik/pkg/middlewares/headers/secure.go:52 +0xea
github.com/unrolled/secure.(*Secure).HandlerFuncWithNextForRequestOnly(0xc000541b80, 0x2ea7660, 0xc000879ef0, 0xc000a53b00, 0xc000f08a80)
/go/pkg/mod/github.com/unrolled/secure@v1.0.7/secure.go:228 +0x201
github.com/containous/traefik/v2/pkg/middlewares/headers.secureHeader.ServeHTTP(0x2e5a460, 0xc0006598f0, 0xc000541b80, 0xc0007d7860, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
/go/src/github.com/containous/traefik/pkg/middlewares/headers/secure.go:51 +0x7a
github.com/containous/traefik/v2/pkg/middlewares/headers.(*Header).ServeHTTP(0xc00083dd80, 0x2ea7660, 0xc000879ea0, 0xc000a53b00)
/go/src/github.com/containous/traefik/pkg/middlewares/headers/header.go:51 +0x133
github.com/containous/traefik/v2/pkg/middlewares/headers.(*headers).ServeHTTP(0xc00083dda0, 0x2ea7660, 0xc000879ea0, 0xc000a53b00)
/go/src/github.com/containous/traefik/pkg/middlewares/headers/headers.go:75 +0x52
github.com/containous/traefik/v2/pkg/middlewares/tracing.(*Wrapper).ServeHTTP(0xc000659c50, 0x2ea7660, 0xc000879ea0, 0xc000a53b00)
/go/src/github.com/containous/traefik/pkg/middlewares/tracing/wrapper.go:57 +0x16a
github.com/containous/traefik/v2/pkg/middlewares/headers.secureHeader.ServeHTTP.func1(0x2eb97e0, 0xc0002fa8c0, 0xc000a53b00)
/go/src/github.com/containous/traefik/pkg/middlewares/headers/secure.go:52 +0xea
github.com/unrolled/secure.(*Secure).HandlerFuncWithNextForRequestOnly(0xc000541e00, 0x2eb97e0, 0xc0002fa8c0, 0xc000a53a00, 0xc000f08fc8)
/go/pkg/mod/github.com/unrolled/secure@v1.0.7/secure.go:228 +0x201
github.com/containous/traefik/v2/pkg/middlewares/headers.secureHeader.ServeHTTP(0x2e5a420, 0xc000659c50, 0xc000541e00, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
/go/src/github.com/containous/traefik/pkg/middlewares/headers/secure.go:51 +0x7a
github.com/containous/traefik/v2/pkg/middlewares/headers.(*headers).ServeHTTP(0xc00083de20, 0x2eb97e0, 0xc0002fa8c0, 0xc000a53a00)
/go/src/github.com/containous/traefik/pkg/middlewares/headers/headers.go:75 +0x52
github.com/containous/traefik/v2/pkg/middlewares/tracing.(*Wrapper).ServeHTTP(0xc000659e30, 0x2eb97e0, 0xc0002fa8c0, 0xc000a53a00)
/go/src/github.com/containous/traefik/pkg/middlewares/tracing/wrapper.go:57 +0x16a
github.com/containous/traefik/v2/pkg/middlewares/accesslog.(*FieldHandler).ServeHTTP(0xc000724c80, 0x2eb97e0, 0xc0002fa8c0, 0xc000a53a00)
/go/src/github.com/containous/traefik/pkg/middlewares/accesslog/field_middleware.go:29 +0x18d
github.com/gorilla/mux.(*Router).ServeHTTP(0xc000b96d80, 0x2eb97e0, 0xc0002fa8c0, 0xc000a53800)
/go/pkg/mod/github.com/containous/mux@v0.0.0-20181024131434-c33f32e26898/mux.go:133 +0x112
github.com/containous/traefik/v2/pkg/middlewares/recovery.(*recovery).ServeHTTP(0xc000b02da0, 0x2eb97e0, 0xc0002fa8c0, 0xc000a53800)
/go/src/github.com/containous/traefik/pkg/middlewares/recovery/recovery.go:33 +0x104
github.com/containous/traefik/v2/pkg/middlewares/accesslog.(*FieldHandler).ServeHTTP(0xc000725300, 0x2eb97e0, 0xc0002fa8c0, 0xc000a53800)
/go/src/github.com/containous/traefik/pkg/middlewares/accesslog/field_middleware.go:29 +0x18d
github.com/containous/traefik/v2/pkg/middlewares/requestdecorator.(*RequestDecorator).ServeHTTP(0xc0003e6ee8, 0x2eb97e0, 0xc0002fa8c0, 0xc000a53700, 0xc000f09768)
/go/src/github.com/containous/traefik/pkg/middlewares/requestdecorator/request_decorator.go:47 +0x37d
github.com/containous/traefik/v2/pkg/middlewares/requestdecorator.WrapHandler.func1.1(0x2eb97e0, 0xc0002fa8c0, 0xc000a53700)
/go/src/github.com/containous/traefik/pkg/middlewares/requestdecorator/request_decorator.go:84 +0x83
net/http.HandlerFunc.ServeHTTP(0xc000b03340, 0x2eb97e0, 0xc0002fa8c0, 0xc000a53700)
/usr/local/go/src/net/http/server.go:2041 +0x44
github.com/containous/traefik/v2/pkg/server/router/tcp.(*Manager).buildEntryPointHandler.func1(0x2eb97e0, 0xc0002fa8c0, 0xc000a53700)
/go/src/github.com/containous/traefik/pkg/server/router/tcp/router.go:194 +0x16f
net/http.HandlerFunc.ServeHTTP(0xc000b03760, 0x2eb97e0, 0xc0002fa8c0, 0xc000a53700)
/usr/local/go/src/net/http/server.go:2041 +0x44
github.com/containous/traefik/v2/pkg/middlewares.(*HTTPHandlerSwitcher).ServeHTTP(0xc0003e6ea8, 0x2eb97e0, 0xc0002fa8c0, 0xc000a53700)
/go/src/github.com/containous/traefik/pkg/middlewares/handler_switcher.go:23 +0x70
github.com/containous/traefik/v2/pkg/middlewares/forwardedheaders.(*XForwarded).ServeHTTP(0xc000626410, 0x2eb97e0, 0xc0002fa8c0, 0xc000a53700)
/go/src/github.com/containous/traefik/pkg/middlewares/forwardedheaders/forwarded_header.go:173 +0x10b
net/http.serverHandler.ServeHTTP(0xc0002fa1c0, 0x2eb97e0, 0xc0002fa8c0, 0xc000a53700)
/usr/local/go/src/net/http/server.go:2836 +0xa3
net/http.(*conn).serve(0xc000a26320, 0x2ec39a0, 0xc0002539c0)
/usr/local/go/src/net/http/server.go:1924 +0x86c
created by net/http.(*Server).Serve
/usr/local/go/src/net/http/server.go:2962 +0x35c
" middlewareName=traefik-internal-recovery middlewareType=Recovery
```
### Possible Solution
<!--- Not obligatory, but suggest a fix/reason for the bug -->
Deploy the new Traefik version 2.3.2.Maintenance Cycle 2020-11Andre LehmannAndre Lehmannhttps://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/18Nextcloud Startpage - footer Text is black and not readable due to dark backg...2020-11-12T10:15:04+01:00Timm Willetimm.wille@ose-germany.deNextcloud Startpage - footer Text is black and not readable due to dark background picture## Expected Behavior
password reset etc → possible to read
## Current Behavior
black text → not readable
## Possible Solution
white text## Expected Behavior
password reset etc → possible to read
## Current Behavior
black text → not readable
## Possible Solution
white textMaintenance Cycle 2020-11Andre LehmannAndre Lehmannhttps://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/35Transfer OpenEcoLab Website Repository to Gitlab2021-03-20T21:30:06+01:00Andre LehmannTransfer OpenEcoLab Website Repository to GitlabThe current OpenEcoLab Website Repository is hosted on our old git service (git.opensourceecology.de). Because I want to retire the old service and replace it entirely with this Gitlab, the website repo must be transfered.
Tasks:
- [x]...The current OpenEcoLab Website Repository is hosted on our old git service (git.opensourceecology.de). Because I want to retire the old service and replace it entirely with this Gitlab, the website repo must be transfered.
Tasks:
- [x] Import repository into the correct group
- [x] Update the repo url on the website
- [x] Enable the website to push changes to the repositoryMaintenance Cycle 2020-12Andre LehmannAndre Lehmannhttps://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/52Shutdown Gitea2021-02-15T16:50:34+01:00Andre LehmannShutdown GiteaWe now have a new home for out Git Projects at our Gitlab instance, therefore we can transfer the remaining projects from Gitea and shut its service down.
Tasks:
- [x] Check what projects still needs to be transferred
- [x] Ask the pro...We now have a new home for out Git Projects at our Gitlab instance, therefore we can transfer the remaining projects from Gitea and shut its service down.
Tasks:
- [x] Check what projects still needs to be transferred
- [x] Ask the project maintainer to transfer their projects
- [x] Delete old projects from Gitea
- [x] Shutdown Gitea
- [x] Archive its dataMaintenance Cycle 2021-01Andre LehmannAndre Lehmann2021-02-15https://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/50Connect Hedgedoc to SSO2021-03-30T15:42:02+02:00Andre LehmannConnect Hedgedoc to SSOTasks:
- [x] Check the options for integrating SSO (Oauth, SAML, ...)
- [x] Figure out how to migrate existing accounts
- [x] Create missing accounts in SSO
- [x] Schedule migration
- [x] Perform migrationTasks:
- [x] Check the options for integrating SSO (Oauth, SAML, ...)
- [x] Figure out how to migrate existing accounts
- [x] Create missing accounts in SSO
- [x] Schedule migration
- [x] Perform migrationMaintenance Cycle 2021-01Andre LehmannAndre Lehmannhttps://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/49Update Hedgedoc (CodiMD)2021-01-16T23:34:03+01:00Andre LehmannUpdate Hedgedoc (CodiMD)We need to update out CodiMD instance, so that we can start to migrate to use SSO.We need to update out CodiMD instance, so that we can start to migrate to use SSO.Maintenance Cycle 2021-01Andre LehmannAndre Lehmannhttps://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/46When Inserting an Emoji CodiMD Crashes2021-01-16T23:35:20+01:00Timm Willetimm.wille@ose-germany.deWhen Inserting an Emoji CodiMD Crashes<!---
PLEASE READ THIS!
This is the template for describing a BUG (problem; unexpected behavior). If
your intention is to file a feature request or something else, please use the
appropriate template for that instead.
Before creating ...<!---
PLEASE READ THIS!
This is the template for describing a BUG (problem; unexpected behavior). If
your intention is to file a feature request or something else, please use the
appropriate template for that instead.
Before creating a new ticket, please search for existing tickets that match your
issue description, to avoid creating a duplicate.
--->
### Summary
<!-- Summarize the bug encountered concisely. -->
### Current Behavior
<!--- Describe what actually happens. -->
### Expected Behavior
<!-- Describe what you should see instead. -->
### Steps to Reproduce
<!--- Describe how one can reproduce the issue. -->
1. Copy an Emoji like 🚂
2. Paste it in CodiMD
### Context/Logs
<!--- Provide context that might help us to come up with a solution. If you have
relevant logs use Markdown code blocks (```) to format them. -->
CodiMD shows 400 error.Maintenance Cycle 2021-01Andre LehmannAndre Lehmannhttps://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/77Import of repositories from Gitlab.com and Github.com2021-02-28T20:33:56+01:00Andre LehmannImport of repositories from Gitlab.com and Github.com<!---
PLEASE READ THIS!
This is the template for describing a BUG (problem; unexpected behavior). If
your intention is to file a feature request or something else, please use the
appropriate template for that instead.
Before creating ...<!---
PLEASE READ THIS!
This is the template for describing a BUG (problem; unexpected behavior). If
your intention is to file a feature request or something else, please use the
appropriate template for that instead.
Before creating a new ticket, please search for existing tickets that match your
issue description, to avoid creating a duplicate.
--->
### Summary
<!-- Summarize the bug encountered concisely. -->
This Gitlab throws an error, when an import of a Gitlab.com repository is attempted (see https://gitlab.opensourceecology.de/verein/projekte/wh100/wirkunghoch100_osh_oer_module/-/issues/9).
### Context/Logs
<!--- Provide context that might help us to come up with a solution. If you have
relevant logs use Markdown code blocks (```) to format them. -->
![](https://gitlab.opensourceecology.de/verein/projekte/wh100/wirkunghoch100_osh_oer_module/uploads/a5dc2320cda3ed0416a1b82c348da7ac/image.png)
### Possible Solution
<!--- Not obligatory, but suggest a fix/reason for the bug -->Maintenance Cycle 2021-02Andre LehmannAndre Lehmannhttps://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/76Wechseln von Branches via Gui2021-02-24T12:50:58+01:00Timm Willetimm.wille@ose-germany.deWechseln von Branches via Guihttps://gitlab.opensourceecology.de/verein/vorstand/finanzen/finanzenhttps://gitlab.opensourceecology.de/verein/vorstand/finanzen/finanzenMaintenance Cycle 2021-02https://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/48Archive Etherpad2021-05-20T19:29:37+02:00Andre LehmannArchive EtherpadOur plan is to retire Etherpad, which is currently running at [pad.opensourceecology.de](https://pad.opensourceecology.de). Before we actually can shutdown the platform, we need to inform the active users. We will proceed as follows:
- ...Our plan is to retire Etherpad, which is currently running at [pad.opensourceecology.de](https://pad.opensourceecology.de). Before we actually can shutdown the platform, we need to inform the active users. We will proceed as follows:
- [x] Write an note for the users
- [x] Insert the note as a banner in the pad
- [x] Make the pad edit only, so that no new pads can be created
- [x] 15.02 Make the pad read-only
- [x] 15.04 Archive the padMaintenance Cycle 2021-04Andre LehmannAndre Lehmann2021-02-15https://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/53Configure Gitlab CI2021-08-14T18:59:07+02:00Andre LehmannConfigure Gitlab CI<!---
PLEASE READ THIS!
This is the template for proposing a new FEATURE (new functionality). If your
intention is to report a bug or something else, please use the appropriate
template for that instead.
Before creating a new ticket, ...<!---
PLEASE READ THIS!
This is the template for proposing a new FEATURE (new functionality). If your
intention is to report a bug or something else, please use the appropriate
template for that instead.
Before creating a new ticket, please search for existing tickets that match your
issue description, to avoid creating a duplicate.
--->
### Problem to solve
<!-- What problem do we solve? Try to define the who/what/why of the opportunity
as a user story. For example, "As a (who), I want (what), so I can (why/value)."
-->
We need the Gitlab CI feature to automate various processes in the IT and also help regular users to run automated tasks for their projects. A comprehensive list of Gitlab CI features can be found [here](https://about.gitlab.com/stages-devops-lifecycle/continuous-integration/).
### Intended users
<!-- Who will use this feature? It's okay to write "Unknown" and fill this field
in later. -->
- Administrators:
- Build Docker Images
- Deploy applications
- Automate tasks
- Users:
- Automate tasks
### Other links/references
<!-- E.g. related issues/MRs -->
- Official Doc: https://docs.gitlab.com/ee/ci/
- Introduction to Gitlab CI: https://medium.com/faun/beginner-friendly-introduction-to-gitlab-ci-cd-1c80ee5ba0aeMaintenance Cycle 2021-06Andre LehmannAndre Lehmannhttps://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/30Distinct favicon for each web application2024-02-08T22:45:44+01:00Andre LehmannDistinct favicon for each web applicationNow that we have a couple of web applications running it might be nice, if we have a distinct favicon for each of the applications, so it is easier to navigate through open browser tabs. My idea is to combine the OSEG logo with a tiny lo...Now that we have a couple of web applications running it might be nice, if we have a distinct favicon for each of the applications, so it is easier to navigate through open browser tabs. My idea is to combine the OSEG logo with a tiny logo of the application software to make it distinct.
- [x] Create favicons and put them into a repository: https://gitlab.opensourceecology.de/server/favicons
- [ ] Install the favicons in the different web services
- [x] Blog: [Uploaded and set via customizer](https://kinsta.com/knowledgebase/wordpress-favicon/)
- [x] Website: green
- [ ] Cloud: blue, set via web interface, Error: `Exception: Argument 2 passed to OCA\Theming\ImageManager::setCachedImage() must be of the type string, null given, called in /container/www/apps/theming/lib/Controller/IconController.php on line 167`
- [x] GitLab: red, set via web interface
- [x] Wiki: grey, set via favicon.ico
- [x] Hedgedoc: black, favicon.ico mounted inside container
- [x] Etherpad: teal
- [x] Survey: yellow, favicon.ico mounted inside container (`/container/www/upload/themes/survey/erweitert_fruity/files`)
- [x] Forum: violet, favicon.ico mounted inside containerMaintenance Cycle 2021-09Andre LehmannAndre Lehmannhttps://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/28Gitlab Modifications2022-01-25T11:21:41+01:00Andre LehmannGitlab ModificationsSome modifications of the Gitlab platform would be nice:
- [x] Fix Wiki reactivation issue (#24)
- [x] Add icons to all relevant groups and projects
- [x] Edit the Welcome Page
- [x] Description Text: What is the platform about? How t...Some modifications of the Gitlab platform would be nice:
- [x] Fix Wiki reactivation issue (#24)
- [x] Add icons to all relevant groups and projects
- [x] Edit the Welcome Page
- [x] Description Text: What is the platform about? How to Login?
- [x] Create Issue templates (Examples: https://gitlab.com/gitlab-org/gitlab/-/tree/master/.gitlab/issue_templates)
- [x] Bug Report
- [x] Feature Proposal
- [x] Enhancements
- [x] Documentation Change
- [x] Update documentation of Ticket System (this issue tracker)
- [ ] Write a documentation on how to maintain the Ticket System
- [x] Enable Features?
- [x] LFS? https://gitlab.opensourceecology.de/help/administration/lfs/index.md
- [x] Gitlab CI (#53)Maintenance Cycle 2021-09Alexander StellmachAlexander Stellmachhttps://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/99Recreate GitLab-CI configuration for OSEGeV Website2022-10-06T11:17:56+02:00Andre LehmannRecreate GitLab-CI configuration for OSEGeV WebsiteSee https://gitlab.opensourceecology.de/verein/koordination/pr/osegev-webseite/-/issues/108See https://gitlab.opensourceecology.de/verein/koordination/pr/osegev-webseite/-/issues/108Maintenance Cycle 2021-10Bastian Menningenbastian.menningen@ose-germany.deBastian Menningenbastian.menningen@ose-germany.dehttps://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/43Deploy Wikibase2021-09-10T18:43:38+02:00Andre LehmannDeploy Wikibase<!---
PLEASE READ THIS!
This is the template for proposing a new FEATURE (new functionality). If your
intention is to report a bug or something else, please use the appropriate
template for that instead.
Before creating a new ticket, ...<!---
PLEASE READ THIS!
This is the template for proposing a new FEATURE (new functionality). If your
intention is to report a bug or something else, please use the appropriate
template for that instead.
Before creating a new ticket, please search for existing tickets that match your
issue description, to avoid creating a duplicate.
--->
### Problem to solve
<!-- What problem do we solve? Try to define the who/what/why of the opportunity
as a user story. For example, "As a (who), I want (what), so I can (why/value)."
-->
Wikibase is a knowledge base software, that is intended to be used as a searchable database for hardware projects.
### Intended users
<!-- Who will use this feature? It's okay to write "Unknown" and fill this field
in later. -->
- Administrators: Ensure service availability, provide service maintenance
- Developers:
- write new queries for the knowledge base (current list of queries [here](https://github.com/OPEN-NEXT/LOSH/blob/master/OSH_metadata.md#competency-questions--use-cases))
- contribute to ontology development (current draft [here](https://github.com/OPEN-NEXT/LOSH/blob/master/osh-metadata.ttl))
- write new crawler modules based on the existent knowledge base (see [this issue](https://github.com/OPEN-NEXT/LOSH/issues/9))
- Users:
- developers:
- first and foremost facilitate design reuse
- replace manual packaging; metadata shall enable a download button for:
- production files (export only)
- developer files (sources only)
- full package (export + sources)
- manufacturers / service providers
- find OSH ready for decentralised (mass) production, maintenance and service provision
- later: include manufacturers in Wikibase to run matchmaking queries ("Where to buy this part?")
- researchers:
- support research on OSH by specialised queries on a very large (and partly manually curated) OSH knowledge base
### Further details
**tl;dr:** connecting open source hardware modules in a graph database – the ICT infrastructure for community-based innovation and circular economy as part of the H2020 research project [OPEN!NEXT](https://opennext.eu/) (no. 869984)
Find project information here: <https://github.com/OPEN-NEXT/LOSH>.
And a list of currently covered use cases here: <https://github.com/OPEN-NEXT/LOSH/blob/master/OSH_metadata.md#competency-questions--use-cases>
### Documentation
<!-- Add all known Documentation Requirements in this section -->
### Other links/references
<!-- E.g. related issues/MRs -->
- https://pad2.opensourceecology.de/y0vfkyLPSFGGK_sezQTCBA
### Tasks
- [x] Install MediaWiki https://wikibase.oho.wiki/
- [x] Install Wikibase Extension in MediaWiki
- [x] Install and configure ElasticSearch
- [x] Deploy application
- [x] Configure it
- [x] Install and configure required MediaWiki extensions
- [x] Test if it works
- [x] Install and configure Query Backend
- [x] Create a new Docker Image
- [x] Deploy application
- [x] Configure it
- [x] Test if it works
- [x] Install and configure Query Frontend https://wikibase.oho.wiki/qs/
- [x] Create a new Docker Image
- [x] Deploy application
- [x] Configure it
- [x] Test if it works
- [x] Configure Backup
- [ ] Add Monitoring
- [ ] Write DocumentationMaintenance Cycle 2021-10Andre LehmannAndre Lehmannhttps://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/54Upgrade Forum2022-12-14T12:23:00+01:00Andre LehmannUpgrade ForumOur forum is quite old, it needs to be updated.
Tasks:
- [x] Upgrade forum software
- [ ] Clear out spam accounts (see inactive users)
- [ ] Add better captcha for registrationOur forum is quite old, it needs to be updated.
Tasks:
- [x] Upgrade forum software
- [ ] Clear out spam accounts (see inactive users)
- [ ] Add better captcha for registrationMaintenance Cycle 2021-12Alexander StellmachAlexander Stellmachhttps://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/51Create a Status Page for our Services2022-01-25T11:05:01+01:00Andre LehmannCreate a Status Page for our Services<!---
PLEASE READ THIS!
This is the template for proposing a new FEATURE (new functionality). If your
intention is to report a bug or something else, please use the appropriate
template for that instead.
Before creating a new ticket, ...<!---
PLEASE READ THIS!
This is the template for proposing a new FEATURE (new functionality). If your
intention is to report a bug or something else, please use the appropriate
template for that instead.
Before creating a new ticket, please search for existing tickets that match your
issue description, to avoid creating a duplicate.
--->
### Problem to solve
<!-- What problem do we solve? Try to define the who/what/why of the opportunity
as a user story. For example, "As a (who), I want (what), so I can (why/value)."
-->
A status page, to display the availability and maintenance status of all our public facing services would be quite beneficial. Users could inform themself about the current status before creating any ticket, when a service appears to be down.
### Intended users
<!-- Who will use this feature? It's okay to write "Unknown" and fill this field
in later. -->
- Administrators:
- get a quick glance about services status
- inform users about
- Users:
- get information about the service status
- check availability and maintenance status, before creating a ticket
### Proposal
<!-- How are we going to solve the problem? -->
There is a [nice list of open-source status page software](https://github.com/ivbeg/awesome-status-pages) we can test out.
### Tasks
- [x] Check the list of status page software and identify potential candidates
- [ ] Test the potential candidates and pick one of them
- [ ] Create a plan to deploy the software on our server
- [ ] Integrate the system
- [ ] Write documentationMaintenance Cycle 2021-12