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-voo...>
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.netgithub.com/publiccodenet | github.com/felixfaassen
felix(a)publiccode.net | +31 624633278
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-...>,
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
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>.
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!
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-f6872aba...
[1]
https://lists.publiccode.net/hyperkitty/hyperkitty/list/openzaak-discuss@...
--
Jan Ainali, Codebase Steward
jan(a)publiccode.net | +46762122776 | @jan_ainali
Foundation for Public Code https://publiccode.net
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-f6872aba8...
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
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=produ...
-
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.netgithub.com/publiccodenet | github.com/felixfaassen
felix(a)publiccode.net | +31 624633278
