[x] Timeout after a few idle hours/minutes: S4L state is auto(saved) after X minutes of idling in a temporary file. Then there is 5 Minute warning popup. Then it closes automatically @odeimaiz https://github.com/ITISFoundation/osparc-simcore/pull/3544
[ ] Service startup: show progress @sanderegg @GitHK (or change the wording) NK says we need to make the startup of s4l-light faster. The progress bar needs to be more verbose and nicer. It should 'flood' the user with more information about the state so it seems like the webpage is "responsive"
[ ] Make sure invitation (oetikers) is sent email from zmt.swiss
[ ] For JupyterNotebooks, they currently open in a second tab with the current UUID-based domain-name-based traefik routing approach. We need to audit if this is viable from a security / scalability point-of-view. From a security point of view, maybe start creating auth. token. @GitHK
[ ] @odeimaiz Talk to Anja and NK about logos and branding
[x] Frontend: On landing-page: Remove osparc-simcore mentions and change itisfoundation to ZMT
[x] Frontend: Add cookie disclaimer to landing page
[x] Frontend: Add a link to S4L Forum page to GUI
[ ] Timeout without logout or study-closure (discuss this with s4l team) after idling for a few hours
[ ] Use the new messaging system to announce scheduled downtimes
[x] 2FA is set up
[ ] NK says we need to make the startup of s4l-light faster. The progress bar needs to be more verbose and nicer. It should 'flood' the user with more information about the state so it seems like the webpage is "responsive"
[ ] Distinguishable pictures (thumbnails) for the tutorials are needed.
[ ] A "first usage" Tutorial or Movie like in tip.itis.swiss is needed
[x] We restrict s4l-web-light-product users to open only one study. This should be handled by the oSparc backend.
[ ] The Issues/Feedback Button will trigger a email popup to sim4life support (possibly including user_id, project_uuid, ... at our discretion)
To be discussed / decided
[ ] NK: "We shall disable accounts after half a year of users not using them" --> What does this mean technically, when is an account considered unused? Will we disable them manually from time to time or have a (semi)automatic procedure?
[ ] Where should the documentation live? --> The manual will likely live in github... Erdem will talk with @mguidon about this separately
[ ] Question by EO: Is the 'one-project == one-file' agreed upon? --> It is not yet clear, there are various pros/cons. This needs to be decided
[ ] For s4l-web-light JupyterNotebooks, they currently open in a second tab with the current UUID-based domain-name-based traefik routing approach. We need to audit if this is viable from a security / scalability point-of-view. A possible blocker could be is s4l-light lives under a zmt.swiss subdomain, such as s4l.zmt.swiss/light.
Not fully committed to these features yet:
[ ] Registration via a zmt.swiss form, possibly automated sign-up link generation via black/white list?
[ ] Service startup: show progress @sanderegg @GitHK (or change the wording) NK says we need to make the startup of s4l-light faster. The progress bar needs to be more verbose and nicer. It should 'flood' the user with more information about the state so it seems like the webpage is "responsive"
[ ] For s4l-web-light JupyterNotebooks, they currently open in a second tab with the current UUID-based domain-name-based traefik routing approach. We need to audit if this is viable from a security / scalability point-of-view. From a security point of view, maybe start creating auth. token.
Requires backend/devops