-
Notifications
You must be signed in to change notification settings - Fork 1
Fledging content #15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fledging content #15
Conversation
This comment was marked as duplicate.
This comment was marked as duplicate.
|
Note: Should add this link as a resource: https://developmentseed.org/scaling_science |
cboettig
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
a few thoughts but looks awesome!
fledging.qmd
Outdated
|
|
||
| Fledging is a goal of these JupyterHubs, so that users who have had success | ||
| and want to continue their adventures in cloud computing, have the knowledge | ||
| and resources to develop their own solutions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we might want a little intro contextualizing how we see and experience the challenge of fledging? As discussed in the slack, this is somewhat the inverse of how 'cloud' is often presented (where new users begin in laptop-based installations first and must then learn how (and when) to migrate those workflows to cloud. The idea of users who can run analyses on the cloud while actually not knowing how or even if they could run it on their own laptop can frankly be mind-blowing to a certain slice of even quite sophisticated computational users.
| of installing and configuring everything yourself. The images used in the | ||
| JupyterHubs can often be used locally using tools like Docker. See some | ||
| examples [here](https://pangeo-docker-images.readthedocs.io/en/latest/howto/launch.html#how-to-launch-jupyterlab-locally-with-one-of-these-images). | ||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know jupyterlite doesn't support all of our packages yet, but I think it's an intriguing option!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Definitely! I haven't followed its development closely, do you think it's worth mentioning here?
fledging.qmd
Outdated
|
|
||
| Fledging is a goal of these JupyterHubs, so that users who have had success | ||
| and want to continue their adventures in cloud computing, have the knowledge | ||
| and resources to develop their own solutions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think crediting the NASA Openscapes Mentors (although it says so on the home page so maybe redundant?) and saying this is a work-in-progress is important here too, I added a bit of text we could use
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @jules32 - sorry I didn't see where your suggested text is?
|
Hi @ateucher , I just added a comment up top and ready for you to take another pass with Carl's comments and then merge? We can share it with Mentors and folks from Tasha's cross-NASA Hub group too and see what they think. Tasha also asked the question at AGU: "what if users don't need to fledge?" I think that's a great question. And also helpful to describe what is involved for users is valuable in any case. |
Content taken and expanded from the AGU fledging poster, and conversations around that.
Deploy preview: https://deploy-preview-15--openscapes-cloud-preview.netlify.app/fledging