diff --git a/approach/tooling.md b/approach/tooling.md index 0c5073a..7b76a4f 100644 --- a/approach/tooling.md +++ b/approach/tooling.md @@ -232,7 +232,29 @@ The above will subscribe to "discussions" in addition to undesirable [default no ## YouTube -Openscapes has a [YouTube channel](https://www.youtube.com/@openscapes). To **make a Playlist**, login as Openscapes YouTube Manager. Click on any video to edit Video details. Under Playlists dropdown, you can choose New playlist, and/or select a checkbox to add the video to an existing Playlist. We can a custom image for a Playlist. Go to that Playlist \> hover over the image \> click the pencil icon to edit. Playlist image must be at lease 640 x 360 pixels. +Openscapes has a [YouTube channel](https://www.youtube.com/@openscapes). + +### Playlists + +To make a Playlist, login as Openscapes YouTube Manager. Click on any video to edit Video details. Under Playlists dropdown, you can choose New playlist, and/or select a checkbox to add the video to an existing Playlist. We can add a custom image for a Playlist. Go to that Playlist \> hover over the image \> click the pencil icon to edit. Playlist image must be at lease 640 x 360 pixels. + +### Upload a video + +- Check beginning and end of video to see if it needs to be trimmed. To edit a video, see [Quicktime video editing] +- Log in to YouTube as \@openscapes (not e.g. stefanie \@openscapes.org) +- Click Create in upper right corner -\> Upload video +- Drag and drop or select video +- Fill in title and description. Note can't hyperlink text in title or description; add url as text. Add links to relevant resources and credit the presenter and their organization. +- Choose a thumbnail - autogenerated usually works well +- Select playlist(s) (e.g. NOAA Fisheries Openscapes + NASA Openscapes) +- Click Next +- Video elements - generally no actions required here +- Click Next +- Initial check - Sometimes checks flag copyrighted songs. “Community Guidelines check” took a long time +- Click Next +- Choose visibility: public +- Click publish +- Copy YouTube link and share. ## Zenodo {#sec-zenodo} @@ -480,35 +502,27 @@ write_clip(champ_emails) ::: ::: {.callout collapse="true"} - ## Restart GitHub Actions or Netlify build/deploy preview -Sometimes a GitHub Actions workflow or Netlify Deploy preview process will stall -for an unknown reason, and you just need to restart it to give it a little nudge. +Sometimes a GitHub Actions workflow or Netlify Deploy preview process will stall for an unknown reason, and you just need to restart it to give it a little nudge. -If it is a GitHub Actions workflow you can go to the "Actions" tab, click on the -running/stalled workflow, and click "Cancel Workflow" and then "Re-run jobs". +If it is a GitHub Actions workflow you can go to the "Actions" tab, click on the running/stalled workflow, and click "Cancel Workflow" and then "Re-run jobs". -If it is a Netlify Deployment (or deploy preview), a -[similar workflow](https://docs.netlify.com/deploy/manage-deploys/manage-deploys-overview/) is -available by logging in to your Netlify account. +If it is a Netlify Deployment (or deploy preview), a [similar workflow](https://docs.netlify.com/deploy/manage-deploys/manage-deploys-overview/) is available by logging in to your Netlify account. -If you don't have access to those GUI tools (e.g., if you don't have login credentials), -you can push an _empty commit_ to the repo which should restart the stuck process. +If you don't have access to those GUI tools (e.g., if you don't have login credentials), you can push an *empty commit* to the repo which should restart the stuck process. The terminal command to create an empty commit is: -``` +``` git commit --allow-empty -m "commit message" ``` Where "commit message" could be something meaningful like: -``` +``` git commit --allow-empty -m "trigger netlify deploy preview" ``` -Then push to the repository (`git push` or with the RStudio/Positron/VSCode GUI) -and it should trigger a new build, but with no actual changes to the repo contents. - +Then push to the repository (`git push` or with the RStudio/Positron/VSCode GUI) and it should trigger a new build, but with no actual changes to the repo contents. :::