> For the complete documentation index, see [llms.txt](https://specs.govstack.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://specs.govstack.global/overview/25q2-1/contributing.md).

# Contributing

{% hint style="info" %}
Please note we have a [code of conduct](https://www.govstack.global/coc/) that applies to all interactions with the project.
{% endhint %}

The GovStack initiative aims to build a common understanding and technical practice on fundamental reusable and interoperable digital components that can be used to implement a **Whole-of-Government** approach to interoperability, which we collectively refer to as Building Blocks. 

**GovStack Specifications** are the core product focus of the **GovSpecs** offering within the initiative. Specifications are quality requirements and principles for the building blocks. Specifications are meant to be applied for public tenders for new digital service component developments as well as for validating digital government oriented solutions made available on the market.

GovStack Specifications are built by experts on the field through **Working Groups**, that convene to discuss the requirements, principles, functionalities and standards required to implement a digital, interoperable service, suitable for the public sector, that complies with the Building Block's approach to interoperability. You can read more about this approach in [Architecture and Nonfunctional Requirements](/overview/25q2-1/architecture-and-nonfunctional-requirements.md)

The best way to become a contributor of the GovStack initiative is by joining a Working Group. Here you can find the information you need about how to participate in one.

## Who can contribute?

GovStack Working Groups are open to experts, implementers, civil society members, technologists, and other contributors passionate about building inclusive digital public infrastructure. Some examples are:

{% columns %}
{% column %}

* Government implementers
* Open source contributors
* Product providers
* Researchers/Academics
  {% endcolumn %}

{% column %}

* Digital ID & Service delivery experts
* Policy & Governance professionals
* UX & Accesibility Advocates
  {% endcolumn %}
  {% endcolumns %}

## Types of participation

<table data-full-width="false"><thead><tr><th width="160">Role</th><th width="197">Description</th><th width="225">Requirements</th><th>Access</th></tr></thead><tbody><tr><td>Observer</td><td>Follows work, reads meeting notes, tracks specs</td><td>None</td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span> Always open</td></tr><tr><td>Contributor</td><td>Suggests edits, joins discussions</td><td>Fill out form / Slack access</td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span> Usually open</td></tr><tr><td>Working Member</td><td>Active in calls, votes on decisions</td><td>Continuous participation in Working Group meetings.</td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span> By involvement</td></tr><tr><td>Facilitator / Chair</td><td>Leads or organizes the WG</td><td>Appointed by community or a GovStack committee</td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span> By request or invitation</td></tr></tbody></table>

## How participation works

{% columns %}
{% column %}

1. Explore existing Working Groups.\
   Browse WGs Directory.
2. Read the Group Charter & Scope.\
   Understand their purpose, meetings, and open tasks.
3. Check Access Type\
   **Open groups:** Anyone can join by link\
   **By request:** Submit interest form → reviewed by chair
4. Join the Slack Channel → Primary communication tools
   {% endcolumn %}

{% column %}
5\. **Attend a meeting** → Introduce yourself, join the discussion, find ways to contribute.
6\. **Contribute to specs, meeting notes, or decisions** → Use GitBook, GitHub, Docs.
7\. **Become an active member** → After consistent engagement, request formal role
{% endcolumn %}
{% endcolumns %}

## Frequently Asked Questions

1. **How can I suggest changes to a specification?**\
   Although it is best to get in touch with the Working Group first, you may also want to submit formal feedback to a specification. You can do so by Opening an issue on their respective [Github repository](https://github.com/GovStackWorkingGroup/).
2. **The Working Group to the Specification I'd like to join is inactive. What can I do?**\
   You can become an organizer. Get in touch with us using the [Be part of our community form ](https://www.govstack.global/join-our-tech-community/)and explain your proposal.
3. **I want to propose a new Specification**\
   We are always on the lookout for new domains that can be specified using the GovStack approach to Whole-of-Government interoperability. Feel free to get in touch with us by filling out the [Be part of our community form](https://www.govstack.global/join-our-tech-community/) and we'll reach out to you.
4. **I represent a product that wants to comply to the specification, or a team that wants to implement GovStack specifications** \
   We have an offering just for this. [GovMarket](https://www.govstack.global/our-offerings/govmarket/) bridges the gap between governments and software or service providers based on a common reference – the GovSpecs. Be sure to check the GovMarket page to see the options of how you can get involved!&#x20;

## How This Might Evolve Over Time

* Working Groups may open or close participation depending on current deliverables or roadmap phase.
* Some may move from closed pilot mode to public collaboration.
* Contribution rules may adapt (e.g. GitHub participation, review cycles).
* Decision-making processes can evolve — you’ll always find updates in the \[Participation Guide].


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://specs.govstack.global/overview/25q2-1/contributing.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.