#Tag
How #CodeCommons uses SWH-fuse & the Kraken compressed graph to map #OpenSource: 8K files/sec and solving 10K process scaling. https://www.softwareheritage.org/2025/10/08/kraken-swh-fuse/
How #CodeCommons uses SWH-fuse & the Kraken compressed graph to map #OpenSource: 8K files/sec and solving 10K process scaling. https://www.softwareheritage.org/2025/10/08/kraken-swh-fuse/
Recently we've been thinking about how we share code (and other design files) for our #OpenSource projects and products.
@span amcewen has written about the flaws in centralized options like Github and Gitlab, and why self-hosting isn't the answer.
Maybe we need some #CodeCommons?
https://mcqn.com/posts/code,-sharing-and-single-points-of-failure/
Recently we've been thinking about how we share code (and other design files) for our #OpenSource projects and products.
@span amcewen has written about the flaws in centralized options like Github and Gitlab, and why self-hosting isn't the answer.
Maybe we need some #CodeCommons?
https://mcqn.com/posts/code,-sharing-and-single-points-of-failure/
Reproducibility in research is key. #CodeCommons aims to enhance it by preserving the full history of software artefacts. Built on @swheritage, it's designed to be an independent & sustainable resource. Learn more: https://www.softwareheritage.org/2025/02/11/codecommons-projects/
A space for Bonfire maintainers and contributors to communicate
