GitLab: partial user content

Author: ben

en/book/04-git-server/chapter4.asc

@@ -665,6 +665,7 @@ Removing a user can be done in two ways.
 ``Destroying'' a user, on the other hand, completely removes them from the database and filesystem. All projects and data in their namespace is removed, and any groups they own will also be removed.
 This is obviously a much more permanent and destructive action, and its uses are rare.
 
+[[_gitlab_groups_section]]
 ===== Groups
 
 A GitLab group is an assemblage of projects, along with data about how users can access those projects.
@@ -710,16 +711,43 @@ This is typically used for system status information (_"The server will be under
 
 ==== Basic Operation
 
-* Creating a project
-* Connecting with git
-* Web UI
+The first thing you'll want to do with GitLab is create a new project.
+This is accomplished by clicking the ``+'' icon on the toolbar.
+You'll be asked for the project's name, which namespace it should belong to, and what its visibility level should be.
+Most of what you specify here isn't permanent, and can be re-adjusted later through the settings interface.
+Click ``Create Project'', and you're done.
+
+Once the project is created, you'll probably want to connect it with a local Git repository.
+Each project is accessible over HTTPS or SSH, either of which can be used to configure a Git remote.
+The URLs are visible at the top of the project's home page.
+For an existing local repository, this command will create a remote named `gitlab` to the hosted location:
+
+    git remote add gitlab <url>
+
+If you don't have a local copy of the repository, you can simply do this:
+
+    git clone <url>
+
+
+The web UI provides access to many useful views of the repository itself.
+Each project's home page shows recent activity, and links along the top will lead you to views of the project's files and commit log.
 
 ==== Working Together
 
-* Collaborators
-* Forks
-* Merge Requests
-* Issues
+The most basic way of working together on a GitLab project is by giving another user direct push access to the git repository.
+You can add another user to a project by going to the ``Members'' section of that project's settings, and associating the new user with an access level (the different access levels are discussed a bit in <<_gitlab_groups_section>>).
+By giving a user an access level of ``Developer'' or above, that user can push commits and branches directly to the repository with impunity.
+
+Another, more isolated way of collaboration is by using merge requests.
+This feature enables any user that can see a project to contribute to it in a controlled way.
+Users with direct access can simply create a branch, push commits to it, and open a merge request from their branch back into `master` or any other branch.
+Users who don't have push permissions for a repository can ``fork'' it (create their own copy), push commits to _that_ copy, and open a merge request from their fork back to the main project.
+This model allows the owner to be in full control of what goes into the repository and when, while allowing contributions from untrusted users.
+
+Merge requests and issues are the main units of long-lived discussion in GitLab.
+Each merge request allows a line-by-line discussion of the proposed change, as well as a general overall discussion thread.
+Both can be assigned to users, or organized into milestones.
+
 * The Wall
 
 === Gerrit