On the other hand, I'll use a single running node for short-content meetings. The node-per-instance model works well for me when I have long notes or need to make per-meeting tweaks to the script. This way, I have notes for each meeting available without having to use version control. I have a template for the IRC commands in one of the higher-level nodes, which I copy into the child nodes with the appropriate details filled in. Under those child nodes, I have nodes for each iteration of the meeting. Each release is a child under that, with a subsequent child node for the beta and final meetings. My Fedora CherryTree file has a node for release meetings. In my role as Fedora program manager, I run several IRC meetings. Child nodes can have their own children with independent properties. Each node can have child nodes, allowing you to easily organize your information. In Linux, everything is a file in CherryTree, everything is a 'node.' Nodes can be plain text, rich text, or have automatic syntax highlighting for a variety of common programming and markup languages. I quickly found CherryTree, a GPLv3-licensed note-taking application. When I left Microsoft to take a job at Red Hat, I wanted to keep using the concept, but with an open source tool.

The hierarchical nature of OneNote files made it easy to arrange this loosely related information into a well-organized set of documentation that I could quickly refer to. I had to learn about internal procedures and tooling, partners, projects, and so many other things.

When I started working at Microsoft a few years ago, one of the first things I did was create a OneNote file to keep track of everything.

Cherrytree software note