Hello all, This year, the ESIP <http://www.esipfed.org/> (Federation of Earth Science Information Partners) community has been developing research code/software guidelines for the Earth Observation and geosciences communities. We're juggling the need to support a diverse range of community members in these activities with the understanding that funding agencies are exploring (or beginning to implement) evaluation efforts for research products.
So, code is code and we are taking a fairly broad approach in this document. There is a lot of interest in the guidelines as a tool for encouraging one's PI or manager to greenlighting some of the best practices (continuous integration and Docker comes up a lot) so let us know if we're missing anything along those lines. The complete draft of ESIP's research code/software guidelines <https://esipfed.github.io/Software-Assessment-Guidelines/> is available for comment throughout October. If you have suggestions or feedback for: 1. Interoperability <https://esipfed.github.io/Software-Assessment-Guidelines/guidelines.html#h.k8wt6ghlvp2k> 2. Jupyter notebooks as code or documentation (any notebook platform) 3. The proposed progression <https://esipfed.github.io/Software-Assessment-Guidelines/guidelines.html#h.b2e39m7jtud5> model 4. Sustainability <https://esipfed.github.io/Software-Assessment-Guidelines/guidelines.html#h.ekrcac4t6s00> or adoption/reuse <https://esipfed.github.io/Software-Assessment-Guidelines/guidelines.html#h.hftwhr372i88> please chime in now! And suggestions for any other section are more than welcome. We are also interested in additional inputs to the Scenarios section. If you're interested in a telecon to discuss the progression model, sustainability and adoption/reuse, the guidelines proper or some other topic in the draft, please let me know by completing this google form this week: https://goo.gl/forms/K3QEH1LUsjbZEhaB2 You don't need to be an ESIP member to participate in the telecon(s). If you use the Hypothes.is tool for commenting, let me know who you are (user name in hypothes.is and name/affiliation) so that we can add you to the Contributors list. Final note: You are expected to follow the SWC code of conduct and this is not the space to comment on the funders' evaluation efforts. (There will be a session at the upcoming AGU Fall Meeting in ESSI for anyone interested in some of the federal approaches.) I am happy to discuss the background or ESIP's position, feel free to ask and I look forward to your input. Thank you, Soren -- Soren Scott Research Coder The Ronin Institute for Independent Scholarship [email protected]
_______________________________________________ Discuss mailing list [email protected] http://lists.software-carpentry.org/listinfo/discuss
