Update documentation

jrsmith3 · jrsmith3 · commit 574ad4644710 · 2014-04-09T16:58:52.000-05:00
diff --git a/feeds/all-en.atom.xml b/feeds/all-en.atom.xml
@@ -4,7 +4,7 @@
 &lt;p&gt;I intend to post updates during the proposal writing process, and I will post a debrief once the proposal has been submitted. In these posts, I will cover what worked and what didn't work.&lt;/p&gt;
 &lt;h1&gt;Motivation&lt;/h1&gt;
 &lt;p&gt;My experience is that the default method of collaboration is completely ad-hoc and consists of emailing various versions of documents. There typically is not a central location, such as a fileserver, on which documents and data are stored.&lt;/p&gt;
-&lt;p&gt;I've seen GitHub used &lt;a href=""&gt;successfully&lt;/a&gt; to coordinate the &lt;a href=""&gt;Software-Carpentry&lt;/a&gt; project. I believe that several contributors to SWC use a git or GitHub based workflow to coordinate the work in their labs.&lt;/p&gt;
+&lt;p&gt;I've seen GitHub used &lt;a href="https://github.com/swcarpentry/"&gt;successfully&lt;/a&gt; to coordinate the &lt;a href="http://software-carpentry.org"&gt;Software-Carpentry&lt;/a&gt; project. I believe that several contributors to SWC use a git or GitHub based workflow to coordinate the work in their labs.&lt;/p&gt;
 &lt;p&gt;I believe the git workflow can be applied to most parts of the proposed project and the goal is to impose this workflow in at the very beginning of the project.&lt;/p&gt;
 &lt;h1&gt;Preparation&lt;/h1&gt;
 &lt;p&gt;I've had several phone and email conversations with my collaborators, to sketch out the scope of the proposal and to get their feedback and buy-in. I have sent them drafts of a document, in PDF, that will ultimately become the proposal. This proto-proposal was prepared using LaTeX, but the whitepaper and proposal itself will be prepared using markdown.&lt;/p&gt;
diff --git a/feeds/all.atom.xml b/feeds/all.atom.xml
@@ -4,7 +4,7 @@
 &lt;p&gt;I intend to post updates during the proposal writing process, and I will post a debrief once the proposal has been submitted. In these posts, I will cover what worked and what didn't work.&lt;/p&gt;
 &lt;h1&gt;Motivation&lt;/h1&gt;
 &lt;p&gt;My experience is that the default method of collaboration is completely ad-hoc and consists of emailing various versions of documents. There typically is not a central location, such as a fileserver, on which documents and data are stored.&lt;/p&gt;
-&lt;p&gt;I've seen GitHub used &lt;a href=""&gt;successfully&lt;/a&gt; to coordinate the &lt;a href=""&gt;Software-Carpentry&lt;/a&gt; project. I believe that several contributors to SWC use a git or GitHub based workflow to coordinate the work in their labs.&lt;/p&gt;
+&lt;p&gt;I've seen GitHub used &lt;a href="https://github.com/swcarpentry/"&gt;successfully&lt;/a&gt; to coordinate the &lt;a href="http://software-carpentry.org"&gt;Software-Carpentry&lt;/a&gt; project. I believe that several contributors to SWC use a git or GitHub based workflow to coordinate the work in their labs.&lt;/p&gt;
 &lt;p&gt;I believe the git workflow can be applied to most parts of the proposed project and the goal is to impose this workflow in at the very beginning of the project.&lt;/p&gt;
 &lt;h1&gt;Preparation&lt;/h1&gt;
 &lt;p&gt;I've had several phone and email conversations with my collaborators, to sketch out the scope of the proposal and to get their feedback and buy-in. I have sent them drafts of a document, in PDF, that will ultimately become the proposal. This proto-proposal was prepared using LaTeX, but the whitepaper and proposal itself will be prepared using markdown.&lt;/p&gt;
diff --git a/feeds/blog.atom.xml b/feeds/blog.atom.xml
@@ -4,7 +4,7 @@
 &lt;p&gt;I intend to post updates during the proposal writing process, and I will post a debrief once the proposal has been submitted. In these posts, I will cover what worked and what didn't work.&lt;/p&gt;
 &lt;h1&gt;Motivation&lt;/h1&gt;
 &lt;p&gt;My experience is that the default method of collaboration is completely ad-hoc and consists of emailing various versions of documents. There typically is not a central location, such as a fileserver, on which documents and data are stored.&lt;/p&gt;
-&lt;p&gt;I've seen GitHub used &lt;a href=""&gt;successfully&lt;/a&gt; to coordinate the &lt;a href=""&gt;Software-Carpentry&lt;/a&gt; project. I believe that several contributors to SWC use a git or GitHub based workflow to coordinate the work in their labs.&lt;/p&gt;
+&lt;p&gt;I've seen GitHub used &lt;a href="https://github.com/swcarpentry/"&gt;successfully&lt;/a&gt; to coordinate the &lt;a href="http://software-carpentry.org"&gt;Software-Carpentry&lt;/a&gt; project. I believe that several contributors to SWC use a git or GitHub based workflow to coordinate the work in their labs.&lt;/p&gt;
 &lt;p&gt;I believe the git workflow can be applied to most parts of the proposed project and the goal is to impose this workflow in at the very beginning of the project.&lt;/p&gt;
 &lt;h1&gt;Preparation&lt;/h1&gt;
 &lt;p&gt;I've had several phone and email conversations with my collaborators, to sketch out the scope of the proposal and to get their feedback and buy-in. I have sent them drafts of a document, in PDF, that will ultimately become the proposal. This proto-proposal was prepared using LaTeX, but the whitepaper and proposal itself will be prepared using markdown.&lt;/p&gt;
diff --git a/pre-brief-collaborative-proposal-prep-via-github-with-non-developer-professors.html b/pre-brief-collaborative-proposal-prep-via-github-with-non-developer-professors.html
@@ -64,7 +64,7 @@
 <p>I intend to post updates during the proposal writing process, and I will post a debrief once the proposal has been submitted. In these posts, I will cover what worked and what didn't work.</p>
 <h1>Motivation</h1>
 <p>My experience is that the default method of collaboration is completely ad-hoc and consists of emailing various versions of documents. There typically is not a central location, such as a fileserver, on which documents and data are stored.</p>
-<p>I've seen GitHub used <a href="">successfully</a> to coordinate the <a href="">Software-Carpentry</a> project. I believe that several contributors to SWC use a git or GitHub based workflow to coordinate the work in their labs.</p>
+<p>I've seen GitHub used <a href="https://github.com/swcarpentry/">successfully</a> to coordinate the <a href="http://software-carpentry.org">Software-Carpentry</a> project. I believe that several contributors to SWC use a git or GitHub based workflow to coordinate the work in their labs.</p>
 <p>I believe the git workflow can be applied to most parts of the proposed project and the goal is to impose this workflow in at the very beginning of the project.</p>
 <h1>Preparation</h1>
 <p>I've had several phone and email conversations with my collaborators, to sketch out the scope of the proposal and to get their feedback and buy-in. I have sent them drafts of a document, in PDF, that will ultimately become the proposal. This proto-proposal was prepared using LaTeX, but the whitepaper and proposal itself will be prepared using markdown.</p>
