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

Codecov security update: Open Zaak is not affected
by Sergei Maertens 10 May '21

10 May '21

Recently there was a security incident at a third party (Codecov) used in the development of Open Zaak. Open Zaak was not affected by this. We've summarized the analysis that we performed and the steps taken on the website <https://openzaak.org/en/news/2021-04-16-codecov-security-update/>.

1 0

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

Conference call to discuss ideas and help organize a OpenZaak community day
by Felix Faassen 31 Mar '21

31 Mar '21

Dear OpenZaak community members, It has been almost a year since the OpenZaak community met with each other. Thus, we think this is a great moment to organize a community day for the OpenZaak community. We would like to invite you to join a conference call to discuss ideas and help organize a OpenZaak community day. This conference call will be open for anyone interested in participating in the discussion and is planned on Tuesday 13th of April at 11:00. You can access the meeting through this link: meet.publiccode.net/OpenZaakCommunityDay *Additional background information* As you may have read in the VNG member letter <https://vng.nl/brieven/standaardverklaring-per-142021-api-standaarden-voor-…> sent on the 4th of March (reference: Lbr. 21/016) the board of VNG decided to declare "Zaak Gericht Werken (ZGW-API) as a standard way of working for all municipalities starting the 1st of April 2021. In 2022 using this standard will become mandatory. This will mean more municipalities starting to investigate using OpenZaak and probably procure more services related to OpenZaak. We as a community could use this opportunity to learn how to facilitate and support this development. Last week we had a successful Signalen community day. One goal of the day was to see how the community could work together to get Signalen used in more municipalities. During the day municipalities shared their experiences in using and implementing Signalen. It also provided an opportunity for municipalities not yet using Signalen to get a personalized demo environment and get to know the community behind Signalen. This proved to be an interesting format in which we got to know both the stories of those who are currently using Signalen and those who are interested in joining its community. We could use this as an inspiration or starting point for organizing our own OpenZaak community meetup. So please mark you calendars and we hope to see you on our call Tuesday the 13th at 11:00. Kind regards, Alba, Eric, Jan and Felix Codebase stewards Foundation for Public Code -- 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

News section on openzaak.org is open for contributions
by Jan Ainali 31 Mar '21

31 Mar '21

Hello everyone, If you haven't noticed yet, there is a new section on openzaak.org for news <https://openzaak.org/news/>. As you can see there are already a few posts in there, and we like to invite you all to think about news worth sharing in it. If you think something would fit you could either just create a pull request with the news following the instructions in the readme <https://github.com/open-zaak/open-zaak-website#how-to-add-a-news-article-to…>, or you could create an issue <https://github.com/open-zaak/open-zaak-website/issues/new/choose> with the information you would like to see shared, and we can work collaboratively to share it with the world. This resource is open for the entire community to share news and highlights that could be interesting for anyone that would like to learn about OpenZaak. -- Jan Ainali, Codebase Steward jan(a)publiccode.net | +46762122776 | @jan_ainali Foundation for Public Code https://publiccode.net

1 0

Open Zaak 1.3.5 and Open Notificaties 1.1.4 released
by Sergei Maertens 25 Mar '21

25 Mar '21

Hi folks, Open Zaak 1.3.5 and Open Notificaties 1.1.4 are both another quality of life release, fixing a number of bugs, improving performance and adding support for environments that wasn't (fully) there yet. Other than the bugs, notable is the support for podman <https://podman.io/> as an alternative to the docker runtime - relevant for RHEL-based systems for example. This was initiated by Gemeente Haarlem. Next to that, we now also support consuming services secured by self-signed certificates, without compromising security on public domains. As always, the full release notes are available on the documentation websites: - Open Zaak <https://open-zaak.readthedocs.io/en/stable/development/changelog.html#id1> - Open Notificaties <https://open-notificaties.readthedocs.io/en/stable/changelog.html#id1> The container images are also still available on Docker hub <https://hub.docker.com/u/openzaak>.

1 0

Default branch renamed [target: developers]
by Sergei Maertens 22 Mar '21

22 Mar '21

Hi all, Following a global example of using more accessible nomenclature, the default branches for Open Zaak and Open Notificaties have been renamed from "master" to "main" on Github. Developers contributing to Open Zaak can update their local environments using: git branch -m master main git fetch origin git branch -u origin/main main Thanks for your attention!

1 0

Release Early Notice List
by Jan Ainali 22 Mar '21

22 Mar '21

Hello, Following up on the last technical steering meeting [1], I'd like to point out that you can now sign up to a release early notice mailing list. This will give you notifications of upcoming releases before they are published. You may want these because for some releases system administrators need time to schedule an update, which can be especially important if a security vulnerability was resolved in the update. Sign up at: https://odoo.publiccode.net/survey/start/086e0627-8bc0-4b65-8aa9-f6872aba89… [1] https://lists.publiccode.net/hyperkitty/hyperkitty/list/openzaak-discuss@li… -- Jan Ainali, Codebase Steward jan(a)publiccode.net | +46762122776 | @jan_ainali Foundation for Public Code https://publiccode.net

1 0

Technical Steering Group meeting 17-03-2021
by Sergei Maertens 18 Mar '21

18 Mar '21

Hi everyone, Yesterday's technical steering group meeting was another short one. See below for the notes taken during the meeting. *Attendees*: - Jan Ainali - Joeri Bekker - Anton Boerma - Eric Herman - Sergei Maertens - Tjerk Vaags Alba Roza and Tahir Malik could not attend. *Agenda items* - introduction/agenda items - status update signup vendor list & contact info - release 1.3.5 - planning / release date - any other items brought in - next meeting & chair *Status update signup vendor list & contact info* There is a signup form now where you can leave your contact details: https://odoo.publiccode.net/survey/fill/086e0627-8bc0-4b65-8aa9-f6872aba89d… One bug was spotted - phone number field should not be required. - details provided will be stored on Foundation for Public Code servers. Only FfPC staff have access to the data. - About phone as preferred way of contact: FfPC staff will call these people. If the list gets too large for 1-2 people to handle this in one day, we'll revisit this. If this happens, it's considered a success. - Link to privacy policy is still missing & will be added - Jan asks how we will promote this: - technically include it in the admin-index fixture (together with link to this mailing list). The links will be available on the dashboard for fresh installations (Sergei) - include the link on openzaak.org (Jan) - include the link on commonground.nl in the Open Zaak group (Anton or Tjerk, who will be added as members to this group) - include the link on the documentation website open-zaak.readthedocs.io (Sergei) - include the link on the Open Zaak github readme (Eric) - announce on mailing list (Jan) *Release 1.3.5 - planning / release date* Bugfix release 1.3.5 is scheduled for release on March 25th. We established that we aspire to follow a monthly release cycle (no promises though). Motivation: underlying framework releases bugfixes at the beginning of the month too, and we want to bring fixes to the user asap. *Backlog pruning results* The technical backlog pruning is organized and passed to the product steering group. Joeri and Felix will be in contact if needed to adequately inform the product steering group members. *Next meeting & chair* April 14th, from 2 to 3pm. Sergei will be chair. <https://hackmd.io/6zA_YsgMQx2xLvJNk3jfoQ#> Select a repo

1 0

2024

2023

2022

2021

2020

openzaak-discuss