I would prefer TechNotes also in LatTex and in a single git repository. Existing "important" technotes should also be PDFed and lodged in Docushare. Robert McKercher would be willing to help with this perhaps.
Userguides .. I can be convinced could be in rst/markdown .. in one of my other projects we still did the top level user guide in TeX but linked to the sphinx generated docs lower down.
Tex Templates for some document types and a DM (now looking more like LSST documents) documentclass are here https://github.com/mjuric/lsst_texdoc
I would say the assignment from Jacek absolutely stands - LDM-493 is completely avoiding the issues mentioned. Namely I do not see :
Point 1. An inventory of all DM documentation including what lives where. Identify obsolete and out of date documentation
Point 2. A document tree to Identify missing documentation
Point 3. Come up with structure (what goes where). Consolidate (reduce) the number of technologies we use for documentation, and clearly define boundaries what should be documented using what technology.
Rather LDM-493 seems to introduce a new technology and I do not understand the approach of having each doc in a single repo and with its own domain.
Point 4. I do not see policies defined
Without the above the other points are impossible to fulfil.
I propose we tackle this in a more systematic way:
A simple policy exists in LSST - Documents should be published as PDF to docushare - we should start to follow the established LSST policy (point 4) before adding our own. Then I have a strong preference for draft documents to be in Latex in a single git repo (I potentially can be convinced otherwise) - having such a repo or having followed the LSST policy would have already avoided the problem of trying to find docs (point 1).
I will put a document tree (taxaonmy) together for DM documents and am happy to have some input to that - I do not have your (Jonathan Sick) work description but I would assume this could fall in your remit. LDM-294 as a top level DM management document should for me contain this, as well as the DM organisation (in dev and in OPS and a clue as to how we transition), Configuration Control, Document Control policies etc .. this will then help to identify which documents are missing (point 2)- then the inventory would be good to know what we have and where it is.
But a couple of documents were given priority namely, risk process and test/validation plan, plus i have limited time since I do not yet work for LSST.
Let me add - delivering DM is everyone's job and we are all responsible for documentation which is part of that delivery.
Also my apologies if the inventory of all docs exists somewhere and also identifies what is missing.
Now its well past my dinner time.