Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RFC Process #32

Closed
JP-Ellis opened this issue Jun 13, 2024 · 1 comment
Closed

RFC Process #32

JP-Ellis opened this issue Jun 13, 2024 · 1 comment
Assignees

Comments

@JP-Ellis
Copy link
Contributor

Summary

Introduce a process to request for comments (RFC) for changes which will impact Pact as a whole.

Motivation

The Pact Foundation has always wanted to be transparent in the way new features are added to Pact, and while most of the information can be discovered (whether it be from some issue thread, Slack discussion or otherwise), the information may not always be as discoverable as desired.

By formalising a RFC process and storing the discussion in a centralised location, we hope to make the process much more discoverable.

Suggestion

In my experience, the Rust RFC process is excellent, albeit perhaps too rigorous for Pact's needs. I would suggest adopting a similar approach for Pact, with some adjustments made to be more lightweight.

Scopes

The Pact ecosystem is split across a number of languages, and therefore part of the initial discussion will be deciding what should go within the scope of the RFCs.

@JP-Ellis JP-Ellis self-assigned this Jun 13, 2024
@mefellows
Copy link
Member

Closed by #96.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants