-
Notifications
You must be signed in to change notification settings - Fork 26
Feat/add scs 0007 #946
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
fkr
wants to merge
12
commits into
main
Choose a base branch
from
feat/add-scs-0007
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Feat/add scs 0007 #946
Changes from all commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
459e01a
a very very rough draft
fkr 5b52e8d
lint
fkr 8a4b133
reword
fkr 35e2f7e
who attestates
fkr 310e575
start rewording. define what is meant with "SCS-compliant"
fkr b20d87c
address some of the concerns raised by @mbuechse - together with @mbu…
fkr ee4a7b0
follow the naming scheme for the other certifications
fkr 05ea60b
wording - especially making clear that abstentions are not counted as…
fkr 520ac04
linting
fkr df72064
lint^2
fkr bd95e53
Update Standards/scs-0007-v1-certification-integrators.md
fkr 7fd8cf5
eligible, not eligble
fkr File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,53 @@ | ||
--- | ||
title: Certification of integrators | ||
type: Procedural | ||
status: Draft | ||
track: Global | ||
description: | | ||
SCS-0007 defines the process and rules on how SCS certified integrators are certified. | ||
--- | ||
|
||
## Introduction | ||
|
||
The purpose of this document is to describe a concept for how implementation partners can obtain SCS certification. 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, 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. | ||
|
||
## Motivation | ||
|
||
## Regulations | ||
|
||
The certificates are awarded for the period for one year. | ||
The certification is done either by the Forum SCS-Standards or a attestation body nominated by the Forum SCS-Standards. | ||
|
||
### Certificates | ||
|
||
* Certified SCS KaaS Integrator: SCS KaaS (Kubernetes as a Service) implementation partner | ||
* Certified SCS IaaS Integrator: SCS IaaS (Infrastructure as a Service) implementation partner | ||
|
||
Criteria for certification, proof of experience in setting up, operating and supporting SCS-compliant environments. | ||
|
||
The organization 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 fullfill at least the _Certified SCS-compatible IaaS_ or _Certified SCS-compatible KaaS_ scope. | ||
|
||
or | ||
|
||
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. | ||
|
||
or | ||
|
||
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. | ||
|
||
### Additional favorable criteria for certification | ||
|
||
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): | ||
|
||
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. | ||
|
||
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. | ||
|
||
### 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 organization to be certified as to whether and to what extent the criteria have been met. | ||
|
||
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. |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Being a very vocal supporter of the cause should not compensate for a lack of measurable experience IMHO.