Versionen im Vergleich

Schlüssel

  • Diese Zeile wurde hinzugefügt.
  • Diese Zeile wurde entfernt.
  • Formatierung wurde geändert.

...

Two areas are important for this theme of 'software citation' in terms of our editorial remit of taking a 'needs based approach to researchers', these are the use of software and the development of software. As examples:The

  • the benefits to the scientific systems can be that

...

  • experiments using software can be replicated and built upon more easily, and

...

  • in the area of software development can be helped by increased discovery and reuse.

The relationship of researchers to research software can quite often be characterized as transitory or 'on-/off', and is compounded by the accelerated development life cycles: a researcher might only briefly use a tool, research software R&D funding is quite often time limited, and in the end the life cycle of a software system is also limited-limited.

In this editorial theme of 'software citation' we want to look at what initiatives and project are working on these issues of software citation and improving the reuse of software. We also want to look practical steps that a variety of users and public institutions can take to improve their systems for software citation. Our initial use cases are:

  • the software maker or contributor,
  • the researcher citing the software, and
  • the researcher reading/using research literature/output and wanting to reuse the software.

Our theme themes are run over a flexible time period, but as default for three four weeks, and then periodically we will revisit a theme. Our editorial approach is to support the Open Science community in its ongoing work in a given area. We do this by carrying short blog posts, and by maintaining a 'notebook' to engaging in discourse and support on our own forum and on social media, as well as carrying resource documentation, as collaborative documents on key sources and how-tos if neededcarry resource documentation.

The future

Advanced software maintenance systems make use of systems for version control systems and dependency management. The result of these two types of technologies results in the ability to have any version in a software's release history being automatically available, and be able to run , the software where applicable. With the additions recent addition of technologies such as 'continuous integration' software can be validated to be in good working order and so ensure it is fit to be useused.

Building on these three technologies, in the not too distant future, the working environment for software making can mean that greater sustainability can be achieved, example R&D will be able to being about a much greater sustainability. Example are a project like Binder for republish Jupyter notebooks https://mybinder.org


Maybe a See the brief sketch on such future casting #Open SciFi story - what if?

...

Community engagement

Literature and projects (Zotero)

A collaborative bibliography on software citation https://www.zotero.org/groups/1838445/o-s/items/tag/software-cite

Related journals

  • PeerJ Computer Science

Key resources (provisional)

2016 Force11 working group running through Dec' 18. Group https://www.force11.org/software-citation-principles Article https://peerj.com/articles/cs-86/

...