docs: rewrite documentation for hackathon submission

- Completely rewrote README.md (574 lines) - professional and concise
- Reduced CONTRIBUTING.md to 282 lines - removed redundant content
- Updated CODE_OF_CONDUCT.md, SECURITY.md for consistency
- Changed LICENSE to MIT License (2025 copyright)
- Removed all unnecessary hackathon-specific files
- Focused on project essentials and meaningful content

Author: imash

CODE_OF_CONDUCT.md

@@ -1,128 +1,162 @@
-# Contributor Covenant Code of Conduct
+# Code of Conduct
 
 ## Our Pledge
 
-We as members, contributors, and leaders pledge to make participation in our
-community a harassment-free experience for everyone, regardless of age, body
-size, visible or invisible disability, ethnicity, sex characteristics, gender
-identity and expression, level of experience, education, socio-economic status,
-nationality, personal appearance, race, religion, or sexual identity
-and orientation.
+We as members, contributors, and leaders pledge to make participation in the MariaDB Vector Store integration project a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
 
-We pledge to act and interact in ways that contribute to an open, welcoming,
-diverse, inclusive, and healthy community.
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
 
 ## Our Standards
 
-Examples of behavior that contributes to a positive environment for our
-community include:
+### Examples of Positive Behavior
 
-* Demonstrating empathy and kindness toward other people
-* Being respectful of differing opinions, viewpoints, and experiences
-* Giving and gracefully accepting constructive feedback
-* Accepting responsibility and apologizing to those affected by our mistakes,
-  and learning from the experience
-* Focusing on what is best not just for us as individuals, but for the
-  overall community
+Behaviors that contribute to a positive environment include:
 
-Examples of unacceptable behavior include:
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes
+- Learning from the experience and making improvements
+- Focusing on what is best not just for us as individuals, but for the overall community
+- Using welcoming and inclusive language
+- Being patient with newcomers and those learning
+- Providing helpful and constructive code reviews
+- Celebrating others' successes and contributions
 
-* The use of sexualized language or imagery, and sexual attention or
-  advances of any kind
-* Trolling, insulting or derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or email
-  address, without their explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
+### Examples of Unacceptable Behavior
+
+Behaviors that are unacceptable include:
+
+- The use of sexualized language or imagery, and sexual attention or advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email address, without their explicit permission
+- Deliberately intimidating, stalking, or following
+- Harassing photography or recording
+- Sustained disruption of discussions or other events
+- Inappropriate physical contact or unwelcome sexual attention
+- Other conduct which could reasonably be considered inappropriate in a professional setting
+- Advocating for, or encouraging, any of the above behaviors
 
 ## Enforcement Responsibilities
 
-Community leaders are responsible for clarifying and enforcing our standards of
-acceptable behavior and will take appropriate and fair corrective action in
-response to any behavior that they deem inappropriate, threatening, offensive,
-or harmful.
+Project maintainers are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
 
-Community leaders have the right and responsibility to remove, edit, or reject
-comments, commits, code, wiki edits, issues, and other contributions that are
-not aligned to this Code of Conduct, and will communicate reasons for moderation
-decisions when appropriate.
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned with this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
 
 ## Scope
 
-This Code of Conduct applies within all community spaces, and also applies when
-an individual is officially representing the community in public spaces.
-Examples of representing our community include using an official e-mail address,
-posting via an official social media account, or acting as an appointed
-representative at an online or offline event.
+This Code of Conduct applies within all project spaces, and also applies when an individual is officially representing the project in public spaces. Examples of representing our project include:
+
+- Using an official project email address
+- Posting via an official social media account
+- Acting as an appointed representative at an online or offline event
+- Contributing code, documentation, or other materials
+- Participating in project discussions on GitHub, forums, or chat platforms
+- Representing the project at hackathons or conferences
 
 ## Enforcement
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported to the community leaders responsible for enforcement at
-[Moderator Email](mailto:samarpatel.mi@gmail.com).
+### Reporting
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the project maintainers responsible for enforcement through:
+
+- **GitHub Issues:** For public concerns about project conduct
+- **MindSQL Repository:** Through the main project's reporting channels
+- **Hackathon Organizers:** For issues during the MariaDB Python Hackathon
+
 All complaints will be reviewed and investigated promptly and fairly.
 
