Fixing for linter checks

Ainali · Ainali · commit 1ad015283a25 · 2022-02-08T16:30:57.000+01:00
Works towards #170, everything fixed except the MD033 Inline HTML.
diff --git a/README.md b/README.md
@@ -14,16 +14,19 @@ This site builds with [Jekyll](http://jekyllrb.com/), as is the default of [GitH
 
 1. To build the site locally make sure you have [Ruby](https://www.ruby-lang.org/en/) and [Bundlr](https://bundler.io/) installed.
 2. Install the dependencies of this repo with
+
 ```bash
 $ bundle install
 ```
 
 ## Serving Locally
 
 1. Run the Jekyll server with
+
 ```bash
 $ bundle exec jekyll serve
 ```
+
 2. You can now view the website locally on `http://localhost:4000`
 
 The server will rebuild the site every time a file changes, with the exception of `_config.yml`.
diff --git a/_posts/2019-12-13-notes-from-community-call-5-december-2019.md b/_posts/2019-12-13-notes-from-community-call-5-december-2019.md
@@ -11,6 +11,7 @@ categories:
 # Notes from the 5 December 2019 Community Call
 
 ## Attendees
+
 * [Ali Gonzalez Garcia](https://twitter.com/basicavisual)
 * [Boris](https://publiccode.net/team/boris-van-hoytema.html)
 * [Jan](https://publiccode.net/team/jan-ainali.html)
diff --git a/_posts/2020-02-07-video-decidimfest-ben-cerveny.md b/_posts/2020-02-07-video-decidimfest-ben-cerveny.md
@@ -12,5 +12,4 @@ categories:
 
 [![Ben Cerveny at DecdimFest 2019]({{site.url}}/assets/ben-cerveny-decidimfest-2019.png)](https://www.youtube.com/watch?v=cnJtnZ9Cx1o)
 
-
-[Ben Cerveny's](https://publiccode.net/team/ben-cerveny.html) [DecidimFest 2019](https://meta.decidim.org/conferences/decidimfest19) talk 'Collaborative Code is the Future of Cities' gives a good overview of why we believe [public code](https://about.publiccode.net/glossary/public-code-definition.html) will become basic infrastructure. It's available now on YouTube at <https://www.youtube.com/watch?v=cnJtnZ9Cx1o>. 
+[Ben Cerveny's](https://publiccode.net/team/ben-cerveny.html) [DecidimFest 2019](https://meta.decidim.org/conferences/decidimfest19) talk 'Collaborative Code is the Future of Cities' gives a good overview of why we believe [public code](https://about.publiccode.net/glossary/public-code-definition.html) will become basic infrastructure. It's available now on YouTube at <https://www.youtube.com/watch?v=cnJtnZ9Cx1o>.
diff --git a/_posts/2020-02-21-notes-from-community-call-20-february-2020.md b/_posts/2020-02-21-notes-from-community-call-20-february-2020.md
@@ -12,10 +12,10 @@ categories:
 
 ## Attendees
 
-- [Elena](https://github.com/ElenaFdR) (chair)
-- [Jan](https://github.com/Ainali) (notes)
-- [Alba](https://github.com/AlbaRoza)
-- [Eric](https://github.com/ericherman)
+* [Elena](https://github.com/ElenaFdR) (chair)
+* [Jan](https://github.com/Ainali) (notes)
+* [Alba](https://github.com/AlbaRoza)
+* [Eric](https://github.com/ericherman)
 
 ## Foundation updates since December 2019
 
diff --git a/_posts/2020-03-20-notes-from-community-call-5-march-2020.md b/_posts/2020-03-20-notes-from-community-call-5-march-2020.md
@@ -20,9 +20,9 @@ categories:
 
 On the call:
 
-- [Jan](https://publiccode.net/team/jan-ainali.html) (chair)
-- [Alba](https://web.archive.org/web/20210225190155/https://publiccode.net/who-we-are/team/alba-roza.html) (notes)
-- [Boris](https://publiccode.net/team/boris-van-hoytema.html)
+* [Jan](https://publiccode.net/team/jan-ainali.html) (chair)
+* [Alba](https://web.archive.org/web/20210225190155/https://publiccode.net/who-we-are/team/alba-roza.html) (notes)
+* [Boris](https://publiccode.net/team/boris-van-hoytema.html)
 
 ## Call notes
 
diff --git a/_posts/2020-03-23-notes-from-community-call-19-march-2020.md b/_posts/2020-03-23-notes-from-community-call-19-march-2020.md
@@ -11,6 +11,7 @@ categories:
 # 19 March 2020 community call
 
 ## Attendees
+
 * [Jan](https://publiccode.net/team/jan-ainali.html) (chair)
 * [Laura](https://web.archive.org/web/20210225183245/https://publiccode.net/who-we-are/team/laura-scheske.html) (notes)
 * [Boris](https://publiccode.net/team/boris-van-hoytema.html)
@@ -30,12 +31,11 @@ We discussed our experiences working remotely under COVID-19 quarantine times. W
 We discussed tools that call participants deemed new or useful.
 
 1. Figma, an online collaborative graphic design and layout tool.
-
 2. Various chat apps (like Odoo, Slack and Mumble) were praised for the ability to separate multiple conversations into themes using 'channels'.
 3. Video calling apps (such as Zoom and VNC) for ability to screen share and hang out with larger groups. We also noted the difference a good headset makes.
 
 An important consideration while using all these tools (often several at once!), is to have a clear understanding within your organization on what to use each tool for. i.e. develop a clear **communications etiquette** that everyone adheres to. For example:
 
-- when it is important that your message is read: send an  e-mail
-- if you want to interrupt someone: call them
-- low priority chatter/information sharing: use a chat app
+* when it is important that your message is read: send an  e-mail
+* if you want to interrupt someone: call them
+* low priority chatter/information sharing: use a chat app
diff --git a/_posts/2020-06-03-notes-from-community-call-7-may-2020.md b/_posts/2020-06-03-notes-from-community-call-7-may-2020.md
@@ -32,7 +32,7 @@ This call discussed two topics: code coverage and design principles.
 
 ### Code coverage
 
-Boris started by giving a brief introduction to the [Standard for Public Code](https://standard.publiccode.net/). Then Eric gave an introduction to why he wrote [a blog post on code coverage](https://opensource.com/article/20/4/testing-code-coverage) and what he learned from that. The discussion that followed was mostly based around the central questions: "What are we measuring?" and "What do we want to achieve by measuring that?" 
+Boris started by giving a brief introduction to the [Standard for Public Code](https://standard.publiccode.net/). Then Eric gave an introduction to why he wrote [a blog post on code coverage](https://opensource.com/article/20/4/testing-code-coverage) and what he learned from that. The discussion that followed was mostly based around the central questions: "What are we measuring?" and "What do we want to achieve by measuring that?"
 
 There was a consensus that there is a risk that measuring just percentage of lines covered by tests will lead to poorer tests that cover all code rather than good tests that cover the important functionality of the code. Different strategies for mitigating that risk was discussed - for example, stewardship by the Foundation for Public Code could steer codebases from blindly trying to achieve complete coverage. The call did not come up with concrete suggestions to change the Standard but acknowledged that this might be worth further thought and discussion.
 
diff --git a/_posts/2020-06-22-notes-from-community-call-3-june-2020.md b/_posts/2020-06-22-notes-from-community-call-3-june-2020.md
@@ -29,7 +29,7 @@ categories:
 Renato joined the call for the first time and was curious about the Standard, and had heard about the new 'open by default' policy in the Netherlands. He shared a couple of links he found inspiring:
 
 * [Creating new collaborative organisations to operate shared services](https://www.dxw.com/2020/02/creating-new-collaborative-organisations-to-operate-shared-services/), a blogpost by Richard Pope and DXW
-* [How to Build an Open Source Business](https://www.youtube.com/watch?v=c9SJAPxU5bs), a video by Peter Levine and Andreessen Horowitz  
+* [How to Build an Open Source Business](https://www.youtube.com/watch?v=c9SJAPxU5bs), a video by Peter Levine and Andreessen Horowitz
 
 We gave a general introduction to the Foundation for Public Code, the [Standard for Public Code](https://standard.publiccode.net/), and the concept of [codebase stewardship](https://about.publiccode.net/activities/explaining-codebase-stewardship/). We will stay in touch to see how we can collaborate further.
 
diff --git a/_posts/2020-06-26-notes-from-community-call-18-june-2020.md b/_posts/2020-06-26-notes-from-community-call-18-june-2020.md
@@ -12,8 +12,8 @@ categories:
 
 ## Update from the Foundation
 
-- we're excited to have completed our support for the [OpenZaak market consultation](https://github.com/open-zaak/open-zaak-market-consultation) - this was a big new area of work for the codebase stewardship team, and we're not aware of any other market consultations hosted by public organizations that asked vendors how they'd like an open source codebase community to be structured
-- not a milestone, but it feels like [the team](https://publiccode.net/team/) has really settled into productive new working rhythms after having a new person join each month for the first 4 months of the year 
+* we're excited to have completed our support for the [OpenZaak market consultation](https://github.com/open-zaak/open-zaak-market-consultation) * this was a big new area of work for the codebase stewardship team, and we're not aware of any other market consultations hosted by public organizations that asked vendors how they'd like an open source codebase community to be structured
+* not a milestone, but it feels like [the team](https://publiccode.net/team/) has really settled into productive new working rhythms after having a new person join each month for the first 4 months of the year
 
 ## Attendees
 
@@ -32,7 +32,7 @@ Are there other aims (professionalism, public values?) that could be better achi
 
 ### Background reading
 
-- [Standard for Public Code issue 330: Code of conduct could cater to public organizations better ](https://github.com/publiccodenet/standard/issues/330)
+- [Standard for Public Code issue 330: Code of conduct could cater to public organizations better](https://github.com/publiccodenet/standard/issues/330)
 - [Standard for Public Code issue 331: Code of conduct is licenced CC-BY](https://github.com/publiccodenet/standard/issues/331)
 - [Open source guide on code of conducts](https://opensource.guide/code-of-conduct/)
 
diff --git a/_posts/2020-08-11-overdue-socially-distant-socializing.md b/_posts/2020-08-11-overdue-socially-distant-socializing.md
@@ -15,7 +15,7 @@ With this transition to a virtual working reality we were in dire need of some o
 
 ![Strolling through cool Dutch forests]({{site.url}}/assets/team-outing-walking-2020.jpeg)
 
-We spent the day hiking through this very diverse national park (temperate forests, heath, dunes), tried to spot the former Queen Beatrix in her castle, refueled for lunch at restaurant "Buiten in de Kuil", and stopped for ice cream on our way back. Check out the locations on the map below! 
+We spent the day hiking through this very diverse national park (temperate forests, heath, dunes), tried to spot the former Queen Beatrix in her castle, refueled for lunch at restaurant "Buiten in de Kuil", and stopped for ice cream on our way back. Check out the locations on the map below!
 
 <iframe src="https://www.komoot.com/tour/233215987/embed?profile=1&gallery=1" width="100%" height="680" frameborder="0" scrolling="no"></iframe>
 
diff --git a/_posts/2020-08-24-notes-from-community-call-6-august-2020.md b/_posts/2020-08-24-notes-from-community-call-6-august-2020.md
@@ -50,6 +50,6 @@ One possible positive side effect of the translations is that they can be a way
 
 ## Summary
 
-The community call was clear: there is a need for translations but they do not need to be "official". 
+The community call was clear: there is a need for translations but they do not need to be "official".
 
 The Foundation for Public Code will look into tools that can fit our workflow that will make it possible to provide community translated versions of the Standard for Public Code.
diff --git a/_posts/2020-09-23-episode-one-of-lets-talk-about-public-code.md b/_posts/2020-09-23-episode-one-of-lets-talk-about-public-code.md
@@ -24,7 +24,7 @@ The video is available in a number of places:
 
 ## Where can I find the podcast?
 
-Do you prefer to listen to just the audio? Then you're in for a treat! We've published a polished version of the interview at [podcast.publiccode.net](https://podcast.publiccode.net/). 
+Do you prefer to listen to just the audio? Then you're in for a treat! We've published a polished version of the interview at [podcast.publiccode.net](https://podcast.publiccode.net/).
 It is also available on most podcast players, so take a few secsonds to subscribe and never miss an episode:
 
 - [Spotify](https://open.spotify.com/show/3m7m3AtL0jf67NpQ9B9HRs)
diff --git a/_posts/2020-10-12-notes-from-community-call-1-october-2020.md b/_posts/2020-10-12-notes-from-community-call-1-october-2020.md
@@ -43,7 +43,7 @@ Following this, we talked a little bit about [our definition of public code](htt
 
 The discussion was mostly philosophical, and it became clear that codebases are diverse: for some it is very obvious that a specific policy is being implemented, and for others it is equally obvious that none exist. The interesting parts are all those cases in between where either:
 
- * it is plausible that a codebase implements policy but it is not being stated explicitly
- * a generic codebase is used as a tool to execute policy, but the policy is not implemented in the codebase itself
+* it is plausible that a codebase implements policy but it is not being stated explicitly
+* a generic codebase is used as a tool to execute policy, but the policy is not implemented in the codebase itself
 
 This discussion was enlightening but not conclusive, so we need to continue it in the future.
diff --git a/index.md b/index.md
@@ -9,8 +9,7 @@
     </li>
   {% endfor %}
  </ul>
- 
- 
+
 ## About this blog
 
 ![Our frontdoor](/assets/frontdoor-2019-05-07-small.jpg)
