Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-930

Improve install/configuration/tests documentation and migrate it to reST format

    XMLWordPrintable

Details

    • Story
    • Status: Done
    • Resolution: Done
    • None
    • Qserv
    • None
    • 1.2
    • DB_S14_06, DB_S14_07, DB_S14_08
    • Data Access and Database

    Description

      This ticket propose to migrate README and README-devel to reST format (see http://sphinx-doc.org/rest.html). The output is located here : http://lsst-web.ncsa.illinois.edu/~fjammes/qserv-doc/

      Furthermore this ticket wil integrate Andy S. DM-622 value-added remarks about Qserv embedded documentation.

      README.txt needs a bit of formatting, whole "NOTE FOR DEVELOPERS" is one long line which may need scrolling depending on what do you use to read the file, same applies to README-devel.txt
      The install procedure in README.txt implies that the whole stack has to be installed including eups. If people have some part of it installed already the it would probably be better to reuse existing stack. Shall we spit install instructions into "Install eups (if not installed already)" and "Install qserv"?
      README-devel.txt says "Once Qserv is installed...", I don't think that we need or want to install whole qserv before we start development (what if qserv is not available yet for the platform I'm trying to test). What probably needed is installed dependencies, and this should be covered by the comments before 'setup -r .'

      Attachments

        Issue Links

          Activity

            No work has yet been logged on this issue.

            People

              jammes Fabrice Jammes
              jammes Fabrice Jammes
              Andy Salnikov
              Andy Salnikov, Daniel Wang [X] (Inactive), Fabrice Jammes, Jacek Becla (Inactive), Kian-Tat Lim
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Jenkins

                  No builds found.