Skip to content

Meeting 2026 05 28 (Service Provider Group)

Stefan edited this page May 28, 2026 · 18 revisions

Time: 14:00 - 16:00 Place: Online

Coordination:

  • Moritz Brennecke (MB)(Service Provider Group Secretary), Valentine Arrieta (VA),

Present:

  • Camille Blanchon (CB)
  • Cyril Meder (CM)
  • Arnaud Poncet-Montanges (AP)
  • Stefan Burckhardt(SB)
  • Gérard Sollberger (GS)
  • Luis Erik Mallea Veizaga (LEMV)

Excused :

  • Lucie Nicolier (LN),
  • Fanny Ruby (FR),

🤝 Organisation

  • New structure of meetings is accepted and in use (organisation, agenda,...).
  • New person certification Newis is in planning, no other demands.

🗓️ Agenda

✈️ Projects

  • TEKSI Training / Academy https://github.com/teksi/academy/discussions -> Goal is to publish date and minimal content before summer vacation, user training group (Cyrile / Lucie) will contact Stefan in the next weeks -> For next Codir (26.06.2025) an offer is given by the user training group

  • HELPDESK :

    • Support of TEKSI Service providers - how do TEKSI Service Providers get support if they cannot fix issues / problems themselves (AP)
    • Draft Helpdesk Process : https://github.com/teksi/Home/wiki/Helpdesk-process
    • Add point "issues and functionalities" to the service provider group to the contents. Arnaud proposes a labeling of issues and fonctionalities in order to decide if to discuss them in the service provider group or technical or user group.
    • Also create label to see if "Certifierd TEKSI Provider" is needed and what main category the issue is: [Infrastructure, QGIS, Module TEKSI]
    • Added proposal to still document solved issues: D[Problème résolu - still open issue with problem and document the solution so that others do not have to solve the same thing]

Schema

flowchart TD

A[Utilisateur rencontre un problème] --> B[Il contacte son prestataire]

B --> C{Le prestataire peut-il résoudre le problème ?}
C -->|Oui| D[Problème résolu - still open issue with problem and document the solution so that others do not have to solve the same thing]
C -->|Non| E{Origine du problème ?}

E -->|Infrastructure| F[Ouvrir ticket chez prestataire informatique]
E -->|QGIS| G[Ouvrir ticket GitHub QGIS<br/>Transmettre au prestataire QGIS]
E -->|Module TEKSI| H[Ouvrir ticket GitHub TEKSI<br/>Assigner à prestataire certifié]

H --> I{Prestataire certifié peut-il traiter ?}
I -->|Oui| J[Résolution en cours]
I -->|Non| K[Escalade au groupe prestataire / responsable technique TEKSI]

K --> L{Bug générique ?}
L -->|Oui| M[Pris en charge par maintenance TEKSI]
L -->|Non| N[Évolution souhaitée<br/>Validation + recherche de financement]
Loading

🚧 Issues and functionalities Technical discussion

Technical issues related to Service providers

  • Here should be proposed issues to be discussed by providers

🧙‍♂️ Provider training - Live demonstration of an QGIS / TMMT installation with issues

  • Most providers have a preconfigured installation in a shell (.bat or text file which can be launched in windows command) to install Qgis together with all dependencies. Arnaud sends an example. Documenation see https://trac.osgeo.org/osgeo4w/wiki/CommandLine
  • Issue has been fixed (pydantic): https://github.com/opengisch/oqtopus/issues/216#issuecomment-4518503701
  • Pip - Needs to be also with OSGeo4W (not shipped with TMMT) - AP creates an issue for this (documentation needed)
  • Attention with personalized Qgis.ini files (from profiles) -> Can create an error with CRS / WKT - seems not related to TMMT - QGIS.ini. Use defualt profile.
  • Documentation: Add printscreen and explain: The system language of windows has to be french switzerland and the qmt file fr_CH. Forcing the language in Qgis does not create the traduction.

Last meeting

Clone this wiki locally