Skip to main content
v2026.11,772 entries · CC-BY 4.0
Dictionary termTrack AStablev2026.2

Open-software contribution

The development, documentation, packaging, testing, or maintenance of research software released under an open-source licence, including authoring new code, contributing to existing projects, releasing reusable libraries, or operating long-term maintenance.

ByCASRAI Editorial Board
· Last updated 22 Aug 2026
Share this

Ask CASRAI · included with Regulatory Radar

Ask about Open-software contribution

Ask CASRAI answers research-administration questions and cites the passages behind every claim — and says so when the corpus does not cover something, instead of guessing. It comes with a Regulatory Radar subscription at $29 a month, alongside the daily digest of regulatory changes and the dashboard of what changed.

150 questions a day, on this site, over the API, or inside your own tools through the CASRAI MCP server.

Everything CASRAI publishes — this page, the dictionary, the guides and the news — stays free to read, with no account and no card.

Examples

Worked examples

  • Is an instance

    A researcher who authored a Python package, released it under MIT with a Zenodo DOI, and maintains it with a CITATION.cff file

Counter-examples

Looks similar, but isn't

  • Not an instance

    A one-off analysis script emailed to a colleague is not open-software contribution in the citable sense

Editorial commentary

Open-software contribution is the development, documentation, packaging, testing, or maintenance of research software released under an open-source licence — authoring new code, contributing to an existing project, releasing a reusable library, or taking on long-term maintenance. Credit is increasingly formalised through software citation with a DOI (via Zenodo or Software Heritage), CRediT’s Software role, and Research Software Engineer (RSE) career frameworks that treat sustained software work as a legitimate research career track in its own right.

How it differs from related terms: Open-data contribution is the same category of preparatory, often-invisible labour applied to datasets rather than code. Credit can attach at different granularities — a citation to a software release as a whole, or a per-contributor list in a machine-readable CITATION.cff file naming individual commits or maintenance roles — and the two are not interchangeable for attribution purposes.

A one-off analysis script emailed to a colleague, with no release, licence, or version history, is not open-software contribution in the citable sense; publication, licensing, and a persistent identifier are what convert code into a creditable output.

References

  • Smith et al., “Software Citation Principles,” PeerJ Computer Science (2016)
  • FORCE11 Software Citation Implementation Working Group (2020)

Also known as

Research software contribution · RSE contribution

Machine-readable encodings

Use in your systems

JATS XML <role> element
xml
<role vocab="credit"
      vocab-identifier="https://casrai.org/dictionary/"
      vocab-term="Open-software contribution"
      vocab-term-identifier="https://casrai.org/dictionary/term/open-software-contribution" />
Schema.org DefinedTerm (JSON-LD)
json
{
  "@context": "https://schema.org",
  "@type": "DefinedTerm",
  "@id": "https://casrai.org/dictionary/term/open-software-contribution",
  "name": "Open-software contribution",
  "identifier": "https://casrai.org/dictionary/term/open-software-contribution",
  "description": "The development, documentation, packaging, testing, or maintenance of research software released under an open-source licence, including authoring new code, contributing to existing projects, releasing reusable libraries, or operating long-term maintenance.",
  "inDefinedTermSet": "https://casrai.org/dictionary/domain/credit-extensions#set",
  "url": "https://casrai.org/dictionary/term/open-software-contribution",
  "sameAs": [
    "Research software contribution",
    "RSE contribution"
  ],
  "license": "https://creativecommons.org/licenses/by/4.0/",
  "publisher": {
    "@id": "https://casrai.org/#organization"
  },
  "author": {
    "@id": "https://casrai.org/#editorial-team"
  },
  "datePublished": "2026-05-21T01:59:03",
  "dateModified": "2026-08-22T15:04:58",
  "inLanguage": "en-GB",
  "isAccessibleForFree": true
}

Referenced across the research world

University of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logoUniversity of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logo
  • University of Cambridge logo
  • Columbia University logo
  • Crossref logo
  • University of Edinburgh logo
  • Harvard University logo
  • University of Oxford logo
  • Princeton University logo
  • Stanford School of Medicine logo
  • University College London logo
  • ORCID logo

View CASRAI adoption →

Regulatory Radar

Stop finding out after the fact

$29/month, cancel anytime. Daily digest updates from our analysis, a dashboard holding the same items, and a cited assistant for everything they raise.

  • Federal Register, Federal Register+, Grants.gov, Regulations.gov, NSF News, UKRI, plus CASRAI’s own published content.
  • 72,264 indexed passages, and every answer cites the ones it drew on.