Get the FREE Ultimate OpenClaw Setup Guide →

don-open-source

Scanned
npx machina-cli add skill dstotijn/developer-overheid-nl-agent-skills/don-open-source --openclaw
Files (1)
SKILL.md
2.0 KB

DON Open Source

When to Use This Skill

Use this skill when you need guidance on:

  • open source
  • publiccode.yml
  • licensing
  • CONTRIBUTING.md
  • CODE_OF_CONDUCT.md

How to Navigate

This skill contains documentation organized by topic. Browse the references below or ask about specific topics.

References

Standaarden

Tools

Tutorials


Source: https://github.com/developer-overheid-nl/don-site/tree/main/docs/open-source

Source

git clone https://github.com/dstotijn/developer-overheid-nl-agent-skills/blob/main/skills/don-open-source/SKILL.mdView on GitHub

Overview

This skill provides guidance for Dutch government open source projects, including licensing, publiccode.yml, and governance documents. It helps teams align with the Standard for Public Code to ensure compliant and well-governed OSS repositories.

How This Skill Works

The skill curates documentation by topic and links to official references (e.g., code-of-conduct-md, contributing-md, publiccode-yml) and practical tutorials. It also points to tools like the Publiccode.yml editor and parser to validate configurations and ensure alignment with the Standard for Public Code.

When to Use It

  • Setting up a new open source repository for a Dutch government project
  • Choosing an appropriate license for a government OSS release
  • Creating or updating a publiccode.yml to meet standards
  • Following the Standard for Public Code for governance and process requirements
  • Preparing CONTRIBUTING.md and CODE_OF_CONDUCT.md for a government OSS project

Quick Start

  1. Step 1: Review relevant standards (Public Code standard, code-of-conduct-md, contributing-md) and determine scope
  2. Step 2: Create or update publiccode.yml and add governance docs (CONTRIBUTING.md, CODE_OF_CONDUCT.md)
  3. Step 3: Select licenses appropriate for Dutch government use and publish with README and licenses

Best Practices

  • Align repository structure and metadata with the Standard for Public Code
  • Include a well-defined publiccode.yml that captures licenses, governance, and project metadata
  • Provide CONTRIBUTING.md and CODE_OF_CONDUCT.md to set expectations for contributors
  • Choose licenses that are compatible with government transparency and reuse policies
  • Regularly reference and follow the standards and tutorials listed under References

Example Use Cases

  • A Dutch ministry publishes an OSS repo with a compliant publiccode.yml and a clear LICENSE, CONTRIBUTING.md, and CODE_OF_CONDUCT.md
  • A city council opens a shared library under a government-approved license, documented according to the Standard for Public Code
  • A cross-government OSS project uses Publiccode.yml editor to validate its configuration and aligns with governance standards
  • An agency publishes README.md and standards-compliant documentation to facilitate reuse by other government bodies
  • A project uses the Publiccode.yml parser to ensure metadata and licensing are correctly declared before release

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers