Project: Apicurio Registry (App Definition and Development / Streaming & Messaging)
File: CONTRIBUTING.md

Want to contribute? Great! We try to make it easy, and all contributions, even the smaller ones, are more than welcome. This includes bug reports, fixes, documentation, examples... But first, read this page (including the small print at the end). + + All original contributions to Apicurio projects are licensed under the , version 2.0 or later, or, if another license is specified as governing the file or directory being modified, such other license. All contributions are subject to the . The DCO text is also included verbatim in the file in the root directory of the repository. This project uses GitHub issues to manage the issues. Open an issue directly in GitHub. If you believe you found a bug, and it's likely possible, please indicate a way to reproduce it, what you are seeing and what you would expect to see. Don't forget to indicate your Apicurio Registry, Java, and Maven versions. To contribute, use GitHub Pull Requests, from your own fork. Also, make sure you have set up your Git authorship correctly: ``` git config --global user.name "Your Full Name" git config --global user.email your.email@example.com ``` If you use different computers to contribute, please make sure the name is the same on all your computers. We may use this information to acknowledge your contributions! All submissions, including submissions by project members, need to be reviewed by at least one Apicurio committer before being merged. is followed for every pull request. We primarily use the Git history to track authorship. GitHub also has . Please take care to write code that fits with existing code styles. For your convenience we have Formatters and/or Code Templates for both and . Commits should be atomic and semantic. Please properly squash your pull requests before submitting them. Fixup commits can be used temporarily during the review process but things should be squashed at the end to have meaningful commits. We typically squash and merge pull requests when they are approved. This tends to keep the commit history a little bit more tidy without placing undue burden on the developers. Because we are all humans, and to ensure Apicurio Registry is stable for everyone, all changes must pass continuous integration before being merged. Apicurio CI is based on GitHub Actions, which means that pull requests will receive automatic feedback. Please watch out for the results of these workflows to see if your PR passes all tests. Don't forget to include tests in your pull requests. Also don't forget the documentation (reference documentation, javadoc...). Be sure to test your pull request using all storage variants: SQL storage (using the `-Psql` profile) SQL Server storage (using the `-Pmssql` profile) KafkaSQL storage (using the `-Pkafkasql` profile) Apicurio Registry is a modular project and allows reuse of artifact types to extend and enhance functionality. You can modify the currently supported artifact types and add new types by providing a higher priority implementation of `io.apicurio.registry.types.<my-type>.provider.ArtifactTypeUtilProviderImpl` to the dependency injection framework. In , you can find an example where we add demo `BigQuery` support. The important parts are as follows: Use Provide a in the constructor to include the additional artifact type NOTES: When creating an artifact of a type that is not included in the default, you must always specify the appropriate artifact type. The registry UI will show the plain name of the additional type and won't have an appropriate icon to identify it. This project is an open source project. Please act responsibly, be nice, polite and enjoy!