openzaak-discuss October 2020

openzaak-discuss@lists.publiccode.net

3 participants
2 discussions

Open Zaak product steering group meeting 2020-10-21 notes

by Joeri Bekker

OpenZaak Product Steering Meeting - 21 October 2020, 15:00 to 16:00 Meeting link: https://meet.community.publiccode.net/OpenZaakProductSteeringGroup Mailinglist: https://lists.publiccode.net/mailman/postorius/lists/openzaak-discuss.lis... Slack Channel: https://samenorganiseren.slack.com/archives/CT6UH711Q <https://hackmd.io/_o_N4lI1SRGrCL0g7GNs7Q?both#Attending>Attending - Felix Faasen, Foundation for Public Code - Alba Roza, Foundation for Public Code - Jan Ainali, Foundation for Public Code - Joeri Bekker, Maykin Media - Niels Lindeboom, Dimpact - Hugo ter Doest, Dimpact - Silvion Moesan, OPEN.satisfaction - Olav Allema, Contezza - Tahir Malik, Contezza - Jolanda van de Kooij (emailed g.vandennoort(a)exxellence.nl) - Peter Moen, Exxcellence - Lazo Bozarov, Gemeente Utrecht (invited late) <https://hackmd.io/_o_N4lI1SRGrCL0g7GNs7Q?both#Agenda>Agenda 1. Agenda 2. Actions from previous meeting 3. Discuss mission, vision and scope 4. Future features and roadmap 5. Evaluate governance/future agenda 6. New or changing members 7. Any other thoughts members want to bring in <https://hackmd.io/_o_N4lI1SRGrCL0g7GNs7Q?both#Notes>Notes <https://hackmd.io/_o_N4lI1SRGrCL0g7GNs7Q?both#1-Agenda>1. Agenda <https://hackmd.io/_o_N4lI1SRGrCL0g7GNs7Q?both#2-Actions-from-previous-mee...>2. Actions from previous meeting ActionResponsibleDue date 1. Ask steering group for representatives in Product Group, post in the CommonGround Niels, Joeri October 21st, 2020 2. Create draft pull request on GOVERNANCE.MD <http://governance.md/> members Peter & Joeri October 21st, 2020 3. Create Mission & Vision Draft on OpenZaak product Hugo October 21st, 2020 1. Invite Edwin/Rita from Delft for this group 2. See: https://github.com/open-zaak/open-zaak/pull/746/files?short_path=b60c6a9#... - All attendees agreed 3. Hugo will do this for next time. <https://hackmd.io/_o_N4lI1SRGrCL0g7GNs7Q?both#3-Discuss-mission-vision-an...>3. Discuss mission, vision and scope Notes from all attending members, as a guideline for the draft document. - Open Zaak product can be used by public organizations, to be open source so everyone can use it. The product is based on zaakgericht werken. - Scoping: What does it mean: Zaakgericht werken (ZGW). Is it limited to ZGW, or extend to “related” to ZGW. - Scoping: Maybe not only limit to ZGW - Also other suppliers should be able to use it, implement and contribute - Follow the national API standards for case-oriented working (ZGW API’s) developed by VNG Realisatie - We are (among) the first users of the standards and we need to propose changes to the standards if needed. - As a mission: We are offering municipalities a solution for ZGW. - “Laagdrempelige” solution in both tech, documentation, service (desk) - Mission: Have a “golden-record” (one single truth) within the organization <https://hackmd.io/_o_N4lI1SRGrCL0g7GNs7Q?both#4-Future-features-and-roadmap>4. Future features and roadmap From the technical steering team: - Post-installation configuration - i-Navigator (and others) support - Better Catalogus management interface - Improve archiving parameters integration - Implement password reset functionality - Provide selectielijst on NLX - Update the API versions - Add klantinteractie APIs (or not) - Bring to core municipality group and get feedback - Allow for “lokale verorderingen” (to the standard) - Fully implement Opschorten functionality - Implement a Search engine (Elasticsearch/SOLR) - Bring to core municipality group and get feedback Additions from the product steering team: - No additonal items provided Suggestion to decide on priority: https://www.scaledagileframework.com/wsjf/ What should we do with this list? <https://hackmd.io/_o_N4lI1SRGrCL0g7GNs7Q?both#5-Evaluate-governancefuture...>5. Evaluate governance/future agenda - Nothing discussed due to time. <https://hackmd.io/_o_N4lI1SRGrCL0g7GNs7Q?both#6-New-or-changing-members>6. New or changing members - Added Rita Berghuis, Delft - rberghuis(a)delft.nl <https://hackmd.io/_o_N4lI1SRGrCL0g7GNs7Q?both#7-Any-other-thoughts-member...>7. Any other thoughts members want to bring in - Next meeting: November 18, 2020 - For next agenda: - Budget - Should we communicate back to the core group - What should we do with the roadmap items? - Tahir will chair the next meeting <https://hackmd.io/_o_N4lI1SRGrCL0g7GNs7Q?both#New-actions>New actions ActionResponsibleDue date 1. Create Mission & Vision Draft on OpenZaak product Hugo November 18, 2020 2. Invite Delft Joeri November 18, 2020

