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: ARCHITECTURE.md
+27-32Lines changed: 27 additions & 32 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,42 +29,12 @@ Rather than for speed, they need optimization for success.
29
29
Secondly, by short _cycle times_ which is the amount of time it takes for a commit to be shipped to a production environment.
30
30
Along this journey, we encounter our scope (more on it below):
31
31
32
-
- aspects of the _contribution_ environment;
32
+
- aspects of the _development_ environment;
33
33
- the packaging pipeline that produces artifacts;
34
34
- and continuous processes integrating the application lifecycle.
35
35
36
36
The goal of Standard is to optimize the critical path along this journey to achieve superior _cycle times_ through the powers of Nix and Flakes over frameworks in failure mode of disregard for the intrinsic value of _reproducability_.
37
37
38
-
## Scope
39
-
40
-
The automatable sections of the SDLC end-to-end process can be subdivided (not broken up!) in roughly three process regions with different overall shapes and characteristics.
41
-
42
-
The stipulated process regions are:
43
-
44
-
-**Contribution Environment** which roughly covers _code-to-commit_.
45
-
-**Packaging Pipeline** which roughly covers _commit-to-distribution_. It is typically set up once and then orchestrated by a CI control loop.
46
-
-**Continuous 'X' within the Application Lifecycle Management** which roughly covers _distribution-to-next-rollout_.
47
-
48
-
> Glossary:
49
-
>
50
-
> We use the term _Contribution Environment_ to mean _Development Environment Plus_.
51
-
> Compared to _Development Environment_, it explicitly encapsulates aspects of contribution and integration of the broader process flow.
52
-
> If you prefer, you can think of _Development Environment_ for practical purposes.
53
-
54
-
While Standard is fundamentally concerned with optimizing across the end-to-end process, we also limit the scope inside this project repository for practical reasons:
55
-
56
-
Therefore, we seek to delegate the **Contribution Environment** to a trusted project with an appropriate scope in the broader Nix Community, while employing community outreach to try to ensure our optimization targets are met or at least not accidentally sabotaged.
57
-
58
-
On the other hand, we seek to delegate **Continuous 'X'** by dovetailing and cultivating outreach with more appropriate initiatives of adjacent ecosystems.
59
-
60
-
## Ideals
61
-
62
-
The project is rooted deeply inside the Nix Ecosystem, but it strives to become a portal to make the powers of a store based reproducible packaging system readily available and palatable to colleagues and friends.
63
-
64
-
-_Use nix only where it is best suited_— a Nix maximalist approach may be an innate condition to some of us, but trying to be a portal we deeply recognize and value other perspectives and don't dismiss them as ignorance.
65
-
-_Disrupt where disruption is necessary_— to our chagrin, the Nix ecosystem is quite a monotheistic silo. Therefore, we don't shy away from deviating from its widely accepted norms and standards when we feel that it furthers our goals.
66
-
-_Look left, right, above and beyond_— our end-to-end perspective commands us to actively seek and reach out to other projects and ecosystems to compose the best possible value chain.
67
-
68
38
## Goals
69
39
70
40
-_Complete_: Standard should make a complete offer for setting up and running the automatable sections of the SDLC.
@@ -80,7 +50,7 @@ We'll make use of a simple value matrix with simple sentiment scores:
80
50
-:smile:→ <i>"feels pretty good."</i>
81
51
-:neutral_face:→ <i>"whatever?!?"</i>
82
52
83
-
The X-Axis represents the three prototypical stakeholder roles, while the Y-Axis represents the broad value creation categories that we have identified.
53
+
The X-axis represents the three prototypical stakeholder roles, while the Y-axis represents the broad value creation categories that we have identified.
84
54
85
55
|| Software Sponsor [Principal]| Provider of SDLC Automation [Agent]| Consumer of SDLC Automation [Agent]|
@@ -122,6 +92,31 @@ The main selling points of Standard are:
122
92
123
93
These points show how Standard can help adopters to improve their software delivery process, and how it can save them time, money and improve the quality of their software.
124
94
95
+
## Scope
96
+
97
+
The automatable sections of the SDLC end-to-end process can be subdivided (not broken up!) in roughly three process regions with different overall shapes and characteristics.
98
+
99
+
The stipulated process regions are:
100
+
101
+
-**Development Environment** which roughly covers _code-to-commit_.
102
+
-**Packaging Pipeline** which roughly covers _commit-to-distribution_. It is typically set up once and then orchestrated by a CI control loop.
103
+
-**Continuous Delivery and Beyond (Application Lifecycle Management)** which roughly covers _distribution-to-next-rollout_.
104
+
105
+
While Standard is fundamentally concerned with optimizing across the end-to-end process, we also limit the scope inside this project repository for practical reasons:
106
+
107
+
Therefore, we seek to delegate the **Development Environment** to a trusted project with an appropriate scope in the broader Nix Community, while employing community outreach to try to ensure our optimization targets are met or at least not accidentally sabotaged.
108
+
109
+
On the other hand, we seek to delegate **Continous Delivery and Beyond** by dovetailing and cultivating outreach with more appropriate initiatives of adjacent ecosystems.
110
+
111
+
## Ideals
112
+
113
+
The project aims to impove the SDLC by sensibly applying Nix' own superpowers and its ecoysystem's ingenuity to the problem.
114
+
But it strives to become a portal to make the powers of a store based reproducible packaging system readily available and palatable to colleagues and friends.
115
+
116
+
-_Use nix only where it is best suited_— a Nix maximalist approach may be an innate condition to some of us, but trying to be a portal we deeply recognize and value other perspectives and don't dismiss them as ignorance.
117
+
-_Disrupt where disruption is necessary_— to our chagrin, the Nix ecosystem is quite a monotheistic silo. Therefore, we don't shy away from deviating from its widely accepted norms and standards when we feel that it furthers our goals.
118
+
-_Look left, right, above and beyond_— our end-to-end perspective commands us to actively seek and reach out to other projects and ecosystems to compose the best possible value chain.
0 commit comments