Project Lifeguard blogpost

content/en/post/2019-project-lifeguard-open-for-ideas.md

@@ -1,8 +1,68 @@
 ---
 title: Project Lifeguard open for ideas
 date: 2019-09-16T14:39:57+02:00
-<!-- featured_image: /images/home-bg.svg -->
-description: About this post and stuff
+featured_image: /images/no-lifeguard-on-duty-antonia-felipe.jpg
+title_dimming_class: bg-gradient-dropshadow
+description: Giving drowning maintainers an escape.
+author: Robin van Boven ([@Beanow](https://github.com/beanow))
 ---
 
-Here's a page, with stuff and things.
+<sub>*Photo by [Antônia Felipe](https://unsplash.com/@a_mfelipe).*</sub>
+
+You may have
+[heard](https://nolanlawson.com/2017/03/05/what-it-feels-like-to-be-an-open-source-maintainer/),
+[this](https://www.youtube.com/watch?v=0t85TyH-h04),
+[before](https://github.com/notify-rs/notify/issues/209).
+Many maintainers working on OSS people depend upon are under
+a lot of stress, responding to people's wants and needs, while doing
+their best not to set the world on fire with breaking changes or security
+vulnerabilities.
+
+![Your packages depend on mine. All of them.](/images/all-your-upstream.png)
+
+It's impressive how much great software is built this way,
+but in the same breath, people have been pushing on to the
+point where having **one or two episodes of burnout became normal**.
+
+But what options are there for maintainers?
+They may have realized it's causing them grief, but
+posting an abandonment notice and hoping for the best&hellip;?
+That seems like a last resort and something you could
+feel quite guilty about doing.
+
+## Project Lifeguard
+
+What I feel is missing here, is a responsible way to leave your
+maintainer position. **Giving _drowning maintainers_ an escape.**
+
+![Life buoy](/images/life-buoy-jametlene-reskp.jpg)
+<sub>*Photo by [Jametlene Reskp](https://unsplash.com/@reskp).*</sub>
+
+The working idea I have now, is to be a group you can hand off
+maintenance to which will offer:
+
+1. Emergency bug and security fixes, by developers we find and pay?
+1. A standard message asking for new maintainers and sponsors.
+1. A long-term plan, to deprecate and archive if needed.
+
+For sponsorships, in particular I think it would be good to look for businesses
+that are using the software and derive value from it.
+
+The standard message, could be used to _make risk a lot clearer_
+for people using the software. Similar to an `npm audit`.
+Or the sustainability information [proposed here](https://writing.kemitchell.com/2019/04/12/package-json-sustainability.html).
+I'm imagining an output such as:
+
+```
+$ npm install
+...
+4 packages have been abandoned.
+12 packages are receiving emergency maintenance.
+Learn what you can do: https://lifeguard.teamopen.dev
+Show the package list with: npx lifeguard
+```
+
+### Just an idea
+
+For now this is an idea. If you're interested in helping,
+[get in touch](/community) and share your thoughts.

layouts/partials/page-header.html

@@ -5,7 +5,7 @@
   <header class="cover bg-top" style="background-image: url('{{ $featured_image }}');">
     <div class="pb1-m pb3-l {{ .Site.Params.cover_dimming_class | default "bg-black-60" }}">
       {{ partial "site-navigation.html" . }}
-      <div class="tc-l pv5 ph2 ph2-ns">
+      <div class="tc-l pv5 ph2 ph2-ns {{ .Params.title_dimming_class }}">
         {{ if not .Params.omit_header_text }}
           <h1 class="f2 f1-l fw2 white-90 mb0 lh-title">{{ .Title | default .Site.Title }}</h1>
           {{ with .Params.description  }}

layouts/post/single.html

@@ -0,0 +1,58 @@
+{{ define "header" }}
+   {{/* We can override any block in the baseof file be defining it in the template */}}
+  {{ partial "page-header.html" . }}
+{{ end }}
+
+{{ define "main" }}
+  {{ $section := .Site.GetPage "section" .Section }}
+  <article class="flex-l flex-wrap justify-between mw8 center ph3">
+
+    <header class="mt4 w-100">
+      <p class="f6 b helvetica tracked">
+          {{/*
+          CurrentSection allows us to use the section title instead of inferring from the folder.
+          https://gohugo.io/variables/page/#section-variables-and-methods
+          */}}
+        {{with .CurrentSection.Title }}{{. | upper }}{{end}}
+      </p>
+      <h1 class="f1 athelas mb1">
+        {{- .Title -}}
+      </h1>
+      <p class="tracked">
+        {{ with .Params.author }}By <b>{{ . | markdownify }}</b>{{ end}}
+      </p>
+      {{/* Hugo uses Go's date formatting is set by example. Here are two formats */}}
+      <time class="f6 mv4 dib tracked" datetime="{{ .Date.Format "2006-01-02T15:04:05Z07:00" }}">
+        {{- .Date.Format "January 2, 2006" -}}
+      </time>
+      {{/*
+          Show "reading time" and "word count" but only if one of the following are true:
+          1) A global config `params` value is set `show_reading_time = true`
+          2) A section front matter value is set `show_reading_time = true`
+          3) A page front matter value is set `show_reading_time = true`
+        */}}
+      {{ if (or (eq (.Param "show_reading_time") true) (eq $section.Params.show_reading_time true) )}}
+        <span class="f6 mv4 dib tracked"> - {{ .ReadingTime}} minutes read</span>
+        <span class="f6 mv4 dib tracked"> - {{ .WordCount}} words</span>
+      {{ end }}
+    </header>
+
+    <section class="nested-copy-line-height lh-copy serif f4 nested-links nested-img mid-gray pr4-l w-two-thirds-l">
+      {{- .Content -}}
+      {{- partial "tags.html" . -}}
+      <div class="mt6">
+      {{ if .Site.DisqusShortname }}
+        {{ template "_internal/disqus.html" . }}
+      {{ end }}
+      {{ if .Site.Params.commentoEnable }}
+        {{- partial "commento.html" . -}}
+      {{ end }}
+      </div>
+    </section>
+
+    <aside class="w-30-l mt6-l">
+      {{- partial "menu-contextual.html" . -}}
+    </aside>
+
+  </article>
+{{ end }}

static/css/custom.css

@@ -1,3 +1,7 @@
 .bg-teamopen {
 	background-color:#709781;
 }
+.bg-gradient-dropshadow {
+    background: linear-gradient(0deg, rgba(0,0,0,0) 0%, rgba(0,0,0,0.75) 22%, rgba(0,0,0,0.75) 75%, rgba(0,0,0,0) 100%);
+    text-shadow: 2px 1px 1px black;
+}