From de12a3812288e0aeb835b2993e5277a2eaf9dc55 Mon Sep 17 00:00:00 2001 From: JP-Ellis Date: Fri, 5 Jul 2024 10:10:50 +1000 Subject: [PATCH] fix: address comments from @YOU54F Primarily around the list, which was perhaps a little confusing with the inclusion of 'various languages' but was immediately followed by a disclaimer that the language implementations are out of scope. Signed-off-by: JP-Ellis --- rfc/0000-rfc-process.md | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/rfc/0000-rfc-process.md b/rfc/0000-rfc-process.md index 5c739bc..b09599e 100644 --- a/rfc/0000-rfc-process.md +++ b/rfc/0000-rfc-process.md @@ -17,15 +17,16 @@ While the evolution of Pact and its ecosystem is open, the process for proposing The Pact ecosystem is broad and includes, broadly speaking, the following areas: -- The Pact specification itself, -- The Pact broker, -- The Pact CLI, -- The Pact FFI, -- The Pact implementation in various languages, +- The Pact specification itself ([pact-foundation/pact-specification](https://github.com/pact-foundation/pact-specification)); +- The Pact broker ([pact-foundation/pact-broker](pact-foundation/pact_broker)); +- The Pact CLI ([pact-foundation/pact-ruby-cl](https://github.com/pact-foundation/pact-ruby-cli)); and, +- The Pact FFI ([pact-foundation/pact-reference](https://github.com/pact-foundation/pact-reference/tree/master/rust/pact_ffi)). -This RFC process is intended to cover any change which will impact the broader Pact ecosystem and therefore includes the first four areas listed above. +This RFC process is intended to cover any change which will impact the broader Pact ecosystem. -While specific changes to the Pact implementation in various languages are out of scope, we do wish to consider how changes in the first four areas will impact the implementation in various languages. Furthermore, we may wish to introduce or formalize common conventions or guidelines that are applied across the various languages to ensure consistency, interoperability, and familiarity for users. +While specific changes to the Pact implementation in various languages are generally out of scope[^1], we do wish to consider how changes in the areas above will impact the implementation in various languages. Furthermore, we may wish to introduce or formalize common conventions or guidelines that are applied across the various languages to ensure consistency, interoperability, and familiarity for users. + +[^1]: Changes to the Pact implementation in various languages are out of scope because they are managed by the maintainers of the individual language implementations (which may even have their own RFC process). ### The Process