@danielskatz@fosstodon.org
@danielskatz@fosstodon.org avatar

danielskatz

@danielskatz@fosstodon.org

Chief Scientist @ NCSA, Research Associate Professor @ CS & ECE & iSchool, @ U Illinois Urbana Champaign
He/him
Works on: computational & data science & engineering #cyberinfrastructure: #software #foss #opensource #systems #tools #policy #practices #scholcomm #FAIR #RSEng #HPC
Orgs: #ReSA, #JOSS_TheOJ, #US_RSE
Also: #fedi22 #photography #birds

This profile is from a federated server and may be incomplete. Browse more on the original instance.

gvwilson, to random
@gvwilson@mastodon.social avatar

The article that @jorgearanda , @mhoye , Brittany Johnson, and I wrote about "It Will Never Work in Theory" has been published in the May/June 2024 issue of "IEEE Software" and is available at https://www.computer.org/csdl/magazine/so/5555/01/10424425/1Ulj1Qa8tJ6. Our thanks to everyone who took part over the years. #nwit

danielskatz,
@danielskatz@fosstodon.org avatar

@gvwilson @jorgearanda @mhoye

Ouch: "We would like to thank the universities, companies, and granting agencies that supported this work, but unfortunately, none did."

danielskatz, to random
@danielskatz@fosstodon.org avatar

Neil Chue Hong and I have completed our special issue in @PeerJ CS on

Software Citation, Indexing, and Discoverability

with an editorial: https://doi.org/10.7717/peerj-cs.1951

The whole special issue (with 5 papers) is available at https://peerj.com/collections/84-software

danielskatz, to random
@danielskatz@fosstodon.org avatar

A common dialog via email

Commercial publisher: Could you review this book [proposal] for us?

If this looks relevant to me:

Me: What compensation do you offer?

Publisher: A book [or some other credit/product] from our company

Me: No. What about money?

There's about a 50/50 chance of their response being yes, and consequently, the same chance of me doing the work...

gvwilson, to random
@gvwilson@mastodon.social avatar

"IEEE Software" will be publishing a short retrospective on "It Will Never Work in Theory". You can find a preprint on their website at https://www.computer.org/csdl/magazine/so/5555/01/10424425/1Ulj1Qa8tJ6 or download the PDF directly from https://www.computer.org/csdl/api/v1/periodical/mags/so/5555/01/10424425/1Ulj1Qa8tJ6/download-article/pdf. Our thanks to everyone who was part of it. #nwit

danielskatz,
@danielskatz@fosstodon.org avatar

@gvwilson congratulations!

Did also see my note in the US-RSE Slack about your website that isn't working now? https://merely-useful.tech/py-rse/ It looks like you may have lost the domain?

danielskatz,
@danielskatz@fosstodon.org avatar

@gvwilson thanks - you might want to look at the github page that hosts this - I think it still points to the old page in the text for where it is deployed

gvwilson, to random
@gvwilson@mastodon.social avatar

should I stay or should I go?

danielskatz,
@danielskatz@fosstodon.org avatar

@gvwilson I always think: should I shave or should I grow?

grimalkina, to random
@grimalkina@mastodon.social avatar

I love a rainy London but truly nothing beats the way it makes me feel to come home to our palm trees and eat a California burrito on the grass in the sunshine with my dog while planning a paddle board session 🥰 love this coast so much

danielskatz,
@danielskatz@fosstodon.org avatar
danielskatz, to random
@danielskatz@fosstodon.org avatar

Today on a Delta flight, the captain told us: "There's too much turbulence expected for the flight attendants to serve the back of the plane, but there's less turbulence in the front, so they will get served"

gvwilson, to random
@gvwilson@mastodon.social avatar

Anyone know what the typical "on hold" time for arxiv.org software engineering submissions is? There doesn't appear to be any way to find out why it's being held up…

danielskatz,
@danielskatz@fosstodon.org avatar

@gvwilson usually if it's held, it ends up being held for a while - there is a contact/help way to write and ask on the website: see https://info.arxiv.org/help/contact.html

danielskatz, to random
@danielskatz@fosstodon.org avatar

A report commissioned by the ARDC estimates that nearly half of the Australian Research Council (ARC) grants from 2010 to 2019 resulted in software production, highlighting the need to strengthen support for and its discovery, reuse and sustainability.

https://ardc.edu.au/article/report-support-needed-for-wealth-of-research-software-created-by-arc-grants/

danielskatz, to random
@danielskatz@fosstodon.org avatar

A new monthly @researchsoft newsletter is out: https://preview.mailerlite.io/emails/webview/778129/113831719893731087

This month’s news includes:

  • This month in research software - community news

  • ADORE.software signed by Dutch funders

  • Supporting ReSA Task Forces

  • Adoption of FAIR4RS Principles - help provide updates

  • Contribute resources on supporting policy change in research institutions

  • Opportunities to get involved with community initiatives

  • Resources

  • Community events

janeadams, to opensource
@janeadams@vis.social avatar

Sometimes in academia, people use the term "open source" to mean that the code is publicly available. To many in the community, "open source" means a lot more.

  1. What should we call prototype research code that accompanies a paper that is made public?

  2. What should research code include, at bare minimum, when shared publicly? (README, docstrings, requirements..)

  3. What is the minimum to actually make something "open source", beyond just publicly posting?

