Funding Open Source for Digital Sovereignty 🔗 **Source:** [Funding Open Source for Digital Sovereignty](https://dri.es/funding-open-source-for-digital-sovereignty) > [!note]+ Document Notes > tags: [open-source, digital-sovereignty, procurement] > author: Dries Buytaert > source: dri.es > reference: [https://dri.es/funding-open-source-for-digital-sovereignty](https://dri.es/funding-open-source-for-digital-sovereignty) > date created: 2026-01-21 10:00 > > # 🏷️ Title: Funding Open Source for Digital Sovereignty > <!-- deep-read:sections start --> ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - Include links cited in or relevant to the article. ## 📝 Summary - What happened: The author argues that while Open Source is Europe’s best route to digital sovereignty, current public procurement sends money to integrators instead of maintainers, undermining security and resilience. - Why it matters: Without funding upstream, Europe remains dependent on foreign vendors whose services can be cut off or politicized. - Key stakeholders: EU institutions, national governments, Open Source maintainers, system integrators, European SMEs, civic tech communities. - Risks and tradeoffs: Politically easier to stick with large vendors; shifting procurement may disrupt existing supplier relationships and demands better governance and transparency. - Bottom line: Europe should make upstream contribution a formal procurement criterion so public money directly sustains the Open Source projects it relies on. ## 📖 Main Content - Core argument: Open Source is the only realistic path to European digital sovereignty because it cannot be unilaterally revoked, but Europe’s procurement structures starve the very maintainers who build and secure it. - Context: - Governments are exiting proprietary US clouds (e.g. ICC leaving Microsoft 365, German and Danish migrations) due to sovereignty and access concerns. - Europe has strong Open Source communities and regulatory power, but hasn’t aligned funding with them. - Problem: - Procurement favors large system integrators with sales capacity and compliance certifications. - Small agencies and maintainers create features and fixes, but when governments tender big contracts, “a much larger company, with no involvement in Drupal, submits a polished proposal… They win the contract… the original authors get nothing in return.” ([case example](https://read.readwise.io/read/01kfh19cs7bm76x78rx2hszfqm?endLexposition=0000M_00000-001g&startLexposition=0000C&emphasizeText=A+much+larger+company%2C+with+no+involvement+in+Drupal%2C+submits+a+polished+proposal)) - Result: “Public money flows around Open Source instead of into it.” ([core diagnosis](https://read.readwise.io/read/01kfh19cs7bm76x78rx2hszfqm?endLexposition=0000Y_00002-001d&startLexposition=0000O&emphasizeText=Public+money+flows+around+Open+Source+instead+of+into+it)) - Why skipping maintainers is bad governance: - Integrators who don’t contribute upstream can ship projects but are weak at “fixing problems at the source or shaping the software’s future.” - This misaligns spending: lots on one-off integration, too little on long-term security, resilience, and product evolution. - Proposed fix: - “Make contribution count in procurement scoring.” ([prescription](https://read.readwise.io/read/01kfh19cs7bm76x78rx2hszfqm?endLexposition=0000Y_00002-001d&startLexposition=0000O&emphasizeText=The+fix+is+straightforward%3A+make+contribution+count+in+procurement+scoring)) - Evaluate vendors on what they give back: code, docs, security fixes, and direct funding. - Use project-run credit systems (like Drupal’s) so projects themselves “vouch for contributors directly,” giving procurement officers a transparent signal and reducing false claims. - Example: Drupal’s public directory ranks companies by contribution; if a vendor isn’t on it, “they’re not contributing in any meaningful way.” ([credit-system example](https://read.readwise.io/read/01kfh19cs7bm76x78rx2hszfqm?endLexposition=0000i_00000_00006-000s&startLexposition=0000a&emphasizeText=We+use+the+credit+system+to+maintain+a+public+directory+of+companies+that+provide+Drupal+services)) - Emerging momentum: - APELL proposes contribution as a procurement criterion. - EuroStack lobbies for a “Buy Open Source Act.” - The European Commission has an Open Source roadmap with procurement recommendations. - Overall thesis: Europe doesn’t need its own hyperscalers; it needs to redirect public procurement toward Open Source builders and maintainers to achieve sovereignty, better software, and stronger local ecosystems. ### 🗒️ Notes - Digital sovereignty problem: - Governments rely on foreign, often US-based, proprietary platforms. - “A decision in Washington can disable services in Brussels overnight.” ([sovereignty risk](https://read.readwise.io/read/01kfh19cs7bm76x78rx2hszfqm?endLexposition=0000A_00000-003v&startLexposition=00000&emphasizeText=A+decision+in+Washington+can+disable+services+in+Brussels+overnight)) - Concrete moves: ICC dropping Microsoft 365; Denmark and Schleswig-Holstein migrating away from Microsoft. - Why Open Source: - “It’s the only software you can run without permission.” ([core Open Source claim](https://read.readwise.io/read/01kfh19cs7bm76x78rx2hszfqm?endLexposition=0000A_00000-003v&startLexposition=00000&emphasizeText=Open+Source+is+the+most+credible+path+to+digital+sovereignty)) - Can be self-hosted, audited, modified, forked; immune to unilateral shutdown. - Procurement failure mode: - Small Open Source agencies build crucial features; large non-contributing firms later win big tenders that depend on those features. - Original maintainers inherit support obligations without commensurate funding. - This pattern spans “every Open Source project in Europe’s software stack.” - Governance implications: - Non-contributing integrators: - Less effective in upstream bug fixing and long-term design. - Increase fragmentation, patches, and maintenance burden for governments. - Underfunded upstream: - Weakens security posture and resilience. - Slows innovation that could be shared across many administrations. - Solution architecture: - Procurement scoring explicitly weights upstream contribution. - Require concrete, verifiable evidence of contributions. - Let projects’ own governance/credit systems provide attestations. - Example: Drupal credits → public vendor rankings, giving procurement an easy filter. - Policy landscape: - APELL and EuroStack coordinating industry voice for contribution-based procurement. - European Commission open consultation (“Towards European Open Digital Ecosystems”); author submitted this article as feedback and invites others to do the same. - End-state vision: - Public money directly sustains “public code.” - Stronger local vendors and Open Source firms. - Increased autonomy and strategic resilience for European public institutions. ## 📚 References - Dries Buytaert – “Funding Open Source for Digital Sovereignty” (original article): https://dri.es/funding-open-source-for-digital-sovereignty - Drupal contribution credit system and marketplace (background to example): https://www.drupal.org/association/blog/drupalorg-sponsor-credits - APELL (Association Professionnelle Européenne du Logiciel Libre): https://apell.info/ - EuroStack initiative (Buy Open Source Act context): https://eurostack.org/ - European Commission – Open Source Software Strategy 2020–2023 (roadmap context): https://commission.europa.eu/about-european-commission/departments-and-executive-agencies/informatics/open-source-software-strategy_en ## 🗣️ Paraphrase - Paragraph A paraphrase: Europe’s governments are trying to regain digital control after realizing that dependence on large foreign tech vendors leaves them vulnerable to political and commercial decisions made elsewhere. Open Source provides a credible path to sovereignty because it can be run, inspected, and modified without external permission. - Paragraph B paraphrase: However, the way governments currently buy software routes money to big integrators that package Open Source rather than to the maintainers who actually build and secure it. To achieve true digital sovereignty, Europe must redesign procurement so that upstream contributors are funded according to their contributions. ## 📰 Newsletter Europe’s digital sovereignty debate just got a powerful Open Source angle. In “Funding Open Source for Digital Sovereignty,” Dries Buytaert argues that Europe already has the building blocks—strong Open Source communities, regulatory reach, and public-sector scale—but procurement is misaligned. Public money tends to flow to large integrators instead of the maintainers who actually write and secure the code. For the WordPress ecosystem, this should sound familiar. Many agencies and plugin authors provide critical infrastructure for governments and public institutions, but long-term funding often goes to vendors who integrate rather than build. Dries proposes a concrete remedy: make upstream contribution a procurement criterion, and use project-managed credit systems (like Drupal’s) to give procurement officers a transparent signal of who genuinely contributes. Imagine a similar contribution directory for WordPress: agencies, hosts, and product companies ranked by their track record of contributing to Core, documentation, security, and translations. Such a signal could guide government and enterprise buyers toward vendors who strengthen the commons instead of merely reselling it. If your work touches public sector WordPress projects, now is a good time to: - Audit your own upstream contributions (Core, plugins, themes, docs, Polyglots). - Publish a transparent contribution report prospective clients can reference. - Track EU initiatives like EuroStack’s “Buy Open Source Act” and the EC’s Open Source roadmap, as they may influence how public tenders are evaluated in coming years. ## ✅ Action Items #### DevRel - Developer advocacy: - Create talks/blogs for public-sector audiences explaining contribution-based procurement using WordPress and Drupal examples. - Develop a demo showing how contribution directories can be queried during vendor evaluation. - Education: - Run workshops for agencies on “How to turn your public-sector work into upstream contributions.” - Offer office hours for integrators wanting to transition into active contributors. - Developer experience: - Provide templates and tooling for agencies to attribute their commits, tickets, and documentation contributions to organizational profiles. - Build quickstart guides for government teams wanting to sponsor specific upstream improvements (e.g., security hardening, accessibility). - Developer marketing: - Launch case studies of agencies that win public contracts because of visible Open Source contributions. - Track attributable leads from content about “sovereign Open Source stacks” and public-sector success stories. - Community management: - Set up a feedback path between public-sector users and maintainers for security and feature priorities. - Facilitate governance discussions about how to run contribution credit systems fairly. - Internal/external/cross-project: - Coordinate with Drupal, Joomla, and other CMS communities on compatible contribution-metrics patterns. - Align cross-project messaging to EU institutions on why contribution signals matter in procurement. #### OSPO - Policy & Governance: - Draft internal policy: public-sector engagements must include a budget line for upstream contributions when using Open Source. - Define decision rights on when and how to upstream patches created for government clients. - License Compliance: - Ensure all public-sector projects have clear license-scanning steps and reports provided to the client. - Train legal and procurement teams on Open Source license basics and implications for reuse and funding. - Security Management: - Establish an intake process for vulnerabilities discovered in government deployments, with clear upstream disclosure paths. - Document embargo and coordination practices with core security teams (WordPress and others). - Software Inventory: - Maintain SBOMs for government-facing products and update them on a defined cadence. - Assign owners internally for each key Open Source dependency in public-sector stacks. - Developer Support: - Offer regular consultation hours for teams building on Open Source for public clients. - Provide reusable templates for Open Source-friendly contract clauses. - Community Engagement: - Allocate a defined percentage of public-sector revenue to upstream funding (grants, sponsorships, maintainer contracts). - Participate in initiatives like EuroStack and APELL as a corporate voice. - Strategic Alignment: - Add KPIs around “percent of public-sector revenue reinvested upstream” and “number of funded upstream features.” - Report to executives on risk reduction achieved through upstream engagement. #### Community - Maintainers: - Host roadmap clinics tailored to public-sector use cases (security, accessibility, multi-language). - Offer maintainers guidance on forming legal entities or cooperatives suitable for government contracts. - Contributors: - Create “public-sector first issue” tags highlighting tasks that directly benefit government users. - Pair new contributors from agencies with experienced maintainers. - Sponsors: - Provide transparent budgets for security and maintenance work required by public bodies. - Share impact reports showing how sponsorships improved reliability for government deployments. - Ecosystem: - Coordinate cross-project incident drills (e.g., dependency vulnerabilities impacting multiple CMSes). - Align disclosure timelines and messaging for high-impact security events. #### WordPress - Core: - Prioritize features crucial for government (privacy controls, data residency, multi-tenant admin tooling). - Improve triage for issues raised by large public bodies and integrators. - Core Performance: - Define performance budgets aligned with government-scale implementations. - Provide dashboards and guidelines on performance baselines for public-sector sites. - Core AI: - Set guardrails for AI features in government contexts (data retention, model provenance, human-in-the-loop). - Pilot AI features with public-sector partners under strict evaluation. - **Core Program Team:** - Establish regular touchpoints with EU digital teams and national gov leads. - Run retrospectives focused on large public-sector migrations to WordPress. - Mobile: - Improve offline workflows for field workers in government agencies. - Review telemetry to understand public-sector usage patterns. - Playground: - Offer browser-based labs for govt IT to prototype sovereign WordPress stacks. - Provide reproducible environments for security and accessibility testing. - Community: - Develop meetup kits centered on “Open Source and digital sovereignty.” - Encourage WordCamp tracks dedicated to public-sector experiences. - Training: - Create curriculum modules on “WordPress for public institutions” including governance, security, and procurement. - Explore certification paths relevant to government tender requirements. - Marketing: - Craft narratives about WordPress as a sovereignty-enabling platform. - Coordinate social content around key policy milestones (e.g., EU consultations). - Support: - Identify knowledge base gaps specific to public-sector deployments. - Define escalation paths for incidents affecting government users. - Design: - Run UX audits for typical government site patterns (services, forms, multilingual content). - Provide design tokens that align with common public-design systems. - Documentation: - Document best practices for WordPress in regulated environments. - Emphasize examples of upstreaming changes made for public-sector customers. - Photos: - Curate photo collections suitable for public institutions (non-commercial, diverse). - Ensure moderation guidelines cover public-sector sensitivities. - TV: - Produce captioned video case studies of government migrations to Open Source. - Index content under “public sector” and “digital sovereignty.” - Polyglots: - Run translation sprints for EU languages and minority languages often needed in government. - Align glossaries with official terminology where appropriate. - Accessibility: - Schedule recurring WCAG audits for default themes and core blocks. - Publish an issues heatmap to prioritize high-impact accessibility fixes. - Meta: - Ensure .org infrastructure reliability SLAs meet expectations of public entities. - Improve contributor tools for agencies that want to push patches upstream. - CLI: - Enhance tooling for automated, repeatable government site deployments. - Improve docs for scripting compliance and security checks with WP-CLI. - Hosting: - Collaborate with hosts to offer “sovereign WordPress” blueprints (data residency, logging, security baselines). - Encourage telemetry that respects privacy while informing reliability improvements. - Tide: - Increase transparency on plugin scoring, especially security-related signals. - Engage with plugin authors used heavily in public-sector stacks. - Openverse: - Support ingestion of public-domain and government media collections. - Provide guidance on copyright and licensing for official content. - Themes: - Develop and maintain government-ready theme templates (service catalogues, forms, accessibility). - Mentor theme authors on public-sector requirements. - Plugins: - Fast-track review of plugins critical to government use (forms, workflows, multilingual). - Enhance provenance checks and security reviews for these plugins specifically. #### The WPOCC - Programs: - Launch fellowship tracks for maintainers working on public-sector-relevant features. - Offer microgrants to small agencies that upstream improvements made for government clients. - Projects: - Run governance clinics to help projects design contribution-credit systems. - Organize documentation sprints focused on public-sector deployment guides. - Funding experiments: - Pilot matched grants tied to public-sector contracts (e.g., 1–5% flows upstream). - Use transparent public ledgers to track how public money sustains maintainers. ### FAIR - Technical independence: - Encourage local verification of updates via signatures and reproducible builds. - Track provenance for code used in government environments. - Policies and covenants: - Define funding transparency commitments and anti-capture clauses. - Include sunset clauses for funding experiments tied to measurable impact. - Productized governance artifacts: - Offer reusable charters and operator agreements for public-sector Open Source programs. - Provide scorecards to assess vendors’ contribution and governance maturity. ## 🧪 Hypotheses - H1: Public-sector tenders that weight upstream Open Source contribution will, over time, increase the security and resilience of government digital services. - H2: Visibility of contribution-based vendor rankings (like Drupal’s) will shift public contracts from non-contributing integrators to contributing maintainers and agencies. - H3: A small percentage (1–5%) of public-sector software budgets earmarked for upstream will significantly increase maintainer capacity without substantial project cost overruns. - H4: Governments that adopt contribution-based procurement will experience lower long-term total cost of ownership for Open Source systems compared to those that don’t. - H5: Clear, project-managed credit systems reduce false contribution claims and improve trust between governments and vendors. ### 📊 Methodology - Study designs: - Comparative case studies: Contrast jurisdictions that adopt contribution-based procurement with those that don’t, over 3–5 years. - Before/after studies: Track incident rates, patch latency, and TCO pre- and post-policy change. - Data sources: - Procurement records, contract amounts, and vendor lists. - Open Source project contribution logs, credit systems, and release timelines. - Security advisories and incident reports for government systems. - Analyses: - Regression analysis linking contribution-weighted procurement to security incidents and downtime. - Network analysis of maintainer ecosystems to see how funding affects contributor retention. - Cost-benefit models comparing integration-only spend vs. combined integration + upstream investment. ### ❓ Questions - How can small Open Source agencies become eligible and competitive in complex public tenders without excessive administrative overhead? - What minimum viable metrics should procurement bodies use to assess “meaningful” contribution? - How can contribution-credit systems prevent gaming while remaining lightweight? - What portion of public-sector software budgets is realistic to dedicate to upstream funding? - How should multi-project dependencies be handled when crediting contributions (e.g., CMS + plugins + libraries)? ### 🔮 Future Research - Design of interoperable contribution-credit standards across multiple Open Source ecosystems. - Long-term socio-economic impact of contribution-based procurement on local tech SMEs and employment. - Governance models for public-sector-funded Open Source consortia. - Best practices for embedding Open Source thinking into civil service training and career paths. - Comparative studies of digital sovereignty strategies in regions beyond Europe (e.g., Latin America, Africa, Asia). ### 💡 Implications - Practice: - Agencies and vendors need to strategically invest in upstream work and track it for procurement signaling. - Policy: - EU and national bodies can codify contribution criteria and transparency requirements into procurement law. - Security: - Better-funded maintainers improve vulnerability response and reduce systemic risk in public services. - Education: - Training for procurement officers must include Open Source governance, licensing, and contribution evaluation. - Funding models: - Shift from project-by-project integration spending toward continuous funding of shared infrastructure. ### 🧠 Learning Styles Assessment - Reading level estimate: - Approx. Flesch-Kincaid Grade Level: 11–12 (policy/tech blog for informed professionals). #### 👀 Visual learners - Present: - Implicit conceptual contrast (foreign hyperscalers vs. local OSS); a hero image (red cube) signaling distinctiveness. - Improve: - Diagrams showing money flows (current vs. reformed procurement). - Architecture diagrams for “sovereign Open Source stack” in government. #### 🔊 Aural learners - Present: - Article is text-only; no explicit audio. - Improve: - 3–5 minute audio summary or podcast segment discussing the proposal. - TTS-enabled version with clear section markers. #### 🗣️ Verbal learners - Present: - Clear narrative, concrete examples (Drupal, ICC, Schleswig-Holstein). - Defined terms like “digital sovereignty” and “upstream maintainers” by context. - Improve: - Glossary of key terms (upstream, integrator, hyperscaler). - More analogies comparing software procurement to physical infrastructure funding. #### 🧩 Kinesthetic learners - Present: - Conceptual but not hands-on. - Improve: - Step-by-step exercise for drafting a contribution-weighted RFP. - Worksheets for agencies to map their contributions to procurement criteria. #### 🧠 Logical learners - Present: - Causal chain from procurement design → funding flows → security and sovereignty. - Real-world evidence from Drupal and European migrations. - Improve: - Simple decision trees for procurement officers. - Tables comparing outcomes under traditional vs. contribution-based procurement. #### 🧑‍🤝‍🧑 Social learners - Present: - References to coalitions (APELL, EuroStack) and EU consultations. - Improve: - Discussion prompts and workshop formats for government and community sessions. - Q&A sections or moderated forums on implementation challenges. #### 🧘‍♀️ Solitary learners - Present: - Article works well for reflective reading and note-taking. - Improve: - Reflection questions at the end (“How does your organization fund upstream?”). - Self-checklists for assessing alignment with digital sovereignty goals. #### 🌿 Naturalistic learners - Present: - Indirect system/ecosystem language about public digital infrastructure. - Improve: - Make ecosystem analogies explicit (maintainers as keystone species). - Discuss environmental and sustainability benefits of shared Open Source infrastructure. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: - Likely proper headings; blog-style layout is typically screen-reader-friendly. - Improve: - Ensure all images (like the red cube) have descriptive alt text. - Confirm language attributes are set correctly. #### Keyboard navigation - Present: - Standard blog should be navigable via keyboard. - Improve: - Ensure visible focus states and skip-to-content links. - Avoid any keyboard traps in navigation or share widgets. #### Contrast and readability - Present: - Typical text vs. background ratio likely meets 4.5:1, but should be verified. - Improve: - Check large-text thresholds and line spacing for longer paragraphs. - Offer reading-mode or high-contrast view. #### Text resizing and reflow - Present: - Modern responsive site likely reflows at 200% zoom. - Improve: - Test for clipping and horizontal scrolling. - Honor prefers-reduced-motion for animations, if any. #### Media and captions - Present: - Primarily text and a static image. - Improve: - Provide image descriptions where relevant. - If future video/audio is added, include captions and downloadable transcripts. #### Forms and interactions - Present: - Minimal interactive elements (maybe comments or contact forms). - Improve: - Ensure labels, error feedback, and target sizes meet WCAG 2.2 AA. #### Standards reference - Map gaps to: - 1.4.x (contrast and reflow), - 2.1.x (keyboard), - 2.4.x (navigation/headings), - 3.3.x (if forms are present). ### 🌍 DEIB Assessment #### Cultural breadth - Present: - Focuses on Europe with specific member-state examples. - Improve: - Brief comparisons or references to similar debates in non-EU regions. #### Inclusive language - Present: - Professional, neutral tone; minimal jargon. - Improve: - Provide short plain-language summaries for policy and technical terms. #### Neurodiversity support - Present: - Structured paragraphs, clear argument flow. - Improve: - More subheadings and bullet lists to break up dense text. - Consistent pattern for examples and recommendations. #### Representation - Present: - Primarily institutional actors; individuals referenced by name for contributions. - Improve: - Highlight more diverse maintainers and organizations across Europe. #### Psychological safety - Present: - Non-inflammatory; focuses on systems, not individuals. - Improve: - Explicitly invite broad participation in consultations (including small orgs and underrepresented groups). - Link to community standards where discussion happens. ### ✅ Logical Validity #### Strong reasoning - Causal reasoning: - Claim: Skipping maintainers in procurement leads to underinvestment in security and resilience. - Strength: Grounded in long-term observation of Drupal and generalizable across Open Source ecosystems; connects incentives to outcomes clearly. - Policy prescription: - Claim: Making contribution a procurement criterion realigns incentives. - Strength: Directly targets the misalignment (who is paid vs. who maintains); uses an existing example (Drupal credit system) to show feasibility. #### Fallacies - Potential hasty generalization: - From Drupal and a few European cases to all Open Source procurement. - Fix: Acknowledge variation across sectors and include pointers to more systematic evidence. - Possible false dilemma (implied): - Proprietary hyperscalers vs. Open Source as the only options. - Fix: Briefly note hybrid or regulated cloud models as partial complements while still stressing Open Source’s unique sovereignty properties. #### Tone of voice - Tone: - Calm, policy-oriented, and constructive. - Mix of concern (“lost digital sovereignty”) and optimism (“Europe has something else: some of the world’s strongest Open Source communities”). ### 🛡️ DARVO Analysis - Deny: - No denial of harm; the article explicitly acknowledges systemic risks of current dependencies. - Attack: - Does not attack specific companies or governments; critiques procurement structures and incentive patterns. - Reverse victim/offender: - No attempt to recast maintainers or Europe as innocent victims while they are responsible for harm; instead, focuses on systemic alignment. - Overall: - The piece is advocacy, not defensive rhetoric; DARVO patterns are not present. ## 🎯 Conclusion - Bottom line: - Open Source is Europe’s most realistic path to digital sovereignty, but current procurement structures channel public money to integrators instead of maintainers. This undermines long-term security, resilience, and autonomy. - Practical next steps: - Policymakers should incorporate contribution-based criteria into public tenders and rely on transparent project-run credit systems to evaluate vendors. Maintainers, agencies, and platforms (including WordPress) should prepare by measuring, reporting, and scaling their upstream contributions in ways that align with emerging European policy. --- ## 🧱 Refactor Appendix ### 📚 Literature Split Pad - Purpose: Stage Konik CEE units that become per-source Literature notes. - Split level: **H3**. - Include verbatim quotes under 25 words and a [view highlight] link. ### [H1] Public money must fund upstream maintainers > [!quote] [Funding Open Source for Digital Sovereignty](https://dri.es/funding-open-source-for-digital-sovereignty) by [[Dries Buytaert]] via [[dri.es]]. Published 2026-01-21. Accessed 2026-01-21. > “Public money flows around Open Source instead of into it.” Two lines: Public procurement currently bypasses maintainers and rewards integrators. Aligning funding with upstream work improves security and resilience. [view highlight](https://dri.es/funding-open-source-for-digital-sovereignty#H1) #xref #articleseed ID:rw_[MISSING] ### [H2] Contribution-based procurement enables digital sovereignty > [!quote] [Funding Open Source for Digital Sovereignty](https://dri.es/funding-open-source-for-digital-sovereignty) > “The fix is straightforward: make contribution count in procurement scoring.” Two lines: Evaluating vendors by upstream contributions directs funds toward those who build and secure shared infrastructure. [view highlight](https://dri.es/funding-open-source-for-digital-sovereignty#H2) #xref ID:rw_[MISSING] --- ### 🔖 Atomic Split Pad (Zettel Candidates) - Purpose: Promote reusable claims into Atomic notes. - Split level: **H4**. - Each item: one idea, present tense, specific, testable. #### [Z1] Contribution-weighted procurement improves OSS resilience - When public contracts reward upstream work, maintainers gain capacity to harden and evolve critical infrastructure. - Pointer to article example of Drupal credit system and EU procurement debates. - Links: [[Digital-Sovereignty]] [[Public-Procurement]] [[Open-Source-Funding]] #### [Z2] Skipping maintainers increases long-term public risk - Governments that fund only integrators without supporting upstream accumulate technical debt and security exposure. - Pointer to Drupal case where feature authors are unfunded but responsible. - Links: [[Technical-Debt]] [[Security-Externalities]] [[Open-Source-Governance]] --- ### ✏️ Fleeting Queue (Extract by Selection) - Purpose: Capture quick actions or sparks for Fleeting notes. - Extraction: **Select one line** → “Refactor: Extract selection to new note (content only).” - Keep each line short and self-contained. - [F1] Draft a generic “contribution-based RFP criteria” template for public-sector WordPress projects — context/https://dri.es/funding-open-source-for-digital-sovereignty #fleeting #inbox - [F2] Map current agency contributions to a simple internal credit system to prepare for future EU tenders — context/https://dri.es/funding-open-source-for-digital-sovereignty #fleeting #inbox - [F3] Compare Drupal’s credit directory with possible WordPress equivalents (e.g., contributor profiles, Five for the Future) — context/https://dri.es/funding-open-source-for-digital-sovereignty #fleeting #inbox --- <!-- deep-read:sections end -->