From 2a663dd70d92399098db22d4781f603a202ee442 Mon Sep 17 00:00:00 2001 From: Elena FdR Date: Tue, 14 Apr 2020 11:19:51 +0200 Subject: [PATCH 01/54] add index.md + content --- index.md | 44 ++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 44 insertions(+) create mode 100644 index.md diff --git a/index.md b/index.md new file mode 100644 index 0000000..82b363d --- /dev/null +++ b/index.md @@ -0,0 +1,44 @@ +# OpenZaak market consultation index + +:tada: Welcome to the OpenZaak market consultation! :tada: + +:tada: Welkom bij de OpenZaak marktconsultatie! :tada: + +## Nederlands + +Het doel van deze marktconsultatie is om marktpartijen uit te nodigen bij het opzetten van de OpenZaak-community. Dit omvat het mede creëren van codebase-governance, de gemeenschapsdynamiek en de product marketing rondom OpenZaak, op een manier die u in staat stelt een duurzaam bedrijfsmodel na te streven. + +Hieronder vindt u een inleiding, een reeks voorstellen en vragen, een voorstel voor governance.md, en **informatie over hoe u op deze consultatie kunt reageren. Deze reacties dienen uiterlijk op 1-5-2020 vóór 17:00 uur ontvangen te zijn.** + +Als je vragen hebt over deze consultatie, aarzel dan niet om [een issue aan te maken](https://github.com/open-zaak/openzaak-market-consultation/issues/new/choose) of e-mail Niels Lindeboom op niels.lindeboom@dimpact.nl. + +## English + +The goal of this market consultation is to invite market parties to help set up the OpenZaak community. This includes co-creating codebase governance, community dynamics, and the product marketing around OpenZaak in a way that allows you to pursue a sustainable business model. + +Below you can find an introductory cover letter, a set of proposals and questions, a draft governance.md, and **how to respond to this consultation. The responses should be received by 1-5-2020 before 17:00.** + +If you have any questions about this consultation, please feel free to [create an issue](https://github.com/open-zaak/openzaak-market-consultation/issues/new/choose) or email Niels Lindeboom at niels.lindeboom@dimpact.nl. + +## Consultation contents / Consultatie inhoud + +Introduction / Inleiding + +* [English](https://hackmd.io/BwMPNgCkTRWfCKxjZVsmiA) +* [Nederlands](https://hackmd.io/qBwWGvmvSk6IwhabTgsrtw) + +Our proposals and questions / Onze voorstellen en vragen + +* [English](https://hackmd.io/XJ0rLW4pQXCJjZIw9A7ArQ) +* [Nederlands](https://hackmd.io/OFGiBKmLSh6ug7Gpv3Hbzw) + +OpenZaak codebase + +* OpenZaak [README](https://github.com/open-zaak/open-zaak/blob/master/README.rst) (Nederlands) +* OpenZaak [CONTRIBUTING](https://github.com/open-zaak/open-zaak/blob/master/CONTRIBUTING.md) (English) +* Draft of a potential [governance.md]() file (English) + +How to respond / Hoe te reageren + +* [English](https://hackmd.io/AQOmgrpSQIeMVC4OhFxKDA) +* [Nederlands](https://hackmd.io/NT4ywg6bSReSgsocu1HFXw) From c0141cc522dc74623a8944e13650ada784222802 Mon Sep 17 00:00:00 2001 From: Jan Ainali Date: Tue, 14 Apr 2020 11:24:47 +0200 Subject: [PATCH 02/54] Rename index.md to README.md --- index.md => README.md | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename index.md => README.md (100%) diff --git a/index.md b/README.md similarity index 100% rename from index.md rename to README.md From 06e2eef67e7dbd136a4f769dcb248a73608f5edf Mon Sep 17 00:00:00 2001 From: ElenaFdR Date: Tue, 14 Apr 2020 11:25:44 +0200 Subject: [PATCH 03/54] add introduction-en.md + content --- introduction-en.md | 46 ++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 46 insertions(+) create mode 100644 introduction-en.md diff --git a/introduction-en.md b/introduction-en.md new file mode 100644 index 0000000..96b97a4 --- /dev/null +++ b/introduction-en.md @@ -0,0 +1,46 @@ +# Introduction: Open invitation for market parties to join the OpenZaak community + +
Home | Introduction | Our proposals and questions | How to respond
+ +OpenZaak is an open source codebase commissioned by a coalition representing over 45 municipalities including Amsterdam, Arnhem, Delft, Haarlem, ’s-Hertogenbosch, Rotterdam, Tilburg, Hoorn, Medemblik, Utrecht, SED (composed of Stede Broec, Enkhuizen and Drechterland) and Dimpact (composed of more than 30 municipalities). + +The first production-ready iteration was completed in February 2020. The OpenZaak community is now looking for market parties to help co-create a vision for what a scalable vendor network and community could look like. OpenZaak has the potential to scale to all Dutch municipalities. + +The outcome of this market consultation will inform how municipalities start procuring vendor support to help with their implementations. + +## What does OpenZaak do? + +The OpenZaak codebase helps Dutch municipalities comply with the [VNG standard for case management](https://www.vngrealisatie.nl/producten/api-standaarden-zaakgericht-werken) (zaakgericht werken). It consists of Python-based backend components which provide production-ready APIs for municipalities. More information about the codebase can be found on the [OpenZaak Github repository](https://github.com/open-zaak/open-zaak). + +## Enabling a healthy vendor community + +The participating municipalities are now looking for interested vendors to support them in implementing the codebase (including in the development, maintenance, implementation and support). The ambition is to have a healthy open source community in which vendors are empowered to grow the market for OpenZaak, and procurement is simplified and standardized. + +For this, we believe it is important to have an open and collaborative community, including a single codebase with a common governance structure and a shared understanding on bug fixes and support. More information on the municipalities’ needs, draft vision, and open questions can be found in [our proposals and questions](https://hackmd.io/XJ0rLW4pQXCJjZIw9A7ArQ) and the [draft governance document](governance.md). + +## About this market consultation + +Market parties interested in participating are asked to carefully [review our proposals](https://hackmd.io/XJ0rLW4pQXCJjZIw9A7ArQ) and respond to the questions listed there. + +Answers must be received by Niels Lindeboom before 1-5-2020. Based on these answers, market parties may be invited to one or several workshops together with the municipalities to define how to set up the OpenZaak community. More information about this market consultation process can be found in [how to respond](https://hackmd.io/AQOmgrpSQIeMVC4OhFxKDA). + +This market consultation is being run by [Dimpact](https://www.dimpact.nl/), on behalf of the OpenZaak municipalities, supported by the [Foundation for Public Code](https://publiccode.net/). + +
Home | Introduction | Our proposals and questions | How to respond
+ + From 896efac753bfbdab8b15d416e9be461e70d478e1 Mon Sep 17 00:00:00 2001 From: ElenaFdR Date: Tue, 14 Apr 2020 11:29:02 +0200 Subject: [PATCH 04/54] Add introduction-nl.md + content --- introduction-nl.md | 46 ++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 46 insertions(+) create mode 100644 introduction-nl.md diff --git a/introduction-nl.md b/introduction-nl.md new file mode 100644 index 0000000..eeb50ea --- /dev/null +++ b/introduction-nl.md @@ -0,0 +1,46 @@ +# Inleiding: Open uitnodiging voor marktpartijen om lid te worden van de OpenZaak community + +
Home | Inleiding | Onze voorstellen en vragen | Reageren op de marktconsultatie
+ +OpenZaak is een open source codebase gebouwd in opdracht van een coalitie van meer dan 45 gemeenten waaronder Amsterdam, Arnhem, Delft, Haarlem, 's-Hertogenbosch, Rotterdam, Tilburg, Hoorn, Medemblik, Utrecht, SED (bestaande uit Stede Broec, Enkhuizen en Drechterland) en Dimpact (bestaande uit meer dan 30 gemeenten). + +De eerste productierijpe iteratie was afgerond in februari 2020. De OpenZaak-community is nu op zoek naar marktpartijen om mee te denken over hoe het schaalbare leveranciersnetwerk en de community eruit zouden kunnen zien. OpenZaak heeft de potentie om op te schalen naar alle Nederlandse gemeenten. + +De uitkomst van deze marktconsultatie zal bepalen hoe gemeenten beginnen met het verkrijgen van leveranciersondersteuning om te helpen bij hun implementaties. + +## Wat doet OpenZaak? + +De OpenZaak codebase helpt Nederlandse gemeenten om te voldoen aan de [VNG-standaard voor zaakgericht werken](https://www.vngrealisatie.nl/producten/api-standaarden-zaakgericht-werken). Het bestaat uit Python-gebaseerde backend componenten die productiewaardige API's voor gemeenten bevatten. Meer informatie over de codebase is te vinden in de [OpenZaak Github repository](https://github.com/open-zaak/open-zaak). + +## Een gezonde leverancierscommunity + +De deelnemende gemeenten zijn op zoek naar geïnteresseerde leveranciers om hen te ondersteunen bij de implementatie van de codebase (onder meer in de ontwikkeling, onderhoud, implementatie en ondersteuning). De ambitie is om een gezonde open source community te hebben waarin leveranciers de mogelijkheid krijgen om de markt voor OpenZaak te laten groeien, en waarin inkoop wordt vereenvoudigd en gestandaardiseerd. + +Hiervoor vinden we het belangrijk om een open en collaboratieve gemeenschap te hebben, inclusief één codebase met een gemeenschappelijke governancestructuur en een gedeeld begrip over bugfixes en -ondersteuning. Meer informatie over de behoeften, conceptvisie en open vragen van de gemeenten is te vinden in [onze voorstellen en vragen](https://hackmd.io/OFGiBKmLSh6ug7Gpv3Hbzw) en het [draft governance.md document](governance.md). + +## Over deze marktconsultatie + +Marktpartijen die geïnteresseerd zijn in deelname worden gevraagd [onze voorstellen en vragen](https://hackmd.io/OFGiBKmLSh6ug7Gpv3Hbzw?both) zorgvuldig te herzien en te reageren op de daar genoemde vragen. + +De antwoorden moeten voor 1-5-2020 worden ontvangen door Niels Lindeboom. Op basis van deze antwoorden kunnen marktpartijen samen met de gemeenten worden uitgenodigd voor één of meerdere workshops om te bepalen hoe de OpenZaak-gemeenschap kan worden opgezet. Meer informatie over dit marktraadplegingsproces is te vinden in [hoe te reageren](https://hackmd.io/NT4ywg6bSReSgsocu1HFXw?both). + +Deze marktconsultatie wordt georganiseerd door [Dimpact](https://www.dimpact.nl/), in opdracht van de OpenZaak gemeenten, ondersteund door de [Foundation for Public Code](https://publiccode.net/). + +
Home | Inleiding | Onze voorstellen en vragen | Reageren op de marktconsultatie
+ + \ No newline at end of file From b9ce791e6c56f925cde545c46e223a683280da50 Mon Sep 17 00:00:00 2001 From: ElenaFdR Date: Tue, 14 Apr 2020 11:37:24 +0200 Subject: [PATCH 05/54] Add questions-nl.md + content --- questions-nl.md | 182 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 182 insertions(+) create mode 100644 questions-nl.md diff --git a/questions-nl.md b/questions-nl.md new file mode 100644 index 0000000..c58925c --- /dev/null +++ b/questions-nl.md @@ -0,0 +1,182 @@ +# Onze voorstellen en vragen + +
Home | Inleiding | Onze voorstellen en vragen | Reageren op de marktconsultatie
+ +Deze pagina bevat drie onderdelen. + +1. Een visie voor een open source community - een conceptvisie voor hoe de OpenZaak community eruit zou kunnen zien. +2. Behoeften van gemeenten - een indicatief overzicht van ondersteuningsvormen die gemeenten nodig hebben van leveranciers. +3. Vragen marktconsultatie - een overzicht van onze open vragen aan marktpartijen. + +## Visie voor een open source community + +Wij geloven dat OpenZaak succesvol is als gemeenten en marktpartijen samen werken aan een gemeenschappelijk doel: een open en samenwerkende community die kan schalen. + +Voor gemeenten is het belangrijk om een groot en divers leveranciersnetwerk te hebben, die elke gemeente kan ondersteunen met hun specifieke behoeften (inclusief ondersteuning voor ontwikkeling, hosting en implementatie). Dit zal ook bijdragen aan het verminderen van de risico's van gemeenten bij de implementatie van de OpenZaak codebase. + +Voor leveranciers is het belangrijk om het aantal deelnemende gemeenten te laten groeien (de markt voor hun diensten te vergroten) en effectief samen te werken met andere leveranciers (het aanvullen van vaardigheden en het verbeteren van de betrouwbaarheid van de implementatie van de OpenZaak codebase). + +Zonder alle antwoorden in detail te kennen, omvat onze visie voor de community: + +* samenwerken aan één leverancier-neutrale codebase en shared branchingmodel, waarbij uiteenlopende forks worden vermeden +* collaborative governance, inclusief rond gedeelde roadmaps (feature en technical) en open issue tracker +* een gedeeld inzicht in hoe bugfixes en -ondersteuning kunnen worden aangepakt, met name in situaties van operationele downtime of beveiligingsrisico's +* een inclusieve community (inclusief open communicatiekanalen, codebase marketingmateriaal en codes of conduct) die nieuwe marktpartijen en nieuwe deelnemende gemeenten verwelkomt +* leveranciers in staat stellen om effectieve leden en ambassadeurs van de community te worden + +## Behoeften van gemeenten + +OpenZaak bestaat uit een set componenten die door gemeenten op diverse wijze gebruikt zullen worden. Dit betekent dat de gemeenschap moet worden ingericht om verschillende soorten leveranciers in staat te stellen verschillende soorten gemeenten te ondersteunen. + +De onderstaande lijsten beschrijven eerst de behoeften die alle gemeenten zullen hebben, en vervolgens drie 'soorten' gemeenten en hun bijbehorende behoeften ten opzichte van de community en marktondersteuning. + +### Behoeften die alle gemeenten hebben + +* Er moeten koppelingen zijn met externe databases/sets (i.e. basisgegevens) +* Er is de behoefte om de eigendom over data te behouden, en continue toegang tot die data te hebben +* Er is eenvoudige dataportabiliteit nodig (bijvoorbeeld voor wettelijk vereiste archivering) +* Er zijn leveranciers nodig die bijdragen aan de main repository van OpenZaak (inclusief [EUPL-licentie](https://github.com/open-zaak/open-zaak/blob/master/LICENSE.md)) +* Er is de behoefte om in lijn te blijven met de [VNG-standaarden](https://www.vngrealisatie.nl/producten/api-standaarden-zaakgericht-werken) +* Er is de behoefte om de feature roadmap te beïnvloeden +* Er is behoefte dat leveranciers OpenZaak opnemen in al hun zaak systemen en andere zaak-gerichte producten en aanbiedingen + +### Behoefte aan ‘Full service' pakket + +Sommige gemeenten hebben behoefte aan een full service pakket. Dit omvat hosting, implementatie, onderhoud en ontwikkeling, door een of meerdere leveranciers. Daarnaast wordt OpenZaak geïntegreerd met bestaande producten van bestaande leveranciers, bijvoorbeeld de zaaksystemen die ze gebruiken. + +Zij hebben leveranciers nodig die het volgende aanbieden: + +* hosting support +* implementation support +* maintenance support +* new feature en bug fix support +* integration support +* helpdesk, configuration support, vragen en training +* bug fixes en hot fixes + +### Behoefte aan 'Backend as a service' + +Sommige gemeenten hebben een 'Backend as a service' nodig. Ze zijn in staat om andere applicaties, die afhankelijk zijn van OpenZaak, op hun eigen servers (of in de cloud) te draaien, maar willen dat leveranciers OpenZaak voor hen hosten, uitvoeren en onderhouden. + +Zij hebben leveranciers nodig die het volgende aanbieden: + +* een integratie partner +* duidelijke continuous integration/continuous development +* een sandbox environment +* bug fixes en hot fixes +* helpdesk, configuration support, en treining + +### Behoefte aan In-house implementatie + +Sommige gemeenten zullen OpenZaak met uitsluitend eigen middelen willen implementeren. Zij zullen hun werk moeten coördineren met andere gemeenten en leveranciers. + +Zij moeten in de community samenwerken aan: + +* duidelijke development/contribution guidelines +* samenwerken met marktpartijen en andere gemeente omtrent een product en technical roadmap en backlogs +* een manier om bug fixes te coordineren met marktpartijen en andere gemeente + +## Vragen marktconsultatie + +Deze sectie bevat een lijst met open vragen. Elk deel bevat onze huidige veronderstellingen en een reeks open vragen die we willen bespreken met de leveranciersgemeenschap. + +Let op: vragen zijn indicatief, we horen graag uw mening over elk van de punten in deze bijlage. + +### 1. Single shared codebase + +#### Veronderstellingen + +We willen een open community op schaal faciliteren, inclusief samenwerking op een vendor- neutrale codebase en shared branching model, waarbij uiteenlopende forks worden vermeden. Dit willen we opnemen in de contracten die gemeenten hebben met leveranciers, bijvoorbeeld door het benoemen van afspraken over branches en een nadruk op continuous integration. + +#### Vragen + +1. Hoe zou u dit principe willen opnemen in contracten die gemeenten met u afsluiten? +2. Hoe stelt u voor om 'soft forks' up-to-date te houden van elkaar? Moet er een centrale repository zijn die als master kan worden beschouwd? +3. Welke uitdagingen zijn er voor u om in zo'n multi-branch omgeving te werken? Hoe kunnen deze uitdagingen worden beperkt om de bedrijfsrisico's voor u te verminderen? +4. Heeft u ooit eerder op deze manier gewerkt? +5. Is de [huidige architectuur en make-up van de codebase](https://github.com/open-zaak/open-zaak) bevorderlijk voor multi-vendor samenwerking en modulaire implementatie van componenten? + +### 2. Shared codebase governance + +#### Veronderstellingen + +Onze visie is om samenwerking mogelijk te maken tussen meerdere gemeenten en leveranciers, die samen aan de codebase werken. Hiervoor is een gedeeld bestuur nodig voor de codebase. Dit kan onder meer het volgende behelzen: a) een open en gedeelde issue en bug tracker, b) een open en gedeelde feature roadmap, en c) een open en gedeelde technical roadmap. Dit omvat ook engineering en contributing guidelines, evenals open communicatiekanalen. + +Deze marktconsultatie omvat een [ontwerpvoorstel van een governancestructuur](governance.md) voor open discussie. + +#### Vragen + +1. Hoe vindt u dat governance moet worden georganiseerd binnen de community? +2. Wat zijn de uitdagingen die u voorziet bij het onderhouden van open backlogs bij uw klanten? +3. Wie moet verantwoordelijk zijn voor het bijwerken van de shared roadmap? U, de gemeenten, of een gedeelde verantwoordelijkheid? +4. Hoe wilt u de gedeelde feature en technical roadmap kunnen beïnvloeden? +5. Hoe wilt u dat de community omgaat met het ontwikkelen, eens worden en onderhouden van gedeelde engineering en contributing guidelines? +6. Welke risico’s ziet u in het werken in zo'n omgeving? + +### 3. Bugs en bug fixes + +#### Veronderstellingen + +Er zal een centrale, openbare en geprioriteerde issue tracker zijn voor features en bugs. Veel van deze problemen kunnen kleine hoeveelheden werk (minder dan 80 uur) omvatten. Daarnaast zullen veel gemeenten issues en bugs hebben die verband houden met hun lokale implementatie en context. + +#### Vragen + +1. Moet het werken op zowel lokale implementaties en de centrale repository worden opgenomen in de zelfde of aparte contracten? +2. Hoe wilt u dat de contracten zo gestructureerd zijn dat u kunt werken aan lokale implementaties en branches en ook kunt bijdragen aan de centrale repository? +3. Hoe moeten bugfixes in de hele community worden geïmplementeerd? Kunnen leveranciers hotfixes van andere leveranciers overnemen voordat deze zijn samengevoegd in de centrale repository? Of moeten leveranciers pas wijzigingen doorvoeren nadat ze zijn samengevoegd in de centrale repository? +4. Wat voor soort aansprakelijkheidsvraagstukken zouden er kunnen zijn indien ‘hot fixing’ onverwachte schade of verdere problemen oplevert? Levert dit een probleem op voor uw contractuele verplichtingen aan uw klant? + +### 4. Helpdesk en support + +#### Veronderstellingen + +Veel gemeenten zullen de voorkeur geven aan één enkele leverancier die ze kunnen bellen voor al hun behoeften. Dit varieert van vragen, bugs, ideeën voor doorontwikkeling, technische integratie, training, configuratie van machtigingen / autorisatie, meldingen, enzovoort. Onze veronderstelling is dat in veel gevallen, geen enkele leverancier al deze diensten kan of wil leveren. + +#### Vragen + +1. Is het mogelijk om één helpdesk op te zetten voor alles wat te maken heeft met het gebruik van OpenZaak door een gemeente? Of zijn er voordelen voor verschillende leveranciers die verschillende helpdesks onderhouden voor verschillende soorten vragen (bijvoorbeeld om hen in staat te stellen hun serviceaanbod te differentiëren?) +2. Kunnen meerdere marktpartijen zich verenigen om hun aanbod te combineren? +3. Kunnen gespecialiseerde 'helpdeskaanbieders' werk uitbesteden aan andere aanbieders? + +### 5. Standards compliance + +#### Veronderstellingen + +De OpenZaak API's zijn gebaseerd op een VNG standaard, de [API's voor zaakgericht werken](https://www.vngrealisatie.nl/producten/api-standaarden-zaakgericht-werken). De standaard wordt continu onderhouden en verbeterd en OpenZaak moet daaraan blijven voldoen. Deze updates moeten worden gepropageerd over de centrale repository-branche, evenals repositories die marktpartijen gebruiken om hun diensten te leveren (zoals backend-as-a-service). + +#### Vragen + +1. Hoe zorgen we ervoor dat updates van de VNG-standaard op de juiste manier worden doorgevoerd in lopende OpenZaak-implementaties? Moeten deze vereisten worden opgenomen in contracten met marktpartijen? +2. Wat vindt u van versiebeheer van OpenZaak ten opzichte van andere toepassingen? Hoeveel backwards-compatible versies moeten worden ondersteund? +3. Moeten leveranciers in het kader van hun contracten worden gevraagd om wat ze hebben geleerd bij het implementeren en ondersteunen van OpenZaak te laten bijdragen aan de VNG-standaard? + +### 6. Codebase marketing + +#### Veronderstellingen + +Om de community effectief te laten schalen, gaan we ervan uit dat er een set neutraal marketingmateriaal moet zijn, waaronder logo, website, productdocumentatie, casestudies, business case materiaal, enzovoort. Wij zijn van mening dat dit leveranciers- en gemeente- neutraal moet zijn om een gedeelde set storytelling resources mogelijk te maken. + +#### Vragen + +1. Op welke wijze zou u willen dat dit marketingmateriaal wordt gemaakt? +2. Wat voor invloed wilt u hebben op dit materiaal en de website? +3. Moeten leveranciers contractueel worden gevraagd om, wat ze hebben geleerd bij het implementeren en ondersteunen van OpenZaak, toe te voegen aan het OpenZaak marketingmateriaal (inclusief bijvoorbeeld user testimonials, business cases, etc)? + +
Home | Inleiding | Onze voorstellen en vragen | Reageren op de marktconsultatie
+ + \ No newline at end of file From 44a5efc1edd2681e6578f3fa4b8ecc895f36c2a0 Mon Sep 17 00:00:00 2001 From: Jan Ainali Date: Tue, 14 Apr 2020 11:40:28 +0200 Subject: [PATCH 06/54] change to the correct file names instead of hackmd --- README.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index 82b363d..e50803c 100644 --- a/README.md +++ b/README.md @@ -16,7 +16,7 @@ Als je vragen hebt over deze consultatie, aarzel dan niet om [een issue aan te m The goal of this market consultation is to invite market parties to help set up the OpenZaak community. This includes co-creating codebase governance, community dynamics, and the product marketing around OpenZaak in a way that allows you to pursue a sustainable business model. -Below you can find an introductory cover letter, a set of proposals and questions, a draft governance.md, and **how to respond to this consultation. The responses should be received by 1-5-2020 before 17:00.** +Below you can find an introductory cover letter, a set of proposals and questions, a draft governance.md, and **how to respond to this consultation. The responses should be received by 1-5-2020 before 17:00.** If you have any questions about this consultation, please feel free to [create an issue](https://github.com/open-zaak/openzaak-market-consultation/issues/new/choose) or email Niels Lindeboom at niels.lindeboom@dimpact.nl. @@ -24,13 +24,13 @@ If you have any questions about this consultation, please feel free to [create a Introduction / Inleiding -* [English](https://hackmd.io/BwMPNgCkTRWfCKxjZVsmiA) -* [Nederlands](https://hackmd.io/qBwWGvmvSk6IwhabTgsrtw) +* [English](introduction-en.md) +* [Nederlands](introduction-nl.md) Our proposals and questions / Onze voorstellen en vragen -* [English](https://hackmd.io/XJ0rLW4pQXCJjZIw9A7ArQ) -* [Nederlands](https://hackmd.io/OFGiBKmLSh6ug7Gpv3Hbzw) +* [English](questions-en.md) +* [Nederlands](questions-nl.md) OpenZaak codebase @@ -40,5 +40,5 @@ OpenZaak codebase How to respond / Hoe te reageren -* [English](https://hackmd.io/AQOmgrpSQIeMVC4OhFxKDA) -* [Nederlands](https://hackmd.io/NT4ywg6bSReSgsocu1HFXw) +* [English](how-to-respond-en.md) +* [Nederlands](how-to-respond-nl.md) From d09b74b4ed109e63679086b14df1cfe051ac2248 Mon Sep 17 00:00:00 2001 From: ElenaFdR Date: Tue, 14 Apr 2020 11:40:36 +0200 Subject: [PATCH 07/54] Add questions-en.md + content --- questions-en.md | 187 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 187 insertions(+) create mode 100644 questions-en.md diff --git a/questions-en.md b/questions-en.md new file mode 100644 index 0000000..d627f6d --- /dev/null +++ b/questions-en.md @@ -0,0 +1,187 @@ +--- +tags: openzaak +URL: Open-Zaak/market-consultation/questions-en.md +--- + +# Our proposals and questions + +
Home | Introduction | Our proposals and questions | How to respond
+ +This page contains three sections: + +- Vision for an open source community - a draft vision for what the OpenZaak community could look like +- Needs of municipalities - an indicative overview of kinds of support the municipalities need from vendors +- Market consultation questions - an overview of our open questions to market parties + +## Vision for an open source community + +We believe the success of OpenZaak involves municipalities and market parties working together towards a common goal: an open and collaborative community at scale. + +For municipalities it is important to have a large and diverse vendor network that can support each municipality with their particular needs (including support for development, hosting and implementation). This will also help reduce municipalities’ risks when implementing the OpenZaak codebase. + +For vendors it is important to grow the number of replicating municipalities (increasing the market for their services), and to work effectively with other vendors (complementing skill sets and improving the reliability of implementing the OpenZaak codebase). + +Without knowing all the answers in detail, our vision for this community includes: + +- collaborating on a single, vendor-neutral codebase and shared branching model, avoiding diverging forks +- collaborative governance, including around shared roadmaps (feature and technical) and open issue tracker +- a shared understanding of how to approach bug fixes and support, particularly in situations of operational downtime or security risks +- an inclusive community (including open communication channels, codebase marketing material and codes of conduct) that is welcoming to new market parties and new replicating municipalities +- empowering vendors to become effective members and ambassadors of the community + +## Needs of municipalities + +OpenZaak consists of a set of components that will be used by a diverse set of municipalities. This means the community needs to be set up to allow for different types of vendors to support different types of municipalities. + +The lists below set out needs all municipalities will have, as well as three ‘types’ of municipalities and their corresponding needs vis-à-vis the community and market support. + +### Needs all municipalities have + +- Need connection with external databases/sets (i.e. basisgegevens) +- Need to retain ownership of data, and continuous access to the data +- Need easy data portability (for example for legally required archiving) +- Need vendors who contribute to the OpenZaak main repository (including [EUPL license](https://github.com/open-zaak/open-zaak/blob/master/LICENSE.md)) +- Need to remain in sync with the [VNG standards](https://www.vngrealisatie.nl/producten/api-standaarden-zaakgericht-werken) +- Need to influence the feature roadmap +- Need vendors to use OpenZaak in all products and services that create or use case management data + +### ‘Full service’ package needs + +Some municipalities need a full service package. This includes hosting, implementation, maintenance and development, by one or many vendors. Additionally, OpenZaak will be integrated with existing products from existing vendors, for example the case management systems they use. + +They need market parties to offer: + +- hosting support +- implementation support +- maintenance support +- new feature and bug fix support +- integration support +- a helpdesk, configuration support, questions and training +- a way to file bug fixes and deploy hotfixes + +### ‘Backend as a service’ needs + +Some municipalities need ‘Backend as a service’. They are able to run other applications dependent on OpenZaak on their own servers (or in the cloud), but would like vendors to host, run and maintain OpenZaak for them. + +They need market parties to offer: + +- an integration partner +- clear continuous integration/continuous development +- a sandbox environment +- a way to file bug fixes and deploy hotfixes +- a helpdesk, configuration support, questions and training + +### In-house implementation needs + +Some municipalities will want to implement the component with exclusively in-house resources. They will need to coordinate their work with other municipalities and vendors. + +They need the community to have: + +- clear development/contribution guidelines +- a way to liaise with vendors and other municipalities regarding product and technical roadmap and backlogs +- a way to fix bugs together with vendors and other municipalities + +## Market consultation questions + +This section includes a list of open questions we have. Each item includes our current assumptions, and open questions we would like to discuss with the vendor community. + +Please note questions are indicative - we would love to hear your thoughts on any of the points in this annex. + +### 1. Single shared codebase + +#### Assumptions + +We would like to facilitate an open community at scale, including collaboration on a single, vendor-neutral codebase and shared branching model, avoiding diverging forks. This should be included in the contracts municipalities have with vendors, for example through naming conventions for branches and an emphasis on continuous integration. + +#### Questions + +1. How would you like to see this principle included in contracts municipalities have with you? +2. How do you propose keeping ‘soft forks’ up to date with each other? Should there be a central repository which can be considered as master? +3. What challenges would working in such a multi-branch environment present for you? How could these challenges be mitigated to reduce the business risks for you? +4. Have you ever worked in this way before? +5. Is the [current architecture and make up of the codebase](https://github.com/open-zaak/open-zaak) conducive to multi-vendor collaboration and modular componentized implementation? + +### 2. Shared codebase governance + +#### Assumptions + +Our vision is to enable collaboration between multiple municipalities and vendors working on the codebase together. For this, we assume we will need shared governance for the codebase. This could include: a) an open shared issue and bug tracker, b) an open and shared feature roadmap, and c) an open and shared technical roadmap. This will also include engineering and contributing guidelines, as well as open communication channels. + +This market consultation includes a [draft proposal for a governance structure](governance.md) for open discussion. + +#### Questions + +1. How would you like to see governance handled within the community? +2. What are the challenges you foresee maintaining open backlogs with your clients? +3. Who should be responsible for updating the shared roadmaps? You, the municipalities, or shared? +4. How would you like to influence the feature and technical roadmap? +5. How would you like to see the community develop, agree and maintain shared engineering and contributing guidelines? +6. What risks do you see working in such an environment? + +### 3. Bugs and bug fixes + +#### Assumptions + +There will be a central, public and prioritised issue tracker for features and bugs. Many of these issues might include small amounts of work (less than 80 hours). Additionally, many municipalities will have issues and bugs related to their local implementation and context. + +#### Questions + +1. Should work on both local instances and the central repository be included in a single contract? +2. How would you like the contracts to be structured so that you can work on local implementations and branches as well as contributing to the central repository? +3. How should bug fixes be deployed throughout the community? Can vendors take hotfixes from other vendors before these have been merged into the central repository? Or should vendors only implement changes after they have been merged to the central repository? +4. What kind of liability issues can come with hotfixing code that leads to unexpected damage or further problems? Does this create a problem for your contractual obligations to your client? + +### 4. Helpdesk and support + +#### Assumptions + +Many municipalities will prefer to have a single provider they can call for all their needs. This ranges from questions, bugs, ideas for new features, technical integration, training, configuration of permissions/authorisation, notifications, and so forth. Our assumption is that in many cases, no single vendor will want to or be able to provide all these services. + +#### Questions + +1. Is it possible to set up a single helpdesk to cover everything related to a municipality’s use of OpenZaak? Or are there benefits to different vendors maintaining different helpdesks for different types of questions (for example, to allow them to differentiate their service offering?) +2. Could multiple market parties join together to combine their offering? +3. Could specialised ‘help desk’ providers subcontract work to other providers? + +### 5. Standards compliance + +#### Assumptions + +The OpenZaak APIs are based on the [APIs for zaakgericht werken](https://www.vngrealisatie.nl/producten/api-standaarden-zaakgericht-werken) which is a VNG standard. The standard is continuously maintained and improved, and OpenZaak has to comply with it. These updates will have to be propagated across the central repository branch, as well as repositories that market parties use to deliver their services (like backend-as-a-service). + +#### Questions + +1. How do we ensure updates to the VNG standard are appropriately reflected across running OpenZaak instances? Should these requirements be included in contracts with market parties? +2. What do you think about version control of OpenZaak vis-à-vis other applications? How many backwards-compatible versions should be supported? +3. Should vendors be asked as part of their contracts to contribute what they’ve learned from implementing and supporting OpenZaak back to the VNG standards? + +### 6. Codebase marketing + +#### Assumptions + +For the community to scale effectively, we assume there should be a set of neutral marketing material, including logo, website, product documentation, case studies, business case material, and so on. We believe this should be vendor -and municipality- neutral to enable a shared set of storytelling resources. + +#### Questions + +1. How would you like to see this marketing material created? +2. What kind of influence would you like over this material and the website? +3. Should vendors be asked as part of their contracts to contribute what they’ve learned from implementing and supporting OpenZaak to the OpenZaak marketing material (including for example user testimonials, business cases, etc)? + +
Home | Introduction | Our proposals and questions | How to respond
+ + From c20c3e00291263573804a4e614a3e418898d426f Mon Sep 17 00:00:00 2001 From: ElenaFdR Date: Tue, 14 Apr 2020 11:42:46 +0200 Subject: [PATCH 08/54] added how-to-respon-en.md + content --- how-to-respond-en.md | 58 ++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 58 insertions(+) create mode 100644 how-to-respond-en.md diff --git a/how-to-respond-en.md b/how-to-respond-en.md new file mode 100644 index 0000000..df41d19 --- /dev/null +++ b/how-to-respond-en.md @@ -0,0 +1,58 @@ +
Home | Introduction | Our proposals and questions | How to respond
+ +# How to respond + +This page explains the process and timing for responding to the market consultation. + +## Starting points for the market consultation + +With OpenZaak we are taking an important step towards realising the [Common Ground](https://commonground.nl/cms/view/54476259/over-common-ground) (Dutch) principles. But we are well aware that OpenZaak is only of value if it is actively used and developed further. + +Our goal is to create a community in which government, suppliers and partners work together. A community, without lock-ins, that works for all parties involved. It is also in this collective spirit that we’re setting up this market consultation. + +We want to use your experience, inspiration and brainpower to come to the right set-up. In order to be able to have the right conversation, we have set out our needs, proposals and questions to the market in this document. + +## Procedure of the market consultation + +The market consultation consists of two parts: + +1. A written response to our questions. We're deliberately not restricting the form and length of your answers. These responses should be received by 1-5-2020 before 17:00. You can send your answers to niels.lindeboom@dimpact.nl. Based on your responses we will review our proposal and adjust it if there are good suggestions. This modified proposal will then become the starting point for the workshop (part two of the consultation). +2. Optional: one or more workshops where together we will determine the various needs and prerequisites within the community (participation only on request of OpenZaak). After submitting your answers, you will receive a message no later than 13-5-2020 if you are invited for the workshop. This will take place on 20th and 21st of May 2020. With the invitation you will receive further information about the exact time and location. + +Dimpact is responsible for the communication about this market consultation. You can contact Niels Lindeboom at niels.lindeboom@dimpact.nl or 06-22270923. + +## Market consultation report + +We will produce an anonymized report after interested parties have answered the questions from the market consultation document and the workshop has taken place. This report will be made available to all market consultation participants, and will be published with the announcement of a possible tender. + +## Planning + +| Description | Datum | +|-------------|-------| +| Market consultation publication | 14-4-2020 | +| Submission deadline | 1-5-2020, 17:00 | +| Possible invitation to workshop | 13-05-2020 | +| Workshop (invitation only) | 20/21-5-2020 | + +## Legal aspects + +This document is for market consultation purposes only. It is made available on the express condition that it will only be used to provide suggestions and ideas. Participation in this market consultation cannot lead to obligations on the part of the participating market parties to enter into agreements with the participating municipalities or Dimpact, and vice versa. Market consultation participation does not entail any reimbursement of costs. + +
Home | Introduction | Our proposals and questions | How to respond
+ + From 0bd08a33beeec26767a76218b17a7fcc21cfba44 Mon Sep 17 00:00:00 2001 From: Jan Ainali Date: Tue, 14 Apr 2020 11:43:50 +0200 Subject: [PATCH 09/54] change hackmd links to file names + remove some trailing spaces --- introduction-nl.md | 28 ++++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/introduction-nl.md b/introduction-nl.md index eeb50ea..6541256 100644 --- a/introduction-nl.md +++ b/introduction-nl.md @@ -1,6 +1,6 @@ -# Inleiding: Open uitnodiging voor marktpartijen om lid te worden van de OpenZaak community +# Inleiding: Open uitnodiging voor marktpartijen om lid te worden van de OpenZaak community -
Home | Inleiding | Onze voorstellen en vragen | Reageren op de marktconsultatie
+
Home | Inleiding | Onze voorstellen en vragen | Reageren op de marktconsultatie
OpenZaak is een open source codebase gebouwd in opdracht van een coalitie van meer dan 45 gemeenten waaronder Amsterdam, Arnhem, Delft, Haarlem, 's-Hertogenbosch, Rotterdam, Tilburg, Hoorn, Medemblik, Utrecht, SED (bestaande uit Stede Broec, Enkhuizen en Drechterland) en Dimpact (bestaande uit meer dan 30 gemeenten). @@ -26,21 +26,21 @@ De antwoorden moeten voor 1-5-2020 worden ontvangen door Niels Lindeboom. Op bas Deze marktconsultatie wordt georganiseerd door [Dimpact](https://www.dimpact.nl/), in opdracht van de OpenZaak gemeenten, ondersteund door de [Foundation for Public Code](https://publiccode.net/). -
Home | Inleiding | Onze voorstellen en vragen | Reageren op de marktconsultatie
+
Home | Inleiding | Onze voorstellen en vragen | Reageren op de marktconsultatie
\ No newline at end of file + From 1d3502c1c04589ea1f5d93f6a30410ed6a2647d8 Mon Sep 17 00:00:00 2001 From: ElenaFdR Date: Tue, 14 Apr 2020 11:44:27 +0200 Subject: [PATCH 10/54] Added how-to-respond-nl.md --- how-to-respond-nl.md | 58 ++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 58 insertions(+) create mode 100644 how-to-respond-nl.md diff --git a/how-to-respond-nl.md b/how-to-respond-nl.md new file mode 100644 index 0000000..ac881e5 --- /dev/null +++ b/how-to-respond-nl.md @@ -0,0 +1,58 @@ +
Home | Inleiding | Onze voorstellen en vragen | Reageren op de marktconsultatie
+ +# Hoe te reageren + +Op deze pagina wordt het proces en het tijdschema voor de reactie op de marktconsultatie toegelicht. + +## Uitgangspunten marktconsultatie + +Met OpenZaak realiseren we een belangrijke stap om de [Common Ground](https://commonground.nl/cms/view/54476259/over-common-ground) principes te realiseren. Maar wij realiseren ons goed dat het pas van waarde is als het actief wordt gebruikt en doorontwikkelt. + +Onze motivatie is een community te realiseren waarin overheid, leveranciers en partners samenwerken. Een community, zonder lock-ins, die voor alle betrokken werkt. Vanuit die gezamenlijkheid willen we ook deze marktconsultatie opzetten. + +We willen jullie ervaring, inspiratie en denkkracht inzetten om tot de juiste opzet te komen. Om het goede gesprek te kunnen voeren hebben we in dit document onze behoeften, voorstellen en vragen aan de markt uitgewerkt. + +## Procedure van de marktconsultatie + +De marktconsultatie bestaat uit twee onderdelen. + +1. Een schriftelijke reactie op onze vragen. We stellen bewust geen restricties aan de vorm en lengte van jullie antwoorden. Deze reacties dienen uiterlijk op 1-5-2020 vóór 17:00 uur ontvangen te zijn. U kunt uw antwoorden sturen aan niels.lindeboom@dimpact.nl. Op basis van jullie antwoorden gaan wij opnieuw kijken naar ons voorstel en dit aanpassen als er goede suggesties zijn gegeven. Dit aangepaste voorstel wordt dan het uitgangspunt voor de workshop (deel twee van de consultatie). +2. Optioneel: een of meer workshops waarin we met elkaar de diverse behoefte en voorwaarden binnen de community gaan bepalen (deelname alleen op verzoek van OpenZaak). Na het indienen van jullie antwoorden ontvang je uiterlijk 13-5-2020 2020 een bericht of je wordt uitgenodigd voor de workshop. Deze vinden plaats op 20/21-5-2020. Bij de uitnodiging ontvang je verdere informatie over de exacte tijd en locatie. + +De communicatie over deze marktconsultatie verloopt via Dimpact. Je kunt contact opnemen met Niels Lindeboom op of 06-22270923. + +## Verslag marktconsultatie + +Nadat de geïnteresseerde partijen de vragen uit het marktconsultatiedocument hebben beantwoord, en de workshop is geweest, maken wij een geanonimiseerd verslag. Dit verslag wordt ter beschikking gesteld aan alle deelnemers van de marktconsultatie, en wordt gepubliceerd bij de aankondiging van een eventuele aanbesteding. + +## Planning + +| Omschrijving | Datum | +|---------------|-------| +| Publicatie marktconsultatie | 14-4-2020 | +| Indienen reactie (uiterlijk) | 1-5-2020, 17:00 | +| Eventuele uitnodiging Workshop | 13-5-2020 | +| Workshop (alleen op uitnodiging) | 20/21-5-2020 | + +## Juridische aspecten + +Dit document is alleen bestemd voor marktconsultatie doeleinden. Het wordt ter beschikking gesteld onder de uitdrukkelijke voorwaarde dat het uitsluitend gebruikt wordt om suggesties en ideeën aan te reiken. Een deelname aan deze marktconsultatie kan niet leiden tot verplichtingen van de deelnemende marktpartijen om overeenkomsten met de deelnemende gemeenten of Dimpact aan te gaan, en vice versa. Aan de deelname van de marktconsultatie is geen vergoeding van kosten verbonden. + +
Home | Inleiding | Onze voorstellen en vragen | Reageren op de marktconsultatie
+ + From 6c4b81ed268a1146f9439e1f77429d2e093fd44f Mon Sep 17 00:00:00 2001 From: Jan Ainali Date: Tue, 14 Apr 2020 11:46:47 +0200 Subject: [PATCH 11/54] replace hackmd links to file names --- how-to-respond-en.md | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/how-to-respond-en.md b/how-to-respond-en.md index df41d19..0484edc 100644 --- a/how-to-respond-en.md +++ b/how-to-respond-en.md @@ -1,4 +1,4 @@ -
Home | Introduction | Our proposals and questions | How to respond
+
Home | Introduction | Our proposals and questions | How to respond
# How to respond @@ -38,21 +38,21 @@ We will produce an anonymized report after interested parties have answered the This document is for market consultation purposes only. It is made available on the express condition that it will only be used to provide suggestions and ideas. Participation in this market consultation cannot lead to obligations on the part of the participating market parties to enter into agreements with the participating municipalities or Dimpact, and vice versa. Market consultation participation does not entail any reimbursement of costs. -
Home | Introduction | Our proposals and questions | How to respond
+
Home | Introduction | Our proposals and questions | How to respond
From 0152f74cf10a3d67a346bba8f383b2a39e547f5e Mon Sep 17 00:00:00 2001 From: Jan Ainali Date: Tue, 14 Apr 2020 11:49:09 +0200 Subject: [PATCH 12/54] replace hachmd links with file names --- how-to-respond-nl.md | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/how-to-respond-nl.md b/how-to-respond-nl.md index ac881e5..5d2b8ac 100644 --- a/how-to-respond-nl.md +++ b/how-to-respond-nl.md @@ -1,4 +1,4 @@ -
Home | Inleiding | Onze voorstellen en vragen | Reageren op de marktconsultatie
+
Home | Inleiding | Onze voorstellen en vragen | Reageren op de marktconsultatie
# Hoe te reageren @@ -38,21 +38,21 @@ Nadat de geïnteresseerde partijen de vragen uit het marktconsultatiedocument he Dit document is alleen bestemd voor marktconsultatie doeleinden. Het wordt ter beschikking gesteld onder de uitdrukkelijke voorwaarde dat het uitsluitend gebruikt wordt om suggesties en ideeën aan te reiken. Een deelname aan deze marktconsultatie kan niet leiden tot verplichtingen van de deelnemende marktpartijen om overeenkomsten met de deelnemende gemeenten of Dimpact aan te gaan, en vice versa. Aan de deelname van de marktconsultatie is geen vergoeding van kosten verbonden. -
Home | Inleiding | Onze voorstellen en vragen | Reageren op de marktconsultatie
+
Home | Inleiding | Onze voorstellen en vragen | Reageren op de marktconsultatie
From 5f6455b512fc4048f6c1acaed9875f92f1f8f399 Mon Sep 17 00:00:00 2001 From: Jan Ainali Date: Tue, 14 Apr 2020 11:52:42 +0200 Subject: [PATCH 13/54] replace hackmd links with file names and remove frontmatter --- questions-en.md | 29 ++++++++++++----------------- 1 file changed, 12 insertions(+), 17 deletions(-) diff --git a/questions-en.md b/questions-en.md index d627f6d..44b1fd3 100644 --- a/questions-en.md +++ b/questions-en.md @@ -1,11 +1,6 @@ ---- -tags: openzaak -URL: Open-Zaak/market-consultation/questions-en.md ---- - # Our proposals and questions -
Home | Introduction | Our proposals and questions | How to respond
+
Home | Introduction | Our proposals and questions | How to respond
This page contains three sections: @@ -167,21 +162,21 @@ For the community to scale effectively, we assume there should be a set of neutr 2. What kind of influence would you like over this material and the website? 3. Should vendors be asked as part of their contracts to contribute what they’ve learned from implementing and supporting OpenZaak to the OpenZaak marketing material (including for example user testimonials, business cases, etc)? -
Home | Introduction | Our proposals and questions | How to respond
+
Home | Introduction | Our proposals and questions | How to respond
From 9b48a9b20c66b8040723264f7560dd3cb220bf1f Mon Sep 17 00:00:00 2001 From: Jan Ainali Date: Tue, 14 Apr 2020 11:54:40 +0200 Subject: [PATCH 14/54] replace hackmd links with file names --- questions-nl.md | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/questions-nl.md b/questions-nl.md index c58925c..6bdfe63 100644 --- a/questions-nl.md +++ b/questions-nl.md @@ -1,6 +1,6 @@ # Onze voorstellen en vragen -
Home | Inleiding | Onze voorstellen en vragen | Reageren op de marktconsultatie
+
Home | Inleiding | Onze voorstellen en vragen | Reageren op de marktconsultatie
Deze pagina bevat drie onderdelen. @@ -162,21 +162,21 @@ Om de community effectief te laten schalen, gaan we ervan uit dat er een set neu 2. Wat voor invloed wilt u hebben op dit materiaal en de website? 3. Moeten leveranciers contractueel worden gevraagd om, wat ze hebben geleerd bij het implementeren en ondersteunen van OpenZaak, toe te voegen aan het OpenZaak marketingmateriaal (inclusief bijvoorbeeld user testimonials, business cases, etc)? -
Home | Inleiding | Onze voorstellen en vragen | Reageren op de marktconsultatie
+
Home | Inleiding | Onze voorstellen en vragen | Reageren op de marktconsultatie
\ No newline at end of file + From 446b2fda3854aa4e6bbe4ee4c87c78e6525d79b3 Mon Sep 17 00:00:00 2001 From: Jan Ainali Date: Tue, 14 Apr 2020 11:58:50 +0200 Subject: [PATCH 15/54] inlineing CSS --- how-to-respond-en.md | 23 ++++------------------- 1 file changed, 4 insertions(+), 19 deletions(-) diff --git a/how-to-respond-en.md b/how-to-respond-en.md index 0484edc..8ba380c 100644 --- a/how-to-respond-en.md +++ b/how-to-respond-en.md @@ -1,4 +1,5 @@ -
Home | Introduction | Our proposals and questions | How to respond
+ # How to respond @@ -38,21 +39,5 @@ We will produce an anonymized report after interested parties have answered the This document is for market consultation purposes only. It is made available on the express condition that it will only be used to provide suggestions and ideas. Participation in this market consultation cannot lead to obligations on the part of the participating market parties to enter into agreements with the participating municipalities or Dimpact, and vice versa. Market consultation participation does not entail any reimbursement of costs. -
Home | Introduction | Our proposals and questions | How to respond
- - + From 1e7b36ed89a808f7371c5ecfa4c5bb55f706ff5e Mon Sep 17 00:00:00 2001 From: ElenaFdR Date: Tue, 14 Apr 2020 12:00:33 +0200 Subject: [PATCH 16/54] proofreading --- how-to-respond-en.md | 4 +-- questions-en.md | 60 ++++++++++++++++++++++---------------------- 2 files changed, 32 insertions(+), 32 deletions(-) diff --git a/how-to-respond-en.md b/how-to-respond-en.md index df41d19..96dc6ac 100644 --- a/how-to-respond-en.md +++ b/how-to-respond-en.md @@ -19,7 +19,7 @@ The market consultation consists of two parts: 1. A written response to our questions. We're deliberately not restricting the form and length of your answers. These responses should be received by 1-5-2020 before 17:00. You can send your answers to niels.lindeboom@dimpact.nl. Based on your responses we will review our proposal and adjust it if there are good suggestions. This modified proposal will then become the starting point for the workshop (part two of the consultation). 2. Optional: one or more workshops where together we will determine the various needs and prerequisites within the community (participation only on request of OpenZaak). After submitting your answers, you will receive a message no later than 13-5-2020 if you are invited for the workshop. This will take place on 20th and 21st of May 2020. With the invitation you will receive further information about the exact time and location. -Dimpact is responsible for the communication about this market consultation. You can contact Niels Lindeboom at niels.lindeboom@dimpact.nl or 06-22270923. +Dimpact is responsible for the communication about this market consultation. You can contact Niels Lindeboom at or 06-22270923. ## Market consultation report @@ -27,7 +27,7 @@ We will produce an anonymized report after interested parties have answered the ## Planning -| Description | Datum | +| Description | Date | |-------------|-------| | Market consultation publication | 14-4-2020 | | Submission deadline | 1-5-2020, 17:00 | diff --git a/questions-en.md b/questions-en.md index d627f6d..27ed8a2 100644 --- a/questions-en.md +++ b/questions-en.md @@ -9,9 +9,9 @@ URL: Open-Zaak/market-consultation/questions-en.md This page contains three sections: -- Vision for an open source community - a draft vision for what the OpenZaak community could look like -- Needs of municipalities - an indicative overview of kinds of support the municipalities need from vendors -- Market consultation questions - an overview of our open questions to market parties +* Vision for an open source community - a draft vision for what the OpenZaak community could look like +* Needs of municipalities - an indicative overview of kinds of support the municipalities need from vendors +* Market consultation questions - an overview of our open questions to market parties ## Vision for an open source community @@ -23,11 +23,11 @@ For vendors it is important to grow the number of replicating municipalities (in Without knowing all the answers in detail, our vision for this community includes: -- collaborating on a single, vendor-neutral codebase and shared branching model, avoiding diverging forks -- collaborative governance, including around shared roadmaps (feature and technical) and open issue tracker -- a shared understanding of how to approach bug fixes and support, particularly in situations of operational downtime or security risks -- an inclusive community (including open communication channels, codebase marketing material and codes of conduct) that is welcoming to new market parties and new replicating municipalities -- empowering vendors to become effective members and ambassadors of the community +* collaborating on a single, vendor-neutral codebase and shared branching model, avoiding diverging forks +* collaborative governance, including around shared roadmaps (feature and technical) and open issue tracker +* a shared understanding of how to approach bug fixes and support, particularly in situations of operational downtime or security risks +* an inclusive community (including open communication channels, codebase marketing material and codes of conduct) that is welcoming to new market parties and new replicating municipalities +* empowering vendors to become effective members and ambassadors of the community ## Needs of municipalities @@ -37,13 +37,13 @@ The lists below set out needs all municipalities will have, as well as three ‘ ### Needs all municipalities have -- Need connection with external databases/sets (i.e. basisgegevens) -- Need to retain ownership of data, and continuous access to the data -- Need easy data portability (for example for legally required archiving) -- Need vendors who contribute to the OpenZaak main repository (including [EUPL license](https://github.com/open-zaak/open-zaak/blob/master/LICENSE.md)) -- Need to remain in sync with the [VNG standards](https://www.vngrealisatie.nl/producten/api-standaarden-zaakgericht-werken) -- Need to influence the feature roadmap -- Need vendors to use OpenZaak in all products and services that create or use case management data +* Need connection with external databases/sets (i.e. basisgegevens) +* Need to retain ownership of data, and continuous access to the data +* Need easy data portability (for example for legally required archiving) +* Need vendors who contribute to the OpenZaak main repository (including [EUPL license](https://github.com/open-zaak/open-zaak/blob/master/LICENSE.md)) +* Need to remain in sync with the [VNG standards](https://www.vngrealisatie.nl/producten/api-standaarden-zaakgericht-werken) +* Need to influence the feature roadmap +* Need vendors to use OpenZaak in all products and services that create or use case management data ### ‘Full service’ package needs @@ -51,13 +51,13 @@ Some municipalities need a full service package. This includes hosting, implemen They need market parties to offer: -- hosting support -- implementation support -- maintenance support -- new feature and bug fix support -- integration support -- a helpdesk, configuration support, questions and training -- a way to file bug fixes and deploy hotfixes +* hosting support +* implementation support +* maintenance support +* new feature and bug fix support +* integration support +* a helpdesk, configuration support, questions and training +* a way to file bug fixes and deploy hotfixes ### ‘Backend as a service’ needs @@ -65,11 +65,11 @@ Some municipalities need ‘Backend as a service’. They are able to run other They need market parties to offer: -- an integration partner -- clear continuous integration/continuous development -- a sandbox environment -- a way to file bug fixes and deploy hotfixes -- a helpdesk, configuration support, questions and training +* an integration partner +* clear continuous integration/continuous development +* a sandbox environment +* a way to file bug fixes and deploy hotfixes +* a helpdesk, configuration support, questions and training ### In-house implementation needs @@ -77,9 +77,9 @@ Some municipalities will want to implement the component with exclusively in-hou They need the community to have: -- clear development/contribution guidelines -- a way to liaise with vendors and other municipalities regarding product and technical roadmap and backlogs -- a way to fix bugs together with vendors and other municipalities +* clear development/contribution guidelines +* a way to liaise with vendors and other municipalities regarding product and technical roadmap and backlogs +* a way to fix bugs together with vendors and other municipalities ## Market consultation questions From 4cee8c708abb5a0658b3ab6e9978ae5071234340 Mon Sep 17 00:00:00 2001 From: ElenaFdR Date: Tue, 14 Apr 2020 12:04:20 +0200 Subject: [PATCH 17/54] proofing --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index e50803c..cce713e 100644 --- a/README.md +++ b/README.md @@ -8,17 +8,17 @@ Het doel van deze marktconsultatie is om marktpartijen uit te nodigen bij het opzetten van de OpenZaak-community. Dit omvat het mede creëren van codebase-governance, de gemeenschapsdynamiek en de product marketing rondom OpenZaak, op een manier die u in staat stelt een duurzaam bedrijfsmodel na te streven. -Hieronder vindt u een inleiding, een reeks voorstellen en vragen, een voorstel voor governance.md, en **informatie over hoe u op deze consultatie kunt reageren. Deze reacties dienen uiterlijk op 1-5-2020 vóór 17:00 uur ontvangen te zijn.** +Hieronder vindt u een inleiding, een reeks voorstellen en vragen, een voorstel voor governance.md, en informatie over hoe u op deze consultatie kunt reageren. **Deze reacties dienen uiterlijk op 1-5-2020 vóór 17:00 uur ontvangen te zijn.** -Als je vragen hebt over deze consultatie, aarzel dan niet om [een issue aan te maken](https://github.com/open-zaak/openzaak-market-consultation/issues/new/choose) of e-mail Niels Lindeboom op niels.lindeboom@dimpact.nl. +Als je vragen hebt over deze consultatie, aarzel dan niet om [een issue aan te maken](https://github.com/open-zaak/openzaak-market-consultation/issues/new/choose) of e-mail Niels Lindeboom op . ## English The goal of this market consultation is to invite market parties to help set up the OpenZaak community. This includes co-creating codebase governance, community dynamics, and the product marketing around OpenZaak in a way that allows you to pursue a sustainable business model. -Below you can find an introductory cover letter, a set of proposals and questions, a draft governance.md, and **how to respond to this consultation. The responses should be received by 1-5-2020 before 17:00.** +Below you can find an introductory cover letter, a set of proposals and questions, a draft governance.md, and how to respond to this consultation. **Responses should be received by 1-5-2020 before 17:00.** -If you have any questions about this consultation, please feel free to [create an issue](https://github.com/open-zaak/openzaak-market-consultation/issues/new/choose) or email Niels Lindeboom at niels.lindeboom@dimpact.nl. +If you have any questions about this consultation, please feel free to [create an issue](https://github.com/open-zaak/openzaak-market-consultation/issues/new/choose) or email Niels Lindeboom at . ## Consultation contents / Consultatie inhoud From 030c4fa55268efd5a9cc524629eff0afe9e0030b Mon Sep 17 00:00:00 2001 From: Jan Ainali Date: Tue, 14 Apr 2020 12:04:33 +0200 Subject: [PATCH 18/54] change div to table --- how-to-respond-nl.md | 23 ++++------------------- 1 file changed, 4 insertions(+), 19 deletions(-) diff --git a/how-to-respond-nl.md b/how-to-respond-nl.md index 5d2b8ac..d4e1cd6 100644 --- a/how-to-respond-nl.md +++ b/how-to-respond-nl.md @@ -1,4 +1,5 @@ -
Home | Inleiding | Onze voorstellen en vragen | Reageren op de marktconsultatie
+| Home | Inleiding | Onze voorstellen en vragen | Reageren op de marktconsultatie | +| -------- | -------- | -------- | -------- | -------- | # Hoe te reageren @@ -38,21 +39,5 @@ Nadat de geïnteresseerde partijen de vragen uit het marktconsultatiedocument he Dit document is alleen bestemd voor marktconsultatie doeleinden. Het wordt ter beschikking gesteld onder de uitdrukkelijke voorwaarde dat het uitsluitend gebruikt wordt om suggesties en ideeën aan te reiken. Een deelname aan deze marktconsultatie kan niet leiden tot verplichtingen van de deelnemende marktpartijen om overeenkomsten met de deelnemende gemeenten of Dimpact aan te gaan, en vice versa. Aan de deelname van de marktconsultatie is geen vergoeding van kosten verbonden. -
Home | Inleiding | Onze voorstellen en vragen | Reageren op de marktconsultatie
- - +| Home | Inleiding | Onze voorstellen en vragen | Reageren op de marktconsultatie | +| -------- | -------- | -------- | -------- | -------- | From 9185c91e66264a1163f42e8f3603fe84d1bff4ee Mon Sep 17 00:00:00 2001 From: Jan Ainali Date: Tue, 14 Apr 2020 12:05:52 +0200 Subject: [PATCH 19/54] linebreaks --- how-to-respond-nl.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/how-to-respond-nl.md b/how-to-respond-nl.md index d4e1cd6..1c1bde1 100644 --- a/how-to-respond-nl.md +++ b/how-to-respond-nl.md @@ -1,4 +1,4 @@ -| Home | Inleiding | Onze voorstellen en vragen | Reageren op de marktconsultatie | +| Home | Inleiding | Onze voorstellen en vragen | Reageren op de marktconsultatie | | -------- | -------- | -------- | -------- | -------- | # Hoe te reageren @@ -39,5 +39,5 @@ Nadat de geïnteresseerde partijen de vragen uit het marktconsultatiedocument he Dit document is alleen bestemd voor marktconsultatie doeleinden. Het wordt ter beschikking gesteld onder de uitdrukkelijke voorwaarde dat het uitsluitend gebruikt wordt om suggesties en ideeën aan te reiken. Een deelname aan deze marktconsultatie kan niet leiden tot verplichtingen van de deelnemende marktpartijen om overeenkomsten met de deelnemende gemeenten of Dimpact aan te gaan, en vice versa. Aan de deelname van de marktconsultatie is geen vergoeding van kosten verbonden. -| Home | Inleiding | Onze voorstellen en vragen | Reageren op de marktconsultatie | +| Home | Inleiding | Onze voorstellen en vragen | Reageren op de marktconsultatie | | -------- | -------- | -------- | -------- | -------- | From 214c30a5f9762e221c3832c5c8e234b718265356 Mon Sep 17 00:00:00 2001 From: Jan Ainali Date: Tue, 14 Apr 2020 12:07:35 +0200 Subject: [PATCH 20/54] - one column --- how-to-respond-nl.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/how-to-respond-nl.md b/how-to-respond-nl.md index 1c1bde1..57b8273 100644 --- a/how-to-respond-nl.md +++ b/how-to-respond-nl.md @@ -1,5 +1,5 @@ | Home | Inleiding | Onze voorstellen en vragen | Reageren op de marktconsultatie | -| -------- | -------- | -------- | -------- | -------- | +| -------- | -------- | -------- | -------- | # Hoe te reageren @@ -40,4 +40,4 @@ Nadat de geïnteresseerde partijen de vragen uit het marktconsultatiedocument he Dit document is alleen bestemd voor marktconsultatie doeleinden. Het wordt ter beschikking gesteld onder de uitdrukkelijke voorwaarde dat het uitsluitend gebruikt wordt om suggesties en ideeën aan te reiken. Een deelname aan deze marktconsultatie kan niet leiden tot verplichtingen van de deelnemende marktpartijen om overeenkomsten met de deelnemende gemeenten of Dimpact aan te gaan, en vice versa. Aan de deelname van de marktconsultatie is geen vergoeding van kosten verbonden. | Home | Inleiding | Onze voorstellen en vragen | Reageren op de marktconsultatie | -| -------- | -------- | -------- | -------- | -------- | +| -------- | -------- | -------- | -------- | From 70862f32c6281c2a9f6302ec9276523609e7460c Mon Sep 17 00:00:00 2001 From: Jan Ainali Date: Tue, 14 Apr 2020 12:10:13 +0200 Subject: [PATCH 21/54] change div to table --- how-to-respond-en.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/how-to-respond-en.md b/how-to-respond-en.md index d06128a..f335298 100644 --- a/how-to-respond-en.md +++ b/how-to-respond-en.md @@ -1,5 +1,5 @@ - +| Home | Introduction | Our proposals and questions | How to respond | +| -------- | -------- | -------- | -------- | # How to respond @@ -39,5 +39,5 @@ We will produce an anonymized report after interested parties have answered the This document is for market consultation purposes only. It is made available on the express condition that it will only be used to provide suggestions and ideas. Participation in this market consultation cannot lead to obligations on the part of the participating market parties to enter into agreements with the participating municipalities or Dimpact, and vice versa. Market consultation participation does not entail any reimbursement of costs. - +| Home | Introduction | Our proposals and questions | How to respond | +| -------- | -------- | -------- | -------- | From 8ffe36e022274cbe29a06e93e6193f07ac24145b Mon Sep 17 00:00:00 2001 From: Jan Ainali Date: Tue, 14 Apr 2020 12:10:59 +0200 Subject: [PATCH 22/54] change css to table --- questions-en.md | 23 ++++------------------- 1 file changed, 4 insertions(+), 19 deletions(-) diff --git a/questions-en.md b/questions-en.md index 15fda58..67d1885 100644 --- a/questions-en.md +++ b/questions-en.md @@ -1,6 +1,7 @@ # Our proposals and questions -
Home | Introduction | Our proposals and questions | How to respond
+| Home | Introduction | Our proposals and questions | How to respond | +| -------- | -------- | -------- | -------- | This page contains three sections: @@ -162,21 +163,5 @@ For the community to scale effectively, we assume there should be a set of neutr 2. What kind of influence would you like over this material and the website? 3. Should vendors be asked as part of their contracts to contribute what they’ve learned from implementing and supporting OpenZaak to the OpenZaak marketing material (including for example user testimonials, business cases, etc)? -
Home | Introduction | Our proposals and questions | How to respond
- - +| Home | Introduction | Our proposals and questions | How to respond | +| -------- | -------- | -------- | -------- | From b0e57078e42e52c6ff51c15a8f2364657c50ce30 Mon Sep 17 00:00:00 2001 From: Jan Ainali Date: Tue, 14 Apr 2020 12:11:41 +0200 Subject: [PATCH 23/54] change css to table --- questions-nl.md | 23 ++++------------------- 1 file changed, 4 insertions(+), 19 deletions(-) diff --git a/questions-nl.md b/questions-nl.md index 6bdfe63..7582df0 100644 --- a/questions-nl.md +++ b/questions-nl.md @@ -1,6 +1,7 @@ # Onze voorstellen en vragen -
Home | Inleiding | Onze voorstellen en vragen | Reageren op de marktconsultatie
+| Home | Inleiding | Onze voorstellen en vragen | Reageren op de marktconsultatie | +| -------- | -------- | -------- | -------- | Deze pagina bevat drie onderdelen. @@ -162,21 +163,5 @@ Om de community effectief te laten schalen, gaan we ervan uit dat er een set neu 2. Wat voor invloed wilt u hebben op dit materiaal en de website? 3. Moeten leveranciers contractueel worden gevraagd om, wat ze hebben geleerd bij het implementeren en ondersteunen van OpenZaak, toe te voegen aan het OpenZaak marketingmateriaal (inclusief bijvoorbeeld user testimonials, business cases, etc)? -
Home | Inleiding | Onze voorstellen en vragen | Reageren op de marktconsultatie
- - +| Home | Inleiding | Onze voorstellen en vragen | Reageren op de marktconsultatie | +| -------- | -------- | -------- | -------- | From a064370d04395943821d21ceb5d148b5106379fc Mon Sep 17 00:00:00 2001 From: Jan Ainali Date: Tue, 14 Apr 2020 12:15:10 +0200 Subject: [PATCH 24/54] change css to table --- introduction-en.md | 23 ++++------------------- 1 file changed, 4 insertions(+), 19 deletions(-) diff --git a/introduction-en.md b/introduction-en.md index 96b97a4..25ed64f 100644 --- a/introduction-en.md +++ b/introduction-en.md @@ -1,6 +1,7 @@ # Introduction: Open invitation for market parties to join the OpenZaak community -
Home | Introduction | Our proposals and questions | How to respond
+| Home | Introduction | Our proposals and questions | How to respond | +| -------- | -------- | -------- | -------- | OpenZaak is an open source codebase commissioned by a coalition representing over 45 municipalities including Amsterdam, Arnhem, Delft, Haarlem, ’s-Hertogenbosch, Rotterdam, Tilburg, Hoorn, Medemblik, Utrecht, SED (composed of Stede Broec, Enkhuizen and Drechterland) and Dimpact (composed of more than 30 municipalities). @@ -26,21 +27,5 @@ Answers must be received by Niels Lindeboom before 1-5-2020. Based on these answ This market consultation is being run by [Dimpact](https://www.dimpact.nl/), on behalf of the OpenZaak municipalities, supported by the [Foundation for Public Code](https://publiccode.net/). -
Home | Introduction | Our proposals and questions | How to respond
- - +| Home | Introduction | Our proposals and questions | How to respond | +| -------- | -------- | -------- | -------- | From ae4f57928664341578918b2e381c6a579ed4efda Mon Sep 17 00:00:00 2001 From: Jan Ainali Date: Tue, 14 Apr 2020 13:12:23 +0200 Subject: [PATCH 25/54] fixing question link --- how-to-respond-en.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/how-to-respond-en.md b/how-to-respond-en.md index f335298..cfe840e 100644 --- a/how-to-respond-en.md +++ b/how-to-respond-en.md @@ -1,4 +1,4 @@ -| Home | Introduction | Our proposals and questions | How to respond | +| Home | Introduction | Our proposals and questions | How to respond | | -------- | -------- | -------- | -------- | # How to respond @@ -39,5 +39,5 @@ We will produce an anonymized report after interested parties have answered the This document is for market consultation purposes only. It is made available on the express condition that it will only be used to provide suggestions and ideas. Participation in this market consultation cannot lead to obligations on the part of the participating market parties to enter into agreements with the participating municipalities or Dimpact, and vice versa. Market consultation participation does not entail any reimbursement of costs. -| Home | Introduction | Our proposals and questions | How to respond | +| Home | Introduction | Our proposals and questions | How to respond | | -------- | -------- | -------- | -------- | From f819b2c52158af7ab05f439419e3e8d3a5a23d78 Mon Sep 17 00:00:00 2001 From: Jan Ainali Date: Tue, 14 Apr 2020 13:13:47 +0200 Subject: [PATCH 26/54] change hackmd links to file names --- introduction-en.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/introduction-en.md b/introduction-en.md index 25ed64f..862a6ce 100644 --- a/introduction-en.md +++ b/introduction-en.md @@ -1,6 +1,6 @@ # Introduction: Open invitation for market parties to join the OpenZaak community -| Home | Introduction | Our proposals and questions | How to respond | +| Home | Introduction | Our proposals and questions | How to respond | | -------- | -------- | -------- | -------- | OpenZaak is an open source codebase commissioned by a coalition representing over 45 municipalities including Amsterdam, Arnhem, Delft, Haarlem, ’s-Hertogenbosch, Rotterdam, Tilburg, Hoorn, Medemblik, Utrecht, SED (composed of Stede Broec, Enkhuizen and Drechterland) and Dimpact (composed of more than 30 municipalities). @@ -27,5 +27,5 @@ Answers must be received by Niels Lindeboom before 1-5-2020. Based on these answ This market consultation is being run by [Dimpact](https://www.dimpact.nl/), on behalf of the OpenZaak municipalities, supported by the [Foundation for Public Code](https://publiccode.net/). -| Home | Introduction | Our proposals and questions | How to respond | +| Home | Introduction | Our proposals and questions | How to respond | | -------- | -------- | -------- | -------- | From e8103b9375d4daf1e52a147a20c818aa9a65cf66 Mon Sep 17 00:00:00 2001 From: Jan Ainali Date: Tue, 14 Apr 2020 13:15:08 +0200 Subject: [PATCH 27/54] change css to table --- introduction-nl.md | 23 ++++------------------- 1 file changed, 4 insertions(+), 19 deletions(-) diff --git a/introduction-nl.md b/introduction-nl.md index 6541256..e574af4 100644 --- a/introduction-nl.md +++ b/introduction-nl.md @@ -1,6 +1,7 @@ # Inleiding: Open uitnodiging voor marktpartijen om lid te worden van de OpenZaak community -
Home | Inleiding | Onze voorstellen en vragen | Reageren op de marktconsultatie
+| Home | Inleiding | Onze voorstellen en vragen | Reageren op de marktconsultatie | +| -------- | -------- | -------- | -------- | OpenZaak is een open source codebase gebouwd in opdracht van een coalitie van meer dan 45 gemeenten waaronder Amsterdam, Arnhem, Delft, Haarlem, 's-Hertogenbosch, Rotterdam, Tilburg, Hoorn, Medemblik, Utrecht, SED (bestaande uit Stede Broec, Enkhuizen en Drechterland) en Dimpact (bestaande uit meer dan 30 gemeenten). @@ -26,21 +27,5 @@ De antwoorden moeten voor 1-5-2020 worden ontvangen door Niels Lindeboom. Op bas Deze marktconsultatie wordt georganiseerd door [Dimpact](https://www.dimpact.nl/), in opdracht van de OpenZaak gemeenten, ondersteund door de [Foundation for Public Code](https://publiccode.net/). -
Home | Inleiding | Onze voorstellen en vragen | Reageren op de marktconsultatie
- - +| Home | Inleiding | Onze voorstellen en vragen | Reageren op de marktconsultatie | +| -------- | -------- | -------- | -------- | From a523a648f883860acded2cbd6d10ebfb842607c5 Mon Sep 17 00:00:00 2001 From: Jan Ainali Date: Tue, 14 Apr 2020 14:32:32 +0200 Subject: [PATCH 28/54] change hackmd links to file names --- introduction-nl.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/introduction-nl.md b/introduction-nl.md index e574af4..9461f54 100644 --- a/introduction-nl.md +++ b/introduction-nl.md @@ -17,13 +17,13 @@ De OpenZaak codebase helpt Nederlandse gemeenten om te voldoen aan de [VNG-stand De deelnemende gemeenten zijn op zoek naar geïnteresseerde leveranciers om hen te ondersteunen bij de implementatie van de codebase (onder meer in de ontwikkeling, onderhoud, implementatie en ondersteuning). De ambitie is om een gezonde open source community te hebben waarin leveranciers de mogelijkheid krijgen om de markt voor OpenZaak te laten groeien, en waarin inkoop wordt vereenvoudigd en gestandaardiseerd. -Hiervoor vinden we het belangrijk om een open en collaboratieve gemeenschap te hebben, inclusief één codebase met een gemeenschappelijke governancestructuur en een gedeeld begrip over bugfixes en -ondersteuning. Meer informatie over de behoeften, conceptvisie en open vragen van de gemeenten is te vinden in [onze voorstellen en vragen](https://hackmd.io/OFGiBKmLSh6ug7Gpv3Hbzw) en het [draft governance.md document](governance.md). +Hiervoor vinden we het belangrijk om een open en collaboratieve gemeenschap te hebben, inclusief één codebase met een gemeenschappelijke governancestructuur en een gedeeld begrip over bugfixes en -ondersteuning. Meer informatie over de behoeften, conceptvisie en open vragen van de gemeenten is te vinden in [onze voorstellen en vragen](questions-nl.md) en het [draft governance.md document](governance.md). ## Over deze marktconsultatie -Marktpartijen die geïnteresseerd zijn in deelname worden gevraagd [onze voorstellen en vragen](https://hackmd.io/OFGiBKmLSh6ug7Gpv3Hbzw?both) zorgvuldig te herzien en te reageren op de daar genoemde vragen. +Marktpartijen die geïnteresseerd zijn in deelname worden gevraagd [onze voorstellen en vragen](questions-nl.md) zorgvuldig te herzien en te reageren op de daar genoemde vragen. -De antwoorden moeten voor 1-5-2020 worden ontvangen door Niels Lindeboom. Op basis van deze antwoorden kunnen marktpartijen samen met de gemeenten worden uitgenodigd voor één of meerdere workshops om te bepalen hoe de OpenZaak-gemeenschap kan worden opgezet. Meer informatie over dit marktraadplegingsproces is te vinden in [hoe te reageren](https://hackmd.io/NT4ywg6bSReSgsocu1HFXw?both). +De antwoorden moeten voor 1-5-2020 worden ontvangen door Niels Lindeboom. Op basis van deze antwoorden kunnen marktpartijen samen met de gemeenten worden uitgenodigd voor één of meerdere workshops om te bepalen hoe de OpenZaak-gemeenschap kan worden opgezet. Meer informatie over dit marktraadplegingsproces is te vinden in [hoe te reageren](how-to-respond-nl.md). Deze marktconsultatie wordt georganiseerd door [Dimpact](https://www.dimpact.nl/), in opdracht van de OpenZaak gemeenten, ondersteund door de [Foundation for Public Code](https://publiccode.net/). From 704bb44062984f2b9abc26682de4d527b660d1a5 Mon Sep 17 00:00:00 2001 From: Jan Ainali Date: Tue, 14 Apr 2020 14:33:47 +0200 Subject: [PATCH 29/54] change hackmd links to file names --- introduction-en.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/introduction-en.md b/introduction-en.md index 862a6ce..5125e2f 100644 --- a/introduction-en.md +++ b/introduction-en.md @@ -17,13 +17,13 @@ The OpenZaak codebase helps Dutch municipalities comply with the [VNG standard f The participating municipalities are now looking for interested vendors to support them in implementing the codebase (including in the development, maintenance, implementation and support). The ambition is to have a healthy open source community in which vendors are empowered to grow the market for OpenZaak, and procurement is simplified and standardized. -For this, we believe it is important to have an open and collaborative community, including a single codebase with a common governance structure and a shared understanding on bug fixes and support. More information on the municipalities’ needs, draft vision, and open questions can be found in [our proposals and questions](https://hackmd.io/XJ0rLW4pQXCJjZIw9A7ArQ) and the [draft governance document](governance.md). +For this, we believe it is important to have an open and collaborative community, including a single codebase with a common governance structure and a shared understanding on bug fixes and support. More information on the municipalities’ needs, draft vision, and open questions can be found in [our proposals and questions](questions-en.md) and the [draft governance document](governance.md). ## About this market consultation -Market parties interested in participating are asked to carefully [review our proposals](https://hackmd.io/XJ0rLW4pQXCJjZIw9A7ArQ) and respond to the questions listed there. +Market parties interested in participating are asked to carefully [review our proposals](questions-en.md) and respond to the questions listed there. -Answers must be received by Niels Lindeboom before 1-5-2020. Based on these answers, market parties may be invited to one or several workshops together with the municipalities to define how to set up the OpenZaak community. More information about this market consultation process can be found in [how to respond](https://hackmd.io/AQOmgrpSQIeMVC4OhFxKDA). +Answers must be received by Niels Lindeboom before 1-5-2020. Based on these answers, market parties may be invited to one or several workshops together with the municipalities to define how to set up the OpenZaak community. More information about this market consultation process can be found in [how to respond](how-to-respond-en.md). This market consultation is being run by [Dimpact](https://www.dimpact.nl/), on behalf of the OpenZaak municipalities, supported by the [Foundation for Public Code](https://publiccode.net/). From 42e06d7fb33ee559aaa26700b0e0c1cc580ea3cc Mon Sep 17 00:00:00 2001 From: Jan Ainali Date: Tue, 14 Apr 2020 14:55:10 +0200 Subject: [PATCH 30/54] Create GOVERNANCE.md --- GOVERNANCE.md | 92 +++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 92 insertions(+) create mode 100644 GOVERNANCE.md diff --git a/GOVERNANCE.md b/GOVERNANCE.md new file mode 100644 index 0000000..dba4d89 --- /dev/null +++ b/GOVERNANCE.md @@ -0,0 +1,92 @@ + +# DRAFT: OpenZaak codebase goverance + +## Introduction + +This document contains a draft proposal for the 'governance.md' file on the OpenZaak repository. + +## Principles + +As a community we want make it easier for new users to become contributors and maintainers. + +The OpenZaak community adheres to the following principles: + +* OpenZaak is open source. +* We're a welcoming and respectful community as mentioned in our [Code of Conduct](#Code-of-Conduct). +* Transparent and accessible, changes to the OpenZaak organization, OpenZaak code repositories, and OpenZaak related activities (e.g. level, involvement, etc) are done in public. +* Ideas and contributions are accepted according to their technical merit and alignment with project objectives, scope, and design principles. + +The maintainers of OpenZaak have two steering teams, a technical one and a product one. + +Through codebase stewardship the Foundation for Public Code supports the governance of OpenZaak, the product and technical steering teams, and its community. + +## Technical steering team + +The OpenZaak technical steering team members are active contributors who are on a day-to-day basis responsible for: + +* Merging pull requests +* Handling code of conduct violations +* Overseeing the resolution and disclosure of security issues + +If technical steering team members cannot reach consensus informally, the question at hand should be forwarded to the technical steering team meeting. + +Any active member of the community can request to become a technical steering team member by asking the technical steering team. The technical steering team will vote on it (simple majority). + +The current team members are: + +* + +The technical steering team has the joint responsibility to: + +* Provide technical direction for the codebase +* Maintain a technical roadmap, an architecure and coding principles +* Resolve issues in development or conflicts between contributors +* Managing and planning releases +* Controlling rights to Open Zaak assets such as source repositories + +The technical steering team meets regularly. Their agenda includes reivew of the technical roadmap and issues that are at an impasse. The intention of the agenda is not to review or approve all patches. This is mainly being done through the process described in the contributing guide. + +If more than one technical steering team member disagrees with a decision of the technical steering team they may appeal to the product steering team who will make the ultimate ruling. + +Ideally, no one company or organization will employ a simple majority of the technical steering team. + +## Product steering team + +Responsibilities of the product steering team: + +* Maintaining the mission, vision, values, and scope of the project +* Collecting planned features and presenting them in a unified view +* Refining the governance as needed +* Making codebase level decisions +* Resolving escalated project decisions when the subteam responsible is blocked +* Managing the OpenZaak brand +* Licensing and intellectual property changes +* Controlling access to OpenZaak assets such as hosting and project calendars + +Members are appointed by the current product steering team members. + +Changes in codebase governance can only be done by the product steering team and requires super majority. + +The current team members are: + +* + +## Decision making process + +The default decision making process is lazy-consensus. This means that any decision is considered supported by the team making it as long as no one objects. Silence on any consensus decision is implicit agreement and equivalent to explicit agreement. Explicit agreement may be stated at will. + +When a consensus cannot be found a team member can call for a majority vote on a decision. Every team member has 1 vote. + +Many of the day-to-day project maintenance tasks can be done by a lazy consensus model. But the following items must be called to vote: + +* Adding a team member (simple majority) +* Removing a team member (super majority) +* Changing the governance rules (this document) (super majority) +* Licensing and intellectual property changes (including new logos, wordmarks) (simple majority) +* Adding, archiving, or removing subprojects (simple majority) + +## Code of Conduct + +OpenZaak's Code of Conduct is explained in [this project's code of conduct](https://hackmd.io/I9xVIG33THuBSFmg1zlkQA). + +If the possible violation involves a team member that member will be recused from voting on the issue. Such issues must be escalated to the product steering team contact, and the product steering team may choose to intervene. From a2f318b89b11ef472c3ad71d859e0f9a659629e8 Mon Sep 17 00:00:00 2001 From: Jan Ainali Date: Tue, 14 Apr 2020 14:57:30 +0200 Subject: [PATCH 31/54] Create CODE OF CONDUCT.md --- CODE OF CONDUCT.md | 36 ++++++++++++++++++++++++++++++++++++ 1 file changed, 36 insertions(+) create mode 100644 CODE OF CONDUCT.md diff --git a/CODE OF CONDUCT.md b/CODE OF CONDUCT.md new file mode 100644 index 0000000..56417de --- /dev/null +++ b/CODE OF CONDUCT.md @@ -0,0 +1,36 @@ +# DRAFT: OpenZaak Code of Conduct + +## Our Pledge + +In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to make participation in our project and our community a positive experience for everyone, regardless of who you are or on whose behalf you are making contributions. + +## Our Standards + +Examples of behavior that contributes to creating a positive environment +include: + +* Using welcoming and inclusive language +* Being respectful of differing viewpoints and experiences +* Gracefully accepting constructive criticism +* Focusing on what is best for the community + +## Our Responsibilities + +OpenZaak maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. + +Technical steering team members have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. + +## Scope + +This Code of Conduct applies within all project spaces, and it also applies when an individual is representing the project or its community in public spaces. Examples of representing a project or community include using an officialproject e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. + +## Enforcement + +Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the technical steering team at [INSERT EMAIL ADDRESS] or by contacting a technical steering team member directly. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The technical steering team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. + +OpenZaak maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the product team's leadership. + +## Attribution + +This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, +available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html From 2d570007c103d3ae6825028064e091a4b8649d2f Mon Sep 17 00:00:00 2001 From: Elena FdR Date: Tue, 14 Apr 2020 15:00:09 +0200 Subject: [PATCH 32/54] Hyperlink to publiccode.net, code-of-conduct.md --- GOVERNANCE.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/GOVERNANCE.md b/GOVERNANCE.md index dba4d89..cce606a 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -1,5 +1,5 @@ -# DRAFT: OpenZaak codebase goverance +# DRAFT: OpenZaak codebase governance ## Introduction @@ -12,13 +12,13 @@ As a community we want make it easier for new users to become contributors and m The OpenZaak community adheres to the following principles: * OpenZaak is open source. -* We're a welcoming and respectful community as mentioned in our [Code of Conduct](#Code-of-Conduct). +* We're a welcoming and respectful community as mentioned in our [Code of Conduct](code-of-conduct.md). * Transparent and accessible, changes to the OpenZaak organization, OpenZaak code repositories, and OpenZaak related activities (e.g. level, involvement, etc) are done in public. * Ideas and contributions are accepted according to their technical merit and alignment with project objectives, scope, and design principles. The maintainers of OpenZaak have two steering teams, a technical one and a product one. -Through codebase stewardship the Foundation for Public Code supports the governance of OpenZaak, the product and technical steering teams, and its community. +Through codebase stewardship the [Foundation for Public Code](https://publiccode.net/) supports the governance of OpenZaak, the product and technical steering teams, and its community. ## Technical steering team @@ -87,6 +87,6 @@ Many of the day-to-day project maintenance tasks can be done by a lazy consensus ## Code of Conduct -OpenZaak's Code of Conduct is explained in [this project's code of conduct](https://hackmd.io/I9xVIG33THuBSFmg1zlkQA). +OpenZaak's Code of Conduct is explained in [this project's code of conduct](code-of-conduct.md). If the possible violation involves a team member that member will be recused from voting on the issue. Such issues must be escalated to the product steering team contact, and the product steering team may choose to intervene. From af94b425b7a63437251df2d30b7b2298a18277c6 Mon Sep 17 00:00:00 2001 From: Jan Ainali Date: Tue, 14 Apr 2020 15:00:35 +0200 Subject: [PATCH 33/54] link fix --- CODE OF CONDUCT.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/CODE OF CONDUCT.md b/CODE OF CONDUCT.md index 56417de..9aacfa9 100644 --- a/CODE OF CONDUCT.md +++ b/CODE OF CONDUCT.md @@ -32,5 +32,4 @@ OpenZaak maintainers who do not follow or enforce the Code of Conduct in good fa ## Attribution -This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, -available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html +This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org/version/1/4/code-of-conduct.html), version 1.4. From b15e5650915e32378f83860e9c63305c4a0a0651 Mon Sep 17 00:00:00 2001 From: Elena FdR Date: Tue, 14 Apr 2020 15:02:05 +0200 Subject: [PATCH 34/54] remove caps --- CODE OF CONDUCT.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/CODE OF CONDUCT.md b/CODE OF CONDUCT.md index 9aacfa9..734a478 100644 --- a/CODE OF CONDUCT.md +++ b/CODE OF CONDUCT.md @@ -1,10 +1,10 @@ # DRAFT: OpenZaak Code of Conduct -## Our Pledge +## Our pledge In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to make participation in our project and our community a positive experience for everyone, regardless of who you are or on whose behalf you are making contributions. -## Our Standards +## Our standards Examples of behavior that contributes to creating a positive environment include: @@ -14,7 +14,7 @@ include: * Gracefully accepting constructive criticism * Focusing on what is best for the community -## Our Responsibilities +## Our responsibilities OpenZaak maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. From b9c4efb1ec64391502c466f257179a67b8606c8e Mon Sep 17 00:00:00 2001 From: Jan Ainali Date: Tue, 14 Apr 2020 15:09:37 +0200 Subject: [PATCH 35/54] Rename CODE OF CONDUCT.md to CODE_OF_CONDUCT.md --- CODE OF CONDUCT.md => CODE_OF_CONDUCT.md | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename CODE OF CONDUCT.md => CODE_OF_CONDUCT.md (100%) diff --git a/CODE OF CONDUCT.md b/CODE_OF_CONDUCT.md similarity index 100% rename from CODE OF CONDUCT.md rename to CODE_OF_CONDUCT.md From 3deb1864c112d1841d35cf4e5ce8f3e4f3d70810 Mon Sep 17 00:00:00 2001 From: Jan Ainali Date: Tue, 14 Apr 2020 15:12:25 +0200 Subject: [PATCH 36/54] Link fix of CODE OF CONDUCT --- GOVERNANCE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/GOVERNANCE.md b/GOVERNANCE.md index cce606a..2befc77 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -87,6 +87,6 @@ Many of the day-to-day project maintenance tasks can be done by a lazy consensus ## Code of Conduct -OpenZaak's Code of Conduct is explained in [this project's code of conduct](code-of-conduct.md). +OpenZaak's Code of Conduct is explained in [this project's code of conduct](CODE_OF_CONDUCT.md). If the possible violation involves a team member that member will be recused from voting on the issue. Such issues must be escalated to the product steering team contact, and the product steering team may choose to intervene. From 5dccaaafe2bed755d0018f0d6f7c84939b7f2154 Mon Sep 17 00:00:00 2001 From: Jan Ainali Date: Tue, 14 Apr 2020 15:14:06 +0200 Subject: [PATCH 37/54] change back to section link --- GOVERNANCE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/GOVERNANCE.md b/GOVERNANCE.md index 2befc77..400b7c6 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -12,7 +12,7 @@ As a community we want make it easier for new users to become contributors and m The OpenZaak community adheres to the following principles: * OpenZaak is open source. -* We're a welcoming and respectful community as mentioned in our [Code of Conduct](code-of-conduct.md). +* We're a welcoming and respectful community as mentioned in our [Code of Conduct](#Code of Conduct). * Transparent and accessible, changes to the OpenZaak organization, OpenZaak code repositories, and OpenZaak related activities (e.g. level, involvement, etc) are done in public. * Ideas and contributions are accepted according to their technical merit and alignment with project objectives, scope, and design principles. From 9836fe3288cc9977840f31231576f36f3f7b2ed6 Mon Sep 17 00:00:00 2001 From: Elena FdR Date: Tue, 14 Apr 2020 15:15:52 +0200 Subject: [PATCH 38/54] change code of conduct jumplink --- GOVERNANCE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/GOVERNANCE.md b/GOVERNANCE.md index 400b7c6..f94b1ac 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -12,7 +12,7 @@ As a community we want make it easier for new users to become contributors and m The OpenZaak community adheres to the following principles: * OpenZaak is open source. -* We're a welcoming and respectful community as mentioned in our [Code of Conduct](#Code of Conduct). +* We're a welcoming and respectful community as mentioned in our [Code of Conduct](#code-of-conduct). * Transparent and accessible, changes to the OpenZaak organization, OpenZaak code repositories, and OpenZaak related activities (e.g. level, involvement, etc) are done in public. * Ideas and contributions are accepted according to their technical merit and alignment with project objectives, scope, and design principles. From 985352238dbccde2b7655a98d57b04c17122a5e3 Mon Sep 17 00:00:00 2001 From: Jan Ainali Date: Tue, 14 Apr 2020 15:17:55 +0200 Subject: [PATCH 39/54] link fix --- GOVERNANCE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/GOVERNANCE.md b/GOVERNANCE.md index f94b1ac..6646de8 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -12,7 +12,7 @@ As a community we want make it easier for new users to become contributors and m The OpenZaak community adheres to the following principles: * OpenZaak is open source. -* We're a welcoming and respectful community as mentioned in our [Code of Conduct](#code-of-conduct). +* We're a welcoming and respectful community as mentioned in our [Code of Conduct](GOVERNANCE.md#Code-of-Conduct). * Transparent and accessible, changes to the OpenZaak organization, OpenZaak code repositories, and OpenZaak related activities (e.g. level, involvement, etc) are done in public. * Ideas and contributions are accepted according to their technical merit and alignment with project objectives, scope, and design principles. From ceb31aedcb21f8e51830f4c7e8e73269d2c0a63a Mon Sep 17 00:00:00 2001 From: Jan Ainali Date: Tue, 14 Apr 2020 16:08:30 +0200 Subject: [PATCH 40/54] move navigation bar to top --- introduction-en.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/introduction-en.md b/introduction-en.md index 5125e2f..7bfbce1 100644 --- a/introduction-en.md +++ b/introduction-en.md @@ -1,8 +1,8 @@ -# Introduction: Open invitation for market parties to join the OpenZaak community - | Home | Introduction | Our proposals and questions | How to respond | | -------- | -------- | -------- | -------- | +# Introduction: Open invitation for market parties to join the OpenZaak community + OpenZaak is an open source codebase commissioned by a coalition representing over 45 municipalities including Amsterdam, Arnhem, Delft, Haarlem, ’s-Hertogenbosch, Rotterdam, Tilburg, Hoorn, Medemblik, Utrecht, SED (composed of Stede Broec, Enkhuizen and Drechterland) and Dimpact (composed of more than 30 municipalities). The first production-ready iteration was completed in February 2020. The OpenZaak community is now looking for market parties to help co-create a vision for what a scalable vendor network and community could look like. OpenZaak has the potential to scale to all Dutch municipalities. From ece75c0f161926b8c2c046de69eb52b2b6e7c8c1 Mon Sep 17 00:00:00 2001 From: Jan Ainali Date: Tue, 14 Apr 2020 16:09:02 +0200 Subject: [PATCH 41/54] move navigation bar to top --- introduction-nl.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/introduction-nl.md b/introduction-nl.md index 9461f54..378436b 100644 --- a/introduction-nl.md +++ b/introduction-nl.md @@ -1,8 +1,8 @@ -# Inleiding: Open uitnodiging voor marktpartijen om lid te worden van de OpenZaak community - | Home | Inleiding | Onze voorstellen en vragen | Reageren op de marktconsultatie | | -------- | -------- | -------- | -------- | - + +# Inleiding: Open uitnodiging voor marktpartijen om lid te worden van de OpenZaak community + OpenZaak is een open source codebase gebouwd in opdracht van een coalitie van meer dan 45 gemeenten waaronder Amsterdam, Arnhem, Delft, Haarlem, 's-Hertogenbosch, Rotterdam, Tilburg, Hoorn, Medemblik, Utrecht, SED (bestaande uit Stede Broec, Enkhuizen en Drechterland) en Dimpact (bestaande uit meer dan 30 gemeenten). De eerste productierijpe iteratie was afgerond in februari 2020. De OpenZaak-community is nu op zoek naar marktpartijen om mee te denken over hoe het schaalbare leveranciersnetwerk en de community eruit zouden kunnen zien. OpenZaak heeft de potentie om op te schalen naar alle Nederlandse gemeenten. From 3868dbe6a17c747170fc3a0eb505947ad5d1a840 Mon Sep 17 00:00:00 2001 From: Jan Ainali Date: Tue, 14 Apr 2020 16:09:30 +0200 Subject: [PATCH 42/54] move navigation bar to top --- questions-en.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/questions-en.md b/questions-en.md index 67d1885..d5639a4 100644 --- a/questions-en.md +++ b/questions-en.md @@ -1,8 +1,8 @@ -# Our proposals and questions - | Home | Introduction | Our proposals and questions | How to respond | | -------- | -------- | -------- | -------- | +# Our proposals and questions + This page contains three sections: * Vision for an open source community - a draft vision for what the OpenZaak community could look like From fd4d957361ac5ba391550f7d38f8e7ab42ef918e Mon Sep 17 00:00:00 2001 From: Jan Ainali Date: Tue, 14 Apr 2020 16:10:14 +0200 Subject: [PATCH 43/54] move navigation bar to top --- questions-nl.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/questions-nl.md b/questions-nl.md index 7582df0..44fdf01 100644 --- a/questions-nl.md +++ b/questions-nl.md @@ -1,8 +1,8 @@ -# Onze voorstellen en vragen - | Home | Inleiding | Onze voorstellen en vragen | Reageren op de marktconsultatie | | -------- | -------- | -------- | -------- | +# Onze voorstellen en vragen + Deze pagina bevat drie onderdelen. 1. Een visie voor een open source community - een conceptvisie voor hoe de OpenZaak community eruit zou kunnen zien. From e942b8dd00b4f4537eb6c95fa3c121c9fc3f605d Mon Sep 17 00:00:00 2001 From: ElenaFdR Date: Wed, 15 Apr 2020 08:54:42 +0200 Subject: [PATCH 44/54] Changes #3 --- GOVERNANCE.md | 4 ++-- questions-en.md | 2 +- questions-nl.md | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/GOVERNANCE.md b/GOVERNANCE.md index 6646de8..08f7341 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -14,7 +14,7 @@ The OpenZaak community adheres to the following principles: * OpenZaak is open source. * We're a welcoming and respectful community as mentioned in our [Code of Conduct](GOVERNANCE.md#Code-of-Conduct). * Transparent and accessible, changes to the OpenZaak organization, OpenZaak code repositories, and OpenZaak related activities (e.g. level, involvement, etc) are done in public. -* Ideas and contributions are accepted according to their technical merit and alignment with project objectives, scope, and design principles. +* Ideas and contributions are accepted according to their technical and functional merit and alignment with project objectives, scope, and design principles. The maintainers of OpenZaak have two steering teams, a technical one and a product one. @@ -44,7 +44,7 @@ The technical steering team has the joint responsibility to: * Managing and planning releases * Controlling rights to Open Zaak assets such as source repositories -The technical steering team meets regularly. Their agenda includes reivew of the technical roadmap and issues that are at an impasse. The intention of the agenda is not to review or approve all patches. This is mainly being done through the process described in the contributing guide. +The technical steering team meets regularly. Their agenda includes review of the technical roadmap and issues that are at an impasse. The intention of the agenda is not to review or approve all patches. This is mainly being done through the process described in the contributing guide. If more than one technical steering team member disagrees with a decision of the technical steering team they may appeal to the product steering team who will make the ultimate ruling. diff --git a/questions-en.md b/questions-en.md index 67d1885..bdfcd24 100644 --- a/questions-en.md +++ b/questions-en.md @@ -131,7 +131,7 @@ There will be a central, public and prioritised issue tracker for features and b #### Assumptions -Many municipalities will prefer to have a single provider they can call for all their needs. This ranges from questions, bugs, ideas for new features, technical integration, training, configuration of permissions/authorisation, notifications, and so forth. Our assumption is that in many cases, no single vendor will want to or be able to provide all these services. +Many municipalities will prefer to have a single provider they can call for all their needs. This ranges from questions, bugs, ideas for new features, technical integration and training to configuration of permissions/authorisation, notifications, and so forth. Our assumption is that in many cases, no single vendor will want to or be able to provide all these services. #### Questions diff --git a/questions-nl.md b/questions-nl.md index 7582df0..9e42773 100644 --- a/questions-nl.md +++ b/questions-nl.md @@ -21,7 +21,7 @@ Zonder alle antwoorden in detail te kennen, omvat onze visie voor de community: * samenwerken aan één leverancier-neutrale codebase en shared branchingmodel, waarbij uiteenlopende forks worden vermeden * collaborative governance, inclusief rond gedeelde roadmaps (feature en technical) en open issue tracker -* een gedeeld inzicht in hoe bugfixes en -ondersteuning kunnen worden aangepakt, met name in situaties van operationele downtime of beveiligingsrisico's +* een gedeeld inzicht in hoe bugfixes en ondersteuning kunnen worden aangepakt, met name in situaties van operationele downtime of beveiligingsrisico's * een inclusieve community (inclusief open communicatiekanalen, codebase marketingmateriaal en codes of conduct) die nieuwe marktpartijen en nieuwe deelnemende gemeenten verwelkomt * leveranciers in staat stellen om effectieve leden en ambassadeurs van de community te worden From 4df6a1ffaaafb1f5cbf3b15707f7bb7fa02a38e5 Mon Sep 17 00:00:00 2001 From: ElenaFdR Date: Wed, 15 Apr 2020 09:25:55 +0200 Subject: [PATCH 45/54] Implementing @hugo-ter-doest edits --- CODE_OF_CONDUCT.md | 2 +- GOVERNANCE.md | 4 ++-- how-to-respond-en.md | 2 +- how-to-respond-nl.md | 6 +++--- introduction-nl.md | 6 +++--- questions-nl.md | 6 +++--- 6 files changed, 13 insertions(+), 13 deletions(-) diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md index 734a478..0609fd5 100644 --- a/CODE_OF_CONDUCT.md +++ b/CODE_OF_CONDUCT.md @@ -22,7 +22,7 @@ Technical steering team members have the right and responsibility to remove, edi ## Scope -This Code of Conduct applies within all project spaces, and it also applies when an individual is representing the project or its community in public spaces. Examples of representing a project or community include using an officialproject e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. +This Code of Conduct applies within all project spaces, and it also applies when an individual is representing the project or its community in public spaces. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. ## Enforcement diff --git a/GOVERNANCE.md b/GOVERNANCE.md index 08f7341..2ee75f7 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -39,7 +39,7 @@ The current team members are: The technical steering team has the joint responsibility to: * Provide technical direction for the codebase -* Maintain a technical roadmap, an architecure and coding principles +* Maintain a technical roadmap, architecture and coding principles * Resolve issues in development or conflicts between contributors * Managing and planning releases * Controlling rights to Open Zaak assets such as source repositories @@ -65,7 +65,7 @@ Responsibilities of the product steering team: Members are appointed by the current product steering team members. -Changes in codebase governance can only be done by the product steering team and requires super majority. +Changes in codebase governance can only be done by the product steering team and requires super majority (2/3). The current team members are: diff --git a/how-to-respond-en.md b/how-to-respond-en.md index cfe840e..bc5941b 100644 --- a/how-to-respond-en.md +++ b/how-to-respond-en.md @@ -17,7 +17,7 @@ We want to use your experience, inspiration and brainpower to come to the right The market consultation consists of two parts: -1. A written response to our questions. We're deliberately not restricting the form and length of your answers. These responses should be received by 1-5-2020 before 17:00. You can send your answers to niels.lindeboom@dimpact.nl. Based on your responses we will review our proposal and adjust it if there are good suggestions. This modified proposal will then become the starting point for the workshop (part two of the consultation). +1. A written response to our questions. We're deliberately not restricting the form and length of your answers. These responses should be received by 1-5-2020 before 17:00. You can send your answers to . Based on your responses we will review our proposal and adjust it if there are good suggestions. This modified proposal will then become the starting point for the workshop (part two of the consultation). 2. Optional: one or more workshops where together we will determine the various needs and prerequisites within the community (participation only on request of OpenZaak). After submitting your answers, you will receive a message no later than 13-5-2020 if you are invited for the workshop. This will take place on 20th and 21st of May 2020. With the invitation you will receive further information about the exact time and location. Dimpact is responsible for the communication about this market consultation. You can contact Niels Lindeboom at or 06-22270923. diff --git a/how-to-respond-nl.md b/how-to-respond-nl.md index 57b8273..849238a 100644 --- a/how-to-respond-nl.md +++ b/how-to-respond-nl.md @@ -7,7 +7,7 @@ Op deze pagina wordt het proces en het tijdschema voor de reactie op de marktcon ## Uitgangspunten marktconsultatie -Met OpenZaak realiseren we een belangrijke stap om de [Common Ground](https://commonground.nl/cms/view/54476259/over-common-ground) principes te realiseren. Maar wij realiseren ons goed dat het pas van waarde is als het actief wordt gebruikt en doorontwikkelt. +Met OpenZaak realiseren we een belangrijke stap om de [Common Ground](https://commonground.nl/cms/view/54476259/over-common-ground) principes te realiseren. Maar wij realiseren ons goed dat het pas van waarde is als het actief wordt gebruikt en doorontwikkeld. Onze motivatie is een community te realiseren waarin overheid, leveranciers en partners samenwerken. Een community, zonder lock-ins, die voor alle betrokken werkt. Vanuit die gezamenlijkheid willen we ook deze marktconsultatie opzetten. @@ -17,7 +17,7 @@ We willen jullie ervaring, inspiratie en denkkracht inzetten om tot de juiste op De marktconsultatie bestaat uit twee onderdelen. -1. Een schriftelijke reactie op onze vragen. We stellen bewust geen restricties aan de vorm en lengte van jullie antwoorden. Deze reacties dienen uiterlijk op 1-5-2020 vóór 17:00 uur ontvangen te zijn. U kunt uw antwoorden sturen aan niels.lindeboom@dimpact.nl. Op basis van jullie antwoorden gaan wij opnieuw kijken naar ons voorstel en dit aanpassen als er goede suggesties zijn gegeven. Dit aangepaste voorstel wordt dan het uitgangspunt voor de workshop (deel twee van de consultatie). +1. Een schriftelijke reactie op onze vragen. We stellen bewust geen restricties aan de vorm en lengte van jullie antwoorden. Deze reacties dienen uiterlijk op 1-5-2020 vóór 17:00 uur ontvangen te zijn. Jij kunt je antwoorden sturen aan . Op basis van jullie antwoorden gaan wij opnieuw kijken naar ons voorstel en dit aanpassen als er goede suggesties zijn gegeven. Dit aangepaste voorstel wordt dan het uitgangspunt voor de workshop (deel twee van de consultatie). 2. Optioneel: een of meer workshops waarin we met elkaar de diverse behoefte en voorwaarden binnen de community gaan bepalen (deelname alleen op verzoek van OpenZaak). Na het indienen van jullie antwoorden ontvang je uiterlijk 13-5-2020 2020 een bericht of je wordt uitgenodigd voor de workshop. Deze vinden plaats op 20/21-5-2020. Bij de uitnodiging ontvang je verdere informatie over de exacte tijd en locatie. De communicatie over deze marktconsultatie verloopt via Dimpact. Je kunt contact opnemen met Niels Lindeboom op of 06-22270923. @@ -37,7 +37,7 @@ Nadat de geïnteresseerde partijen de vragen uit het marktconsultatiedocument he ## Juridische aspecten -Dit document is alleen bestemd voor marktconsultatie doeleinden. Het wordt ter beschikking gesteld onder de uitdrukkelijke voorwaarde dat het uitsluitend gebruikt wordt om suggesties en ideeën aan te reiken. Een deelname aan deze marktconsultatie kan niet leiden tot verplichtingen van de deelnemende marktpartijen om overeenkomsten met de deelnemende gemeenten of Dimpact aan te gaan, en vice versa. Aan de deelname van de marktconsultatie is geen vergoeding van kosten verbonden. +Dit document is alleen bestemd voor marktconsultatie doeleinden. Het wordt ter beschikking gesteld onder de uitdrukkelijke voorwaarde dat het uitsluitend gebruikt wordt om suggesties en ideeën aan te reiken. Een deelname aan deze marktconsultatie kan niet leiden tot verplichtingen van de deelnemende marktpartijen om overeenkomsten met de deelnemende gemeenten of Dimpact aan te gaan, en vice versa. Aan deelname van de marktconsultatie is geen vergoeding van kosten verbonden. | Home | Inleiding | Onze voorstellen en vragen | Reageren op de marktconsultatie | | -------- | -------- | -------- | -------- | diff --git a/introduction-nl.md b/introduction-nl.md index 9461f54..2e41edb 100644 --- a/introduction-nl.md +++ b/introduction-nl.md @@ -17,13 +17,13 @@ De OpenZaak codebase helpt Nederlandse gemeenten om te voldoen aan de [VNG-stand De deelnemende gemeenten zijn op zoek naar geïnteresseerde leveranciers om hen te ondersteunen bij de implementatie van de codebase (onder meer in de ontwikkeling, onderhoud, implementatie en ondersteuning). De ambitie is om een gezonde open source community te hebben waarin leveranciers de mogelijkheid krijgen om de markt voor OpenZaak te laten groeien, en waarin inkoop wordt vereenvoudigd en gestandaardiseerd. -Hiervoor vinden we het belangrijk om een open en collaboratieve gemeenschap te hebben, inclusief één codebase met een gemeenschappelijke governancestructuur en een gedeeld begrip over bugfixes en -ondersteuning. Meer informatie over de behoeften, conceptvisie en open vragen van de gemeenten is te vinden in [onze voorstellen en vragen](questions-nl.md) en het [draft governance.md document](governance.md). +Hiervoor vinden we het belangrijk om een open en samenwerkende gemeenschap te hebben, inclusief één codebase met een gemeenschappelijke governancestructuur en een gedeeld begrip over bugfixes en ondersteuning. Meer informatie over de behoeften, conceptvisie en open vragen van de gemeenten is te vinden in [onze voorstellen en vragen](questions-nl.md) en het [draft governance.md document](governance.md). ## Over deze marktconsultatie -Marktpartijen die geïnteresseerd zijn in deelname worden gevraagd [onze voorstellen en vragen](questions-nl.md) zorgvuldig te herzien en te reageren op de daar genoemde vragen. +Marktpartijen die geïnteresseerd zijn in deelname worden gevraagd [onze voorstellen en vragen](questions-nl.md) zorgvuldig te lezen en te reageren op de daar genoemde vragen. -De antwoorden moeten voor 1-5-2020 worden ontvangen door Niels Lindeboom. Op basis van deze antwoorden kunnen marktpartijen samen met de gemeenten worden uitgenodigd voor één of meerdere workshops om te bepalen hoe de OpenZaak-gemeenschap kan worden opgezet. Meer informatie over dit marktraadplegingsproces is te vinden in [hoe te reageren](how-to-respond-nl.md). +De antwoorden moeten voor 1-5-2020 binnen zijn bij Niels Lindeboom. Op basis van deze antwoorden kunnen marktpartijen samen met de gemeenten worden uitgenodigd voor één of meerdere workshops om te bepalen hoe de OpenZaak-gemeenschap kan worden opgezet. Meer informatie over dit marktraadplegingsproces is te vinden in [hoe te reageren](how-to-respond-nl.md). Deze marktconsultatie wordt georganiseerd door [Dimpact](https://www.dimpact.nl/), in opdracht van de OpenZaak gemeenten, ondersteund door de [Foundation for Public Code](https://publiccode.net/). diff --git a/questions-nl.md b/questions-nl.md index 9e42773..7a65e38 100644 --- a/questions-nl.md +++ b/questions-nl.md @@ -81,7 +81,7 @@ Zij moeten in de community samenwerken aan: Deze sectie bevat een lijst met open vragen. Elk deel bevat onze huidige veronderstellingen en een reeks open vragen die we willen bespreken met de leveranciersgemeenschap. -Let op: vragen zijn indicatief, we horen graag uw mening over elk van de punten in deze bijlage. +Let op: vragen zijn indicatief, we horen graag jouw mening over elk van de punten in deze bijlage. ### 1. Single shared codebase @@ -111,7 +111,7 @@ Deze marktconsultatie omvat een [ontwerpvoorstel van een governancestructuur](go 2. Wat zijn de uitdagingen die u voorziet bij het onderhouden van open backlogs bij uw klanten? 3. Wie moet verantwoordelijk zijn voor het bijwerken van de shared roadmap? U, de gemeenten, of een gedeelde verantwoordelijkheid? 4. Hoe wilt u de gedeelde feature en technical roadmap kunnen beïnvloeden? -5. Hoe wilt u dat de community omgaat met het ontwikkelen, eens worden en onderhouden van gedeelde engineering en contributing guidelines? +5. Hoe wilt u dat de community omgaat met het ontwikkelen, eens worden over en onderhouden van gedeelde engineering en contributing guidelines? 6. Welke risico’s ziet u in het werken in zo'n omgeving? ### 3. Bugs en bug fixes @@ -143,7 +143,7 @@ Veel gemeenten zullen de voorkeur geven aan één enkele leverancier die ze kunn #### Veronderstellingen -De OpenZaak API's zijn gebaseerd op een VNG standaard, de [API's voor zaakgericht werken](https://www.vngrealisatie.nl/producten/api-standaarden-zaakgericht-werken). De standaard wordt continu onderhouden en verbeterd en OpenZaak moet daaraan blijven voldoen. Deze updates moeten worden gepropageerd over de centrale repository-branche, evenals repositories die marktpartijen gebruiken om hun diensten te leveren (zoals backend-as-a-service). +De OpenZaak API's zijn gebaseerd op een VNG standaard, de [API's voor zaakgericht werken](https://www.vngrealisatie.nl/producten/api-standaarden-zaakgericht-werken). De standaard wordt continu onderhouden en verbeterd en OpenZaak moet daaraan blijven voldoen. Deze updates moeten worden gepropageerd naar de centrale repository-branche, evenals repositories die marktpartijen gebruiken om hun diensten te leveren (zoals backend-as-a-service). #### Vragen From d0aa7c824a2a068b60b64d59ca251e936d657a3b Mon Sep 17 00:00:00 2001 From: ElenaFdR Date: Wed, 15 Apr 2020 09:29:23 +0200 Subject: [PATCH 46/54] supermajority --- GOVERNANCE.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/GOVERNANCE.md b/GOVERNANCE.md index 2ee75f7..65561bd 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -65,7 +65,7 @@ Responsibilities of the product steering team: Members are appointed by the current product steering team members. -Changes in codebase governance can only be done by the product steering team and requires super majority (2/3). +Changes in codebase governance can only be done by the product steering team and requires supermajority (2/3). The current team members are: @@ -80,9 +80,9 @@ When a consensus cannot be found a team member can call for a majority vote on a Many of the day-to-day project maintenance tasks can be done by a lazy consensus model. But the following items must be called to vote: * Adding a team member (simple majority) -* Removing a team member (super majority) -* Changing the governance rules (this document) (super majority) -* Licensing and intellectual property changes (including new logos, wordmarks) (simple majority) +* Removing a team member (supermajority) +* Changing the governance rules (this document) (supermajority) +* Licensing and intellectual property changes (including new logos, wordmarks) (supermajority) * Adding, archiving, or removing subprojects (simple majority) ## Code of Conduct From bdb20b41ad0bc93dda9e545ddb72115cd47da56c Mon Sep 17 00:00:00 2001 From: claus Date: Wed, 15 Apr 2020 12:34:27 +0200 Subject: [PATCH 47/54] Fix hyperlink to issue tracker --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index cce713e..a1e4c93 100644 --- a/README.md +++ b/README.md @@ -10,7 +10,7 @@ Het doel van deze marktconsultatie is om marktpartijen uit te nodigen bij het op Hieronder vindt u een inleiding, een reeks voorstellen en vragen, een voorstel voor governance.md, en informatie over hoe u op deze consultatie kunt reageren. **Deze reacties dienen uiterlijk op 1-5-2020 vóór 17:00 uur ontvangen te zijn.** -Als je vragen hebt over deze consultatie, aarzel dan niet om [een issue aan te maken](https://github.com/open-zaak/openzaak-market-consultation/issues/new/choose) of e-mail Niels Lindeboom op . +Als je vragen hebt over deze consultatie, aarzel dan niet om [een issue aan te maken](https://github.com/open-zaak/open-zaak-market-consultation/issues) of e-mail Niels Lindeboom op . ## English @@ -18,7 +18,7 @@ The goal of this market consultation is to invite market parties to help set up Below you can find an introductory cover letter, a set of proposals and questions, a draft governance.md, and how to respond to this consultation. **Responses should be received by 1-5-2020 before 17:00.** -If you have any questions about this consultation, please feel free to [create an issue](https://github.com/open-zaak/openzaak-market-consultation/issues/new/choose) or email Niels Lindeboom at . +If you have any questions about this consultation, please feel free to [create an issue](https://github.com/open-zaak/open-zaak-market-consultation/issues) or email Niels Lindeboom at . ## Consultation contents / Consultatie inhoud From f0e3d622cf07e676f2bffb926dcc158a88b8872e Mon Sep 17 00:00:00 2001 From: Jan Ainali Date: Wed, 15 Apr 2020 13:55:46 +0200 Subject: [PATCH 48/54] added back link straight to issue creation --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index a1e4c93..b4157fe 100644 --- a/README.md +++ b/README.md @@ -10,7 +10,7 @@ Het doel van deze marktconsultatie is om marktpartijen uit te nodigen bij het op Hieronder vindt u een inleiding, een reeks voorstellen en vragen, een voorstel voor governance.md, en informatie over hoe u op deze consultatie kunt reageren. **Deze reacties dienen uiterlijk op 1-5-2020 vóór 17:00 uur ontvangen te zijn.** -Als je vragen hebt over deze consultatie, aarzel dan niet om [een issue aan te maken](https://github.com/open-zaak/open-zaak-market-consultation/issues) of e-mail Niels Lindeboom op . +Als je vragen hebt over deze consultatie, aarzel dan niet om [een issue aan te maken](https://github.com/open-zaak/open-zaak-market-consultation/issues/new/choose) of e-mail Niels Lindeboom op . ## English @@ -18,7 +18,7 @@ The goal of this market consultation is to invite market parties to help set up Below you can find an introductory cover letter, a set of proposals and questions, a draft governance.md, and how to respond to this consultation. **Responses should be received by 1-5-2020 before 17:00.** -If you have any questions about this consultation, please feel free to [create an issue](https://github.com/open-zaak/open-zaak-market-consultation/issues) or email Niels Lindeboom at . +If you have any questions about this consultation, please feel free to [create an issue](https://github.com/open-zaak/open-zaak-market-consultation/issues/new/choose) or email Niels Lindeboom at . ## Consultation contents / Consultatie inhoud From 8e9ad2b7f518f409e0a9e035c2a68688bd0a3a66 Mon Sep 17 00:00:00 2001 From: ElenaFdR Date: Wed, 15 Apr 2020 14:36:49 +0200 Subject: [PATCH 49/54] collaborative governance/public issue tracker --- questions-en.md | 2 +- questions-nl.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/questions-en.md b/questions-en.md index bdfcd24..4c3496e 100644 --- a/questions-en.md +++ b/questions-en.md @@ -20,7 +20,7 @@ For vendors it is important to grow the number of replicating municipalities (in Without knowing all the answers in detail, our vision for this community includes: * collaborating on a single, vendor-neutral codebase and shared branching model, avoiding diverging forks -* collaborative governance, including around shared roadmaps (feature and technical) and open issue tracker +* governance based on collaboration, including around shared roadmaps (feature and technical) and public issue tracker * a shared understanding of how to approach bug fixes and support, particularly in situations of operational downtime or security risks * an inclusive community (including open communication channels, codebase marketing material and codes of conduct) that is welcoming to new market parties and new replicating municipalities * empowering vendors to become effective members and ambassadors of the community diff --git a/questions-nl.md b/questions-nl.md index 7a65e38..3421b4d 100644 --- a/questions-nl.md +++ b/questions-nl.md @@ -20,7 +20,7 @@ Voor leveranciers is het belangrijk om het aantal deelnemende gemeenten te laten Zonder alle antwoorden in detail te kennen, omvat onze visie voor de community: * samenwerken aan één leverancier-neutrale codebase en shared branchingmodel, waarbij uiteenlopende forks worden vermeden -* collaborative governance, inclusief rond gedeelde roadmaps (feature en technical) en open issue tracker +* governance op basis van samenwerking, waarbij ook wordt samengewerkt rond gedeelde roadmaps (feature en technical) en openbare issue tracker * een gedeeld inzicht in hoe bugfixes en ondersteuning kunnen worden aangepakt, met name in situaties van operationele downtime of beveiligingsrisico's * een inclusieve community (inclusief open communicatiekanalen, codebase marketingmateriaal en codes of conduct) die nieuwe marktpartijen en nieuwe deelnemende gemeenten verwelkomt * leveranciers in staat stellen om effectieve leden en ambassadeurs van de community te worden From 5c3c0c0b3b167f9201f4846d93cf671e31863939 Mon Sep 17 00:00:00 2001 From: claus Date: Thu, 16 Apr 2020 10:39:52 +0200 Subject: [PATCH 50/54] Fix links in readme Add code of conduct --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index b4157fe..d26304f 100644 --- a/README.md +++ b/README.md @@ -37,6 +37,7 @@ OpenZaak codebase * OpenZaak [README](https://github.com/open-zaak/open-zaak/blob/master/README.rst) (Nederlands) * OpenZaak [CONTRIBUTING](https://github.com/open-zaak/open-zaak/blob/master/CONTRIBUTING.md) (English) * Draft of a potential [governance.md]() file (English) +* Draft of a potential [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md) file (English) How to respond / Hoe te reageren From 19e681698dd1c038dc002242aa106868fdd2f870 Mon Sep 17 00:00:00 2001 From: claus Date: Thu, 16 Apr 2020 10:40:26 +0200 Subject: [PATCH 51/54] link governance file --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index d26304f..6a51c5a 100644 --- a/README.md +++ b/README.md @@ -36,7 +36,7 @@ OpenZaak codebase * OpenZaak [README](https://github.com/open-zaak/open-zaak/blob/master/README.rst) (Nederlands) * OpenZaak [CONTRIBUTING](https://github.com/open-zaak/open-zaak/blob/master/CONTRIBUTING.md) (English) -* Draft of a potential [governance.md]() file (English) +* Draft of a potential [GOVERNANCE.md](GOVERNANCE.md) file (English) * Draft of a potential [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md) file (English) How to respond / Hoe te reageren From 0c63b8f2c7adb397b85524a9994d5ba457b42760 Mon Sep 17 00:00:00 2001 From: claus Date: Thu, 16 Apr 2020 10:41:28 +0200 Subject: [PATCH 52/54] align to style --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 6a51c5a..c269968 100644 --- a/README.md +++ b/README.md @@ -36,8 +36,8 @@ OpenZaak codebase * OpenZaak [README](https://github.com/open-zaak/open-zaak/blob/master/README.rst) (Nederlands) * OpenZaak [CONTRIBUTING](https://github.com/open-zaak/open-zaak/blob/master/CONTRIBUTING.md) (English) -* Draft of a potential [GOVERNANCE.md](GOVERNANCE.md) file (English) -* Draft of a potential [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md) file (English) +* Draft of a potential [GOVERNANCE](GOVERNANCE.md) file (English) +* Draft of a potential [CODE_OF_CONDUCT](CODE_OF_CONDUCT.md) file (English) How to respond / Hoe te reageren From 4d24976d84da4a7d3bf009c1e0dd5ba6ef689231 Mon Sep 17 00:00:00 2001 From: Elena FdR Date: Thu, 16 Apr 2020 10:54:33 +0200 Subject: [PATCH 53/54] Update GOVERNANCE.md --- GOVERNANCE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/GOVERNANCE.md b/GOVERNANCE.md index 65561bd..1c4df54 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -73,7 +73,7 @@ The current team members are: ## Decision making process -The default decision making process is lazy-consensus. This means that any decision is considered supported by the team making it as long as no one objects. Silence on any consensus decision is implicit agreement and equivalent to explicit agreement. Explicit agreement may be stated at will. +The default decision making process is lazy consensus. This means that any decision is considered supported by the team making it as long as no one objects. Silence on any consensus decision is implicit agreement and equivalent to explicit agreement. Explicit agreement may be stated at will. When a consensus cannot be found a team member can call for a majority vote on a decision. Every team member has 1 vote. From a8a7b08d11e0b34ca3e5e8ba51a3e5fffe0ed91d Mon Sep 17 00:00:00 2001 From: Elena FdR Date: Thu, 16 Apr 2020 10:59:12 +0200 Subject: [PATCH 54/54] Update how-to-respond-en.md --- how-to-respond-en.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/how-to-respond-en.md b/how-to-respond-en.md index bc5941b..cdfaf94 100644 --- a/how-to-respond-en.md +++ b/how-to-respond-en.md @@ -20,7 +20,7 @@ The market consultation consists of two parts: 1. A written response to our questions. We're deliberately not restricting the form and length of your answers. These responses should be received by 1-5-2020 before 17:00. You can send your answers to . Based on your responses we will review our proposal and adjust it if there are good suggestions. This modified proposal will then become the starting point for the workshop (part two of the consultation). 2. Optional: one or more workshops where together we will determine the various needs and prerequisites within the community (participation only on request of OpenZaak). After submitting your answers, you will receive a message no later than 13-5-2020 if you are invited for the workshop. This will take place on 20th and 21st of May 2020. With the invitation you will receive further information about the exact time and location. -Dimpact is responsible for the communication about this market consultation. You can contact Niels Lindeboom at or 06-22270923. +Dimpact is responsible for communication about this market consultation. You can contact Niels Lindeboom at or 06-22270923. ## Market consultation report