Issue on E4S page: E4S Container Download - E4S Facility deployment container link #40
Description
Please describe the problem with this page:
https://E4S-Project.github.io/container-download/
From David Bernholdt:
Mike and team, I noticed that a link to OLCF on https://e4s.io/container-download/#e4s-facility-deployment is 404 and should probably be removed.
As you will know from our conversations with Fernando, OLCF does not deploy E4S is a separate entity, but incorporates software from E4S into its deployed software stack. Module listings and such are now annotated to indicate packages sourced from E4S, so this is definitely visible to users – in many ways more so than when you had to load a whole separate module to access any of it. I think, if we wanted information about E4S availability at OLCF to be available to users there, we could probably create a page that would talk about OLCF’s approach to E4S and perhaps provide suggestions for how users can (a) request additional E4S packages be installed, and/or (b) recommend how to build/install additional E4S packages for their own or their project’s use. Of course we’d want to consult with Fernando to make sure that the messages we’re sending are appropriate.
The OLCF docs site uses Sphinx and is managed through GitHub. It is easy to submit a PR against it, and anyone can do so. I’ve done it for other things and am willing to help in this case. Though I think we need others to engage on the content. Actually, I suppose we should run the whole idea by Fernando (and perhaps others) to make sure that it is okay with them before we start writing anything. The premise would be that a user has heard about E4S and wants to know how to access E4S software at OLCF, so we can tell them.