Evangelism / Enablement / Advocacy / Community
Good communities are places where people ❤️ to be.
We are committed to making our Pact community, the go to place for all things contract-testing but also for people to get to know each, connect, meet, share experiences and become life-long friends.
As a Developer Advocate / Community Shepherd, I know that pact foundation has huge amount of GitHub repositories and maintainers hold a huge amount of weight on our shoulders, to ensure that people can use Pact day-in day-out to protect their deployments. It's a hard job to keep track of.
Let me make the Pact landscape a little easier to navigate
| Project | Resources |
|---|---|
| Pact Broker | Github / Github Actions / Docker |
| Pact CLI | Github / Docker |
| Pact Ruby Standalone | Releases / E2E example |
| Pact JS | Github / Message docs |
| Roadmap | Canny |
| Docs | Homepage |
The Pact ecosystem is vast, I will be sharing some posts over the upcoming months, showing the size of the estate, and looking to gain insight from you, the community, as to how we can reduce the signal-to-noise and help reduce the cognitive load required to navigate the path the Pact Nirvana in your own organisation.
There are a multitude of ways, and you don't need to be a code wizard to start:
Our documentation is the primary way to communicate to our users, you can help out with small changes like a typo, help rewrite larger pieces, or add new content. Think of it as a open source contract testing wiki, and you are all the curators.
We have implementations across multiple languages, and not all of them are at feature parity. Sometimes you might need that feature, or you've found a bug. Every pact-foundation repository is open-source, and contains a contributing guide to help you get started. Maybe you are building your own Pact tooling, let us know, we would love to shout about it.
The Pact roadmap is available on Canny, where you can see some of the teams current and upcoming priorities in the OSS space. You can request new features, or browse the list and vote/comment on ones you would love to see. See one that particularly resonates? You could help work on it, reach out via Slack and we can help guide you through your contribution.
The community use our tools in a variety of different ways, and solve various challenges that others could benefit. Got something to share? Why not add a new recipe to the site?
We created a number of workshops, across several languages. Is there a language implementation not covered in the workshop? Maybe you've created or seen some amazing workshops out there in the wild? Add it to the list, or if you are the author, you can discuss bringing your workshop under the Pact-foundation, if you feel all Pact users could benefit
Articles about contract testing are appearing left, right and centre, I can't keep up. Make sure our reading list doesn't get dry, by adding your favourite content to the list
Meetups, in person, it feels like a distant memory, but as the doors start opening again, and dinner is provided, people are beginning to flock outdoors. Have you got a meetup or event planned? Already had one and recorded it? You can add them to the list, and let us and the community know about it on Slack.
We know many of you in the community love sharing your contract testing knowledge with others, you can see the various places our users land for help, sometimes in GitHub issues, Stack overflow, or Slack. You are welcome to help them out whether you are new to Pact, or a seasoned pro, all questions, opinions and thoughts are welcome.
Are you like our co-founder Beth Skurrie, who decided that Pact idea was the best thing since sliced bread, and she hasn't stopped yacking on about it since. Want to share your knowledge, and build your social profile in the world of tech with a global platform? Please get in touch, we want to support the amazing work you do!
This section contains technical information about the pact source code and builds. Go to pact.io for user documentation
To minimise the amount of code maintenance, many pact implementations depend on some shared libraries. When the shared libraries are updated, it is important to update the packages that use them.
This graph shows the dependency relationships to assist in updating the libraries.
See the Dependency Graph of Doom
We want to track our GitHub repo usage, health, and cross-correlate with Slack, so we can reach the right people quicker, and ultimately save leaving you hanging.
I'd also love to build some tooling myself, but why reinvent the wheel, there is already plenty of stuff to do in Pact land!
So why Orbit? I'll let them explain in their own words
The fact that Pact works across so many different languages these day is due to the contribution of many different people and companies. To acknowledge the support that many companies have made to Pact's open source code, some repositories still live under the github organisation of their original author. They are listed below.