commit 5701f71ba9fecca4170a050d91c59e17a89b5f02
parent d3a87305a53088edcdaadccc90cf637c11c6ecf9
Author: Amit Dutta <amitdutta4255@gmail.com>
Date: Tue, 16 Dec 2025 12:51:30 +0530
[202-12-16] .\CODE_OF_CONDUCT.md, CONTRIBUTING.md : Updated as per the rules of ESAL-1.0
Diffstat:
2 files changed, 30 insertions(+), 24 deletions(-)
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
@@ -1,18 +1,17 @@
-# Contributor Covenant Code of Conduct
----
+# Code of Conduct
## Our Pledge
-In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+I am committed to making this repository a welcoming and respectful place for learning and discussion.
-## Our Standards
+## Expectations
-Examples of behavior that contributes to a positive environment include:
+* **Be Respectful:** Treat others with kindness and respect in Issues and Discussions.
+* **Academic Integrity:** Do not use this platform to facilitate cheating or academic dishonesty.
+* **Constructive Feedback:** Criticism should be helpful and focused on the code, not the person.
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
+## Enforcement
-This project is a personal learning project, and I ask that all interactions remain respectful and constructive. Thank you for your consideration.-
\ No newline at end of file
+As the repository owner, I reserve the right to remove any comments, issues, or pull requests that violate these standards or the academic integrity goals of this project.
+
+Thank you for being a responsible part of this learning journey.+
\ No newline at end of file
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -1,19 +1,26 @@
# Contributing to bsc
-Thank you for your interest in contributing to this repository! As this is a personal learning project, I'm happy to receive feedback and suggestions.
+Thank you for your interest in improving this repository!
+
+While this is a personal academic repository protected by the **Educational Source-Available License (ESAL-1.0)**, I welcome constructive feedback, bug reports, and suggestions for optimization.
+
+## ⚠️ Important Legal Notice for Contributors
+
+By submitting a Pull Request (PR) or code snippet to this repository, you agree to the following terms:
+
+1. **License Agreement:** You acknowledge that your contribution will be governed by the **[ESAL-1.0 License](LICENSE)**. You are *not* contributing under an open-source license like MIT or GPL.
+2. **Originality:** You certify that the code you submit is your own original work and does not violate any academic integrity policies of your institution.
+3. **Rights:** You grant Amit Dutta (the repository owner) the perpetual right to use, modify, and distribute your contribution as part of this project.
## How to Contribute
-1. **Fork the Repository:** Start by forking this repository to your own GitHub account.
-2. **Create a New Branch:** Create a new branch for your changes (e.g., `git checkout -b feature-my-awesome-feature`).
-3. **Make Your Changes:** Write your code, solve a problem, or add a new example or a problem.
-4. **Commit Your Changes:** Commit your changes with a clear and descriptive message.
-5. **Submit a Pull Request:** Push your branch to your forked repository and open a pull request. In the pull request description, please explain the changes you've made.
+1. **Report Bugs:** If you find an error in a solution, please open an **Issue** rather than a PR, unless the fix is trivial.
+2. **Suggest Improvements:** If you have a more efficient algorithm, feel free to share it in an Issue or a PR.
+3. **Documentation:** Typos and clarity improvements are always welcome.
-## What to Contribute
+## What NOT to Contribute
-* **Bug Fixes:** If you find any mistakes in the code or a program that isn't working correctly.
-* **New Code Examples:** If you have a cleaner or more efficient solution to an existing problem.
-* **Documentation Improvements:** If you find a typo or a way to make the README or other files clearer.
+* **Plagiarized Code:** Do not submit code copied from textbooks, other students, or online sources without attribution.
+* **Homework Solutions:** Do not submit solutions to *active* assignments from WBSU or other institutions that differ from the ones already present, as this could facilitate cheating.
-Thank you for your help!-
\ No newline at end of file
+Thank you for helping keep this resource accurate and high-quality!+
\ No newline at end of file
