Skip to content

Commit fe027ce

Browse files
lwasserkierisi
andcommitted
fix(edits): review by @kierSi
Co-authored-by: Jesse Mostipak <[email protected]>
1 parent 409fd5f commit fe027ce

File tree

1 file changed

+17
-18
lines changed

1 file changed

+17
-18
lines changed

_posts/2024-07-22-pyopensci-at-scipy-2024.md

Lines changed: 17 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -19,11 +19,11 @@ comments: true
1919
<div class="notice" markdown = "1">
2020
## TL;DR
2121

22-
* pyOpenSci lead 3 incredibly successful events at SciPy this year: A tutorial,
23-
a talk and a 1.5 day sprint
22+
* pyOpenSci lea 3 incredibly successful events at [SciPy](https://www.scipy2024.scipy.org/ this year: A tutorial,
23+
a talk and a 1.5 day sprint.
2424
* During our SciPy 2024 meeting sprint we had over 35 GitHub issues and pull requests submitted by XX new contributors.
25-
* Our tutorial had 40 registrations and ~30 people showed up. Almost all learners had never created a Python package before and almost all learners were successful creating their first Python package.
26-
* I thoroughly enjoyed connect with new and old colleagues and friends.
25+
* Our tutorial had over 30 attendees. Almost all of the learners had never created a Python package before, and most of them were successful creating their first Python package.
26+
* I thoroughly enjoyed connecting with new and old colleagues and friends.
2727

2828
</div>
2929

@@ -32,34 +32,33 @@ a talk and a 1.5 day sprint
3232
This year was my fourth time attending the annual SciPy meeting—a meeting
3333
organized by [NumFocus](https://www.numfocus.org) that celebrates the scientific
3434
Python ecosystem. My first experience was in 2019, where we held the very first
35-
pyOpenSci BoF (Birds of a Feather) session.
35+
pyOpenSci Birds of a Feather (BoF) session.
3636

3737
A Birds of a Feather session, also known as a BoF, is a community-organized
38-
event where people lead a discussion around a specific topic. Our BoF was about
38+
event where people lead a discussion around a specific topic. Our 2019 SciPy BoF was about
3939
our peer review process, which we had just launched that year.
4040
{: .notice }
4141

42-
In previous years, pyOpenSci was less known in the community. This year, however,
43-
was different. There were many familiar faces, including:
42+
One of the biggest differences this year has been how much pyOpenSci has grown, which means we saw many familiar faces, including:
4443

4544
* Maintainers of packages that we have reviewed and accepted through our
46-
[scientific Python software peer review process](/about-peer-review/index.html)
47-
* Colleagues who I have met at other meetings such as PyCon,
45+
[scientific Python software peer review process](/about-peer-review/index.html),
46+
* Colleagues who I have met at other meetings, such as [PyCon](https://pycon.org/),
4847
* Reviewers and editors from our community,
4948
* Members of our advisory council, contributors, and
5049
* Friends—so many friends.
5150

52-
This year, I was busy as SciPy:
51+
This year, I was busy at SciPy, and spent my days:
5352

54-
1. Running an in-person tutorial: Create Your First Python Package.
55-
2. Giving a talk in the Maintainers Track (what an honor!).
53+
1. Running an in-person tutorial: [Create Your First Python Package](https://cfp.scipy.org/2024/talk/QT9GBY/).
54+
2. Giving a talk, [The power of community in solving scientific Python’s most challenging problems](https://cfp.scipy.org/2024/talk/AMTLJ7/), in the Maintainers Track (what an honor!).
5655
3. Working the hallway track.
5756
4. Running a 1.5-day sprint that resulted in over 35 issues and pull requests.
5857
Wow.
5958

6059
Admittedly, I started off this conference behind and frazzled. You see, pyOpenSci
6160
has been growing in recent months. With that growth comes more wonderful people
62-
to support and engage with. More people getting involved does mean more work for
61+
to support and engage with, which is wonderful! But more people getting involved does mean more work for
6362
pyOpenSci. However, the time is worth it, as all of this effort is moving
6463
pyOpenSci's mission of supporting open science forward.
6564

@@ -78,15 +77,15 @@ More on all of that below. But first--what is the SciPy Conference?
7877

7978
If you haven't attended this meeting before, let me give you the rundown. The
8079
SciPy Conference is an annual event dedicated to celebrating and learning more
81-
about scientific computing using the Python programming language. The meeting
80+
about scientific computing, all using the Python programming language. The meeting
8281
started back in [~2002](https://web.archive.org/web/20021030003450/http://www.scipy.org/site_content/scipy02/). The early meetings were run by EnThought and
8382
were smaller in size and scope. Over the years, SciPy has evolved significantly,
8483
mirroring the [🚀 explosive growth of the Python ecosystem 🚀](https://stackoverflow.blog/2023/01/26/comparing-tag-trends-with-our-most-loved-programming-languages/)
8584
in scientific computing and data science.
8685

87-
Today, the SciPy Conference, hosted by [NumFocus](https://numfocus.org/),
86+
Today the SciPy Conference, hosted by [NumFocus](https://numfocus.org/),
8887
attracts over 700 attendees from diverse scientific fields such as astronomy,
89-
biology, geophysics, and more. SciPy is much more than just a workshop.
88+
biology, geophysics, and more. SciPy is much more than just a meeting.
9089

9190
SciPy features:
9291

@@ -95,7 +94,7 @@ SciPy features:
9594
* Talks from the community about tools and approaches.
9695
* Poster sessions that allow presenters to directly engage and discuss cool
9796
work with the meeting attendees.
98-
* Tutorials led by community members (and pyOpenSci) that cover important
97+
* Tutorials led by community members (including pyOpenSci) that cover important
9998
scientific data processing and analysis-related Python skills.
10099
* Sprints: collaborative coding sessions where people come to contribute to
101100
and learn about open-source projects.

0 commit comments

Comments
 (0)