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. I prefer Markdown, its just stripped down HTML which itself is like Word at the very base of it, its just instead of having a bloated program render it as you type, you use elements and css, and don't know the WYSIWYG side too well other than to know that OpenOffice/LibreOffice suck donkey balls. I also would suggest you spend sometime determining if you want to use Markdown or a WYSIWYG editor. In theory could keep your whole system backed up on it, but I don't even try to do that still the price is right). So I would rule out anything like Notable, NotesUp (especially the stupid database abstraction layer here cost me hours of reassembling my notes renaming what I could even recover) and other options without very direct Dropbox integration (worth paying for, 10 bucks for 2 TB and it works. With applications available via the 'app stores' various DEs package into themselves, you will be fine until you try to recover the notes you made if for instance you have to reinstall (which happens) or other unforeseeable disaster strikes as such is the nature of Linux to strike you when you are least prepared. What to Use If Loosing Notes Doesn't Bother You
0 kommentar(er)
