- openzaak-discuss - nextcloud-publiccode.maadix.org

Important product steering updates
by Felix Faassen 16 Mar '21

16 Mar '21

Dear product steering team, We would like to take this opportunity to provide you with some updates surrounding product steering. Issues & Feature request process As discussed in our previous product steering call we decided to streamline this process. This means the separate product-steering repository has been deleted and that the 2 issues on it are transferred to the openzaak repository where all openzaak issues live. After speaking with the developers, we introduced the label ‘product-steering’ to indicate these are issues the product steering group should discuss or decide upon. We already taken the liberty to select a few good first product-steering group issues to discuss for our next meeting which you can find on the project board “Backlog voorbereiding” in the column intake. - Feature requests, bugs, improvements: https://github.com/open-zaak/open-zaak/issues - To create new feature requests: https://github.com/open-zaak/open-zaak/issues/new?assignees=&labels=product… - Project board “Backlog voorbereiding”: https://github.com/open-zaak/open-zaak/projects/3 Technical steering backlog pruning In an effort to reduce the clutter in the backlog, the Technical steering team spent time reviewing and pruning what is already there. Part of this review included identifying issues that are high priority from a technical point of view in order to provide input to product steering. The current state of their work can be seen here: https://hackmd.io/jmp49FfpRxa9NLg6RAhYTw We can’t expect to discuss everything in one meeting, so we’ve labeled a few for discussion in the first product steering meeting. We also placed these issues on our product backlog. We hope that the product steering team will gradually work through issues from tech steering in the upcoming product steering meetings. New member for product steering group During the pruning session the team noticed an issue from Johan Groenen of TiltShift asking to join the product steering group. The issue was created in December so it would be good to let him know he is welcome as soon as possible. If there are no objections to him joining we will invite Tiltshift to the upcoming product steering meeting. (this is the issue with the request: https://github.com/open-zaak/open-zaak/issues/748) Kind regards, Eric & Felix -- Felix Faassen, Codebase steward Foundation for Public Code | https://publiccode.net github.com/publiccodenet | github.com/felixfaassen felix(a)publiccode.net | +31 624633278

1 0

OpenZaak ecosysteem infographic/plaatje
by Felix Faassen 24 Feb '21

24 Feb '21

Beste Allemaal, Zoals besproken in de product steering leek het mij een leuk idee om een infographic / plaatje te maken van de OpenZaak communtiy. Een plaatje dat in 1 keer laat zien wat OpenZaak is, wie het gebruikt en welke integraties met producten en leveranciers er zijn. We zouden dit plaatje op de website kunnen gebruiken en ook op de commonground pleio. Maar wellicht bestaat er al zo'n plaat. <https://miro.com/app/board/o9J_lXSQCCU=/> Ik heb een heel klein voorzetje gemaakt: https://miro.com/app/board/o9J_lXSQCCU=/ Als jullie dit ook waardevol vinden nodig ik je van harte uit om er eens naar te kijken en nog beter aan toe te voegen. Mocht je het niet waardevol vinden of is er al een dergelijk plaatje dan hoor ik dat uiteraard ook graag. Groeten, Felix -- Felix Faassen, Codebase steward Foundation for Public Code | https://publiccode.net github.com/publiccodenet | github.com/felixfaassen felix(a)publiccode.net | +31 624633278

1 0

Meeting notes - technical steering meeting 2021-02-17
by Jan Ainali 24 Feb '21

24 Feb '21

Attendees - Eric Herman, Foundation for Public Code - Jan Ainali, Foundation for Public Code - Tjerk Vaags, Contezza - Joeri Bekker, Maykin Media - Sergei Maertens, Maykin Media <https://hackmd.io/rlyr147URxO3TO3yocyQiw#Agenda>Agenda - Agenda items - installation signup and vendor list and contact info - “dev-grooming” of the backlog - https://www.thecleaningmob.nl/ ? - Next meeting & chair <https://hackmd.io/rlyr147URxO3TO3yocyQiw#Notes>Notes <https://hackmd.io/rlyr147URxO3TO3yocyQiw#Installation-signup-and-vendor-lis…>Installation signup and vendor list and contact info Nothing done yet, a big question is where to store it. Jan and Eric will come back with a proposal. open-zaak#871 <https://github.com/open-zaak/open-zaak/issues/871> <https://hackmd.io/rlyr147URxO3TO3yocyQiw#%E2%80%9CDev-grooming%E2%80%9D-of-…>“Dev grooming” of the backlog Tjerk will send an invitation, 14.00-16.00 next Wednesday. (The product steering team has meeting 15.00-16.00.) <https://hackmd.io/rlyr147URxO3TO3yocyQiw#The-cleaning-mob>The cleaning mob Would OpenZaak like to participate in it? Sergei: send e-mail to discuss list with results of McGabe complexity analysis -> can be referenced to TheCleaningMob. <https://hackmd.io/rlyr147URxO3TO3yocyQiw#Various-tips>Various tips - Jan tipped that OWCcon21 has an open call for presentations <https://www.ow2con.org/view/2021/Call_For_Presentations?year=2021&event=OW2…> . - Jan also tipped that Open Summer of code will come to the Netherlands this year, organized by the Open Fields Foundation <https://www.openfieldsfoundation.com/>. <https://hackmd.io/rlyr147URxO3TO3yocyQiw#Open-Zaak-Helm-amp-Common-Ground-d…>Open Zaak Helm & Common Ground dashboard Conduction has a common ground dashboard (managing infrastructure/applications installations). Open Zaak now has Helm charts <https://github.com/open-zaak/charts>, which should provide the required integration. <https://hackmd.io/rlyr147URxO3TO3yocyQiw#Misc>Misc - Haarlem -> sponsoring Podman support (alternative for Docker). - Community signals complicated Ansible-based deployment. - Documentation quite elaborate on Docker/Kubernetes -> refactor documentation. - Usability of admin interface has limits - there should be a frontend (layer 5) interface for functional administrators. Topic for product steering group. - Request for review of pull request 824 <https://github.com/open-zaak/open-zaak/pull/824>. - Documenten API unclear behaviour may affect Open Zaak ( https://github.com/VNG-Realisatie/gemma-zaken/issues/1768) <https://hackmd.io/rlyr147URxO3TO3yocyQiw#Next-meeting-amp-chair>Next meeting & chair March 17th - Sergei -- Jan Ainali, Codebase Steward jan(a)publiccode.net | +46762122776 | @jan_ainali Foundation for Public Code https://publiccode.net

1 0

Re: Recording of podcast on Monday, 1 February
by Jan Ainali 08 Feb '21

08 Feb '21

Hello, This episode is now available here: https://podcast.publiccode.net/e/3-sergei-maertens-and-tjerk-vaags-openzaak/ (or find it by searching in your favorite podcast app). The slightly longer recording is available here: - YouTube <https://www.youtube.com/watch?v=1xojrumKgfA> - Periscope <https://www.pscp.tv/w/1gqxvoRWjgwKB> - Facebook <https://www.facebook.com/publiccodenet/videos/321846445885858/> -- Jan Ainali, Codebase Steward jan(a)publiccode.net | +46762122776 | @jan_ainali Foundation for Public Code https://publiccode.net

1 0

Open Zaak 1.3.4 released
by Sergei Maertens 05 Feb '21

05 Feb '21

Version 1.3.4 is a regular maintenance release, fixing a number of bugs, improving the documentation and providing some more flexibility in the deployment tooling. We're proud to announce the community-contributed Helm charts <https://github.com/open-zaak/charts> for Open Zaak and Open Notificaties, providing an alternative way of deploying both projects on (Haven <https://haven.commonground.nl/>-compliant) Kubernetes clusters. Additionally, we've documented the process on how to deal with security vulnerabilities <https://open-zaak.readthedocs.io/en/stable/support/security.html>, with support from the Foundation For Public Code. We hope this can serve as a source of inspiration for other Common Ground projects. You can find a complete list of the changes in the release notes <https://open-zaak.readthedocs.io/en/stable/development/changelog.html#id1>. As always, container images with the appropriate version tags are published on Docker Hub <https://hub.docker.com/r/openzaak/open-zaak>.

1 0

Recording of podcast on Monday, 1 February
by Jan Ainali 28 Jan '21

28 Jan '21

Hello, On Monday we will be recording a podcast with Sergei Maertens and Tjerk Vaags about the security issue that was resolved in version 1.3.3. It will be streamed here, and you can ask questions in the chat too: YouTube: https://www.youtube.com/watch?v=1xojrumKgfA Facebook: https://www.facebook.com/285004318294/posts/10157974663423295/ But if you prefer a polished podcast version, you can sign up here: https://podcast.publiccode.net/ -- Jan Ainali, Codebase Steward jan(a)publiccode.net | +46762122776 | @jan_ainali Foundation for Public Code https://publiccode.net

1 0

Happy new year and website live
by Felix Faassen 04 Jan '21

04 Jan '21

