Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: Stack Documentation and UX
-
Labels:
-
Story Points:2
-
Epic Link:
-
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.
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.