feat(blog): scipy24 recap blogpost with pictures #448

lwasser · 2024-07-25T22:15:28Z

This is a long one. opening as a draft for now in favor of finishing the sprint one first (which this one needs to link to)

To see the specific tasks where the Asana app for GitHub is being used, see below:
- https://app.asana.com/0/0/1207946917241899

kierisi

reviewed! let me know what questions you have.

kierisi · 2024-08-01T15:43:40Z

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

@@ -0,0 +1,463 @@
+---
+layout: single
+title: "pyOpenSci a Recap of @ SciPy 2024 Meeting - Tacoma, Washington"


Suggested change

title: "pyOpenSci a Recap of @ SciPy 2024 Meeting - Tacoma, Washington"

title: "pyOpenSci a Recap of @ SciPy 2024 Meeting - Tacoma, Washington"

I think we can punch this up a bit to be more clear. maybe something like "pyOpenSci at SciPy 2024: a recap of our time in Tacoma"

awesome. @kierisi just a note that here you have a suggested change but the actual change is in the comment text so i can't actually "accept" the change and give you credit for it . Would you like to make the change inline so i can commit it (and the commit then is in your name! so your work gets credit). i can also modify locally - up to you!

nope! I didn't want to assume what the title should be, so feel free to use whatever works best for you :)

Ok got it. I suggest that you play with the how comments work and what they look like on GitHub.

This is what i see which suggests you were trying to edit the text inline. When i look at the comment, I think your intention might have been to suggest a change to the header which is why i asked you for followup.

I think your actual intention was just to leave text feedback. it would be more clear to me then if you just left a comment rather than a text suggestion that has no actual changes to the text

does that make sense? please let me know if it doesnt. there are several comments here that look like you started to edit the text and then didn't which will prompt me to ask for more information to ensure i'm capturing the feedbac correctly.

yep, got it! I'll be more decisive next time in whether or not I provide an inline edit, and make sure to use the corresponding feature.

kierisi · 2024-08-01T15:44:42Z

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

+---
+layout: single
+title: "pyOpenSci a Recap of @ SciPy 2024 Meeting - Tacoma, Washington"
+excerpt: "This year I gave a talk and lead a packaging workshop at the SciPy 2024 conference in Tacoma Washington. Learn more about the SciPy meeting and how exciting it was for pyOpenSci to be there this year!"


Suggested change

excerpt: "This year I gave a talk and lead a packaging workshop at the SciPy 2024 conference in Tacoma Washington. Learn more about the SciPy meeting and how exciting it was for pyOpenSci to be there this year!"

excerpt: "This year our Executive Director and Founder, Leah Wasser, gave a talk and led a packaging workshop at the SciPy 2024 conference in Tacoma, Washington. Learn more about the SciPy meeting and how exciting it was for pyOpenSci to be there this year!"

the preview on our website doesn't show who the author is, so by adding your name in we can ideally get more people interested in reading.

oh weird. that is a bug! it may be a bug in CI because when i build locally i see the author name and picture on the page. i'm going to hold off on accepting this because I did write the blog post so it should be coming from me . i could mention who i am in the post too however if you think that would be useful.

are you thinking of the actual blog post page? this is what I see when I go to the main blog page:

so there's no author information

(also, I just noted that the alignment is off between the title and the body of the preview text. should I file an issue for that?)

that alignment is intentional. I just redid that page this week with the events pr.

the issue that i think you should file is related to wanting the author to be listed on the blog listing page. This topic is out of scope for this pr because this pr is only a new blog post.

Being super specific about where information is missing (in context of a specific PR) is important to avoid scope creep in a single pr and conversations then straying from the pr that we are trying to merge.

Feel free to open an issue (and a pr?) related to the blog landing page and please include screenshots and make it specific if you want someone else to fix it so we can tag it with help wanted!

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

kierisi · 2024-08-01T16:28:06Z

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

+I spent a lot of time talking with colleagues, friends, and community members
+about all things Python, open source, and open science.
+
+* I worked with Sarah Kaiser on our new GitHub container to support workshops.


is there something we could link to for the GitHub container?

oh yes - it's not merged yet but i could link to the PR! i'll do that locally.

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

kierisi · 2024-08-01T16:31:08Z

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

+Additionally, I caught up with colleagues, chatting about packaging and scientific Python.
+
+
+## Sprints


going to stop noting it, but overall I think headings could be stronger with a descriptive and declarative statement, which will also help with SEO.

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

lwasser

Ok thank you for the feedback. i've integrated all of the inline comments and left a few questions. i'll work on headers and content enhancements tomorrow so we can get this merged.

lwasser · 2024-08-01T22:46:57Z

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

