# Open Zaak Technical Steering Group

## Jan 10 2024

### Attendees

- [x] Jan Ainali, FFPC
- [x] Joeri Bekker, Maykin Media
- [] Anton Boerma, Exxellence (was excused)
- [x] Eric Herman, FFPC
- [] Sergei Maertens, Maykin Media (was excused)
- [x] Tahir Malik, Contezza
- [] Rick de Rooij, Contezza (was excused)
- [x] Daniel Langeveld, WeAreFrank
- [x] Sander B, WeAreFrank

### Agenda

- OpenZaak insight release 1.10 and 1.11
- OpenZaak fixtures import feature
- Indexing OpenZaak with SOLR
- Contezza Alfresco-DRC Open Source status

### OpenZaak insight release 1.10 and 1.11

Joeri reported about the previous release, 1.10, which was released two months ago. Mostly an API update. 1.10.1 followed soon after where some things were removed from the image and image scanning was added to the CI/CD pipeline.

1.11 is ongoing will include new API functionality for expansions reflecting the updated VNG specification. Expected to be released later in January.

After 1.10 CMIS will not be developed anymore. It may possibly have a role in the municipality landscape, but there is a low demand now. If reimplemented, it would be better as a separate extension than in core OpenZaak.

### OpenZaak fixtures import feature

Customers want this feature pulled into the main OpenZaak repo. How are we going to do that?
https://github.com/Contezza/openzaak-packaging
In short: customers want to supply the fixtures as an env so they can configure the same image within the OTAP street

Contezza will make a pull-request to get this feature analyzed and hopefully included in a next release.

### Indexing OpenZaak with SOLR

We've got a production use-case which indexes the zaakeigenschappen en zaaktoelichting (still need to make it dynamic to index which-ever property you want)

The Alfresco Open Zaak Solr (AoZs) application makes it possible to index Zaken in Solr and execute searches in Solr. This allows for searching for attributes that are not easy to search using the default Open Zaak API. The primary use case is to search for zaakeigenschappen (case properties) stored in Open Zaak.

AoZs connects to Alfresco, Open Zaak, and Solr. Open Notificaties also communicates with AoZs to send all updates relevant to zaken (cases).

image: harbor.contezza.nl/contezza/addons/alfresco-openzaak-solr-app:latest
environment:
TZ: Europe/Amsterdam
ALFRESCO_ENDPOINT_URL: "http://alfresco.local:8080/alfresco"
ALFRESCO_AUTH_USERNAME: "admin"
ALFRESCO_AUTH_PASSWORD: "admin"
OPENZAAK_ENDPOINT_URL: "http://openzaak.local:8000"
OPENZAAK_AUTH_CLIENTID: "client-id"
OPENZAAK_AUTH_SECRET: "secret"
SOLR_ENDPOINT_URL: "http://solr:8983/solr"
JAVA_TOOL_OPTIONS: "
-Dserver.port=8080
-Dspring.profiles.active=prod
"

A side discussion about meeting structures and group formations exploring how product vision discussions could be reinitiated. Good information sharing on history and current situation.

### Contezza Alfresco-DRC Open Source status

Didn't get any funding, will probably combine with making Tezza open source.

## May 3 2023

### Attendees

- [x] Jan Ainali, FFPC
- [ ] Joeri Bekker, Maykin Media
- [ ] Anton Boerma, Exxellence
- [x] Eric Herman, FFPC
- [x] Sergei Maertens, Maykin Media
- [x] Tahir Malik, Contezza
- [ ] Rick de Rooij, Contezza
- [ ] Daniel Langeveld, WeAreFrank

### Agenda

- Contezza Alfresco-DRC is made Open Source
- Testing the DRC Component
- Release calendar Open-Zaak

### Contezza Alfresco-DRC is made Open Source

WIP, Some libraries are still in our Private Nexus repository.
We still need to publish the libraries to Maven Central.
Several Municipalities have contacted us for the project/code, and it has been delivered as is.

Planning before the next meetup to have it privately accessible for us to review the repository.

### Testing the DRC Component

We've updated the drc-tas-api in our private GitLab to the latest DRC specs 1.1. Still need to publish the code to GitHub.

### Release Calendar Open-Zaak

The intent is to do a monthly release.
Can be followed in the GitHub new project board: https://github.com/orgs/open-zaak/projects/3/

Here, customers/providers can see what is upcoming.

### APM

Elastic APM has been enabled configurably and can be enabled/disabled with some configs.

### Next release

The next release will be a patch release with a number of performance patches.

### Issue management

General discussion about how to handle issues, specifically to coordinate about needs.

