I’ve just re-read the QWT community doc: there’s a lot of info there - which is great - but it will take a significant amount of work/time to find out what content is still relevant for R4.1 together with the updated QWT tools, vs. what part is outdated.
Having spent a considerable amount of time writing detailed guides/doc a few years ago, and seeing how most of their content hasn’t aged well, maybe there are a few important things to agree upon before you - or anyone - spend a lot of time too:
-
Should content known to be outdated/non-relevant to the current Qubes OS releases be deleted ? In a perfect world with unlimited resources it’d be nice to have docs for each release but it’ll be much easier to just stick to the current version and scrap old stuff - IMHO.
-
Should content that isn’t known to work with the current release be preceded by a “This content is untested for R4.1” banner ? (that could be because the instructions didn’t mention what release they applied to and testing to see if they’re still relevant would take time)
-
Should new content always mention the release they apply to - eg. “Those instructions are for Qubes OS Rx.y” ? (I think it should, rather than trying to find out later on what release the original author used).
-
Content specific to QWT: since it’s a “fast moving target”, at least for now, decide what to do with the QWT doc; eg.
- Add a “banner” at the top of the doc that content might be outdated, and redirect to this wiki page ?
- Add banners to sections that are known to be outdated, or unknown to work with R4.1 ?
- Temporarily replace the link to the QWT doc with the wiki page, until the doc’s content is fully updated to reflect the current qubes release / QWT version ?
-
More generally, favour the forum’s wiki functionality over community/official docs to publish community guides and only put links in the community/official docs ? The you-must-send-git-PRs approach proved/proves to be too much of a hurdle for people to contribute stuff ; compare to how easy it is to create a post here for posterity with a “fyi that’s how I solved that, hopes this helps others” (which can then be improved upon and transformed into a wiki guide). It doesn’t help either that even the github qubes-community project, which ought to be much more “relaxed” than the official docs, seems too curated.
@adw - that’s your area here - thoughts ?