Displaying 2 results from an estimated 2 matches for "eod1amifnnqrodvy0".
2015 Mar 16
0
Docs strategy and tactics [RFC]
...6hD8G955c5JH3KnzSBmCRPaHxbv7
XX7sBJwR66LMI1RwWH4yfSuQQ3shhp9r2kxkPpNhB7bj70qR4/oQcOJSkwTV2OtR
mjM7hOXh5wGRWCbsJajQ+bYBnEMHLUWhGWg1oaeWWhhF7sutsSCqgwVcS4bVCu8i
uQyvhxgIJhJZWfFR2jTgoJgrMHwceoSjBS9K8DLEmWqu5edpIk/xoPSiWuwDfU46
auSqtYBfPztPLKvmq6gzkR/YniFZXdCLSyP/nowbsnoDkKoveNnh42bRGybM7ckg
j0UL2Uxk3C+EOd1AMiFNNqRoDVy0+WsfwOwFJsSif3JjXJtXwHKjEnkPf2k2cSFD
XoictwEmTJH50dzI9DOS
=C+5k
-----END PGP SIGNATURE-----
2015 Mar 12
6
Docs strategy and tactics [RFC]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I've been thinking for a little while, and talking with people, about
what would be a good documentation strategy for the CentOS Project.
== tl;dnr aka Summary
This is a proposal around creating new, short-format
documentation about doing cool new things on top of CentOS
Linux. These docs would support the work of the various SIGs (Cloud,