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

    • Type: Story
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: Qserv
    • Labels:
      None
    • Story Points:
      1.2
    • Sprint:
      DB_S14_06, DB_S14_07, DB_S14_08
    • Team:
      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

            jammes Fabrice Jammes created issue -
            jammes Fabrice Jammes made changes -
            Field Original Value New Value
            Sprint DB_S14_06 [ 35 ]
            jammes Fabrice Jammes made changes -
            Summary Improve documentation and migrate it to RST format Improve documentation and migrate it to reST format
            jammes Fabrice Jammes made changes -
            Description This ticket propose to migrate README and README-devel to RST format. 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.
            {quote}
            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"?
            REDME-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 .'
            {quote}
            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.
            {quote}
            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"?
            REDME-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 .'
            {quote}
            jammes Fabrice Jammes made changes -
            Reviewers Andy Salnikov [ salnikov ]
            Status To Do [ 10001 ] In Review [ 10004 ]
            jbecla Jacek Becla made changes -
            Sprint DB_S14_06 [ 35 ] DB_S14_06, DB_S14_07 [ 35, 36 ]
            jbecla Jacek Becla made changes -
            Rank Ranked higher
            jammes Fabrice Jammes made changes -
            Epic Link DM-51 [ 11299 ]
            jammes Fabrice Jammes made changes -
            Link This issue is blocked by DM-622 [ DM-622 ]
            jammes Fabrice Jammes made changes -
            Summary Improve documentation and migrate it to reST format Improve install/configuration/tests documentation and migrate it to reST format
            jammes Fabrice Jammes made changes -
            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.
            {quote}
            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"?
            REDME-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 .'
            {quote}
            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.
            {quote}
            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 .'
            {quote}
            jammes Fabrice Jammes made changes -
            Story Points 1 1.2
            jbecla Jacek Becla made changes -
            Team Database [ 10204 ]
            jbecla Jacek Becla made changes -
            Sprint DB_S14_06, DB_S14_07 [ 35, 36 ] DB_S14_06, DB_S14_07, DB_S14_08 [ 35, 36, 37 ]
            jbecla Jacek Becla made changes -
            Rank Ranked higher
            jammes Fabrice Jammes made changes -
            Link This issue blocks DM-649 [ DM-649 ]
            salnikov Andy Salnikov made changes -
            Status In Review [ 10004 ] Review Complete [ 10101 ]
            jammes Fabrice Jammes made changes -
            Resolution Done [ 10000 ]
            Status Review Complete [ 10101 ] Done [ 10002 ]

              People

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

                Dates

                Created:
                Updated:
                Resolved:

                  Jenkins

                  No builds found.