2020-07-08-june-status-update.html (7996B)
1 <!DOCTYPE html> 2 <html lang="en"> 3 <head> 4 <!-- Sep 03, 2024 --> 5 <meta charset="utf-8" /> 6 <meta name="viewport" content="width=device-width, initial-scale=1" /> 7 <title>Status update, June 2020</title> 8 <meta name="author" content="Vincent Demeester" /> 9 <meta name="generator" content="Org Mode" /> 10 <link rel='icon' type='image/x-icon' href='/images/favicon.ico'/> 11 <meta name='viewport' content='width=device-width, initial-scale=1'> 12 <link rel='stylesheet' href='/css/new.css' type='text/css'/> 13 <link rel='stylesheet' href='/css/syntax.css' type='text/css'/> 14 <link href='/index.xml' rel='alternate' type='application/rss+xml' title='Vincent Demeester' /> 15 </head> 16 <body> 17 <main id="content" class="content"> 18 <header> 19 <h1 class="title">Status update, June 2020</h1> 20 </header><section id="outline-container-Introduction" class="outline-2"> 21 <h2 id="Introduction">Introduction</h2> 22 <div class="outline-text-2" id="text-Introduction"> 23 <p> 24 Time for the first new monthly status update! I do like those updates from <a href="https://drewdevault.com/2020/06/15/Status-update.html">Drew DeVault</a> 25 and <a href="https://emersion.fr/blog/2020/status-update-19/">Simon Ser</a>, so I figured, why not trying myself 🙃. I am not sure where to start and 26 where to end, but I guess I’ll figure things out as I go. 27 </p> 28 </div> 29 </section> 30 <section id="outline-container-Tekton%20%26%20OpenShift%20Pipelines" class="outline-2"> 31 <h2 id="Tekton%20%26%20OpenShift%20Pipelines">Tekton & OpenShift Pipelines</h2> 32 <div class="outline-text-2" id="text-Tekton%20%26%20OpenShift%20Pipelines"> 33 <p> 34 As you know, <i>or may not</i>, I am working on the <a href="https://github.com/tektoncd/">TektonCD</a> project and also on our <a href="https://redhat.com">RedHat</a> 35 product <a href="https://www.openshift.com/learn/topics/pipelines">OpenShift Pipelines</a>. As far as the month of June went : 36 </p> 37 38 <ul class="org-ul"> 39 <li>We release <a href="https://github.com/tektoncd/pipeline/releases/tag/v0.13.0">v0.13.0</a> “Bobtail Bishop” and a bunch of fixes (<a href="https://github.com/tektoncd/pipeline/releases/tag/v0.13.2">v0.13.2</a>) 40 <ul class="org-ul"> 41 <li>It’s the second release after the <code>v1beta1</code> bump, and we start to stabilise things.</li> 42 <li><a href="https://github.com/tektoncd/pipeline/releases/tag/v0.14.0">v0.14.0</a> will (and actually is already) a more feature-packed release because there is 43 now the <code>finally</code> field support and cloud-events opt-in.</li> 44 </ul></li> 45 <li><p> 46 But the <b>most important</b> contributions I tried to make during that month is the TEP 47 process. <b>TEP</b> stands for <b>Tekton Enhancement proposals</b>. 48 </p> 49 50 <div class="org-src-container"> 51 <pre class="src src-markdown"># Tekton Enhancement Proposals (TEPs) 52 53 A Tekton Enhancement Proposal (TEP) is a way to propose, communicate 54 and coordinate on new efforts for the Tekton project. You can read 55 the full details of the project in 56 [TEP-1](https://github.com/tektoncd/community/blob/master/teps/0001-tekton-enhancement-proposal-process.md). 57 58 ## What is a TEP 59 60 A standardized development process for Tekton is proposed in order to 61 62 - provide a common structure and clear checkpoints for proposing 63 changes to Tekton 64 - ensure that the motivation for a change is clear 65 - allow for the enumeration stability milestones and stability 66 graduation criteria 67 - persist project information in a Version Control System (VCS) for 68 future Tekton users and contributors 69 - support the creation of _high value user facing_ information such 70 as: 71 - an overall project development roadmap 72 - motivation for impactful user facing changes 73 - ensure community participants are successfully able to drive changes 74 to completion across one or more releases while stakeholders are 75 adequately represented throughout the process 76 77 This process is supported by a unit of work called a Tekton 78 Enhancement Proposal (TEP). A TEP attempts to combine aspects of the 79 following: 80 81 - feature, and effort tracking document 82 - a product requirements document 83 - design document 84 85 into one file which is created incrementally in collaboration with one 86 or more [Working 87 Groups](https://github.com/tektoncd/community/blob/master/working-groups.md) 88 (WGs). 89 90 This process does not block authors from doing early design docs using 91 any means. It does not block authors from sharing those design docs 92 with the community (during Working groups, on Slack, GitHub, …. 93 94 **This process acts as a requirement when a design docs is ready to be 95 implemented or integrated in the `tektoncd` projects**. In other words, 96 a change that impact other `tektoncd` projects or users cannot be 97 merged if there is no `TEP` associated with it. 98 99 This TEP process is related to 100 - the generation of an architectural roadmap 101 - the fact that the what constitutes a feature is still undefined 102 - issue management 103 - the difference between an accepted design and a proposal 104 - the organization of design proposals 105 106 This proposal attempts to place these concerns within a general 107 framework. 108 109 110 See [TEP-1](https://github.com/tektoncd/community/blob/master/teps/0001-tekton-enhancement-proposal-process.md) for more details. 111 </pre> 112 </div></li> 113 </ul> 114 </div> 115 </section> 116 <section id="outline-container-%3Dhome%3D%2C%20Nixos%20and%20the%20rest%20of%20thing" class="outline-2"> 117 <h2 id="%3Dhome%3D%2C%20Nixos%20and%20the%20rest%20of%20thing"><code>home</code>, Nixos and the rest of thing</h2> 118 <div class="outline-text-2" id="text-%3Dhome%3D%2C%20Nixos%20and%20the%20rest%20of%20thing"> 119 <p> 120 I did some big changes in my <a href="https://git.sr.ht/~vdemeester/home"><code>home</code></a> repository, it’s still much a work-in-progress but it 121 is in a way better state than before. 122 </p> 123 124 <ul class="org-ul"> 125 <li>It is more reproductible. All dependencies are managed by <a href="https://github.com/nmattia/niv">niv</a> and all machines are using 126 a pinned version of channels from there. That way I can test the configuration (on the 127 CI) and cache the packages for all channels that my machines uses. I also can decide 128 when I want to upgrade a particular channel (nixos, unstable, …).</li> 129 <li>I am slowly experimenting on simplifying things more and more. This is a bit related to 130 the <a href="2020-02-22-digital-minimalism.html">previous post</a>. I am trying to use Gnome3 everywhere. Well configured, managed by 131 NixOS, it’s enough for my test and reduce the configuration cruft I need to do.</li> 132 </ul> 133 134 <p> 135 An ongoing work is my knowledge base and how it is published as part of this website : 136 <a href="https://vincent.demeester.fr/articles/">articles</a>. I am trying to make all those publishable (for the one that do not hold any 137 secret). I’ll document this a bit more at some point but… 138 </p> 139 <ul class="org-ul"> 140 <li>Configurations are now part of that knowledge base, the <code>docs</code> folder of <a href="https://git.sr.ht/~vdemeester/home"><code>home</code></a> is going 141 away.</li> 142 <li>I am trying to use litterate configuration as much as possible. So slowly, the content 143 from <a href="https://git.sr.ht/~vdemeester/home"><code>home</code></a> will be a tangled version of my knowledge base. At least that is the goal as 144 of today.</li> 145 </ul> 146 147 <p> 148 And I feel that’s all <i>for June</i>. 149 </p> 150 </div> 151 </section> 152 </main> 153 <footer id="postamble" class="status"> 154 <footer> 155 <small><a href="/" rel="history">Index</a> • <a href="/sitemap.html">Sitemap</a> • <a href="https://dl.sbr.pm/">Files</a></small><br/> 156 <small class='questions'>Questions, comments ? Please use my <a href="https://lists.sr.ht/~vdemeester/public-inbox">public inbox</a> by sending a plain-text email to <a href="mailto:~vdemeester/public-inbox@lists.sr.ht">~vdemeester/public-inbox@lists.sr.ht</a>.</small><br/> 157 <small class='copyright'> 158 Content and design by Vincent Demeester 159 (<a rel='licence' href='http://creativecommons.org/licenses/by-nc-sa/3.0/'>Some rights reserved</a>) 160 </small><br /> 161 </footer> 162 </footer> 163 </body> 164 </html>