IT Tickets issueshttps://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues2021-02-03T19:09:28+01:00https://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/58Jahresbericht IT-Teil2021-02-03T19:09:28+01:00Lukas SchattenhoferJahresbericht IT-TeilFür den Jahresbericht bräuchte ich eine Seite von der IT, was im letzten Jahr passiert ist.
Eine Tabelle mit aktuellen Systemen wäre auch gut. Ich hab hier mal eine kleine Vorlage vorbereitet:
https://pad2.opensourceecology.de/it-jahresb...Für den Jahresbericht bräuchte ich eine Seite von der IT, was im letzten Jahr passiert ist.
Eine Tabelle mit aktuellen Systemen wäre auch gut. Ich hab hier mal eine kleine Vorlage vorbereitet:
https://pad2.opensourceecology.de/it-jahresbericht2020#Alexander StellmachAlexander Stellmach2021-02-03https://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/33Write documentation for the server setup2021-03-01T16:43:56+01:00Andre LehmannWrite documentation for the server setup<!---
PLEASE READ THIS!
This is the template for describing a DOCUMENTATION CHANGE. 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 sea...<!---
PLEASE READ THIS!
This is the template for describing a DOCUMENTATION CHANGE. 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
<!-- Include the following detail as necessary:
* What docs or doc section affected? Include links or paths.
* Is there a problem with a specific document, or a feature/process that's not addressed sufficiently in docs?
* Any other ideas or requests?
* What audience is it intended for?
-->
I set up the server semi-automatically using Ansible. I need to document my steps and thoughts in a transparent manner.
### Proposal
<!-- Further specifics for how can we solve the problem. -->
The documentation should be put into the private server wiki.
### Who can address the issue
<!-- What if any special expertise is required to resolve this issue? -->
The documentation can only written by me.
### Other links/references
<!-- E.g. related issues/MRs -->Andre LehmannAndre Lehmannhttps://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/23Do we need an other repo for tracking OSEG wide, non IT related issues?2020-10-18T19:29:15+02:00AdministratorDo we need an other repo for tracking OSEG wide, non IT related issues?*Created by: hoijui*
... or should we rather change the description of this repo instead, to make it more general, to encompass all issues (not just IT ones)?*Created by: hoijui*
... or should we rather change the description of this repo instead, to make it more general, to encompass all issues (not just IT ones)?