# Feature request process If you have an idea for a new feature, we encourage you to first [discuss it with the Speedb community](https://github.com/speedb-io/speedb/discussions) regarding its viability and potential. Once you've discussed it with the community, you should prepare a proposal and submit it as a feature request. For your feature proposal, [use the feature request template](https://github.com/speedb-io/speedb/issues/new?assignees=\&labels=\&template=feature_request.md\&title=). \ \ When working on a proposal, it's important to keep in mind that it takes time to discuss new ideas with the community, review it, and eventually implement it. We encourage you to discuss your idea early, before even writing your proposal. Once your proposal is accepted, the next step is to [submit a pull request](/getting-started/how-to-contribute/submit-a-pull-request.md#important-information-when-creating-a-pull-request). ### A few things to note * Bug fixes and mechanical improvements don't need a feature request. * All new features and bug fixes must include unit tests, since they help to (a) document and validate concrete usage of a feature and its edge cases, and (b) guard against future breaking changes to lower the maintenance cost. * Unit tests must pass with the changes. * If a feature with failed tests (unrelated to the feature) is submitted, it will only be considered once the feature passes all testing. * Code changes should be made with API compatibility and evolvability in mind. Pull requests should only be sent once a proposal has been discussed, submitted, and reviewed. It's important to note that all new features and substantive changes to Speedb need to go through a formal feature request process. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.speedb.io/getting-started/how-to-contribute/feature-request-process.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.