Merge branch 'main' into remove-qemu-tests

Author: Githubguy132010

.github/copilot-instructions.md

@@ -126,3 +126,17 @@ Promoting ethics and social responsibility must be an integral part of the devel
     - Risky patterns and potential security issues must be explicitly flagged with warning annotations to ensure developers are aware of the implications.
     - Promoting ethics and social responsibility must be an integral part of the development culture, with attention to minimizing harmful impacts and maximizing positive societal contributions.
 
+### Best Practices for Writing Clear and Concise Documentation
+
+To write clear and concise documentation, follow these best practices:
+
+1. **Use clear and simple language**: Avoid jargon and complex sentences. Write in a way that is easy to understand for all users.
+2. **Be concise**: Keep your documentation brief and to the point. Avoid unnecessary information and focus on what is essential.
+3. **Organize content logically**: Structure your documentation in a logical order. Use headings, subheadings, and bullet points to break down information into manageable sections.
+4. **Provide examples**: Include examples to illustrate how to use the software or perform specific tasks. This helps users understand the instructions better.
+5. **Use consistent formatting**: Maintain a consistent style throughout the documentation. Use the same font, headings, and bullet points to make the document look professional and easy to read.
+6. **Include troubleshooting tips**: Add a section for common issues and their solutions. This helps users resolve problems quickly without needing additional support.
+7. **Update regularly**: Keep the documentation up to date with the latest changes in the software. Regularly review and revise the content to ensure its accuracy.
+8. **Use visuals**: Incorporate diagrams, screenshots, and other visuals to help explain complex concepts. Visual aids can make the documentation more engaging and easier to understand.
+9. **Provide links to additional resources**: Include links to related documentation, tutorials, and other resources that can help users learn more about the software.
+10. **Review and edit**: Proofread the documentation for grammar and spelling errors. Have someone else review it to ensure clarity and completeness.

CONTRIBUTING.md

@@ -48,3 +48,26 @@ By contributing, you agree that your contributions will be licensed under its Li
 
 ## References
 This document was adapted from the open-source contribution guidelines for [Facebook's Draft](https://github.com/facebook/draft-js/blob/a9316a723f9e918afde44dea68b5f9f39b7d9b00/CONTRIBUTING.md).
+
+## Testing and Documentation Updates
+
+When contributing to this project, please ensure that your code is well-tested and that the documentation is up to date. Here are some guidelines:
+
+1. **Write Tests**: If you've added code that should be tested, add tests to cover the new functionality. Use the existing test suite as a reference.
+2. **Update Documentation**: If you've changed APIs or added new features, update the documentation accordingly. This includes the `README.md` file and any other relevant documentation files.
+3. **Run Tests**: Ensure that the test suite passes before submitting your pull request. This helps maintain the stability of the project.
+
+## Coding Standards
+
+To maintain consistency and readability in the codebase, please adhere to the following coding standards:
+
+1. **Follow Conventions**: Use camelCase for variable and function names, and PascalCase for class names. Follow the existing style in the codebase.
+2. **Use Comments**: Add comments to explain complex logic and algorithms. This helps other contributors understand your code.
+3. **Keep Functions Small**: Write small, modular functions that serve a single responsibility. This enhances reusability and simplifies bug fixes or extensions.
+4. **Avoid Nested Functions**: Avoid overly nested functions or methods to limit cyclomatic complexity.
+5. **Validate Inputs**: Ensure that all inputs are thoroughly validated before being processed within the application.
+6. **Handle Errors Gracefully**: Implement robust error handling to provide clear messages and logging mechanisms that enable developers to quickly locate and resolve issues.
+7. **Optimize Performance**: Write code with algorithmic efficiency in mind. Avoid redundant iterations and use efficient data structures where appropriate.
+8. **Maintain Security**: Avoid known vulnerabilities, such as SQL injection and buffer overflows. Use prepared statements and avoid vulnerable APIs.
+9. **Document Your Code**: Each function should be accompanied by clear and concise documentation describing its functionality and limitations. Include example implementations for practical application.
+10. **Review and Edit**: Proofread your code for clarity and completeness. Have someone else review it to ensure it meets the project's standards.

README.md

@@ -229,3 +229,40 @@ You can download the latest ISO from the [releases page](https://github.com/Gith
 ## License
 
 This project is licensed under my custom license - see the [LICENSE](LICENSE) file for details.
+
+---
+
+## Setting Up the Development Environment
+
+To set up the development environment for this project, follow these steps:
+
+1. **Ensure you have Docker installed on your system**. Refer to the instructions in the `README.md` for Docker installation on different operating systems.
+2. **Clone the repository**:
+   ```bash
+   git clone https://github.com/Githubguy132010/Arch-Linux-without-the-beeps.git
+   cd Arch-Linux-without-the-beeps
+   ```
+3. **Build the Docker image**:
+   ```bash
+   docker build -t arch-iso-builder .
+   ```
+4. **Run the Docker container to build the ISO**:
+   ```bash
+   docker run --rm --privileged -v $(pwd):/workdir arch-iso-builder bash -c "mkarchiso -v -w workdir/ -o out/ ."
+   ```
+5. **Retrieve the ISO from the `out/` directory in your local folder**.
+
+For more detailed instructions, refer to the `README.md` file. If you encounter any issues, check the troubleshooting section in the same file.
+
+---
+
+## Additional Resources for New Contributors
+
+To help new contributors get started with the project, the following additional resources are available:
+
+- **Detailed setup instructions**: Ensure the `README.md` file includes comprehensive steps for setting up the development environment, including Docker installation and common troubleshooting tips.
+- **Contribution guidelines**: Expand the `CONTRIBUTING.md` file to include more specific details on testing, documentation updates, and coding standards.
+- **Code of conduct**: Add a `CODE_OF_CONDUCT.md` file to outline the expected behavior and guidelines for contributors.
+- **Issue and pull request templates**: Ensure the `.github/ISSUE_TEMPLATE/` directory contains templates for bug reports and feature requests to standardize submissions.
+- **Security policy**: Include a `SECURITY.md` file to provide guidelines on reporting vulnerabilities and the project's security measures.
+- **Additional resources**: Provide links to relevant documentation, tutorials, and other resources that can help contributors learn more about the project and its dependencies.