Skip to content

Evaluate all GL University content for best use (remove vs. move and/or update)

Issue

  • There are just a few pages in /university/
  • We're splitting the source of truth
  • By having technical articles, we supply the necessity of having the /university/

Proposal

Either we incorporate the articles into doc/university, or we get rid of GL university as planned a while ago.

If we stick with the decision of removing university, I propose:

That's all the content we have in /university/.

Update 2/13/2018 (@mikelewis)

Current content

├── README.md
├── bookclub
│   ├── booklist.md
│   └── index.md
├── glossary
│   └── README.md
├── high-availability
│   └── aws
│       └── README.md
├── process
│   └── README.md
├── support
│   └── README.md
└── training
    ├── end-user
    │   └── README.md
    ├── gitlab_flow
    │   ├── feature_branches.png
    │   ├── production_branch.png
    │   └── release_branches.png
    ├── gitlab_flow.md
    ├── index.md
    ├── logo.png
    ├── topics
    │   ├── agile_git.md
    │   ├── bisect.md
    │   ├── cherry_picking.md
    │   ├── env_setup.md
    │   ├── explore_gitlab.md
    │   ├── feature_branching.md
    │   ├── getting_started.md
    │   ├── git_add.md
    │   ├── git_intro.md
    │   ├── git_log.md
    │   ├── gitlab_flow.md
    │   ├── merge_conflicts.md
    │   ├── merge_requests.md
    │   ├── rollback_commits.md
    │   ├── stash.md
    │   ├── subtree.md
    │   ├── tags.md
    │   └── unstage.md
    └── user_training.md
Edited by Achilleas Pipinellis