-
Notifications
You must be signed in to change notification settings - Fork 96
November Newsletter #1819
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
November Newsletter #1819
Conversation
Update deadline for next round of for US-RSE Community and Travel Funds
Co-authored-by: github-actions <github-actions@users.noreply.github.com>
Google Form responses 619 and 620 Signed-off-by: Chad Dougherty <crd477@icloud.com>
* Automated push to update jobs files 2025-08-23 * add september community call * Update _events/2025/2025-09-community-call.md Co-authored-by: Julia Damerow <jdamerow@users.noreply.github.com> --------- Co-authored-by: github-actions <github-actions@users.noreply.github.com> Co-authored-by: Julia Damerow <jdamerow@users.noreply.github.com>
Co-authored-by: github-actions <github-actions@users.noreply.github.com>
Google Form response 621 Signed-off-by: Chad Dougherty <crd477@icloud.com>
* Fixed broken link, replaced some <a>s with Markdown URLs. * Changed Slack links so they go directly to the channel. * Improved text.
Co-authored-by: github-actions <github-actions@users.noreply.github.com>
…SE#1782) Google Form response 622 Signed-off-by: Chad Dougherty <crd477@icloud.com>
Google Form response 623 Signed-off-by: Chad Dougherty <crd477@icloud.com>
Google Form response 624 Signed-off-by: Chad Dougherty <crd477@icloud.com>
collectively submitted in Google Form response 625 Signed-off-by: Chad Dougherty <crd477@icloud.com>
Co-authored-by: Miranda Mundt <55767766+mrmundt@users.noreply.github.com>
|
|
||
| - **Dan Katz**, presenting \"Research Software Engineering in the Age of AI\" panel on Thursday, 20 Nov 2025, 1:30 pm - 3:00 pm, rooms 240-241-242 [Link here.](https://sc25.conference-program.com/presentation/?id=pan109&sess=sess351) | ||
|
|
||
| - The **RSE-HPC workshop** at SC25 this year, on Sunday, 16 November 2025 from 9:00 am - 5:30 pm in room 267: [Link here.](https://sc25.conference-program.com/session/?sess=sess234) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My guess is there are a bunch of other people from US-RSE with various roles. It might be worth asking who else is on the program.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My concern here is unresponsiveness -- I'm more than happy to do a couple of blasts, but at this point folks know about both the HackMD and the Newsletter submission form and still I have to manually trawl the slack every month. If people aren't posting after multiple prompts, I have to assume they aren't as motivated as yourself for eg...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
that's fair, though if you have time, I might suggest posting something to #general saying "Are you involved in an event (paper, workshop, etc.) in the SC25 program? If so, please let us know by the end of Monday so that we can publicize all US-RSE participants at SC in the US-RSE newsletter that's now being finalized"
|
|
||
| - **Saul, B.** (2025). _"Great expectations: Unifying Statistical Theory and Programming."_ arXiv. [Read the pre-print.](https://doi.org/10.48550/arXiv.2510.09853) | ||
|
|
||
| - **Nature Portfolio** (2025). _"Six factors affecting reproducibility in life science research and how to handle them."_ [Read the editorial.](https://www.nature.com/articles/d42473-019-00004-y) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this should be in the newsletter. It's not a peer-reviewed article or even an editorial, but an ad from a company.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now I'm confused because I wrote all of these by hand following the last mishap and now I can't find the original message that proposed it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Happy to remove
Co-authored-by: Daniel S. Katz <d.katz@ieee.org>
Co-authored-by: Daniel S. Katz <d.katz@ieee.org>
Co-authored-by: Daniel S. Katz <d.katz@ieee.org>
Co-authored-by: Daniel S. Katz <d.katz@ieee.org>
Co-authored-by: Daniel S. Katz <d.katz@ieee.org>
Co-authored-by: Daniel S. Katz <d.katz@ieee.org>
Co-authored-by: Daniel S. Katz <d.katz@ieee.org>
Removed a citation related to reproducibility in life science research.
Description
Checklist:
When you are ready for a technical review/merge, post the for the link for the PR in the US-RSE Slack (#website) to ask for reviewers.