05 Call Digest [ 2022-noaa-sefsc-summer ]

[stefaniebutland]

Hello @Openscapes/2022-noaa-sefsc-summer-cohort!

Thank you all for our fifth (final!) session last Thursday. This was a really special cohort, our first with so many supervisors and IT included and it was really inspiring to hear your shared progress forward for more open and inclusive data science within and across your teams. Thank you for sharing so much with your colleagues, as well as your needs and ideas for SEFSC leadership. Openscapes would also love your feedback so we can improve future cohorts - including the upcoming fall NMFS cohorts; please fill out this survey by Sept 8.

We hope you can carry the inspiration forward with our rockin' Openscapes Spotify Playlist - updated with SEFSC’s tunes!

Many of you expressed interest in continuing communication and meetings among SEFSC Openscapes Champions and the ongoing Surf Sessions are a great way to do this. The next one is Friday, September 2 · 2:00 – 3:00pm: meet.google.com/ukh-qwnw-wxq. Details came in email from Ady.

We look forward to watching you advance on your journeys! We’ve got several ways to stay in touch. If you can make it, please join us for a ~3 month check in on Thursday, December 1, 2:00 - 3:00 ET so we can see what everyone is up to. We'll send a calendar invite :) Our SEFSC Openscapes Community Google Space will remain, and you’re welcome to also join Openscapes Slack (if you haven’t already) where your colleagues across NMFS and other Openscapes Champions are.

Please have someone from each team please email/direct message Julie a physical address where we can send stickers via postal service! We'll ask that you distribute them within your team.

Below is a light digest of Call 05.

Stef, Julie, Ady, Molly

Digest: Cohort Call 05 [ 2022-noaa-sefsc-summer ]

CohortCalls folder - contains video recordings and completed agendas

Cohort webpage - contains all of the digests and links to materials used during the workshop

Goals: ‎Each team shared their Pathways and we discussed next steps going forward.

Teams' Pathways are located in this PathwayShare Folder.

Here is one example screenshot from the The SFD Assessment Workflow Team showing how they use GitHub for both an outward facing page and internal issue / progress tracking 😍 :

A second example: the IEA team shares how their reports are currently made, how they envision making this process better, and challenges to overcome

Resources - NMFS Open Science and R learning community

The nmfs-openscapes users group is an informal meeting space for any open science users from across NMFS! Many are focused on automating reports. You are welcome here.

• NMFS Open Science: https://nmfs-opensci.github.io/ResourceBook/
• NMFS Openscapes: https://nmfs-openscapes.github.io,
• NMFS R Users Group: https://nmfs-opensci.github.io/NMFS-R-UG/: Platform/org for communication and place for shared tutorial repos, resources.
  • NMFS R UG Calendar - to add the group calendar to your personal work calendar.
  • Video recordings of past meetings
  • Meeting notes
  • JOIN the google space and github groups! (You REALLY are welcome here!)
• NMFS-level RStudio Connect

A few lines from shared notes in the Agenda doc:

• Developing good habits so that these practices become second nature
• ‎”Automation and increasing efficiency of support for stock assessments + documentation for onboarding”
• Following standard labeling, file structure, and shared storage practices to make life easy for future us/others
• Leaning on experience from other groups to quickly adopt effective practices
• “My pathway document looks like everyone else’s - and that’s one of the takeaways. We’re all rowing the boat forward”; I don't’ feel alone and running against the current anymore
• whether or not GitHub, I have a way to think and organize and share my todos and work, so I hope whether we use GitHub at enterprise/personal shouldn’t stop us!
• We use GitHub for methods/product internal/external project management/version control +1: so important to communicate that.

Upon completing Openscapes, how do you feel about your needs and how you are supported to meet those needs?

• Having everyone working together across groups/branches is very encouraging and has also increased collaboration between groups. +4
• I feel a bit better about asking for time to learn new skills, and I am very grateful to have a community to reach out to for recommendations +3
• I’m excited to see different groups all working in the same direction - we really need all parts of the chain to have similar goals for this to work and it seems like we do! +1+1+1
• Direct supervisors are recognizing the value of github/rmarkdown/etc. which is very encouraging because part of this process will require to spend more time at the front end learning/building (but ultimately will be a huge time saver at the back end and once workflows are set up) +1
• Openscapes has really given us GitHub Momentum, when I am working now I want my code to be “built to last” and I want it to be useful to others even if they are working on something different (I have learned so much from other repositories that I want mine to also help do good contribute to our openness!) +1

Upon completing Openscapes, what are your ideas and needs for your team’s future progress?

• Maintain momentum by continuing to have regular meetings focused on this topic +4
  • Maintain momentum with co-working hours. +2
  • Continue meeting regularly to exchange ideas and share roadblocks so we are all working efficiently and learning from one another
  • Our seaside chats have been great for getting us to think big picture and discuss problems more collaboratively. We are hoping to keep that momentum going post openscapes.
• Time to actually pull this into existing workflows is critical.
• In order to reach our goals we need strategic support from leadership to allow more time to incorporate existing workflows with future states. This will require increased time on the front end (extended deadlines for SEDAR products until personnel are “GitHub ready”

Thank you so much! Please reuse/remix resources and stay in touch

• We’re learning how to continue to support teams and help strengthen our community and the open science movement after the Cohort ends

  • github.com/Openscapes - pinned repositories
  • openscapes.github.io/series - continually improved lessons
  • openscapes.org/blog - guest posts welcome!
  • openscapes.org/events - Champions Cohorts, Community Calls, talks
  • Twitter @openscapes - please tag us and we’ll retweet!
  • Slack - now with “events” and “jobs” channels
  • Newsletter ~5x/year

[mollystevens-noaa]

Been working this morning to our Openscapes Community playlist, and I am loving the variety & motivation! Thanks for leading a great cohort @jules32 , @stefaniebutland , @eeholmes , and @AdyanRios-NOAA !!