One idea is to direct municipalities to the [mailing list](https://lists.publiccode.net/mailman/postorius/lists/openzaak-discuss.lists.publiccode.net/) to discuss and possibly coordinate future development.

Maybe set up an Odoo form, using the Foundation for Public Code Odoo instance, for the top 10 features where Municipalities can vote and allocate budget to implement these features.

### Indexing OpenZaak with SOLR

We're sticking with SOLR because it's fully Open Source.
Project is WIP and working locally, but we haven't fully implemented in Tezza so can't deliver it.

For the time being we'll use gitlab, for the project intill it's solid to share and move to Open-zaak.

### VNG tests have changed

It is being worked on.

----

## Jan 11 2023

### Attendees

- [x] Jan Ainali, FFPC
- [ ] Joeri Bekker, Maykin Media
- [x] Anton Boerma, Exxellence
- [x] Eric Herman, FFPC
- [x] Sergei Maertens, Maykin Media
- [x] Tahir Malik, Contezza
- [x] Rick de Rooij, Contezza
- [ ] Daniel Langeveld, WeAreFrank

### Agenda

### Releasing Contezza Alfresco-DRC in the OpenZaak org

At this moment the DRC isn't vendor neutral. We'll push it first towards the Contezza repository and after it's been approved we'll push it(github ui) to the Open-Zaak repository.

### [Helm-charts](https://github.com/open-zaak/charts)
Contezza will do review of the pull-requests for the time being.
Contezza will only fix bugs and feature requests when the customer/partners pais for the effort put in.

There should be a readme update which clarifies what is and how is it being a maintained.

### [Ansible collection](https://github.com/open-zaak/ansible-collection)

Can this repository be archived?
No objections were made.

### Release 1.8.0

Released last Monday! [Changelog](https://open-zaak.readthedocs.io/en/stable/development/changelog.html#id1).

### VNG is picking up updates of the API

Information sharing.

### Open-Zaak index

Contezza has started on creating their own Index server on Open Zaak with SOLR on design level.
If there are pointers on this these can be shared within slack.
Sergei pointed out to make a generic model which can be changed for each implementation.

### Action points from previous meeting

### Next meeting

----

## Sep. 7th 2022

We meet in https://meet.community.publiccode.net/OpenZaakTechnicalSteeringGroup as usual

### Attendees

- [x] Jan Ainali, FFPC
- [x] Joeri Bekker, Maykin Media
- [ ] Anton Boerma, Exxellence (was excused)
- [x] Eric Herman, FFPC (joined late)
- [x] Sergei Maertens, Maykin Media
- [x] Tahir Malik, Contezza
- [ ] Alba Roza, FFPC (not with FFPC any longer)
- [x] Rick de Rooij, Contezza
- [x] Daniel Langeveld, WeAreFrank

### Agenda

* Contezza Alfresco-DRC is made Open Source, there are some things we need to agree on (feature request is made)
* To Test the DRC Component we’ve made a Unit test, the DRC specs has been changed for 1.1 and there is no clear communication line what needs to be changed etc.
* Make a recurring Session 😊, I’ve made the following recurring every 4 months  let’s discuss if this is too much/less
* https://github.com/VNG-Realisatie/gemma-zaken/issues/2081 How do we deal with such an issue?
* Maintainers Open-Zaak Repositories, how do we manage these. Contezza like to be part of the charts repository
* Info about the upcoming v1.8 release

## Contezza Alfresco-DRC is made Open Source, there are some things we need to agree on (feature request is made)

* Publish image to hub.docker.com
* Will need to get a token for a seperate repository
* Publish source code on github
* For the first part we'll create a readme within a link to our gitlab repository which will be publically --> Temporary max 3 months, to give time to move the code to Github with the proper docs, tests and links to related tools.
* Publish modules to Maven central
* Wil need to share the credentials with public-code
* Documentation needs to be up-to-date
* NON-functional, like the contact information
* Security issues
* Github issues --> Contezza gives commitment for maintaining
* Peer-Review should be done on any sub-repository
* Licensing EUPL 1.2
* [The assessment for OpenZaak](https://github.com/open-zaak/open-zaak/blob/main/docs/introduction/open-source/public_code.md) - [empty template](https://about.publiccode.net/activities/codebase-auditing/review-template.html)

## Helm-charts

* Any-one from the technical Steering team can be come maintainer as long we do a peer-review
* for the time being Tahir & Sergei kan peer-review each others pull requests

## Unit test DRC project

* Contezza will need to follow the github project of VNG-Realisatie

## Action points from previous meeting

## Next meeting

Make it recurring?