Change the name of the Kitware contact (RobotLocomotion#15239)

doc/_pages/buildcop.md

@@ -230,8 +230,7 @@ Infrastructure flakes will be red in Jenkins. If you believe you are looking at
 an infrastructure flake, run the build manually at HEAD. If it passes, you are
 definitely looking at an infrastructure flake, and no further action is
 required. If you believe the rate of a particular infrastructure flake has
-increased, alert Kitware by assigning a GitHub issue to both @BetsyMcPhail and
-@jamiesnape.
+increased, alert Kitware by assigning a GitHub issue to `@BetsyMcPhail`.
 
 Note that "slow read" warnings during Bazel builds are due to the relative
 slowness of the remote storage used by the CI infrastructure when compared to
@@ -249,13 +248,12 @@ could crash or become wedged.  During infrastructure collapses, lots of builds
 will turn red and stay red.
 
 Attempt to figure out what infrastructure collapsed. If it's under our control,
-alert Kitware by assigning a GitHub issue to both @BetsyMcPhail and
-@jamiesnape. If it's under a vendor's control, spread the news and simply wait
-it out.
+alert Kitware by assigning a GitHub issue to `@BetsyMcPhail`. If it's under a
+vendor's control, spread the news and simply wait it out.
 
 ## Drake External Examples
 
 Details of failures in the [drake-external-examples](https://github.com/RobotLocomotion/drake-external-examples/)
 repository, which may be denoted by red "build failing" icons at the top of the build
 dashboard on Jenkins, should be posted to the [#buildcop](https://drakedevelopers.slack.com/messages/buildcop/details/)
-channel on Slack, ensuring that @jamiesnape is mentioned in the message.
+channel on Slack, ensuring that `@betsymcphail` is mentioned in the message.

doc/_pages/issues.md

@@ -32,7 +32,7 @@ their responsibilities are:
   systems framework
 
 * ``kitware``
-  * lead: jamiesnape
+  * lead: BetsyMcPhail
   * responsibilities: build, continuous integration
 
 * ``manipulation``

doc/_pages/jenkins.md

@@ -109,8 +109,8 @@ unprovisioned experimental builds, e.g.:
 * ``@drake-jenkins-bot mac-catalina-unprovisioned-clang-bazel-experimental-release please``
 
 After this has passed, go through normal review. Once normal review is done,
-add ``@jamiesnape`` for review and request that the provisioned instances be
-updated. He will then respond on when it is appropriate to merge the PR.
+add `@BetsyMcPhail` for review and request that the provisioned instances be
+updated. She will then respond on when it is appropriate to merge the PR.
 
 ## Building Binary Packages on Demand
 

doc/_pages/release_playbook.md

@@ -140,8 +140,8 @@ the main body of the document:
     1. Check that the link to drake.mit.edu docs from the GitHub release draft
        page actually works.
     2. Click "Publish release"
-    3. Notify ``@jamiesnape`` via a GitHub comment to manually tag docker images
-       and upload the releases to S3. Be sure to provide him with the binary
+    3. Notify `@BetsyMcPhail` via a GitHub comment to manually tag docker images
+       and upload the releases to S3. Be sure to provide her with the binary
        date, commit SHA, and release tag in the same ping.
     4. Announce on Drake Slack, ``#general``.
     5. Party on, Wayne.

tools/workspace/drake_visualizer/repository.bzl

@@ -31,8 +31,6 @@ Argument:
 
 load("@drake//tools/workspace:os.bzl", "determine_os")
 
-# TODO(jamiesnape): Publish scripts used to create binaries. There will be a CI
-# job for developers to build new binaries on demand.
 def _impl(repository_ctx):
     os_result = determine_os(repository_ctx)
     if os_result.error != None: