Skip to content

Telcos Meetings

Jump to bottom
Oliver Egger edited this page Feb 5, 2025 · 22 revisions

Every Wednesday on the first on month we do a short coordination call for the Mobile Access Gateway with Google Meet at 9am (Zurich Time): https://meet.google.com/met-whzc-qwi, by phone: ‪(CH) +41 43 430 94 54‬ PIN: ‪590 884 665‬#, additional numbers: https://tel.meet/met-whzc-qwi?pin=1939660559668

** Agenda 5.2.2025, 09.00 **

  • Introduction
  • Participants: Oliver Egger, Luis de Soiusa
  • Experience with Release 1.0.0?
  • Hold off further meetings until new requests / usage please contact Oliver

Agenda 6.11.2024, 09.00

  • Introduction
  • Participants: Dmytro Rud, Luís de Sousa, Quentin Ligier
  • Open PR / Issues
  • Release Plan: v1.0.0 before the next meeting
  • Next meeting: to be discussed, the 4.12 won't work

Agenda 4.9.2024, 09.00

  • Introduction
  • Participants: Dmytro Rud, Oliver Egger, Sabrina Vivien Küffer
  • Open PR / Issues see Issues
  • Release Plan version for projectathon
  • Next meeting 5.10, 09.00

Agenda 7.8.2024, 09.00 (Could be moved potentially a week later)

  • Introduction
  • Participants: Dmytro Rud, Leonardo Staffolani, Luís de Sousa, Oliver Egger, Quentin Ligier, Sabrina Vivien Küffer, Stefano Limonta
  • Open PR / Issues see Issues
  • Release Plan version for projectathon
  • Next meeting 4.9, 09.00

Agenda 3.7.2024, 09.00

  • Participants
    • Bas van Drongelen, Dmytro Rud, Hamdi Hagberg, leonardo staffolani, Luís de Sousa, Oliver Egger, Quentin Ligier, Stefano Limonta
  • Open PR / Issues
  • Opcoming Projectathon
    • Post: Will come with the Mobile Access Gateway with a UI to test it to against it (intermediate layer) for MHD
    • ahdis: Plain Mobile Access Gateway for testing
    • Continue discussion in August and schedule a separate meeting in September
  • Release Plan

Agenda 15.5.2024, 09.00

  • Introduction
  • Participants
    • adesso: Dmytro
    • Post: Luis, Leonardo
    • ahdis: Oliver
  • Open PR / Issues
    • ahdis: multiple IdP integration (trustId) release with v070
    • post: fork of mobile access gateway on github for collaboration
    • discussion about mapping between xds and mhd: see issue #123
  • Release Plan
    • Discussion for participating at the connectathon

Agenda 3.4.2024, 09.00

  • Introduction
  • Participants
    • BFH: Alexander
    • adesso: Dmytro, Benjamin
    • Post: Stefano, Luis, Bas
    • ahdis: Quentin, Oliver
  • Open PR / Issues
  • Release Plan
  • Next Meeting 15.5 09.00 (1.5 public holiday, 5.6 IHE Connectathon)
  • AOB

Protocol 6.3.2024, 09.00

  • Introduction
  • Participants
    • BFH: Alexander
    • adesso: Benjamin, Dmytro, Hoang
    • Post: Leonardo, Stefano, David, Andreas
    • ahdis: Quentin, Oliver
  • Open PR / Issues
  • Release Plan
    • ahdis: work on 1.0.0, multiple IdP's
    • post: injecting of path of client certificate
    • adesso: request from client to simplify the authentication / token handling
  • Discussion
    • mobile access gateway communication is currently stateless, token's are not stored at the moment
    • post does not use the authentication/authorization out of the box

Protocol 5.2.2024, 09.00

  • Introduction Participants: Leonardo, Florian, Alexander, Stefano, Dmytro, Oliver
  • Open PR / Issues
    • Add documentation that the container is published #132
  • Release Plan
  • Topics Post:
    • How do we handle PRs in a beneficial and timely manner (Gentle reminder that we still have an open PR from December. Is there something we need to do to make that PR ready to merge?)
      • we try to handle them in a timely manner
    • How do we handle small and medium features? To a large extent, this relies a lot on the PR process so that we can contribute quickly.
      • work in branches, a pull-request will be rebased on master, we configure this in github, for future pr's unit tests are required for the back-end
    • We need to agree on a minimal versioning approach
      • move to a semantic versioning (mayor, minor, patch) approach
    • We think github PR comments, issues, and discussions should be enough for managing communication on given topics.
    • We need to discuss maybe in more details our expectations and commitment on things like testing, documentation, and logging.
      • remove console.log entries, only sensitive data in debug level
    • We have been identifying and analyzing features we need to implement. We will share this. We hope to have a slide deck to share by end of day on Tuesday.
    • We have some suggestions big and small on some improvements we think should be considered.
    • We also have some potentially radical ideas to discuss if tight collaboration is not as easy as we thought.
  • AOB

Discussion:

  • Separate gui / backend in two separate projects, that the backend could be run without the frontened
  • Injecting of path of client certificate, password through client certificates (work from Post).
Clone this wiki locally