I'd like to review the documentation and remove or mark as obsolete parts that don't correspond any more to the software or to current practices, e.g. use of pacman.
I started some changes in a branch off master: master_marco_doc
I decided to start with html documents and will change also the glideinWMS.ini template to match updated recommendation
Here I have some questions:
Pacman can be removed as installation method for the dependencies (no more supportedm there are RPM and tar balls). Correct?
Are the pacman options still mandatory (with empty value but in the file)?
HTCondor is not making GCB available any more. Should I remove the section? Should there be something else instead?
Same for Quill. Can the section be removed?
#2 Updated by Marco Mambelli over 5 years ago
Updated documentation, consistency, links, general updates
- Name is GlideinWMS
- Uniform component names (User Pool, WMS Pool, ...)
- HTCondor instead of Condor
- updated links to condor manual
- no more dead links
- more links to RPM installs
- Pacman no more available
- removed GCB section
- kept quill but did not check its validity/did not update
- GIT command instead of CVS
I checked w/ Parag and there are no plans to replace Pacman OSG Client installation w/ the tarball one.
The current documents suggest to pre-install OSG Client and point to OSG documentation.
List articles about GlideinWMS in the documentation list.
Suggest an article for references to GlideinWMS (people that have to cite it in papers)
And maybe add it also in the documents footer
Something to think more long term could be the possibility to move the documentation to a templating system:
- something like template-toolkit (http://template-toolkit.org/python/index.html) or jekyll (http://jekyllrb.com/docs/templates/)
- the result are static pages like the current ones
- it allows inclusions and variables that would make document maintenance easier