danielskatz,
@danielskatz@fosstodon.org avatar

@janeadams I often think about this as open licensing vs open community

danielskatz,
@danielskatz@fosstodon.org avatar

@janeadams Also, a small group of us has been looking at "open source" vs "Open Source" - see https://arxiv.org/abs/2402.02824 for some discussion

danielskatz, to random
@danielskatz@fosstodon.org avatar

Open-source and research software ( ) experts:

Where should open-source research software projects go to learn about best practices for
a) governance documents
b) roadmaps
c) contributor documents
d) codes of conduct

We have https://choosealicense.com for licenses; what's the equivalent for these other things?

I don't need one place that has all of these; multiple places would be good.

danielskatz, to random
@danielskatz@fosstodon.org avatar

While it's never good to see 8% of a research organizations staff being laid off, not because of careful decisions but because the funding organization (the US Congress) is unable to make any decisions, this plan for how to do so seems well-organized.

My sympathies go out to all my former colleagues at JPL.

https://www.jpl.nasa.gov/news/jpl-workforce-update

danielskatz, to random
@danielskatz@fosstodon.org avatar

Have a look at the URSSI policy project’s most recent article about ways to make a lasting difference in research software, published in CommonPlace:
‘From Code to Tenure: Valuing Research Software in Academia’
https://doi.org/10.21428/6ffd8432.8f39775d

Engage with ideas for advancing research software on GitHub:
https://github.com/si2-urssi/policy/issues?q=is%3Aissue+is%3Aopen+label%3AActivity
Let’s advance research software together!

danielskatz,
@danielskatz@fosstodon.org avatar

@gvwilson Thanks very much!!

leahawasser, to python
@leahawasser@fosstodon.org avatar

Every day I think about how extraordinary it is that so many care so deeply about free and open source software. Isabel is one of a team of volunteers who run peer review of scientific software. Ironically, despite the broad understand in the community of it's value to writing software is not consistently valued in traditional academic settings. how can we change that... together?

https://pyopensci.discourse.group/t/isabel-zimmerman-pyopenscis-winter-2024-software-peer-review-editor-in-chief/430

danielskatz,
@danielskatz@fosstodon.org avatar

@leahawasser It's worth considering that the @joss reviewer database, consisting of people who have volunteered to review open source research software submissions for JOSS, is now over 3000 people, as another example of so many who care

amcasari, to random
@amcasari@hachyderm.io avatar

While it may be US government policy to release federally funded code to the public domain or open source it, ask ANY scientist working in national labs, or the engineers which support them, how their federally funded agencies interpret these policies.

Spoiler: It's as uneven as you would expect. 🙃🫠

danielskatz,
@danielskatz@fosstodon.org avatar

@amcasari While I appreciate this point, it's worth noting the 2016 OMB guidance was about software that federal agencies developed either directly or via contractors, but was not about software that was developed by grantees. Also, re software being missing in the Nelson memo, a group of us wrote recommendations to help the next version of this memo address software: https://doi.org/10.1371/journal.pbio.3002204

danielskatz, to random
@danielskatz@fosstodon.org avatar

new @researchsoft newsletter, w/

  • This month in research software - community news
  • SciLifeLab to co-host third international research software funders event
  • ReSA Membership update - welcome to VolkswagenStiftung
  • ReSA Community Report and News from our Asia and Africa Community Managers
  • Opportunities to get involved with community initiatives
  • Community events and resources

https://preview.mailerlite.com/n9l7f7x6p5/2398270524028360866/a7a1/

pdebuyl, to space
danielskatz,
@danielskatz@fosstodon.org avatar

@pdebuyl @ChelleGentemann @crawfordsm

You've convinced me to try this as well. My first issue is that FAIR is defined just in the context of data, even though we have FAIR principles for software, workflows, science gateways, etc.

danielskatz,
@danielskatz@fosstodon.org avatar

@pdebuyl Maybe that will appear after the intro, because in that first part, it's just about data.

I also wonder how to point out small issues? Like this, where it's unclear if 2023 or 2022 is correct, but seems like they should be consistent, so I would have liked to have opened an issue. I also saw an extra space in one place, which I could have suggested a PR to fix.

danielskatz,
@danielskatz@fosstodon.org avatar

@pdebuyl Ah, now I found https://github.com/nasa/Transform-to-Open-Science/ so I can try some PRs...

danielskatz,
@danielskatz@fosstodon.org avatar

@pdebuyl No, I spoke too soon. Even though this what the help page suggests, the source isn't actually there, and I found a FAQ there that says content suggestions/fixes should be emailed...

danielskatz,
@danielskatz@fosstodon.org avatar

@pdebuyl yes, you are right - I didn't dig deeply enough

  • All
  • Subscribed
  • Moderated
  • Favorites
  • bokunoheroacademia
  • cubers
  • rosin
  • Durango
  • DreamBathrooms
  • osvaldo12
  • magazineikmin
  • Youngstown
  • slotface
  • InstantRegret
  • mdbf
  • thenastyranch
  • khanakhh
  • kavyap
  • HellsKitchen
  • ethstaker
  • everett
  • tester
  • normalnudes
  • tacticalgear
  • GTA5RPClips
  • cisconetworking
  • modclub
  • Leos
  • lostlight
  • relationshipadvice
  • anitta
  • sketchdaily
  • All magazines