Nous sommes dans une ère "pré-théorique" de l'« open source ». On ne peut saisir la nature de ce concept sous l'angle de la logique et de la rationalité, la sociologie vient nous éclairer sur son sens. En train de lire "La Construction sociale de la réalité" qui nous donne des clés de lecture pour appréhender le phénomène.

La définition de l'open source est une construction sociale de la réalité, c'est ce qui en fait un objet aussi instable et controversé.

Berger découpe 3 phases dans notre construction sociale de la réalité :

1/ L'externalisation : des individus projettent leur propre pratique et conception au monde extérieur, notamment à travers le langage. Eric Raymond et Bruce Perens utilisent la Debian Free Software Guideline et la renomment en Open Source Definition (OSD).

2/ L'objectivation : Cette construction sociale vit de manière autonome indépendamment de leurs auteurs. L'Open Source Initiative (OSI) vient institutionnaliser cette vision du concept par l'OSD.

3/ L'internalisation : Cet objet social s'intègre comme la réalité pour les suivants à travers leur socialisation, cela devient la normalité des nouvelles générations. L'Open Source Definition devient une évidence qu'on arrête de véritablement questionner, un « c'est comme ça » sans compréhension de ces fondements.

Il y a également deux processus intéressants, la légitimation et la sédimentation. On vient tenter d'apporter une justification à l'institutionnalisation, par exemple ce fonctionnement est nécessaire au développement du logiciel open source ou permet d'apporter une cohérence juridique.

La sédimentation c'est le fait que cette institutionnalisation se fige de plus en plus, cette conception de l'open source façonne l'identité, des lois et règles se structurent autour, rendant le changement plus complexe.

Cela fait qu'un choix arbitraire produit par 2 individus devient les bases de tout un système, qui se retrouve alors justifié par une multiplicité d'individus qui ont des intérêt directs au maintien de ce système. C'est notre nature sociale qui apporte une cohérence à l'incohérence de l'« open source », en partant de bien peu de choses pour justifier l'actuelle "définition" de l'open source par l'OSD.

Je vais ajouter cette dimension sociologique à une version 0.2 de mon preprint « Open Source 2.0: From Open Source Software to Open Source Resources » : https://doi.org/10.5281/zenodo.20237079

Ce preprint pourrait aider à basculer d'un stade pré-théorique à la véritable théorisation du concept pour espérer plus pleinement en saisir le sens, aujourd'hui bloqué par tout un ordre social cristallisé.

#openmodels #opensource #openscience #openeducation #communsnumeriques #logicielsLibres #opensoftware #REL #educationouverte #scienceouverte #openaccess #digitalcommons #opensource2

F-G02 wave closes on the SecOps-NG framework: every shipped playbook now carries a validated outbound mappings overlay (OSCAL / D3FEND / OCSF / NIS2 / DORA), with a new CI completeness guard behind the set. Honest framing — several rows still name inbound gaps in-line; inbound-closure opens next.

CI guard: https://github.com/secops-ng/secops-ng-framework/pull/399
Framework: https://github.com/secops-ng/secops-ng-framework

#NIS2 #DORA #OSCAL #D3FEND #DigitalCommons #SovereignEU

tests(g02): guard finalized-playbook mapping-overlay completeness by petermat · Pull Request #399 · secops-ng/secops-ng-framework

What Adds tests/content/test_playbook_mapping_coverage.py — a CI guard that defends G-02's orphaned-playbook KRI. The existing tests/content/test_playbook_mappings.py validates the shape of ove...

GitHub

Field note #67 — F-G02 outbound cross-standard mappings overlay wave.

Ten further SKELETON mappings.yaml overlays merged. 14 of 15 playbooks now carry a typed outbound surface cross-linking OSCAL, D3FEND, OCSF, and the EU regulatory clauses (NIS2 / DORA / CRA / GDPR) each playbook discharges.

Read: https://secops-ng.com/blog/field-note-67-fg02-overlay-wave-fourteen-of-fifteen/

#DigitalCommons #NIS2 #DORA #OSCAL #D3FEND #OCSF

Field note #66 is up.

F-SV-02 eIDAS 2.0 wallet integration pattern → Shipped. Three-target parity closed (n8n + Temporal + LangGraph) with byte-parity goldens. A Pydantic-typed EUDIW attestation now reads as a portable, framework-agnostic workflow input. First Shipped row on the sovereignty lane.

F-G02 outbound mappings overlay lane also opens — OSCAL · D3FEND · OCSF · NIS2 · DORA · CRA · GDPR.

https://github.com/secops-ng/secops-ng-website/pull/78

#eIDAS2 #EUDIW #NIS2 #DORA #DigitalCommons

blog: field note #66 — F-SV-02 eIDAS 2.0 wallet pattern Shipped (three-target parity closed) + F-G02 outbound mappings overlay lane opens by petermat · Pull Request #78 · secops-ng/secops-ng-website

Field note #66 in the Digital Commons voice. Reads two rows since field note #65: F-SV-02 eIDAS 2.0 wallet integration pattern — Shipped (three-target parity closed). LangGraph CORE-FANOUT lands (...

GitHub

Field note #65: F-WF-12 IT-and-security support agent flips Shipped with three-target parity (n8n, Temporal, LangGraph) on the F-CP-02 incidents stream — NIS2 Art.21(2)(b). F-WF-11 on-boarding/off-boarding tracker closes out into the cookbook — Art.21(2)(i). F-SV-02 eIDAS 2.0 wallet pattern opens on the sovereignty lane: typed EUDIW attestation input, two of three targets landed.

https://github.com/secops-ng/secops-ng-website/pull/77

#NIS2 #eIDAS2 #EUDIW #DigitalCommons

blog: field note #65 — F-WF-12 IT-support-agent Shipped (three-target), F-WF-11 closeout, F-SV-02 eIDAS 2.0 wallet pattern opens by petermat · Pull Request #77 · secops-ng/secops-ng-website

Field note #65 in the SecOps-NG Digital Commons series. Reads three rows moved since field note #64: F-WF-12 IT-and-security support agent — Shipped (three-target parity). Temporal CORE-FANOUT — ...

GitHub

Field note #63 — F-WF-10 contractual-obligations tracker flips to Shipped across n8n, Temporal, and LangGraph with byte-parity goldens.

The catalogue now carries both axes of NIS2 Art.21(2)(d) supply-chain security: execution-time (F-CP-03) and contract-time (F-WF-10), keyed distinctly, reconciled on the same supplier ref.

PR: https://github.com/secops-ng/secops-ng-website/pull/75

#NIS2 #DigitalCommons #SovereignSecurity

blog: field note #63 — F-WF-10 contractual-obligations tracker Shipped (three-target CORE wave + EXTEND closeout, NIS2 Art.21(2)(d)) by petermat · Pull Request #75 · secops-ng/secops-ng-website

Field note #63 announces F-WF-10 contractual-obligations tracker flipping to Shipped on the framework ROADMAP. Reads the lane end to end: SKELETON (PR #356) — CACAO playbook playbook.contractual_o...

GitHub

Field note #62 — F-SV-03 Shipped.

The DORA Article 19(4) technical-incident report variant now emits across n8n, Temporal, and LangGraph from one operator-supplied incident context. Four milestones (initial_4h / intermediate_72h / final_1mo / voluntary_cyber_threat) — byte-identical per variant across targets, 66 goldens pinning parity, reporting-chain invariant resolved at the emitter.

Write-up: https://github.com/secops-ng/secops-ng-website/pull/73

#SecOpsNG #DORA #DigitalCommons

blog: field note #62 — F-SV-03 DORA Art. 19 technical-incident report variant Shipped by petermat · Pull Request #73 · secops-ng/secops-ng-website

Field note #62 for the SecOps-NG Digital Commons website. What this reads The F-SV-03 shipment that landed 2026-06-19: the DORA Article 19(4) technical-incident report variant, opened with a schema...

GitHub

Today in Paris: the official kick-off of the #DigitalCommons EDIC's activities. There were sessions on the EU #TechSovereigntyPackage, on why Member States built a shared instrument for digital commons, as well as 3 working tracks: #Connect, #Deploy, and #Maintain. 1/2

@dinum
@BMDS
@zendis

📌 It took a while to get this out (because I kept coming across and needing to reflect on additional reference points) but finally the blog post on: "What do we mean when we talk about AI and open knowledge" or otherwise, reflections on the AI-Bridges Symposium held in London at the end of May, is published on the @tibhannover Blog.

🧶 It's a dense thinky-piece, but - just in time for some weekend reading - I hope some of it resonates. Open to feedback and critique, and hearing what others are thinking / writing about these thorny topics.

🔗 https://blog.tib.eu/2026/06/19/what-do-we-mean-when-we-talk-about-ai-and-open-knowledge/

#AIBridges #OpenKnowledge #OpenScience #DigitalCommons #KnowledgeCommons #Wikimedia #ECHOLOT

What do we mean when we talk about AI and open knowledge? - TIB-Blog

Commercial AI applications are increasingly scraping public data, which also impacts the open knowledge ecosystem. The AI-Bridges Symposium at the University of London brought together policy makers, academics, and open knowledge stakeholders to discuss this shift. Two central themes of the conference were the threat of extractive data usage and the great potential of Wikibase and Wikidata for fairer, AI-supported, and collaborative data workflows.

TIB-Blog

📅 Save the date: 2nd Digital Commons Policy Summit 2026

🗓 12 November 2026

The 2025 edition showed the growing momentum behind Digital Commons in Europe. In 2026, the focus shifts from introduction to implementation.

Organised by the @NGICommons Commons consortium in close collaboration with the European Commission.

More details soon: https://commons.ngi.eu/event/digital-commons-policy-summit-2026/

#DigitalCommons #NGICommons #TechSovereignty #EU

@martelinnovate @cnrs @openfuture @OpenForumEurope @linuxfoundation @EC_NGI