jekyll-theme-csu-cs 0.1.4 → 0.1.5

data/_includes/helpdesk.html

@@ -1,110 +1,110 @@
-<p>The TAs will be posting hours in which they will be available on the <a href="https://www.acns.colostate.edu/microsoft-teams-students/">Microsoft Team</a>
-    for the class.</p>
-
-<p>In general, we ask that you contact us (both TAs, and the instructor) on Microsoft Teams
-    (don’t use email / canvas - unless it is a long message), this can be via direct message or general channel for open
-    questions.</p>
-
-<p>We also will be running a virtual help desk over Microsoft Teams. As the MS Teams is not designed
-    to be a help desk queue, we have developed the following procedure for asking for help.</p>
-
-<ol>
-    <li>In general chat, you should ask general questions (do NOT post your code)
-        <ul>
-            <li>You should do this <em>first</em>, as talking through a problem often helps you solve it!</li>
-            <li>Good questions to ask are “I am looking at problem X, and I think the algorithm is as follows…
-                (English line by line). What are your thoughts?”</li>
-            <li>A bad question is “I am stuck on problem X.”, as it leaves people to guess what is going on instead of helping directly.</li>
-            <li>This allows anyone in the class to help answer your question, not just TAs, building both the community
-                and larger response time.</li>
-            <li>While we say don’t post <em>your</em> code, posting algorithms is fine, or provided code from lecture / labs. It is also
-                fine to post links to help sites, as long as this is not abused.</li>
-        </ul>
-    </li>
-    <li>Coding questions
-        <ol>
-            <li>Post in general chat (during TA hours): “I have a coding question on (lab x:step y, practical x, etc)”</li>
-            <li>TAs will be going through them in order, putting a :thumbs up: emote on questions they are helping with</li>
-            <li>They will then direct message you, asking for your question
-                <ul>
-                    <li>note: response times can vary, but if you are not around when they respond, they will have to move on.</li>
-                </ul>
-            </li>
-            <li>You will then respond with your question + code.
-                <ul>
-                    <li>For a better response, don’t just send code. Instead, send a <strong>question with what you have tried</strong>, along with
-                        the code. Try explaining your code in your message.</li>
-                    <li>Remember your <a href="https://support.microsoft.com/en-ie/office/use-markdown-formatting-in-teams-4d10bd65-55e2-4b2d-a1f3-2bebdcd2c772">formatting options</a>,
-                        especially the format code option &lt;/&gt; <br />
-                        <img src="{{ "/assets/img/msteamsformat.png" | relative_url }}" alt="MS Teams Format Banner" /></li>
-                    <li>Also, if you just paste the code into Teams from your IDE, it automatically formats the code - so pretty easy to make code look nice.</li>
-                    <li>This means there is no reason to send screenshots of your code! Please don’t, they are hard to work with.</li>
-                    <li>Depending on your question, your TA may ask you to go into Teams videochat, and screen share with them. Please
-                        make sure this is <a href="https://support.office.com/en-us/article/show-your-screen-during-a-meeting-90c84e5a-b6fe-4ed4-9687-5923d230d3a7">setup correctly</a>.</li>
-                </ul>
-            </li>
-            <li>After your question is answered, your TA will put a smiley face next to the “I have a coding question…” message
-                in general chat. Please note, the answer to your question could be to try a few things, and then come back. They
-                may still put a smiley face for tracking purposes, and if they direct you to message them directly
-                after that, it is fine.</li>
-            <li>After your question is answered, we ask that you wait a bit before posting “I have a coding question” again, and if you
-                immediately continue to do that - they may move you to the bottom of the ‘queue’ in order to help other students.</li>
-        </ol>
-    </li>
-    <li>During non-standard lab times, feel free to send a direct message. TAs will answer during their office hours. TAs
-        are tagged with the TA tag.</li>
-</ol>
-
-<p>As a last reminder, the more you can have a general question, as compared to a coding question - the more
-    you will learn! We encourage general questions to all students to see and discuss.</p>
-
-<h2 id="live-sessions">Live Sessions</h2>
-<p>The TAs and Instructor will be having live sessions each week. The live session time will be scheduled in Microsoft Teams.
-    All live sessions are <strong>optional</strong>.</p>
-
-<p>Our plan is to record the stream, so you can look at it later if you are unable to make the session. This doesn’t
-    always work as we expect, but for the most part, it works fine.</p>
-
-<p>Make sure you check Teams for the scheduled times each week.</p>
-
-<h2 id="additional-debugging-advice">Additional Debugging Advice</h2>
-<p>When coding, there is a lot of debugging. We suggest the following to help / try before asking coding questions. Please
-    note that if you have general / insight question, these don’t apply. However, trying these debugging techniques before
-    asking coding questions will help you become a better programmer.</p>
-
-<ul>
-    <li>Design before you code
-        <ul>
-            <li>the best developers build a plan before coding. They figure out what they want to do, either by writing it
-                in comments or using paper. It makes a major difference.</li>
-        </ul>
-    </li>
-    <li>Talk through your code / algorithm (see ducky below)</li>
-    <li>Write code in small segments (one or two lines at a time)
-        <ul>
-            <li>make sure it compiles</li>
-            <li>toss in a System.out.println() to make sure it is doing what you think</li>
-            <li>this may mean adding extra variables</li>
-        </ul>
-    </li>
-    <li>Have a bug, use printlns liberally to figure out what is going on
-        <ul>
-            <li>this may mean commenting out sections of your code, and slowly stepping through it</li>
-            <li>we suggest using “TESTING” or “DEBUG” in whatever you print. That way, you don’t accidentally leave a print in there
-                when you submit for grading.</li>
-        </ul>
-    </li>
-</ul>
-
-<h3 id="before-asking-questions-talk-to-the-ducky">Before asking questions, talk to the ducky!</h3>
-
-<p><img src="{{"/assets/img/ducky.png" | relative_url }}" style="float:right;width:125px;padding-right:10px;padding-left:10px;padding-bottom:50px;" /></p>
-
-<p>Often the best thing you can do is explain what you are attempting to do to a friend. In the process of explaining it,
-    you usually figure out your errors, and it helps give you a direction to go from there.</p>
-
-<p>Sometimes in companies, this can be a time-cost for other developers so thus the introduction of a
-    <a href="https://en.wikipedia.org/wiki/Rubber_duck_debugging">Rubber Duck</a> for
-    testing. This gives you an object for you to talk to just like you would a friend. The object doesn’t have to give feedback
-    (just like a friend doesn’t), but instead, the process of talking through the code out loud will often provide
+<p>The TAs will be posting hours in which they will be available on the <a href="https://www.acns.colostate.edu/microsoft-teams-students/">Microsoft Team</a>
+    for the class.</p>
+
+<p>In general, we ask that you contact us (both TAs, and the instructor) on Microsoft Teams
+    (don’t use email / canvas - unless it is a long message), this can be via direct message or general channel for open
+    questions.</p>
+
+<p>We also will be running a virtual help desk over Microsoft Teams. As the MS Teams is not designed
+    to be a help desk queue, we have developed the following procedure for asking for help.</p>
+
+<ol>
+    <li>In general chat, you should ask general questions (do NOT post your code)
+        <ul>
+            <li>You should do this <em>first</em>, as talking through a problem often helps you solve it!</li>
+            <li>Good questions to ask are “I am looking at problem X, and I think the algorithm is as follows…
+                (English line by line). What are your thoughts?”</li>
+            <li>A bad question is “I am stuck on problem X.”, as it leaves people to guess what is going on instead of helping directly.</li>
+            <li>This allows anyone in the class to help answer your question, not just TAs, building both the community
+                and larger response time.</li>
+            <li>While we say don’t post <em>your</em> code, posting algorithms is fine, or provided code from lecture / labs. It is also
+                fine to post links to help sites, as long as this is not abused.</li>
+        </ul>
+    </li>
+    <li>Coding questions
+        <ol>
+            <li>Post in general chat (during TA hours): “I have a coding question on (lab x:step y, practical x, etc)”</li>
+            <li>TAs will be going through them in order, putting a :thumbs up: emote on questions they are helping with</li>
+            <li>They will then direct message you, asking for your question
+                <ul>
+                    <li>note: response times can vary, but if you are not around when they respond, they will have to move on.</li>
+                </ul>
+            </li>
+            <li>You will then respond with your question + code.
+                <ul>
+                    <li>For a better response, don’t just send code. Instead, send a <strong>question with what you have tried</strong>, along with
+                        the code. Try explaining your code in your message.</li>
+                    <li>Remember your <a href="https://support.microsoft.com/en-ie/office/use-markdown-formatting-in-teams-4d10bd65-55e2-4b2d-a1f3-2bebdcd2c772">formatting options</a>,
+                        especially the format code option &lt;/&gt; <br />
+                        <img src="{{ "/assets/img/msteamsformat.png" | relative_url }}" alt="MS Teams Format Banner" /></li>
+                    <li>Also, if you just paste the code into Teams from your IDE, it automatically formats the code - so pretty easy to make code look nice.</li>
+                    <li>This means there is no reason to send screenshots of your code! Please don’t, they are hard to work with.</li>
+                    <li>Depending on your question, your TA may ask you to go into Teams videochat, and screen share with them. Please
+                        make sure this is <a href="https://support.office.com/en-us/article/show-your-screen-during-a-meeting-90c84e5a-b6fe-4ed4-9687-5923d230d3a7">setup correctly</a>.</li>
+                </ul>
+            </li>
+            <li>After your question is answered, your TA will put a smiley face next to the “I have a coding question…” message
+                in general chat. Please note, the answer to your question could be to try a few things, and then come back. They
+                may still put a smiley face for tracking purposes, and if they direct you to message them directly
+                after that, it is fine.</li>
+            <li>After your question is answered, we ask that you wait a bit before posting “I have a coding question” again, and if you
+                immediately continue to do that - they may move you to the bottom of the ‘queue’ in order to help other students.</li>
+        </ol>
+    </li>
+    <li>During non-standard lab times, feel free to send a direct message. TAs will answer during their office hours. TAs
+        are tagged with the TA tag.</li>
+</ol>
+
+<p>As a last reminder, the more you can have a general question, as compared to a coding question - the more
+    you will learn! We encourage general questions to all students to see and discuss.</p>
+
+<h2 id="live-sessions">Live Sessions</h2>
+<p>The TAs and Instructor will be having live sessions each week. The live session time will be scheduled in Microsoft Teams.
+    All live sessions are <strong>optional</strong>.</p>
+
+<p>Our plan is to record the stream, so you can look at it later if you are unable to make the session. This doesn’t
+    always work as we expect, but for the most part, it works fine.</p>
+
+<p>Make sure you check Teams for the scheduled times each week.</p>
+
+<h2 id="additional-debugging-advice">Additional Debugging Advice</h2>
+<p>When coding, there is a lot of debugging. We suggest the following to help / try before asking coding questions. Please
+    note that if you have general / insight question, these don’t apply. However, trying these debugging techniques before
+    asking coding questions will help you become a better programmer.</p>
+
+<ul>
+    <li>Design before you code
+        <ul>
+            <li>the best developers build a plan before coding. They figure out what they want to do, either by writing it
+                in comments or using paper. It makes a major difference.</li>
+        </ul>
+    </li>
+    <li>Talk through your code / algorithm (see ducky below)</li>
+    <li>Write code in small segments (one or two lines at a time)
+        <ul>
+            <li>make sure it compiles</li>
+            <li>toss in a System.out.println() to make sure it is doing what you think</li>
+            <li>this may mean adding extra variables</li>
+        </ul>
+    </li>
+    <li>Have a bug, use printlns liberally to figure out what is going on
+        <ul>
+            <li>this may mean commenting out sections of your code, and slowly stepping through it</li>
+            <li>we suggest using “TESTING” or “DEBUG” in whatever you print. That way, you don’t accidentally leave a print in there
+                when you submit for grading.</li>
+        </ul>
+    </li>
+</ul>
+
+<h3 id="before-asking-questions-talk-to-the-ducky">Before asking questions, talk to the ducky!</h3>
+
+<p><img src="{{"/assets/img/ducky.png" | relative_url }}" style="float:right;width:125px;padding-right:10px;padding-left:10px;padding-bottom:50px;" /></p>
+
+<p>Often the best thing you can do is explain what you are attempting to do to a friend. In the process of explaining it,
+    you usually figure out your errors, and it helps give you a direction to go from there.</p>
+
+<p>Sometimes in companies, this can be a time-cost for other developers so thus the introduction of a
+    <a href="https://en.wikipedia.org/wiki/Rubber_duck_debugging">Rubber Duck</a> for
+    testing. This gives you an object for you to talk to just like you would a friend. The object doesn’t have to give feedback
+    (just like a friend doesn’t), but instead, the process of talking through the code out loud will often provide
     insights into both development and errors.</p>

data/_includes/icon-github.html

@@ -1 +1 @@
-<a href="https://github.com/{{ include.username }}"><span class="icon icon--github">{% include icon-github.svg %}</span><span class="username">{{ include.username }}</span></a>
+<a href="https://github.com/{{ include.username }}"><span class="icon icon--github">{% include icon-github.svg %}</span><span class="username">{{ include.username }}</span></a>

data/_includes/icon-github.svg

@@ -1 +1 @@
-<svg viewBox="0 0 16 16" width="16px" height="16px"><path fill="#828282" d="M7.999,0.431c-4.285,0-7.76,3.474-7.76,7.761 c0,3.428,2.223,6.337,5.307,7.363c0.388,0.071,0.53-0.168,0.53-0.374c0-0.184-0.007-0.672-0.01-1.32 c-2.159,0.469-2.614-1.04-2.614-1.04c-0.353-0.896-0.862-1.135-0.862-1.135c-0.705-0.481,0.053-0.472,0.053-0.472 c0.779,0.055,1.189,0.8,1.189,0.8c0.692,1.186,1.816,0.843,2.258,0.645c0.071-0.502,0.271-0.843,0.493-1.037 C4.86,11.425,3.049,10.76,3.049,7.786c0-0.847,0.302-1.54,0.799-2.082C3.768,5.507,3.501,4.718,3.924,3.65 c0,0,0.652-0.209,2.134,0.796C6.677,4.273,7.34,4.187,8,4.184c0.659,0.003,1.323,0.089,1.943,0.261 c1.482-1.004,2.132-0.796,2.132-0.796c0.423,1.068,0.157,1.857,0.077,2.054c0.497,0.542,0.798,1.235,0.798,2.082 c0,2.981-1.814,3.637-3.543,3.829c0.279,0.24,0.527,0.713,0.527,1.437c0,1.037-0.01,1.874-0.01,2.129 c0,0.208,0.14,0.449,0.534,0.373c3.081-1.028,5.302-3.935,5.302-7.362C15.76,3.906,12.285,0.431,7.999,0.431z"/></svg>
+<svg viewBox="0 0 16 16" width="16px" height="16px"><path fill="#828282" d="M7.999,0.431c-4.285,0-7.76,3.474-7.76,7.761 c0,3.428,2.223,6.337,5.307,7.363c0.388,0.071,0.53-0.168,0.53-0.374c0-0.184-0.007-0.672-0.01-1.32 c-2.159,0.469-2.614-1.04-2.614-1.04c-0.353-0.896-0.862-1.135-0.862-1.135c-0.705-0.481,0.053-0.472,0.053-0.472 c0.779,0.055,1.189,0.8,1.189,0.8c0.692,1.186,1.816,0.843,2.258,0.645c0.071-0.502,0.271-0.843,0.493-1.037 C4.86,11.425,3.049,10.76,3.049,7.786c0-0.847,0.302-1.54,0.799-2.082C3.768,5.507,3.501,4.718,3.924,3.65 c0,0,0.652-0.209,2.134,0.796C6.677,4.273,7.34,4.187,8,4.184c0.659,0.003,1.323,0.089,1.943,0.261 c1.482-1.004,2.132-0.796,2.132-0.796c0.423,1.068,0.157,1.857,0.077,2.054c0.497,0.542,0.798,1.235,0.798,2.082 c0,2.981-1.814,3.637-3.543,3.829c0.279,0.24,0.527,0.713,0.527,1.437c0,1.037-0.01,1.874-0.01,2.129 c0,0.208,0.14,0.449,0.534,0.373c3.081-1.028,5.302-3.935,5.302-7.362C15.76,3.906,12.285,0.431,7.999,0.431z"/></svg>

data/_includes/icon-twitter.html

@@ -1 +1 @@
-<a href="https://twitter.com/{{ include.username }}"><span class="icon icon--twitter">{% include icon-twitter.svg %}</span><span class="username">{{ include.username }}</span></a>
+<a href="https://twitter.com/{{ include.username }}"><span class="icon icon--twitter">{% include icon-twitter.svg %}</span><span class="username">{{ include.username }}</span></a>

data/_includes/icon-twitter.svg

@@ -1 +1 @@
-<svg viewBox="0 0 16 16" width="16px" height="16px"><path fill="#828282" d="M15.969,3.058c-0.586,0.26-1.217,0.436-1.878,0.515c0.675-0.405,1.194-1.045,1.438-1.809c-0.632,0.375-1.332,0.647-2.076,0.793c-0.596-0.636-1.446-1.033-2.387-1.033c-1.806,0-3.27,1.464-3.27,3.27 c0,0.256,0.029,0.506,0.085,0.745C5.163,5.404,2.753,4.102,1.14,2.124C0.859,2.607,0.698,3.168,0.698,3.767 c0,1.134,0.577,2.135,1.455,2.722C1.616,6.472,1.112,6.325,0.671,6.08c0,0.014,0,0.027,0,0.041c0,1.584,1.127,2.906,2.623,3.206 C3.02,9.402,2.731,9.442,2.433,9.442c-0.211,0-0.416-0.021-0.615-0.059c0.416,1.299,1.624,2.245,3.055,2.271 c-1.119,0.877-2.529,1.4-4.061,1.4c-0.264,0-0.524-0.015-0.78-0.046c1.447,0.928,3.166,1.469,5.013,1.469 c6.015,0,9.304-4.983,9.304-9.304c0-0.142-0.003-0.283-0.009-0.423C14.976,4.29,15.531,3.714,15.969,3.058z"/></svg>
+<svg viewBox="0 0 16 16" width="16px" height="16px"><path fill="#828282" d="M15.969,3.058c-0.586,0.26-1.217,0.436-1.878,0.515c0.675-0.405,1.194-1.045,1.438-1.809c-0.632,0.375-1.332,0.647-2.076,0.793c-0.596-0.636-1.446-1.033-2.387-1.033c-1.806,0-3.27,1.464-3.27,3.27 c0,0.256,0.029,0.506,0.085,0.745C5.163,5.404,2.753,4.102,1.14,2.124C0.859,2.607,0.698,3.168,0.698,3.767 c0,1.134,0.577,2.135,1.455,2.722C1.616,6.472,1.112,6.325,0.671,6.08c0,0.014,0,0.027,0,0.041c0,1.584,1.127,2.906,2.623,3.206 C3.02,9.402,2.731,9.442,2.433,9.442c-0.211,0-0.416-0.021-0.615-0.059c0.416,1.299,1.624,2.245,3.055,2.271 c-1.119,0.877-2.529,1.4-4.061,1.4c-0.264,0-0.524-0.015-0.78-0.046c1.447,0.928,3.166,1.469,5.013,1.469 c6.015,0,9.304-4.983,9.304-9.304c0-0.142-0.003-0.283-0.009-0.423C14.976,4.29,15.531,3.714,15.969,3.058z"/></svg>

data/_includes/policies/cheating.html

@@ -1,66 +1,66 @@
-<p><em>We are accountable for our actions and will act ethically and honestly in all
-    our interactions.</em></p>
-
-<p>Within the classroom, that means you do your own work! This is especially
-    true when it comes to programming, as it is easy to copy another’s code. Copying
-    code <em>is cheating</em> and lacks integrity. Such violations of cheating
-    or plagiarism will result in zero to a full negative grade on the assignment
-    and reporting to the appropriate university resources. Further
-    infractions will result in an F given in the course.</p>
-
-<p>CMU provides some nice examples to follow:</p>
-
-<p>For personal assistance, here are some of the things that are appropriate:</p>
-<ul>
-    <li>Clarifying ambiguities or vague points in class handouts, textbooks, or lectures</li>
-    <li>Discussing or explaining the general class material</li>
-    <li>Providing assistance with Java, in using the system facilities, or with editing and debugging tools</li>
-    <li>Discussing the code that we give out on the assignment</li>
-    <li>Discussing the assignments to better understand them</li>
-    <li>Getting help from anyone concerning programming issues which are clearly more general than the specific project (e.g., what does a particular error message mean?)</li>
-    <li>Suggesting solution strategies</li>
-    <li>In general, oral collaboration is OK.</li>
-</ul>
-
-<p>Here are some things that are inappropriate:</p>
-
-<ul>
-    <li>Copying files or parts of files (such as source code, written text, or unit tests) from another person or source</li>
-    <li>Copying (or retyping) files or parts of files with minor modifications such as style changes or minor logic modifications</li>
-    <li>Allowing someone else to copy your code or written assignment, either in draft or final form</li>
-    <li>Getting help that you do not fully understand, and from someone whom you do not acknowledge on your solution</li>
-    <li>Writing, using, or submitting a program that attempts to alter or erase grading information or otherwise compromise security</li>
-    <li>Copying someone else’s files containing draft solutions, even if the file permissions are incorrectly set to allow it</li>
-    <li>Lying to course staff</li>
-    <li>Reading the current solution (handed out) if you will be handing in the current assignment late</li>
-    <li>Copying prose or programs directly</li>
-    <li>Giving copies of work to others</li>
-    <li>Coaching others step-by-step</li>
-</ul>
-
-<p>If you do any of these, your should also acknowledge it in what you turn in; but expect to have a
-    conversation with an instructor about it and, at least, suffer some penalty
-    in the grade. If we discover you have done this and not acknowledged it,
-    the penalty will be much more severe. In other words, dishonesty is much
-    worse than stupidity.</p>
-
-<p>Here are some gray areas:</p>
-
-<ul>
-    <li>Reading someone’s code for clarity or bugs, after you have completed your own</li>
-    <li>Helping with debugging</li>
-    <li>Looking at someone’s prose or program but thinking about them and writing your own</li>
-    <li>Following someone’s advice or instructions without understanding them</li>
-    <li>Many others</li>
-</ul>
-
-<p>These, too, should be acknowledged.</p>
-
-<p>A few resources</p>
-<ul>
-    <li><a href="https://legacy.scu.edu/ethics/publications/iie/v13n1/challenge.html">Cheating versus Collaboration</a></li>
-    <li><a href="https://www.cs.cmu.edu/~211/policy/cheating.html">CMU Policy</a></li>
-    <li><a href="https://resolutioncenter.colostate.edu/student-conduct-code/">CSU Resolution Center - Conduct Code</a></li>
-</ul>
-
-
+<p><em>We are accountable for our actions and will act ethically and honestly in all
+    our interactions.</em></p>
+
+<p>Within the classroom, that means you do your own work! This is especially
+    true when it comes to programming, as it is easy to copy another’s code. Copying
+    code <em>is cheating</em> and lacks integrity. Such violations of cheating
+    or plagiarism will result in zero to a full negative grade on the assignment
+    and reporting to the appropriate university resources. Further
+    infractions will result in an F given in the course.</p>
+
+<p>CMU provides some nice examples to follow:</p>
+
+<p>For personal assistance, here are some of the things that are appropriate:</p>
+<ul>
+    <li>Clarifying ambiguities or vague points in class handouts, textbooks, or lectures</li>
+    <li>Discussing or explaining the general class material</li>
+    <li>Providing assistance with Java, in using the system facilities, or with editing and debugging tools</li>
+    <li>Discussing the code that we give out on the assignment</li>
+    <li>Discussing the assignments to better understand them</li>
+    <li>Getting help from anyone concerning programming issues which are clearly more general than the specific project (e.g., what does a particular error message mean?)</li>
+    <li>Suggesting solution strategies</li>
+    <li>In general, oral collaboration is OK.</li>
+</ul>
+
+<p>Here are some things that are inappropriate:</p>
+
+<ul>
+    <li>Copying files or parts of files (such as source code, written text, or unit tests) from another person or source</li>
+    <li>Copying (or retyping) files or parts of files with minor modifications such as style changes or minor logic modifications</li>
+    <li>Allowing someone else to copy your code or written assignment, either in draft or final form</li>
+    <li>Getting help that you do not fully understand, and from someone whom you do not acknowledge on your solution</li>
+    <li>Writing, using, or submitting a program that attempts to alter or erase grading information or otherwise compromise security</li>
+    <li>Copying someone else’s files containing draft solutions, even if the file permissions are incorrectly set to allow it</li>
+    <li>Lying to course staff</li>
+    <li>Reading the current solution (handed out) if you will be handing in the current assignment late</li>
+    <li>Copying prose or programs directly</li>
+    <li>Giving copies of work to others</li>
+    <li>Coaching others step-by-step</li>
+</ul>
+
+<p>If you do any of these, your should also acknowledge it in what you turn in; but expect to have a
+    conversation with an instructor about it and, at least, suffer some penalty
+    in the grade. If we discover you have done this and not acknowledged it,
+    the penalty will be much more severe. In other words, dishonesty is much
+    worse than stupidity.</p>
+
+<p>Here are some gray areas:</p>
+
+<ul>
+    <li>Reading someone’s code for clarity or bugs, after you have completed your own</li>
+    <li>Helping with debugging</li>
+    <li>Looking at someone’s prose or program but thinking about them and writing your own</li>
+    <li>Following someone’s advice or instructions without understanding them</li>
+    <li>Many others</li>
+</ul>
+
+<p>These, too, should be acknowledged.</p>
+
+<p>A few resources</p>
+<ul>
+    <li><a href="https://legacy.scu.edu/ethics/publications/iie/v13n1/challenge.html">Cheating versus Collaboration</a></li>
+    <li><a href="https://www.cs.cmu.edu/~211/policy/cheating.html">CMU Policy</a></li>
+    <li><a href="https://resolutioncenter.colostate.edu/student-conduct-code/">CSU Resolution Center - Conduct Code</a></li>
+</ul>
+
+

data/_includes/policies/copyrighted.html

@@ -1,7 +1,7 @@
-<p>Please do not share material from this course in online, print, or other media. Course material is
-    the property of the instructor who developed the course. Materials authored by third parties and
-    used in the course are also subject to copyright protections. Posting course materials on external
-    sites (commercial or not) violates both copyright law and the CSU Student Conduct Code.
-    Students who share course content without the instructor’s express permission, including with
-    online sites that post materials to sell to other students, could face appropriate disciplinary or
+<p>Please do not share material from this course in online, print, or other media. Course material is
+    the property of the instructor who developed the course. Materials authored by third parties and
+    used in the course are also subject to copyright protections. Posting course materials on external
+    sites (commercial or not) violates both copyright law and the CSU Student Conduct Code.
+    Students who share course content without the instructor’s express permission, including with
+    online sites that post materials to sell to other students, could face appropriate disciplinary or
     legal action.</p>

data/_includes/policies/daca.html

@@ -1,5 +1,5 @@
-<p>Any CSU student who faces challenges or hardships due to their legal status in the United States
-    and believes that it may impact their academic performance in this course is encouraged to visit
-    <a href="https://undocumented.colostate.edu/">Student Support Services for Undocumented, DACA &amp; ASSET</a>
-    for resources and support. Additionally, only if you feel comfortable, please
+<p>Any CSU student who faces challenges or hardships due to their legal status in the United States
+    and believes that it may impact their academic performance in this course is encouraged to visit
+    <a href="https://undocumented.colostate.edu/">Student Support Services for Undocumented, DACA &amp; ASSET</a>
+    for resources and support. Additionally, only if you feel comfortable, please
     notify your professor so they may pass along any additional resources they may possess.</p>

