blog: pmOS year priorities

I've included quite a lot of background, not sure if I went too far. Let's see what people think. Deadline is next Sunday 16th, but could also be Sunday 23rd if need be. when it is ready :)

There is still lots of work to do, thus marked as Draft

assigned to @pabloyoyoista

added 1 commit

• 82f3eec5 - blog: pmOS year priorities

Compare with previous version

added 5 commits

• 82f3eec5...d10e3f4c - 4 commits from branch master
• e355b926 - blog: pmOS year priorities

Compare with previous version

added 10 commits

• e355b926...5ab23075 - 9 commits from branch master
• 5f9a2659 - blog: pmOS year priorities

Compare with previous version

I finished filling out all the boilerplate for this blog post. As discussed with @ollieparanoid changed the target for the 9th of March

marked this merge request as ready

requested review from @ollieparanoid

unassigned @pabloyoyoista

added 1 commit

• 23cb1414 - blog: pmOS year priorities

Compare with previous version

requested changes

added 25 commits

• 23cb1414...5c5b5350 - 22 commits from branch master
• 62df8bfd - blog: pmOS year priorities
• 75f2d1c5 - blog: year priorites v2
• 137afe3d - config: usernames: add ci-tron people

Compare with previous version

@ollieparanoid this is the take 2, trying to implement the structure you asked about. Before sinking more time on it, I want to make sure it makes sense to you how it reads. I've put it into a new file to ease the transition for myself, but we should just remove the first commit before merging

added 2 commits

• eedb6775 - blog: year priorites v2
• ba9392e2 - config: usernames: add ci-tron people

Compare with previous version

added 2 commits

• 6469d4cc - blog: year priorites v2
• 296d2d69 - config: usernames: add ci-tron people

Compare with previous version

added 2 commits

• d3fef00b - blog: year priorites v2
• 574329d9 - config: usernames: add ci-tron people

Compare with previous version