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

OpenZaak testing and deployment infrastructure

by Eric Herman

Dear OpenZaak community members, We see our role as ["Providing long term product sustainability"]( https://about.publiccode.net/activities/codebase-stewardship/goals#provid...) in codebase stewardship. We should provide this infrastructure to the entire community as that lies outside of the mandate of any individual organization whilst everyone depends on it for their operational continuity. As you know during the last technical steering meeting important issues were raised concerning the existing testing and deployment infrastructure. Due to a change in the business model of the services used, the OpenZaak test and deployment infrastructure will become unavailable if no action is taken. In the short term, we propose to take over responsibility for the existing infrastructure. We can do this by paying for the services. In the mid-to-longer term we strongly recommend a transition to another more open and accessible platform. To achieve a healthy and strong community around OpenZaak, regardless of what's stated above, we request public organizations to become members of the Foundation for Public Code Vereniging. Membership is an investment in the social and technical infrastructures to achieve the goals of OpenZaak and open source in gemeenten. We propose to take over the Travis and DockerHub accounts and are ready to operationalize this as soon as that happens. Please let us know how you think about this and let's discuss how we can move this forward. Kind regards, Eric & Felix -- Eric Herman, Lead codebase steward for quality Foundation for Public Code | https://publiccode.net github.com/publiccodenet | github.com/ericherman eric(a)publiccode.net | +31 620719662 | @Eric_Herman

2 years, 6 months

1
0
0 0

Product steering feature requests and product backlog

by Felix Faassen

Dear all, As discussed in our product steering meeting this week. I opted to propose to manage our feature requests and product backlog in the open on Github. Next product steering meeting I will provide a small demo on how this could work and discuss how to move further. As for now I've created the following so existing feature requests can be added. How does this work: We now have a new issue only repository on Github which you can find here: https://github.com/open-zaak/product-steering .It includes a start of a README which we can use to document our process as we go along. To create a feature request (make sure you have a Github account) you can go here: https://github.com/open-zaak/product-steering/issues/new?assignees=&label... This will open a new issue using a feature request template which is also used in the Signalen project. We can change this template as much as we like. See screenshot below: [image: Screenshot from 2020-11-20 16-55-37.png] At the right you can click on "projects" and choose the OpenZaak Product Backlog. This way the you can later add this feature request on the the product backlog board. After you have filled out the feature request and submitted it you can add it as a card on the product backlog Go to the product backlog board here: https://github.com/orgs/open-zaak/projects/2 You see the screen below: [image: Screenshot from 2020-11-20 16-59-14.png] Click "add cards" and at the right you can see your newly created feature request, drag the card the first column. This way we can collect,store and prioritize our feature requests. As feature requests mature, budget allocated, developers refined it issues can be created by developers linking these features in the appropriate repositories. I will demo this in the upcoming product steering but feel free to start creating feature requests ;-) Enjoy the weekend and talk to you soon. Kind regards, Felix -- Felix Faassen, Codebase steward Foundation for Public Code | https://publiccode.net github.com/publiccodenet | github.com/felixfaassen felix(a)publiccode.net | +31 624633278

2 years, 6 months

1
0
0 0

OpenZaak new website update

by Felix Faassen

Dear all, As discussed during the product steering meeting Alba and I are very busy create a new website which we will demo in the next product steering meeting. If you are curious to follow our work you can check out this outstanding draft pull request: https://github.com/open-zaak/open-zaak-website/pull/39 After the demo we will invite you to provide feedback but feel free to create issues if you have any suggestions or comments. All the work is done in a separate branch 'new-design' (https://github.com/open-zaak/open-zaak-website/tree/new-design). If you checkout that branche you will find instructions in the README on how to get site up and running locally. Enjoy your weekend. Kind regards, Felix -- Felix Faassen, Codebase steward Foundation for Public Code | https://publiccode.net github.com/publiccodenet | github.com/felixfaassen felix(a)publiccode.net | +31 624633278

2 years, 6 months

1
0
0 0

Meeting notities van afgelopen sessie.

by Tahir Malik

Even een copy en past vanuit Hackmd, oorspronkelijke versie staat in link hieronder (beter leesbaar): https://hackmd.io/cyw3Frv7Re-vm3wOLIL3rw OpenZaak Product Steering Meeting - 18 November 2020, 15:00 to 16:00 Meeting link: https://meet.community.publiccode.net/OpenZaakProductSteeringGroup Mailinglist: https://lists.publiccode.net/mailman/postorius/lists/openzaak-discuss.lis... Slack Channel: https://samenorganiseren.slack.com/archives/CT6UH711Q Agenda 1. Agenda 2. Actions from previous meeting 3. Discuss mission, vision and scope 4. Future features and roadmap 5. Evaluate governance/future agenda 6. New or changing members 7. Any other thoughts members want to bring in Notes 1. Agenda 2. Actions from previous meeting Action Responsible Due date 1. Ask steering group for representatives in Product Group, post in the CommonGround Niels, Joeri October 21st, 2020 2. Create draft pull request on GOVERNANCE.MD<http://GOVERNANCE.MD> members Peter & Joeri October 21st, 2020 3. Create Mission & Vision Draft on OpenZaak product Hugo October 21st, 2020 1. Invite Edwin/Rita from Delft for this group 2. See: https://github.com/open-zaak/open-zaak/pull/746/files?short_path=b60c6a9#... * All attendees agreed 3. Review Pull request for Mission & Vision Draft https://github.com/open-zaak/open-zaak/pull/749 4. Budget 5. Should we communicate back to the core group 6. What should we do with the roadmap items? 3. Discuss mission, vision and scope Pull Request is ready. Everyone can make their suggestions on this PR. See: https://github.com/open-zaak/open-zaak/pull/749 From the technical steering team: * Post-installation configuration * i-Navigator (and others) support * Better Catalogus management interface * Improve archiving parameters integration * Implement password reset functionality * Provide selectielijst on NLX * Update the API versions * Add klantinteractie APIs (or not) * Bring to core municipality group and get feedback * Allow for "lokale verorderingen" (to the standard) * Fully implement Opschorten functionality * Implement a Search engine (Elasticsearch/SOLR) * Bring to core municipality group and get feedback Additions from the product steering team: * No additonal items provided Suggestion to decide on priority: https://www.scaledagileframework.com/wsjf/ What should we do with this list? 5. Budget Kerngroep decided there will be no general funding for development for Open Zaak Parties should sign SLA for Open Zaak and that is the place to get the funding. Joeri suggested is to reserve a percentage within in de SLA to do general bug-fixing. Gemeente Buren has such a SLA just for bug-fixes. Issues related to general funding: https://github.com/open-zaak/open-zaak/issues?q=is%3Aopen+is%3Aissue+labe... 6. New or changing members * Added Anita Potters, Equalit - a.potters(a)equalit.nl<mailto:a.potters@equalit.nl> * Added Holger Peters, Buren - hpeters(a)buren.nl<mailto:hpeters@buren.nl> 7. Any other thoughts members want to bring in * Next meeting: December 16, 2020 * For next agenda: * See actions * Tahir Silvion will chair the next meeting * Meetings will be in Dutch, but notes will stay in english * Whenever actions are done, just send an email to the mailinglist openzaak-discuss(a)lists.publiccode.net<mailto:openzaak-discuss@lists.publiccode.net> so everyone can review them hopefully before the meeting New actions Action Responsible Due date 1. Review Mission & Vision Draft Pull request Everyone December 16, 2020 2. Product management repo maken Felix December 16, 2020 3. Request to have a session with core group Lazo December 16, 2020 4. Demo openzaak.org<http://openzaak.org> Felix/Publiccode December 16, 2020 5. Feature requests describe in the repo made bij point 2. Everyone December 16, 2020 6. Budget issues bekijken op Github, aanbrengen bij Kerngroep Lazo December 16?, 2020 Select a repo Met vriendelijke groet, [cid:image003.png@01D6BE6D.58D3B330] Tahir Shazad Malik email tahir.malik(a)contezza.nl<mailto:tahir.malik@contezza.nl> mobile +31 (0)6 14 77 50 82 office +31 (0)848 68 89 02 website www.contezza.nl<http://www.contezza.nl/> [linkedIn]<https://www.linkedin.com/in/tsmalik/> [Twitter]<http://twitter.com/tahirshazad/> Afwezig: vrijdag

2 years, 6 months

1
0
0 0

Open Zaak technical steering group meeting 2020-11-18 notes

by Sergei Maertens

Attending - Anton Boerma, Exxellence (left around 14:40 for technical reasons) - Eric Herman, Foundation for Public Code - Jan Ainali, Foundation for Public Code - Joeri Bekker, Maykin Media - Sergei Maertens, Maykin Media - Tahir Malik, Contezza (could not attend) - Tjerk Vaags, Contezza <https://hackmd.io/afAA4_-9QNaDJ4nKx1hs6g#Agenda>Agenda - Introduction/agenda items - Support questions on (Common Ground) Slack - (Travis) CI - PR#640 - Helm Support - Questions about importing catalogi - Next meeting & chair <https://hackmd.io/afAA4_-9QNaDJ4nKx1hs6g#Notes>Notes <https://hackmd.io/afAA4_-9QNaDJ4nKx1hs6g#Support-questions-on-Slack>Support questions on Slack The Slack channel is here <https://samenorganiseren.slack.com/archives/CT6UH711Q>. The Slack channel is used, almost on a daily basis questions are asked, often technical in nature. Currently, it looks like only 1-2 community members actively handle questions. This takes about 15-30 minutes per question, often with looking up something in the docs/codebase. The annoying thing is that it happens in-between other things unrelated to Open Zaak - stealing valuable mind-space. This is something that should be distributed more by community members. Tjerk has experience being a consultant and handling initial questions, and forwaring them to development (team) if needed. Eric remarks that we must make it clear how much time a person invests into this, so that it can be invoiced by the organization. Joeri indicated to municipalities that this costs time (and money), they reply “we should do something about it” but nothing really happens (yet). Suggestion (from Joeri): municipalities make it part of the procurement that suppliers/vendors allocate time to support of Open Zaak itself. Anton states that this is exactly what they are planning. <https://hackmd.io/afAA4_-9QNaDJ4nKx1hs6g#Travis-CI>(Travis) CI To continue CI something needs to change. - .org -> .com migration, need to apply for open-source credits for free builds - CI pipeline relies on Travis for PRs, quality control and publishing of Docker images - moving to Github actions? Buying a subscription? - Eric mentions experience with hosting gitlab runners - Travis commercial package is around EUR 3.000 per year - time sensitive - 31 Dec. is deadline - Joeri will mention this in the product steering group - Sergei will be contacting Travis about Open Source build & keep Eric in the loop - Foundation for Public Code might help - Anton suggest buying 2-3 months of paid subscription to ease the transition <https://hackmd.io/afAA4_-9QNaDJ4nKx1hs6g#PR640---Helm-Support>PR#640 - Helm Support See: https://github.com/open-zaak/open-zaak/pull/640 Follow-up from previous meeting, where the staleness of this PR was discussed. Anton will be acquiring Helm knowledge in the near future, this introduces possibility for support from within the community. PR will stay open but marked as won’t merge, plan is to take the input from the contribution and publish it as a helm chart on a public repository and include installation instructions in the documentation. Thereby not merging the chart/templates into the Open Zaak codebase directly. We will make a note in the PR thread about this. <https://hackmd.io/afAA4_-9QNaDJ4nKx1hs6g#Questions-about-importing-catalogi>Questions about importing catalogi Tjerk: Customers have test/production environments. When transferring from test to production, catalogus name changes for example. All objects are unpublished on import -> user has to publish them after import. Question is more suited for github issue, but we have time :-) Comments Joeri: - both things are intentional - export is based on API standard -> exports in format of API (no catalogus name in standard) - publishing: also intentional - after you import you might want to adjust things => easy solution: bulk publish action (create Github issue) - Eric mentions: example export that could be a RFC on how the standard could/should be changed (adding name to catalogus resource) - different flavours of export are also an option <https://hackmd.io/afAA4_-9QNaDJ4nKx1hs6g#testopenzaaknl-domain> test.openzaak.nl domain Runs a test environment, on Kubernetes. Used for testing deployment amongst others. Maykin has been paying that this year. Question: is there any need for this? MiniKube (or others?) may be a viable option for local testing/development, so the cluster will be shut down (and test.openzaak.nl will cease to exist). Important! -> affects selectielijst.openzaak.nl, this needs to be migrated and be paid for -> this is the default selectielijst service and is *required* for good operation of Open Zaak <https://hackmd.io/afAA4_-9QNaDJ4nKx1hs6g#Docker-Hub>Docker Hub Docker is introducing limits for pulls (200 per 6 hours) and starts to delete stale (= no pulls in a while) images. This means at some point, you can not pull Open Zaak from Docker, and that Open Zaak 1.0.0 (ie. not the latest version) at some point might disappear. Joeri will create a Github issue for this. <https://hackmd.io/afAA4_-9QNaDJ4nKx1hs6g#Next-meeting-amp-chair>Next meeting & chair December 16th, Wed. 2pm-3pm Chair: Tjerk Vaags, will collect agenda points and send invites

2 years, 6 months

1
0
0 0

Help needed: new iteration of website content!

by Alba Roza

Good evening everyone, Felix and I are working on a new iteration of the OpenZaak website with a more mature UX. In order to achieve this goal we are planning to use the [Signalen website](signalen.org) as an inspiration. Besides its features, the core of the Signalen website is its vibrant community. Likewise, OpenZaak isn't far behind and can boast its community too, composed of vendors, municipalities, project managers, developers... That's why we need your help with some of our following actions: 1. We are going to create a **video** documentary like [this one]( https://www.youtube.com/watch?v=AdBNyYwbf8A) with short inputs from the OpenZaak community. Please, let me know when a short **interview would work best for you**! Also, if you have some footage that we could use in between interviews (people in streets, an event, a construction work, a road, etc.). 2. There's going to be a "**community banner**" in the main page with the logos of the community. Please, send me your organization's logo in vector format. 3. OpenZaak **integrations**. We'd like to highlight some of the top features of OpenZaak and we think one attractive factor for replicators would be a list of existing integrations with OpenZaak that are already out there: Alfresco, Contezza DMS, etc. Can you think of any more? You can send me your questions and hopefully answers to: alba(a)publiccode.net Thanks! -- Alba Roza | Codebase Steward for Communities alba(a)publiccode.net | @alba_roza Foundation for Public Code | https://publiccode.net

2 years, 6 months

1
0
0 0

Open Zaak 1.3.2 and Open Notificaties 1.1.1 released!

by Sergei Maertens

Both Open Zaak and Open Notificaties have received a bugfix release today. The Open Zaak release includes a number of security updates, bug fixes and documentation updates. Note that it potentially requires manually interventions, see the release notes <https://open-zaak.readthedocs.io/en/stable/development/changelog.html>. Notable is the bug fixes applied to the CMIS-adapter, improving compatibility with various DMS implementations. Open Zaak is actively tested against Alfresco and Corsa. The Open Notificaties release adds some small deployment improvements and includes some documentation fixes, as well as updates to development tooling. Both Open Zaak and Open Notificaties are available on Docker Hub <https://hub.docker.com/u/openzaak>. Any (new) issues found can be reported on Github <https://github.com/open-zaak/open-zaak>, of course.

2 years, 6 months

1
0
0 0

Reply mail adress

by Rick Spierings

Rick Spierings Projectleider [ODNHN BP voorblad headerlogo vDEF] ............................................................................................. Omgevingsdienst Noord-Holland Noord (OD NHN) T 06 14863440 E rspierings@odnhn<mailto:edekok@odnhn.nl>.nl W www.odnhn.nl<http://www.odnhn.nl/> .......................................................................................... =================================================================================================================== Disclaimer OD NHN: Deze informatie is uitsluitend bestemd voor de geadresseerde(n) en mag niet worden gedeeld zonder toestemming van de zender. Als dit bericht verkeerd verzonden is, wilt u dan de zender daarover informeren? Doorsturen, openbaar maken, vermenigvuldigen of anderszins verstrekking van deze informatie aan derden is alleen met toestemming van de zender toegestaan. ===================================================================================================================

2 years, 6 months

1
0
0 0

FW: Open Zaak Product Steering Group

by Tahir Malik

Hoi Allen, Blijkbaar is er de vraag om nu 3 personen uit te nodigen voor het komend overleg: 1. Anita Potters (Equalit) 2. Holger Peters (Buren) 3. Bartel van Strien (Utrechtse Heuvelrug) Uiteraard hebben we met elkaar afgesproken dat we stemmen wie wel/niet onderdeel is van het team, maar ergens staat dat misschien los van het overleg zelf. Ik heb er persoonlijk geen moeite om deze mensen nu al uit te nodigen voor komend overleg en graag ontvang ik jullie akkoord hierop. Met vriendelijke groet, Tahir Shazad Malik mobile +31 (0)6 14 77 50 82 From: Niels Lindeboom <niels.lindeboom(a)dimpact.nl> Sent: donderdag 5 november 2020 10:49 To: Tahir Malik <tahir(a)contezza.nl> Cc: Holger Peters <hpeters(a)buren.nl> Subject: RE: Open Zaak Product Steering Group Dag Tahir, Wil jij ook Holger Peters van Gemeente Buren uitnodigen voor de eerstvolgened Product Steering Commitee? Met vriendelijke groet, Niels Lindeboom Regisseur Samenwerking [cid:image001.png@01D6B361.40F7CE70] +31 6 22270923 | 088 346 0001 [Telefoon]<https://www.dimpact.nl/> [Twitter] <https://twitter.com/DIMPACT_tweets> -----Oorspronkelijke afspraak----- Van: Tahir Malik <tahir(a)contezza.nl<mailto:tahir@contezza.nl>> Verzonden: vrijdag 30 oktober 2020 17:17 Aan: Joeri Bekker; jan(a)publiccode.net<mailto:jan@publiccode.net>; g.vandennoort(a)exxellence.nl<mailto:g.vandennoort@exxellence.nl>; Hugo ter Doest; felix; Peter Moen; Niels Lindeboom; silvion.moesan(a)opensatisfaction.nl<mailto:silvion.moesan@opensatisfaction.nl>; alba(a)publiccode.net<mailto:alba@publiccode.net>; Bozarov, Lazo; Rita Berghuis Onderwerp: Open Zaak Product Steering Group Tijd: woensdag 18 november 2020 15:00-16:00 (UTC+01:00) Amsterdam, Berlijn, Bern, Rome, Stockholm, Wenen. Locatie: https://meet.community.publiccode.net/OpenZaakProductSteeringGroup Meeting link: https://meet.community.publiccode.net/OpenZaakProductSteeringGroup Mailinglist: https://lists.publiccode.net/mailman/postorius/lists/openzaak-discuss.lis... Slack Channel: https://samenorganiseren.slack.com/archives/CT6UH711Q Previous Hack MD file: https://hackmd.io/_o_N4lI1SRGrCL0g7GNs7Q?view The following meeting will be held in Dutch/Nederlands as proposed unless publiccode has a valid reason not to. New Agenda: 1. Actions from previous meeting 2. Budget 3. Should we communicate back to the core group 4. What should we do with the roadmap items? 5. Any other thoughts members want to bring in Previous Agenda: 1. Discuss mission, vision and scope 2. Future features and roadmap 3. Evaluate governance/future agenda 4. New or changing members

2 years, 6 months

3
2
0 0

OpenZaak article to be mentioned in Open Source newsletter ministry of internal affairs (BZK)

by Felix Faassen

Dear OpenZaak community, As you may know we got the opportunity to get a mention in the BZK open source newsletter. The article is published on: https://opensource.pleio.nl/groups/view/57979222/open-source/blog/view/57... and will be mentioned in the newsletter going out today. As soon as the open source BZK newsletter is sent out you can share and/or like this article if you want. Best, Felix -- Felix Faassen, Codebase steward Foundation for Public Code | https://publiccode.net github.com/publiccodenet | github.com/felixfaassen felix(a)publiccode.net | +31 624633278

2 years, 7 months

1
0
0 0

2023

2022

2021

2020

openzaak-discuss November 2020