You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Standards/scs-0005-v1-project-governance.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -94,7 +94,7 @@ Every person who is a member of the GitHub organization "Sovereign Cloud Stack"
94
94
### Electoral management
95
95
96
96
The voting process is governed by the _Forum SCS-Standards_.
97
-
Voting is done using the [Condorcet Internet Voting Service](https://civs.cs.cornell.edu). This is the same system as is [being used by the OpenInfra foundation](https://wiki.openstack.org/wiki/Election_Officiating_Guidelines#Running_the_election_itself).
97
+
Voting is done using the [Condorcet Internet Voting Service](https://civs1.civs.us/). This is the same system as is [being used by the OpenInfra foundation](https://wiki.openstack.org/wiki/Election_Officiating_Guidelines#Running_the_election_itself).
SCS-0007 defines the process and rules on how SCS integrators are certified.
8
+
---
9
+
10
+
## Introduction
11
+
12
+
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.
13
+
For this purpose, two 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 certification.
14
+
15
+
## Motivation
16
+
17
+
## Regulations
18
+
19
+
The certificates are awarded for the period of one year.
20
+
The certification is done either by the Forum SCS-Standards or an attestation body nominated by the forum.
21
+
22
+
### Certificates
23
+
24
+
- Certified SCS KaaS Integrator: SCS KaaS (Kubernetes as a Service) implementation partner
25
+
- Certified SCS IaaS Integrator: SCS IaaS (Infrastructure as a Service) implementation partner
26
+
27
+
### Criteria
28
+
29
+
Criteria for certification, proof of experience in setting up, operating and supporting SCS-compliant environments:
30
+
31
+
The organization to be certified needs to satisfy one of the following requirements
32
+
33
+
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.
34
+
35
+
or
36
+
37
+
b) actively manage 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.
38
+
39
+
or
40
+
41
+
c) have been operating a _Certified SCS-compatible IaaS_ public cloud with at least two regions or at least three availability zones for more than one year.
42
+
43
+
#### Additional favorable criteria for certification
44
+
45
+
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 for certification or compensate for any criteria that are not fully met (see above):
46
+
47
+
The implementation partners should work towards ensuring that digital sovereignty is implemented in accordance with the SCS definition (Standards, Open Software, OpenOperations). 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 organization have already been configured in accordance with the standards and are listed on the SCS compliance list.
48
+
49
+
The implementation partners should work towards ensuring that the cloud environments they set up and/or manage are also officially visible as SCS clouds, thereby strengthening the SCS brand.
50
+
51
+
### Attestation
52
+
53
+
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 organization to be certified as to whether and to what extent the criteria have been met.
54
+
55
+
If one of the above criteria is not met, the forum can be requested to certify the candidate 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.
0 commit comments