📖 Project Pythia Blog

[rowanc1]

No description provided.

[jnywong]

I've just had a quick glance and left a few small comments. Great blog post, you really captured the excitement of the event!

[jnywong]

Reading this again, this still blows my mind 😄

[rowanc1]

🚀

[rowanc1]

Had a quick chat with @choldgraf and he suggested that we put a small funding statement at the bottom of the blog that mentions the pythia grant as well as Curvenote's investment in the week.

@choldgraf if you wanted to take a first pass at the, go for it. I can take that over the line tomorrow if you don't get it done.

[choldgraf]

I think the content looks great to me - I have one suggestion, and curious what people think about it:

What if we added a brief acknowledgements section at the end that briefly described the major contributions each organization made? I don't think it should go into much detail, and we could encourage project participants to write their own "framing" of the event that goes into more detail about funding sources etc, and cross-link to this post for engineering/technical details.

My rationale: I think it's important to recognize the organizational investments / roles that various stakeholders played when we talk about new developments in the MyST / JB ecosystem. That way we can recognize the work that folks did, and incentivize more of this kind of participation moving forward.

Examples of the kinds of stuff I'm thinking of:

• 2i2c got funding, helped organize/convene the meeting, sent team members to work at the meeting, and provided development cycles via Angus
• Curvenote had almost their entire team participate heavily in development cycles throughout the week (even though they didn't receive any funding to do so)
• Others in orgs related to Pythia played their own roles that should be recognized.

Note

If this isn't straightforward from y'alls perspective, I don't think it needs to block the blog post. 2i2c can always write a short stub post that cross-references this one anyway.

[choldgraf]

I'll approve this to make it clear that I think it's good to go regardless of the changes I suggested.

To try and move this forward - I suggest that if we haven't got resolution on this by EOD tomorrow (or whenever Rowan decides, assuming nobody asks us to hold up), we just merge the blog post as-is and we can always dig into the specific contributions in org-specific blog posts that cross-reference this one.

[choldgraf]

Just noting that some images seem to be not rendering in the preview

[rowanc1]

Yes, videos will work on merge to main (jupyter-book make videos hard)!

I will write a quick funding blurb and ping you by tomorrow.

[brian-rose]

I like the suggestion to acknowledge funding and contributions.

There are three arms of the collaborative Pythia NSF award, and all three orgs made substantial contributions to last week's event:

• University at Albany (NSF award 2324302): Led the funding acquisition, helped organize and facilitate the event.
• UCAR (NSF award 2324303): Led the planning and logistics for the event.
• 2i2c / Code for Science and Society (NSF award 2324304): Provided tailored compute services and on-site support.

[jnywong]

Hey all! The 2i2c blog post is live ✨

I've made a cross-link to this EB blog post, so ping me when this PR is merged and I can get that cross-link updated.

[rowanc1]

@jnywong the blog on EBP side should be live shortly, good to see more perspectives on the event written down. Was a special week. :)

@brian-rose, can you ping us when there is a Pythia blog live, and we can cross-link as well!