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

Fix/delete “Top-level packages” topic in pipelines.lsst.io

    XMLWordPrintable

    Details

    • Story Points:
      2
    • Sprint:
      AP F23-3 (August)
    • Team:
      Alert Production
    • Urgent?:
      No

      Description

      John Swinbank reports the page on top-level packages doesn’t work:

      [..] https://pipelines.lsst.io/v/15-0/install/top-level-packages.html is fairly unhelpful — does some poor scientist who just wants to try out the LSST codebase want “the core packages that LSST will use in operations”, or do they want something else? Could we just add a banner saying “if you don't know what you want, you want this”?

      “This” should probably be lsst_distrib (rather than _apps), if that's what we're also packaging up into Docker images — the user should get the same set of software, regardless of which installation method they prefer.

      The likely solution is to delete this page, since we seem to finally be converging on lsst_distrib as the default top-level package (it used to be split between lsst_apps and lsst_distrib). Some thought will have to go into topics that needed to link to this one.

        Attachments

          Activity

          Hide
          kherner Kenneth Herner added a comment -

          Is it a fair statement to say we have consensus to narrow the scope of work for this particular ticket to 1) remove the detailed package list, 2) put lsst_distrib first and cast lsst_apps as a way to get only the essentials for those on a storage budget? If so I can finish that up this week.

          Show
          kherner Kenneth Herner added a comment - Is it a fair statement to say we have consensus to narrow the scope of work for this particular ticket to 1) remove the detailed package list, 2) put lsst_distrib first and cast lsst_apps as a way to get only the essentials for those on a storage budget? If so I can finish that up this week.
          Hide
          jbosch Jim Bosch added a comment -

          Yup, that sounds like reasonable scope for this ticket to me.

          Show
          jbosch Jim Bosch added a comment - Yup, that sounds like reasonable scope for this ticket to me.
          Hide
          kherner Kenneth Herner added a comment -
          Show
          kherner Kenneth Herner added a comment - All done; Jenkins run was clean: https://ci.lsst.codes/blue/organizations/jenkins/sqre%2Finfra%2Fdocumenteer/detail/documenteer/2112/pipeline Anybody up for a quick review?
          Hide
          kherner Kenneth Herner added a comment -

          Jim Bosch JIRA doesn't seem to be picking up the PR so here's a link: https://github.com/lsst/pipelines_lsst_io/pull/254

          Show
          kherner Kenneth Herner added a comment - Jim Bosch JIRA doesn't seem to be picking up the PR so here's a link: https://github.com/lsst/pipelines_lsst_io/pull/254
          Hide
          jbosch Jim Bosch added a comment -

          I think we can go a bit further in downplaying lsst_apps (see PR), otherwise looks good.

          Show
          jbosch Jim Bosch added a comment - I think we can go a bit further in downplaying lsst_apps (see PR), otherwise looks good.

            People

            Assignee:
            kherner Kenneth Herner
            Reporter:
            jsick Jonathan Sick
            Reviewers:
            Jim Bosch
            Watchers:
            Jim Bosch, John Swinbank, Jonathan Sick, Kenneth Herner, Kian-Tat Lim, Lee Kelvin, Tim Jenness, Yusra AlSayyad
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Jenkins

                No builds found.