Loading policy/tpa-rfc-1-policy.md +8 −8 Original line number Diff line number Diff line Loading @@ -2,7 +2,7 @@ title: TPA-RFC-1: RFC process --- Summary: policy decisions should be made in an online concensus Summary: policy decisions should be made in an online consensus building process with a 2 days to 2 weeks delay, and formally documented in this wiki. Loading @@ -24,7 +24,7 @@ it's unclear how that process works or if it works at all. This is therefore a formalization of this process. We do understand that people can make mistakes and might improvise sometimes, especially if process is not currently doumented. sometimes, especially if process is not currently documented. # Proposal Loading Loading @@ -80,7 +80,7 @@ by the proposer based on the urgency of the changes proposed. Objections must be formulated constructively and justified with reasonable technical or social explanations. The goal of this step is to communicate potential negative impacts and evaluate if they outweight the possible benefits of the proposal. outweigh the possible benefits of the proposal. If the negative impacts outweigh the benefits, a constructive objection must also propose changes can be made to the proposal to Loading @@ -106,7 +106,7 @@ Once the discussion period has passed and no objection is raised, the If objections are raised and no solution is found, the proposal is `rejected`. Some policies can be completely overriden using the current policy Some policies can be completely overridden using the current policy process, including this policy, in which case the old policy because `obsolete`. Old, one-time decisions can also be marked as `obsolete` when it's clear they do not need to be listed in the main policy Loading @@ -128,8 +128,8 @@ soon as the older `TPA-RFC-N` is modified. Examples of ideas relevant for the RFC process: * replacing Munin with grafana and prometheus [#29681][] * setting defaut locale to C.UTF-8 [#33042][] * replacing Munin with Grafana and prometheus [#29681][] * setting default locale to C.UTF-8 [#33042][] * using Ganeti as a clustering solution * using setup-storage as a disk formatting system * setting up a loghost Loading @@ -143,8 +143,8 @@ Counter examples: * setting up a new Ganeti node (part of the roadmap) * performing security updates (routine) * picking a different hardware configuration for the new ganeti node (process wasn't documented explicitely, we accept honest mistakes) * picking a different hardware configuration for the new Ganeti node (process wasn't documented explicitly, we accept honest mistakes) Examples of obsolete proposals: Loading Loading
policy/tpa-rfc-1-policy.md +8 −8 Original line number Diff line number Diff line Loading @@ -2,7 +2,7 @@ title: TPA-RFC-1: RFC process --- Summary: policy decisions should be made in an online concensus Summary: policy decisions should be made in an online consensus building process with a 2 days to 2 weeks delay, and formally documented in this wiki. Loading @@ -24,7 +24,7 @@ it's unclear how that process works or if it works at all. This is therefore a formalization of this process. We do understand that people can make mistakes and might improvise sometimes, especially if process is not currently doumented. sometimes, especially if process is not currently documented. # Proposal Loading Loading @@ -80,7 +80,7 @@ by the proposer based on the urgency of the changes proposed. Objections must be formulated constructively and justified with reasonable technical or social explanations. The goal of this step is to communicate potential negative impacts and evaluate if they outweight the possible benefits of the proposal. outweigh the possible benefits of the proposal. If the negative impacts outweigh the benefits, a constructive objection must also propose changes can be made to the proposal to Loading @@ -106,7 +106,7 @@ Once the discussion period has passed and no objection is raised, the If objections are raised and no solution is found, the proposal is `rejected`. Some policies can be completely overriden using the current policy Some policies can be completely overridden using the current policy process, including this policy, in which case the old policy because `obsolete`. Old, one-time decisions can also be marked as `obsolete` when it's clear they do not need to be listed in the main policy Loading @@ -128,8 +128,8 @@ soon as the older `TPA-RFC-N` is modified. Examples of ideas relevant for the RFC process: * replacing Munin with grafana and prometheus [#29681][] * setting defaut locale to C.UTF-8 [#33042][] * replacing Munin with Grafana and prometheus [#29681][] * setting default locale to C.UTF-8 [#33042][] * using Ganeti as a clustering solution * using setup-storage as a disk formatting system * setting up a loghost Loading @@ -143,8 +143,8 @@ Counter examples: * setting up a new Ganeti node (part of the roadmap) * performing security updates (routine) * picking a different hardware configuration for the new ganeti node (process wasn't documented explicitely, we accept honest mistakes) * picking a different hardware configuration for the new Ganeti node (process wasn't documented explicitly, we accept honest mistakes) Examples of obsolete proposals: Loading
