Record teardown/test of GitLab Basics docs

Attempt to use https://docs.gitlab.com/ee/gitlab-basics/ as a new user, walking through all the steps, and record video of the progress, narrating as you go.

Join your own Zoom call, share your screen, and record. Make sure to do a quick test recording first and ensure it looks/sounds good.

This can be broken up into multiple sections/videos if it's too much for one session.

@eread or I will then turn your videos into notes. This should result in a list of items that were unclear, poorly organized, or didn't work; and ideas for fixes and improvements.

During the video:

• You can read the doc to yourself in realtime, but intersperse narration of any thoughts about the doc, anything missing/unclear, and any actions you are taking to test the usage of the doc on your computer or in GitLab itself.

Recordings:

Recordings are uploaded to the "GitLab Unfiltered" YouTube channel on completion.

Notes:
https://docs.google.com/document/d/1Jk07dYpOuypGUa6XHuTsIUvmxQy3_Napr-VLErshEek/

Videos:
https://www.youtube.com/channel/UCMtZ0sc1HHNtGGWZFDRTh5A/search?query=%22GitLab+basics%22+docs

changed milestone to %11.10

added documentation label

changed the description

changed the description

I have completed a teardown/test of the following documents so far:

• https://docs.gitlab.com/ee/gitlab-basics/
• https://docs.gitlab.com/ee/gitlab-basics/command-line-commands.html
• https://docs.gitlab.com/ee/gitlab-basics/start-using-git.html

Each session has been recorded as a 1-person Zoom meeting, and all recordings are available in the following folder: https://drive.google.com/drive/folders/1A-DM5tYtvNPeUUgjO9otl9o8V2tdxgWK

Update: The videos are now being uploaded to the GitLab Unfiltered YouTube channel.

changed the description

changed the description

I have now uploaded the videos to the GitLab Unfiltered Youtube channel. Please view them there as I will remove them from the Google Drive folder.

GitLab Basics

https://youtu.be/FSxCW75am0o

Start using Git on the command line

https://youtu.be/xY99ZpTrc2U

Command line basic commands

https://youtu.be/DglPwjs9XiA

I recorded twice a video for topic "Create and add your SSH Keys" but in the first recording my headset was not recording audio correctly, and in the second there was some personally identifiable information. I will record that session again.

I have successfully recorded the video for "Create and add your SSH Keys" again.

Create and add your SSH Keys

https://youtu.be/P4yaGtPrJrg

Videos are yet to be produced for the following topics:

• Create a project
• Create a group
• Create a branch
• Fork a project
• Add a file
• Add an image
• Create an issue
• Create a merge request

changed the description

changed the description

added to epic &1179

I've added a link in the issue description for a YouTube search that displays the current videos.

@eread would you have time to get started on converting these to notes/issues, and I'll pick up whatever you can't get done before your time off?

I created an epic &1179. I'm thinking that rather than use the Google Doc and then creating issues off of that, that we could instead simply create one issue per teardown video and log problems found (and potentially also proposed resolutions for each). What do you think?

mentioned in epic &1179

mentioned in issue #60251 (moved)

marked this issue as related to #60251 (moved)

mentioned in issue #60254 (moved)

marked this issue as related to #60254 (moved)

I have recorded a video for the "Create a project" documentation.

Create a project

https://youtu.be/e9lCeFQpDZs

I have recorded a video for the "Create a group" documentation.

Create a group

https://youtu.be/7OwGuAfbFPY

I have recorded 2 more videos.

Create a branch

https://youtu.be/NcANCJ7LZ8

Fork a project

https://youtu.be/bLa7iWziT14

Videos are yet to be recorded for the following topics:

• Add a file
• Add an image
• Create an issue
• Create a merge request

I have recorded a video for the Add a file content.

https://youtu.be/cvyx7-RyCeE

I have recorded a video for the Add an image content.

https://youtu.be/Eqtpo6bHl5g

I have recorded a video for the Create an issue content.

https://youtu.be/YJ6Dn1ZPXag

I have recorded a video for the Create a merge request content.

https://youtu.be/vD46KDjTGSU

I have recorded videos for each piece of content linked from the GitLab basics documentation page.

marked this issue as related to #61225 (closed)

marked this issue as related to #61227 (moved)

marked this issue as related to #61229 (moved)

added devopscreate docs-only labels

Milestone %11.10 has expired, this will be rescheduled to the next milestone in active development %12.0. If you think this is incorrect, please feel free to update the milestone to a more appropriate one.

We're also adding missed:11.10

changed milestone to %12.0

added missed:11.10 label

mentioned in issue #62132 (closed)

changed milestone to %12.1

mentioned in issue #65094 (closed)

changed milestone to %12.2

added missed:12.1 label

mentioned in issue #66572 (closed)

mentioned in issue #66594 (closed)

changed milestone to %12.3

added missed:12.2 label

mentioned in issue #66618 (closed)

changed milestone to %12.4

Hey!

GitLab is moving all development for both GitLab Community Edition and Enterprise Edition into a single codebase. The current gitlab-ce repository will become a read-only mirror, without any proprietary code. All development is moved to the current gitlab-ee repository, which we will rename to just gitlab in the coming weeks. As part of this migration, issues will be moved to the current gitlab-ee project.

If you have any questions about all of this, please ask them in our dedicated FAQ issue.

https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

You can also find more information here:

• https://gitlab.com/gitlab-org/gitlab-ee/issues/13304
• https://about.gitlab.com/2019/08/23/a-single-codebase-for-gitlab-community-and-enterprise-edition/

Frequently Asked Questions

For an up to date list of questions and answers, please take a look at https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

What will we do with the repository names?

https://gitlab.com/gitlab-org/gitlab-ee/ will become https://gitlab.com/gitlab-org/gitlab, and https://gitlab.com/gitlab-org/gitlab-ce will become https://gitlab.com/gitlab-org/gitlab-foss.

Why rename gitlab-ce to gitlab-foss?

Using "gitlab" and "gitlab-ce" would be confusing, so we decided to rename gitlab-ce to gitlab-foss to make the purpose of this FOSS repository more clear

I created a merge requests for CE, and this got closed. What do I need to do?

You will need to create a merge request at https://gitlab.com/gitlab-org/gitlab-ee/. This link will eventually redirect to https://gitlab.com/gitlab-org/gitlab.

How does the licensing work in this new setup?

Everything in the ee/ directory is proprietary. Everything else is free and open source software. If your merge request does not change anything in the ee/ directory, the process of contributing changes is the same as when using the gitlab-ce repository.

Will you accept merge requests on the gitlab-ce/gitlab-foss project after it has been renamed?

No. Merge requests submitted to this project will be closed automatically.

Will I still be able to view old issues and merge requests in gitlab-ce/gitlab-foss?

Yes.

How will this affect users of GitLab CE using Omnibus?

No changes will be necessary, as the packages built remain the same.

How will this affect users of GitLab CE that build from source?

Once the project has been renamed, you will need to change your Git remotes to use this new URL. GitLab will take care of redirecting Git operations so there is no hard deadline, but we recommend doing this as soon as the projects have been renamed.

Where can I see a timeline of the remaining steps?

https://gitlab.com/gitlab-org/gitlab-ee/issues/13304

Will community contributions submitted to the new "gitlab" repository be available in the new gitlab-foss repository?

Yes, these changes will be synced to gitlab-foss automatically, several times per day.

locked this issue