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

02 Call Digest [ 2022-noaa-sefsc-fall ] #29

Open
stefaniebutland opened this issue Oct 25, 2022 · 0 comments
Open

02 Call Digest [ 2022-noaa-sefsc-fall ] #29

stefaniebutland opened this issue Oct 25, 2022 · 0 comments
Labels

Comments

@stefaniebutland
Copy link
Member

stefaniebutland commented Oct 25, 2022

Hi @nmfs-openscapes/2022-noaa-sefsc-fall-cohort

Now that you’ve learned about GitHub Issues, we’ll be posting Cohort Call Digests here and not emailing them 😁. You can try clicking on the digest issue label; it will show only issues that have that label.

On top of practicing following so many windows - Zoom video and chat, Slides when we’re not screensharing, Google doc - there was a lot of content to absorb. Feel like you missed something in the live demos? The video of our Call is in our Google Cohort Folder.

It was wonderful to see folks going from “What if I want to …” to creating their first repo or from creating their GitHub account to making their first commit. Thank you for being willing to screenshare to allow others to learn along with you. Thank you to those who share their thoughts, clarifications, and questions to our collaborative Google doc during the Call. Finally, it makes us really happy to see people asking and responding to questions in Google Spaces and Slack! Vulnerability? Yes! Shame? No!

Wishing you a growth mindset 😉,

Stef, Ileana, Julie, Molly, Ady

Digest: Cohort Call 02 [ 2022-noaa-sefsc-fall ]

Cohort Google Drive folder - contains agendas, video recordings, slides, pathways folder

openscapes.github.io/2022-noaa-sefsc-fall - cohort webpage

Goals: We practiced GitHub hands-on for collaborative research through publication and project management, from the browser.

Task: Have a Seaside Chat about GitHub. Please see the Agenda doc (under Closing) for more details.

Slide Deck: GitHub Clinic: Contributing from the browser (slides)

Coworking and learning opportunities (optional)

This week, Tues Oct 25, we have SEFSC coworking 10:00 - 11:00 am PT / 1:00 - 2:30 ET, and during Themed Cross-Cohort Coworking 1:00 - 2:30 pm PT / 4:00 - 5:30 pm ET, Eli Holmes will lead a guided session to work on your Pathways “Next steps”--where you want to get to and what you can do to get you there. Eli will give a brief intro to the ideas around using short sets of tasks (can be accomplished in 2-3 weeks) to make headway on amorphous or overwhelming goals (aka agile methodologies). Changing individual or team workflows and learning new skills definitely falls into this category! You can review Eli's talks on Agile workflows from the summer if you like, but you don’t need to be familiar with the concepts. It’s pretty straight-forward and on Tuesday, we’ll be learning by working on our Pathways.

There’s going to be a chunk of time (~40mins) for you to work on next steps for your Pathway. It’s totally ok to use this as your Seaside Chat time.

A few lines from shared notes in the Agenda doc, excerpted from all 4 NMFS Cohorts:

  • Our group talked about labels vs. milestones, and assignees (to add folks to the issue) vs. the @ tool within a specific comment to flag the comment to a particular person within the issue subgroup.
  • What if I want to do work outside of nmfs-openscapes?
    • Create a new repository in your personal or NOAA account
  • Thoughts on collaborating on writing projects on GitHub vs Google docs or Word
    • Google doc is great for fast progress - lots of people working nearly simultaneously
    • Depends on how complicated your manuscript is. Get to a point where [you’re] happy with it, then move to Google doc to get input from folks who don’t use GitHub.
    • Reports = R Markdown or Quarto; Live writing together (coworking) = Google doc
  • Is there a file size limit for GitHub?
    • See About large files on GitHub
    • ~50 mb will generate a warning, 100 mb hard stop, adding files via the browser are limited to 25 mb; But, there are options for sharing large files via releases or Git LFS
    • For general best practices, Megsie Siple recommends avoiding putting bulky data files etc on GitHub (store on Google Drive and link to GitHub)
  • Using Branches on GitHub
  • Can Rmarkdown be linked to Endnote for inserting citations into a document?
    • You can’t directly add a citation from Endnote to an Rmarkdown document. You need to export your endnote library as a bibtex file first. You can add citations with Rmarkdown using the {bookdown} package, and others. Quarto allows you to directly add citations from a Zotero library.

Bonus post-Call resource!

Eli Holmes (NWFSC) shared 3 GitHub template repositories!

How templates work: Click the green "Use This Template" button to make a copy of the repo with all the files. Then follow the instructions in the readme.

Try it without any set-up! There is a RStudio Cloud project set up for the Quarto and Distill templates. Click the button and it is all set-up for you to add content and try building the website.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant