We had a display table at ADASS in addition to participating in a Birds of a Feather (BoF) session and passed out a few documents, showed a few slides, had a couple glasses of wine… Cannot share the wine, but can share some of the files:
ASCL flyer (PDF)
BoF talking points handout (.docx)
BoF discussion questions presentation (.pptx)
Request for suggestions for improving the ASCL (.pptx)
Papers of possible interest to astronomical software users (.docx) (also available online)
ASCL has a display table at ADASS XXII; below is the short presentation we are running at the table.
Several of the ASCL’s Advisory Committee are panelists for a Birds of a Feather session that seeks answers to the following questions:
How do we ensure code release is recognized as an essential part of assuring reproducibility of research?
How can the community change the culture so developers will release their programs?
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?
How do we reduce expectations of support when a developer does not wish to (or cannot) take on that role after program release?
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?
How can universities be convinced to change policies which prohibit software publication?
Can funding agencies and publishers encourage documentation of programs, and if so, how?
Got answers? Ideas? Comments? Please share!