Lab3 & Lab4

Signed-off-by: Dmitriy Creed <[email protected]>

Author: Cre-eD

lab3/README.md

@@ -0,0 +1,39 @@
+# Version Control
+
+In this lab, you will learn about version control systems and their importance in collaborative software development. You will specifically focus on Git, one of the most widely used version control systems. Follow the tasks below to complete the lab assignment.
+
+## Task 1: Understanding Version Control Systems
+
+**To achieve a grade of 6/10**, follow these steps:
+
+1. Conduct research to understand the concept of version control systems and their significance in collaborative software development.
+2. Create a Markdown file named "VersionControl.md" in the lab3 folder and provide the following information:
+   - Definition of version control systems and their purpose
+   - Explanation of the benefits and advantages of using version control in a collaborative environment
+   - Overview of different types of version control systems (centralized, distributed, etc.)
+   - Comparison of popular version control systems (Git, Subversion, Mercurial, etc.)
+3. Use your own words to explain the concepts and provide examples to support your explanations.
+
+## Task 2: Practice with Git Reset Command
+
+**To earn an additional 4 points**, follow these steps to practice using different ways to use the `git reset` command:
+
+1. Create a new branch named "git-reset-practice" in your Git repository.
+2. Perform the following actions on the branch:
+   a. Make several commits with different changes to a file.
+   b. Use `git reset` with different options (soft, mixed, hard) to undo the commits and observe the changes.
+   c. Experiment with resetting to a specific commit using commit hashes or relative references (e.g., HEAD~2).
+   d. Take note of the differences and outcomes of each `git reset` variation.
+3. Document your practice in a Markdown file named "GitResetPractice.md" in the lab3 folder and include the following details:
+   - Steps you took to perform the Git reset operations.
+   - Description of the different `git reset` options used and their effects.
+   - Examples and outputs of the commands executed.
+   - Reflection on the benefits and use cases of the `git reset` command in version control workflows.
+
+### Guidelines
+
+- Use proper Markdown formatting and structure for the documentation files.
+- Organize the files within the lab folder using appropriate naming conventions.
+- Create a Pull Request to the main branch of the repository with your completed lab assignment.
+
+> Note: It is crucial to actively practice and experiment with the `git reset` command during this lab to gain hands-on experience and a better understanding of its functionalities in version control workflows.

lab4/README.md

@@ -0,0 +1,40 @@
+# Software Distribution
+
+In this lab, you will explore software distribution strategies and best practices. You will gain insights into the different approaches used to distribute software and understand the importance of effective software distribution in the development lifecycle. Follow the tasks below to complete the lab assignment.
+
+## Task 1: Research Software Distribution Strategies
+
+**To achieve a grade of 6/10**, follow these steps:
+
+1. Conduct research to understand the various software distribution strategies employed in the industry.
+2. Create a Markdown file named "SoftwareDistributionStrategies.md" in the lab4 folder and provide the following information:
+   - Definition of software distribution and its significance
+   - Different software distribution strategies and their characteristics
+   - Best practices for software distribution
+
+3. Use your own words to describe the concepts and provide relevant examples to support your explanations.
+
+## Task 2: Install Docker and Docker Compose
+
+To earn an additional 4 points, follow these steps to install Docker and Docker Compose from pip and include the versions in your report:
+
+1. Install Docker:
+   - Use the appropriate command to install Docker using pip.
+   - Provide the version number of Docker in your report.
+
+2. Install Docker Compose:
+   - Use the appropriate command to install Docker Compose using pip.
+   - Include the version number of Docker Compose in your report.
+
+3. Document your installation process in a Markdown file named "DockerInstallation.md" in the lab4 folder and include the following details:
+   - The commands or steps you followed to install Docker and Docker Compose.
+   - The version number of Docker and Docker Compose you installed.
+   - Any observations or challenges you encountered during the installation process.
+
+### Guidelines
+
+- Use proper Markdown formatting and structure for the documentation files.
+- Organize the files within the lab folder using appropriate naming conventions.
+- Create a Pull Request to the main branch of the repository with your completed lab assignment.
+
+> Note: It is essential to actively explore the software distribution strategies.