+---
+layout: single
+title: "pyOpenSci a Recap of @ SciPy 2024 Meeting - Tacoma, Washington"
+excerpt: "This year I gave a talk and lead a packaging workshop at the SciPy 2024 conference in Tacoma Washington. Learn more about the SciPy meeting and how exciting it was for pyOpenSci to be there this year!"


oh weird. that is a bug! it may be a bug in CI because when i build locally i see the author name and picture on the page. i'm going to hold off on accepting this because I did write the blog post so it should be coming from me . i could mention who i am in the post too however if you think that would be useful.

lwasser · 2024-08-01T22:48:22Z

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

+
+</div>
+
+## My SciPy 2024 experience


sure - when you say "this" do you mean that first sentence or the paragraph?
If you can help me understand what that would look like then I can make a change locally?

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

lwasser · 2024-08-01T22:51:13Z

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

+
+More on all of that below. But first--what is the SciPy Conference?
+
+## About the SciPy Conference


i like the idea of making it more powerful. Are you suggesting that I change the header text or the content of the paragraph or both?

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

lwasser · 2024-08-01T22:55:28Z

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

+I'd be remiss if I didn't mention the lightning talk sessions. During lightning
+talks, people throw their names into a literal bucket. If their name is selected,
+they are given 5 minutes (or less if the dice are rolled) to talk about a topic
+they love. At SciPy, there are often off-beat distractions from the moderators


oh that is totally what happens. they literally heckle you on the stage and intentionally disrupt. it's funny tho because everyone is used to it. but it really is intentional disruption and the audience just laughs.

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

lwasser · 2024-08-01T22:58:33Z

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

+Several participants enjoyed the process so much that they joined our sprint
+afterwards to help build out the packaging guide. More on that below.
+
+## My talk on Python packaging at SciPy 2024


ok i think i understand - above you were referencing the headers being changed.

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

lwasser · 2024-08-01T23:00:44Z

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

+I spent a lot of time talking with colleagues, friends, and community members
+about all things Python, open source, and open science.
+
+* I worked with Sarah Kaiser on our new GitHub container to support workshops.


oh yes - it's not merged yet but i could link to the PR! i'll do that locally.

kierisi · 2024-08-02T10:43:40Z

re: #448 (comment)

I think what's happening there is that I start with a suggested change and then end up deleting it but leaving the comment. I'll be more diligent on that going forward!

as for clarifying, I think if you could "set the scene" and describe what happens at the lightning talks for someone who has never been, it would be great! almost like a tour guide explanation of what happens (it doesn't have to be super in-depth, just enough to give someone context!)

kierisi · 2024-08-02T10:48:20Z

re: #448 (comment)

totally about the headers! SEO operates largely on headers, so one of the ways we can continue to grow awareness of pyOpenSci is by writing headers that "answer a question," as it makes them more likely to be picked up by Google, and show up as "snippets" when someone enters a query on the web.

so a totally random and arbitrary example could be someone googling "Is SciPy fun?" and us having a heading like "SciPy is the most fun conference I've ever been to!", which could then get picked up by Google and shown as one of the "featured" snippets in response to the person doing the googling.

you'll actually see people writing for SEO//using AI for SEO try to hijack this, where they'll have a great header, but the actual text under the header doesn't actually answer the question (sometimes it doesn't even address it).

lwasser · 2024-08-02T23:06:49Z

ok fantastic @kierisi i went through and tried to make the headers more engaging. I do remember working on this when we optimized earthdatascience.org with seo people. it just takes more time to write. But also i'm not sure if what i've changed hits our goals. can you please re-review this pr with the updated headers? i think once i have a bit more context i can try to just write better headers. That website work i did was in 2016 -- seo has come a long way.

lwasser · 2024-08-02T23:08:58Z

_data/contributors.yml

something weird happened when i rebased... will fix

Co-authored-by: Jesse Mostipak <[email protected]>

lwasser · 2024-08-02T23:16:10Z

_posts/2024-05-30-pyos-pyconus-2024-recap.md

@@ -112,8 +112,7 @@ fundamental concepts, and
 for beginners.

 <figure>
-  <img src="{{ site.baseurl }}/images/blog/2024/may/pyopensci-too-many-python-packaging-options-pycon-talk-2024.png
-" alt="A cute image of a black flat coated retriever laying on the floor with a purple ice pack on it's head looking right at you." />
+  <img src="{{ site.baseurl }}/images/blog/2024/may/pyopensci-too-many-python-packaging-options-pycon-talk-2024.png" alt="A cute image of a black flat coated retriever laying on the floor with a purple ice pack on it's head looking right at you." />


somehow this link got broken when i was working on the blog so i fixed it here.

lwasser · 2024-08-02T23:17:47Z

@kierisi i suggest that you just go through and add optimizations to the blog post directly as suggested inline changes i have made a lot of changes but also am keen to move past scipy work and focus on fall festival and funding! so if you can help me with the seo part here that would be great. maybe we can try to get this merged by tuesday next week?

