<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xml:base="https://blog.cnuc.nu/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>cnuc</title>
    <link>https://blog.cnuc.nu/</link>
    <atom:link href="https://blog.cnuc.nu/feed.xml" rel="self" type="application/rss+xml" />
    <description>a personal blog</description>
    <language>en</language>
    <item>
      <title>A consensus voting mechanism</title>
      <link>https://blog.cnuc.nu/posts/consensus-voting-mechanism/</link>
      <description>I recently went to an event where many decisions needed to happen and where consensus was important. With this backgound a person introduced a consensus voting mechanism developed to be effective in reaching consensus. The process First a proposal is presented to be voted on. Then there are four actions to take in a voting round. Agreement This is signalled by raising your hand. Counterproposal This is signalled by raising your fist. Question This is signalled by raising a finger. Indifference This is signalled by your palm facing the ground. If someone has a question, then the question is asked and answered and a new voting round is made. If someone has a counterproposal then the proposal is presented and a new voting round is started based on the new proposal. If everyone is in agreement or are indifferent, a decision has been made.</description>
      <pubDate>Wed, 23 Aug 2023 00:00:00 +0000</pubDate>
      <dc:creator></dc:creator>
      <guid>https://blog.cnuc.nu/posts/consensus-voting-mechanism/</guid>
    </item>
    <item>
      <title>Git commit messages</title>
      <link>https://blog.cnuc.nu/posts/git-commit-messages/</link>
      <description>OK, so I read three articles/blog posts about good commit messages. I did this so you don’t have to. The best one of then was this one by Jacob Herrington. The first line of the commit message is the subject line. Start with a capital letter. Use no more than 50 letters. Don’t end with a period. This should be a good summary of the change. Write in imperative mood: Fix, not Fixes or Fixed. The second line should always be empty. The body of the commit message should focus on why the change was made. (Unless it is a minor obvious change) Then write what was done. Give context. This is the part that the subject line of the commit message is summarizing. Happy committing.</description>
      <pubDate>Mon, 23 Mar 2020 00:00:00 +0000</pubDate>
      <dc:creator></dc:creator>
      <guid>https://blog.cnuc.nu/posts/git-commit-messages/</guid>
    </item>
    <item>
      <title>Vegan Pancakes</title>
      <link>https://blog.cnuc.nu/posts/vegan-pancakes/</link>
      <description>Ingredients: 3 dl Flour 6 dl Soy Milk 1⁄2 dl Rapeseed Oil 1⁄2 krm Salt Stir and bake. Yum, yum.</description>
      <pubDate>Sat, 21 Mar 2020 00:00:00 +0000</pubDate>
      <dc:creator></dc:creator>
      <guid>https://blog.cnuc.nu/posts/vegan-pancakes/</guid>
    </item>
  </channel>
</rss>