Community
Note
Disclaimer: Protean framework is not associated with, or related to, Protean eGov Technologies or Code for Gov Tech initiatives.
Forum
If you've hit a problem with something you're working on and could use some help, the best place to ask is on GitHub Discussions where we use issues as a message board. These discussions are indexed by search engines which means asking your questions here will make it easier for others to find the answer if they have a similar problem in the future.
Github
Found a bug, have a feature request, or want to contribute to the framework itself?
Head to Protean's home on Github.
Star the repo
While GitHub stars don't tell the whole story, they do help increase the visibility of the framework, making it easier for other users to discover and adopt it.
Star Protean on GitHub, by clicking the star button at the top right.
Watch for releases
You can watch Protean on GitHub for new releases and updates.
Click on the "watch" button at the top right in Github and select "Releases only".
You will then receive notifications (in your email) whenever there's a new release (a new version) of Protean with bug fixes and new features.
Contributing
Protean is designed and maintained by a single maintainer, from one coherent view of the whole framework. This is a deliberate choice that keeps the design consistent and the correctness bar high. It does not mean the project is closed to you: the contributions below are genuinely valued.
Report bugs
A clear, reproducible bug report is the single most useful thing you can send. Real-world failure cases are how a framework earns its correctness. File bugs and feature requests on GitHub Issues with enough detail to reproduce the problem.
Share use cases and feedback
Tell us where Protean fits your domain awkwardly, where an abstraction leaks, or where the docs mislead you. Open a Discussion or an issue.
Build adapters
Databases, brokers, event stores, and caches plug in through a public port contract and are verified by a conformance suite. Adapters live in their own packages, owned by their authors, rather than in the core, so you can extend Protean without touching it. See Building Adapters to get started.
Improve documentation
Corrections and clarifications are welcome, and small doc fixes can go straight to a pull request.
Spread the word
Sharing your experience, writing about Protean, or speaking at events all help others discover the framework.
How code contributions are handled. Small, obvious fixes are welcome directly as pull requests. Anything larger should start with an issue so the approach can be agreed first; unsolicited large pull requests may not be merged. The full policy, including the bar for AI-assisted pull requests, is in CONTRIBUTING.