Skip to content
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

Write lesson and episode objectives. #11

Merged
merged 2 commits into from
Feb 1, 2024
Merged

Write lesson and episode objectives. #11

merged 2 commits into from
Feb 1, 2024

Conversation

jnywong
Copy link
Member

@jnywong jnywong commented Jan 30, 2024

First draft defining lesson and episode level objectives for the hub champion training.

@jnywong jnywong self-assigned this Jan 30, 2024
Copy link

github-actions bot commented Jan 30, 2024

Thank you!

Thank you for your pull request 😃

🤖 This automated message can help you check the rendered files in your submission for clarity. If you have any questions, please feel free to open an issue in {sandpaper}.

If you have files that automatically render output (e.g. R Markdown), then you should check for the following:

  • 🎯 correct output
  • 🖼️ correct figures
  • ❓ new warnings
  • ‼️ new errors

Rendered Changes

🔍 Inspect the changes: https://github.com/czi-catalystproject/hub-champion-training/compare/md-outputs..md-outputs-PR-11

The following changes were observed in the rendered markdown documents:


What does this mean?

If you have source files that require output and figures to be generated (e.g. R Markdown), then it is important to make sure the generated figures and output are reproducible.

This output provides a way for you to inspect the output in a diff-friendly manner so that it's easy to see the changes that occur due to new software versions or randomisation.

⏱️ Updated at 2024-02-01 09:17:13 +0000

@jnywong
Copy link
Member Author

jnywong commented Jan 30, 2024

Hi @jmunroe ! Can I get some feedback whether the proposed lesson and episode objectives are appropriate? I am wary of straying into topics that may be "too advanced", so it would be useful to call upon your experience with 2i2c communities here to help sharpen my focus.

Copy link
Contributor

@jmunroe jmunroe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this captures what we discussed in lesson development course. Please merge it.

README.md Outdated Show resolved Hide resolved
README.md Outdated
1. Applying software environments
- explain the value of reproducibility with containerized software environments
- select a pre-configured image container for your hub
- pull a custom container to your hub
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The pre-configured environments are likely Jupyter and RStudio. I can think of nice exercise by having learners launch an already configured and available 'Linux Desktop Environment' to demonstrate the versatility available here.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks like we are agreed that 'customizing' your own hub image is out-of-scope for this particular training. We can make that explicit and direct hub champions to refer to our our service documentation.

We'll need to consult with others at 2i2c to determine how important 'customizing' images really is for communities.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps "pull a custom container to your hub" could be interpreted broadly. My intention here was to narrow the focus and walk through hub champions how to use the "Other" profile option to copy and paste in a publicly available image tag from https://quay.io/organization/2i2c

README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
github-actions bot pushed a commit that referenced this pull request Feb 1, 2024
@jnywong jnywong merged commit 2ab197b into main Feb 1, 2024
3 checks passed
@jnywong jnywong deleted the objectives branch February 2, 2024 09:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment