Add CONTRIBUTING.md and CODE_OF_CONDUCT.md (Fixes #23) #32
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I am actively contributing to open-source projects as part of my journey toward Google Summer of Code (GSoC) 2025. My goal is to gain hands-on experience collaborating with open-source communities, improving documentation, and working on impactful projects. I look forward to engaging more with this repository and contributing further to its development.
This PR adds the missing CONTRIBUTING.md and CODE_OF_CONDUCT.md files to establish clear contribution guidelines and community behavior expectations. These documents align with open-source best practices and improve the onboarding process for new contributors.
Created CONTRIBUTING.md with detailed guidelines on how to contribute, including instructions for forking, cloning, submitting PRs, and following coding standards.
Created CODE_OF_CONDUCT.md based on the Contributor Covenant 2.1 to ensure a respectful and inclusive community.
Updated README.md to link to these files for easy access.
Why These Changes Are Important?
Provides clear instructions for new contributors.
Establishes community standards for behavior and collaboration.
Aligns with best practices followed by major open-source projects.
Testing and Verification
No functional code changes were made in this PR, so no testing is required.