4.10

Author: Bugfish

.gitattributes

@@ -14,11 +14,42 @@
 *.lang text eol=lf
 *.txt text eol=lf
 *.md text eol=lf
-*.bat text eol=lf
+*.bat text eol=crlf
+*.sh text eol=lf
+*.bash text eol=lf
+*.pl text eol=lf
+*.py text eol=lf
+*.json text eol=lf
+*.xml text eol=lf
+*.yml text eol=lf
+*.yaml text eol=lf
 
 # Denote all files that are truly binary and should not be modified.
 *.ico binary
 *.png binary
 *.jpg binary
+*.jpeg binary
+*.gif binary
+*.bmp binary
+*.tiff binary
+*.tif binary
 *.odt binary
 *.odf binary
+*.pdf binary
+*.zip binary
+*.tar binary
+*.gz binary
+*.7z binary
+*.rar binary
+*.mp3 binary
+*.wav binary
+*.flac binary
+*.mp4 binary
+*.mov binary
+*.avi binary
+*.mkv binary
+*.exe binary
+*.dll binary
+*.woff binary
+*.woff2 binary
+*.eot binary

.github/CODE_OF_CONDUCT.md

@@ -1,17 +1,11 @@
 # 🤝 Code of Conduct  
 
-We’re on a mission to create groundbreaking solutions, pushing the boundaries of technology. By being here, you’re an integral part of that journey. 
+We’re focused on developing innovative solutions and advancing technology. By being part of this, you contribute to our progress.
 
-**Positive Guidelines:**
-- Be kind, empathetic, and respectful in all interactions.
-- Engage thoughtfully, offering constructive, solution-oriented feedback.
-- Foster an environment of collaboration, support, and mutual respect.
+Positive guidelines include being kind, empathetic, and respectful in all interactions. It is important to engage thoughtfully and offer constructive, solution-oriented feedback. Fostering an environment of collaboration, support, and mutual respect is essential.
 
-**Unacceptable Behavior:**
-- Harassment, hate speech, or offensive language.
-- Personal attacks, discrimination, or any form of bullying.
-- Sharing private or sensitive information without explicit consent.
+Unacceptable behaviors include harassment, hate speech, or offensive language. Personal attacks, discrimination, or any form of bullying are not tolerated. Sharing private or sensitive information without explicit consent is strictly prohibited.
 
-Let’s collaborate, inspire one another, and build something extraordinary together!
+Together, we can partner to achieve common goals by following guidelines designed to promote effective collaboration and positive teamwork.
 
 🐟 Bugfish

.github/CONTRIBUTING.md

@@ -2,18 +2,19 @@
 
 I am excited that you're considering contributing to our project! Here are some guidelines to help you get started.
 
-## How to Contribute
+We primarily accept security fixes and critical patches to maintain project stability and coherence. Feature updates are not accepted to preserve our backend architecture and overall project integrity.
 
-1. Fork the repository to create your own copy.
-2. Create a new branch for your work (e.g., `feature/my-feature`).
-3. Make your changes and ensure they work as expected.
-4. Run tests to confirm everything is functioning correctly.
-5. Commit your changes with a clear, concise message.
-6. Push your branch to your forked repository.
-7. Submit a pull request with a detailed description of your changes.
-8. Reference any related issues or discussions in your pull request.
+Below is an example of how to contribute to this GitHub project. Please follow this guideline and all other contribution rules carefully; otherwise, your request may be denied.
 
-## Coding Style
+- Fork the repository to create your own copy.
+- Create a new branch for your changes (e.g., feature/my-feature).
+- Make your changes and verify everything works correctly.
+- Commit your changes with clear and concise messages.
+- Push your branch to your forked repository.
+- Open a pull request to the main repository’s main branch with a detailed description of your changes.
+- Reference any related issues or discussions in your pull request.
+
+To ensure your implementation is effective and maintainable by other developers, please follow the code quality guidelines outlined below.
 
 - Keep your code clean and well-organized.
 - Add comments to explain complex logic or functions.
@@ -23,8 +24,6 @@ I am excited that you're considering contributing to our project! Here are some
 - Avoid code duplication by reusing existing functions or modules.
 - Ensure your code is easily readable and maintainable by others.
 
-## Issues
-
 If you encounter a bug or have an enhancement suggestion, please check the "Issues" section of our GitHub repository or visit our official website for guidance before beginning any work on it.
 
 🐟 Bugfish

.gitignore

@@ -1,10 +1,5 @@
 # This is just an internal File to ignore Files during git operations
 
-# Block a File
-# folder/file.php
-# Block a Folder
-# folder/
-
 # Ignore all htaccess & htpasswd Files
-# **/.htaccess*
-# **/.htpasswd*
+**/.htaccess*
+**/.htpasswd*

CONTRIBUTING.md

@@ -2,18 +2,19 @@
 
 I am excited that you're considering contributing to our project! Here are some guidelines to help you get started.
 
-## How to Contribute
+We primarily accept security fixes and critical patches to maintain project stability and coherence. Feature updates are not accepted to preserve our backend architecture and overall project integrity.
 
-1. Fork the repository to create your own copy.
-2. Create a new branch for your work (e.g., `feature/my-feature`).
-3. Make your changes and ensure they work as expected.
-4. Run tests to confirm everything is functioning correctly.
-5. Commit your changes with a clear, concise message.
-6. Push your branch to your forked repository.
-7. Submit a pull request with a detailed description of your changes.
-8. Reference any related issues or discussions in your pull request.
+Below is an example of how to contribute to this GitHub project. Please follow this guideline and all other contribution rules carefully; otherwise, your request may be denied.
 
-## Coding Style
+- Fork the repository to create your own copy.
+- Create a new branch for your changes (e.g., feature/my-feature).
+- Make your changes and verify everything works correctly.
+- Commit your changes with clear and concise messages.
+- Push your branch to your forked repository.
+- Open a pull request to the main repository’s main branch with a detailed description of your changes.
+- Reference any related issues or discussions in your pull request.
+
+To ensure your implementation is effective and maintainable by other developers, please follow the code quality guidelines outlined below.
 
 - Keep your code clean and well-organized.
 - Add comments to explain complex logic or functions.
@@ -23,8 +24,6 @@ I am excited that you're considering contributing to our project! Here are some
 - Avoid code duplication by reusing existing functions or modules.
 - Ensure your code is easily readable and maintainable by others.
 
-## Issues
-
 If you encounter a bug or have an enhancement suggestion, please check the "Issues" section of our GitHub repository or visit our official website for guidance before beginning any work on it.
 
 🐟 Bugfish

_changelogs/4.10.html

@@ -0,0 +1 @@
+<b>Release 4.10</b><br />  - Bugfish Framework 4.10 update on dolibarr module