##Risk Description

= Fedora Fails to Satisfy Requirements =

## Detailed description of this risk and its possible implications.
## E.g. If one of the car's tires suffers a puncture, we may run off the road.

e.g. Fedora doesn't scale.

Note that we have done extensive scaling testing and a pre-analysis project points to Fedora fulfilling requirements.

== When to react? ==

## When must we respond to the risk? E.g. When the event occurs or already when we see the warning signs?
## E.g. We must react if we hear a hissing sound.

When we start seeing inefficiencies or undesirable properties in either the scalability, stability or behaviour of Fedora

== Reaction ==

## Detailed description of how to react on the risk and which actions to take, if it is imminent.

## There exists 4 basic reactions:
## 1: Accept the risk.
## 2: Eliminate the cause to the risk.
## 3: Mitigate the probability or the consequence of the risk.
## 4: Delegate the risk to another party, e.g. by outsourcing it or take out insurance for it.

## E.g. We accept the risk and change the tire if we suffer a puncture.
First try to mitigate the problem by working with the Fedora development team about addressing the problems. 

If the problems are unsolvable, try mitigating the problem by working around the issue.

If the problem is still unsolvable, start investigating a replacement for Fedora, and re-estimate the DOMS project. Seek input from the steering committee.

== Responsible Persons ==

The below persons are responsible for continuously monitoring and acting on this risk:

## Add a bullet list with links to the wiki pages of the responsible persons here:
## E.g.
## * [:JohnDoe: John Doe]