From f2c6f0b33ece33d93d950a0a3e10d5fc86af8f18 Mon Sep 17 00:00:00 2001 From: Michele Claus Date: Tue, 25 Jun 2024 15:46:06 +0000 Subject: [PATCH 1/2] Remove mention to examples folder --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 24c28899..f2485b6c 100644 --- a/README.md +++ b/README.md @@ -40,7 +40,7 @@ This repository contains a set of files formally describing the openEO Processes ## Process * All new processes must be added to the [`proposals`](proposals/) folder. -* Processes will only be moved from proposals to the stable process specifications once there are at least two implementations and an example process in the [`examples`](examples/) folder showing it in a use case. This doesn't require a PSC vote individually as it's not a breaking change, just an addition. +* Processes will only be moved from proposals to the stable process specifications once there are at least two implementations. This doesn't require a PSC vote individually as it's not a breaking change, just an addition. * The [`proposals`](proposals/) folder allows breaking changes without a PSC vote and without increasing the major version number (i.e. a breaking change in the proposals doesn't require us to make the next version number 2.0.0). * The proposals are released as experimental processes with the other processes. * Each release and all breaking changes in the stable process specifications must go through PSC vote. \ No newline at end of file From 25d9b521e43098ee1b5dee312367497391e14406 Mon Sep 17 00:00:00 2001 From: Matthias Mohr Date: Mon, 29 Jul 2024 12:33:34 +0200 Subject: [PATCH 2/2] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index f2485b6c..71f78f57 100644 --- a/README.md +++ b/README.md @@ -40,7 +40,7 @@ This repository contains a set of files formally describing the openEO Processes ## Process * All new processes must be added to the [`proposals`](proposals/) folder. -* Processes will only be moved from proposals to the stable process specifications once there are at least two implementations. This doesn't require a PSC vote individually as it's not a breaking change, just an addition. +* Processes will only be moved from proposals to the stable process specifications once there are at least two implementations and an example process in the [`openEO community examples`](https://github.com/Open-EO/openeo-community-examples/) showing it in a use case. This doesn't require a PSC vote individually as it's not a breaking change, just an addition. * The [`proposals`](proposals/) folder allows breaking changes without a PSC vote and without increasing the major version number (i.e. a breaking change in the proposals doesn't require us to make the next version number 2.0.0). * The proposals are released as experimental processes with the other processes. * Each release and all breaking changes in the stable process specifications must go through PSC vote. \ No newline at end of file