Doc updates to NTP best practices
25 views
Skip to first unread message
Martin Thygesen
Sep 2, 2019, 5:33:10 AM9/2/19
to qubes-users
Is there a particular approval process required to augment the existing documentation structure.
I want to augment the existing Time update documentation with relevant details on using NTP correctly
Per
I want to update this documentation with the information located here
The how to on changing timezone is ok but it does not provide guidance on the intent behind the use of NTP and which VM to use for that purpose.
I'm capable of expanding this doc, but just want to make sure the devels' are ok with this strategy
- Martin
Andrew David Wong
Sep 2, 2019, 5:47:27 AM9/2/19
to Martin Thygesen, qubes-users
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Thank you for your willingness to contribute to the documentation!
General information about updating the docs is here:
https://www.qubes-os.org/doc/doc-guidelines/
To answer your specific question, if it's a relatively small PR, you
can simply submit the PR, and we'll hash it out in that PR. Worst
case, it gets closed rather than merged, but no big loss, since it was
relatively small.
On the other hand, if it would be a lot of work that you
(understandably) don't want going to waste, then it would better to
open an issue that describes your proposed documentation enhancement,
and we can hash it out there before you submit a PR.
- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAl1s5R8ACgkQ203TvDlQ
MDCzyg/8CR2D2Icj/4FRmyI5+9/43GvdjAlqUYsTiOKpu1KZLmBhITLfpXkmlU+S
GweO44QfRTq5oyHfyCyXEc91aTHNSyqJcRD/Vs8a6AeJW6tPByDVxx7ydXdfMwsv
X/OOWowSRMt/kV2xUx26LG5egRpJzrgktYpON6FMUHaKwGqhFssW74pi9tNaeRKH
zvOjiW8rOAtcjufMJR5dgK5dmQbKhivfB5VhprhA5qhS5RyK01bu+gAxmsGBZN4k
2gyhj5Tt5DqbwovwZ/gqyso4XSYXHg9oE0cZ+bdsfXauUBWnAIFR8WRniXm741iE
Nwt4pAa1niuCL380XO6KZTCg1D18fsRnU1TXmSifMVUQ5qdk54K0oRkFDPq3a42T
iiJZaU1DTMU7fY5oV7yRHGNhgZSxeo4U6OH2VUJBEHxmeMqBySX1zsDjfRwuPar1
HZFaAY2ql7JnF/m5Bl4AJktOngsrLNc94DIL7haaHjXACHXGXASukbeMBLoZsKUG
cKT2oSzfRjav9s0Hmz7zVJOkmYbVHtUM+z2JwTUeAJVHontaZ0bBTUkzB8yDh4s/
vxwBDJbA/MzV8vtxCcXGUV96Hd4gGj7vAGwgciuH/wMLc8vdQ21l9MRHvhJx+fCH
xR5sn34GNA2Ak7KUqiiz5hBUpKtprf6HqD9lzvjQWQ9lMQ+1lEY=
=m3bI
-----END PGP SIGNATURE-----
Hash: SHA512
General information about updating the docs is here:
https://www.qubes-os.org/doc/doc-guidelines/
To answer your specific question, if it's a relatively small PR, you
can simply submit the PR, and we'll hash it out in that PR. Worst
case, it gets closed rather than merged, but no big loss, since it was
relatively small.
On the other hand, if it would be a lot of work that you
(understandably) don't want going to waste, then it would better to
open an issue that describes your proposed documentation enhancement,
and we can hash it out there before you submit a PR.
- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAl1s5R8ACgkQ203TvDlQ
MDCzyg/8CR2D2Icj/4FRmyI5+9/43GvdjAlqUYsTiOKpu1KZLmBhITLfpXkmlU+S
GweO44QfRTq5oyHfyCyXEc91aTHNSyqJcRD/Vs8a6AeJW6tPByDVxx7ydXdfMwsv
X/OOWowSRMt/kV2xUx26LG5egRpJzrgktYpON6FMUHaKwGqhFssW74pi9tNaeRKH
zvOjiW8rOAtcjufMJR5dgK5dmQbKhivfB5VhprhA5qhS5RyK01bu+gAxmsGBZN4k
2gyhj5Tt5DqbwovwZ/gqyso4XSYXHg9oE0cZ+bdsfXauUBWnAIFR8WRniXm741iE
Nwt4pAa1niuCL380XO6KZTCg1D18fsRnU1TXmSifMVUQ5qdk54K0oRkFDPq3a42T
iiJZaU1DTMU7fY5oV7yRHGNhgZSxeo4U6OH2VUJBEHxmeMqBySX1zsDjfRwuPar1
HZFaAY2ql7JnF/m5Bl4AJktOngsrLNc94DIL7haaHjXACHXGXASukbeMBLoZsKUG
cKT2oSzfRjav9s0Hmz7zVJOkmYbVHtUM+z2JwTUeAJVHontaZ0bBTUkzB8yDh4s/
vxwBDJbA/MzV8vtxCcXGUV96Hd4gGj7vAGwgciuH/wMLc8vdQ21l9MRHvhJx+fCH
xR5sn34GNA2Ak7KUqiiz5hBUpKtprf6HqD9lzvjQWQ9lMQ+1lEY=
=m3bI
-----END PGP SIGNATURE-----
Reply all
Reply to author
Forward
0 new messages