home.social

#softwareheritage — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #softwareheritage, aggregated by home.social.

  1. I just submitted Family Size VM to Software Heritage, which collects and preserves public Git repositories. It hasn't seen every repository, especially on Codeberg and other smaller Git hosts. Check if your own project is crawled and save it if it isn't yet.
    archive.softwareheritage.org/

    #SoftwareHeritage #Git #decentralization #preservation #FamilySizeVM #Codeberg

  2. I just submitted Family Size VM to Software Heritage, which collects and preserves public Git repositories. It hasn't seen every repository, especially on Codeberg and other smaller Git hosts. Check if your own project is crawled and save it if it isn't yet.
    archive.softwareheritage.org/

    #SoftwareHeritage #Git #decentralization #preservation #FamilySizeVM #Codeberg

  3. I just submitted Family Size VM to Software Heritage, which collects and preserves public Git repositories. It hasn't seen every repository, especially on Codeberg and other smaller Git hosts. Check if your own project is crawled and save it if it isn't yet.
    archive.softwareheritage.org/

    #SoftwareHeritage #Git #decentralization #preservation #FamilySizeVM #Codeberg

  4. I just submitted Family Size VM to Software Heritage, which collects and preserves public Git repositories. It hasn't seen every repository, especially on Codeberg and other smaller Git hosts. Check if your own project is crawled and save it if it isn't yet.
    archive.softwareheritage.org/

    #SoftwareHeritage #Git #decentralization #preservation #FamilySizeVM #Codeberg

  5. I just submitted Family Size VM to Software Heritage, which collects and preserves public Git repositories. It hasn't seen every repository, especially on Codeberg and other smaller Git hosts. Check if your own project is crawled and save it if it isn't yet.
    archive.softwareheritage.org/

    #SoftwareHeritage #Git #decentralization #preservation #FamilySizeVM #Codeberg

  6. Everything you need to know about #SoftwareHeritage and why long-term preservation of source code matters is in @zacchiro interview here 👉 youtube.com/watch?v=R8kBztTivNw

    cc @swheritage

  7. Everything you need to know about #SoftwareHeritage and why long-term preservation of source code matters is in @zacchiro interview here 👉 youtube.com/watch?v=R8kBztTivNw

    cc @swheritage

  8. Everything you need to know about #SoftwareHeritage and why long-term preservation of source code matters is in @zacchiro interview here 👉 youtube.com/watch?v=R8kBztTivNw

    cc @swheritage

  9. Everything you need to know about #SoftwareHeritage and why long-term preservation of source code matters is in @zacchiro interview here 👉 youtube.com/watch?v=R8kBztTivNw

    cc @swheritage

  10. Everything you need to know about #SoftwareHeritage and why long-term preservation of source code matters is in @zacchiro interview here 👉 youtube.com/watch?v=R8kBztTivNw

    cc @swheritage

  11. Reading post: « Git mirror and #Nix flakes – a practical approach to supply chain security »

    🤔 I’m not convinced that mirroring is “the Right Thing” here; it sounds to me as some “worse and holed is maybe better”.

    Instead of mirrors for tackling the upstream troubles, it seems more elegant to have an archive that collects all the public code and then fallback to it when needed.

    Guess what? #Guix does that using #SoftwareHeritage!

    softwareheritage.org/2025/05/2

    blog.networld.to/git-mirrors-a

  12. Reading post: « Git mirror and #Nix flakes – a practical approach to supply chain security »

    🤔 I’m not convinced that mirroring is “the Right Thing” here; it sounds to me as some “worse and holed is maybe better”.

    Instead of mirrors for tackling the upstream troubles, it seems more elegant to have an archive that collects all the public code and then fallback to it when needed.

    Guess what? #Guix does that using #SoftwareHeritage!

    softwareheritage.org/2025/05/2

    blog.networld.to/git-mirrors-a

  13. Reading post: « Git mirror and #Nix flakes – a practical approach to supply chain security »

    🤔 I’m not convinced that mirroring is “the Right Thing” here; it sounds to me as some “worse and holed is maybe better”.

    Instead of mirrors for tackling the upstream troubles, it seems more elegant to have an archive that collects all the public code and then fallback to it when needed.

    Guess what? #Guix does that using #SoftwareHeritage!

    softwareheritage.org/2025/05/2

    blog.networld.to/git-mirrors-a

  14. Reading post: « Git mirror and #Nix flakes – a practical approach to supply chain security »

    🤔 I’m not convinced that mirroring is “the Right Thing” here; it sounds to me as some “worse and holed is maybe better”.

    Instead of mirrors for tackling the upstream troubles, it seems more elegant to have an archive that collects all the public code and then fallback to it when needed.

    Guess what? #Guix does that using #SoftwareHeritage!

    softwareheritage.org/2025/05/2

    blog.networld.to/git-mirrors-a

  15. Reading post: « Git mirror and #Nix flakes – a practical approach to supply chain security »

    🤔 I’m not convinced that mirroring is “the Right Thing” here; it sounds to me as some “worse and holed is maybe better”.

    Instead of mirrors for tackling the upstream troubles, it seems more elegant to have an archive that collects all the public code and then fallback to it when needed.

    Guess what? #Guix does that using #SoftwareHeritage!

    softwareheritage.org/2025/05/2

    blog.networld.to/git-mirrors-a

  16. I wish people from #Codeberg and #Zenodo would collaborate to get the same clever integration features that allow people to preserve #GitHub releases at Zenodo. I bet people from the scientific community would like that. Is it too much to wish some big sciency inftrastructure group would fund this? ;-)

    I'm going to archive stuff at Zenodo as I move out of GitHub.

    Update - Tip from Ale Abdo: let's use #SoftwareHeritage !

    #hopeful #FLOSS

  17. I wish people from #Codeberg and #Zenodo would collaborate to get the same clever integration features that allow people to preserve #GitHub releases at Zenodo. I bet people from the scientific community would like that. Is it too much to wish some big sciency inftrastructure group would fund this? ;-)

    I'm going to archive stuff at Zenodo as I move out of GitHub.

    Update - Tip from Ale Abdo: let's use #SoftwareHeritage !

    #hopeful #FLOSS

  18. I wish people from #Codeberg and #Zenodo would collaborate to get the same clever integration features that allow people to preserve #GitHub releases at Zenodo. I bet people from the scientific community would like that. Is it too much to wish some big sciency inftrastructure group would fund this? ;-)

    I'm going to archive stuff at Zenodo as I move out of GitHub.

    Update - Tip from Ale Abdo: let's use #SoftwareHeritage !

    #hopeful #FLOSS

  19. I wish people from #Codeberg and #Zenodo would collaborate to get the same clever integration features that allow people to preserve #GitHub releases at Zenodo. I bet people from the scientific community would like that. Is it too much to wish some big sciency inftrastructure group would fund this? ;-)

    I'm going to archive stuff at Zenodo as I move out of GitHub.

    Update - Tip from Ale Abdo: let's use #SoftwareHeritage !

    #hopeful #FLOSS

  20. I wish people from #Codeberg and #Zenodo would collaborate to get the same clever integration features that allow people to preserve #GitHub releases at Zenodo. I bet people from the scientific community would like that. Is it too much to wish some big sciency inftrastructure group would fund this? ;-)

    I'm going to archive stuff at Zenodo as I move out of GitHub.

    Update - Tip from Ale Abdo: let's use #SoftwareHeritage !

    #hopeful #FLOSS

  21. RE: mstdn.social/@swheritage/11626

    A very interesting exhibition! Using only a few examples, source code is celebrated not as a means to produce, but also as a means to create, and/or convey messages.
    Perhaps my favourite panel is the one showcasing #wenyan. There is a specific mention that source code carries a lot of cultural elements and preconceptions, and in itself is biased, i.e., mostly written by white men. So, I'm glad that fundamentally different programming languages are mentioned.

    #softwareheritage #citedessciences #programming

    EDIT: I failed to mention the exhibition is available online sourcecode-exhibition.software

  22. RE: mstdn.social/@swheritage/11626

    A very interesting exhibition! Using only a few examples, source code is celebrated not as a means to produce, but also as a means to create, and/or convey messages.
    Perhaps my favourite panel is the one showcasing #wenyan. There is a specific mention that source code carries a lot of cultural elements and preconceptions, and in itself is biased, i.e., mostly written by white men. So, I'm glad that fundamentally different programming languages are mentioned.

    #softwareheritage #citedessciences #programming

    EDIT: I failed to mention the exhibition is available online sourcecode-exhibition.software

  23. 📣 Hey, do you know that now #SoftwareHeritage implements SWHEP?

    SWHEP: SoftWare Heritage Enhancement Proposals

    Please checkout the two accepted first ones:

    • Switching from ORC to Parquet for graph exports
    • Paving the way for more versatile object storages by turning shards into mosaic

    🤔 Still puzzled where are numbers 0002 and 0003. 🙃

    gitlab.softwareheritage.org/sw

    gitlab.softwareheritage.org/sw
    gitlab.softwareheritage.org/sw

  24. 📣 Hey, do you know that now #SoftwareHeritage implements SWHEP?

    SWHEP: SoftWare Heritage Enhancement Proposals

    Please checkout the two accepted first ones:

    • Switching from ORC to Parquet for graph exports
    • Paving the way for more versatile object storages by turning shards into mosaic

    🤔 Still puzzled where are numbers 0002 and 0003. 🙃

    gitlab.softwareheritage.org/sw

    gitlab.softwareheritage.org/sw
    gitlab.softwareheritage.org/sw

  25. 📣 Hey, do you know that now #SoftwareHeritage implements SWHEP?

    SWHEP: SoftWare Heritage Enhancement Proposals

    Please checkout the two accepted first ones:

    • Switching from ORC to Parquet for graph exports
    • Paving the way for more versatile object storages by turning shards into mosaic

    🤔 Still puzzled where are numbers 0002 and 0003. 🙃

    gitlab.softwareheritage.org/sw

    gitlab.softwareheritage.org/sw
    gitlab.softwareheritage.org/sw

  26. 📣 Hey, do you know that now #SoftwareHeritage implements SWHEP?

    SWHEP: SoftWare Heritage Enhancement Proposals

    Please checkout the two accepted first ones:

    • Switching from ORC to Parquet for graph exports
    • Paving the way for more versatile object storages by turning shards into mosaic

    🤔 Still puzzled where are numbers 0002 and 0003. 🙃

    gitlab.softwareheritage.org/sw

    gitlab.softwareheritage.org/sw
    gitlab.softwareheritage.org/sw

  27. Via @aprilorg, @HenriVerdier : « J’aime bien le concept de #communs qui nous vient d’une autre tradition. Un commun numérique, a digital commons, c’est une ressource qui est cultivée par ses contributeurs et sa gouvernance est opérée par les gens qui contribuent. Ce sont, par exemple #wikipedia #openstreetmap #softwareheritage ces grandes ressources avec beaucoup de contributeurs et dont le destin est décidé par les contributeurs. »

    librealire.org/l-ia-a-rendu-to

    Bonne lecture !

  28. Via @aprilorg, @HenriVerdier : « J’aime bien le concept de #communs qui nous vient d’une autre tradition. Un commun numérique, a digital commons, c’est une ressource qui est cultivée par ses contributeurs et sa gouvernance est opérée par les gens qui contribuent. Ce sont, par exemple #wikipedia #openstreetmap #softwareheritage ces grandes ressources avec beaucoup de contributeurs et dont le destin est décidé par les contributeurs. »

    librealire.org/l-ia-a-rendu-to

    Bonne lecture !

  29. Via @aprilorg, @HenriVerdier : « J’aime bien le concept de #communs qui nous vient d’une autre tradition. Un commun numérique, a digital commons, c’est une ressource qui est cultivée par ses contributeurs et sa gouvernance est opérée par les gens qui contribuent. Ce sont, par exemple #wikipedia #openstreetmap #softwareheritage ces grandes ressources avec beaucoup de contributeurs et dont le destin est décidé par les contributeurs. »

    librealire.org/l-ia-a-rendu-to

    Bonne lecture !

  30. Via @aprilorg, @HenriVerdier : « J’aime bien le concept de #communs qui nous vient d’une autre tradition. Un commun numérique, a digital commons, c’est une ressource qui est cultivée par ses contributeurs et sa gouvernance est opérée par les gens qui contribuent. Ce sont, par exemple #wikipedia #openstreetmap #softwareheritage ces grandes ressources avec beaucoup de contributeurs et dont le destin est décidé par les contributeurs. »

    librealire.org/l-ia-a-rendu-to

    Bonne lecture !

  31. Via @aprilorg, @HenriVerdier : « J’aime bien le concept de #communs qui nous vient d’une autre tradition. Un commun numérique, a digital commons, c’est une ressource qui est cultivée par ses contributeurs et sa gouvernance est opérée par les gens qui contribuent. Ce sont, par exemple #wikipedia #openstreetmap #softwareheritage ces grandes ressources avec beaucoup de contributeurs et dont le destin est décidé par les contributeurs. »

    librealire.org/l-ia-a-rendu-to

    Bonne lecture !