Contributing

Please note we have a code of conduct that applies to all interactions with the project.

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

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:

• Government implementers

• Open source contributors

• Product providers

• Researchers/Academics

• Digital ID & Service delivery experts

• Policy & Governance professionals

• UX & Accesibility Advocates

Types of participation

Role	Description	Requirements	Access
Observer	Follows work, reads meeting notes, tracks specs	None	✅ Always open
Contributor	Suggests edits, joins discussions	Fill out form / Slack access	✅ Usually open
Working Member	Active in calls, votes on decisions	Continuous participation in Working Group meetings.	✅ By involvement
Facilitator / Chair	Leads or organizes the WG	Appointed by community or a GovStack committee	✅ By request or invitation

How participation works

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

1. Attend a meeting → Introduce yourself, join the discussion, find ways to contribute.

2. Contribute to specs, meeting notes, or decisions → Use GitBook, GitHub, Docs.

3. Become an active member → After consistent engagement, request formal role

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.

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 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 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 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!

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].