Attending - Anton Boerma, Exxellence (left around 14:40 for technical reasons) - Eric Herman, Foundation for Public Code - Jan Ainali, Foundation for Public Code - Joeri Bekker, Maykin Media - Sergei Maertens, Maykin Media - Tahir Malik, Contezza (could not attend) - Tjerk Vaags, Contezza <https://hackmd.io/afAA4_-9QNaDJ4nKx1hs6g#Agenda>Agenda - Introduction/agenda items - Support questions on (Common Ground) Slack - (Travis) CI - PR#640 - Helm Support - Questions about importing catalogi - Next meeting & chair <https://hackmd.io/afAA4_-9QNaDJ4nKx1hs6g#Notes>Notes <https://hackmd.io/afAA4_-9QNaDJ4nKx1hs6g#Support-questions-on-Slack>Su... questions on Slack The Slack channel is here <https://samenorganiseren.slack.com/archives/CT6UH711Q>;. The Slack channel is used, almost on a daily basis questions are asked, often technical in nature. Currently, it looks like only 1-2 community members actively handle questions. This takes about 15-30 minutes per question, often with looking up something in the docs/codebase. The annoying thing is that it happens in-between other things unrelated to Open Zaak - stealing valuable mind-space. This is something that should be distributed more by community members. Tjerk has experience being a consultant and handling initial questions, and forwaring them to development (team) if needed. Eric remarks that we must make it clear how much time a person invests into this, so that it can be invoiced by the organization. Joeri indicated to municipalities that this costs time (and money), they reply “we should do something about it” but nothing really happens (yet). Suggestion (from Joeri): municipalities make it part of the procurement that suppliers/vendors allocate time to support of Open Zaak itself. Anton states that this is exactly what they are planning. <https://hackmd.io/afAA4_-9QNaDJ4nKx1hs6g#Travis-CI>(Travis) CI To continue CI something needs to change. - .org -> .com migration, need to apply for open-source credits for free builds - CI pipeline relies on Travis for PRs, quality control and publishing of Docker images - moving to Github actions? Buying a subscription? - Eric mentions experience with hosting gitlab runners - Travis commercial package is around EUR 3.000 per year - time sensitive - 31 Dec. is deadline - Joeri will mention this in the product steering group - Sergei will be contacting Travis about Open Source build & keep Eric in the loop - Foundation for Public Code might help - Anton suggest buying 2-3 months of paid subscription to ease the transition <https://hackmd.io/afAA4_-9QNaDJ4nKx1hs6g#PR640---Helm-Support>PR#640 - Helm Support See: https://github.com/open-zaak/open-zaak/pull/640 Follow-up from previous meeting, where the staleness of this PR was discussed. Anton will be acquiring Helm knowledge in the near future, this introduces possibility for support from within the community. PR will stay open but marked as won’t merge, plan is to take the input from the contribution and publish it as a helm chart on a public repository and include installation instructions in the documentation. Thereby not merging the chart/templates into the Open Zaak codebase directly. We will make a note in the PR thread about this. <https://hackmd.io/afAA4_-9QNaDJ4nKx1hs6g#Questions-about-importing-catalo... about importing catalogi Tjerk: Customers have test/production environments. When transferring from test to production, catalogus name changes for example. All objects are unpublished on import -> user has to publish them after import. Question is more suited for github issue, but we have time :-) Comments Joeri: - both things are intentional - export is based on API standard -> exports in format of API (no catalogus name in standard) - publishing: also intentional - after you import you might want to adjust things => easy solution: bulk publish action (create Github issue) - Eric mentions: example export that could be a RFC on how the standard could/should be changed (adding name to catalogus resource) - different flavours of export are also an option <https://hackmd.io/afAA4_-9QNaDJ4nKx1hs6g#testopenzaaknl-domain> test.openzaak.nl domain Runs a test environment, on Kubernetes. Used for testing deployment amongst others. Maykin has been paying that this year. Question: is there any need for this? MiniKube (or others?) may be a viable option for local testing/development, so the cluster will be shut down (and test.openzaak.nl will cease to exist). Important! -> affects selectielijst.openzaak.nl, this needs to be migrated and be paid for -> this is the default selectielijst service and is *required* for good operation of Open Zaak <https://hackmd.io/afAA4_-9QNaDJ4nKx1hs6g#Docker-Hub>Docker Hub Docker is introducing limits for pulls (200 per 6 hours) and starts to delete stale (= no pulls in a while) images. This means at some point, you can not pull Open Zaak from Docker, and that Open Zaak 1.0.0 (ie. not the latest version) at some point might disappear. Joeri will create a Github issue for this. <https://hackmd.io/afAA4_-9QNaDJ4nKx1hs6g#Next-meeting-amp-chair>Next meeting & chair December 16th, Wed. 2pm-3pm Chair: Tjerk Vaags, will collect agenda points and send invites