Attending:
- Anton Boerma, exxellence.nl
- Eric Herman, publiccode.net
- Jan Ainali, publiccode.net
- Joeri Bekker, maykinmedia.nl
- Sergei Maertens, maykinmedia.nl
- Tahir Malik, contezza.nl
- Tjerk Vaags, contezza.nl
Anton tried to join but had technical troubles.
Agenda items
- Discuss the goal of this group
- GOVERNANCE.md
<https://github.com/open-zaak/open-zaak/blob/master/GOVERNANCE.md>
- Technical Roadmap
- Engineering Guidelines
- Maintenance and support
- Known technical items
- Financial considerations
- Next meeting
- Select chair
- Date/time
NotesDiscuss the goal of this group
Eric gave an introduction about why this group has been called together.
Discussion about the governance file and the wording in it. We found a few
places where the wording was ambiguous and not really easy to understand.
- One example was the first bullet point list which was meant to
describe activities handled everyday by the team members rather than tasks
for the team to solve during the technical steering meetings. To solve it,
we could move the responsibilities list above the list of member
attributes/activities.
- We could separate out code-of-conduct violations, as that may not be a
great indicator to technical seniority.
Sergei shared a really nice draft for a roadmap
<https://github.com/open-zaak/open-zaak/pull/720>. Eric suggested to add
some sense of cost and impact, Joeri agreed it would be good.
Maintenance and support
Q: Where does the prioritization set? It seems to not really be in either
the product or technical teams.
A: Probably by the people having the budget, being informed by senior
technical people they trust.
Q: How do we handle maintenance and bugs (which is quite different from
feature requests)?
3 types of issues:
- Bugs that are just reported, without any budget/code contribution
- Bugs that are resolved with budget or code contributions
- Features/Wishes from a municipality
We discussed if it would make sense to compile a list of longstanding bugs
(that are not feature requests) and present to the either the product
steering team or Dimpact and start the conversation about organizing
procurements including SLAs and on-going support.
Any other business
Q: Which channels are we using for communicating?
A: In addition to the github repository, the mailing list is the main
communication channel, news, invites and notes will be sent there. But for
convenience invites will also be sent directly as meetings. The HackMDs are
only meant for collaborative note taking and not for archival purposes. The
Slack channel is for quick synchronous communication.
Next meeting
Eric will reach out to Anton, who missed the meeting today.
Next meeting: likely 21 October 14.00 just ahead of the product steering
group meeting, Sergei will send invites for it.
--
Eric Herman, Lead codebase steward for quality
Foundation for Public Code | https://publiccode.netgithub.com/publiccodenet | github.com/ericherman
eric(a)publiccode.net | +31 620719662 | @Eric_Herman
Hello everyone!
Here are the notes from the first Product steering meeting.
OpenZaak Product Steering Meeting - 22 September 2020, 10:00 to 11:00
Meeting link: https://meet.publiccode.net/OpenZaakProductSteering
Mailinglist:
https://lists.publiccode.net/mailman/postorius/lists/openzaak-discuss.lis...
Slack Channel: https://samenorganiseren.slack.com/archives/CT6UH711Q
<https://hackmd.io/TuT0Icv0R42W-Nr4L1hHLw#Attending>Attending
- Felix Faasen, Foundation for Public Code
- Jan Ainali, Foundation for Public Code
- Joeri Bekker, Maykin Media
- Niels Lindeboom, Dimpact
- Hugo ter Doest, Dimpact
- Silvion Moesan, OPEN.satisfaction
- Olav Allema, Contezza
- Lazo Bozarov, Utrecht
- Tahir Malik, Contezza
- Jolanda
- Peter, Exxcellence
<https://hackmd.io/TuT0Icv0R42W-Nr4L1hHLw#Agenda>Agenda
1. Introduction round
2. Decide on the responsibilities / composition of the product steering
team. Finalize the GOVERNANCE file
<https://github.com/open-zaak/open-zaak/blob/master/GOVERNANCE.md> (that’s
in draft right now),
3. Update of APIs for customers, so that OpenZaak follows the ZGW API
standard as closely as possible
4. Content and theme of the website
<https://hackmd.io/TuT0Icv0R42W-Nr4L1hHLw#Introduction-round>Introduction
round
After the introduction round the input of Joeri and Silvion was
highlighted. A number of these topics will be touched upon in our
discussion topic about reponsibilities / composition of the product
steering team. The proposed agenda item concerning the mission/vision/goal
and strategy around OpenZaak product is being drafted by Hugo and discussed
for review in our next meeting.
Additional proposed agenda items by Joeri and Silvion:
<https://hackmd.io/TuT0Icv0R42W-Nr4L1hHLw#Proposed-by-Joeri>Proposed by
Joeri:
- Richtlijnen opstellen voor deelname aan stuurgroepen (zijn er bepaalde
eisen voor deelname en/of zitten er verplichtingen aan?)
- Expliciete rollen benoemen (PO, website maintainer, meeting organizers)
- Exposure (zijn er nog -marketing- events waar we Open Zaak willen
tonen?)
- Indien toepasselijk: Financiering voor product development (wat is de
beste manier om ongoing financiering te regelen voor ontwikkeling, het doen
van bugfixes?)
<https://hackmd.io/TuT0Icv0R42W-Nr4L1hHLw#Proposed-by-Silvion>Proposed by
Silvion:
- Mission/vision/doelen/strategie om zo te kunnen focussen waar we
willen staan met OpenZaak en waar we dus ook nee (iig nu niet) op kunnen
zeggen met een gegronde onderbouwing
- Bespreekmomenten / structuur product steering group overleg
- Hoe gaan we gemeenten (klanten) aanhaken bij de product steering group
<https://hackmd.io/TuT0Icv0R42W-Nr4L1hHLw#Decide-on-the-responsibilities--...>Decide
on the responsibilities / composition of the product steering team.
The group discussed numerous topics concerning the responsibilities,
composition and scope of the OpenZaak product steering group.
The group discussion involved questions about; people vs. organizations,
type of organizations in the team (vendors vs. municipalities), roles in
the team, and selection criteria.
Also the optimal group size was discussed; typically between 3 and 9 people
and/or organizations was deemed as a good size.
Should it be organizations or persons that are part of the group? Both
cases were made. An important point that was generally agreed upon was that
the people coming to meetings should be invested. They are there to do work
and take care about OpenZaak, not to make bureaucracy tick.
Everyone in the group agreed the minimal requirement should be that a team
member should at least use OpenZaak in some shape or form (use, buy, sell,
develop). Other requirements discussed (not decided) included:
- Vendors contribute development time
- Vendors contribute skills
- Vendors use/integrate OpenZaak
- Municipality invests in OpenZaak
- Is active in community (tickets) or do work that benefits OpenZaak
- Attend at least X% of the meetings
Lazo mentioned that members are not there to represent their own interest
but the health and interest of the OpenZaak ecosystem as whole. There were
no opposing views expressed on that.
We did not decide yet on the composition of the team but Peter and Joeri
volunteered to capture thoughts of the group discussions and other ideas
into the draft GOVERNANCE.MD <http://governance.md/> file in the OpenZaak
repository. They will make a pull request for it so we can review this in
our next product steering meeting.
<https://hackmd.io/TuT0Icv0R42W-Nr4L1hHLw#Update-of-APIs-for-customers-so-...>Update
of APIs for customers, so that OpenZaak follows the ZGW API standard as
closely as possible
Agenda point proposed by Hugo about how to stay up-to-date / in sync with
the ZWG-API’s which is evolving. A discussion around the scope of the
OpenZaak product steering team started, weighing components vs. ecosystem.
What is part of case oriented working and what isn’t and what should be in
scope?
Part of this discussion will also be touched upon in the drafting of the
product mission, vision and goals and need further discussion.
<https://hackmd.io/TuT0Icv0R42W-Nr4L1hHLw#Todo%E2%80%99s>To Do's
ActionResponsibleDue date
Ask steering group for representatives in Product Group, post in the
CommonGround Niels, Joeri October 21st, 2020
Create draft pull request on GOVERNANCE.MD <http://governance.md/>
members Peter
& Joeri October 21st, 2020
Create Mission & Vision Draft on OpenZaak product Hugo October 21st, 2020
<https://hackmd.io/TuT0Icv0R42W-Nr4L1hHLw#Agenda-for-next-meeting>Agenda
for next meeting
Suggested to have rotating chair, Joeri takes next chair on Oct 21, 2020
15.00
- Review & discuss pull request on draft GOVERNANCE.MD
<http://governance.md/> file
- Review & discuss product mission/vision and goals
- PROPOSED: Feedback website?
- PROPOSED: Any other points?
Best,
Jan Ainali, Codebase Steward
jan(a)publiccode.net | +46762122776 | @jan_ainali
Foundation for Public Code https://publiccode.net
This is the notes from the OpenZaak Community call 9 September.
<https://hackmd.io/ardKOwfyR_KhPUZPZGkBUQ?both#Attending>Attending
- Jan Ainali, Foundation for Public Code.
- Felix Faasen, Foundation for Public Code.
- Alba Roza, Foundation for Public Code.
- Eric Herman, Foundation for Public Code.
- Gelmer van den Noort, Sales Consultant at exxellence.nl
- Joeri Bekker,- Maykin Media
- Silvion Moesan, Open Satisfaction
- Sergei Maertens, Maykin Media
- Hugo-ter-Doest - Dimpact + VNG
- Niels Lindeboom - Dimpact
<https://hackmd.io/ardKOwfyR_KhPUZPZGkBUQ?both#Agenda>Agenda
- Brief introduction round
- Technical steering team: composition
- Define agenda items for the first meeting technical steering team
- Product steering team: composition
- Define agenda items for the first meeting product steering team
- OpenZaak Website presentation and demo! Next steps
<https://hackmd.io/ardKOwfyR_KhPUZPZGkBUQ?both#Technical-Steering-Team>Technical
Steering Team
- Schedule: Monthly meeting.
- First one: 23 September, 14:00.
- Interested in becoming members:
- Joeri
- Sergei
- Eric (coaching/observing)
- Agenda points for the first meeting:
- Joeri suggests: Keep the maintenance and support going. Also the
financial aspect.
<https://hackmd.io/ardKOwfyR_KhPUZPZGkBUQ?both#Product-Steering-Team>Product
Steering Team
- Schedule: Monthly meeting, preferably just after the technical
steering team meeting.
- First one: 22 September, 10.00.
- Interested in becoming members:
- Hugo
- Gelmer
- Silvion
- Joeri
- Felix (coaching/observing)
- MUNICIPALITIES. Hugo wants at least:
- Utrecht
- Zuid-West Friesland
- Agenda points for the first meeting:
- Decide on the responsibilities of each of the teams. Finalize the
GOVERNANCE file (that’s in draft right now),
- Update of APIs for customers, so that OpenZaak follows the ZGW API
standard as closely as possible
- Content and theme of the website
<https://hackmd.io/ardKOwfyR_KhPUZPZGkBUQ?both#Website-Openzaakorg>Website
Openzaak.org <http://openzaak.org/>
Felix presented the first website for OpenZaak. It is a start and a
proposal to the community and it is not finished. He also talked a bit
about the new signalen.org website and we could use the website for
OpenZaak. He also presented a few technical details which might limit
content contribution/edits but proposed to have a look at it with the
community and decide how to move forward. Discussing the website content
and layout will be an agenda point for the first product steering meeting.
<https://hackmd.io/ardKOwfyR_KhPUZPZGkBUQ?both#Action-Points>Action Points
ActionResponsibleDue date
Plan in recurring product and technical steering meeting and communiticate
on mailing list Jan + Felix 10-9-2020
Involve more municipalities and vendors in technical steering group Gelmer
asks colleague, Hugo+Niels
Involve more municipalities in product steering group Niels & Hugo
Feedback on the website
--
Jan Ainali, Codebase Steward
jan(a)publiccode.net | +46762122776 | @jan_ainali
Foundation for Public Code https://publiccode.net
From the changelog
<https://github.com/open-zaak/open-zaak/blob/master/CHANGELOG.rst>:
Changes
- Updated CMIS-adapter to 1.1 featuring support CMIS 1.0 Webservice
binding and various new configuration options.
- Added support for configurable Selectielijst years to retrieve
specific years from the Selectielijst API (#689)
- Prevent error monitoring from logging special personal data (#696)
Bugfixes
- Accept comma separated in EigenschapSpecificatie.waardenverzameling
(#686)
Documentation
- Added SPDX license headers and check.
- Added Docker storage hint to make sure users run the Docker containers
on volumes with enough disk space.
--
Jan Ainali, Codebase Steward
jan(a)publiccode.net | +46762122776 | @jan_ainali
Foundation for Public Code https://publiccode.net
Hello!
The date and time for the first community call for OpenZaak has been
announced - September 9, 2020, 14.00-15.00 CEST.
*Agenda*
* Brief introduction round
* Technical steering team: agree on new members
* If you would like to join, please make a pull request to add yourself
* Define agenda items for the first meeting technical steering team
* Product steering team: agree on new members
* If you would like to join, please email [niels.lindeboom(a)dimpact.nl]
* Define agenda items for the first meeting product steering team
* OpenZaak Website launch and demo! and feedback
Video Link: https://meet.publiccode.net/CommunityCallOpenZaak
See you in September!
--
Jan Ainali, Codebase Steward
jan(a)publiccode.net | +46762122776 | @jan_ainali
Foundation for Public Code https://publiccode.net
