https://github.com/essammohamed1/oop_sections_s1

oop sections with cairo university students
https://github.com/essammohamed1/oop_sections_s1

Last synced: about 1 month ago
JSON representation

oop sections with cairo university students

• Host: GitHub
• URL: https://github.com/essammohamed1/oop_sections_s1
• Owner: ESSAMMOHAMED1
• Created: 2024-04-20T18:26:07.000Z (9 months ago)
• Default Branch: master
• Last Pushed: 2024-06-02T15:01:47.000Z (8 months ago)
• Last Synced: 2024-06-02T16:53:33.916Z (8 months ago)
• Language: C++
• Size: 1.18 MB
• Stars: 1
• Watchers: 1
• Forks: 3
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# Contribution Rules

## Contributing to Student Solutions

Thank you for your interest in contributing to our project! To ensure smooth collaboration, please follow these guidelines:

1. **Folder Structure:**

   - All student contributions must be placed in the `Student_Solutions` folder.

2. **Naming Conventions for Solution Folder:**

   - Create a new Folder for your solution with the following naming convention:

     ```

     OOP_Solve_TaskNumber_StudentName

     ```

     Replace `TaskNumber` with the specific task number you are solving, and `StudentName` with your own name or identifier.

     Example: `OOP_Solve_Task1_JohnDoe`

3. **File Types:**

   - For C++ solutions, ensure that your file has the `.cpp` extension.

   - Name your C++ files the same as the task name for clarity and organization.

4. **Submission Process:**

   - Fork this repository and create a new branch for your changes.

   - Place your solution file in the `Student_Solutions` folder of your branch.

   - Submit a pull request (PR) to the main repository, detailing the task you solved and any relevant information.

5. **Code Quality:**

   - Write clear and concise code that follows best practices and adheres to any project-specific coding standards.

6. **Documentation:**

   - Include comments or documentation within your code to explain your approach, algorithms used, and any other relevant information.

7. **Testing:**

   - If applicable, include test cases or instructions on how to test your solution to ensure it functions correctly.

We appreciate your contributions and look forward to seeing your solutions!