Documentation : life cycling
How will we maintain regular updates to the public, the community and also to the maintainers of libre.sh?
Note taking during calls happens either continuously in the same, or via a backlink to previous pad ("HEAD
").
Some of the more interesting highlights include:
- "pad of pads 2018"
-
📄 standardize user signup on web free software (📝 )
continued in Standardisation of sign up experience in the free software world - Talk - libreho.st
Also questions about long term perspectives #2 for maintenance resurface at times and we also rewrite our understanding of the
-
A subdomain docs.libre.sh
seems useful to provide documentation for users/developers and the maintainers. -
A presentation on a https://libre.sh (which still redirects to GitHub) website can be informative to -
A declaration of the value propositions can constitute a shared community. -
Process notes migrate from https://wekan.indie.host/b/aEDScbA8LWbK42Ecx/libre-sh-organisational-perspective into the issue tracker here
Federated writing experiments can liberally continue in wiki.libre.sh
Which other aspects, like the OpenCollective page and updates there, come to your mind when thinking about the life cycles of documentation processes?