Hi Maxim, >> It would be nice to have user notes below the manuals too just like it's >> done >> in the PHP world to let people know what's the actual state of the things >> we're documenting. >> >> One example where this would have been useful to me is docker, what we >> have packaged in Guix is severely >> outdated, and when I was at the meeting held by Tanguy he just told me that >> everyone using podman anyways, I think you should not have to search >> through >> mail/irc/attend event to know that. > > I think we could add footnote for that. But really, what would be > ideal is someone steps up to update the docker package in Guix, instead > of documenting that 'beware, our package is currently outdated'.
I do agree that ideally this should get fixed right away, but I still think there is value in having a place where user can comment on that kind of details whether it be in the manual or some other places. I do believe that we should have a wiki and regular forums like they do with the arch wiki in addition to the mailing list. There is so much people not keeping up with the mailing lists for many reasons. I just created the awesome list here: https://github.com/tieong/awesome-guix Made a reddit post as well https://www.reddit.com/r/GUIX/comments/1jhwt77/improving_the_docs/ Had nice feedback, one of them is that we are lacking lot of docs in the security department. And I noted these bullet points for myself and anyone else up to write something. - How do we manage secrets in Guix? How do we make sure some secrets in a config.scm don't end up in the store that kind of thing. Someone made this blogpost which was interesting: https://fishinthecalculator.me/blog/secrets-management-with-sops-guix.html - Full disk encryption, do we support luks2, Luks on LVM, can /boot be stored unencrypted? Why do we need to type our password 2-3 times to unlock our computer? - What firewalls do we have? - SELinux, App Armor? - Hardened kernel? - TPM?
