HACKING.rst: clarify that everyone needs to do the LP->GH dance (#130)

The previous language suggested that only people who had signed the CLA
previously needed to prove their GH identity, which is not the case.

1 files changed, 7 insertions, 6 deletions

diff --git a/HACKING.rst b/HACKING.rst
index c74bd5af..4ebdac17 100644
--- a/HACKING.rst
+++ b/HACKING.rst
@@ -17,12 +17,13 @@ Do these things once
   has signed.  When signing the CLA and prompted for 'Project contact' or
   'Canonical Project Manager' enter 'Josh Powers'.
 
-  For existing contributors who've already signed the agreement, we can verify
-  the link between your `Launchpad`_ account and your `GitHub`_ account by
-  creating a branch with both your Launchpad and GitHub usernames into both
-  Launchpad and GitHub cloud-init repositories.  We've added a tool
-  (tools/migrate-lp-user-to-github) to the cloud-init repository to handle this
-  migration as automatically as possible.
+  For first-time signers, or for existing contributors who have already signed
+  the agreement in Launchpad, we need to verify the link between your
+  `Launchpad`_ account and your `GitHub`_ account.  To enable us to do this, we
+  ask that you create a branch with both your Launchpad and GitHub usernames
+  against both the Launchpad and GitHub cloud-init repositories.  We've added a
+  tool (``tools/migrate-lp-user-to-github``) to the cloud-init repository to
+  handle this migration as automatically as possible.
 
   The cloud-init team will review the two merge proposals and verify
   that the CLA has been signed for the Launchpad user and record the