Skip to content

euroargodev/software_guidelines

View on GitHub ↗Related repositories →

Argo software development guidelines

active 2025-07-032026-06-15 (UTC)

Complete coverage26,625 / 26,625 hourly files (100%) · 2 absent upstream2023-08-152026-08-28 (UTC)
Events
95
Pushes
52
Pull requests
0
Issues
35
Stars
0
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 348 days from 2025-07-03 to 2026-06-15. Pushes: 52 total, peak 21 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 35 total, peak 34 in a day. Comments: 2 total, peak 1 in a day. Stars: 0 total, peak 0 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
gmaze511302
github-actions[bot]333300
quai206600

Recent activity

Latest issues, pull requests and releases

  • Issue#36gmaze2026-05-28 14:06
    The project includes a basic documentation
  • Issue comment#56gmaze2026-01-22 13:31
    The software is released under an open-source license (include an open-source LICENSE file with the license content to the codebase)
  • Issue comment#65gmaze2025-07-09 15:39
    github pages guildelines json display
  • Issue#62gmaze2025-07-03 13:48
    Unit tests cover multiple platforms and operating systems
  • Issue#59gmaze2025-07-03 13:48
    The software uses an open-source programming language (https://en.wikipedia.org/wiki/List_of_open-source_programming_languages)
  • Issue#56gmaze2025-07-03 13:47
    The software is released under an open-source license (include an open-source LICENSE file with the license content to the codebase)
  • Issue#55gmaze2025-07-03 13:47
    The software is registered in at least one public software registry (e.g., Zenodo, Seanoe, Research Software Directory)
  • Issue#52gmaze2025-07-03 13:47
    The software includes continuous integration and unit testing
  • Issue#50gmaze2025-07-03 13:47
    The software has been presented to the Argo community (e.g. Data Management Team meeting)
  • Issue#45gmaze2025-07-03 13:46
    The software documentation includes the list of changes to the codebase between each software releases
  • Issue#44gmaze2025-07-03 13:46
    The software documentation includes the definition of the execution environment supported
  • Issue#42gmaze2025-07-03 13:46
    The software documentation has an API reference section automatically generated
  • Issue#41gmaze2025-07-03 13:46
    The software documentation and codebase are written in English
  • Issue#40gmaze2025-07-03 13:46
    The project is hosted on an Argo developer platform (eg: github/euroargodev, github/ArgoDMQC, github/ArgoRTQC or any other project or institute level organisation)
  • Issue#38gmaze2025-07-03 13:46
    The project includes a document describing expected contributions (e.g. a CONTRIBUTING file)
  • Issue#37gmaze2025-07-03 13:46
    The project includes a change log
  • Issue#36gmaze2025-07-03 13:46
    The project includes a basic documentation (e.g. a README file)
  • Issue#34gmaze2025-07-03 13:45
    The project includes a LICENSE file
  • Issue#32gmaze2025-07-03 13:45
    The project include a CITATION.cff file to indicate how to cite the software
  • Issue#31gmaze2025-07-03 13:45
    The project has multiple collaborators from the Argo community
  • Issue#28gmaze2025-07-03 13:45
    The project clearly list all software identifiers in the README file (e.g. DOI, SWHID)
  • Issue#27gmaze2025-07-03 13:45
    The project allows any user to submit an issue or bug report and ease the process (e.g. provide list of labels, issue templates)
  • Issue#26gmaze2025-07-03 13:45
    The methodology implemented by the software has been presented to the Argo community (e.g. Data Management Team meeting)
  • Issue#25gmaze2025-07-03 13:45
    The codebase is formatted following referenced standards (e.g. black in Python)
  • Issue#24gmaze2025-07-03 13:45
    The codebase is designed with modular components to facilitate reuse, testing and maintenance

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 0 stars here means stars gained during the window, not the repo's star count.