openzaak-discuss April 2021

openzaak-discuss@lists.publiccode.net

2 participants
3 discussions

Open Zaak 1.4.0 released
by Sergei Maertens 03 May '21

03 May '21

Hi everyone, Open Zaak 1.4.0 is released today. This is combined feature- and bugfix release. The new features are mostly focused on cloud integration, such as fully automated provisioning of the initial admin user during installation and integration with Azure AD for SSO. We also continue to improve the CMIS-adapter performance. As always, the full release notes are available on the documentation website <https://open-zaak.readthedocs.io/en/stable/development/changelog.html#id1> and images are published to Docker Hub <https://hub.docker.com/r/openzaak/open-zaak>.

2 1

Technical Steering Group meeting April 14th 2021
by Sergei Maertens 29 Apr '21

29 Apr '21

Hi all, Apologies for the late summary of the latest TSG meeting, it's been quite busy! This is the report of the topics that were discussed in the last technical steering group meeting. Attendees - Jan Ainali - Joeri Bekker (later) - Anton Boerma - Eric Herman (excused) - Sergei Maertens - Tahir Malik - Alba Roza (excused) - Tjerk Vaags (excused) <https://hackmd.io/67m-C--GSG-03a82y7ce_Q#Agenda>Agenda - Intro - Open Zaak & Alfresco model packaging ( https://github.com/open-zaak/open-zaak/pull/933) - Zaken API 1.0.3 changes processed - Clean up & dropped dependencies - Docs versions configuration - Helm chart repository ( https://github.com/open-zaak/open-zaak/issues/923) - Other - Next meeting & chair <https://hackmd.io/67m-C--GSG-03a82y7ce_Q#Open-Zaak-amp-Alfresco-model-packa…>Open Zaak & Alfresco model packaging Issue: https://github.com/open-zaak/open-zaak/issues/931 Decisions needed: https://github.com/open-zaak/open-zaak/issues/931#issuecomment-819281443 PR: https://github.com/open-zaak/open-zaak/pull/933 Outcome: 1. Create repo for test image to be used by OZ CI/CD 2. Question 2 & 3: not relevant, OZ does not concern itself with (production) Alfresco, this is up to the service providers. Anton will review <https://hackmd.io/67m-C--GSG-03a82y7ce_Q#Zaken-API-103-changes-processed>Zaken API 1.0.3 changes processed Planned for 1.4.0 release, changelog entries: https://github.com/open-zaak/open-zaak/blob/main/CHANGELOG.rst#140-2021-03- <https://hackmd.io/67m-C--GSG-03a82y7ce_Q#Clean-up-amp-dropped-dependencies>Clean up & dropped dependencies Some NLX specific things were changed in 1.2.0 - these dependencies have now been dropped. If you’re upgrading from Open Zaak < 1.2.0, you need to upgrade in two steps. Only relevant if: - use NLX - currently on Open Zaak < 1.2.0 Documentation clear enough? Agreed by everyone. <https://hackmd.io/67m-C--GSG-03a82y7ce_Q#Docs-versions-configuration>Docs versions configuration https://readthedocs.org/projects/open-zaak/ -> I can’t edit the Open Zaak settings in the RTD UI. Joeri: map latest to main instead of master, or add maintainers? -> Joeri adds Sergei as maintainer & changed to main <https://hackmd.io/67m-C--GSG-03a82y7ce_Q#Helm-chart-repository>Helm chart repository Issue: https://github.com/open-zaak/open-zaak/issues/923 Example: https://artifacthub.io/packages/helm/open-zaak/open-zaak Looks good, some tweaking required (dependency versions, application version…) Works by: - github is source of truth - github actions publish to https://open-zaak.github.io/charts/ - artifacthub syncs with github <https://hackmd.io/67m-C--GSG-03a82y7ce_Q#Other>Other - Travis CI finally replied to the OSS credits, we will not use these and stick with Github Actions. - Sergei mentions the absence of Tahir in steering group meetings and asks the Foundation to contact Tahir about the membership. - Jan remarks the GOVERNANCE file is still in a draft format -> not much to enforce yet because it’s in draft. It’s still in draft because of PSG (TSG was essentially ok with publishing). Draft status hinders effectiveness. <https://hackmd.io/67m-C--GSG-03a82y7ce_Q#Next-chair-and-meeting>Next chair and meeting Joeri, May 12th

1 0

Re: Open Zaak Product Steering Team Meeting
by Felix Faassen 21 Apr '21

21 Apr '21

Beste Edwin, Je kunt zelf een meeting aanmaken door een kopie te maken van de voorgaande meeting in je agenda. In die uitnodiging staan ook alle email adressen en in de beschrijving staan ook alle links incl. meeting link. Misschien dat iemand ander op de mailinglist je even zou willen helpen hiermee? Mocht het niet lukken of onduidelijk zijn laat het me even weten.Mocht je nog niet op de mailinglist staan schrijf je dan zeker even in op : https://lists.publiccode.net/mailman/postorius/lists/openzaak-discuss.lists… Ik zal je de oude uitnodiging van 7 april nog even opsturen. Groeten, Felix On Wed, Apr 21, 2021 at 9:00 AM Edwin Coster <ecoster(a)delft.nl> wrote: > Hoi Felix, > > > > Ik wil graag de volgende Open Zaak PST meeting organiseren. > > > > Hoe regel ik dat? > > > > Groet, > > > > *Edwin Coster* > *Applicatiearchitect* > *Gemeente Delft* > *Interne Dienstverlening - Informatietechnologie* > =========================== > (: +31 (0)6 52739421 > *: ecoster(a)delft.nl > =========================== > > > Aan dit e-mailbericht kunnen geen rechten worden ontleend. Dit bericht is > uitsluitend bestemd voor de geadresseerde(n). De Gemeente Delft staat niet > in voor de juiste en volledige overbrenging van de inhoud van een verzonden > e-mail, noch voor de tijdige ontvangst ervan. > -- 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

2024

2023

2022

2021

2020

openzaak-discuss April 2021