🗣 Production plan proposal and discussion for os2samtale

[janhalen]

Production plan:

This issue relates to the deployment of the complete stack with os2ID(Authentik) and os2samtale(Zulip)

Proposal for items that needs to be discussed and agreed upon:

• Setting up a SLA for the pre-release version ➡️ 📃 Create a Service Level agreement for the 0.9 Release #10

• Organizational and Repository Structure

  • Overview of repository organization
  • Environment-specific repositories

• Technical Documentation and Architecture

  • Onboarding guides for using the deployment templates
  • Architectural diagrams to help understand the stack

• Access Control and Branch Protections

  • Maintainable role-based access control (RBAC) in the repos
  • Branch protection rules
  • Code ownership and review processes

• Secrets Management

  • Strategies for storing and accessing secrets
  • Integration with secrets management tools

• Upgrading / Image Handling and Security

  • External image scanning and vulnerability assessment using CI in the repos
  • Accepting and maintaining image sources/fixed versions in the charts

[janhalen]

@mikkeschiren: I have drafted some initial points here for getting the stack into production (on the technical side)

[janhalen]

Furthermore I think we need to have a dialogue about where Digitalist draws it line for operations services.

My guess is that we need someone outside Digitalist to take responsibility for the day to day managment, support and educations... To illustrate it, here is my recommendations for at minimals set of roles to be filled.

Roles

Organization Owner:

This role has the highest level of permissions, including managing users, public channels, organization settings, and billing. They can do anything an administrator can do and more

Organization Administrator:

Administrators can manage users, public channels, and organization settings. They cannot make someone an owner or change an existing owner's role

Moderators

Moderators have additional permissions configured by your organization, such as managing messages and channels

Support Staff:

Provides user support and handles any issues that arise. This role is crucial for maintaining user satisfaction and addressing technical problems promptly.

[janhalen]

Zulip has some internal documentation for a subset of what permissions these roles have inside Zulip: https://docs.zulip.com/help/user-roles

[janhalen]

If introduced and onboarded in the right way, some of the roles could be filled by some of the interrested users maybe?

Contact information for 0.9 test groups in OS2forms and OS2borgerPC #8

[janhalen]

No progress made yet on deciding how administrative personel is allocated.

In short the staff that is dedicated to creating new users, setting and distributing passwords, communication with users regarding the onboarding process, reacting to support questions, distributing tasks to our supplier, updating documentation and other plain administrative tasks.

A proposal for this has been drafted by @ChatBotBerg.