data/_includes/policies/diversityStatement.html

@@ -1,3 +1,3 @@
-<p>The <a href="https://diversity.colostate.edu/mission-vision-and-goals/">Mission, Vision, and Focus</a>
-    webpage of the Vice President for Diversity includes a
+<p>The <a href="https://diversity.colostate.edu/mission-vision-and-goals/">Mission, Vision, and Focus</a>
+    webpage of the Vice President for Diversity includes a
     comprehensive statement of CSU’s commitment to diversity and inclusion.</p>

data/_includes/policies/honorPledge.html

@@ -1,12 +1,12 @@
-<p>This course will adhere to the CSU <a href="https://catalog.colostate.edu/general-catalog/policies/students-responsibilities/#academic-integrity">Academic Integrity/Misconduct</a>
-    policy as found in the General Catalog and the <a href="https://catalog.colostate.edu/general-catalog/academic-standards/academic-policies/">Student Conduct Code</a>.</p>
-
-<p>Academic integrity lies at the core of our common goal: to create an intellectually honest and
-    rigorous community. Because academic integrity, and the personal and social integrity of which
-    academic integrity is an integral part, is so central to our mission as students, teachers, scholars,
-    and citizens, I will ask that you affirm the
-    <a href="https://tilt.colostate.edu/Integrity/Pledge">CSU Honor Pledge</a>
-    as part of completing your work in this course.</p>
-
-<p>Further information about Academic Integrity is available at CSU’s
+<p>This course will adhere to the CSU <a href="https://catalog.colostate.edu/general-catalog/policies/students-responsibilities/#academic-integrity">Academic Integrity/Misconduct</a>
+    policy as found in the General Catalog and the <a href="https://catalog.colostate.edu/general-catalog/academic-standards/academic-policies/">Student Conduct Code</a>.</p>
+
+<p>Academic integrity lies at the core of our common goal: to create an intellectually honest and
+    rigorous community. Because academic integrity, and the personal and social integrity of which
+    academic integrity is an integral part, is so central to our mission as students, teachers, scholars,
+    and citizens, I will ask that you affirm the
+    <a href="https://tilt.colostate.edu/Integrity/Pledge">CSU Honor Pledge</a>
+    as part of completing your work in this course.</p>
+
+<p>Further information about Academic Integrity is available at CSU’s
     <a href="https://tilt.colostate.edu/TipsAndGuides/Tip/18">Academic Integrity - Student Resources</a>.</p>

data/_includes/policies/netiquette.html

@@ -1,3 +1,3 @@
-<p>Please review the core <a href="https://tilt.colostate.edu/TipsAndGuides/Tip/128">rules of netiquette</a>
-    for some guidelines and expectations on how to
+<p>Please review the core <a href="https://tilt.colostate.edu/TipsAndGuides/Tip/128">rules of netiquette</a>
+    for some guidelines and expectations on how to
     behave in an online learning environment, such as canvas.</p>