Merge remote-tracking branch 'origin/main'

Author: raj713335

.github/FUNDING.yml

@@ -0,0 +1,13 @@
+# These are supported funding model platforms
+
+github: ['raj713335']
+patreon: # Replace with a single Patreon username
+open_collective: # Replace with a single Open Collective username
+ko_fi: # Replace with a single Ko-fi username
+tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
+community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
+liberapay: # Replace with a single Liberapay username
+issuehunt: # Replace with a single IssueHunt username
+otechie: # Replace with a single Otechie username
+lfx_crowdfunding: # Replace with a single LFX Crowdfunding project-name e.g., cloud-foundry
+custom: ['paypal.me/raj713335']

CODE_OF_CONDUCT.md

@@ -0,0 +1,32 @@
+# Low Level Design Lld Using Python Code of Conduct
+
+Like the technical community as a whole, the Low Level Design Lld Using Python team and community is made up of a mixture of professionals and volunteers from all over the world, working on every aspect of the mission - including mentorship, teaching, and connecting people.
+
+Diversity is one of our huge strengths, but it can also lead to communication issues and unhappiness. To that end, we have a few ground rules that we ask people to adhere to. This code applies equally to founders, mentors and those seeking help and guidance.
+
+This isn’t an exhaustive list of things that you can’t do. Rather, take it in the spirit in which it’s intended - a guide to make it easier to enrich all of us and the technical communities in which we participate.
+
+This code of conduct applies to all spaces managed by the Low Level Design Lld Using Python project or . This includes IRC, the mailing lists, the issue tracker, DSF events, and any other forums created by the project team which the community uses for communication. In addition, violations of this code outside these spaces may affect a person's ability to participate within them.
+
+If you believe someone is violating the code of conduct, we ask that you report it by emailing [raj713335@gmail.com](mailto:raj713335@gmail.com). For more details please see our 
+
+- **Be friendly and patient.**
+- **Be welcoming.** We strive to be a community that welcomes and supports people of all backgrounds and identities. This includes, but is not limited to members of any race, ethnicity, culture, national origin, colour, immigration status, social and economic class, educational level, sex, sexual orientation, gender identity and expression, age, size, family status, political belief, religion, and mental and physical ability.
+- **Be considerate.** Your work will be used by other people, and you in turn will depend on the work of others. Any decision you take will affect users and colleagues, and you should take those consequences into account when making decisions. Remember that we're a world-wide community, so you might not be communicating in someone else's primary language.
+- **Be respectful.** Not all of us will agree all the time, but disagreement is no excuse for poor behavior and poor manners. We might all experience some frustration now and then, but we cannot allow that frustration to turn into a personal attack. It’s important to remember that a community where people feel uncomfortable or threatened is not a productive one. Members of the Low Level Design Lld Using Python community should be respectful when dealing with other members as well as with people outside the Low Level Design Lld Using Python community.
+- **Be careful in the words that you choose.** We are a community of professionals, and we conduct ourselves professionally. Be kind to others. Do not insult or put down other participants. Harassment and other exclusionary behavior aren't acceptable. This includes, but is not limited to: 
+ - Violent threats or language directed against another person.
+ - Discriminatory jokes and language.
+ - Posting sexually explicit or violent material.
+ - Posting (or threatening to post) other people's personally identifying information ("doxing").
+ - Personal insults, especially those using racist or sexist terms.
+ - Unwelcome sexual attention.
+ - Advocating for, or encouraging, any of the above behavior.
+ - Repeated harassment of others. In general, if someone asks you to stop, then stop.
+- **When we disagree, try to understand why.** Disagreements, both social and technical, happen all the time and Low Level Design Lld Using Python is no exception. It is important that we resolve disagreements and differing views constructively. Remember that we’re different. The strength of Low Level Design Lld Using Python comes from its varied community, people from a wide range of backgrounds. Different people have different perspectives on issues. Being unable to understand why someone holds a viewpoint doesn’t mean that they’re wrong. Don’t forget that it is human to err and blaming each other doesn’t get us anywhere. Instead, focus on helping to resolve issues and learning from mistakes.
+
+Original text courtesy of the [Speak Up! project](http://web.archive.org/web/20141109123859/http://speakup.io/coc.html).
+
+## Questions?
+
+If you have questions, please see . If that doesn't answer your questions, feel free to [contact us](mailto:raj713335@gmail.com).

CONTRIBUTING.md

@@ -0,0 +1,122 @@
+# Contributing to Low Level Design LLD Using Python
+
+Welcome to the Low Level Design LLD Using Python project!
+Thank you for taking the time to contribute. We’re excited to collaborate with fellow engineers and learners to make this a world-class resource for system design.
+
+
+## How to Contribute
+
+### 1. Fork the Repository
+
+Click the **Fork** button in the top right corner of this repo to create your copy.
+
+### 2. Clone Your Fork
+
+```bash
+$ git clone https://github.com/raj713335/Low_Level_Design_LLD_Using_Python.git
+$ cd Low_Level_Design_LLD_Using_Python
+````
+
+### 3. Create a Feature Branch
+
+```bash
+$ git checkout -b feature/your-feature-name
+```
+
+### 4. Make Your Changes
+
+* Follow the existing folder and naming conventions.
+* Keep your code clean, modular, and well-documented.
+* If adding a new algorithm:
+
+  * Place it in the appropriate section.
+  * Include comments and usage examples.
+* If updating documentation:
+
+  * Maintain consistent formatting.
+  * Use Markdown best practices.
+
+### 5. Test Your Contribution
+
+Run your code and verify it works correctly. Add edge cases and examples where appropriate.
+
+### 6. Commit and Push
+
+```bash
+$ git add .
+$ git commit -m "Add: Description of your change"
+$ git push origin feature/your-feature-name
+```
+
+### 7. Open a Pull Request
+
+Submit a pull request from your branch to the `main` branch of this repository. Fill out the PR template with:
+
+* A brief summary of your changes
+* Related issue (if applicable)
+* Screenshots or logs for UI/code changes
+
+---
+
+## Contribution Guidelines
+
+* Keep commits atomic and meaningful.
+* Use clear and descriptive names for files, folders, and variables.
+* Include docstrings/comments for all functions and algorithms.
+* Maintain cross-platform compatibility (especially for scripts).
+* Do **not** modify files unrelated to your contribution.
+* Run linters and format your code (e.g., `black`, `flake8`).
+* Contributions should be beginner-friendly and educational.
+* Add references or links for advanced concepts where needed.
+
+---
+
+## Contribution Ideas
+
+You can contribute in many ways:
+
+* Add new Low Level design patterns or algorithms.
+* Improve documentation or examples
+* Create diagrams or visuals for concepts
+* Submit bug fixes or optimizations
+* Translate content into other languages
+* Add test cases or edge scenarios
+* Create presentation slides or learning guides
+
+---
+
+## Development Setup
+
+* Python 3.7+
+* pip
+
+To install common dependencies:
+
+```bash
+pip install -r requirements.txt
+```
+
+For specific modules, refer to the README or project root guide.
+
+---
+
+## Support & Questions
+
+* Open an [Issue](https://github.com/raj713335/Low_Level_Design_LLD_Using_Python/issues) for bugs, questions, or feature requests.
+* Join discussions in the community tab or comments.
+* Please search existing issues before creating a new one.
+
+---
+
+## License
+
+By contributing, you agree that your contributions will be licensed under the [GNU Lesser General Public License v2.1](LICENSE).
+
+---
+
+## Acknowledgment
+
+Your efforts make this project better! Whether it’s code, docs, or just a bug report — **every bit helps**. Let’s build the ultimate system design masterclass together.
+
+## Happy Contributing!
+

SECURITY.md

@@ -0,0 +1,21 @@
+# Security Policy
+
+## Supported Versions
+
+Use this section to tell people about which versions of your project are
+currently being supported with security updates.
+
+| Version | Supported          |
+| ------- | ------------------ |
+| 5.1.x   | :white_check_mark: |
+| 5.0.x   | :x:                |
+| 4.0.x   | :white_check_mark: |
+| < 4.0   | :x:                |
+
+## Reporting a Vulnerability
+
+Use this section to tell people how to report a vulnerability.
+
+Tell them where to go, how often they can expect to get an update on a
+reported vulnerability, what to expect if the vulnerability is accepted or
+declined, etc.