No description
  • Python 88.1%
  • HTML 8.4%
  • CSS 2.4%
  • Shell 0.6%
  • Makefile 0.5%
Find a file
Alex d2fbd79602
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
feat(website/template/project_detail): parse more project level data
2026-09-01 16:52:35 +02:00
data feat(data/projects): add logoUrls 2026-08-31 19:13:12 +02:00
examples tests: fix & improve tests 2026-08-24 16:10:36 +02:00
LICENSES app: add very basic python Flask web application 2026-08-24 10:21:07 +02:00
scripts feat(schema,website): add project logo handling 2026-09-01 15:54:53 +02:00
tests rename app/ to website/ 2026-08-24 16:51:21 +02:00
website feat(website/template/project_detail): parse more project level data 2026-09-01 16:52:35 +02:00
.gitignore feat(schema,website): add project logo handling 2026-09-01 15:54:53 +02:00
.pre-commit-config.yaml ci: reorder pre-commit hooks 2026-08-25 22:06:21 +02:00
.woodpecker.yml ci: add missing dependency 2026-09-01 15:54:53 +02:00
Makefile rename app/ to website/ 2026-08-24 16:51:21 +02:00
pyproject.toml ci: add missing dependency 2026-09-01 15:54:53 +02:00
README.md update README 2026-08-22 23:54:02 +02:00
schema.json feat(schema,website): add project logo handling 2026-09-01 15:54:53 +02:00
schema.json.license initial (DRAFT) commit 2026-06-22 18:21:59 +02:00

NGI-0 project collection

This repo contains the individual software project level descriptions as they are used in the NGI-0 tech dossiers.

Data format

Every project lives in its own JSON file in the data/projects directory. The (currently draft) JSON schema against which the JSON files are validated is described in the schema.json.

If you make edits in the schema schema.json, please add (and possibly adapt the existing) .json examples in the examples/ and data directory. They are then automatically checked for compliance with the schema.

Data sources

We want to reuse as much high-quality information for the project files as is available online so as to keep manual categorization/tagging efforts at a minimum.

NGI makes its different grants available as a JSON file. Now, a single project can benefit from multiple NGI grants, which means that grants need to be grouped by project. Some of the grouping is being done by NGI, when creating their hexes.

Once projects are identified from the grants, we enrich them with attributes like the OW2 Market Readiness Levels.

There are multiple options for categorical mappings: Inspiration can be drawn from the NLNet topics or the CDC EuroCommons coalitions.

The ingestor and mapping scripts which tap into the different sources and programmatically generate/update (most of) the project JSONs can be found in the scripts directory.