Hi everyone, First I want to wish everyone a happy and healthy new year and hope we can greet each other in good health in real life somewhere in the near future. As discussed at our previous OpenZaak product steering meeting we decided to put the new website for OpenZaak online. You can find it here: https://openzaak.org Please have a look at it and if you have improvements or other feedback please make an issue here: https://github.com/open-zaak/open-zaak-website/issues or make the change yourself. We will gradually improve the website as we go along. Kind regards, Felix -- Felix Faassen, Codebase steward Foundation for Public Code | https://publiccode.net github.com/publiccodenet | github.com/felixfaassen felix(a)publiccode.net | +31 624633278

1 0

Open Zaak 1.3.3 and Open Notificaties 1.1.2 released (fixes CVE-2020-26251)
by Sergei Maertens 17 Dec '20

17 Dec '20

Today, a bugfix release of Open Zaak and broader support release of Open Notificaties have been issued. Open Zaak 1.3.3 fixes a number of bugs, including a fix for a CORS-related security vulnerability. You can find more details in the security advisory <https://github.com/open-zaak/open-zaak/security/advisories/GHSA-chhr-gxrg-6…>. We recommend that you update your installations as soon as possible. The full release notes can be found in the changelog <https://open-zaak.readthedocs.io/en/stable/development/changelog.html#id1>. Open Notificaties 1.1.2 changed the deployment tooling to more easily support different target platforms. Most notably, RHEL/CentOS are now explicitly supported. Open Notificaties itself (the application) has not changed. As always, images with the appropriate version tags are published on Docker Hub <https://hub.docker.com/u/openzaak>.

1 0

Status update on CI migration & related issues
by Sergei Maertens 15 Dec '20

15 Dec '20

Hi all - this community update aims to give some insight in recent maintenance that was done to the Open Zaak projects on Github. We were forced to undertake a number of actions because of external influences, with the common theme of being "budget" related. Most notably, our Continuous Integration was affected by these items: - Travis CI is no longer as Open Source friendly as they used to be ( https://github.com/open-zaak/open-zaak/issues/773) - Docker Hub is aggressively applying rate limits and altered the retention conditions of container images ( https://github.com/open-zaak/open-zaak/issues/774) - Postman mock endpoint collections (hosted) are expensive ( https://github.com/open-zaak/open-zaak/issues/790) To resolve the CI situation, we've decided to migrate to Github Workflows/Actions. Github Workflows/Actions are free for public (open source) repositories, and have a budget of about 2000 minutes/month for private repositories, which serves our needs well. However, this migration required time (for free) from the community - all in all this cost about 10 hours to make the necessary changes. Additionally, Open Zaak has a test suite that verifies the compliance with the "API's voor Zaakgericht Werken" standard. This test suite used some mock endpoints hosted on postman.io which became unavailable due to lack of funding for that subscription. Since this is an extremely important step to have as part of our CI, it was decided to implement a non-subscription alternative ourselves, which cost another 2-3 hours to fully set in place. Of course the good news is that we're confident in the Github Actions approach, and we've been able to expand the build matrix to include explicit support for a range of PostgreSQL versions, Postgis versions and flavours of CMIS-adapter bindings. CI is also a bit more performant now, because we can reuse build artifacts in different build steps. We have some lingering issues to resolve - it appears that something in the test suite is not 100% deterministic, leading to erratic builds, but I'm sure that will be sorted out. Best, Sergei

1 0

OpenZaak testing and deployment infrastructure
by Eric Herman 23 Nov '20

23 Nov '20

Dear OpenZaak community members, We see our role as ["Providing long term product sustainability"]( https://about.publiccode.net/activities/codebase-stewardship/goals#providin…) in codebase stewardship. We should provide this infrastructure to the entire community as that lies outside of the mandate of any individual organization whilst everyone depends on it for their operational continuity. As you know during the last technical steering meeting important issues were raised concerning the existing testing and deployment infrastructure. Due to a change in the business model of the services used, the OpenZaak test and deployment infrastructure will become unavailable if no action is taken. In the short term, we propose to take over responsibility for the existing infrastructure. We can do this by paying for the services. In the mid-to-longer term we strongly recommend a transition to another more open and accessible platform. To achieve a healthy and strong community around OpenZaak, regardless of what's stated above, we request public organizations to become members of the Foundation for Public Code Vereniging. Membership is an investment in the social and technical infrastructures to achieve the goals of OpenZaak and open source in gemeenten. We propose to take over the Travis and DockerHub accounts and are ready to operationalize this as soon as that happens. Please let us know how you think about this and let's discuss how we can move this forward. Kind regards, Eric & Felix -- Eric Herman, Lead codebase steward for quality Foundation for Public Code | https://publiccode.net github.com/publiccodenet | github.com/ericherman eric(a)publiccode.net | +31 620719662 | @Eric_Herman

1 0

2024

2023

2022

2021

2020

openzaak-discuss