2.1 Organizing your notes

org-gnosis provides a zettelkasten-inspired approach to note-taking, treating knowledge (gnosis) as valuable and not merely something to be boxed into a single category, to be disposed after a certain period of time or task accomplishment.

Using directories to organize your notes is not recommended, a preferred method is to create MOC files (Maps Of Contents) for specific categories/projects that you are working on.

An MOC file can be the syllabus of a class or a project road map. For example, you might create an MOC like this for a class on Biopolymers:

• First create a node using M-x org-gnosis-find followed by Biopolymers, which will be created if it does not already exist.
• Use M-x org-gnosis-insert-tags to insert moc tag.
• Start inserting your syllabus points with M-x org-gnosis-insert as nodes, which will be automatically created & saved in separated files.

Example:

:PROPERTIES:
:ID:       15edada1-9815-4fb3-9b8f-7da08107bdb2
:END:
#+title: Biopolymers Syllabus
#+filetags: :moc:

* Proteins
- Protein Structure Levels
- Protein Domains
- Protein MOTIF
- Difference between a motif and a domain in a protein
- Protein Families

* Nucleic acids
- DNA
- RNA
- Recognition and self-assembly of macromolecules
- Cytoskeleton

Note: Items with ‘-’ would be links. The headings in the above example could be links to an MOC as well.

This way your notes are atomic & can be reused in future classes/projects.

• For example you’d reuse your notes on nucleic acids in a genetics class MOC for your next semester.

2.2 Importing Notes

If you are a previous user of packages that use org-mode and org ids, your current note collection should be able to work with org-gnosis without you having to change anything.

To sync your note collection use M-x org-gnosis-db-sync

3.1 Sources

• Main repository: https://git.thanosapollo.org/org-gnosis/
• Mirrors:
  • https://codeberg.org/thanosapollo/emacs-org-gnosis

3.2 Patches Require Copyright Assignment To The FSF

Code contributions are most welcome. For any major edit (more than 15 lines, or so, in aggregate per person), you need to make a copyright assignment to the Free Software Foundation. This is necessary as the FSF must at all times be in a position to enforce the GNU General Public License.

Here’s the process:

1. Review and adapt the request form below.
2. Email the specified address with your request.
3. Await a legal agreement from the FSF.
4. Sign and return the document, which can be done via email.

The entire process usually takes about a week and needs to be completed only once, allowing you to contribute to GNU Emacs.

Please email the following information to assign@gnu.org, and we
will send you the assignment form for your past and future changes.

Please use your full legal name (in ASCII characters) as the subject
line of the message.

REQUEST: SEND FORM FOR PAST AND FUTURE CHANGES

[Additional people we should notify about the progress of the assignment.]

Thanos Apollo <public@thanosapollo.org>

[What is the name of the program or package you're contributing to?]

Emacs

[Did you copy any files or text written by someone else in these changes?
Even if that material is free software, we need to know about it.]


[Do you have an employer who might have a basis to claim to own
your changes?  Do you attend a school which might make such a claim?]


[For the copyright registration, what country are you a citizen of?]


[What year were you born?]


[Please write your email address here.]


[Please write your postal address here.]


[Which files have you changed so far, and which new files have you written
so far?]