Datasets:
Release [run release-20261116T123924Z]
#115
by Battam - opened
This view is limited to 50 files because it contains too many changes. See the raw diff here.
- CHANGELOG.md +9 -0
- README.md +17 -17
- README.zh.md +17 -17
- campaign_files/2026-10-gt-browser-tests-2/calamine-tests-ods/README.md +2 -2
- campaign_files/2026-10-gt-browser-tests-2/calamine-tests-xlsx/README.md +2 -2
- campaign_files/2026-10-gt-browser-tests-2/chrome-devtools-mcp-heap-fixtures/README.md +3 -3
- campaign_files/2026-10-gt-browser-tests-2/chrome-har-perflogs/README.md +2 -2
- campaign_files/2026-10-gt-browser-tests-2/chrome-recorder-cypress-export-tests/README.md +2 -2
- campaign_files/2026-10-gt-browser-tests-2/chrome-recorder-nightwatch-export-tests/README.md +2 -2
- campaign_files/2026-10-gt-browser-tests-2/chrome-recorder-webdriverio-export-tests/README.md +2 -2
- campaign_files/2026-10-gt-browser-tests-2/chromium-bidi-unit-tests/README.md +2 -2
- campaign_files/2026-10-gt-browser-tests-2/chromium-policy-pref-mapping/README.md +2 -2
- campaign_files/2026-10-gt-browser-tests-2/coach-core-merge-tests/README.md +2 -2
- campaign_files/2026-10-hw-eda-tests-2/buserror-simavr-tests-github/README.md +2 -2
- campaign_files/2026-10-hw-eda-tests-2/cadquery-plugins-community-plugin-collection-for-cadquery/README.md +2 -2
- campaign_files/2026-10-hw-eda-tests-2/camotics-gcodetool-regression-tests-github-cauldrondevelopmentllc-camotics/README.md +2 -2
- campaign_files/2026-10-hw-eda-tests-2/cocotb-examples/README.md +4 -4
- campaign_files/2026-10-hw-eda-tests-2/cocotb/README.md +2 -2
- campaign_files/2026-10-m-issue-trackers-2/buildroot-buildroot/README.md +1 -1
- campaign_files/2026-10-m-issue-trackers-2/busybox-net-busybox/README.md +1 -1
- campaign_files/2026-10-m-issue-trackers-2/camunda-jira/README.md +1 -1
- campaign_files/2026-10-m-issue-trackers-2/carouselbuses-passenger-gtfs/README.md +2 -2
- campaign_files/2026-10-m-issue-trackers-2/centos-centos/README.md +1 -1
- campaign_files/2026-10-m-issue-trackers-2/centro-syracuse-gtfs/README.md +2 -2
- campaign_files/2026-10-m-issue-trackers-2/ceph-ceph-users/README.md +1 -1
- campaign_files/2026-10-m-issue-trackers-2/clamav-users/README.md +1 -1
- campaign_files/2026-10-m-issue-trackers-2/clusterlabs-users/README.md +1 -1
- campaign_files/2026-10-m-issue-trackers-2/coachservices-passenger-gtfs/README.md +2 -2
- campaign_files/2026-10-m-issue-trackers-2/codeberg-beacondb-beacondb-pulls/README.md +2 -2
- campaign_files/2026-10-m-issue-trackers-2/codeberg-codeberg-org-pulls/README.md +2 -2
- campaign_files/2026-10-m-issue-trackers-2/codeberg-emersion-soju-pulls/README.md +2 -2
- campaign_files/2026-10-m-issue-trackers-2/codeberg-evi-editor-evi-pulls/README.md +2 -2
- campaign_files/2026-10-m-issue-trackers-2/codeberg-fediverse-fep-pulls/README.md +2 -2
- campaign_files/2026-10-m-issue-trackers-2/codeberg-fitotrack-pulls/README.md +2 -2
- campaign_files/2026-10-m-issue-trackers-2/codeberg-forgejo-docs-pulls/README.md +2 -2
- campaign_files/2026-10-m-issue-trackers-2/codeberg-forgejo-pulls/README.md +2 -2
- campaign_files/2026-10-m-issue-trackers-2/codeberg-gotosocial-pulls/README.md +2 -2
- campaign_files/2026-10-m-issue-trackers-2/codeberg-keyoxide-keyoxide-web-pulls/README.md +2 -2
- campaign_files/2026-10-m-issue-trackers-2/codeberg-mergiraf-pulls/README.md +2 -2
- campaign_files/2026-10-m-issue-trackers-2/codeberg-microcad-microcad-pulls/README.md +2 -2
- campaign_files/2026-10-m-issue-trackers-2/codeberg-mineclonia-pulls/README.md +2 -2
- campaign_files/2026-10-m-issue-trackers-2/codeberg-tenacityteam-tenacity-pulls/README.md +2 -2
- campaign_files/2026-10-m-issue-trackers-2/codeberg-tusky-tusky-pulls/README.md +2 -2
- campaign_files/2026-10-m-issue-trackers-2/codeberg-zig-pulls/README.md +2 -2
- campaign_files/2026-10-md-media-and-documents/cdc-podcast-306916-radiation-myths/README.md +2 -2
- campaign_files/2026-10-md-media-and-documents/cdc-podcast-313910-1-gateway-duggan-whypodcast/README.md +2 -2
- campaign_files/2026-10-md-media-and-documents/cdc-podcast-315594-btd-spheres-maccannell/README.md +2 -2
- campaign_files/2026-10-md-media-and-documents/cdc-podcast-317876-healthybodyhealthybrain/README.md +2 -2
- campaign_files/2026-10-md-media-and-documents/cdc-podcast-319887-fdaw/README.md +2 -2
- campaign_files/2026-10-md-media-and-documents/cdc-podcast-back-to-schoolemergencyplan/README.md +2 -2
CHANGELOG.md
CHANGED
|
@@ -4656,3 +4656,12 @@ Changes to the content of this index, oldest first. There is one entry for each
|
|
| 4656 |
- mitre-cwe-249de311: one source, one upstream: mitre-cwe-249de311: no declared upstream (upstream_kind dataset or catalog, upstream_agent and upstream_entry: a corpus's row of catalog/sources.tsv, a material set's row of catalog/upstreams.tsv)
|
| 4657 |
- software-packages: one source, one upstream: https://pypi.org/simple/: one upstream_entry split by 2 sources of the layer corpus whose licenses do not tell them apart (pypi, software-packages)
|
| 4658 |
- zenodo-workbooks-cc-by: 2 new name hit(s)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 4656 |
- mitre-cwe-249de311: one source, one upstream: mitre-cwe-249de311: no declared upstream (upstream_kind dataset or catalog, upstream_agent and upstream_entry: a corpus's row of catalog/sources.tsv, a material set's row of catalog/upstreams.tsv)
|
| 4657 |
- software-packages: one source, one upstream: https://pypi.org/simple/: one upstream_entry split by 2 sources of the layer corpus whose licenses do not tell them apart (pypi, software-packages)
|
| 4658 |
- zenodo-workbooks-cc-by: 2 new name hit(s)
|
| 4659 |
+
|
| 4660 |
+
## 2026-11-16: sources held back
|
| 4661 |
+
|
| 4662 |
+
- Each source below keeps its newest version that passed every check; its newer batch waits until it passes them:
|
| 4663 |
+
- audio-processing-trees-f675cc1e: one source, one upstream: audio-processing-trees-f675cc1e: several upstreams, 4 agents and 4 entries (https://github.com/espnet/espnet, https://github.com/FFmpeg/FFmpeg, https://github.com/k2-fsa/sherpa-onnx, https://github.com/ggml-org/whisper.cpp)
|
| 4664 |
+
- crypto-library-trees-2856d04b: one source, one upstream: crypto-library-trees-2856d04b: several upstreams, 5 agents and 5 entries (https://github.com/google/boringssl, https://github.com/openssl/openssl, https://github.com/pyca/cryptography, https://github.com/jedisct1/libsodium, https://github.com/C2SP/wycheproof)
|
| 4665 |
+
- mitre-cwe-249de311: one source, one upstream: mitre-cwe-249de311: no declared upstream (upstream_kind dataset or catalog, upstream_agent and upstream_entry: a corpus's row of catalog/sources.tsv, a material set's row of catalog/upstreams.tsv)
|
| 4666 |
+
- software-packages: one source, one upstream: https://pypi.org/simple/: one upstream_entry split by 2 sources of the layer corpus whose licenses do not tell them apart (pypi, software-packages)
|
| 4667 |
+
- zenodo-workbooks-cc-by: 2 new name hit(s)
|
README.md
CHANGED
|
@@ -35,18 +35,18 @@ this dataset is the foundation's public index.
|
|
| 35 |
English | [简体中文](README.zh.md) · [Data page](https://huggingface.co/spaces/Battam/training-data-foundation) · [Usage video](https://huggingface.co/spaces/Battam/training-data-foundation#usage-video)
|
| 36 |
|
| 37 |
<picture class="not-prose">
|
| 38 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.
|
| 39 |
-
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.
|
| 40 |
</picture>
|
| 41 |
<picture class="not-prose">
|
| 42 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.
|
| 43 |
-
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.
|
| 44 |
</picture>
|
| 45 |
|
| 46 |
## Get data in one command
|
| 47 |
|
| 48 |
```sh
|
| 49 |
-
uv run https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.
|
| 50 |
```
|
| 51 |
|
| 52 |
This fetches every spreadsheet material set whole into `./data`, one folder per unit, and checks each file against the size and hashes its row records.
|
|
@@ -57,7 +57,7 @@ the same command takes the same units of this release.
|
|
| 57 |
<details>
|
| 58 |
<summary>What the command takes, and in which order</summary>
|
| 59 |
|
| 60 |
-
The command and the queries below are pinned to the release tag `release-2026-11-16.
|
| 61 |
[uv](https://docs.astral.sh/uv/) reads the script's dependencies, at the versions published before the day of this release.
|
| 62 |
|
| 63 |
The command returns units: every unit that passes the default profile of each material set whose form is `spreadsheets`, each in a folder of its own named after its `unit_id`.
|
|
@@ -85,7 +85,7 @@ Choose material sets from the catalog with [DuckDB](https://duckdb.org/):
|
|
| 85 |
|
| 86 |
```sql
|
| 87 |
SELECT source, collection, title, units, files, top_types, license.tier AS license_tier, needs_auth
|
| 88 |
-
FROM 'hf://datasets/Battam/training-data-foundation@release-2026-11-16.
|
| 89 |
WHERE kind = 'material_set' AND needs_auth = 'no' AND license.tier IN ('permissive', 'share-alike')
|
| 90 |
ORDER BY collection, units DESC;
|
| 91 |
```
|
|
@@ -96,7 +96,7 @@ with `kind = 'corpus'` it returns corpora instead, counted in rows (`files`).
|
|
| 96 |
Choose files in one corpus:
|
| 97 |
|
| 98 |
```sql
|
| 99 |
-
SET VARIABLE files = (SELECT list('hf://datasets/Battam/training-data-foundation@release-2026-11-16.
|
| 100 |
SELECT uri, size_bytes, lower(hex(sha256)) AS sha256
|
| 101 |
FROM read_parquet(getvariable('files'))
|
| 102 |
WHERE source = 'habs-haer-hals' AND ext = 'pdf' AND size_bytes BETWEEN 100000 AND 5000000
|
|
@@ -112,12 +112,12 @@ A data file may hold the rows of several sources, so the query keeps this one's
|
|
| 112 |
## What's inside
|
| 113 |
|
| 114 |
<picture class="not-prose">
|
| 115 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.
|
| 116 |
-
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.
|
| 117 |
</picture>
|
| 118 |
<picture class="not-prose">
|
| 119 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.
|
| 120 |
-
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.
|
| 121 |
</picture>
|
| 122 |
|
| 123 |
<details>
|
|
@@ -149,12 +149,12 @@ Every material set and every corpus, with its counts, size, license tier and log
|
|
| 149 |
## How it is made
|
| 150 |
|
| 151 |
<picture class="not-prose">
|
| 152 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.
|
| 153 |
-
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.
|
| 154 |
</picture>
|
| 155 |
<picture class="not-prose">
|
| 156 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.
|
| 157 |
-
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.
|
| 158 |
</picture>
|
| 159 |
|
| 160 |
Collectors read whole public upstreams into corpora, the material of pre-training and mid-training, and admission turns works found upstream and chosen corpus rows into material sets, the material of post-training.
|
|
@@ -182,7 +182,7 @@ The full text, with the license details, personal information read from sample f
|
|
| 182 |
@misc{training_data_foundation,
|
| 183 |
title = {training-data-foundation: an index of public materials for building agent environments},
|
| 184 |
howpublished = {https://huggingface.co/datasets/Battam/training-data-foundation},
|
| 185 |
-
note = {Release release-2026-11-16.
|
| 186 |
year = {2026}
|
| 187 |
}
|
| 188 |
```
|
|
|
|
| 35 |
English | [简体中文](README.zh.md) · [Data page](https://huggingface.co/spaces/Battam/training-data-foundation) · [Usage video](https://huggingface.co/spaces/Battam/training-data-foundation#usage-video)
|
| 36 |
|
| 37 |
<picture class="not-prose">
|
| 38 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.6/docs/figures/stages-narrow-light.svg">
|
| 39 |
+
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.6/docs/figures/stages-wide-light.svg" alt="What each training stage can use in this release. Pre-training (provisional): 30.7 TB deduplicated size, 151,161,846 rows, 30.0 TB allowed for training. Mid-training (provisional): 3.87 TB deduplicated size, 34,243,169 rows, 1.42 TB allowed for training. Post-training: 1,770 material sets, from 1,982 upstream sources, 1,406 allowed for training.">
|
| 40 |
</picture>
|
| 41 |
<picture class="not-prose">
|
| 42 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.6/docs/figures/stages-narrow-dark.svg">
|
| 43 |
+
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.6/docs/figures/stages-wide-dark.svg" alt="What each training stage can use in this release. Pre-training (provisional): 30.7 TB deduplicated size, 151,161,846 rows, 30.0 TB allowed for training. Mid-training (provisional): 3.87 TB deduplicated size, 34,243,169 rows, 1.42 TB allowed for training. Post-training: 1,770 material sets, from 1,982 upstream sources, 1,406 allowed for training.">
|
| 44 |
</picture>
|
| 45 |
|
| 46 |
## Get data in one command
|
| 47 |
|
| 48 |
```sh
|
| 49 |
+
uv run https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.6/tools/fetch.py --kind material_set --form spreadsheets --out ./data
|
| 50 |
```
|
| 51 |
|
| 52 |
This fetches every spreadsheet material set whole into `./data`, one folder per unit, and checks each file against the size and hashes its row records.
|
|
|
|
| 57 |
<details>
|
| 58 |
<summary>What the command takes, and in which order</summary>
|
| 59 |
|
| 60 |
+
The command and the queries below are pinned to the release tag `release-2026-11-16.6`.
|
| 61 |
[uv](https://docs.astral.sh/uv/) reads the script's dependencies, at the versions published before the day of this release.
|
| 62 |
|
| 63 |
The command returns units: every unit that passes the default profile of each material set whose form is `spreadsheets`, each in a folder of its own named after its `unit_id`.
|
|
|
|
| 85 |
|
| 86 |
```sql
|
| 87 |
SELECT source, collection, title, units, files, top_types, license.tier AS license_tier, needs_auth
|
| 88 |
+
FROM 'hf://datasets/Battam/training-data-foundation@release-2026-11-16.6/meta/catalog.parquet'
|
| 89 |
WHERE kind = 'material_set' AND needs_auth = 'no' AND license.tier IN ('permissive', 'share-alike')
|
| 90 |
ORDER BY collection, units DESC;
|
| 91 |
```
|
|
|
|
| 96 |
Choose files in one corpus:
|
| 97 |
|
| 98 |
```sql
|
| 99 |
+
SET VARIABLE files = (SELECT list('hf://datasets/Battam/training-data-foundation@release-2026-11-16.6/' || f) FROM (SELECT unnest(data_files) AS f FROM 'hf://datasets/Battam/training-data-foundation@release-2026-11-16.6/meta/catalog.parquet' WHERE source = 'habs-haer-hals'));
|
| 100 |
SELECT uri, size_bytes, lower(hex(sha256)) AS sha256
|
| 101 |
FROM read_parquet(getvariable('files'))
|
| 102 |
WHERE source = 'habs-haer-hals' AND ext = 'pdf' AND size_bytes BETWEEN 100000 AND 5000000
|
|
|
|
| 112 |
## What's inside
|
| 113 |
|
| 114 |
<picture class="not-prose">
|
| 115 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.6/docs/figures/inside-narrow-light.svg">
|
| 116 |
+
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.6/docs/figures/inside-wide-light.svg" alt="The training stages by top-level domain, largest first. Pre-training (provisional), deduplicated size, by domain: Data science 29.9 TB; Science 531 GB; Machine learning 82.8 GB; Media 48.7 GB; Unclassified 47.0 GB; System administration 35.7 GB; Many domains 29.6 GB; Hardware 29.6 GB; Security 4.18 GB; Misc 376 MB; Software engineering 183 MB; Operations 4.08 KB. Mid-training (provisional), deduplicated size, by domain: System administration 1.27 TB; Many domains 1.00 TB; Machine learning 503 GB; Science 462 GB; Data science 429 GB; Hardware 177 GB; Security 13.9 GB; Unclassified 4.43 GB; Misc 3.45 GB; Software engineering 3.00 GB; Media 735 MB; Operations 13.9 MB. Post-training, material sets, by domain: Data science 348; Software engineering 286; Media 273; Operations 207; Machine learning 183; Science 175; Security 104; Hardware 87; System administration 71; Misc 36.">
|
| 117 |
</picture>
|
| 118 |
<picture class="not-prose">
|
| 119 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.6/docs/figures/inside-narrow-dark.svg">
|
| 120 |
+
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.6/docs/figures/inside-wide-dark.svg" alt="The training stages by top-level domain, largest first. Pre-training (provisional), deduplicated size, by domain: Data science 29.9 TB; Science 531 GB; Machine learning 82.8 GB; Media 48.7 GB; Unclassified 47.0 GB; System administration 35.7 GB; Many domains 29.6 GB; Hardware 29.6 GB; Security 4.18 GB; Misc 376 MB; Software engineering 183 MB; Operations 4.08 KB. Mid-training (provisional), deduplicated size, by domain: System administration 1.27 TB; Many domains 1.00 TB; Machine learning 503 GB; Science 462 GB; Data science 429 GB; Hardware 177 GB; Security 13.9 GB; Unclassified 4.43 GB; Misc 3.45 GB; Software engineering 3.00 GB; Media 735 MB; Operations 13.9 MB. Post-training, material sets, by domain: Data science 348; Software engineering 286; Media 273; Operations 207; Machine learning 183; Science 175; Security 104; Hardware 87; System administration 71; Misc 36.">
|
| 121 |
</picture>
|
| 122 |
|
| 123 |
<details>
|
|
|
|
| 149 |
## How it is made
|
| 150 |
|
| 151 |
<picture class="not-prose">
|
| 152 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.6/docs/figures/steps-narrow-light.svg">
|
| 153 |
+
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.6/docs/figures/steps-wide-light.svg" alt="How the index is made, in four steps. 1, collect: collectors read whole public upstreams into corpora, one row per file or record, the material of pre-training and mid-training. 2, admit: works the search found upstream and groups of corpus rows become material sets, the material of post-training. 3, check: licenses, personal data, overlap with benchmarks and sizes are checked before release. 4, release: one commit with its own tag, release-2026-11-16.6.">
|
| 154 |
</picture>
|
| 155 |
<picture class="not-prose">
|
| 156 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.6/docs/figures/steps-narrow-dark.svg">
|
| 157 |
+
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.6/docs/figures/steps-wide-dark.svg" alt="How the index is made, in four steps. 1, collect: collectors read whole public upstreams into corpora, one row per file or record, the material of pre-training and mid-training. 2, admit: works the search found upstream and groups of corpus rows become material sets, the material of post-training. 3, check: licenses, personal data, overlap with benchmarks and sizes are checked before release. 4, release: one commit with its own tag, release-2026-11-16.6.">
|
| 158 |
</picture>
|
| 159 |
|
| 160 |
Collectors read whole public upstreams into corpora, the material of pre-training and mid-training, and admission turns works found upstream and chosen corpus rows into material sets, the material of post-training.
|
|
|
|
| 182 |
@misc{training_data_foundation,
|
| 183 |
title = {training-data-foundation: an index of public materials for building agent environments},
|
| 184 |
howpublished = {https://huggingface.co/datasets/Battam/training-data-foundation},
|
| 185 |
+
note = {Release release-2026-11-16.6},
|
| 186 |
year = {2026}
|
| 187 |
}
|
| 188 |
```
|
README.zh.md
CHANGED
|
@@ -22,18 +22,18 @@ tags:
|
|
| 22 |
[English](README.md) | 简体中文 · [数据页](https://huggingface.co/spaces/Battam/training-data-foundation) · [使用示例视频](https://huggingface.co/spaces/Battam/training-data-foundation#usage-video)
|
| 23 |
|
| 24 |
<picture class="not-prose">
|
| 25 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.
|
| 26 |
-
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.
|
| 27 |
</picture>
|
| 28 |
<picture class="not-prose">
|
| 29 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.
|
| 30 |
-
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.
|
| 31 |
</picture>
|
| 32 |
|
| 33 |
## 一条命令取数据
|
| 34 |
|
| 35 |
```sh
|
| 36 |
-
uv run https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.
|
| 37 |
```
|
| 38 |
|
| 39 |
这条命令把每个电子表格材料集整个取进 `./data`,每个单元一个文件夹,并按每个文件所在行记录的大小和哈希值校验它。
|
|
@@ -44,7 +44,7 @@ uv run https://huggingface.co/datasets/Battam/training-data-foundation/resolve/r
|
|
| 44 |
<details>
|
| 45 |
<summary>命令取什么、按什么顺序取</summary>
|
| 46 |
|
| 47 |
-
这条命令和下面的查询都固定在发布标签 `release-2026-11-16.
|
| 48 |
[uv](https://docs.astral.sh/uv/) 会读取脚本声明的依赖,取这个发布当天之前发布的版本。
|
| 49 |
|
| 50 |
命令返回单元:形式为 `spreadsheets` 的每个材料集中通过默认配置的全部单元,每个单元放在以它的 `unit_id` 命名的单独文件夹里。
|
|
@@ -72,7 +72,7 @@ uv run https://huggingface.co/datasets/Battam/training-data-foundation/resolve/r
|
|
| 72 |
|
| 73 |
```sql
|
| 74 |
SELECT source, collection, title, units, files, top_types, license.tier AS license_tier, needs_auth
|
| 75 |
-
FROM 'hf://datasets/Battam/training-data-foundation@release-2026-11-16.
|
| 76 |
WHERE kind = 'material_set' AND needs_auth = 'no' AND license.tier IN ('permissive', 'share-alike')
|
| 77 |
ORDER BY collection, units DESC;
|
| 78 |
```
|
|
@@ -83,7 +83,7 @@ ORDER BY collection, units DESC;
|
|
| 83 |
在一个语料库里挑选文件:
|
| 84 |
|
| 85 |
```sql
|
| 86 |
-
SET VARIABLE files = (SELECT list('hf://datasets/Battam/training-data-foundation@release-2026-11-16.
|
| 87 |
SELECT uri, size_bytes, lower(hex(sha256)) AS sha256
|
| 88 |
FROM read_parquet(getvariable('files'))
|
| 89 |
WHERE source = 'habs-haer-hals' AND ext = 'pdf' AND size_bytes BETWEEN 100000 AND 5000000
|
|
@@ -99,12 +99,12 @@ ORDER BY size_bytes LIMIT 20;
|
|
| 99 |
## 内容概览
|
| 100 |
|
| 101 |
<picture class="not-prose">
|
| 102 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.
|
| 103 |
-
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.
|
| 104 |
</picture>
|
| 105 |
<picture class="not-prose">
|
| 106 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.
|
| 107 |
-
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.
|
| 108 |
</picture>
|
| 109 |
|
| 110 |
<details>
|
|
@@ -136,12 +136,12 @@ ORDER BY size_bytes LIMIT 20;
|
|
| 136 |
## 怎样做成
|
| 137 |
|
| 138 |
<picture class="not-prose">
|
| 139 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.
|
| 140 |
-
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.
|
| 141 |
</picture>
|
| 142 |
<picture class="not-prose">
|
| 143 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.
|
| 144 |
-
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.
|
| 145 |
</picture>
|
| 146 |
|
| 147 |
采集器整批读取完整的公开上游,记成语料库,供预训练和中训练使用,收录则把检索在上游找到的作品和选出的语料库行做成材料集,供后训练使用。
|
|
@@ -169,7 +169,7 @@ ORDER BY size_bytes LIMIT 20;
|
|
| 169 |
@misc{training_data_foundation,
|
| 170 |
title = {training-data-foundation: an index of public materials for building agent environments},
|
| 171 |
howpublished = {https://huggingface.co/datasets/Battam/training-data-foundation},
|
| 172 |
-
note = {Release release-2026-11-16.
|
| 173 |
year = {2026}
|
| 174 |
}
|
| 175 |
```
|
|
|
|
| 22 |
[English](README.md) | 简体中文 · [数据页](https://huggingface.co/spaces/Battam/training-data-foundation) · [使用示例视频](https://huggingface.co/spaces/Battam/training-data-foundation#usage-video)
|
| 23 |
|
| 24 |
<picture class="not-prose">
|
| 25 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.6/docs/figures/stages-narrow-light.zh.svg">
|
| 26 |
+
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.6/docs/figures/stages-wide-light.zh.svg" alt="本次发布中每个训练阶段能用的数据。预训练(暂定):去重后大小 30.7 TB,151,161,846 行,其中 30.0 TB 允许用于训练。中训练(暂定):去重后大小 3.87 TB,34,243,169 行,其中 1.42 TB 允许用于训练。后训练:材料集 1,770,来自 1,982 个上游来源,其中 1,406 允许用于训练。">
|
| 27 |
</picture>
|
| 28 |
<picture class="not-prose">
|
| 29 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.6/docs/figures/stages-narrow-dark.zh.svg">
|
| 30 |
+
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.6/docs/figures/stages-wide-dark.zh.svg" alt="本次发布中每个训练阶段能用的数据。预训练(暂定):去重后大小 30.7 TB,151,161,846 行,其中 30.0 TB 允许用于训练。中训练(暂定):去重后大小 3.87 TB,34,243,169 行,其中 1.42 TB 允许用于训练。后训练:材料集 1,770,来自 1,982 个上游来源,其中 1,406 允许用于训练。">
|
| 31 |
</picture>
|
| 32 |
|
| 33 |
## 一条命令取数据
|
| 34 |
|
| 35 |
```sh
|
| 36 |
+
uv run https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.6/tools/fetch.py --kind material_set --form spreadsheets --out ./data
|
| 37 |
```
|
| 38 |
|
| 39 |
这条命令把每个电子表格材料集整个取进 `./data`,每个单元一个文件夹,并按每个文件所在行记录的大小和哈希值校验它。
|
|
|
|
| 44 |
<details>
|
| 45 |
<summary>命令取什么、按什么顺序取</summary>
|
| 46 |
|
| 47 |
+
这条命令和下面的查询都固定在发布标签 `release-2026-11-16.6` 上。
|
| 48 |
[uv](https://docs.astral.sh/uv/) 会读取脚本声明的依赖,取这个发布当天之前发布的版本。
|
| 49 |
|
| 50 |
命令返回单元:形式为 `spreadsheets` 的每个材料集中通过默认配置的全部单元,每个单元放在以它的 `unit_id` 命名的单独文件夹里。
|
|
|
|
| 72 |
|
| 73 |
```sql
|
| 74 |
SELECT source, collection, title, units, files, top_types, license.tier AS license_tier, needs_auth
|
| 75 |
+
FROM 'hf://datasets/Battam/training-data-foundation@release-2026-11-16.6/meta/catalog.parquet'
|
| 76 |
WHERE kind = 'material_set' AND needs_auth = 'no' AND license.tier IN ('permissive', 'share-alike')
|
| 77 |
ORDER BY collection, units DESC;
|
| 78 |
```
|
|
|
|
| 83 |
在一个语料库里挑选文件:
|
| 84 |
|
| 85 |
```sql
|
| 86 |
+
SET VARIABLE files = (SELECT list('hf://datasets/Battam/training-data-foundation@release-2026-11-16.6/' || f) FROM (SELECT unnest(data_files) AS f FROM 'hf://datasets/Battam/training-data-foundation@release-2026-11-16.6/meta/catalog.parquet' WHERE source = 'habs-haer-hals'));
|
| 87 |
SELECT uri, size_bytes, lower(hex(sha256)) AS sha256
|
| 88 |
FROM read_parquet(getvariable('files'))
|
| 89 |
WHERE source = 'habs-haer-hals' AND ext = 'pdf' AND size_bytes BETWEEN 100000 AND 5000000
|
|
|
|
| 99 |
## 内容概览
|
| 100 |
|
| 101 |
<picture class="not-prose">
|
| 102 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.6/docs/figures/inside-narrow-light.zh.svg">
|
| 103 |
+
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.6/docs/figures/inside-wide-light.zh.svg" alt="按顶层领域分的各训练阶段,由大到小。预训练(暂定),去重后大小,按领域:数据科学 29.9 TB;科学 531 GB;机器学习 82.8 GB;媒体 48.7 GB;未分类 47.0 GB;系统管理 35.7 GB;多领域 29.6 GB;硬件 29.6 GB;安全 4.18 GB;杂项 376 MB;软件工程 183 MB;运营 4.08 KB。中训练(暂定),去重后大小,按领域:系统管理 1.27 TB;多领域 1.00 TB;机器学习 503 GB;科学 462 GB;数据科学 429 GB;硬件 177 GB;安全 13.9 GB;未分类 4.43 GB;杂项 3.45 GB;软件工程 3.00 GB;媒体 735 MB;运营 13.9 MB。后训练,材料集,按领域:数据科学 348;软件工程 286;媒体 273;运营 207;机器学习 183;科学 175;安全 104;硬件 87;系统管理 71;杂项 36。">
|
| 104 |
</picture>
|
| 105 |
<picture class="not-prose">
|
| 106 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.6/docs/figures/inside-narrow-dark.zh.svg">
|
| 107 |
+
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.6/docs/figures/inside-wide-dark.zh.svg" alt="按顶层领域分的各训练阶段,由大到小。预训练(暂定),去重后大小,按领域:数据科学 29.9 TB;科学 531 GB;机器学习 82.8 GB;媒体 48.7 GB;未分类 47.0 GB;系统管理 35.7 GB;多领域 29.6 GB;硬件 29.6 GB;安全 4.18 GB;杂项 376 MB;软件工程 183 MB;运营 4.08 KB。中训练(暂定),去重后大小,按领域:系统管理 1.27 TB;多领域 1.00 TB;机器学习 503 GB;科学 462 GB;数��科学 429 GB;硬件 177 GB;安全 13.9 GB;未分类 4.43 GB;杂项 3.45 GB;软件工程 3.00 GB;媒体 735 MB;运营 13.9 MB。后训练,材料集,按领域:数据科学 348;软件工程 286;媒体 273;运营 207;机器学习 183;科学 175;安全 104;硬件 87;系统管理 71;杂项 36。">
|
| 108 |
</picture>
|
| 109 |
|
| 110 |
<details>
|
|
|
|
| 136 |
## 怎样做成
|
| 137 |
|
| 138 |
<picture class="not-prose">
|
| 139 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.6/docs/figures/steps-narrow-light.zh.svg">
|
| 140 |
+
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.6/docs/figures/steps-wide-light.zh.svg" alt="索引分四步做成。1,采集:采集器整批读取完整的公开上游,每个文件或每条记录记一行,成为语料库,供预训练和中训练使用。2,收录:检索在上游找到的作品和成组的语料库行,收录为材料集,供后训练使用。3,检查:发布前核对许可证、个人信息、与基准测试的重叠和大小。4,发布:一个带有自己标签的提交,release-2026-11-16.6。">
|
| 141 |
</picture>
|
| 142 |
<picture class="not-prose">
|
| 143 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.6/docs/figures/steps-narrow-dark.zh.svg">
|
| 144 |
+
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-16.6/docs/figures/steps-wide-dark.zh.svg" alt="索引分四步做成。1,采集:采集器整批读取完整的公开上游,每个文件或每条记录记一行,成为语料库,供预训练和中训练使用。2,收录:检索在上游找到的作品和成组的语料库行,收录为材料集,供后训练使用。3,检查:发布前核对许可证、个人信息、与基准测试的重叠和大小。4,发布:一个带有自己标签的提交,release-2026-11-16.6。">
|
| 145 |
</picture>
|
| 146 |
|
| 147 |
采集器整批读取完整的公开上游,记成语料库,供预训练和中训练使用,收录则把检索在上游找到的作品和选出的语料库行做成材料集,供后训练使用。
|
|
|
|
| 169 |
@misc{training_data_foundation,
|
| 170 |
title = {training-data-foundation: an index of public materials for building agent environments},
|
| 171 |
howpublished = {https://huggingface.co/datasets/Battam/training-data-foundation},
|
| 172 |
+
note = {Release release-2026-11-16.6},
|
| 173 |
year = {2026}
|
| 174 |
}
|
| 175 |
```
|
campaign_files/2026-10-gt-browser-tests-2/calamine-tests-ods/README.md
CHANGED
|
@@ -1,12 +1,12 @@
|
|
| 1 |
# calamine-tests-ods
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: OpenDocument spreadsheet (.ods) as input; per-sheet used range (start cell and cell grid) as answer.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://github.com/tafia/calamine. Kind: test or example files shipped with a tool. Test fixture of calamine for ODS repeated rows (tool_fixture).
|
| 8 |
|
| 9 |
-
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream.
|
| 10 |
|
| 11 |
**Tools to open and check:** calamine Rust crate (open_workbook_auto on .ods), or Python odfpy / pandas.read_excel(engine='odf'); a script writes the used range of each sheet as JSON
|
| 12 |
|
|
|
|
| 1 |
# calamine-tests-ods
|
| 2 |
|
| 3 |
+
**What this is:** Files published by Johann Tuffe and contributors (tafia/calamine). Collection theme: File format libraries: test corpora of libraries such as Apache POI, openpyxl, python-docx and odfpy (documents normally opened in a GUI; answers from the tests).
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: OpenDocument spreadsheet (.ods) as input; per-sheet used range (start cell and cell grid) as answer.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://github.com/tafia/calamine. Kind: test or example files shipped with a tool. Test fixture of calamine for ODS repeated rows (tool_fixture).
|
| 8 |
|
| 9 |
+
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. Each file names companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
**Tools to open and check:** calamine Rust crate (open_workbook_auto on .ods), or Python odfpy / pandas.read_excel(engine='odf'); a script writes the used range of each sheet as JSON
|
| 12 |
|
campaign_files/2026-10-gt-browser-tests-2/calamine-tests-xlsx/README.md
CHANGED
|
@@ -1,12 +1,12 @@
|
|
| 1 |
# calamine-tests-xlsx
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: Office Open XML workbook (.xlsx) as input; table names, columns and data values as answer; .xlsx as input; list of merged regions (sheet name, start and end cell) as answer; .xlsx as input; typed cell values of A1:B3 as answer; .xlsx as input; per-cell formula text, value and shared-formula range as answer; .xlsx as input; start cell, end cell, first row and cell count per choice as answer; .xlsx as input; formula grid of sheets Column ranges and Row ranges as answer.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://github.com/tafia/calamine. Kind: test or example files shipped with a tool. Test fixture of calamine built for its Excel table reader (tool_fixture); test fixture of calamine for merged-cell reading (tool_fixture); test fixture of calamine for date and duration typing (tool_fixture); test fixture of calamine for shared formulas (tool_fixture); test fixture of calamine for header-row selection (tool_fixture); test fixture of calamine for column and row range formulas (tool_fixture).
|
| 8 |
|
| 9 |
-
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream.
|
| 10 |
|
| 11 |
**Tools to open and check:** calamine Rust crate (open_workbook_auto, worksheet_range, ...), or Python openpyxl / odfpy / pandas.read_excel; a script reads the workbook and writes the asked values to a JSON file
|
| 12 |
|
|
|
|
| 1 |
# calamine-tests-xlsx
|
| 2 |
|
| 3 |
+
**What this is:** Files published by Johann Tuffe and contributors (tafia/calamine). Collection theme: File format libraries: test corpora of libraries such as Apache POI, openpyxl, python-docx and odfpy (documents normally opened in a GUI; answers from the tests).
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: Office Open XML workbook (.xlsx) as input; table names, columns and data values as answer; .xlsx as input; list of merged regions (sheet name, start and end cell) as answer; .xlsx as input; typed cell values of A1:B3 as answer; .xlsx as input; per-cell formula text, value and shared-formula range as answer; .xlsx as input; start cell, end cell, first row and cell count per choice as answer; .xlsx as input; formula grid of sheets Column ranges and Row ranges as answer.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://github.com/tafia/calamine. Kind: test or example files shipped with a tool. Test fixture of calamine built for its Excel table reader (tool_fixture); test fixture of calamine for merged-cell reading (tool_fixture); test fixture of calamine for date and duration typing (tool_fixture); test fixture of calamine for shared formulas (tool_fixture); test fixture of calamine for header-row selection (tool_fixture); test fixture of calamine for column and row range formulas (tool_fixture).
|
| 8 |
|
| 9 |
+
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. Each file names companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
**Tools to open and check:** calamine Rust crate (open_workbook_auto, worksheet_range, ...), or Python openpyxl / odfpy / pandas.read_excel; a script reads the workbook and writes the asked values to a JSON file
|
| 12 |
|
campaign_files/2026-10-gt-browser-tests-2/chrome-devtools-mcp-heap-fixtures/README.md
CHANGED
|
@@ -1,12 +1,12 @@
|
|
| 1 |
# chrome-devtools-mcp-heap-fixtures
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** Each unit is one upstream folder, delivered as all the files fetched from it or one upstream file, kept at its upstream path. Format: V8 heap snapshot JSON (.heapsnapshot: snapshot.meta, nodes, edges, strings), about 1.2 MB each; V8 heap snapshot JSON (.heapsnapshot), about 2.4 MB.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: ChromeDevTools/chrome-devtools-mcp. Kind: test or example files shipped with a tool. Test fixtures of the Chrome DevTools MCP server heap snapshot processor, recorded from the d8 shell (tool_fixture); the server source is not fetched, not bundled and not run; test fixture of the Chrome DevTools MCP server heap snapshot formatter (tool_fixture); the server source is not fetched, not bundled and not run.
|
| 8 |
|
| 9 |
-
**Self-contained:** Not self-contained: each unit is used together with other files from the same upstream.
|
| 10 |
|
| 11 |
**Tools to open and check:** a script that parses the .heapsnapshot JSON (snapshot.meta node and edge fields, nodes, edges and strings arrays) and diffs objects per constructor between two snapshots; or the DevTools heap snapshot model run under Node (chrome-devtools-mcp HeapSnapshotManager, memlab heap analysis); a script that parses the .heapsnapshot JSON and aggregates nodes per constructor (count, shallow size, retained size from the dominator tree); or the DevTools heap snapshot model run under Node (chrome-devtools-mcp HeapSnapshotManager, memlab heap analysis)
|
| 12 |
|
|
@@ -16,7 +16,7 @@
|
|
| 16 |
|
| 17 |
Units:
|
| 18 |
|
| 19 |
-
- `tests/fixtures/`
|
| 20 |
Format: V8 heap snapshot JSON (.heapsnapshot: snapshot.meta, nodes, edges, strings), about 1.2 MB each
|
| 21 |
Origin: test fixtures of the Chrome DevTools MCP server heap snapshot processor, recorded from the d8 shell (tool_fixture); the server source is not fetched, not bundled and not run
|
| 22 |
Check: Final file state: the agent writes, for class NewObject, the number of objects added from heap-1 to heap-3 and from heap-2 to heap-3 (the # New column of the DevTools Memory panel Comparison view) to a result file; require exact integer equality with 7 and 5
|
|
|
|
| 1 |
# chrome-devtools-mcp-heap-fixtures
|
| 2 |
|
| 3 |
+
**What this is:** Units published by Google LLC (Chrome DevTools team), ChromeDevTools/chrome-devtools-mcp. Collection theme: Browser automation: tests shipped with browser automation tools (recorders and code exporters for Chrome DevTools Recorder and Selenium IDE, HAR converters, DevTools trace and heap snapshot processors).
|
| 4 |
|
| 5 |
**What one unit is:** Each unit is one upstream folder, delivered as all the files fetched from it or one upstream file, kept at its upstream path. Format: V8 heap snapshot JSON (.heapsnapshot: snapshot.meta, nodes, edges, strings), about 1.2 MB each; V8 heap snapshot JSON (.heapsnapshot), about 2.4 MB.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: ChromeDevTools/chrome-devtools-mcp. Kind: test or example files shipped with a tool. Test fixtures of the Chrome DevTools MCP server heap snapshot processor, recorded from the d8 shell (tool_fixture); the server source is not fetched, not bundled and not run; test fixture of the Chrome DevTools MCP server heap snapshot formatter (tool_fixture); the server source is not fetched, not bundled and not run.
|
| 8 |
|
| 9 |
+
**Self-contained:** Not self-contained: each unit is used together with other files from the same upstream. Each unit names companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes. Dependencies named upstream are listed per unit in the notes.
|
| 10 |
|
| 11 |
**Tools to open and check:** a script that parses the .heapsnapshot JSON (snapshot.meta node and edge fields, nodes, edges and strings arrays) and diffs objects per constructor between two snapshots; or the DevTools heap snapshot model run under Node (chrome-devtools-mcp HeapSnapshotManager, memlab heap analysis); a script that parses the .heapsnapshot JSON and aggregates nodes per constructor (count, shallow size, retained size from the dominator tree); or the DevTools heap snapshot model run under Node (chrome-devtools-mcp HeapSnapshotManager, memlab heap analysis)
|
| 12 |
|
|
|
|
| 16 |
|
| 17 |
Units:
|
| 18 |
|
| 19 |
+
- `tests/fixtures/`: Heap snapshot comparison: count of NewObject instances added between V8 heap snapshots heap-1 and heap-3, and heap-2 and heap-3.
|
| 20 |
Format: V8 heap snapshot JSON (.heapsnapshot: snapshot.meta, nodes, edges, strings), about 1.2 MB each
|
| 21 |
Origin: test fixtures of the Chrome DevTools MCP server heap snapshot processor, recorded from the d8 shell (tool_fixture); the server source is not fetched, not bundled and not run
|
| 22 |
Check: Final file state: the agent writes, for class NewObject, the number of objects added from heap-1 to heap-3 and from heap-2 to heap-3 (the # New column of the DevTools Memory panel Comparison view) to a result file; require exact integer equality with 7 and 5
|
campaign_files/2026-10-gt-browser-tests-2/chrome-har-perflogs/README.md
CHANGED
|
@@ -1,12 +1,12 @@
|
|
| 1 |
# chrome-har-perflogs
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: JSON array of 7138 DevTools protocol messages (Network.* and Tracing.dataCollected) as input; HAR 1.2 JSON as output.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://github.com/sitespeedio/chrome-har. Kind: test or example files shipped with a tool. Regression perflog and test of the chrome-har converter used by sitespeed.io and browsertime (tool_fixture).
|
| 8 |
|
| 9 |
-
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream.
|
| 10 |
|
| 11 |
**Tools to open and check:** Node chrome-har `harFromMessages(perflog)` or any script that turns Chrome DevTools protocol Network events into HAR 1.2 JSON; headless Chrome produces the perflog via chromedriver or CDP
|
| 12 |
|
|
|
|
| 1 |
# chrome-har-perflogs
|
| 2 |
|
| 3 |
+
**What this is:** Files published by Tobias Lidskog, Peter Hedenskog and Jonathan Lee (sitespeed.io). Collection theme: Browser automation: tests shipped with browser automation tools (CDP performance log to HAR converter).
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: JSON array of 7138 DevTools protocol messages (Network.* and Tracing.dataCollected) as input; HAR 1.2 JSON as output.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://github.com/sitespeedio/chrome-har. Kind: test or example files shipped with a tool. Regression perflog and test of the chrome-har converter used by sitespeed.io and browsertime (tool_fixture).
|
| 8 |
|
| 9 |
+
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. Each file names companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
**Tools to open and check:** Node chrome-har `harFromMessages(perflog)` or any script that turns Chrome DevTools protocol Network events into HAR 1.2 JSON; headless Chrome produces the perflog via chromedriver or CDP
|
| 12 |
|
campaign_files/2026-10-gt-browser-tests-2/chrome-recorder-cypress-export-tests/README.md
CHANGED
|
@@ -1,12 +1,12 @@
|
|
| 1 |
# chrome-recorder-cypress-export-tests
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: TypeScript test file; each case builds a Recorder step or flow object (Chrome DevTools Recorder JSON schema of @puppeteer/replay) inline and states the expected Cypress code string inline.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: cypress-io/cypress-chrome-recorder. Kind: test or example files shipped with a tool. Unit tests of the Cypress exporter for the Chrome DevTools Recorder (tool_fixture); the exporter source is not fetched, not bundled and not run.
|
| 8 |
|
| 9 |
-
**Self-contained:** The file is self-contained.
|
| 10 |
|
| 11 |
**Tools to open and check:** @cypress/chrome-recorder CLI (npx @cypress/chrome-recorder recording.json) or its Node API on the Recorder JSON, or a script that maps each @puppeteer/replay step to a Cypress command
|
| 12 |
|
|
|
|
| 1 |
# chrome-recorder-cypress-export-tests
|
| 2 |
|
| 3 |
+
**What this is:** Files published by Cypress.io, cypress-io/cypress-chrome-recorder. Collection theme: Browser automation: tests shipped with browser automation tools (recorders and code exporters for Chrome DevTools Recorder and Selenium IDE, HAR converters, DevTools trace and heap snapshot processors).
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: TypeScript test file; each case builds a Recorder step or flow object (Chrome DevTools Recorder JSON schema of @puppeteer/replay) inline and states the expected Cypress code string inline.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: cypress-io/cypress-chrome-recorder. Kind: test or example files shipped with a tool. Unit tests of the Cypress exporter for the Chrome DevTools Recorder (tool_fixture); the exporter source is not fetched, not bundled and not run.
|
| 8 |
|
| 9 |
+
**Self-contained:** The file is self-contained. Each file names companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
**Tools to open and check:** @cypress/chrome-recorder CLI (npx @cypress/chrome-recorder recording.json) or its Node API on the Recorder JSON, or a script that maps each @puppeteer/replay step to a Cypress command
|
| 12 |
|
campaign_files/2026-10-gt-browser-tests-2/chrome-recorder-nightwatch-export-tests/README.md
CHANGED
|
@@ -1,12 +1,12 @@
|
|
| 1 |
# chrome-recorder-nightwatch-export-tests
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: TypeScript test file; each case builds a Recorder step or flow object (Chrome DevTools Recorder JSON schema of @puppeteer/replay) inline and states the expected Nightwatch code string inline.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: nightwatchjs/nightwatch-chrome-recorder. Kind: test or example files shipped with a tool. Unit tests of the Nightwatch exporter for the Chrome DevTools Recorder (tool_fixture); the exporter source is not fetched, not bundled and not run.
|
| 8 |
|
| 9 |
-
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream.
|
| 10 |
|
| 11 |
**Tools to open and check:** @nightwatch/chrome-recorder CLI (npx @nightwatch/chrome-recorder recording.json) or its Node API on the Recorder JSON, or a script that maps each @puppeteer/replay step to a Nightwatch command
|
| 12 |
|
|
|
|
| 1 |
# chrome-recorder-nightwatch-export-tests
|
| 2 |
|
| 3 |
+
**What this is:** Files published by BrowserStack (Nightwatch project), nightwatchjs/nightwatch-chrome-recorder. Collection theme: Browser automation: tests shipped with browser automation tools (recorders and code exporters for Chrome DevTools Recorder and Selenium IDE, HAR converters, DevTools trace and heap snapshot processors).
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: TypeScript test file; each case builds a Recorder step or flow object (Chrome DevTools Recorder JSON schema of @puppeteer/replay) inline and states the expected Nightwatch code string inline.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: nightwatchjs/nightwatch-chrome-recorder. Kind: test or example files shipped with a tool. Unit tests of the Nightwatch exporter for the Chrome DevTools Recorder (tool_fixture); the exporter source is not fetched, not bundled and not run.
|
| 8 |
|
| 9 |
+
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. Each file names companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
**Tools to open and check:** @nightwatch/chrome-recorder CLI (npx @nightwatch/chrome-recorder recording.json) or its Node API on the Recorder JSON, or a script that maps each @puppeteer/replay step to a Nightwatch command
|
| 12 |
|
campaign_files/2026-10-gt-browser-tests-2/chrome-recorder-webdriverio-export-tests/README.md
CHANGED
|
@@ -1,12 +1,12 @@
|
|
| 1 |
# chrome-recorder-webdriverio-export-tests
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: TypeScript test file; each case builds a Recorder step or flow object (Chrome DevTools Recorder JSON schema of @puppeteer/replay) inline and states the expected WebdriverIO code string inline.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: webdriverio/chrome-recorder. Kind: test or example files shipped with a tool. Unit tests of the WebdriverIO exporter for the Chrome DevTools Recorder (tool_fixture); the exporter source is not fetched, not bundled and not run.
|
| 8 |
|
| 9 |
-
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream.
|
| 10 |
|
| 11 |
**Tools to open and check:** @wdio/chrome-recorder CLI (npx @wdio/chrome-recorder recording.json) or its Node API on the Recorder JSON, or a script that maps each @puppeteer/replay step to a WebdriverIO command
|
| 12 |
|
|
|
|
| 1 |
# chrome-recorder-webdriverio-export-tests
|
| 2 |
|
| 3 |
+
**What this is:** Files published by OpenJS Foundation (WebdriverIO project), webdriverio/chrome-recorder. Collection theme: Browser automation: tests shipped with browser automation tools (recorders and code exporters for Chrome DevTools Recorder and Selenium IDE, HAR converters, DevTools trace and heap snapshot processors).
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: TypeScript test file; each case builds a Recorder step or flow object (Chrome DevTools Recorder JSON schema of @puppeteer/replay) inline and states the expected WebdriverIO code string inline.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: webdriverio/chrome-recorder. Kind: test or example files shipped with a tool. Unit tests of the WebdriverIO exporter for the Chrome DevTools Recorder (tool_fixture); the exporter source is not fetched, not bundled and not run.
|
| 8 |
|
| 9 |
+
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. Each file names companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
**Tools to open and check:** @wdio/chrome-recorder CLI (npx @wdio/chrome-recorder recording.json) or its Node API on the Recorder JSON, or a script that maps each @puppeteer/replay step to a WebdriverIO command
|
| 12 |
|
campaign_files/2026-10-gt-browser-tests-2/chromium-bidi-unit-tests/README.md
CHANGED
|
@@ -1,12 +1,12 @@
|
|
| 1 |
# chromium-bidi-unit-tests
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: Node:test test file (TypeScript) with chai assertions; inputs and expected values inline; node:test test file (TypeScript) with a table of cases (STRING_FORMAT_TEST_CASES: input remote value and the expected text per specifier) and chai assertions; mocha and chai test file (TypeScript) with each URL and the expected boolean inline; mocha and chai test file (TypeScript) with each string (as escapes) and the expected boolean inline.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: GoogleChromeLabs/chromium-bidi. Kind: test or example files shipped with a tool. Unit tests of the Chromium WebDriver BiDi mapper (tool_fixture); the mapper source is not fetched, not bundled and not run; unit tests of the Chromium WebDriver BiDi mapper log helper (tool_fixture); the mapper source is not fetched, not bundled and not run; unit tests of the chromium-bidi URL helpers (tool_fixture); the library source is not fetched, not bundled and not run; unit tests of the chromium-bidi grapheme tools (tool_fixture); the library source is not fetched, not bundled and not run.
|
| 8 |
|
| 9 |
-
**Self-contained:**
|
| 10 |
|
| 11 |
**Tools to open and check:** a script (TypeScript or any language) that implements the conversions between WebDriver BiDi and Chrome DevTools protocol network headers and cookies and the BiDi URL pattern match, and writes the results; the DevTools Network panel shows the same headers, its request blocking takes URL patterns and the Application panel edits the same cookies; a script that formats the console arguments (WebDriver BiDi script.RemoteValue objects) with the console format specifiers %d %f %s %o %O %c and writes the message text; the DevTools Console panel renders the same console.log calls; a script using the WHATWG URL parser (node URL or python urllib.parse) that classifies the URLs; chromium-bidi runs headless as the BiDi mapper of Chrome; a script using Intl.Segmenter with granularity grapheme (node) or the regex module \X (python); chromium-bidi runs headless as the BiDi mapper
|
| 12 |
|
|
|
|
| 1 |
# chromium-bidi-unit-tests
|
| 2 |
|
| 3 |
+
**What this is:** Files published by Google LLC (Chromium BiDi project), GoogleChromeLabs/chromium-bidi. Collection theme: Browser automation: Chrome DevTools protocol and WebDriver BiDi protocol tests, and the tests shipped with browser automation tools (recorders and code exporters, HAR builders and converters, DevTools trace processors).
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: Node:test test file (TypeScript) with chai assertions; inputs and expected values inline; node:test test file (TypeScript) with a table of cases (STRING_FORMAT_TEST_CASES: input remote value and the expected text per specifier) and chai assertions; mocha and chai test file (TypeScript) with each URL and the expected boolean inline; mocha and chai test file (TypeScript) with each string (as escapes) and the expected boolean inline.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: GoogleChromeLabs/chromium-bidi. Kind: test or example files shipped with a tool. Unit tests of the Chromium WebDriver BiDi mapper (tool_fixture); the mapper source is not fetched, not bundled and not run; unit tests of the Chromium WebDriver BiDi mapper log helper (tool_fixture); the mapper source is not fetched, not bundled and not run; unit tests of the chromium-bidi URL helpers (tool_fixture); the library source is not fetched, not bundled and not run; unit tests of the chromium-bidi grapheme tools (tool_fixture); the library source is not fetched, not bundled and not run.
|
| 8 |
|
| 9 |
+
**Self-contained:** Some files are self-contained; the others are used together with other upstream files. Each file names companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
**Tools to open and check:** a script (TypeScript or any language) that implements the conversions between WebDriver BiDi and Chrome DevTools protocol network headers and cookies and the BiDi URL pattern match, and writes the results; the DevTools Network panel shows the same headers, its request blocking takes URL patterns and the Application panel edits the same cookies; a script that formats the console arguments (WebDriver BiDi script.RemoteValue objects) with the console format specifiers %d %f %s %o %O %c and writes the message text; the DevTools Console panel renders the same console.log calls; a script using the WHATWG URL parser (node URL or python urllib.parse) that classifies the URLs; chromium-bidi runs headless as the BiDi mapper of Chrome; a script using Intl.Segmenter with granularity grapheme (node) or the regex module \X (python); chromium-bidi runs headless as the BiDi mapper
|
| 12 |
|
campaign_files/2026-10-gt-browser-tests-2/chromium-policy-pref-mapping/README.md
CHANGED
|
@@ -1,12 +1,12 @@
|
|
| 1 |
# chromium-policy-pref-mapping
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: Chromium policy_pref_mapping JSON (list of PolicyTestCase objects with os, can_be_recommended and either policy_pref_mapping_tests or simple_policy_pref_mapping_test); Chromium policy_pref_mapping JSON (list of PolicyTestCase objects with os, can_be_recommended and simple_policy_pref_mapping_test {pref_name, default_value, values_to_test}).
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://github.com/chromium/chromium. Kind: test or example files shipped with a tool. Test data of Chromium's PolicyPrefsTest, which applies each policy and checks the resulting pref values (tool_fixture).
|
| 8 |
|
| 9 |
-
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream.
|
| 10 |
|
| 11 |
**Tools to open and check:** write the policy as JSON into the managed-policy directory (/etc/opt/chrome/policies/managed/*.json for Chrome or /etc/chromium/policies/managed/*.json for Chromium on Linux, a plist via defaults on macOS, the registry via reg add on Windows) with a text editor, jq or a script; the user-setting direction edits the pref in the profile's Preferences JSON with jq while the browser is closed; Chrome or Chromium can then be started headless (--headless) to load them
|
| 12 |
|
|
|
|
| 1 |
# chromium-policy-pref-mapping
|
| 2 |
|
| 3 |
+
**What this is:** Files published by The Chromium Authors (Chromium project, GitHub mirror of chromium.googlesource.com/chromium/src). Collection theme: Desktop and application settings: configuration formats of desktop environments and common applications, and the tests of settings tools.
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: Chromium policy_pref_mapping JSON (list of PolicyTestCase objects with os, can_be_recommended and either policy_pref_mapping_tests or simple_policy_pref_mapping_test); Chromium policy_pref_mapping JSON (list of PolicyTestCase objects with os, can_be_recommended and simple_policy_pref_mapping_test {pref_name, default_value, values_to_test}).
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://github.com/chromium/chromium. Kind: test or example files shipped with a tool. Test data of Chromium's PolicyPrefsTest, which applies each policy and checks the resulting pref values (tool_fixture).
|
| 8 |
|
| 9 |
+
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. Each file names companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
**Tools to open and check:** write the policy as JSON into the managed-policy directory (/etc/opt/chrome/policies/managed/*.json for Chrome or /etc/chromium/policies/managed/*.json for Chromium on Linux, a plist via defaults on macOS, the registry via reg add on Windows) with a text editor, jq or a script; the user-setting direction edits the pref in the profile's Preferences JSON with jq while the browser is closed; Chrome or Chromium can then be started headless (--headless) to load them
|
| 12 |
|
campaign_files/2026-10-gt-browser-tests-2/coach-core-merge-tests/README.md
CHANGED
|
@@ -1,12 +1,12 @@
|
|
| 1 |
# coach-core-merge-tests
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: Ava test file plus three JSON advice result files (DOM result, HAR result, HAR result with an override).
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: sitespeedio/coach-core. Kind: test or example files shipped with a tool. Unit tests and fixtures of the coach-core advice merge (tool_fixture); the library source is not fetched, not bundled and not run.
|
| 8 |
|
| 9 |
-
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream.
|
| 10 |
|
| 11 |
**Tools to open and check:** a script (node or jq) that merges the two JSON advice files; the coach-core CLI or sitespeed.io run headless with --coach produces the merged result
|
| 12 |
|
|
|
|
| 1 |
# coach-core-merge-tests
|
| 2 |
|
| 3 |
+
**What this is:** Files published by sitespeed.io (Coach project), sitespeedio/coach-core. Collection theme: Browser automation: Chrome DevTools protocol and WebDriver BiDi protocol tests, and the tests shipped with browser automation tools (recorders and code exporters, HAR builders and converters, DevTools trace processors).
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: Ava test file plus three JSON advice result files (DOM result, HAR result, HAR result with an override).
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: sitespeedio/coach-core. Kind: test or example files shipped with a tool. Unit tests and fixtures of the coach-core advice merge (tool_fixture); the library source is not fetched, not bundled and not run.
|
| 8 |
|
| 9 |
+
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. Each file names companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
**Tools to open and check:** a script (node or jq) that merges the two JSON advice files; the coach-core CLI or sitespeed.io run headless with --coach produces the merged result
|
| 12 |
|
campaign_files/2026-10-hw-eda-tests-2/buserror-simavr-tests-github/README.md
CHANGED
|
@@ -1,12 +1,12 @@
|
|
| 1 |
# buserror-simavr-tests-github
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: AVR C firmware file (with simavr section macros) compiled by avr-gcc to .axf, plus a host C test program linked against simavr; reference output is UART text in the test program.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream name: buserror/simavr (default branch master, commit d6aed536) tests/, GitHub. Upstream: buserror/simavr. Kind: test or example files shipped with a tool. Simavr's own regression tests: an AVR firmware file plus a host test program that runs it in the emulator and checks the UART text or cycle count; written by the project.
|
| 8 |
|
| 9 |
-
**Self-contained:** Whether each file needs other upstream files is not stated.
|
| 10 |
|
| 11 |
**Tools to open and check:** Tools are named in the check written per file in the notes.
|
| 12 |
|
|
|
|
| 1 |
# buserror-simavr-tests-github
|
| 2 |
|
| 3 |
+
**What this is:** Files published by Michel Pollet and simavr contributors. Collection theme: Firmware on emulators (QEMU and Renode examples and tests with expected output).
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: AVR C firmware file (with simavr section macros) compiled by avr-gcc to .axf, plus a host C test program linked against simavr; reference output is UART text in the test program.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream name: buserror/simavr (default branch master, commit d6aed536) tests/, GitHub. Upstream: buserror/simavr. Kind: test or example files shipped with a tool. Simavr's own regression tests: an AVR firmware file plus a host test program that runs it in the emulator and checks the UART text or cycle count; written by the project.
|
| 8 |
|
| 9 |
+
**Self-contained:** Whether each file needs other upstream files is not stated. Each file names companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
**Tools to open and check:** Tools are named in the check written per file in the notes.
|
| 12 |
|
campaign_files/2026-10-hw-eda-tests-2/cadquery-plugins-community-plugin-collection-for-cadquery/README.md
CHANGED
|
@@ -1,12 +1,12 @@
|
|
| 1 |
# cadquery-plugins-community-plugin-collection-for-cadquery
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: Python test module (pytest or unittest) importing one plugin package from the plugins/ directory, run against CadQuery.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream name: cadquery-plugins (GitHub CadQuery/cadquery-plugins, commit 364500a): community plugin collection for CadQuery. Upstream: CadQuery/cadquery-plugins. Kind: test or example files shipped with a tool. Test written by the plugin author to check a community CadQuery plugin; expected numbers are closed-form geometry or recorded kernel results.
|
| 8 |
|
| 9 |
-
**Self-contained:** Whether each file needs other upstream files is not stated.
|
| 10 |
|
| 11 |
**Tools to open and check:** pytest runs the module from the repository root (pytest tests/test_gear_generator.py); volumes, areas and coordinates read from Volume(), Area() and Center() in the CadQuery Python API; pytest runs the module from the repository root (pytest tests/test_heatserts.py); volumes, areas and coordinates read from Volume(), Area() and Center() in the CadQuery Python API; pytest runs the module from the repository root (pytest tests/test_fragment.py); volumes, areas and coordinates read from Volume(), Area() and Center() in the CadQuery Python API; pytest runs the module from the repository root (pytest tests/test_teardrop.py); volumes, areas and coordinates read from Volume(), Area() and Center() in the CadQuery Python API; pytest runs the module from the repository root (pytest tests/test_apply_to_each_face.py); volumes, areas and coordinates read from Volume(), Area() and Center() in the CadQuery Python API
|
| 12 |
|
|
|
|
| 1 |
# cadquery-plugins-community-plugin-collection-for-cadquery
|
| 2 |
|
| 3 |
+
**What this is:** Files published by CadQuery project (cadquery-plugins contributors). Collection theme: Parametric CAD models (OpenSCAD, CadQuery, FreeCAD scripts with computed dimensions and volumes).
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: Python test module (pytest or unittest) importing one plugin package from the plugins/ directory, run against CadQuery.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream name: cadquery-plugins (GitHub CadQuery/cadquery-plugins, commit 364500a): community plugin collection for CadQuery. Upstream: CadQuery/cadquery-plugins. Kind: test or example files shipped with a tool. Test written by the plugin author to check a community CadQuery plugin; expected numbers are closed-form geometry or recorded kernel results.
|
| 8 |
|
| 9 |
+
**Self-contained:** Whether each file needs other upstream files is not stated. Each file names companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
**Tools to open and check:** pytest runs the module from the repository root (pytest tests/test_gear_generator.py); volumes, areas and coordinates read from Volume(), Area() and Center() in the CadQuery Python API; pytest runs the module from the repository root (pytest tests/test_heatserts.py); volumes, areas and coordinates read from Volume(), Area() and Center() in the CadQuery Python API; pytest runs the module from the repository root (pytest tests/test_fragment.py); volumes, areas and coordinates read from Volume(), Area() and Center() in the CadQuery Python API; pytest runs the module from the repository root (pytest tests/test_teardrop.py); volumes, areas and coordinates read from Volume(), Area() and Center() in the CadQuery Python API; pytest runs the module from the repository root (pytest tests/test_apply_to_each_face.py); volumes, areas and coordinates read from Volume(), Area() and Center() in the CadQuery Python API
|
| 12 |
|
campaign_files/2026-10-hw-eda-tests-2/camotics-gcodetool-regression-tests-github-cauldrondevelopmentllc-camotics/README.md
CHANGED
|
@@ -1,12 +1,12 @@
|
|
| 1 |
# camotics-gcodetool-regression-tests-github-cauldrondevelopmentllc-camotics
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: RS274/NGC G-code text (LinuxCNC-style dialect read by CAMotics); reference output is the gcodetool normalised G-code text with MSG lines.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream name: CAMotics (master at commit e84665f, 2026-03-23) gcodetool regression tests, GitHub CauldronDevelopmentLLC/CAMotics. Upstream: CauldronDevelopmentLLC/CAMotics. Kind: test or example files shipped with a tool. A small upstream regression program written to exercise the interpreter feature named in the title; a small upstream regression program for G53 with an active G92 offset; a small upstream regression program for G10 L1 and G43 tool length compensation; a small upstream regression program for G10 L10 relative tool length setting.
|
| 8 |
|
| 9 |
-
**Self-contained:**
|
| 10 |
|
| 11 |
**Tools to open and check:** CAMotics gcodetool (headless command line G-code parser and evaluator, prints the normalised program): `gcodetool < tests/offsetTests/GlobalTest/data/stdin`; tests/testHarness runs the command of tests/offsetTests/test.json with data/stdin as standard input and checks stdout, stderr and the return code. Other files: see the notes.
|
| 12 |
|
|
|
|
| 1 |
# camotics-gcodetool-regression-tests-github-cauldrondevelopmentllc-camotics
|
| 2 |
|
| 3 |
+
**What this is:** Files published by Cauldron Development LLC (CAMotics project). Collection theme: CNC and 3D printing programs (G-code with interpreter or simulator results).
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: RS274/NGC G-code text (LinuxCNC-style dialect read by CAMotics); reference output is the gcodetool normalised G-code text with MSG lines.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream name: CAMotics (master at commit e84665f, 2026-03-23) gcodetool regression tests, GitHub CauldronDevelopmentLLC/CAMotics. Upstream: CauldronDevelopmentLLC/CAMotics. Kind: test or example files shipped with a tool. A small upstream regression program written to exercise the interpreter feature named in the title; a small upstream regression program for G53 with an active G92 offset; a small upstream regression program for G10 L1 and G43 tool length compensation; a small upstream regression program for G10 L10 relative tool length setting.
|
| 8 |
|
| 9 |
+
**Self-contained:** Some files are self-contained; for the others it is not stated. Each file names companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
**Tools to open and check:** CAMotics gcodetool (headless command line G-code parser and evaluator, prints the normalised program): `gcodetool < tests/offsetTests/GlobalTest/data/stdin`; tests/testHarness runs the command of tests/offsetTests/test.json with data/stdin as standard input and checks stdout, stderr and the return code. Other files: see the notes.
|
| 12 |
|
campaign_files/2026-10-hw-eda-tests-2/cocotb-examples/README.md
CHANGED
|
@@ -1,12 +1,12 @@
|
|
| 1 |
# cocotb-examples
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** Each unit is one upstream folder, delivered as all the files fetched from it, kept at its upstream path. Format: Cocotb example directory: hdl/ DUT sources (SystemVerilog and VHDL), tests/Makefile for the cocotb makefile flow and pytest-runnable Python test module(s).
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: cocotb/cocotb. Kind: test or example files shipped with a tool. Example design and testbench shipped with the cocotb verification framework (tool_fixture).
|
| 8 |
|
| 9 |
-
**Self-contained:** Not self-contained: each unit is used together with other files from the same upstream.
|
| 10 |
|
| 11 |
**Tools to open and check:** Check: In a sandbox with the versions listed in dependencies run make in examples/matrix_multiplier/tests. Two variants are judged. Verilog variant: TOPLEVEL_LANG=verilog and SIM=icarus (both the Makefile defaults, tests/Makefile:4-5). VHDL variant: make TOPLEVEL_LANG=vhdl SIM=nvc (NVC is the open-source simulator the Makefile wires for VHDL, tests/Makefile:48-50; with SIM=ghdl the Makefile skips the run, tests/Makefile:63-66 "Skipping since GHDL doesn't support constants effectively", and test_matrix_multiplier.py:14-15 skips the runner test the same way, so GHDL is not used). Each variant passes when make exits 0 and results.xml has no <failure> element, i.e. the one cocotb test test_random passes its final assert tb.checker.errors == 0 (matrix_multiplier_tests.py:438-470); the same testbench and Python reference model judge both variants. For a write-the-RTL task, hide hdl/matrix_multiplier.sv (Verilog variant) or hdl/matrix_multiplier.vhd (VHDL variant) and keep tests/ unchanged (the directory has no model/); whether hdl/matrix_multiplier_pkg.vhd is given or hidden in the VHDL task is decided when the task is written. In a sandbox with the versions listed in dependencies run make in examples/adder/tests (TOPLEVEL_LANG defaults to verilog at tests/Makefile:7; tests/Makefile sets no SIM, so the simulator is the default of cocotb's own makefile, Makefile.sim:84 `SIM ?= icarus` at the same commit); for the VHDL variant run make TOPLEVEL_LANG=vhdl SIM=ghdl. The unit passes when make exits 0 and results.xml has no <failure> element, i.e. both cocotb tests adder_basic_test and adder_randomised_test pass. For a write-the-RTL task, hide the hdl/ files and keep tests/ and model/ unchanged.
|
| 12 |
|
|
@@ -16,13 +16,13 @@
|
|
| 16 |
|
| 17 |
Units:
|
| 18 |
|
| 19 |
-
- `examples/matrix_multiplier/`
|
| 20 |
Format: cocotb example directory: hdl/ DUT sources (SystemVerilog and VHDL), tests/Makefile for the cocotb makefile flow and pytest-runnable Python test module(s)
|
| 21 |
Origin: example design and testbench shipped with the cocotb verification framework (tool_fixture)
|
| 22 |
Check: In a sandbox with the versions listed in dependencies run make in examples/matrix_multiplier/tests. Two variants are judged. Verilog variant: TOPLEVEL_LANG=verilog and SIM=icarus (both the Makefile defaults, tests/Makefile:4-5). VHDL variant: make TOPLEVEL_LANG=vhdl SIM=nvc (NVC is the open-source simulator the Makefile wires for VHDL, tests/Makefile:48-50; with SIM=ghdl the Makefile skips the run, tests/Makefile:63-66 "Skipping since GHDL doesn't support constants effectively", and test_matrix_multiplier.py:14-15 skips the runner test the same way, so GHDL is not used). Each variant passes when make exits 0 and results.xml has no <failure> element, i.e. the one cocotb test test_random passes its final assert tb.checker.errors == 0 (matrix_multiplier_tests.py:438-470); the same testbench and Python reference model judge both variants. For a write-the-RTL task, hide hdl/matrix_multiplier.sv (Verilog variant) or hdl/matrix_multiplier.vhd (VHDL variant) and keep tests/ unchanged (the directory has no model/); whether hdl/matrix_multiplier_pkg.vhd is given or hidden in the VHDL task is decided when the task is written.
|
| 23 |
Companions (not included): LICENSE
|
| 24 |
Dependencies: cocotb at commit 1f037538302fbb176e4f84dd249f0415aaf2fec5; open source, not packed; Icarus Verilog v13_0 (iverilog and vvp; upstream does not pin it; latest release on or before the unit commit date 2026-10-05, GitHub release published 2026-03-02, prerelease s20251012 not counted; https://github.com/steveicarus/iverilog/releases/tag/v13_0); open source, not packed; NVC r1.23.0 (VHDL variant only; upstream does not pin it; latest release on or before the unit commit date 2026-10-05, GitHub release published 2026-09-19T17:02:33Z, read from https://api.github.com/repos/nickg/nvc/releases on 2026-10-06; https://github.com/nickg/nvc/releases/tag/r1.23.0); open source, not packed
|
| 25 |
-
- `examples/adder/`
|
| 26 |
Format: cocotb example directory: hdl/ DUT sources (SystemVerilog and VHDL), tests/Makefile for the cocotb makefile flow and pytest-runnable Python test module(s)
|
| 27 |
Origin: example design and testbench shipped with the cocotb verification framework (tool_fixture)
|
| 28 |
Check: In a sandbox with the versions listed in dependencies run make in examples/adder/tests (TOPLEVEL_LANG defaults to verilog at tests/Makefile:7; tests/Makefile sets no SIM, so the simulator is the default of cocotb's own makefile, Makefile.sim:84 `SIM ?= icarus` at the same commit); for the VHDL variant run make TOPLEVEL_LANG=vhdl SIM=ghdl. The unit passes when make exits 0 and results.xml has no <failure> element, i.e. both cocotb tests adder_basic_test and adder_randomised_test pass. For a write-the-RTL task, hide the hdl/ files and keep tests/ and model/ unchanged.
|
|
|
|
| 1 |
# cocotb-examples
|
| 2 |
|
| 3 |
+
**What this is:** Units published by cocotb contributors (FOSSi Foundation project). Collection theme: RTL designs and testbenches (modules in open-source IP core and SoC repositories with cocotb or Verilator tests and expected outputs).
|
| 4 |
|
| 5 |
**What one unit is:** Each unit is one upstream folder, delivered as all the files fetched from it, kept at its upstream path. Format: Cocotb example directory: hdl/ DUT sources (SystemVerilog and VHDL), tests/Makefile for the cocotb makefile flow and pytest-runnable Python test module(s).
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: cocotb/cocotb. Kind: test or example files shipped with a tool. Example design and testbench shipped with the cocotb verification framework (tool_fixture).
|
| 8 |
|
| 9 |
+
**Self-contained:** Not self-contained: each unit is used together with other files from the same upstream. Each unit names companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes. Dependencies named upstream are listed per unit in the notes.
|
| 10 |
|
| 11 |
**Tools to open and check:** Check: In a sandbox with the versions listed in dependencies run make in examples/matrix_multiplier/tests. Two variants are judged. Verilog variant: TOPLEVEL_LANG=verilog and SIM=icarus (both the Makefile defaults, tests/Makefile:4-5). VHDL variant: make TOPLEVEL_LANG=vhdl SIM=nvc (NVC is the open-source simulator the Makefile wires for VHDL, tests/Makefile:48-50; with SIM=ghdl the Makefile skips the run, tests/Makefile:63-66 "Skipping since GHDL doesn't support constants effectively", and test_matrix_multiplier.py:14-15 skips the runner test the same way, so GHDL is not used). Each variant passes when make exits 0 and results.xml has no <failure> element, i.e. the one cocotb test test_random passes its final assert tb.checker.errors == 0 (matrix_multiplier_tests.py:438-470); the same testbench and Python reference model judge both variants. For a write-the-RTL task, hide hdl/matrix_multiplier.sv (Verilog variant) or hdl/matrix_multiplier.vhd (VHDL variant) and keep tests/ unchanged (the directory has no model/); whether hdl/matrix_multiplier_pkg.vhd is given or hidden in the VHDL task is decided when the task is written. In a sandbox with the versions listed in dependencies run make in examples/adder/tests (TOPLEVEL_LANG defaults to verilog at tests/Makefile:7; tests/Makefile sets no SIM, so the simulator is the default of cocotb's own makefile, Makefile.sim:84 `SIM ?= icarus` at the same commit); for the VHDL variant run make TOPLEVEL_LANG=vhdl SIM=ghdl. The unit passes when make exits 0 and results.xml has no <failure> element, i.e. both cocotb tests adder_basic_test and adder_randomised_test pass. For a write-the-RTL task, hide the hdl/ files and keep tests/ and model/ unchanged.
|
| 12 |
|
|
|
|
| 16 |
|
| 17 |
Units:
|
| 18 |
|
| 19 |
+
- `examples/matrix_multiplier/`: Cocotb example matrix_multiplier: parameterised matrix multiplier in SystemVerilog and VHDL with a cocotb testbench that has a Python reference model and scoreboard.
|
| 20 |
Format: cocotb example directory: hdl/ DUT sources (SystemVerilog and VHDL), tests/Makefile for the cocotb makefile flow and pytest-runnable Python test module(s)
|
| 21 |
Origin: example design and testbench shipped with the cocotb verification framework (tool_fixture)
|
| 22 |
Check: In a sandbox with the versions listed in dependencies run make in examples/matrix_multiplier/tests. Two variants are judged. Verilog variant: TOPLEVEL_LANG=verilog and SIM=icarus (both the Makefile defaults, tests/Makefile:4-5). VHDL variant: make TOPLEVEL_LANG=vhdl SIM=nvc (NVC is the open-source simulator the Makefile wires for VHDL, tests/Makefile:48-50; with SIM=ghdl the Makefile skips the run, tests/Makefile:63-66 "Skipping since GHDL doesn't support constants effectively", and test_matrix_multiplier.py:14-15 skips the runner test the same way, so GHDL is not used). Each variant passes when make exits 0 and results.xml has no <failure> element, i.e. the one cocotb test test_random passes its final assert tb.checker.errors == 0 (matrix_multiplier_tests.py:438-470); the same testbench and Python reference model judge both variants. For a write-the-RTL task, hide hdl/matrix_multiplier.sv (Verilog variant) or hdl/matrix_multiplier.vhd (VHDL variant) and keep tests/ unchanged (the directory has no model/); whether hdl/matrix_multiplier_pkg.vhd is given or hidden in the VHDL task is decided when the task is written.
|
| 23 |
Companions (not included): LICENSE
|
| 24 |
Dependencies: cocotb at commit 1f037538302fbb176e4f84dd249f0415aaf2fec5; open source, not packed; Icarus Verilog v13_0 (iverilog and vvp; upstream does not pin it; latest release on or before the unit commit date 2026-10-05, GitHub release published 2026-03-02, prerelease s20251012 not counted; https://github.com/steveicarus/iverilog/releases/tag/v13_0); open source, not packed; NVC r1.23.0 (VHDL variant only; upstream does not pin it; latest release on or before the unit commit date 2026-10-05, GitHub release published 2026-09-19T17:02:33Z, read from https://api.github.com/repos/nickg/nvc/releases on 2026-10-06; https://github.com/nickg/nvc/releases/tag/r1.23.0); open source, not packed
|
| 25 |
+
- `examples/adder/`: Cocotb example adder: parameterised adder in SystemVerilog and VHDL with a cocotb testbench checking against a Python reference model.
|
| 26 |
Format: cocotb example directory: hdl/ DUT sources (SystemVerilog and VHDL), tests/Makefile for the cocotb makefile flow and pytest-runnable Python test module(s)
|
| 27 |
Origin: example design and testbench shipped with the cocotb verification framework (tool_fixture)
|
| 28 |
Check: In a sandbox with the versions listed in dependencies run make in examples/adder/tests (TOPLEVEL_LANG defaults to verilog at tests/Makefile:7; tests/Makefile sets no SIM, so the simulator is the default of cocotb's own makefile, Makefile.sim:84 `SIM ?= icarus` at the same commit); for the VHDL variant run make TOPLEVEL_LANG=vhdl SIM=ghdl. The unit passes when make exits 0 and results.xml has no <failure> element, i.e. both cocotb tests adder_basic_test and adder_randomised_test pass. For a write-the-RTL task, hide the hdl/ files and keep tests/ and model/ unchanged.
|
campaign_files/2026-10-hw-eda-tests-2/cocotb/README.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
| 1 |
# cocotb
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** Each unit is one upstream folder, delivered as all the files fetched from it, kept at its upstream path. Format: SystemVerilog DUT with a cocotb (Python) testbench and a cocotb make file.
|
| 6 |
|
|
@@ -16,7 +16,7 @@
|
|
| 16 |
|
| 17 |
Units:
|
| 18 |
|
| 19 |
-
- `examples/first_steps/`
|
| 20 |
Format: SystemVerilog DUT with a cocotb (Python) testbench and a cocotb make file
|
| 21 |
Origin: self-checking cocotb test written by the cocotb maintainers for a tutorial DUT (tool_fixture): expected values are fixed in the test
|
| 22 |
Check: Build in a sandbox with the versions listed in dependencies: in examples/first_steps run `make` (SIM = icarus). The unit passes when the cocotb results.xml reports no failed test; only test_self_checking compares against expected values, the other seven tests are tutorial steps that pass when they run without error. For a write-the-RTL task, hide or replace counter.sv and keep counter_tests.py unchanged.
|
|
|
|
| 1 |
# cocotb
|
| 2 |
|
| 3 |
+
**What this is:** Units published by cocotb contributors. Collection theme: RTL designs and testbenches (modules in open-source IP core and SoC repositories with cocotb or Verilator tests and expected outputs).
|
| 4 |
|
| 5 |
**What one unit is:** Each unit is one upstream folder, delivered as all the files fetched from it, kept at its upstream path. Format: SystemVerilog DUT with a cocotb (Python) testbench and a cocotb make file.
|
| 6 |
|
|
|
|
| 16 |
|
| 17 |
Units:
|
| 18 |
|
| 19 |
+
- `examples/first_steps/`: Cocotb first_steps: 8-bit loadable counter in SystemVerilog with a self-checking cocotb test.
|
| 20 |
Format: SystemVerilog DUT with a cocotb (Python) testbench and a cocotb make file
|
| 21 |
Origin: self-checking cocotb test written by the cocotb maintainers for a tutorial DUT (tool_fixture): expected values are fixed in the test
|
| 22 |
Check: Build in a sandbox with the versions listed in dependencies: in examples/first_steps run `make` (SIM = icarus). The unit passes when the cocotb results.xml reports no failed test; only test_self_checking compares against expected values, the other seven tests are tutorial steps that pass when they run without error. For a write-the-RTL task, hide or replace counter.sv and keep counter_tests.py unchanged.
|
campaign_files/2026-10-m-issue-trackers-2/buildroot-buildroot/README.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
| 1 |
# buildroot-buildroot
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. A file whose upstream path has no folder is kept in a folder named after its unit. Format: Pipermail month archive, mbox text gzip-compressed: full headers (From with obfuscated address and name, Date, Subject, Message-ID, In-Reply-To, References) and plain-text bodies. Cut the thread by root Message-ID through the In-Reply-To closure (last References entry when In-Reply-To is missing).
|
| 6 |
|
|
|
|
| 1 |
# buildroot-buildroot
|
| 2 |
|
| 3 |
+
**What this is:** Files published by Buildroot project (lists.buildroot.org Mailman, buildroot list). Collection theme: Public mailing-list archives (Mailman, Pipermail, HyperKitty, public-inbox; taken per thread).
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. A file whose upstream path has no folder is kept in a folder named after its unit. Format: Pipermail month archive, mbox text gzip-compressed: full headers (From with obfuscated address and name, Date, Subject, Message-ID, In-Reply-To, References) and plain-text bodies. Cut the thread by root Message-ID through the In-Reply-To closure (last References entry when In-Reply-To is missing).
|
| 6 |
|
campaign_files/2026-10-m-issue-trackers-2/busybox-net-busybox/README.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
| 1 |
# busybox-net-busybox
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. A file whose upstream path has no folder is kept in a folder named after its unit. Format: Pipermail month archive, mbox text gzip-compressed: full headers (From with obfuscated address and name, Date, Subject, Message-ID, In-Reply-To, References) and plain-text bodies. Cut the thread by root Message-ID through the In-Reply-To closure (last References entry when In-Reply-To is missing).
|
| 6 |
|
|
|
|
| 1 |
# busybox-net-busybox
|
| 2 |
|
| 3 |
+
**What this is:** Files published by BusyBox project (lists.busybox.net Mailman, busybox list). Collection theme: Public mailing-list archives (Mailman, Pipermail, HyperKitty, public-inbox; taken per thread).
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. A file whose upstream path has no folder is kept in a folder named after its unit. Format: Pipermail month archive, mbox text gzip-compressed: full headers (From with obfuscated address and name, Date, Subject, Message-ID, In-Reply-To, References) and plain-text bodies. Cut the thread by root Message-ID through the In-Reply-To closure (last References entry when In-Reply-To is missing).
|
| 6 |
|
campaign_files/2026-10-m-issue-trackers-2/camunda-jira/README.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
| 1 |
# camunda-jira
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: Jira REST API v2 issue JSON with expand=changelog: fields (status, resolution, resolutiondate, assignee, reporter, comment.comments[]) and changelog.histories[] (author, created, items[] with field, fromString, toString).
|
| 6 |
|
|
|
|
| 1 |
# camunda-jira
|
| 2 |
|
| 3 |
+
**What this is:** Files published by Camunda's self-hosted public Jira jira.camunda.com, project Camunda Optimize (OPT). Collection theme: Self-hosted issue trackers (Bugzilla, Jira, Trac, Redmine, Launchpad and similar, with status transitions, comments and assignment history).
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: Jira REST API v2 issue JSON with expand=changelog: fields (status, resolution, resolutiondate, assignee, reporter, comment.comments[]) and changelog.histories[] (author, created, items[] with field, fromString, toString).
|
| 6 |
|
campaign_files/2026-10-m-issue-trackers-2/carouselbuses-passenger-gtfs/README.md
CHANGED
|
@@ -1,12 +1,12 @@
|
|
| 1 |
# carouselbuses-passenger-gtfs
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** Each unit is one file read out of an upstream archive (the archive's address is in the notes), kept at its upstream path. A file whose upstream path has no folder is kept in a folder named after its unit. Format: text/csv (GTFS Schedule calendar.txt; companions calendar_dates.txt, agency.txt).
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://s3-eu-west-1.amazonaws.com/passenger-sources/carouselbuses/gtfs/carouselbuses_1789714852.zip. Kind: real files published upstream. Live static GTFS feed published by Carousel Buses (published through Passenger, data.discoverpassenger.com) at https://s3-eu-west-1.amazonaws.com/passenger-sources/carouselbuses/gtfs/carouselbuses_1789714852.zip. calendar.txt and its companions were read by member out of the zip with HTTP Range requests (spec general rule 4: by member); kept as a snapshot pinned by sha256.
|
| 8 |
|
| 9 |
-
**Self-contained:** The unit is self-contained.
|
| 10 |
|
| 11 |
**Tools to open and check:** Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
|
| 12 |
|
|
|
|
| 1 |
# carouselbuses-passenger-gtfs
|
| 2 |
|
| 3 |
+
**What this is:** Units published by Carousel Buses (published through Passenger, data.discoverpassenger.com). Collection theme: Public transit GTFS calendars (calendar.txt and calendar_dates.txt).
|
| 4 |
|
| 5 |
**What one unit is:** Each unit is one file read out of an upstream archive (the archive's address is in the notes), kept at its upstream path. A file whose upstream path has no folder is kept in a folder named after its unit. Format: text/csv (GTFS Schedule calendar.txt; companions calendar_dates.txt, agency.txt).
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://s3-eu-west-1.amazonaws.com/passenger-sources/carouselbuses/gtfs/carouselbuses_1789714852.zip. Kind: real files published upstream. Live static GTFS feed published by Carousel Buses (published through Passenger, data.discoverpassenger.com) at https://s3-eu-west-1.amazonaws.com/passenger-sources/carouselbuses/gtfs/carouselbuses_1789714852.zip. calendar.txt and its companions were read by member out of the zip with HTTP Range requests (spec general rule 4: by member); kept as a snapshot pinned by sha256.
|
| 8 |
|
| 9 |
+
**Self-contained:** The unit is self-contained. Each unit names companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes.
|
| 10 |
|
| 11 |
**Tools to open and check:** Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
|
| 12 |
|
campaign_files/2026-10-m-issue-trackers-2/centos-centos/README.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
| 1 |
# centos-centos
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. A file whose upstream path has no folder is kept in a folder named after its unit. Format: Pipermail month archive, mbox text gzip-compressed: full headers (From with obfuscated address and name, Date, Subject, Message-ID, In-Reply-To, References) and plain-text bodies. Cut the thread by root Message-ID through the In-Reply-To closure (last References entry when In-Reply-To is missing).
|
| 6 |
|
|
|
|
| 1 |
# centos-centos
|
| 2 |
|
| 3 |
+
**What this is:** Files published by The CentOS Project (lists.centos.org Mailman, centos general list). Collection theme: Public mailing-list archives (Mailman, Pipermail, HyperKitty, public-inbox; taken per thread).
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. A file whose upstream path has no folder is kept in a folder named after its unit. Format: Pipermail month archive, mbox text gzip-compressed: full headers (From with obfuscated address and name, Date, Subject, Message-ID, In-Reply-To, References) and plain-text bodies. Cut the thread by root Message-ID through the In-Reply-To closure (last References entry when In-Reply-To is missing).
|
| 6 |
|
campaign_files/2026-10-m-issue-trackers-2/centro-syracuse-gtfs/README.md
CHANGED
|
@@ -1,12 +1,12 @@
|
|
| 1 |
# centro-syracuse-gtfs
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** Each unit is one file read out of an upstream archive (the archive's address is in the notes), kept at its upstream path. A file whose upstream path has no folder is kept in a folder named after its unit. Format: text/csv (GTFS Schedule calendar.txt; companions calendar_dates.txt, agency.txt, feed_info.txt).
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://www.centro.org/CentroGTFS/CentroGTFS.zip. Kind: real files published upstream. Live static GTFS feed published by Central New York Regional Transportation Authority (Centro) at https://www.centro.org/CentroGTFS/CentroGTFS.zip. calendar.txt and its companions were read by member out of the zip with HTTP Range requests (spec general rule 4: by member); kept as a snapshot pinned by sha256.
|
| 8 |
|
| 9 |
-
**Self-contained:** The unit is self-contained.
|
| 10 |
|
| 11 |
**Tools to open and check:** Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
|
| 12 |
|
|
|
|
| 1 |
# centro-syracuse-gtfs
|
| 2 |
|
| 3 |
+
**What this is:** Units published by Central New York Regional Transportation Authority (Centro). Collection theme: Public transit GTFS calendars (calendar.txt and calendar_dates.txt).
|
| 4 |
|
| 5 |
**What one unit is:** Each unit is one file read out of an upstream archive (the archive's address is in the notes), kept at its upstream path. A file whose upstream path has no folder is kept in a folder named after its unit. Format: text/csv (GTFS Schedule calendar.txt; companions calendar_dates.txt, agency.txt, feed_info.txt).
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://www.centro.org/CentroGTFS/CentroGTFS.zip. Kind: real files published upstream. Live static GTFS feed published by Central New York Regional Transportation Authority (Centro) at https://www.centro.org/CentroGTFS/CentroGTFS.zip. calendar.txt and its companions were read by member out of the zip with HTTP Range requests (spec general rule 4: by member); kept as a snapshot pinned by sha256.
|
| 8 |
|
| 9 |
+
**Self-contained:** The unit is self-contained. Each unit names companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes.
|
| 10 |
|
| 11 |
**Tools to open and check:** Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
|
| 12 |
|
campaign_files/2026-10-m-issue-trackers-2/ceph-ceph-users/README.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
| 1 |
# ceph-ceph-users
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. A file whose upstream path has no folder is kept in a folder named after its unit. Format: HyperKitty REST API JSON (?format=json): list of the thread's messages, each with message_id, message_id_hash, subject, sender (address obfuscated with '(a)', mailman_id), sender_name, date (with zone), parent (URL of the parent message, null for the root), children and thread.
|
| 6 |
|
|
|
|
| 1 |
# ceph-ceph-users
|
| 2 |
|
| 3 |
+
**What this is:** Files published by Ceph Foundation (lists.ceph.io Mailman 3 / HyperKitty, ceph-users list). Collection theme: Public mailing-list archives (Mailman, Pipermail, HyperKitty, public-inbox; taken per thread).
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. A file whose upstream path has no folder is kept in a folder named after its unit. Format: HyperKitty REST API JSON (?format=json): list of the thread's messages, each with message_id, message_id_hash, subject, sender (address obfuscated with '(a)', mailman_id), sender_name, date (with zone), parent (URL of the parent message, null for the root), children and thread.
|
| 6 |
|
campaign_files/2026-10-m-issue-trackers-2/clamav-users/README.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
| 1 |
# clamav-users
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. A file whose upstream path has no folder is kept in a folder named after its unit. Format: Pipermail month archive, mbox text gzip-compressed: full headers (From with obfuscated address and name, Date, Subject, Message-ID, In-Reply-To, References) and plain-text bodies. Cut the thread by root Message-ID through the In-Reply-To closure (last References entry when In-Reply-To is missing).
|
| 6 |
|
|
|
|
| 1 |
# clamav-users
|
| 2 |
|
| 3 |
+
**What this is:** Files published by ClamAV project, Cisco Talos (lists.clamav.net Mailman, clamav-users list). Collection theme: Public mailing-list archives (Mailman, Pipermail, HyperKitty, public-inbox; taken per thread).
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. A file whose upstream path has no folder is kept in a folder named after its unit. Format: Pipermail month archive, mbox text gzip-compressed: full headers (From with obfuscated address and name, Date, Subject, Message-ID, In-Reply-To, References) and plain-text bodies. Cut the thread by root Message-ID through the In-Reply-To closure (last References entry when In-Reply-To is missing).
|
| 6 |
|
campaign_files/2026-10-m-issue-trackers-2/clusterlabs-users/README.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
| 1 |
# clusterlabs-users
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. A file whose upstream path has no folder is kept in a folder named after its unit. Format: Pipermail month archive, mbox text gzip-compressed: full headers (From with obfuscated address and name, Date, Subject, Message-ID, In-Reply-To, References) and plain-text bodies. Cut the thread by root Message-ID through the In-Reply-To closure (last References entry when In-Reply-To is missing).
|
| 6 |
|
|
|
|
| 1 |
# clusterlabs-users
|
| 2 |
|
| 3 |
+
**What this is:** Files published by ClusterLabs (lists.clusterlabs.org Mailman, users list). Collection theme: Public mailing-list archives (Mailman, Pipermail, HyperKitty, public-inbox; taken per thread).
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. A file whose upstream path has no folder is kept in a folder named after its unit. Format: Pipermail month archive, mbox text gzip-compressed: full headers (From with obfuscated address and name, Date, Subject, Message-ID, In-Reply-To, References) and plain-text bodies. Cut the thread by root Message-ID through the In-Reply-To closure (last References entry when In-Reply-To is missing).
|
| 6 |
|
campaign_files/2026-10-m-issue-trackers-2/coachservices-passenger-gtfs/README.md
CHANGED
|
@@ -1,12 +1,12 @@
|
|
| 1 |
# coachservices-passenger-gtfs
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** Each unit is one file read out of an upstream archive (the archive's address is in the notes), kept at its upstream path. A file whose upstream path has no folder is kept in a folder named after its unit. Format: text/csv (GTFS Schedule calendar.txt; companions calendar_dates.txt, agency.txt).
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://s3-eu-west-1.amazonaws.com/passenger-sources/coachservices/gtfs/coachservices_1791193056.zip. Kind: real files published upstream. Live static GTFS feed published by Coach Services (published through Passenger, data.discoverpassenger.com) at https://s3-eu-west-1.amazonaws.com/passenger-sources/coachservices/gtfs/coachservices_1791193056.zip. calendar.txt and its companions were read by member out of the zip with HTTP Range requests (spec general rule 4: by member); kept as a snapshot pinned by sha256.
|
| 8 |
|
| 9 |
-
**Self-contained:** The unit is self-contained.
|
| 10 |
|
| 11 |
**Tools to open and check:** Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
|
| 12 |
|
|
|
|
| 1 |
# coachservices-passenger-gtfs
|
| 2 |
|
| 3 |
+
**What this is:** Units published by Coach Services (published through Passenger, data.discoverpassenger.com). Collection theme: Public transit GTFS calendars (calendar.txt and calendar_dates.txt).
|
| 4 |
|
| 5 |
**What one unit is:** Each unit is one file read out of an upstream archive (the archive's address is in the notes), kept at its upstream path. A file whose upstream path has no folder is kept in a folder named after its unit. Format: text/csv (GTFS Schedule calendar.txt; companions calendar_dates.txt, agency.txt).
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://s3-eu-west-1.amazonaws.com/passenger-sources/coachservices/gtfs/coachservices_1791193056.zip. Kind: real files published upstream. Live static GTFS feed published by Coach Services (published through Passenger, data.discoverpassenger.com) at https://s3-eu-west-1.amazonaws.com/passenger-sources/coachservices/gtfs/coachservices_1791193056.zip. calendar.txt and its companions were read by member out of the zip with HTTP Range requests (spec general rule 4: by member); kept as a snapshot pinned by sha256.
|
| 8 |
|
| 9 |
+
**Self-contained:** The unit is self-contained. Each unit names companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes.
|
| 10 |
|
| 11 |
**Tools to open and check:** Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
|
| 12 |
|
campaign_files/2026-10-m-issue-trackers-2/codeberg-beacondb-beacondb-pulls/README.md
CHANGED
|
@@ -1,12 +1,12 @@
|
|
| 1 |
# codeberg-beacondb-beacondb-pulls
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 30 entries, fewer than 50, so it is complete.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://codeberg.org/beacondb/beacondb/pulls/92. Kind: real files published upstream. Live Forgejo REST interface of a closed pull request, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
|
| 8 |
|
| 9 |
-
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream.
|
| 10 |
|
| 11 |
**Tools to open and check:** curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
|
| 12 |
|
|
|
|
| 1 |
# codeberg-beacondb-beacondb-pulls
|
| 2 |
|
| 3 |
+
**What this is:** Files published by beaconDB project, on Codeberg (codeberg.org, Codeberg e.V.). Collection theme: Code hosting platform issue and merge request timelines (GitHub, GitLab, Gitea/Forgejo and similar, as fixed exports or datasets).
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 30 entries, fewer than 50, so it is complete.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://codeberg.org/beacondb/beacondb/pulls/92. Kind: real files published upstream. Live Forgejo REST interface of a closed pull request, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
|
| 8 |
|
| 9 |
+
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. Each file names companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
|
| 10 |
|
| 11 |
**Tools to open and check:** curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
|
| 12 |
|
campaign_files/2026-10-m-issue-trackers-2/codeberg-codeberg-org-pulls/README.md
CHANGED
|
@@ -1,12 +1,12 @@
|
|
| 1 |
# codeberg-codeberg-org-pulls
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 28 entries, fewer than 50, so it is complete. Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 43 entries, fewer than 50, so it is complete.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://codeberg.org/Codeberg/org/pulls/1204; https://codeberg.org/Codeberg/org/pulls/54. Kind: real files published upstream. Live Forgejo REST interface of a closed pull request, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
|
| 8 |
|
| 9 |
-
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream.
|
| 10 |
|
| 11 |
**Tools to open and check:** curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
|
| 12 |
|
|
|
|
| 1 |
# codeberg-codeberg-org-pulls
|
| 2 |
|
| 3 |
+
**What this is:** Files published by Codeberg e.V. (organisation repository), on Codeberg (codeberg.org, Codeberg e.V.). Collection theme: Code hosting platform issue and merge request timelines (GitHub, GitLab, Gitea/Forgejo and similar, as fixed exports or datasets).
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 28 entries, fewer than 50, so it is complete. Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 43 entries, fewer than 50, so it is complete.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://codeberg.org/Codeberg/org/pulls/1204; https://codeberg.org/Codeberg/org/pulls/54. Kind: real files published upstream. Live Forgejo REST interface of a closed pull request, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
|
| 8 |
|
| 9 |
+
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. Each file names companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
|
| 10 |
|
| 11 |
**Tools to open and check:** curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
|
| 12 |
|
campaign_files/2026-10-m-issue-trackers-2/codeberg-emersion-soju-pulls/README.md
CHANGED
|
@@ -1,12 +1,12 @@
|
|
| 1 |
# codeberg-emersion-soju-pulls
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 23 entries, fewer than 50, so it is complete. Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 16 entries, fewer than 50, so it is complete.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://codeberg.org/emersion/soju/pulls/81; https://codeberg.org/emersion/soju/pulls/55. Kind: real files published upstream. Live Forgejo REST interface of a closed pull request, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
|
| 8 |
|
| 9 |
-
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream.
|
| 10 |
|
| 11 |
**Tools to open and check:** curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
|
| 12 |
|
|
|
|
| 1 |
# codeberg-emersion-soju-pulls
|
| 2 |
|
| 3 |
+
**What this is:** Files published by soju IRC bouncer project (emersion), on Codeberg (codeberg.org, Codeberg e.V.). Collection theme: Code hosting platform issue and merge request timelines (GitHub, GitLab, Gitea/Forgejo and similar, as fixed exports or datasets).
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 23 entries, fewer than 50, so it is complete. Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 16 entries, fewer than 50, so it is complete.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://codeberg.org/emersion/soju/pulls/81; https://codeberg.org/emersion/soju/pulls/55. Kind: real files published upstream. Live Forgejo REST interface of a closed pull request, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
|
| 8 |
|
| 9 |
+
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. Each file names companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
|
| 10 |
|
| 11 |
**Tools to open and check:** curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
|
| 12 |
|
campaign_files/2026-10-m-issue-trackers-2/codeberg-evi-editor-evi-pulls/README.md
CHANGED
|
@@ -1,12 +1,12 @@
|
|
| 1 |
# codeberg-evi-editor-evi-pulls
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 18 entries, fewer than 50, so it is complete.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://codeberg.org/evi-editor/evi/pulls/194. Kind: real files published upstream. Live Forgejo REST interface of a closed pull request, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
|
| 8 |
|
| 9 |
-
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream.
|
| 10 |
|
| 11 |
**Tools to open and check:** curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
|
| 12 |
|
|
|
|
| 1 |
# codeberg-evi-editor-evi-pulls
|
| 2 |
|
| 3 |
+
**What this is:** Files published by evi editor project, on Codeberg (codeberg.org, Codeberg e.V.). Collection theme: Code hosting platform issue and merge request timelines (GitHub, GitLab, Gitea/Forgejo and similar, as fixed exports or datasets).
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 18 entries, fewer than 50, so it is complete.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://codeberg.org/evi-editor/evi/pulls/194. Kind: real files published upstream. Live Forgejo REST interface of a closed pull request, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
|
| 8 |
|
| 9 |
+
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. Each file names companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
|
| 10 |
|
| 11 |
**Tools to open and check:** curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
|
| 12 |
|
campaign_files/2026-10-m-issue-trackers-2/codeberg-fediverse-fep-pulls/README.md
CHANGED
|
@@ -1,12 +1,12 @@
|
|
| 1 |
# codeberg-fediverse-fep-pulls
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 22 entries, fewer than 50, so it is complete.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://codeberg.org/fediverse/fep/pulls/885. Kind: real files published upstream. Live Forgejo REST interface of a closed pull request, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
|
| 8 |
|
| 9 |
-
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream.
|
| 10 |
|
| 11 |
**Tools to open and check:** curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
|
| 12 |
|
|
|
|
| 1 |
# codeberg-fediverse-fep-pulls
|
| 2 |
|
| 3 |
+
**What this is:** Files published by Fediverse Enhancement Proposals (FEP) repository, fediverse organisation, on Codeberg (codeberg.org, Codeberg e.V.). Collection theme: Code hosting platform issue and merge request timelines (GitHub, GitLab, Gitea/Forgejo and similar, as fixed exports or datasets).
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 22 entries, fewer than 50, so it is complete.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://codeberg.org/fediverse/fep/pulls/885. Kind: real files published upstream. Live Forgejo REST interface of a closed pull request, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
|
| 8 |
|
| 9 |
+
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. Each file names companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
|
| 10 |
|
| 11 |
**Tools to open and check:** curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
|
| 12 |
|
campaign_files/2026-10-m-issue-trackers-2/codeberg-fitotrack-pulls/README.md
CHANGED
|
@@ -1,12 +1,12 @@
|
|
| 1 |
# codeberg-fitotrack-pulls
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 19 entries, fewer than 50, so it is complete. Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 22 entries, fewer than 50, so it is complete.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://codeberg.org/jannis/FitoTrack/pulls/663; https://codeberg.org/jannis/FitoTrack/pulls/471. Kind: real files published upstream. Live Forgejo REST interface of a closed pull request, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
|
| 8 |
|
| 9 |
-
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream.
|
| 10 |
|
| 11 |
**Tools to open and check:** curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
|
| 12 |
|
|
|
|
| 1 |
# codeberg-fitotrack-pulls
|
| 2 |
|
| 3 |
+
**What this is:** Files published by FitoTrack project (jannis), on Codeberg (codeberg.org, Codeberg e.V.). Collection theme: Code hosting platform issue and merge request timelines (GitHub, GitLab, Gitea/Forgejo and similar, as fixed exports or datasets).
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 19 entries, fewer than 50, so it is complete. Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 22 entries, fewer than 50, so it is complete.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://codeberg.org/jannis/FitoTrack/pulls/663; https://codeberg.org/jannis/FitoTrack/pulls/471. Kind: real files published upstream. Live Forgejo REST interface of a closed pull request, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
|
| 8 |
|
| 9 |
+
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. Each file names companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
|
| 10 |
|
| 11 |
**Tools to open and check:** curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
|
| 12 |
|
campaign_files/2026-10-m-issue-trackers-2/codeberg-forgejo-docs-pulls/README.md
CHANGED
|
@@ -1,12 +1,12 @@
|
|
| 1 |
# codeberg-forgejo-docs-pulls
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 27 entries, fewer than 50, so it is complete. Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 12 entries, fewer than 50, so it is complete.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://codeberg.org/forgejo/docs/pulls/2171; https://codeberg.org/forgejo/docs/pulls/2212. Kind: real files published upstream. Live Forgejo REST interface of a closed pull request, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
|
| 8 |
|
| 9 |
-
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream.
|
| 10 |
|
| 11 |
**Tools to open and check:** curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
|
| 12 |
|
|
|
|
| 1 |
# codeberg-forgejo-docs-pulls
|
| 2 |
|
| 3 |
+
**What this is:** Files published by Forgejo project (documentation repository), on Codeberg (codeberg.org, Codeberg e.V.). Collection theme: Code hosting platform issue and merge request timelines (GitHub, GitLab, Gitea/Forgejo and similar, as fixed exports or datasets).
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 27 entries, fewer than 50, so it is complete. Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 12 entries, fewer than 50, so it is complete.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://codeberg.org/forgejo/docs/pulls/2171; https://codeberg.org/forgejo/docs/pulls/2212. Kind: real files published upstream. Live Forgejo REST interface of a closed pull request, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
|
| 8 |
|
| 9 |
+
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. Each file names companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
|
| 10 |
|
| 11 |
**Tools to open and check:** curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
|
| 12 |
|
campaign_files/2026-10-m-issue-trackers-2/codeberg-forgejo-pulls/README.md
CHANGED
|
@@ -1,12 +1,12 @@
|
|
| 1 |
# codeberg-forgejo-pulls
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds fewer than 50 entries, so it is complete.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://codeberg.org/forgejo/forgejo/pulls/11434; https://codeberg.org/forgejo/forgejo/pulls/11417; https://codeberg.org/forgejo/forgejo/pulls/11288; https://codeberg.org/forgejo/forgejo/pulls/7075; https://codeberg.org/forgejo/forgejo/pulls/7067. Kind: real files published upstream. Live Forgejo REST interface of a closed pull request, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
|
| 8 |
|
| 9 |
-
**Self-contained:** Each file is self-contained.
|
| 10 |
|
| 11 |
**Tools to open and check:** curl the Forgejo/Gitea REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
|
| 12 |
|
|
|
|
| 1 |
# codeberg-forgejo-pulls
|
| 2 |
|
| 3 |
+
**What this is:** Files published by Forgejo project, on Codeberg (codeberg.org, Codeberg e.V.). Collection theme: Code hosting platform issue and merge request timelines (GitHub, GitLab, Gitea/Forgejo and similar, as fixed exports or datasets).
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds fewer than 50 entries, so it is complete.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://codeberg.org/forgejo/forgejo/pulls/11434; https://codeberg.org/forgejo/forgejo/pulls/11417; https://codeberg.org/forgejo/forgejo/pulls/11288; https://codeberg.org/forgejo/forgejo/pulls/7075; https://codeberg.org/forgejo/forgejo/pulls/7067. Kind: real files published upstream. Live Forgejo REST interface of a closed pull request, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
|
| 8 |
|
| 9 |
+
**Self-contained:** Each file is self-contained. Each file names companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
|
| 10 |
|
| 11 |
**Tools to open and check:** curl the Forgejo/Gitea REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
|
| 12 |
|
campaign_files/2026-10-m-issue-trackers-2/codeberg-gotosocial-pulls/README.md
CHANGED
|
@@ -1,12 +1,12 @@
|
|
| 1 |
# codeberg-gotosocial-pulls
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds fewer than 50 entries, so it is complete.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://codeberg.org/superseriousbusiness/gotosocial/pulls/4557. Kind: real files published upstream. Live Forgejo REST interface of a closed pull request, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
|
| 8 |
|
| 9 |
-
**Self-contained:** The file is self-contained.
|
| 10 |
|
| 11 |
**Tools to open and check:** curl the Forgejo/Gitea REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
|
| 12 |
|
|
|
|
| 1 |
# codeberg-gotosocial-pulls
|
| 2 |
|
| 3 |
+
**What this is:** Files published by GoToSocial project, on Codeberg (codeberg.org, Codeberg e.V.). Collection theme: Code hosting platform issue and merge request timelines (GitHub, GitLab, Gitea/Forgejo and similar, as fixed exports or datasets).
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds fewer than 50 entries, so it is complete.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://codeberg.org/superseriousbusiness/gotosocial/pulls/4557. Kind: real files published upstream. Live Forgejo REST interface of a closed pull request, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
|
| 8 |
|
| 9 |
+
**Self-contained:** The file is self-contained. Each file names companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
|
| 10 |
|
| 11 |
**Tools to open and check:** curl the Forgejo/Gitea REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
|
| 12 |
|
campaign_files/2026-10-m-issue-trackers-2/codeberg-keyoxide-keyoxide-web-pulls/README.md
CHANGED
|
@@ -1,12 +1,12 @@
|
|
| 1 |
# codeberg-keyoxide-keyoxide-web-pulls
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 24 entries, fewer than 50, so it is complete.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://codeberg.org/keyoxide/keyoxide-web/pulls/196. Kind: real files published upstream. Live Forgejo REST interface of a closed pull request, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
|
| 8 |
|
| 9 |
-
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream.
|
| 10 |
|
| 11 |
**Tools to open and check:** curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
|
| 12 |
|
|
|
|
| 1 |
# codeberg-keyoxide-keyoxide-web-pulls
|
| 2 |
|
| 3 |
+
**What this is:** Files published by Keyoxide project, on Codeberg (codeberg.org, Codeberg e.V.). Collection theme: Code hosting platform issue and merge request timelines (GitHub, GitLab, Gitea/Forgejo and similar, as fixed exports or datasets).
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 24 entries, fewer than 50, so it is complete.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://codeberg.org/keyoxide/keyoxide-web/pulls/196. Kind: real files published upstream. Live Forgejo REST interface of a closed pull request, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
|
| 8 |
|
| 9 |
+
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. Each file names companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
|
| 10 |
|
| 11 |
**Tools to open and check:** curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
|
| 12 |
|
campaign_files/2026-10-m-issue-trackers-2/codeberg-mergiraf-pulls/README.md
CHANGED
|
@@ -1,12 +1,12 @@
|
|
| 1 |
# codeberg-mergiraf-pulls
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 21 entries, fewer than 50, so it is complete. Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 11 entries, fewer than 50, so it is complete.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://codeberg.org/mergiraf/mergiraf/pulls/817; https://codeberg.org/mergiraf/mergiraf/pulls/802. Kind: real files published upstream. Live Forgejo REST interface of a closed pull request, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
|
| 8 |
|
| 9 |
-
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream.
|
| 10 |
|
| 11 |
**Tools to open and check:** curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
|
| 12 |
|
|
|
|
| 1 |
# codeberg-mergiraf-pulls
|
| 2 |
|
| 3 |
+
**What this is:** Files published by Mergiraf project, on Codeberg (codeberg.org, Codeberg e.V.). Collection theme: Code hosting platform issue and merge request timelines (GitHub, GitLab, Gitea/Forgejo and similar, as fixed exports or datasets).
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 21 entries, fewer than 50, so it is complete. Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 11 entries, fewer than 50, so it is complete.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://codeberg.org/mergiraf/mergiraf/pulls/817; https://codeberg.org/mergiraf/mergiraf/pulls/802. Kind: real files published upstream. Live Forgejo REST interface of a closed pull request, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
|
| 8 |
|
| 9 |
+
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. Each file names companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
|
| 10 |
|
| 11 |
**Tools to open and check:** curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
|
| 12 |
|
campaign_files/2026-10-m-issue-trackers-2/codeberg-microcad-microcad-pulls/README.md
CHANGED
|
@@ -1,12 +1,12 @@
|
|
| 1 |
# codeberg-microcad-microcad-pulls
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 33 entries, fewer than 50, so it is complete.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://codeberg.org/microcad/microcad/pulls/537. Kind: real files published upstream. Live Forgejo REST interface of a closed pull request, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
|
| 8 |
|
| 9 |
-
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream.
|
| 10 |
|
| 11 |
**Tools to open and check:** curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
|
| 12 |
|
|
|
|
| 1 |
# codeberg-microcad-microcad-pulls
|
| 2 |
|
| 3 |
+
**What this is:** Files published by microcad project, on Codeberg (codeberg.org, Codeberg e.V.). Collection theme: Code hosting platform issue and merge request timelines (GitHub, GitLab, Gitea/Forgejo and similar, as fixed exports or datasets).
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 33 entries, fewer than 50, so it is complete.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://codeberg.org/microcad/microcad/pulls/537. Kind: real files published upstream. Live Forgejo REST interface of a closed pull request, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
|
| 8 |
|
| 9 |
+
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. Each file names companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
|
| 10 |
|
| 11 |
**Tools to open and check:** curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
|
| 12 |
|
campaign_files/2026-10-m-issue-trackers-2/codeberg-mineclonia-pulls/README.md
CHANGED
|
@@ -1,12 +1,12 @@
|
|
| 1 |
# codeberg-mineclonia-pulls
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 28 entries, fewer than 50, so it is complete.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://codeberg.org/mineclonia/mineclonia/pulls/4758. Kind: real files published upstream. Live Forgejo REST interface of a closed pull request, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
|
| 8 |
|
| 9 |
-
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream.
|
| 10 |
|
| 11 |
**Tools to open and check:** curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
|
| 12 |
|
|
|
|
| 1 |
# codeberg-mineclonia-pulls
|
| 2 |
|
| 3 |
+
**What this is:** Files published by Mineclonia project, on Codeberg (codeberg.org, Codeberg e.V.). Collection theme: Code hosting platform issue and merge request timelines (GitHub, GitLab, Gitea/Forgejo and similar, as fixed exports or datasets).
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 28 entries, fewer than 50, so it is complete.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://codeberg.org/mineclonia/mineclonia/pulls/4758. Kind: real files published upstream. Live Forgejo REST interface of a closed pull request, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
|
| 8 |
|
| 9 |
+
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. Each file names companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
|
| 10 |
|
| 11 |
**Tools to open and check:** curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
|
| 12 |
|
campaign_files/2026-10-m-issue-trackers-2/codeberg-tenacityteam-tenacity-pulls/README.md
CHANGED
|
@@ -1,12 +1,12 @@
|
|
| 1 |
# codeberg-tenacityteam-tenacity-pulls
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 18 entries, fewer than 50, so it is complete. Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 11 entries, fewer than 50, so it is complete.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://codeberg.org/tenacityteam/tenacity/pulls/736; https://codeberg.org/tenacityteam/tenacity/pulls/747. Kind: real files published upstream. Live Forgejo REST interface of a closed pull request, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
|
| 8 |
|
| 9 |
-
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream.
|
| 10 |
|
| 11 |
**Tools to open and check:** curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
|
| 12 |
|
|
|
|
| 1 |
# codeberg-tenacityteam-tenacity-pulls
|
| 2 |
|
| 3 |
+
**What this is:** Files published by Tenacity audio editor project, on Codeberg (codeberg.org, Codeberg e.V.). Collection theme: Code hosting platform issue and merge request timelines (GitHub, GitLab, Gitea/Forgejo and similar, as fixed exports or datasets).
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 18 entries, fewer than 50, so it is complete. Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 11 entries, fewer than 50, so it is complete.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://codeberg.org/tenacityteam/tenacity/pulls/736; https://codeberg.org/tenacityteam/tenacity/pulls/747. Kind: real files published upstream. Live Forgejo REST interface of a closed pull request, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
|
| 8 |
|
| 9 |
+
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. Each file names companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
|
| 10 |
|
| 11 |
**Tools to open and check:** curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
|
| 12 |
|
campaign_files/2026-10-m-issue-trackers-2/codeberg-tusky-tusky-pulls/README.md
CHANGED
|
@@ -1,12 +1,12 @@
|
|
| 1 |
# codeberg-tusky-tusky-pulls
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 20 entries, fewer than 50, so it is complete.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://codeberg.org/tusky/Tusky/pulls/5522. Kind: real files published upstream. Live Forgejo REST interface of a closed pull request, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
|
| 8 |
|
| 9 |
-
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream.
|
| 10 |
|
| 11 |
**Tools to open and check:** curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
|
| 12 |
|
|
|
|
| 1 |
# codeberg-tusky-tusky-pulls
|
| 2 |
|
| 3 |
+
**What this is:** Files published by Tusky project (Mastodon client for Android), on Codeberg (codeberg.org, Codeberg e.V.). Collection theme: Code hosting platform issue and merge request timelines (GitHub, GitLab, Gitea/Forgejo and similar, as fixed exports or datasets).
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 20 entries, fewer than 50, so it is complete.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://codeberg.org/tusky/Tusky/pulls/5522. Kind: real files published upstream. Live Forgejo REST interface of a closed pull request, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
|
| 8 |
|
| 9 |
+
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. Each file names companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
|
| 10 |
|
| 11 |
**Tools to open and check:** curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
|
| 12 |
|
campaign_files/2026-10-m-issue-trackers-2/codeberg-zig-pulls/README.md
CHANGED
|
@@ -1,12 +1,12 @@
|
|
| 1 |
# codeberg-zig-pulls
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 12 entries, fewer than 50, so it is complete. Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 6 entries, fewer than 50, so it is complete.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://codeberg.org/ziglang/zig/pulls/37063; https://codeberg.org/ziglang/zig/pulls/37102. Kind: real files published upstream. Live Forgejo REST interface of a closed pull request, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
|
| 8 |
|
| 9 |
-
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream.
|
| 10 |
|
| 11 |
**Tools to open and check:** curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
|
| 12 |
|
|
|
|
| 1 |
# codeberg-zig-pulls
|
| 2 |
|
| 3 |
+
**What this is:** Files published by Zig Software Foundation (ziglang), on Codeberg (codeberg.org, Codeberg e.V.). Collection theme: Code hosting platform issue and merge request timelines (GitHub, GitLab, Gitea/Forgejo and similar, as fixed exports or datasets).
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 12 entries, fewer than 50, so it is complete. Forgejo REST API v1 JSON: the issue object (title, state, created_at, closed_at, user, assignees, pull_request.merged) and the timeline array (type, user.login, created_at, body, assignee, assignee_team, removed_assignee) with types comment, review, assignees, review_request, close, reopen, merge_pull, label, pull_push and others. The timeline was requested with limit=50 and holds 6 entries, fewer than 50, so it is complete.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://codeberg.org/ziglang/zig/pulls/37063; https://codeberg.org/ziglang/zig/pulls/37102. Kind: real files published upstream. Live Forgejo REST interface of a closed pull request, collected as a NOASSERTION pointer row under spec general rule 4: the issue JSON and the timeline JSON were each fetched twice apart and were byte-identical. Unit files kept only outside the repository for checking and then deleted.
|
| 8 |
|
| 9 |
+
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. Each file names companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
|
| 10 |
|
| 11 |
**Tools to open and check:** curl the Forgejo REST API v1 (/api/v1/repos/{owner}/{repo}/issues/{n} and /issues/{n}/timeline) and read the JSON with jq or Python json; the tea CLI or fj (forgejo-cli) also reach the same data
|
| 12 |
|
campaign_files/2026-10-md-media-and-documents/cdc-podcast-306916-radiation-myths/README.md
CHANGED
|
@@ -1,12 +1,12 @@
|
|
| 1 |
# cdc-podcast-306916-radiation-myths
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: MP3, 10,305,340 bytes, about 429 seconds (afinfo estimate; CDC media record durationSeconds 183): host interview between two fixed announcer lines.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://tools.cdc.gov/podcasts/media/mp3/306916_Radiation_Myths.mp3. Kind: real files published upstream. Official CDC podcast recorded by or for CDC, transcript written and published by CDC.
|
| 8 |
|
| 9 |
-
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream.
|
| 10 |
|
| 11 |
**Tools to open and check:** Check: Give the agent the mp3 only; it writes the transcript; extract the PDF text, remove page header and footer lines, bracketed speaker labels and the title block from the reference; score word error rate (WER) against the remaining transcript words, reported as a number with no pass mark; case and punctuation folded on both sides; CDC transcripts are edited scripts or lightly cleaned transcripts (fillers and false starts may be dropped, numbers and web addresses are written in digits and URL form), so the score is a soft reference score; speaker turns may be scored separately as a diarisation check against the labels.
|
| 12 |
|
|
|
|
| 1 |
# cdc-podcast-306916-radiation-myths
|
| 2 |
|
| 3 |
+
**What this is:** Files published by U.S. Centers for Disease Control and Prevention (CDC), podcast series: CDC radiation emergencies podcast. Collection theme: Human-transcribed English audio (read speech, lectures, broadcasts with human transcripts).
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: MP3, 10,305,340 bytes, about 429 seconds (afinfo estimate; CDC media record durationSeconds 183): host interview between two fixed announcer lines.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://tools.cdc.gov/podcasts/media/mp3/306916_Radiation_Myths.mp3. Kind: real files published upstream. Official CDC podcast recorded by or for CDC, transcript written and published by CDC.
|
| 8 |
|
| 9 |
+
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. Each file names companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
|
| 10 |
|
| 11 |
**Tools to open and check:** Check: Give the agent the mp3 only; it writes the transcript; extract the PDF text, remove page header and footer lines, bracketed speaker labels and the title block from the reference; score word error rate (WER) against the remaining transcript words, reported as a number with no pass mark; case and punctuation folded on both sides; CDC transcripts are edited scripts or lightly cleaned transcripts (fillers and false starts may be dropped, numbers and web addresses are written in digits and URL form), so the score is a soft reference score; speaker turns may be scored separately as a diarisation check against the labels.
|
| 12 |
|
campaign_files/2026-10-md-media-and-documents/cdc-podcast-313910-1-gateway-duggan-whypodcast/README.md
CHANGED
|
@@ -1,12 +1,12 @@
|
|
| 1 |
# cdc-podcast-313910-1-gateway-duggan-whypodcast
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: MP3, 5,708,622 bytes, about 238 seconds (afinfo estimate; CDC media record durationSeconds 238): host interview between two fixed announcer lines.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://tools.cdc.gov/podcasts/media/mp3/313910_1_Gateway_Duggan_WhyPodcast.mp3. Kind: real files published upstream. Official CDC podcast recorded by or for CDC, transcript written and published by CDC.
|
| 8 |
|
| 9 |
-
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream.
|
| 10 |
|
| 11 |
**Tools to open and check:** Check: Give the agent the mp3 only; it writes the transcript; extract the PDF text, remove page header and footer lines, bracketed speaker labels and the title block from the reference; score word error rate (WER) against the remaining transcript words, reported as a number with no pass mark; case and punctuation folded on both sides; CDC transcripts are edited scripts or lightly cleaned transcripts (fillers and false starts may be dropped, numbers and web addresses are written in digits and URL form), so the score is a soft reference score; speaker turns may be scored separately as a diarisation check against the labels.
|
| 12 |
|
|
|
|
| 1 |
# cdc-podcast-313910-1-gateway-duggan-whypodcast
|
| 2 |
|
| 3 |
+
**What this is:** Files published by U.S. Centers for Disease Control and Prevention (CDC), podcast series: Gateway to Health Communication. Collection theme: Human-transcribed English audio (read speech, lectures, broadcasts with human transcripts).
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: MP3, 5,708,622 bytes, about 238 seconds (afinfo estimate; CDC media record durationSeconds 238): host interview between two fixed announcer lines.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://tools.cdc.gov/podcasts/media/mp3/313910_1_Gateway_Duggan_WhyPodcast.mp3. Kind: real files published upstream. Official CDC podcast recorded by or for CDC, transcript written and published by CDC.
|
| 8 |
|
| 9 |
+
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. Each file names companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
|
| 10 |
|
| 11 |
**Tools to open and check:** Check: Give the agent the mp3 only; it writes the transcript; extract the PDF text, remove page header and footer lines, bracketed speaker labels and the title block from the reference; score word error rate (WER) against the remaining transcript words, reported as a number with no pass mark; case and punctuation folded on both sides; CDC transcripts are edited scripts or lightly cleaned transcripts (fillers and false starts may be dropped, numbers and web addresses are written in digits and URL form), so the score is a soft reference score; speaker turns may be scored separately as a diarisation check against the labels.
|
| 12 |
|
campaign_files/2026-10-md-media-and-documents/cdc-podcast-315594-btd-spheres-maccannell/README.md
CHANGED
|
@@ -1,12 +1,12 @@
|
|
| 1 |
# cdc-podcast-315594-btd-spheres-maccannell
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: MP3, 10,476,864 bytes, about 436 seconds (afinfo estimate; CDC media record durationSeconds 314): host interview between two fixed announcer lines.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://tools.cdc.gov/podcasts/media/mp3/315594_BTD_SPHERES_MacCannell.mp3. Kind: real files published upstream. Official CDC podcast recorded by or for CDC, transcript written and published by CDC.
|
| 8 |
|
| 9 |
-
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream.
|
| 10 |
|
| 11 |
**Tools to open and check:** Check: Give the agent the mp3 only; it writes the transcript; extract the PDF text, remove page header and footer lines, bracketed speaker labels and the title block from the reference; score word error rate (WER) against the remaining transcript words, reported as a number with no pass mark; case and punctuation folded on both sides; CDC transcripts are edited scripts or lightly cleaned transcripts (fillers and false starts may be dropped, numbers and web addresses are written in digits and URL form), so the score is a soft reference score; speaker turns may be scored separately as a diarisation check against the labels.
|
| 12 |
|
|
|
|
| 1 |
# cdc-podcast-315594-btd-spheres-maccannell
|
| 2 |
|
| 3 |
+
**What this is:** Files published by U.S. Centers for Disease Control and Prevention (CDC), podcast series: Beyond the Data (Public Health Grand Rounds companion podcast). Collection theme: Human-transcribed English audio (read speech, lectures, broadcasts with human transcripts).
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: MP3, 10,476,864 bytes, about 436 seconds (afinfo estimate; CDC media record durationSeconds 314): host interview between two fixed announcer lines.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://tools.cdc.gov/podcasts/media/mp3/315594_BTD_SPHERES_MacCannell.mp3. Kind: real files published upstream. Official CDC podcast recorded by or for CDC, transcript written and published by CDC.
|
| 8 |
|
| 9 |
+
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. Each file names companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
|
| 10 |
|
| 11 |
**Tools to open and check:** Check: Give the agent the mp3 only; it writes the transcript; extract the PDF text, remove page header and footer lines, bracketed speaker labels and the title block from the reference; score word error rate (WER) against the remaining transcript words, reported as a number with no pass mark; case and punctuation folded on both sides; CDC transcripts are edited scripts or lightly cleaned transcripts (fillers and false starts may be dropped, numbers and web addresses are written in digits and URL form), so the score is a soft reference score; speaker turns may be scored separately as a diarisation check against the labels.
|
| 12 |
|
campaign_files/2026-10-md-media-and-documents/cdc-podcast-317876-healthybodyhealthybrain/README.md
CHANGED
|
@@ -1,12 +1,12 @@
|
|
| 1 |
# cdc-podcast-317876-healthybodyhealthybrain
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: MP3, 7,058,278 bytes, about 294 seconds (afinfo estimate; CDC media record durationSeconds 294): host interview between two fixed announcer lines.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://tools.cdc.gov/podcasts/media/mp3/317876_HealthyBodyHealthyBrain.mp3. Kind: real files published upstream. Official CDC podcast recorded by or for CDC, transcript written and published by CDC.
|
| 8 |
|
| 9 |
-
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream.
|
| 10 |
|
| 11 |
**Tools to open and check:** Check: Give the agent the mp3 only; it writes the transcript; extract the PDF text, remove page header and footer lines, bracketed speaker labels and the title block from the reference; score word error rate (WER) against the remaining transcript words, reported as a number with no pass mark; case and punctuation folded on both sides; CDC transcripts are edited scripts or lightly cleaned transcripts (fillers and false starts may be dropped, numbers and web addresses are written in digits and URL form), so the score is a soft reference score; speaker turns may be scored separately as a diarisation check against the labels.
|
| 12 |
|
|
|
|
| 1 |
# cdc-podcast-317876-healthybodyhealthybrain
|
| 2 |
|
| 3 |
+
**What this is:** Files published by U.S. Centers for Disease Control and Prevention (CDC), podcast series: Aging and Health Matters. Collection theme: Human-transcribed English audio (read speech, lectures, broadcasts with human transcripts).
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: MP3, 7,058,278 bytes, about 294 seconds (afinfo estimate; CDC media record durationSeconds 294): host interview between two fixed announcer lines.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://tools.cdc.gov/podcasts/media/mp3/317876_HealthyBodyHealthyBrain.mp3. Kind: real files published upstream. Official CDC podcast recorded by or for CDC, transcript written and published by CDC.
|
| 8 |
|
| 9 |
+
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. Each file names companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
|
| 10 |
|
| 11 |
**Tools to open and check:** Check: Give the agent the mp3 only; it writes the transcript; extract the PDF text, remove page header and footer lines, bracketed speaker labels and the title block from the reference; score word error rate (WER) against the remaining transcript words, reported as a number with no pass mark; case and punctuation folded on both sides; CDC transcripts are edited scripts or lightly cleaned transcripts (fillers and false starts may be dropped, numbers and web addresses are written in digits and URL form), so the score is a soft reference score; speaker turns may be scored separately as a diarisation check against the labels.
|
| 12 |
|
campaign_files/2026-10-md-media-and-documents/cdc-podcast-319887-fdaw/README.md
CHANGED
|
@@ -1,12 +1,12 @@
|
|
| 1 |
# cdc-podcast-319887-fdaw
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: MP3, 7,165,324 bytes, about 298 seconds (afinfo estimate; CDC media record durationSeconds 299): host interview between two fixed announcer lines.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://tools.cdc.gov/podcasts/media/mp3/319887_FDAW.mp3. Kind: real files published upstream. Official CDC podcast recorded by or for CDC, transcript written and published by CDC.
|
| 8 |
|
| 9 |
-
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream.
|
| 10 |
|
| 11 |
**Tools to open and check:** Check: Give the agent the mp3 only; it writes the transcript; extract the PDF text, remove page header and footer lines, bracketed speaker labels and the title block from the reference; score word error rate (WER) against the remaining transcript words, reported as a number with no pass mark; case and punctuation folded on both sides; CDC transcripts are edited scripts or lightly cleaned transcripts (fillers and false starts may be dropped, numbers and web addresses are written in digits and URL form), so the score is a soft reference score; speaker turns may be scored separately as a diarisation check against the labels.
|
| 12 |
|
|
|
|
| 1 |
# cdc-podcast-319887-fdaw
|
| 2 |
|
| 3 |
+
**What this is:** Files published by U.S. Centers for Disease Control and Prevention (CDC), podcast series: CDC fungal disease awareness episode (Fungal Disease Awareness Week). Collection theme: Human-transcribed English audio (read speech, lectures, broadcasts with human transcripts).
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: MP3, 7,165,324 bytes, about 298 seconds (afinfo estimate; CDC media record durationSeconds 299): host interview between two fixed announcer lines.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://tools.cdc.gov/podcasts/media/mp3/319887_FDAW.mp3. Kind: real files published upstream. Official CDC podcast recorded by or for CDC, transcript written and published by CDC.
|
| 8 |
|
| 9 |
+
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. Each file names companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
|
| 10 |
|
| 11 |
**Tools to open and check:** Check: Give the agent the mp3 only; it writes the transcript; extract the PDF text, remove page header and footer lines, bracketed speaker labels and the title block from the reference; score word error rate (WER) against the remaining transcript words, reported as a number with no pass mark; case and punctuation folded on both sides; CDC transcripts are edited scripts or lightly cleaned transcripts (fillers and false starts may be dropped, numbers and web addresses are written in digits and URL form), so the score is a soft reference score; speaker turns may be scored separately as a diarisation check against the labels.
|
| 12 |
|
campaign_files/2026-10-md-media-and-documents/cdc-podcast-back-to-schoolemergencyplan/README.md
CHANGED
|
@@ -1,12 +1,12 @@
|
|
| 1 |
# cdc-podcast-back-to-schoolemergencyplan
|
| 2 |
|
| 3 |
-
**What this is:**
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: MP3, 8,747,804 bytes, about 219 seconds (afinfo estimate; CDC media record durationSeconds 219): host interview between two fixed announcer lines.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://tools.cdc.gov/podcasts/media/mp3/Back_to_SchoolEmergencyPlan.mp3. Kind: real files published upstream. Official CDC podcast recorded by or for CDC, transcript written and published by CDC.
|
| 8 |
|
| 9 |
-
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream.
|
| 10 |
|
| 11 |
**Tools to open and check:** Check: Give the agent the mp3 only; it writes the transcript; extract the PDF text, remove page header and footer lines, bracketed speaker labels and the title block from the reference; score word error rate (WER) against the remaining transcript words, reported as a number with no pass mark; case and punctuation folded on both sides; CDC transcripts are edited scripts or lightly cleaned transcripts (fillers and false starts may be dropped, numbers and web addresses are written in digits and URL form), so the score is a soft reference score; speaker turns may be scored separately as a diarisation check against the labels.
|
| 12 |
|
|
|
|
| 1 |
# cdc-podcast-back-to-schoolemergencyplan
|
| 2 |
|
| 3 |
+
**What this is:** Files published by U.S. Centers for Disease Control and Prevention (CDC), podcast series: CDC children's emergency preparedness podcast. Collection theme: Human-transcribed English audio (read speech, lectures, broadcasts with human transcripts).
|
| 4 |
|
| 5 |
**What one unit is:** One upstream file per unit, kept at its path in the upstream repository or site. Format: MP3, 8,747,804 bytes, about 219 seconds (afinfo estimate; CDC media record durationSeconds 219): host interview between two fixed announcer lines.
|
| 6 |
|
| 7 |
**Where it comes from:** Upstream: https://tools.cdc.gov/podcasts/media/mp3/Back_to_SchoolEmergencyPlan.mp3. Kind: real files published upstream. Official CDC podcast recorded by or for CDC, transcript written and published by CDC.
|
| 8 |
|
| 9 |
+
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. Each file names companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
|
| 10 |
|
| 11 |
**Tools to open and check:** Check: Give the agent the mp3 only; it writes the transcript; extract the PDF text, remove page header and footer lines, bracketed speaker labels and the title block from the reference; score word error rate (WER) against the remaining transcript words, reported as a number with no pass mark; case and punctuation folded on both sides; CDC transcripts are edited scripts or lightly cleaned transcripts (fillers and false starts may be dropped, numbers and web addresses are written in digits and URL form), so the score is a soft reference score; speaker turns may be scored separately as a diarisation check against the labels.
|
| 12 |
|