1 / 10

Empowering Software Visibility & Reuse in Research: Insights from ADASS XXII BoF Collaboration

Dive into increasing software visibility and reuse in research at the ADASS XXII event in Champaign, IL. Explore crucial questions like promoting code release for reproducibility, changing developer culture, crediting code authors, and more. Join the ongoing conversation on Google Drive or the ASCL blog.

yachi
Télécharger la présentation

Empowering Software Visibility & Reuse in Research: Insights from ADASS XXII BoF Collaboration

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. BoF: Bring out your codesIncreasing software visibility and re-use ADASS XXII, Champaign, IL

  2. Bring out your codes (please!) Monday’s BoF sought answers to the following seven questions…

  3. Discussion question #1 How do we ensure code release is recognized as an essential part of assuring reproducibility of research?

  4. Discussion question #2 How can the community change the culture so developers will release their programs?

  5. Discussion question #3 What can we do to ensure code authors receive credit for writing and releasing their software, and encourage them to release it even if it's "messy" code?

  6. Discussion question #4 How do we reduce expectations of support when a developer does not wish to (or cannot) take on that role after program release?

  7. Discussion question #5 What role might journal publishers and funding agencies have in furthering code release, and how can the community influence them to take on that role?

  8. Discussion question #6 How can universities be convinced to change policies which prohibit software publication?

  9. Discussion question #7 Can funding agencies and publishers encourage documentation of programs, and if so, how?

  10. The answers… … are still out there. Please join the conversation either on Google Drive at tinyurl.com/CodesBoF or on the ASCL blog at asterisk.apod.com/wp/

More Related