No, documentation doesn't have to be boring. Well, it can of course be a soul-numbing, Kafkaesque exercise, but then, can't everything?

In an open-source project, good documentation is a must; everything needs to be explained and discussed properly for the benefit of all interested, and particularly for collaborators.

And not writing documentation in a group endeavour will land you in precisely the situation Josef K enjoyed so very much. Even in agile Prozesse – it's a myth that agile discourages documentation. It's all about the appropriate level. But then, isn't it always?

Ultimately, writing – and reading – documentation is all about the proper conservation of energy. It's just a question of finding the point where the curves intersect.

Anyway, here are a few additions to the Documentation section you might like. Feel free to evaluate them as lazily as you wish:

Architecture Decision Log

• Now expanded with a bunch of additional ADRs.

Backend src README

• Read all about it! Well, perhaps not all about it, but at least about the backend architecture, code organisation, principles, conventions, and of course the general programming paradigm.

Development Plan

• Quod factum est, quod fit, quod fiet.

​
​License

• Mozilla Public License (MPL) 2.0, with a couple of small twists.

Code of Conduct

• Our Code of Conduct. Because not having one is being naive.