remove liveshare section

Author: StevenClontz

source/ch-collaboration.ptx

@@ -1,52 +1,11 @@
 <?xml version='1.0' encoding='utf-8'?>
 <chapter xml:id="ch-collaboration">
   <title>Collaborating with Others</title>
-  <section xml:id="sec-liveshare">
-    <title>Live Share</title>
-    <p>
-A nice feature of collaborative authoring tools such
-as Google Docs and Overleaf is the ability for several
-collaborators to edit the same file synchronously, with
-a feature set similar to <c>GitHub.dev</c>.
-    </p>
-    <p>
-Using the Extensions sidebar, search for and install
-Microsoft's <q>Live Share</q> extension. Once installed,
-you will have a <q>Live Share</q> option in your
-bottom toolar. Clicking it will automatically copy a URL
-ending in
-<c>https://.../join?[randomStringOfCharacters]</c>.
-If you share this URL with a colleague (or
-colleagues) you trust, they will be able to collaboratively
-edit your repository's text files with you via their web
-browser. When you commit your
-changes, they will be listed as co-authors of the commit.
-    </p>
-    <remark>
-      <p>
-As of writing, my experience with LiveShare has been hit-or-miss,
-so I'll suggest another mechanism for live collaboration.
-Sometimes when I'm working on a Git repository
-with a collague on Zoom, I'll share my screen and give my collaborator
-control of my mouse and keyboard, or vice versa. Obviously
-you should only do this with a collaborator you trust, but it's
-a simple solution to quickly work together on the same repo!
-      </p>
-    </remark>
-  </section>
   <section xml:id="sec-collaborators-prs">
     <title>Collaborators and Pull Requests</title>
     <p>
-A particular downside of Live Share (<xref ref="sec-liveshare"/>)
-is that it requires
-the repository owner to create the Codespace and provision
-the Live Share session. As a result, there's no way for a
-collaborator to make a contribution via Live Share to a GitHub project
-without the active involvement of the repository owner.
-    </p>
-    <p>
-To address this, one solution is for the repository owner to
-add other GitHub users as collaborators.
+A direct way to allow multiple people you trust to work on the
+same repository is to add these GitHub users as collaborators.
     </p>
     <definition xml:id="def-collabotors">
       <statement>
@@ -89,16 +48,19 @@ must name their distinct branches.
     </warning>
     <note>
       <p>
-One workflow to support multiple collaborators on the same
+Our recommendation to support multiple collaborators on the same
 repository is to <em>never directly commit to the <c>main</c> branch</em>,
 even if you're the owner.
       </p>
       <p>
 To commit to an alternative branch in <c>GitHub.dev</c> or Codespaces, select
 <c>main</c> in the bottom toolbar, then type the name of your new branch,
-and select <q>Create new branch</q>. The name of this branch could
-be topical, e.g. <c>add-derivative-chapter</c>, but it's also fine to
-pick some other unique identifier, e.g. <c>lastname-YYYY-MM-DD</c>.
+and select <q>Create new branch</q>. It's a good idea to name your
+branch in the form <c>UserName/short-description-of-topic</c>,
+or if you're unsure of the topic, you can just use the current
+date: <c>UserName/YYYYMMDD</c>. Note that prefixing with your
+<c>UserName</c> helps prevent two people from accidentally using the same
+branch name.
       </p>
     </note>
     <p>