Refactor community pages (#139)

* refactor community pages

Signed-off-by: Max Wolfs <mail@maxwolfs.com>

* fix link

Signed-off-by: Max Wolfs <mail@maxwolfs.com>

* rename dev docs to contributor docs

Signed-off-by: Max Wolfs <mail@maxwolfs.com>

* add calendar redirect

Signed-off-by: Max Wolfs <mail@maxwolfs.com>

* rm redirect

Signed-off-by: Max Wolfs <mail@maxwolfs.com>

* add links

Signed-off-by: Max Wolfs <mail@maxwolfs.com>

---------

Signed-off-by: Max Wolfs <mail@maxwolfs.com>

community/collaboration/index.mdx

@@ -0,0 +1,42 @@
+import CommunityCalendar from '../../src/components/CommunityCalendar'
+
+# Collaboration
+
+## We’re an open community
+
+Our meetings are publicly announced and we are happy to welcome both newcomers and established members alike. You can navigate either through the calendar below or subscribe with your favorite client to https://sovereigncloudstack.github.io/calendar/scs.ics. The calendar is collaboratively maintained on GitHub and new entries, such as a lightning talk, are highly appreciated!
+
+<CommunityCalendar />
+
+## Collaborating with issues and pull requests
+
+We use the GitHub flow to track and discuss changes in issues, then propose and
+review changes in pull requests. See the
+[GitHub documentation](https://docs.github.com/en/free-pro-team@latest/github/collaborating-with-issues-and-pull-requests)
+for more details.
+
+## Meetings
+
+### Project updates
+
+- Weekly with all teams on Thursday at 15:05 CEST (40 mins)
+- In some weeks we schedule an additional lightning talk at 15:40 CEST
+
+### Sprint review/Backlog refinement/Sprint planning meetings
+
+- Weekly Team meetings (~1hr) for currently 4 teams:
+  - Team IaaS
+  - Team Container
+  - Team IAM & Security
+  - Team Operations
+- Please refer to the public calendar above for details.
+
+### Special interest groups (SIGs) and hacking sessions
+
+- There are a number of SIG meetings and hacking sessions that meet weekly or bi-weekly
+  - SIG Monitoring and Logging
+  - SIG Standardization and Certification
+  - SIG Documentation
+  - SIG Community
+  - SIG Central API
+- Please refer to the public calendar above for details.

community/collaboration/sig-central-api.md

@@ -0,0 +1,10 @@
+# SIG Central API
+
+For defining a Common and Central interface for the Customers of SCS cloud to manage the Infrastructure cloud resources open stack and Kubernetes and identity and Access management.
+
+We want to define a single point of managment with consistent experience for managing the entire infrastructure.
+
+We aim to establish an unified and central interface that provides customers
+of the SCS clouds with the ability to manage cloud resources and/or services.
+
+SIG explores the possibilities for a central API by creating a MVP.

community/collaboration/sig-community.md

@@ -0,0 +1,3 @@
+# SIG Community
+
+In this meeting, we come together to shape our community strategy and coordinate collaborative efforts within our community. Our goal is to cultivate an open and welcoming community where we can share the message of SCS. We plan engaging community events, strive to make this open-source community even more inclusive, and aim to keep it informative, inspiring, and captivating. We warmly invite you to join us in our mission and become a part of this exciting journey!

community/collaboration/sig-documentation.md

@@ -0,0 +1,7 @@
+---
+title: SIG Documentation
+operator: Max Wolfs
+time: bi-weekly mondays 11-12 CET
+---
+
+We curate and enhance the SCS Documentation, focusing on refining its information architecture for optimal usability. Our objective is to facilitate straightforward contributions from community developers and to provide operators with a clear, quick reference guide that accelerates the initiation of an SCS deployment.

community/collaboration/sig-monitoring.md

@@ -0,0 +1,3 @@
+# SIG Monitoring
+
+The Special Interest Group (SIG) Monitoring meets on a fortnightly base (alternating with the audit log WG) to discuss the monitoring needs of SCS Operators, Users and Integrators. Together we shape how monitoring and observability within the SCS landscape looks like.

community/collaboration/sig-standardization.md

@@ -0,0 +1,5 @@
+# SIG Standardization
+
+In this Special Interest Group, we discuss and align our activities and approach to standardization and certification. That is to say, we devise and refine the relevant concepts and processes; we work on a roadmap for new certificate versions; and we align on which standards are desireable for each certificate subject. We then work with the teams to align on existing or new standards.
+
+Besides aspects of openness and sovereignty, the main goal of our standards is interoperability. We should take the user perspective: As a member of a DevOps team developing a service (think SaaS or PaaS) for SCS, I need XYZ. Every standard should be abstract enough to work regardless of the SCS reference implementation.

community/collaboration/team-container.md

@@ -0,0 +1,7 @@
+# Team Container
+
+The Team Container deals with all topics around Containers and Kubernetes.
+
+at the moment: Kubernetes Deployments via ClusterAPI
+in the future deployments via ClusterStacks
+KaaS Standard

community/collaboration/team-iaas.md

@@ -0,0 +1,3 @@
+# Team Iaas
+
+We build the reference implementation of the IaaS parts of SCS that informs and adheres to the SCS IaaS standards.

community/collaboration/team-iam.md

@@ -0,0 +1,7 @@
+# Team IAM
+
+The Team IAM deals with topics around Identity and Access Management.
+
+Users that access cloud and container infrastructure need to authenticate themselves and then authorizations to see and access resources from the infrastructure are derived from the identity of the users as they belong to groups and are roles are assigned to them (or the groups they belong to).
+
+Sovereign Cloud Stack has the goal that user identities can used across several layers in the stack (most importantly IaaS and Container layer), that user management should be a self-service capability and that user identities can be federated, i.e. user identities and authentication from one SCS cloud (or from one standards-compliant Identity Provider) can be used in other SCS clouds. Federation is an imporant principle in SCS.

community/collaboration/team-ops.md

@@ -0,0 +1,3 @@
+# Team Ops
+
+We build tooling and infrastructure design for easy, efficient and transparent ways to operate an SCS Cloud.

community/index.md

@@ -5,14 +5,8 @@ title: Overview
 
 ## Welcome to our SCS Community
 
-## Contribute to Sovereign Cloud Stack
-
 Sovereign Cloud Stack is an open community of providers and end-users joining forces in defining, implementing and operating a fully open, federated, compatible platform. We actively encourage you to contribute either code, documentation or issues and to participate in the various discussions happening on GitHub or during our various meetings.
 
-## We're chatty
-
-We have created an open community space on the Matrix network. Feel free to join the several channels and start interacting with the community. A good starting point is entering the General & Announcements and the Tech channel.
-
-## We're on GitHub
+We have created an open community space on the [Matrix network](https://matrix.to/#/#scs-community:matrix.org). Feel free to join the several channels and start interacting with the community. A good starting point is entering the [General & Announcements](https://matrix.to/#/#scs-general:matrix.org) and the [Tech channel](https://matrix.to/#/#scs-tech:matrix.org).
 
-We're actively developing, discussing and planning on GitHub. The three technical teams are using a joint project board to plan and monitor the progress during our sprints.
+Check out our [Community Calendar](/community/collaboration) to know when our several Teams and SIGs meet.