kierisi

@lwasser the headings are great! I made some small grammatical suggestions and left a note on emoji v. font awesome. let me know what questions you have!

_posts/2024-08-02-pyopensci-at-scipy-2024.md

kierisi · 2024-08-03T02:52:26Z

_posts/2024-08-02-pyopensci-at-scipy-2024.md

+Every year at SciPy, we spend the last two days of the meeting sprinting.
+This year was the first time I stayed for both days of the sprints.
+
+### A brief overview of open-source sprints


Suggested change

### A brief overview of open-source sprints

### A brief overview of open-source software sprints

_posts/2024-08-02-pyopensci-at-scipy-2024.md

Co-authored-by: Jesse Mostipak <[email protected]>

lwasser · 2024-08-06T19:53:36Z

ok i am going to merge this once CI finishes!

lwasser changed the title ~~Blog scipy24 recap~~ feat(blog): scipy24 recap blogpost with pictures Jul 25, 2024

lwasser force-pushed the blog-scipy24 branch from 6f9e80a to 49a47b0 Compare July 25, 2024 22:28

lwasser mentioned this pull request Jul 25, 2024

feat(blog): pycon sprints & how pyos leads sprints 2024 #423

Merged

lwasser force-pushed the blog-scipy24 branch 3 times, most recently from 9781e08 to 95a2f59 Compare July 31, 2024 22:26

lwasser marked this pull request as ready for review July 31, 2024 22:26

lwasser requested a review from kierisi as a code owner July 31, 2024 22:26

kierisi reviewed Aug 1, 2024

View reviewed changes

lwasser commented Aug 1, 2024

View reviewed changes

lwasser added 4 commits August 2, 2024 09:45

feat(blog): scipy 2024 recap

9b2ec8a

Fix: alt text and typos

d40b45d

Fix: copy edits and alt tags

2b5c5f8

Fix: cleanup styles for readability

b0705ca

lwasser commented Aug 2, 2024

View reviewed changes

_data/contributors.yml Outdated

Copy link

Member Author

lwasser Aug 2, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

something weird happened when i rebased... will fix

lwasser and others added 8 commits August 2, 2024 17:11

feat(blog): scipy 2024 recap

902c571

Fix: alt text and typos

df879c6

Fix: copy edits and alt tags

30c5460

Fix: cleanup styles for readability

3b9480b

fix(edits): review by @kierSi

ec41658

Co-authored-by: Jesse Mostipak <[email protected]>

fix(edits): review by @kierSi

2affecb

Co-authored-by: Jesse Mostipak <[email protected]>

fix(rename)

073974d

feat(headings): more expressive seo friendly headings

ff2249e

lwasser force-pushed the blog-scipy24 branch from 7a2ef2e to ff2249e Compare August 2, 2024 23:13

fix(image): broken link

aacd508

lwasser commented Aug 2, 2024

View reviewed changes

kierisi reviewed Aug 3, 2024

View reviewed changes

Apply suggestions from code review

aa3d8d4

Co-authored-by: Jesse Mostipak <[email protected]>

lwasser merged commit b3813f4 into pyOpenSci:main Aug 6, 2024
4 checks passed

lwasser deleted the blog-scipy24 branch August 6, 2024 19:55

	title: "pyOpenSci a Recap of @ SciPy 2024 Meeting - Tacoma, Washington"
	title: "pyOpenSci a Recap of @ SciPy 2024 Meeting - Tacoma, Washington"

	excerpt: "This year I gave a talk and lead a packaging workshop at the SciPy 2024 conference in Tacoma Washington. Learn more about the SciPy meeting and how exciting it was for pyOpenSci to be there this year!"
	excerpt: "This year our Executive Director and Founder, Leah Wasser, gave a talk and led a packaging workshop at the SciPy 2024 conference in Tacoma, Washington. Learn more about the SciPy meeting and how exciting it was for pyOpenSci to be there this year!"

		Additionally, I caught up with colleagues, chatting about packaging and scientific Python.


		## Sprints


		More on all of that below. But first--what is the SciPy Conference?

		## About the SciPy Conference

	### A brief overview of open-source sprints
	### A brief overview of open-source software sprints

feat(blog): scipy24 recap blogpost with pictures #448

feat(blog): scipy24 recap blogpost with pictures #448

Uh oh!

Conversation

lwasser commented Jul 25, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

kierisi left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

lwasser left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

kierisi commented Aug 2, 2024

Uh oh!

kierisi commented Aug 2, 2024

Uh oh!

lwasser commented Aug 2, 2024

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

lwasser commented Aug 2, 2024

Uh oh!

kierisi left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

lwasser commented Jul 25, 2024 •

edited

Loading