Merge branch 'kc-remove-gitober23' into 'develop'

remove gitober23 content

See merge request R3/school/courses!186

2023/2023-10-03_gitober-part1/slides/index.md

-# R3.school
-
-## October 3rd, 2023
-
-<div style="top: 6em; left: 0%; position: absolute;">
-    <img src="theme/img/lcsb_bg.png">
-</div>
-
-<div style="top: 5em; left: 60%; position: absolute;">
-    <img src="slides/img/r3-training-logo.png" height="200px">
-    <br><br><br><br>
-    <h1>Gitober - Part I</h1>
-    <h2>Contribute using WebIDE</h2>
-    <br><br><br>
-    <h4>
-        Kaan Çimir<br>
-        R3 Team - <a href="mailto:lcsb-r3@uni.lu">lcsb-r3@uni.lu</a><br>
-        <i>Luxembourg Centre for Systems Biomedicine</i>
-    </h4>
-</div>

2023/2023-10-03_gitober-part1/slides/list.json

-[
-    { "filename": "index.md" },
-    { "filename": "versioning.md" },
-    { "filename": "what_is_git.md" },
-    { "filename": "repository.md" },
-    { "filename": "gitlab.md" },
-    { "filename": "forks.md" },
-    { "filename": "commit.md"},
-    { "filename": "branches.md" },
-    { "filename": "web-ide.md" },
-    { "filename": "merge.md" },
-    { "filename": "example.md" },
-    { "filename": "syncFork.md" },
-    { "filename": "best_practices.md" },
-    { "filename": "thanks.md" }
-]

2023/2023-10-03_gitober-part1/slides/merge.md

-# New term: <font color="color:red">merge</font>
-
-* You have made changes on your branch
-* Now you want your changes to be reflected on another branch </br>(most probably `develop`)
-
-<div style="position:absolute;left:70%;top:1em">
-<img src="slides/img/branch_merge-detail.png" height="800px" >
-</div>
-
-You have to <font color="color:red">merge</font> the branches.
-
-- Merging is directional - *Merge branch A to branch B*
-- Merging of branches is a process that is initiated via a so called **merge request** (MR):
-- Your peers can comment on your changes in a merge request **review**!
-
-
-
-# What happened in the background?
-
-<div align="center">
-<img src="slides/img/fork_branch-diagram-after-commit.png" height="600px" >
-</div>
-
-
-
-# What happened in the background?
-
-<div align="center">
-<img src="slides/img/fork_branch-diagram-after-commit-with-back-arrow.png" height="600px" >
-</div>
-
-
-
-# Merge request (MR)
-
-<img src="slides/img/icon-live-demo.png" height="100px">
-
-After *Committing*, the *Create MR* button redirects you to the submission page for your *merge request (MR)*
-
-* Propose to merge your branch into the *development* branch. This is shown at the top of the merge request page.
-<!-- .element: class="fragment" data-fragment-index="1" -->
-* Select the "develop" branch
-<!-- .element: class="fragment" data-fragment-index="2" -->
-* Fill your merge request submission form and select an Assignee.
-<!-- .element: class="fragment" data-fragment-index="5" -->
-* Under Changes tab, you can see your changes
-<!-- .element: class="fragment" data-fragment-index="5" -->
-
-![bulb](slides/img/bulb.png) Good practice is to select *Delete source branch when merge request is accepted*. Why?
-
-<div style="position:absolute;left:30%;top:1em" class="fragment fade-in-then-out" data-fragment-index="0">
-<img src="slides/img/merge-request_popup.png" width="60%" >
-</div>
-
-<div style="position:absolute;left:30%;top:10em" class="fragment fade-in-then-out" data-fragment-index="3">
-<img src="slides/img/merge-request_branches.png" width="60%" >
-</div>
-
-<div style="position:absolute;left:20%;top:20em" class="fragment fade-in-then-out" data-fragment-index="5">
-<img src="slides/img/merge-request_delete-source.png" width="70%" >
-</div>

2023/2023-10-03_gitober-part1/slides/overview.md

-# Overview
-
-0. Subject 1
-1. Subject 2

2023/2023-10-03_gitober-part1/slides/repository.md

-# New term:  <font color="color:red">repository</font>
-
-<div style="position:relative;text-align:center;top:10em">
-Project folder keeping all your files and their history
-</div>

2023/2023-10-03_gitober-part1/slides/syncFork.md

-# Synchronize your fork
-
-As mentioned earlier, your fork has been created a certain moment in time.
-
-How to keep it updated?
-
-## Easy way
-
-Delete your fork and re-create it!
-
-- Go to `Settings > General`
-- Scroll down to the `Advanced` section and expand it
-- Click on `Delete project` and follow the on-screen instructions
-
-![bulb](slides/img/bulb.png) Before you do this, please make sure that all your merge requests have been accepted.
-
-## Automatic way
-
-Follow the instructions on the How-To card: [https://howto.lcsb.uni.lu/?contribute:mirror-fork](https://howto.lcsb.uni.lu/?contribute:mirror-fork)
-
-## Alternative way
-
-The **Update fork** button on GitLab updates the current branch.
-
-<div style="position:absolute;left:50%;top:27em">
-<img src="slides/img/update_fork.png" width="50%" >
-</div>

2023/2023-10-03_gitober-part1/slides/thanks.md

-# Thank you.
-
-<center><img src="slides/img/r3-training-logo.png" height="200px"></center>
-
-Contact us if you need help:
-
-<a href="mailto:lcsb-r3@uni.lu">lcsb-r3@uni.lu</a>
-

2023/2023-10-03_gitober-part1/slides/versioning.md

-# Why use a version control system?
-
-Basic features:
-
-* Maintain different versions of documents or code
-* Ability to recover previous versions
-* Track all changes to a document or code
-
-<div style="position:absolute;left:60%;top:1em">
-<img src="slides/img/version-history_OneDrive.png" height="650px">
-</div>
-
-Common tools you are already using supporting "version control":
-
-* Owncloud
-* OneDrive
-* ...
-
-From the list of files, it is clear *who* changed which file and *when*.
-
-
-<div class="fragment">
-
-But some information is missing:
-
-- *What exactly* was changed? (which section or row?)
-- *Why* was it changed?
-
-
-
-# Why use a version control system?
-
-## Manual file versioning + CHANGELOG
-
-<br>
-
-<div style="position:absolute; width:30%">
-
-Your folder:
-```
-my-document_v01.docx
-my-document_v02.docx
-...
-my-document_v12.docx
-CHANGELOG.txt
-```
-</div>
-<div style="position:relative; left:40%; width:60%"">
-
-CHANGELOG.txt:
-```
-v01 -> v02
-- Chapter 1 updated to contain last findings
-- fixing typo on page 3
-
-v02 -> v03
-- rephrasing section 2 to adhere to standard
-- add missing diagram
-...
-```
-</div>
-
-<br>
-<br>
-
-<div class="fragment">
-
-**What exactly** has changed? - Solved!
-
-**Why** it was changed? - Solved!
-</div>
-<div class="fragment">
-Really?
-
-note: overhead for doing this manually is huge
-</div>
-
-
-
-# Using versioning system?
-
-What happens when **3** people contribute?
-
-```
-my-document_v01_AK.docx
-my-document_v01_AK_BP.docx
-my-document_v02_revised.docx
-my-document_v02_LP_revised-and-approved.docx
-my-document_v002_draft_LP-AK_do-not-touch.docx
-...
-my-document_v12_we-made-it.docx
-CHANGELOG.txt
-```
-
-<div class="fragment">
-
-What happens when **10** people contribute?

2023/2023-10-03_gitober-part1/slides/web-ide.md

-# Workflow - Web IDE
-
-To change content of a file:
-
-* Browse to *your fork*
-* Open Web IDE
-<!-- .element: class="fragment" data-fragment-index="1" -->
-* Select the "develop" branch
-<!-- .element: class="fragment" data-fragment-index="2" -->
-* Edit file content
-<!-- .element: class="fragment" data-fragment-index="3" -->
-* Commit
-<!-- .element: class="fragment" data-fragment-index="4" -->
-  * Click on the "Source Control" button
-  * Type your commit message
-  * Click on "Commit to new branch"
-  * Name your branch (optional, but recommended)
-  * Press 'Enter' or 'Return' to commit
-  
-
-
-  
-
-
-<div style="position:absolute;left:30%;top:1em" class="fragment fade-in-then-out" data-fragment-index="1">
-<img src="slides/img/commit_GUI_web-ide.png" width="95%" >
-</div>
-
-<div style="position:absolute;left:30%;top:1em" class="fragment fade-in-then-out" data-fragment-index="2">
-<img src="slides/img/web-ide_select-branch.png" width="80%" >
-</div>
-
-<div style="position:absolute;left:30%;top:1em" class="fragment fade-in-then-out" data-fragment-index="3">
-<img src="slides/img/web-ide_edit-file.png" width="90%" >
-</div>
-
-<div style="position:absolute;left:45%;top:1em" class="fragment fade-in-then-out" data-fragment-index="4">
-<img src="slides/img/web-ide_source-control.png" width="60%" >
-</div>
-
-<div style="position:absolute;left:67%;top:1em" class="fragment fade-in-then-out" data-fragment-index="4">
-<img src="slides/img/web-ide_commit-detail.png" width="90%" >
-</div>
-
-<div style="position:absolute;left:45%;top:20em" class="fragment fade-in-then-out" data-fragment-index="4">
-<img src="slides/img/web-ide_commit-newbranch.png" width="85%" >
-</div>

2023/2023-10-03_gitober-part1/slides/what_is_git.md

-# What is `git`?
-
-`git` is a **version control system** (VCS) for tracking changes in computer files and coordinating work on those files among multiple people [1].
-
-Designed and implemented in 2005 by **Linus Torvalds**
-
-<div align="center">
-<img src="slides/img/linus.jpg">
-</div>
-
-
-[1] *https://en.wikipedia.org/wiki/Git*
-
-
-
-## The inventor of `git`
-
-<div align="center">
-<img src="slides/img/git_definition.png">
-</div>
-
-`I'm an egotistical bastard, and I name all my projects after myself.
-First Linux, now git.`
-Linus Torvalds (2007-06-14)
-
-
-
-# What is the use of `git`?
-
-<div align="center">
-<img src="slides/img/Git-logo.png" height="120">
-</div>
-
-* Ability to recover old versions
-* No need to fully rewrite text or code; **reuse** and **save time**
-* Keep the changes you made over time (**history**) to every single line
-* Annotate each change with description
-* **Backtrack** (if necessary) and undo unwanted changes
-* Contribute content in parallel
-* Easily **add contributions** of your collaborators to any version
-
-
-note:
-
-Other points to mention:
-
-* git stems from SW development domain with >100 of people contributing to one project
-* git shall not be considered as a nuisance, but as a tool that should help to track and trace the code.
-* git is not to track performance. Not using it shows exactly the opposite.