-All community leaders are obligated to respect the privacy and security of the
-reporter of any incident.
+All project maintainers are obligated to respect the privacy and security of the reporter of any incident.
+
+### Enforcement Guidelines
+
+Project maintainers will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+#### 1. Correction
+
+**Community Impact:** Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence:** A private, written warning from project maintainers, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+#### 2. Warning
 
-## Enforcement Guidelines
+**Community Impact:** A violation through a single incident or series of actions.
 
-Community leaders will follow these Community Impact Guidelines in determining
-the consequences for any action they deem in violation of this Code of Conduct:
+**Consequence:** A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in project spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
 
-### 1. Correction
+#### 3. Temporary Ban
 
-**Community Impact**: Use of inappropriate language or other behavior deemed
-unprofessional or unwelcome in the community.
+**Community Impact:** A serious violation of community standards, including sustained inappropriate behavior.
 
-**Consequence**: A private, written warning from community leaders, providing
-clarity around the nature of the violation and an explanation of why the
-behavior was inappropriate. A public apology may be requested.
+**Consequence:** A temporary ban from any sort of interaction or public communication with the project for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
 
-### 2. Warning
+#### 4. Permanent Ban
 
-**Community Impact**: A violation through a single incident or series
-of actions.
+**Community Impact:** Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
 
-**Consequence**: A warning with consequences for continued behavior. No
-interaction with the people involved, including unsolicited interaction with
-those enforcing the Code of Conduct, for a specified period of time. This
-includes avoiding interactions in community spaces as well as external channels
-like social media. Violating these terms may lead to a temporary or
-permanent ban.
+**Consequence:** A permanent ban from any sort of public interaction within the project community.
 
-### 3. Temporary Ban
+## Technical Conduct
 
-**Community Impact**: A serious violation of community standards, including
-sustained inappropriate behavior.
+In addition to general community standards, we expect all contributors to follow these technical conduct guidelines:
 
-**Consequence**: A temporary ban from any sort of interaction or public
-communication with the community for a specified period of time. No public or
-private interaction with the people involved, including unsolicited interaction
-with those enforcing the Code of Conduct, is allowed during this period.
-Violating these terms may lead to a permanent ban.
+### Code Review
 
-### 4. Permanent Ban
+- Provide constructive, specific, and actionable feedback
+- Focus on the code, not the person
+- Be patient with less experienced contributors
+- Explain the "why" behind suggestions
+- Acknowledge good practices and clever solutions
 
-**Community Impact**: Demonstrating a pattern of violation of community
-standards, including sustained inappropriate behavior,  harassment of an
-individual, or aggression toward or disparagement of classes of individuals.
+### Collaboration
 
-**Consequence**: A permanent ban from any sort of public interaction within
-the community.
+- Communicate clearly and respectfully
+- Be open to different approaches and solutions
+- Document your code and decisions
+- Help others learn and grow
+- Share knowledge generously
+
+### Quality Standards
+
+- Write clean, maintainable code
+- Follow project coding standards
+- Include appropriate tests
+- Document public APIs
+- Respect existing architectural decisions
+
+### Issue Reporting
+
+- Search for existing issues before creating new ones
+- Provide detailed reproduction steps
+- Include relevant environment information
+- Be respectful of maintainer time
+- Follow issue templates when provided
 
 ## Attribution
 
-This Code of Conduct is adapted from the [Contributor Covenant][homepage],
-version 2.0, available at
-https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org/), version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html](https://www.contributor-covenant.org/version/2/1/code_of_conduct.html).
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
+
+For answers to common questions about this code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq). Translations are available at [https://www.contributor-covenant.org/translations](https://www.contributor-covenant.org/translations).
+
+## Questions
+
+If you have questions about this Code of Conduct, please:
+
+- Review the [Contributor Covenant FAQ](https://www.contributor-covenant.org/faq)
+- Open a discussion in the project repository
+- Contact the project maintainers
+
+## Commitment
+
+We are committed to providing a welcoming and inspiring community for all. We expect all community members to follow this Code of Conduct in all project interactions.
+
+Thank you for helping make this a welcoming, friendly community for everyone.
 
-Community Impact Guidelines were inspired by [Mozilla's code of conduct
-enforcement ladder](https://github.com/mozilla/diversity).
+---
 
-[homepage]: https://www.contributor-covenant.org
+**Last Updated:** October 31, 2024  
+**Version:** 1.0.0
 
-For answers to common questions about this code of conduct, see the FAQ at
-https://www.contributor-covenant.org/faq. Translations are available at
-https://www.contributor-covenant.org/translations.