Alkeme

We warmly welcome contributions from the open-source community to help improve, expand, and maintain this project. Pull requests are strongly encouraged, particularly in three core areas: bug fixes, improved data sources, and refinements to our backtesting methodology. Whether you are resolving a subtle edge case in an existing script, integrating a cleaner or more comprehensive financial dataset, or introducing more rigorous statistical validation techniques, your efforts directly enhance the reliability and usefulness of this codebase for researchers, developers, and users alike. Before investing significant time into major development, we ask that you please open an issue first to discuss any substantial changes. Initiating a conversation early allows project maintainers and fellow contributors to review your proposal, provide constructive feedback, align on architectural direction, and ensure your planned work does not overlap with ongoing initiatives. While smaller, straightforward bug fixes and minor documentation updates can be submitted directly via a pull request, opening a quick issue beforehand for broader visibility and tracking is always appreciated. To ensure a smooth, efficient review and integration process, please refer to our CONTRIBUTING.md file for complete contribution guidelines. Inside that document, you will find detailed instructions covering our preferred coding style, formatting standards, branch naming conventions, unit testing requirements, and pull request submission templates. Adhering to these established practices helps us maintain a clean, readable, and well-documented repository while enabling maintainers to test, review, and merge your contributions much more quickly. We also encourage contributors to keep their pull requests focused and modular. Submitting separate pull requests for distinct bug fixes, individual data source integrations, or isolated methodological updates makes code review significantly easier and reduces the likelihood of merge conflicts. Whenever possible, please include clear commit messages, updated documentation, and relevant test cases demonstrating that your changes work as expected without breaking existing functionality. Finally, if you are looking for a more guided way to get involved, receive dedicated mentorship, and work on impactful project milestones, we invite you to contribute as part of a structured program. Be sure to check out the DBERT Internship Program detailed above for comprehensive information regarding program eligibility, key timelines, project tracks, and application instructions. We deeply appreciate your interest, time, and expertise, and we look forward to collaborating with you to make this project even better!