replace exception rule by Incubator status

Standards/scs-0007-v2-certification-integrators.md

@@ -0,0 +1,62 @@
+---
+title: Certification of integrators
+type: Procedural
+status: Draft
+#stabilized_at: YYYY-MM-DD # TODO when Stable
+replaces:
+  - scs-0007-v1-certification-integrators.md
+track: Global
+description: |
+  SCS-0007 defines the process and rules on how SCS integrators are certified.
+---
+
+## Introduction
+
+The purpose of this document is to describe a concept for how implementation partners can obtain certification as SCS integrators. In essence, this certificate is intended to express that an organization has sufficient technical knowledge and experience to provide technical support to companies using SCS.
+For this purpose, essential criteria are defined that must be fulfilled. In addition, there are a few other criteria that can be taken into account in favor of a certification with _Incubator_ status.
+
+## Motivation
+
+As an implementation partner, I want to obtain a certificate as _Certified SCS IaaS Integrator_ or _Certified SCS KaaS Integrator_ in order to prove sufficient technical knowledge and experience to provide technical support for SCS.
+
+## Regulations
+
+The certificates are awarded for the period of one year.
+The certification is done either by the Forum SCS-Standards or an attestation body nominated by the forum.
+
+### Certificates
+
+- Certified SCS IaaS Integrator: SCS IaaS (Infrastructure as a Service) implementation partner
+- Certified SCS KaaS Integrator: SCS KaaS (Kubernetes as a Service) implementation partner
+
+### Criteria
+
+Criteria for certification, proof of experience in setting up, operating and supporting SCS-compliant environments.
+
+The implementation partner to be certified needs to satisfy one of the following requirements:
+
+a) Have successfully brought at least two SCS-compliant environments of a third party (customer) into production in the last 12 months. The two environments must fulfill at least the [_Certified SCS-compatible IaaS_](https://docs.scs.community/standards/scs-compatible-iaas) or [_Certified SCS-compatible KaaS_](https://docs.scs.community/standards/scs-compatible-kaas) scope.
+
+or
+
+b) Actively manages at least two such environments of third parties (customers) at the time the certificate is issued. These environments must have been managed at least for a year at the time of attestation or the management must have started within the period as _Incubator_.
+
+or
+
+c) Have been operating a [_Certified SCS-compatible IaaS_](https://docs.scs.community/standards/global/scs-0004) public cloud with at least two regions or at least three availability zones for more than one year or put such a cloud into operation during the period as _Incubator_.
+
+#### Incubator status
+
+SCS is an open source community project with the goal of enabling digital sovereignty. As such, the commitment and support of this mission should be recognized and promoted beyond technical competence. To this end, the following aspects can be taken into account to compensate for any criteria that are not fully met yet (see above) and may qualify for a certification with _Incubator_ status.
+
+The implementation partner should work towards ensuring that digital sovereignty is implemented in accordance with the SCS definition (Standards and [Mission Statement](https://docs.scs.community/community/mission-statement)). This is expressed in a way that, in addition to the technology used to build environments (not necessarily only SCS environments), knowledge and experience in SCS standards compliance (SCS-compatible IaaS and KaaS) is also available and that environments built by this implementation partner have already been configured in accordance with the standards and are listed on the SCS compliance list.
+
+The goal of the _Incubator_ status is to meet the criteria for the SCS integrator certification after one year. For this reason, the status is granted only once for one year.
+
+The implementation partner should work towards ensuring that the cloud environments it sets up and/or manages are also officially visible as SCS clouds, thereby strengthening the SCS brand.
+
+### Attestation
+
+The audit for the certification of an implementation partner is carried out by a person appointed by the Forum SCS-Standards. The person will assess and, if necessary, obtain evidence from the implementation partner to be certified as to whether and to what extent the criteria have been met.
+
+If one of the above criteria is not yet met, the forum can be requested to certify the implementation partner with status _Incubator_ nevertheless. This must be decided by unanimous vote in the forum, two third of all eligible votes must be present. Abstentions are not counted as votes against.

Standards/scs-0007-w2-certification-integrators-implementation-notes.md

@@ -0,0 +1,36 @@
+---
+title: "Implementation hints for achieving Certified SCS Integrator"
+type: Supplement
+track: Global
+supplements:
+  - scs-0007-v2-certification-integrators.md
+replaces:
+  - scs-0007-w1-certification-integrators-implementation-notes.md
+---
+
+## Introduction
+
+The standard scs-0007 documents what requirements integration partners must fulfill to be eligible
+for being certified as SCS integrators.
+This document contains hints how these requirements may be evaluated by the Forum SCS-Standards
+auditor and how the process to get _Incubator_ status will be handled.
+
+### Voting on _Incubator_ status
+
+When someone requests approval for a certification as SCS integrator with _Incubator_ status (criteria are not met yet), this can be waived with a qualified vote in the Forum SCS-Standards.
+To avoid conflict of interests and counteract social pressure, we envision the following process:
+
+- The beneficiary party (the implementation partner in whose favor _Incubator_ status is requested)
+  should be invited to a meeting to explain why they believe that they qualify as incubator for a
+  SCS integrator certification despite not meeting the normal qualification criteria.
+- The forum members may ask the beneficiary party clarifying questions that should be answered.
+- To ensure an open discussion, the beneficiary party should be excluded from the discussions about
+  the matter.
+  The same applies if the beneficiary party is a member of the Forum SCS-Standards.
+  In that case, the expulsion should not be counted against the required quorum to avoid forum
+  members from having a disadvantage.
+  If the excluded party is a voting member, they will automatically abstain from the vote.
+- Any parties that have significant conflicts of interests are expected to make these
+  conflicts transparent and cast abstention votes.
+
+The goal during the period having _Incubator_ status is to work in accordance with the SCS Standards and Mission Statement towards the criteria for the SCS integrator certification.