Emily

Do we want the wiki to apply to develop, or to master (i.e. the latest release)? If to master, then the proposed workflow doesn't work. Generally, if we want to...

Alternatively, we can make it a part of the release checklist: somebody has to go through the CHANGELOG and update the wiki. In this case having `/docs` is pointless for...

> feel free to suggest some simpler way of getting docs in place. Alright, here's my own proposal: ## A bunch of Markdown files on Github We put docs as...

Oh, right, the last point. ## "that can be used without getting near any source code" If we rename our `doc` folder to `docs`, we can get a Github Pages...

(NB: I might sound confident because it's 1am already and I'm tired. In reality I have literally no idea how to get good documentation for any project. None of the...

> To accomplish effortless wiki-like editing process, people shall be allowed to push documentation-only commits directly into develop, similarly to how people can currently edit the wiki and nobody reviews...

> The question is, when writing new sections (more than, say, 10-20 lines) of documentation, how "effortless" does it need to be, is a PR + review + merge too...

If I understand correctly, this involves basically ditching our own existing E2E protocol (https://github.com/wireapp/proteus), moving to something like OMEMO, and implementing OMEMO support in all our clients. Then, whenever we...

Also: I'm not familiar with XMPP federation, so I'm curious to know whether adopting XMPP will make federation easier for us even if we decide that we still need to...

Oh, just in case: I wasn't implying "this is not trivial so why are you even proposing this". Far from it. I will, however, admit that I'm sceptical about standardization...