Create Day 1 Blog for BSSw.io: Software Teams Experiences & Challenges

[maherou]

Summarize the content of Day 1 discussion notes to create a Blog article for BSSw.io

The source content for this article is available from this webpage: https://collegeville.github.io/CW21/WorkshopResources/WorkshopSlidesNotes/WorkshopSlidesNotesList.html

There are four PDF files containing the notes from each discussion group. At the end of each file is a list of 3 - 5 high-level items identified by the discussion group. These items should be considered in aggregate and summarized for the Blog article.

A complete draft of the Day 1 blog is available as an attachment.

@jlcohoon: Please review and revise as you see fit. Day1-Blog.txt

[jlcohoon]

Returning to work after a surgery and am picking this up now! I'll have it back to you tomorrow. @maherou

[maherou]

Hi Hannah,

Nice to hear from you on this side of your surgery. I hope all went well. Thank you for your quick resumption of activities.

Mike

---

From: Hannah Cohoon @.> Sent: Thursday, August 19, 2021 9:52 AM To: Collegeville/CW21 @.> Cc: Heroux, Michael A @.>; Mention @.> Subject: [EXTERNAL] Re: [Collegeville/CW21] Create Day 1 Blog for BSSw.io: Software Teams Experiences & Challenges (#25)

Returning to work after a surgery and am picking this up now! I'll have it back to you tomorrow. @maherouhttps://github.com/maherou

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/Collegeville/CW21/issues/25#issuecomment-901982126, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAHZIS74DYRIBJ76FBTD7YLT5ULDPANCNFSM5CCJM77A. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email.

[jlcohoon]

@maherou New draft attached. Process/changes described below.

I read through the groups' notes and then assembled what I thought were the common themes, given the challenges that each group called out as most important. Then I read the draft you had and compared the themes you had with the ones I had to make sure we were on the same page. We mostly were, but I'd combined a few and that's reflected in the attached draft. That meant that I moved some sentences around, added some, removed some. I think I reduced from 9 themes/challenges to 7, but I don't think that we lost any meaningful content. I did try to add more language that referenced the fact that the ideas came from discussion groups, but I never called out an idea as belonging to a specific person (although, we could and perhaps should?). I also reordered the themes, moving the funding one to the end because it's tangentially related to all of the previous ones. Most of my other edits were mostly superficial: trying to be consistent with oxford commas and capitalization, adding in GitHub usernames I could find, using parallel structure across section titles.

One last edit I want to call out is the start to the blog post itself—I added some questions at the start. I'm not really in love with them, but I figured that a blog post can have a punchier start than a research article so I tried to give it a little intrigue. If you have a different idea for a lead (or just want to cut these questions out entirely), have at it!

Day1-Blog.txt

[jlcohoon]

Just noting that I just now double checked and none of the errors that @danielskatz fixed in his read through have carried through to this version. But, it is notable that I took out the sentence, "We need to support maintainers who do not want to be principal investigators (PIs)."

I did that assuming the same message was implicit in the current version of the passage, though looking at it again now I can see that we might want the specificity of the original sentence: "However, in general, we need to improve the recognition, value, and career paths for all members of a scientific software team. Without being recognized and funded, non-PIs find it difficult to continue contributing to a software project and establish their career, forcing them to decide between jeopardizing one or the other. We need to distribute credit across the team so that the diverse actors needed feel valued. We need to address the question one participant posed, 'Why can’t I be a phenomenal contributor?'"