Skip to content

Commit 0cd134e

Browse files
committed
update help appendix
1 parent 3faaa3d commit 0cd134e

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

pretext/welcome.ptx

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -71,7 +71,7 @@
7171
</p>
7272
</li>
7373
<li>Join our
74-
<url href="https://join.slack.com/t/runestoneteam/shared_invite/enQtODUwNDIwMzg5NDQxLTZlMjAzOTNlNzNlYTVjZDEyODI4ZTY1YjFjNTg3YTBiOWY2ODNlZTA4NWFiMjAxNzlkZGE1MmY0ZTQyY2E5Y2Q" visual="slack channel" />. There is almost always someone live and available on the slack. So if you have something truly urgent that might be a good option.
74+
<url href="https://discord.gg/f3Qmbk9P3U" visual="discord" />. There is almost always someone live and available on the discord. So if you have something truly urgent that might be a good option.
7575
</li>
7676
</ol>
7777
</p>
@@ -81,7 +81,7 @@
8181
<section xml:id="drop-in">
8282
<title>Weekly Drop-Ins</title>
8383

84-
<p>There are two opportunities each week to ask questions of the development team. Tuesday afternoons from 1PM Central to 3PM Central on Zoom. The link is always the same and is always provided as a reminder in the slack channel. The Zoom meeting number is RUNESTONE1 on your telephone keypad.  The link is:  <url href="https://us02web.zoom.us/j/7863786631?pwd=b2g4bk5RSURDWjVyVUZ3YWxoSUwxUT09" visual="RUNESTONE1" /></p>
84+
<p>There are two opportunities each week to ask questions of the development team. You can find our current schedule on <url href="https://prose.runestone.academy" visual="Our Website" />. The link is always the same and is always provided as a reminder in the discord channel. The Zoom meeting is at <url href="https://prose.runestone.academy/dropin" visual="Runestone/Pretext Drop-In" />. </p>
8585

8686
<p>Since May
8787
<nbsp />2020 there has been a standing weekly online gathering of
@@ -112,7 +112,7 @@
112112
<li>Specifically what went wrong? What error message did you see? What exactly did happen that you think should not have happened. You can speculate about what you think is broken, but often you will be wrong and misleading. Just the facts is a great policy.</li>
113113
<li>Give some context about your environment. What course are you in? What is your username? What page of the course? Specifically what exercise does not work? Each activity has a unique identifier. please include that. What browser are you using? What version of the browser. (Runestone relies on many modern features of Javascript that are only present in new-ish browsers) We can not test every browser so if you are using something outside of Chrome, Firefox, Safari, or maybe Edge it is likely that I have not tested it there.</li>
114114
<li><p>If there is a traceback on the page, please copy it and include it in your Github Issue.
115-
Many many errors can be quickly diagnosed from the Javascript Console error log.
115+
Many many errors can be quickly diagnosed from the Javascript Console error log.
116116
<ul>
117117
<li>Chrome: View --> Developer --> Javascript Console</li>
118118
<li>Safari: ⌥⌘i or Develop --> Show Web Inspector </li>
@@ -125,14 +125,14 @@
125125
<p>Please note, I'm not trying to be rude, but years of observation have taught me that CS teachers are pretty bad bug reporters! Imagine if a student sent you the following email:</p>
126126
<pre>
127127
Hey,
128-
129-
You know problem 2 for the homework next week.
130-
My program just doesn't work. I'm pretty sure
131-
I've done everything right. Can you tell me how
128+
129+
You know problem 2 for the homework next week.
130+
My program just doesn't work. I'm pretty sure
131+
I've done everything right. Can you tell me how
132132
to fix it?
133-
133+
134134
Thanks,
135-
135+
136136
Student
137137
</pre>
138138
<p>You wouldn't be able to help this student very much, in fact you probably wouldn't have any idea what program that student was even asking about without spending your own valuable time figuring it out. Sadly, It is a pretty good representation of thousands of bug reports I've received. So please, take a few seconds and read or re-read Filing an effective bug report. Thanks.

0 commit comments

Comments
 (0)