-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 2020-09-22 8:22 AM, c1e0 wrote:
> Hiya!
> 
> Happy to be here.  \o/ . I'm Cleopatra. I go by c1e0 here and on IRC, and 
> my username on GitHub is PROTechThor. I'm the Google Season of Docs 
> technical writer (Thanks again for accepting my proposal, Marek). I've been 
> lurking around here for some time. I should have said something earlier, 
> but I was so caught up trying to refine the Troubleshooting Guide document 
> layout. 
> 

Welcome! Thanks for working on this. :)

> The official documentation development period began last Monday. Here are 
> some things I did last week:
> - Attempted to set up a local version of the Qubes website (facing some 
> podman issues. Should figure this out soon)

Feel free to ask me questions about this. I recently dealt with the same
thing and have a working setup now.

> - Searched Github issues, #qubes-users, Reddit and Discourse for common 
> issues. I recorded every issue which was mentioned at least three times. I 
> managed to go as far back as 2018, when Qubes 4.0 was released.
> - I went through all (I think) the existing documentation to find any 
> troubleshoots lurking within instructions and recorded them.
> - I modified my initial proposed layout 
> <https://docs.google.com/document/d/187NlnEvctYVVUnRuGtwY2PkYBVxBSSPfpSwZEaczqL8/edit?usp=sharing>
>  
> for the Troubleshooting Guide. This initial layout was severely lacking in 
> terms of content. I have expanded upon it, as you can see in my new and 
> improved document layout pasted below. The caterogization is also improved, 
> in my opinion. 
> 
> Do you have any feedback on this new layout? I don't think it's perfect 
> yet, but I will commence writing the guide and maybe make changes to the 
> layout as I go. Some things may be added and others removed. We'll see. I 
> will try to submit a PR weekly, each one addressing one or two of the 
> troubleshooting topics. 

Just a cursory read, but it looks pretty good to me. I see a lot of
problems that are common pain points for users. I'm sure other folks
will have more detailed things to say about specific points.

> I didn't account for how long it would take me to refine the document 
> layout in my initial proposal timeline. I'll put together a new timeline 
> soon, depending on how this and next week goes. 
> 
> *Refined TROUBLESHOOTING GUIDE layout*
> 
> [...]

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAl9qHhIACgkQ203TvDlQ
MDBjfw/9FMAsnrfbW2oYDKWxFehDPHbPYR43HDYL5ugZ2FM+IDq+aahFRu7BHriA
/zc6yyr9mwHr781Yra1FwSQXkYWGMAhsYtLV71yO0xBNIxOXNoeOU8zSi4rl7PMn
O/Izkk+GO2GiszULGKkdUsHGqg1nCzswL/ytX9Hkvsxa8lwtVAac9RF++usHrmgn
MsGzm0YwSX/KD/P7C/MZUNKO30ynwrbb7Dh6UjBlY+RWpIMyRDonMvfyBiAPgq7z
i1YIcr8R4z6Gbw39QUcHZ3rwnSITf0+2KQz6Fg15zsvLO+uixe9qzqnIkJ7fvrFC
bRpI310Bojy0gToTsexNsrpTNwL9K5ZG1B3p9jxkbzwJWJ3fsV1ezZikrjLUBh00
5yyf7nrDJXI8v+9yt32OTsfbZgFg6C5J2bKc8DM8dw6xL7ovhb9y7xrUdiL9uBnh
btlXJMbuIHlH4kGtdtmXupr+7GJraeb8U+dznzxEoY1TqlWfBA9oJaAJFtUvlJqz
FAN6wjRb649rLHdlJbMc1IdaTQIVmkUcfxMC94Y5WKhT0QVZ3bXKMYbCXNBjgPhe
m0siAxPD6rXkD5GjaZtJN10bEwsXE5axQY95PcqpzCzbwit7XoXdLFqblz6htIbO
q1Aqv9JyyDL7k4bprlGcy3LQiQOtVCjm0Gz7uvJ9mC5z673uilU=
=Pzc3
-----END PGP SIGNATURE-----

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-devel/c57d08f2-1ba5-99a9-ae2e-bf9d71733f01%40qubes-os.org.

Reply via email to