IT Tickets issueshttps://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues2021-03-29T16:14:42+02:00https://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/87Replace Favicon of the Blog2021-03-29T16:14:42+02:00Andre LehmannReplace Favicon of the Blog<!---
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)."
-->
The current favicon used for the OSEG Blog (blog.opensourceecology.de) is an older one, which doesn't comply with the current [Favicons line-up](https://gitlab.opensourceecology.de/verein/server/favicons). We should consider to replace it with the new green version in PNG format. The PNG files are smaller and might provide a better resolution for high dpi devices.
### Intended users
<!-- Who will use this feature? It's okay to write "Unknown" and fill this field
in later. -->
- any
### Proposal
<!-- How are we going to solve the problem? -->
The relevant contents of the [green favicon directory](https://gitlab.opensourceecology.de/verein/server/favicons/-/tree/master/generated-favicons/green) can be included in the OSEG Wordpress theme (`/wp-content/themes/underscores_oseg/favicon`). The paths in the file `site.webmanifest` need to be adapted to the theme path, then the only thing left to do is to include the following HTML code in the header:
```html
<link rel="apple-touch-icon" sizes="180x180" href="/wp-content/themes/underscores_oseg/favicon/apple-touch-icon.png">
<link rel="icon" type="image/png" sizes="32x32" href="/wp-content/themes/underscores_oseg/favicon/favicon-32x32.png">
<link rel="icon" type="image/png" sizes="16x16" href="/wp-content/themes/underscores_oseg/favicon/favicon-16x16.png">
<link rel="manifest" href="/wp-content/themes/underscores_oseg/favicon/site.webmanifest">
<meta name="msapplication-TileColor" content="#75b62f">
<meta name="theme-color" content="#75b62f">
```
### Further details
<!-- Include use cases, benefits, goals, or any other details that will help us
understand the problem better. -->
### Documentation
<!-- Add all known Documentation Requirements in this section -->
### Other links/references
<!-- E.g. related issues/MRs -->Bastian Menningenbastian.menningen@ose-germany.deBastian Menningenbastian.menningen@ose-germany.dehttps://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/86Static web hosting for user generated content2021-03-29T10:11:47+02:00Andre LehmannStatic web hosting for user generated content<!---
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 want to offer simple static web hosting for pages DIN-SPEC and other projects. For now the access can be a simple SFTP account.
### Intended users
<!-- Who will use this feature? It's okay to write "Unknown" and fill this field
in later. -->
- some members of the association
### Proposal
<!-- How are we going to solve the problem? -->
Provide a Nginx webserver, a domain pages.opensourceecology.de and a SFTP access.
### Further details
<!-- Include use cases, benefits, goals, or any other details that will help us
understand the problem better. -->
### Documentation
<!-- Add all known Documentation Requirements in this section -->
### Other links/references
<!-- E.g. related issues/MRs -->https://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/84Hosting Frontend LOSH (wikibase)2021-09-29T18:14:13+02:00Martin HäuerHosting Frontend LOSH (wikibase)Wikibase bietet (entgegen der Erwartungen der TUB) leider keine sinnvolle Möglichkeiten zur Datenvisualisierung. Insofern muss noch ein Frontend entwickelt und gehostet werden. Entwicklung wird keinesfalls bei OSEG landen (wahrscheinlich...Wikibase bietet (entgegen der Erwartungen der TUB) leider keine sinnvolle Möglichkeiten zur Datenvisualisierung. Insofern muss noch ein Frontend entwickelt und gehostet werden. Entwicklung wird keinesfalls bei OSEG landen (wahrscheinlich bei WMDE). Hosting kann bei OSEG landen, wenn wir das wollen.
Das Frontend wird einigermaßen simpel sein – ähnlich der [OKH-Seite](search.openknowhow.com), aber mit Projektseiten zur Anzeige der Metadaten, Filterfunktionen und ein paar Knöpfen mehr ('I built this', 'file an issue', 'report faulty data' etc.); konkret ist der Funktionsumfang noch nicht.
Pro Hosting:
- Front- & Backend aus einer Hand (Wikibase läuft ja schon bei uns)
- passt super ins Portfolio (neben dem Conformity Assessment Body)
- Suchmaschine/Register lockt ggf. Leute zu OSEG oder dient als Referenz
Con Hosting:
- zusätzliche Plattform mit allen damit verbundenen Aufwänden & Risiken
- zusätzliche Lieferfrist: Frontend müsste bis Anfang August eingebunden sein (Entwicklung durch anderen Partner steht noch aus und hat noch nicht begonnen)
- (mehr fällt mir gerade nicht ein)
---
1. Wie sieht das Meinungsbild bei Euch in der IT dazu aus? (@aisberg @alexander @bmen)
2. Was wären die Voraussetzungen/Anforderungen von unserer Seite, damit ein Hosting denkbar wäre?
3. Sonstige Wünsche?
Das Hosting könnte in den Vertrag aufgenommen werden oder unter der Hand laufen. Letzteres ist natürlich für OSEG einfacher, weil unverbindlicher. Weiß allerdings noch nicht, ob ich das durchgesetzt bekäme. Zwar bezogen sich alle Verhandlungen bisher ausschließlich auf Wikibase, aber damals war auch noch nicht klar, dass Wikibase keine Datenvisualisierung bietet. Das hat uns WMDE erst im Januar auf Nachfrage erzählt.
---
Edit: Repo des Frontends: https://github.com/wmde/LOSH-Frontend/https://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/83Domainwechsel Wikibase2021-09-01T12:20:20+02:00Martin HäuerDomainwechsel WikibaseMit der Ausgliederung von OHO (#56 #57) geht uns auch die Subdomain `wikibase.oho.wiki` verloren.
Das Projekt um Wikibase (LOSH) wird künftig 2 (Sub)Domains benötigen:
- backend (Wikibase) → vorgeschlagene Subdomain: `wikibase.ose-germ...Mit der Ausgliederung von OHO (#56 #57) geht uns auch die Subdomain `wikibase.oho.wiki` verloren.
Das Projekt um Wikibase (LOSH) wird künftig 2 (Sub)Domains benötigen:
- backend (Wikibase) → vorgeschlagene Subdomain: `wikibase.ose-germany.de`
- frontend (voraussichtl. v. WMDE entwickelt, vermutlich Mediawiki-basiert)
Da die Wikibase-Instanz für das Projekt erreichbar bleiben sollte, wäre es gut, wenn wir die Subdomain vor der OHO-Domainübergabe umschalten.
Sofern wir das Frontend hosten möchten (#84), würde ich `losh.ose-germany.de` dafür reservieren wollen.Andre LehmannAndre Lehmannhttps://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/81Add a security.txt to all websites2021-03-16T16:07:09+01:00Andre LehmannAdd a security.txt to all websites[security.txt](https://securitytxt.org) is used to defined a security policies and enables people from the outside to contact us, in case they find critical security flaws in our infrastructure.[security.txt](https://securitytxt.org) is used to defined a security policies and enables people from the outside to contact us, in case they find critical security flaws in our infrastructure.https://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/79E-Mail Vorlagen erstellen2021-03-06T20:18:13+01:00Andre LehmannE-Mail Vorlagen erstellen1. E-Mail Vorlagen (+ kurzer aussagekräftiger Betreff) in Deutsch und Englisch für:
- Einladung einen Account zu erstellen
- Auf welche Vereins-Plattformen die Personen dann Zugriff erhalten und welche Möglichkeiten ihnen dan...1. E-Mail Vorlagen (+ kurzer aussagekräftiger Betreff) in Deutsch und Englisch für:
- Einladung einen Account zu erstellen
- Auf welche Vereins-Plattformen die Personen dann Zugriff erhalten und welche Möglichkeiten ihnen dann offen stehen
- Ein Survey ist auszufüllen https://cloud.opensourceecology.de/apps/forms/xiEwEFzwkXdHBqXz
- Kurze Infos weshalb wir die Infos aus dem Survey benötigen: Einrichtung Account, Einordnung wer die Person
- Willkommen - Informationen zum Durchstarten
- Die nächsten Schritte, nachdem sie einen Account erhalten haben (Email verifizieren mit Link, den sie bekommen haben, einmal anmelden und Passwort ändern)
- Was können sie nun alles machen
- Wo finden sie weitere Informationen und Ansprechpartner
- Abschied bei Löschen des Accounts
2. Wo können diese abgelegt werden, sodass diese einfach abgerufen und angepasst werden können?
3. Welches Format sollen diese haben, also sollen die Nachrichten nur per Mail verschickt werden?
4. Soll eine Art Automatisierung für das Versenden der Mails eingerichtet werden?https://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/62Keycloak as Identity Broker and Identity Provider for external Users2022-01-25T11:24:36+01:00Alexander StellmachKeycloak as Identity Broker and Identity Provider for external Users### Problem to solve
You might have two different Keycloak instance running: one for the external users (Keyloak-External)and another for the internal members (Keycloak-Internal). We want to allow our guest users to also authenticate wi...### Problem to solve
You might have two different Keycloak instance running: one for the external users (Keyloak-External)and another for the internal members (Keycloak-Internal). We want to allow our guest users to also authenticate with external service without going for registering a new account.
### Intended users
External users who actively participate in oseg related projects
### Proposal
<!-- How are we going to solve the problem? -->
### Further details
<!-- Include use cases, benefits, goals, or any other details that will help us
understand the problem better. -->
### Documentation
<!-- Add all known Documentation Requirements in this section -->
### Other links/references
https://link.medium.com/eplYelxZBdbAlexander StellmachAlexander Stellmachhttps://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-12https://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/40Concept for Clustering2020-10-18T15:18:31+02:00Andre LehmannConcept for Clustering<!---
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)."
-->
### Intended users
<!-- Who will use this feature? It's okay to write "Unknown" and fill this field
in later. -->
### Proposal
<!-- How are we going to solve the problem? -->
### Further details
<!-- Include use cases, benefits, goals, or any other details that will help us
understand the problem better. -->
### Documentation
<!-- Add all known Documentation Requirements in this section -->
### Other links/references
<!-- E.g. related issues/MRs -->https://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/39Chat- & VOIP-Service2020-10-18T15:09:14+02:00Andre LehmannChat- & VOIP-Service<!---
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)."
-->
### Intended users
<!-- Who will use this feature? It's okay to write "Unknown" and fill this field
in later. -->
### Proposal
<!-- How are we going to solve the problem? -->
Find a software solution that satisfies the requirements:
- open-source, self hosted
- chat
- voice and video chat
- screensharing, doing presentations ...
- filesharing
- requirements for the users is only a webbrowser and maybe a plugin
### Further details
<!-- Include use cases, benefits, goals, or any other details that will help us
understand the problem better. -->
### Documentation
<!-- Add all known Documentation Requirements in this section -->
### Other links/references
<!-- E.g. related issues/MRs -->https://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/36Test OhMyForm and compare to LimeSurvey2023-10-03T23:30:33+02:00Andre LehmannTest OhMyForm and compare to LimeSurvey<!---
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 are using LimeSurvey as a survey tool, which is quite complex and cumbersome to use. The software [OhMyForm](https://github.com/ohmyform/ohmyform) might provide us with all the features we actually need while being easier to use. We should check OhMyForm out.
### Intended users
<!-- Who will use this feature? It's okay to write "Unknown" and fill this field
in later. -->
Survey creators
### Proposal
<!-- How are we going to solve the problem? -->
Setup OhMyForm and compare to LimeSurvey
### Further details
<!-- Include use cases, benefits, goals, or any other details that will help us
understand the problem better. -->
### Documentation
<!-- Add all known Documentation Requirements in this section -->
### Other links/references
<!-- E.g. related issues/MRs -->Alexander StellmachAlexander Stellmachhttps://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/32Wildcard TLS Certificates (+ DNS using DNSec)2022-01-25T11:20:00+01:00Andre LehmannWildcard TLS Certificates (+ DNS using DNSec)<!---
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)."
-->
Currently we create a TLS certificate for each of our services. As it our platform grows, the more certificates will be in use. There are certain limits imposed by Let's Encrypt on how many certificates can be re-issued and therefore it might be beneficial to keep the amount of certificates as low as possible. To do so, we could use a wildcard certificate. Problem is, we currently cannot create such a certificate, because it requires a DNS nameserver with an API, which we don't have.
### Intended users
<!-- Who will use this feature? It's okay to write "Unknown" and fill this field
in later. -->
- Everyone browsing our services
### Proposal
<!-- How are we going to solve the problem? -->
An option might be to use an external nameserver while still keeping our Domain registrar. For example we could use the service [deSEC](https://desec.io/#!), which offers an API, DNSec and hosting in Germany. With this, it should be possible to create wildcard certificates over Let's Encrypt.
### Further details
<!-- Include use cases, benefits, goals, or any other details that will help us
understand the problem better. -->
A use cases might be:
- Use a single wildcard certificate (*.opensourceecology.de) for the gros of our public services and maybe another on for administrational services.
- With DNSec we might also be able to use encrypted-sni with TLS v1.3
Additional Resources:
- https://administrator.de/forum/funktioniert-subdomains-fritzbox-537565.html#comment-1420979
- https://blog.cloudflare.com/encrypted-sni/
### Documentation
<!-- Add all known Documentation Requirements in this section -->
### Other links/references
<!-- E.g. related issues/MRs -->Andre LehmannAndre Lehmannhttps://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/31Automatically renew Mumble TLS certificate2020-10-14T19:05:36+02:00Andre LehmannAutomatically renew Mumble TLS certificate<!---
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)."
-->
Currently Mumble is using a Let's Encrypt certificate, that is manually copied from the Traefik certificate store. Because of the short lifetime of the certificates, it will expire after only 3 month. If the certificate is not changed in this period, users connecting to Mumble will receive a warning message about the expired certificate. Therefore the error prone manual certificate exchange should be automated.
### Proposal
<!-- How are we going to solve the problem? -->
There are some scripts, that can watch Traefiks certificate store for changes and automatically extract changed certs. We can use this feature and combine it with a custom script, that exchanges the cert of Mumble and restarts the Mumble server.
### Further details
<!-- Include use cases, benefits, goals, or any other details that will help us
understand the problem better. -->
### Documentation
<!-- Add all known Documentation Requirements in this section -->
### Other links/references
<!-- E.g. related issues/MRs -->https://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/29Central User Management and SSO2022-01-25T11:21:31+01:00Andre LehmannCentral User Management and SSO**General Tasks:**
- [x] install and configure Keycloak
- [ ] install and configure OpenLDAP
- [x] setup admin accounts
- [ ] propose user, group and role structure
- [x] setup normal user accounts accounts
- [x] notify user about their...**General Tasks:**
- [x] install and configure Keycloak
- [ ] install and configure OpenLDAP
- [x] setup admin accounts
- [ ] propose user, group and role structure
- [x] setup normal user accounts accounts
- [x] notify user about their new user account
- [ ] configure user federation with LDAP
- [ ] setup permission structure
**Integrate Platforms:**
1. [x] Git Service (Gitlab)
2. [x] MariaDB Frontend (phpMyAdmin)
3. [x] Dashboard (Traefik)
4. [x] Pad (Hedgedoc) #50
5. [x] Blog (Wordpress)
6. [ ] Wiki (MediaWiki)
7. [ ] Cloud File Share (Nextcloud)
Handle Account Migration (Format: `SSO Account -> Plattform Account`)
- `foo -> ?`:
- Create platform account by impersonating the SSO account
- `foo -> foo`:
- Check if the owner of the SSO account is the same as the platform account
- migrate account to SSO
- `foo -> bar`:
- Check if the SSO account is the same as the platform account (match email)
- rename platform account and migrate to SSO
- `? -> qot`:
- user has no SSO account yet
- check if user is member of OSEG
- either create a SSO account or delete the platform accountMaintenance Cycle 2021-12Alexander StellmachAlexander Stellmachhttps://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/26Create a new community website for OSEG2022-03-14T22:21:49+01:00Andre LehmannCreate a new community website for OSEGThe current community website is not very well maintained. We need to assemble a working group and create a new one.
**Tasks:**
- [ ] Gather people willing to help out
- [ ] Schedule a first meeting and gather requirements
- [ ] ...The current community website is not very well maintained. We need to assemble a working group and create a new one.
**Tasks:**
- [ ] Gather people willing to help out
- [ ] Schedule a first meeting and gather requirements
- [ ] ...Bastian Menningenbastian.menningen@ose-germany.deBastian Menningenbastian.menningen@ose-germany.dehttps://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/14Webserver cannot access files created by users2020-09-14T13:40:36+02:00AdministratorWebserver cannot access files created by users*Created by: Aisberg*
## Expected Behavior
<!--- If you're describing a bug, tell us what should happen -->
<!--- If you're suggesting a change/improvement, tell us how it should work -->
All backend files (reachable over SSH) created b...*Created by: Aisberg*
## Expected Behavior
<!--- If you're describing a bug, tell us what should happen -->
<!--- If you're suggesting a change/improvement, tell us how it should work -->
All backend files (reachable over SSH) created by the users should be readable and writeable by the corresponding webserver as well.
## Current Behavior
<!--- If describing a bug, tell us what happens instead of the expected behavior -->
<!--- If suggesting a change/improvement, explain the difference from current behavior -->
The webserver cannot access the files leading due to permission error.
## Possible Solution
<!--- Not obligatory, but suggest a fix/reason for the bug, -->
<!--- or ideas how to implement the addition or change -->
Change the ACL to include the webserver.Andre LehmannAndre Lehmann