Mission

We contribute to the GovStack vision with our mission to build a community within and around the GovStack project by identifying and addressing the motivations that drive people to participate in the project. We create the environment to participate that promotes a growing community of contributors.

In practice, this means that the team is responsible for researching the needs of contributors, and potential contributors, to the GovStack project and creating the systems and process that best meet those needs. In many cases, this will mean both documenting current processes in ways that are digestible by the community and by helping to improve the systems and process we already have. It may also include providing education and support for people in various roles in the current community so that we are all best able to support the growing community.

Further Activities

The activities of the Community Management can be summarised as the following: 

• CommunityMeet

  • Regular meetings within the GovStack Tech Community (Working Group members, Commit Leads, Triage Leads) will take place online every three months. The Tech Community will have the opportunity to briefly share their updates. There will also be at least one GovStack contribution each time (e.g. country update, CoP update, capacity dev. update) by the responsible team. (--> first online Meet up: February)

  • Once a year, the meeting is held in person as part of an overarching GovStack event (e.g. Country Deep Dive, Roadshow, RTC) or an international conference taking place at the same time. The aim is to continue to get to know the GovStack community in person and create a space for dialogue. In addition, the Tech Community should get an idea of how their theoretical GovSpecs are being received by partners and implemented in practice and what great value they deliver in reality. 

• CommunityGrowth

  • As a point of contact for new interested contributors who contact GovStack, the Community Manager receives such requests via email/Website Forms/ LinkedIn and forwards them to the respective Triage Lead, who then takes over further communication and onboarding.  

  • The Community Management outreaches to further potential contributors according to specifc needs

• CommunityOverview

  • The documentation of current Tech Community members (e.g. who is actively engaged in the WGs, which WG is not working anymore, which is working on a new version etc.) will be kept up to date and constantly improved.

  • The visibility of the Tech Community is being improved (e.g. on the website, LinkedIn etc.)

     

    Open

    
    Open

    

Deliverables

See Community Growth Team Roadmap (old) but the high level items are:

1. Improve onboarding materials for the project

2. Coordinate management of the tooling used by the project

3. Provide support and education to the Building Block Leads, enabling them to recruit contributors and support their contributions to the project

4. Organise at least one in-person technical community event in 2024

5. Coordinate public recognition (e.g. on Social Media) of Community Contributors

Other Information