Signalen Product Steering Meeting 18th of February, 2021, 11:00 to 12:00

Chair: Felix

Video Chat using Jitsi: https://meet.publiccode.net/SignalenProductSteering

This note: https://hackmd.io/9kmLSzNaQC-S3-AJ0t8x2g?edit

Shared Product backlog: https://github.com/orgs/Signals/projects/2

Product steering and feature requests documentation: https://github.com/Signalen/product-steering

Create feature request: https://github.com/Signalen/product-steering/issues/new?assignees=&label...]

Slack Channel: https://join.slack.com/share/zt-heae6d92-sqH1xvJvJQ_RMpAAMnHLKQ

Mailing list: https://lists.publiccode.net/mailman/postorius/lists/signalen-discuss.lists.... (Check spam)

Board: https://miro.com/app/board/o9J_kkwkuBE=/ Agenda:

- Community updates Jacco - Update implementation Guide - Centralized issue management - Website update

Update Jacco

Jacco shares draft program from the community meeting. Would be nice to have a keynote speaker who can share experience about working in open-source with community and government. The theme of the community meeting is onboarding of new interested municipalities to start using Signalen and sharing learning experiences of municipalities who are already testing and using Signalen.

Result field lab, there are market parties interested in using Signalen. Talking about how to work together with vendors will also be part of the community day. Jacco will also want to give every participant a demo environment of Signalen. Feedback is positive on the agenda. Bram mentions to also make the target audience clear in the program.

Jacco will work on program with Alba and Felix. Will gather input and feedback from Astrid and Bram.

The sprint review meeting will be repurposed to a community call and a separate sprint review will be planned in the coming month. Update implementation guide

Felix showed a generic user manual on https://docs.signalen.org and explained everyone can add or change the content. Bram was interested to also include the learnings of Den Bosch into the website. Felix mentioned everyone is free to add and contribute and if they want some information or demo on how to do that just reach out.

Arvid is available to create an implementation guide. Arjo proposed to include writing an implementation guide as part of the implementation work Arvid is doing for Almere. Arjo will discuss this with his team and report back in the next product steering meeting. Centralized issue management

Arvid and Felix will put epics and feature requests from Amsterdam on the product steering repo. We will also invite Amy van Sommeren from Den Bosch to join that meeting. After having collected those we can have more product steering discussion about all the epics on the table which will form the basis for a first roadmap. Website update

The signalen website now has a news section where we can publish articles or information relevant to the Signalen community. Felix asked everyone if they have something to share which is relevant to put an article on GitHub or send a suggestion to the Signalen mailing list.

Furthermore, these notes will be put on the https://github.com/Signalen/product-steering repository. Joint mission / Vision

We also briefly discussed working on a joint mission and vision action point. For now, we keep it on the list and continue to work on it after we have made some progress with centralizing all feature epics. Here is a work-in-progress example of the mission and vision for OpenZaak https://github.com/open-zaak/open-zaak/blob/17d32ea48bd69238776410f8a7375681... The reason why describing this is important is outlined in the standard for public code: https://standard.publiccode.net/criteria/document-objectives.html Agenda next meeting

To be decided Action points

Next chair: ??? Action Responsible Due date Arjo will consult with team to make writing the implementation guide part of Arvid assignment when implementing Signalen in Almere Arjo 18-02-2021 Write down short vision/mission Signalen ALL TBD