2 years, 5 months

Open Zaak technical steering group meeting 2020-10-21 notes

by Sergei Maertens

*Attending* - Eric Herman, publiccode.net - Jan Ainali, publiccode.net - Joeri Bekker, Maykin Media - Sergei Maertens, Maykin Media - Tahir Malik, contezza.nl - Tjerk Vaags, contezza.nl Anton Boerma (exxellence.nl) could not attend. *Agenda items* 1. Commit and merge rights to the Open Zaak repository 2. Roadmap draft 3. Architectural principles and code style 4. PR containing Helm Chart 5. Other items *Notes* *Commit and merge rights to the Open Zaak repository* Merging pull requests to master is currently limited to two people: - Joeri Bekker (Maykin Media) - Sergei Maertens (Maykin Media) Nobody has permission to push directly to master because of the branch protection rules in Github. Anyone else who needs merge rights should bring this up during a technical steering group meeting, where a decision is made using a simple majority vote. We want to avoid that merge rights are assigned simply as a "symbolic" gesture, even if you do not actively contribute or review technical pull-requests. Any technical steering group member should be able to create branches directly in the Open Zaak repository (i.e. a fork should not be needed). For that reason Tjerk will be added to the developers group on Github, and Anton will be asked at the next meeting. *Roadmap draft* The Roadmap draft in https://github.com/open-zaak/open-zaak/pull/736 was collectively discussed to ensure that everyone understands the meaning of the items on the roadmap. The roadmap will serve as input to the product steering team to prioritize the items and sort out budget. A number of extra roadmap items were brought up, but not added yet: - Updating the API versions from 1.0.x stable to 1.1.x, estimated as medium/large size. VNG is close to releasing 1.1 versions of (most of) the existing APIs, and Open Zaak should implement these. - Adding the "customer interactions" APIs (or not). VNG is about to release three new APIs that fit the "zaakgericht werken" landscape. There is a rough consensus that these APIs should not be added to the codebase of Open Zaak, but should rather exist in a separate codebase (following the Open Zaak / Open Notificaties pattern) - Allow for "lokale verorderingen". There are valid reasons to diverge from "Selectielijst"-criteria, which is currently enforced by Open Zaak because the standard prescribes this. The team shall formulate how the standard should be changed and recommend this to VNG (small size). Only then something can be done in Open Zaak (medium size). - Fully implement "Opschorten" functionality. Cases can be put on hold, but currently nothing is done with this information. This should affect the "planned due date" of a case. A proposal for implementation will be made, together with a proposal to VNG to describe this explicitly in the standard. - Implement a search engine (Elasticsearch/SOLR). Search, indexing and performance is a large topic that should be tackled. User stories will be created in the Open Zaak repository, and then it will be judged if this falls within scope or should be brought up with VNG *Architectural principles and code style* Time was running out, so every member was asked to review the pull request ( https://github.com/open-zaak/open-zaak/pull/736) and either approve it, ask for clarifications or request changes. *PR Helm Chart* Early July 2020 *rjzondervan* submitted a pull request adding support for Helm Charts (https://github.com/open-zaak/open-zaak/pull/640). The PR has been reviewed with changes requested, but there has not been any follow-up since. We noted that there are no suitable maintainers for Helm charts in the group. We will ask if these charts can be maintained and if the feedback will be processed and bring it up again during the next meeting. *Next meeting* The next meeting is not planned yet, so we'll keep an eye on the next product steering group meeting and try to plan it before that. Sergei will send invites for it.

2 years, 5 months

2023

2022

2021

2020

openzaak-discuss October 2020