Details
-
Type:
RFC
-
Status: Implemented
-
Resolution: Done
-
Component/s: DM
-
Labels:None
Description
This is an RFC of a plan to resolve the incongruity between (1) the git package/class name for the jupyter-lab based service called jupyterlabdemo (2) the deployment of same on GKE (3) the informal name within DM of the Notebook Aspect of the Science Platform which is jellybean [from JupyterLab-Based Environment for Analysis Notebooks]
There was an initial proposal for the team to unify all of the above using what was the unofficial designation (jellybean) but there was a concern expressed from DM leadership that this lacked the necessary gravitas.
A number of alternatives were proposed to the DMLT, and after a straw poll the popular choice is nublado. Nublado stands for *N*otebooks for *U*ser *B*ased *L*SST *A*nalysis and *D*ata *O*perations. It means cloudy in Spanish, and is an oblique reference both to its cloud-based deployment architecture and the well-observed tendency for astronomers to do more analysis when it's cloudy. It also has the advantage that it is consistent with the eventual public URL for the notebook service designated by the LSP Product Owner {science platform URL}/nb.
Please note that this renaming does not constrain the public-facing URL for operational-era services, nor any future decisions on re-branding the LSST Science Platform or any of its components. It is intended as the name of the software packages /service underwriting the Notebook Aspect of the LSST Science Platform.
As with all naming RFCs, please keep in mind there is no solution that will satisfy everyone. We are particularly soliciting comments if:
- You are affected by the renaming of the jupyterlabdemo repo/classes or its GKE-based test deployment and need to negotiate timing
- You have reason to believe the name is offensive or has other problematic connotations that the proposers may not be aware of.
We ask that people refrain from "I just don't like it / I have a better idea" type comments as all that will result in is DM-CCB escalation.
Attachments
Issue Links
Activity
I agree with point number 2 in Nate's comment above (I believe I am the Spanish speaking colleague he is referring to). When I heard "nublado" for the first time, it made me think right away of something with a negative connotation. However, this might fall into the category "I don't like it", which is precisely the type of comments that the instructions of this RFC request to avoid.
Notey McNoteface?
Thanks to all for the comments (and the restraint!). I am adopting this RFC.
I understand the concern that cloudy is not the world's most exciting sentiment but given it is unlikely that this will have any real world repercussions, I think we can put that aside. If it's any consolation, I would have been okay with "muddy" "grim" "bogus" and any other non-glossy sentiment given it's just a back-end name. 
Seems we are ok (this was not flagged in any case)
"Nublado" may not be perfect, but:
1) it's a lot better than "jupyterlabdemo" since it a) does not enshrine a particular technology likely to be replaced by the end of operations, and b) even our current environment is clearly no longer just a demo.
2) It makes sense with the route `/nb` (which was initially for "notebook", but which involves the configurable proxy, the Hub, and the JWT authenticator as well as the notebook environment (which is currently "JupyterLab" rather than the classic Notebook).