New Blog: adventures at Scipy 2023

_posts/2023-07-18-pyopensci-scipy-2023.md

@@ -0,0 +1,224 @@
+---
+layout: single
+title: "Shark Attacks and Open Science - pyOpenSci @ SciPy 2023 Meeting"
+excerpt: "The SciPy 2023 meeting did not disappoint this year. We have a whole new group of contributors helping to build this vibrant and diverse Python open science community. Learn about my experience there."
+author: "Leah Wasser"
+permalink: /blog/scipy-2023-community.html
+header:
+  overlay_color: "#542668"
+  overlay_filter: 0.6
+categories:
+  - blog-post
+  - highlight
+  - community
+  - talks
+classes: wide
+toc: false
+comments: true
+---
+
+## <i class="fa-solid fa-fish-fins"></i> Shark attack - pyOpenSci at SciPy
+
+I was so excited for SciPy this year.
+
+I wanted to spread the word about pyOpenSci's core mission - supporting
+the scientific open source Python community. I wanted to get more people
+involved.
+
+pyOpenSci represents everything that matters most to me:
+
+- 🌱 Community & People
+- 🎓 Education
+- 🔓 Open Science and Open Source
+- 🌈 Diversity, Equity and Inclusion
+
+## Unplanned is often best
+
+I am not used to going into a meeting with no specific plans and obligations.
+While pyOpenSci didn't get a talk or a community session / BoF this year, we
+did get a lightning talk! It was a randomized selection, and I threw my name
+into the bucket (literally) with fingers crossed that i'd get a lightning talk.
+
+And on the final day of the meeting, I was selected to present!
+
+<blockquote class="twitter-tweet"><p lang="en" dir="ltr"><a href="https://twitter.com/pyOpenSci?ref_src=twsrc%5Etfw">@pyOpenSci</a> got the cutest slides at the lighting talk @SciPyCon <a href="https://twitter.com/hashtag/SciPy2023?src=hash&amp;ref_src=twsrc%5Etfw">#SciPy2023</a> <a href="https://t.co/ZXleLpdkqB">pic.twitter.com/ZXleLpdkqB</a></p>&mdash; Cheuk Ting Ho (@cheukting_ho) <a href="https://twitter.com/cheukting_ho/status/1679962465508147200?ref_src=twsrc%5Etfw">July 14, 2023</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
+
+## The shark attack - my lightning talk about pyOpenSci
+
+Let me give you the backstory on lightning talks at SciPy. It's known that
+moderators will often "play" with those presenting.
+
+Puns are always pervasive and community embraced!
+
+This year there was a "sea" theme featuring sharks and crab claws. 😂 Watch
+below as the session is started with a crab claw pun by Paul followed up with
+a shark attack on yours truly from [Madicken](https://github.com/munkm/). You will also learn about the
+pyOpenSci mission and vision.
+
+<iframe width="560" height="315" src="https://www.youtube-nocookie.com/embed/vJpH-ctvPoU" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen></iframe>
+
+## Sprints - my new favorite part of every meeting
+
+A sprint, in the tech world, is a short time period where people on a team work
+together to complete something on a technical project. At conferences, there are
+often open sprints. The idea here is that people, often some of whom are new
+to a project, get together in person and work on things that the project needs.
+
+### Mentored sprints make open source more inclusive
+
+In our open source world we also have [mentored sprints](https://www.mentored-sprints.dev/).
+The term mentored sprints was coined by an [amazing team of people](https://www.mentored-sprints.dev/team/) including [Tania Allard (who's passion for open source and open data resonates with my own)](https://www.trallard.dev/).
+It focuses on supporting those who are new to sprinting and using platforms such as
+GitHub in making their first contribution to open source.
+
+Given pyOpenSci's core values around diversity equity and inclusion, every
+sprint we hold is a mentored sprint as far as i'm concerned!
+
+This was the second sprint that i've lead with the [first being at pyCon US 2023](https://www.pyopensci.org/blog/pycon-2023-packaging-presentation-sprints-leah-wasser.html).
+
+### An organized list of tasks is key for any sprint
+
+My friend, colleague and [esteemed pyOpenSci advisory council member,](https://www.pyopensci.org/our-community/index.html#pyopensci-advisory-council) [Inessa Pawson](https://github.com/InessaPawson) taught me
+that:
+
+1. It's best to go into a sprint with an organized set of help-wanted issues.
+1. Identifying issues that could be completed in a few hours to a day is ideal.
+1. And tagging issues as beginner friendly helps those who are newer to sprints
+
+<figure>
+    <a href="/images/github/pyopensci-github-help-board.png">
+    <img src="/images/github/pyopensci-github-help-board.png" style="max-width:100%" alt="An image with a black background showing all of the issues that we could use help with at pyOpenSci. The caption for this image contains a link to the board which will allow you to hear and read through each issue listed on the board.">
+    </a>
+    <figcaption>Our pyOpenSci help-wanted issue board has a list of things that we could use help with. Issues that could be done during a sprint are tagged "sprintable". Issues that are ideal for beginners are also tagged - beginner friendly. <a href = "https://github.com/orgs/pyOpenSci/projects/3">View the board here.</a>
+    </figcaption>
+</figure>
+
+I went into our SciPy 2023 sprint with a [more organized pyOpenSci help-wanted board.](https://github.com/orgs/pyOpenSci/projects/3)
+This board has been a great way to keep track of things
+that we need help with.
+
+**<i class="fa-solid fa-circle-info"></i> GitHub PROTIP:** I struggled at PyCon with assigning people who didn't belong
+to a repository or our organization to specific issues. Now, I know that
+if someone comments on an issue first, I can then assign it to them
+(many thanks to [Thomas Fan](https://github.com/thomasjpfan) for the tip!!).
+{: .notice .info}
+
+## So many helpful contributions to pyOpenSci!
+
+I am absolutely blown away by and profoundly grateful for the
+support that pyOpenSci received at this year's SciPy sprints!
+
+We had over 20 pull requests emerge from this sprint - WOW! Two sprinters also
+submitted their first ever contributions!!
+
+**<i class="fa-solid fa-circle-info"></i> Info:** a pull request, known as a "pr", represents a set of suggested changes to a set of code or text. In the GitHub.com interface you can view the suggested changes and comment on them - in the same way that you might comment on suggested changes in a Google doc.
+{: .notice }
+
+Some of the contributions included:
+
+- Updating our website workflow to allow for site preview on every pr. This means that no one needs to setup a ruby environment locally in order to view website changes. And the less ruby environments contributors need to deal with, the better as far as I am concerned :) !!
+- Updating and enhancing our contributor package metadata workflow to be more efficient and effective
+- _A first contribution ever!!_ Grace helped us by fixing typos in our throughout our peer review guide! She called these fixes trivial but there is NO SUCH THING as a trivial pull request. We need fresh sets of eyes on all of our guides and appreciate any and all fixes that pr's bring big or small!
+
+In case you are curious, most of the pull requests submitted during the sprint this year are listed below:
+
+<div class="notice" markdown="1">
+## Pull requests submitted to pyOpenSci the 2023 SciPy sprints
+- **Thomas:** Thomas submitted a [set of pr's that allow us to preview our website after every pull request](https://github.com/pyOpenSci/pyopensci.github.io/pulls/thomasjpfan) is submitted.
+- **Mike:** Mike tackled our automated workflow that tracks contributors across our GitHub repositories and also that tracks packages, reviewers and editors in our review process.
+- **ruoxi** Ruoxi submitted an issue surrounding a rendering issue with our packaging guide in the Safari browser. And also a [pull request updating text around our partnership](https://github.com/pyOpenSci/software-peer-review/pull/232/files) with the Journal of Open Source Software (JOSS) where they accept our review as theirs and only review your paper.
+- **Grace:** [Grace made her first, second, third ...seventh!! pull requests ever fixing typos in our peer review guide](https://github.com/pyOpenSci/software-peer-review/pulls/g-patlewicz)
+- **Ricky:** [Url redirect fixes on website](https://github.com/pyOpenSci/pyopensci.github.io/pull/235)
+- **Kerry:** [Fixed the packages order so that newest was at the top of the page not the bottom](https://github.com/pyOpenSci/pyopensci.github.io/pull/234)
+
+</div>
+
+### People kept sprinting without me!
+
+I left before day two of the sprints. However, that did not stop
+the community from continuing to sprint and contribute to
+pyOpenSci! People continued to work additional
+website fixes that were still open our project board.
+
+### Lessons learned from SciPy 2023
+
+I learned a lot this year from SciPy.
+
+Sometimes the best moments are the unexpected ones. I had the
+chance to connect with amazing individuals and share pyOpenSci's
+impactful mission that I care about so deeply.
+
+And the best part? Our pyOpenSci community continues to grow, attracting more
+wonderful Pythonistas who share our vision. Together, I'm confident that we
+will make a positive impact on scientific open source Python community.
+
+That's what truly matters.
+
+And I gave out a lot of pyOpenSci stickers too!
+
+<figure>
+    <a href="/images/pyopensci-stickers.png">
+    <img src="/images/pyopensci-stickers.png" style="max-width:100%" alt="Two pyOpenSci sticker designs. the one is a light purple flower with white stamen and the letters pr and O as the center of the sticker. The S is a snake. The econd sticker is a darker and lighter purpler that says pyOPenSci and has the top half of a flower above the O in open.">
+    </a>
+    <figcaption>Fresh off the press - pyOpenSci stickers!
+    </figcaption>
+</figure>
+
+## For all of you introverts - a few tips that helped me this year
+
+My approach to participating in SciPy was so much better than that at pyCon.
+
+I learned some valuable lessons about taking care of
+both my work and my mental well-being. As an introvert in a busy meeting filled
+with awesome colleagues, it's easy to get burnt out.
+
+Here's what I did to make sure I left the meeting feeling refreshed and energized:
+
+- 🌟 I prioritized mental health: It's all about balance. I put as much effort into taking care of myself as I did into my work during the meeting.
+- 🌟 Embraced breaks: During the meeting, I consciously took short breaks to unwind. Whether it was chilling in my hotel room or going for a stroll outside, giving my brain a breather made a world of difference. And guess what? I slept better at night too!
+
+* 🌟 Me time matters: While I didn't participate in every social activity, I didn't feel like I was missing out. Instead, I used that time to recharge solo and get some extra sleep. And let me tell you, it worked wonders!
+* 🌟 Balanced work and recovery: To avoid getting run down, I allowed myself to miss the second day of the sprints. This allowed me to travel home on Sunday and recover in the afternoon with my furry friend, Juno.
+
+In the end, I may have missed a bit of the action, but the payoff was totally worth it. I left the meeting feeling way better than I did after PyCon.
+
+So, fellow introverts, remember this little secret weapon called
+"recovery time" at your next big event! It's a game-changer!
+
+## A personal note - flying solo in the open source world is never truly solo
+
+Back in March 2023, I made a bold decision to leave a toxic academic
+environment and fully dedicate myself to building and growing pyOpenSci—an
+amazing, community-focused organization.
+
+Let me tell you, taking that leap of faith was pretty intimidating. The academic
+setting had taken a toll on me, shattering my confidence and even affecting my
+health. But I knew in my heart that I wanted to channel all my energy into
+community work, collaborating with people who respected and appreciated me as
+much as I respected them.
+
+And guess what? This journey has been beyond my wildest dreams! Not only has
+the pyOpenSci community thrived and made a remarkable impact in just its first
+year, but it has also turned out to be the kind of inclusive, supportive
+community I always envisioned.
+
+It's incredible how not only is pyOpenSci helping others, but it's also been a
+source of support and healing for me. I couldn't be more grateful for this
+vibrant and uplifting environment that we've created together.
+
+I'll keep pushing forward, knowing that this beautiful journey is just the
+beginning.
+
+Thank you, SciPy for supporting me and reinforcing the fact that I made the right decision! And i'd be remiss if I didn't also thank the pyOpenSci community
+that is truly bring pyOpenSci's vision to life.
+
+## Wrapping up
+
+And that is all I have to say about SciPy 2023! It was an incredible experience.
+If you are reading this and we connected at SciPy this year or if you contributed
+to pyOpensci this year, I just want to say thank you.
+
+From the bottom of my heart. I see change coming in the upcoming years.
+pyOpenSci wants to be a part of and to drive that change!!
+
+We can't achieve that without your help!

_sass/minimal-mistakes/_base.scss

@@ -14,6 +14,7 @@ body {
   color: $text-color;
   font-family: $global-font-family;
   line-height: 1.5;
+  weight: $weight-3;
 
   &.overflow--hidden {
     /* when primary navigation is visible, the content in the background won't scroll */
@@ -31,6 +32,7 @@ h6 {
   line-height: 1.2;
   font-family: $header-font-family;
   font-weight: bold;
+  color: #542668
 }
 
 h1 {
@@ -44,6 +46,8 @@ h2 {
 
 h3 {
   font-size: $h-size-3;
+  //font-family: $sans-serif;
+  font-weight: $weight-4
 }
 
 h4 {

_sass/minimal-mistakes/_page.scss

@@ -84,13 +84,18 @@ body {
 
 .page__lead {
   font-family: $global-font-family;
-  font-size: $type-size-4;
+  font-size: $type-size-5;
+  font-weight: $weight-3;
 }
 
 .page__content {
+  p {
+    max-width: 900px;
+    font-weight: $weight-4;
+  }
   h2 {
-    padding-bottom: 0.5em;
-    border-bottom: 1px solid $border-color;
+    padding-bottom: 0.2em;
+    border-bottom: 3px solid $border-color;
   }
 
 	h1, h2, h3, h4, h5, h6 {

_sass/minimal-mistakes/_pyos-grid.scss

@@ -74,6 +74,9 @@
 }
 
 /* Package cards splash */
+.cards h2.archive__item-title {
+  font-size: 1.1em!important;
+}
 
 .cards {
     display: block;
@@ -90,7 +93,6 @@
     border: 1px solid #f2f8f9;
     font-size: .8em;
 
-
     &.highlight div {
       padding:0;
     }
@@ -106,6 +108,7 @@
         cursor:default;
       }
 
+
       .card-body {
         margin: .2em;
         padding: 1.2em;

_sass/minimal-mistakes/_pyos-main.scss

@@ -100,10 +100,6 @@ h2.clearall {
   font-size: .9em;
 }
 
-.page__lead {
-  font-size: 1em!important;
-}
-
 
 // /* */
 

_sass/minimal-mistakes/_variables.scss

@@ -6,6 +6,17 @@
    Typography
    ========================================================================== */
 
+/* font weights */
+$weight-1: 100;
+$thin-weight: 200;
+$weight-3: 300;
+$weight-4:   400;
+$weight-5:   500;
+$semibold-weight: 600;
+$bold-weight:     700;
+$xbold-weight:    800;
+$black-weight:    900;
+
 $doc-font-size: 15 !default;
 
 /* paragraph indention */
@@ -29,12 +40,14 @@ $bodoni: "Bodoni MT", serif !default;
 $calisto: "Calisto MT", serif !default;
 $garamond: Garamond, serif !default;
 
-$global-font-family: $sans-serif !default;
+$global-font-family: $sans-serif!default;
 $header-font-family: 'Itim', cursive, $sans-serif !default;
 $caption-font-family: $serif !default;
 $header-font: 'Itim', cursive;
 $body-font: 'Poppins', sans-serif!default;//'Open Sans', sans-serif;
 
+
+
 /* type scale */
 $type-size-1: 2.441em !default; // ~39.056px
 $type-size-2: 1.953em !default; // ~31.248px
@@ -47,8 +60,8 @@ $type-size-8: 0.625em !default; // ~10px
 
 /* headline scale */
 $h-size-1: 1.563em !default; // ~25.008px
-$h-size-2: 1.45em !default; // ~20px H2 tag increased to 1.45 (1.25 origin)
-$h-size-3: 1.125em !default; // ~18px
+$h-size-2: 1.85em !default; // ~20px H2 tag increased to 1.45 (1.25 origin)
+$h-size-3: 1.45em !default; // ~18px
 $h-size-4: 1.0625em !default; // ~17px
 $h-size-5: 1.03125em !default; // ~16.5px
 $h-size-6: 1em !default; // ~16px
@@ -61,7 +74,7 @@ $nav-hover-color: #8d0065;
 $background-block: #d6cfde;
 
 $gray: #24052f !default;
-$dark-gray: mix(#000, $gray, 50%) !default;
+$dark-gray: #4c454e !default;
 $darker-gray: mix(#000, $gray, 60%) !default;
 $light-gray: mix(#fff, $gray, 50%) !default;
 $lighter-gray: mix(#fff, $gray, 90%) !default;

_sass/minimal-mistakes/vendor/susy/susy/_syntax-helpers.scss

@@ -10,7 +10,7 @@
 /// and accessing the core math.
 ///
 /// This is the same technique we use internally,
-/// to keep our API layer simple and light-weight.
+/// to keep our API layer simple and weight-3.
 /// Every function accepts two arguments,
 /// a "shorthand" description of the span or context,
 /// and an optional settings-map to override global defaults.