-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathindex.html
More file actions
403 lines (261 loc) · 30.9 KB
/
Copy pathindex.html
File metadata and controls
403 lines (261 loc) · 30.9 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
<!doctype html>
<!-- The Time Machine GitHub pages theme was designed and developed by Jon Rohan, on Feb 7, 2012. -->
<!-- Follow him for fun. http://twitter.com/jonrohan. Tail his code on http://github.com/jonrohan -->
<html>
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
<link rel="stylesheet" href="stylesheets/stylesheet.css" media="screen"/>
<link rel="stylesheet" href="stylesheets/pygment_trac.css"/>
<script type="text/javascript" src="https://ajax.googleapis.com/ajax/libs/jquery/1.7.1/jquery.min.js"></script>
<script type="text/javascript" src="javascripts/script.js"></script>
<title>Terrapinhackersreference</title>
<meta name="description" content="A reference work on how the Terrapin Hackers club is set up">
<meta name="viewport" content="width=device-width,initial-scale=1">
</head>
<body>
<div class="wrapper">
<header>
<h1 class="title">Terrapinhackersreference</h1>
</header>
<div id="container">
<p class="tagline">A reference work on how the Terrapin Hackers club is set up</p>
<div id="main" role="main">
<div class="download-bar">
<div class="inner">
<a href="https://github.com/TerrapinHackers/TerrapinHackersReference/tarball/master" class="download-button tar"><span>Download</span></a>
<a href="https://github.com/TerrapinHackers/TerrapinHackersReference/zipball/master" class="download-button zip"><span>Download</span></a>
<a href="https://github.com/TerrapinHackers/TerrapinHackersReference" class="code">View Terrapinhackersreference on GitHub</a>
</div>
<span class="blc"></span><span class="trc"></span>
</div>
<article class="markdown-body">
<p>Contents</p>
<p>[[TOC]]</p>
<p>(Bilandzic & Foth, 2013)(News & Events, 2013)(Kostakis, Niaros, & Giotitsas, 2014)</p>
<p>(Gubbels, 2014)</p>
<h1>
<a name="preface" class="anchor" href="#preface"><span class="octicon octicon-link"></span></a>Preface</h1>
<pre><code>The work is separated into several sections in order to make it generally readable. They are:
</code></pre>
<p>Goal and Metaorganization, which covers the overarching goal of the group and how the Organizers are organized.</p>
<p>Running Hacking, which covers the meat of what we do- get people hacking.</p>
<p>Equipment, Inventory, and Money covers our ideas about equipment, what to get and how to get it.</p>
<p>Relations, Sponsors, and Conflict covers most of what remains, Terrapin Hackers’ relations to the outside world and to each other.</p>
<pre><code>This work is intended for the Organizers of Terrapin Hackers at the University of Maryland, College Park, but it is hoped that this will be useful to anyone who is trying to foster a culture of hacking wherever they are. Once published, this work is licensed under a Creative Commons Attribution 4.0 International License (Creative Commons, 2014).
</code></pre>
<p>A note on style: it will be noticed that several terms are capitalized (such as Organizer, Hackathon, Treasurer, etc.) this is the intentional styling of the organization.</p>
<h1>
<a name="cover-letter" class="anchor" href="#cover-letter"><span class="octicon octicon-link"></span></a>Cover Letter</h1>
<p>Hello Organizers of Terrapin Hackers, both current and future! This guide represents an attempt to cultivate and collate group knowledge and experience so that this group will have a future, and a way to look at the past. This is a reference work, it would please me to no end if you do read this all the way through, but that is in no way required or expected in order to get the maximum out of this work. This should be seen as a living document that will (hopefully) be updated whenever procedure changes. Most of this work is not in a terribly formal tone as this is not a terribly formal organization. </p>
<h1>
<a name="the-manual" class="anchor" href="#the-manual"><span class="octicon octicon-link"></span></a>The Manual</h1>
<h2>
<a name="goal-and-meta-organization" class="anchor" href="#goal-and-meta-organization"><span class="octicon octicon-link"></span></a>Goal and Meta-organization</h2>
<h3>
<a name="the-overall-goal-terrapin-hackers" class="anchor" href="#the-overall-goal-terrapin-hackers"><span class="octicon octicon-link"></span></a>The overall goal Terrapin Hackers</h3>
<p>The goal of Terrapin Hackers is to get students hacking. We live in a world where the superstars are the ones that spend their time making and creating and gaining the skills therein. We want to see a huge community of people making lots of things and lots of really cool Hackathon projects. We want to not simply be a group, but to create a culture around hacking and going to hackathons that fosters a UMD hacker identity and aspirations to be a great hacker.</p>
<p>To this end, we provide the resources needed and generally try to lower the barrier to entry for everyone.</p>
<h3>
<a name="organization-of-the-organizers-of-terrapin-hackers" class="anchor" href="#organization-of-the-organizers-of-terrapin-hackers"><span class="octicon octicon-link"></span></a>Organization of the organizers of Terrapin Hackers</h3>
<p>The leadership of Terrapin Hackers are the Organizers of Terrapin Hackers. This is essentially a group of committed people who run the club and mostly try to just keep things going. Membership is open to anyone that comes to Organizers meetings and gets involved. Organizers have the right and responsibility to create sub –groups focused on their area to assist them and to delegate tasks.</p>
<p>The Organizers maintain a shared Google Drive folder, make sure you have access to it when you become an Organizer!</p>
<p>It is proposed that the Organizers operate on a consensus system, where everyone must consent or stand aside in order to pass a motion. Quorum (enough people to make a decision) is defined as having at least 5 of the named positions present. </p>
<p>There are several permanent positions, which are described here:</p>
<p>President: The President’s duties are to run Organizers meetings, to be the point-of-contact with all external groups, to keep the rest of the Organizers accountable for their actions. The president is a university-mandated position. The president also serves as SGA liaison. The Presidency is an elected position</p>
<p>Vice President: The duty of the Vice President is to assist the President in any of her duties. The Vice Presidency is an elected position. </p>
<p>Treasurer: The position of Treasurer is a university-mandated position. The Treasurer is in charge of all financial affairs; she maintains any budget and coordinates spending with the University. The Treasurer is an elected position</p>
<p>Hacktorial Organizer: Is the point person for coordinating and organizing Hacktorials. See: Section on Hacktorials.</p>
<p>Hack Night Organizer: Is the point person for organizing and welcoming people to Hack Night. See Section on Hack Nights.</p>
<p>Hackathon Organizer: Is the point person for getting busses to and from Hackathons. See: Section on Hackathons.</p>
<p>Hardware Organizer: In charge of keeping inventory and working with Collider to optimize hacking. See: Section on Hardware.</p>
<p>Website/Social Media Organizer: Is the point person for the Terrapin Hackers social media presence. Will have access to, and will use all of, but not limited to: administration of the Terrapin Hackers Facebook page, the <a href="https://github.com/TerrapinHackers" class="user-mention">@TerrapinHackers</a> twitter handle, the terrapinhackers.com domain, the Organizers Google Drive Folder, the Terrapin Hackers GitHub group and any other social media that may exist. The website Organizer will be in charge of keeping the website updated with any relevant information. This may be multiple positions.</p>
<p>Collider Liaison: This is not a full position, and should be combined with one of the above positions. The Collider liaison is the Organizer that is the official point-of-contact with Collider as an organization. Any Terrapin Hackers + Collider meetings must include this person.</p>
<h3>
<a name="organizers-meeting-guidelines" class="anchor" href="#organizers-meeting-guidelines"><span class="octicon octicon-link"></span></a>Organizers Meeting Guidelines</h3>
<p>These guidelines should not be seen as strict rules, but as a method of organization that works elsewhere and a nice system for keeping things going. Much of this is taken from Eric Weiss’ experience with Coop Housing, University of Maryland. It is a system that really does work and really does foster communication and moves the organization forward.</p>
<ol>
<li><p>The president (or someone she designates) will create an agenda about what to talk about and how long the meeting will be, and will post at least a draft 24 hours before the meeting. Any Organizer can add something to the agenda at will. </p></li>
<li><p>The Facilitator is the person who directs the flow of the meeting and makes sure time is kept to and the agenda is actually followed. Often the President, but it is at her discretion if she wishes someone else to do it.</p></li>
<li><p>Someone at the meeting needs to volunteer (or the President needs to volunteer someone) to take notes. Computers and voice recognition are acceptable if they actually work. We need a record of what happens at meetings for ourselves and for those unable to be present.</p></li>
<li><p>We have the position of Stack Taker. The Stack Taker’s job is to see when someone wants to speak and add them to the list of people who want to speak. This creates order in speaking and is an excellent way of preventing chaos and confusion.</p></li>
<li><p>At the end of the meeting we have checkouts where we go around and say what we are going to do once the meeting is over, any tasks we are going to do.</p></li>
</ol><h3>
<a name="university-required-ephemera" class="anchor" href="#university-required-ephemera"><span class="octicon octicon-link"></span></a>University Required Ephemera</h3>
<p>Terrapin Hackers is a university club. Our sponsor is Bryan Quinn of the Electrical and Computer Engineering department. University regulations require us to have a President and Treasurer, as well as an SGA liaison (Student Government Association, 2014). </p>
<p>Official Sponsor: Bryan Quinn; bquinn[at]umd[dot]edu ; 1411 A.V. Williams</p>
<p>The official contact Address: 1411 A.V. Williams</p>
<p>The official phone number: Shariq Hashme’s number </p>
<p>The official mission statement: Unknown</p>
<p>The official email address: Unknown</p>
<p>The official website: terrapinhackers.com</p>
<h2>
<a name="running-hacking" class="anchor" href="#running-hacking"><span class="octicon octicon-link"></span></a>Running Hacking</h2>
<h3>
<a name="running-hack-nights" class="anchor" href="#running-hack-nights"><span class="octicon octicon-link"></span></a>Running hack nights</h3>
<p>"Until Midnight after a Hacktorial, hackers can experience an intense bursts of creativity-without the worries of tomorrow’s class. At hack night you bring your ideas to life, anything from a new app or a possibly famous self-sorting trash can. Nothing can stop you here, and the goal is to have something created by the end of the night." (Hackers)</p>
<p>Hack nights are all about getting people to make things. We often advertise it as a mini Hackathon for 4 hours on a weekday. </p>
<p>Set up: currently we have them start at 8 and end at midnight. Usually there are just people around Collider, so we make an effort to clean up the place and make it look nice, put stuff away, and that sort of thing. So far we have had some themed hack nights such as a Valentine’s Day themed one with paper hearts and a prize of a giant chocolate Hershey’s Kiss.</p>
<p>During the Hack Night: the Organizers role is to welcome people in (there are a lot of people who come to Collider for the first time at Hack Nights), inform them of the current happenings, facilitate team formation (if applicable), obtain any supplies or information as needed. Or she delegates any or all of the above.</p>
<p>One idea is to have something to take apart every week, be it an old printer or a piece of scientific equipment, this gives those who have no idea what to do something to do.</p>
<h3>
<a name="organizing-hackathon-trips" class="anchor" href="#organizing-hackathon-trips"><span class="octicon octicon-link"></span></a>Organizing Hackathon trips</h3>
<p>"Hack nights were so good-the hacking community created the Hackathon. They are 36 hours of productive, sleepless fun. Hackathons are where we create something incredible, in a limited amount of time." (Hackers)</p>
<p>The Hackathon Organizer is responsible for obtaining busses to Hackathons. This means contacting the organizers of the Hackathon and negotiating to get one or two busses paid for by them. Then it means calling various bus companies and obtaining quotes from them and selecting the best one, then telling the selected bus company that we will be sending the bill to the person that will be paying for it.</p>
<p>The Hackathon Organizer is also responsible for making sure that enough people know about the Hackathon and are going to get on the bus. This involves a lot of outreach. At minimum, we have created a pinned post in the Terrapin Hackers Facebook group with a Facebook event. It should be noted that the event needs to be made public and not simply accidentally private to the group. </p>
<p>We have also created a Twilio application that participant’s text their email address to before they get on the bus so we can send out messages to everyone. </p>
<p>We are currently having an issue with people signing up for Hackathons and not showing up. What other Universities do is have people give a $10 deposit which they get back once they get on the bus. The problem with this is that some people simply don’t have $10 to spare. Another problem with this is that it may discourage people from going to Hackathons in the first place as it creates a barrier. </p>
<p>We never want to charge students for going to Hackathons. We want to make going to Hackathons as free and as easy as possible for participants. As such, we don’t want to ever charge people to get on a bus or to participate in anything we do. What this means is that we only really advertise the Hackathons we actually are getting a bus for. A result of this is that we don’t know what Hackathons we will be going to, which makes it difficult to create a list or schedule of them.</p>
<p>We have previously used McLean, DOTS, and US Coachways as our charter bus sources.</p>
<p><a href="http://mcleanbus.com/">http://mcleanbus.com/</a></p>
<p><a href="http://www.transportation.umd.edu/charter_req.html">www.transportation.umd.edu/charter_req.html</a></p>
<p><a href="https://www.uscoachways.com/">https://www.uscoachways.com/</a> </p>
<h3>
<a name="running-hacktorials" class="anchor" href="#running-hacktorials"><span class="octicon octicon-link"></span></a>Running hacktorials</h3>
<p>Hacktorials are "Your guide to the future. Beginners and experts alike can be brought up to speed about the most relevant technologies. An immensely passionate host will give one every week, followed up by an epic hack night." (Hackers). We aim to teach people something new, usually (but not exclusively) being taught by undergraduate and graduate students. </p>
<p>Currently, Hacktorials are held on Wednesday nights from 7-9 at changing locations. Historically, they may have been held in the Computer Science lecture hall or other classrooms. </p>
<p>The Hacktorial Organizer is responsible for ensuring that there is someone ready to give the hacktorials, make sure people are aware and willing to attend, and make sure that the room is secured for use. He also coordinates a time to go over the presentation in an informal fashion, and helps out during the hacktorials for whatever is needed. </p>
<p>Currently the Hacktorial Organizer has been reaching out to those he knows in the community that would give a good talk. He looks for people who have interesting skills and asks whether they would be interested in giving a hacktorials, and he usually gets positive responses. The Organizer </p>
<p>Previously, we tried a system of having the presenter present a day or so before the hacktorials to a board of three people who would judge it and make suggestions. This was found to not work.</p>
<h3>
<a name="public-hacks" class="anchor" href="#public-hacks"><span class="octicon octicon-link"></span></a>Public Hacks</h3>
<p>Public Hacks are hacks done outside of normal locations and events that are done primarily around the UMD campus for the purposes of fun, advertisement, and creating something cool. These are to be a positively oriented thing that will generally reflect well on the club and University. Nothing black hat (such as putting cars on roofs) is to be associated with the group.</p>
<h3>
<a name="how-to-encourage-projects" class="anchor" href="#how-to-encourage-projects"><span class="octicon octicon-link"></span></a>How to encourage projects</h3>
<p>The primary way in which we will encourage hacking is by hacking, and having the most people hacking. To this end, we will show off peoples current projects and provide any needed resources that are requested. Maker proposes: "Keep something like an “idea rummage box" in the space, where members can throw in cool clippings and clever objects they think could inspire others. Show off the products and the process. Choose well placed shelves and wall space for showcasing examples of past projects and current activities to seed ideas and inspiration.” (Maker Media, 2013)</p>
<h2>
<a name="equipment-inventory-and-money" class="anchor" href="#equipment-inventory-and-money"><span class="octicon octicon-link"></span></a>Equipment, Inventory, and Money</h2>
<p>What equipment we have and how to deal with it</p>
<p>Terrapin Hackers owns a large amount of valuable equipment. It is important that we keep track of it so that we have it to use. The first step we have decided is that equipment is generally not to leave Collider. Any exceptions should be directed towards the Hardware Organizer. In general, we allow exceptions for things like quadcopters and GoPros, as those are primarily usable only outside collider. As well, anyone can rent things for Hackathons. We have created a template for Hackathon equipment checkouts that is located on the Google Drive Folder.</p>
<p>Keeping equipment organized and in its place is probably one of the hardest things we do. Most of what we have is so small, and we have not really projected the message of keeping things in the space, that much equipment is walking off.</p>
<p>Currently, we have started a system of labeling where tools go and what they are. The system seems to be a good one, however it is up to every organizer to actually tell people to put away tools so we don’t have to do it constantly ourselves. We are in the process of getting a system of labeled boxes so we can display what hardware we have and make accessing documentation for it easier.</p>
<pre><code>The key to being Hardware Organizer not actually knowing what all the hardware does, but mostly to be willing to work with the other Organizers and Collider to optimize how it is organized and presented. It also means being in the space very often, and helping people out when they need to find something. It means taking initiative and realizing that everyone here is a student and really has no idea what they are doing. Talk about your ideas and then implement them. Make the system your personal hack.
The biggest problem we are going to have is the tragedy of the commons. Briefly, the tragedy of the commons is the tendency to take an action that wholly benefits you (putting another sheep on the common green or not putting a tool away) but the downsides are shared among everyone (overgrazing and degrading of the land or not having tools in their place (Hardin, 1968). In the end, we have tools not in their place and supplies will go missing. Harding suggests that the only way to remove this is to remove the commons aspect. This is a dilemma. We want people to do great things, but we also want people in the future to have the resources to do things. We don’t want this to be a private club, but we do want people to care. This guidebook does not pretend to have the solution, only to show the problem is real and needs to be addressed.
</code></pre>
<h3>
<a name="what-items-we-should-buy" class="anchor" href="#what-items-we-should-buy"><span class="octicon octicon-link"></span></a>What items we should buy</h3>
<p>If/when money becomes available, this will be a flexible list of the priority items to obtain, as well as a general list of consumables.</p>
<p>Consumables, or items we should reasonably have to replace every so often:</p>
<table>
<tr>
<td>LEDs (Tri-Color)</td>
<td>First Aid Kit supplies</td>
</tr>
<tr>
<td>LEDs (Single Color)</td>
<td>Hot Glue</td>
</tr>
<tr>
<td>Resistors</td>
<td>Wire (Various)</td>
</tr>
<tr>
<td>Capacitors</td>
<td>Breadboards (Var. sizes)</td>
</tr>
<tr>
<td>Batteries</td>
<td>Sandpaper</td>
</tr>
<tr>
<td>Tape</td>
<td>Blades for saws</td>
</tr>
<tr>
<td>Drill Bits</td>
<td>String</td>
</tr>
<tr>
<td>Drill Tips</td>
<td>Cardboard</td>
</tr>
</table><h3>
<a name="spending-money" class="anchor" href="#spending-money"><span class="octicon octicon-link"></span></a>Spending Money</h3>
<p>Money should be spent to gain the maximum benefit to the group and longevity of funds. We currently have received money from the Department of Electrical and Computer Engineering and the Department of Computer Science. Nobody likes bureaucracy, however we want systems that are prudent and deliberate in spending money.</p>
<p>Proposed is a method for ensuring agreement and minimization of waste. In order to spend money, there must be a quorum of Organizers that is required to include the Treasurer, either the President or the vice president, and the Hardware manager (if it is a physical item being bought). This should be presented in a document that states at minimum:</p>
<ol>
<li><p>The item being purchased</p></li>
<li><p>A link to the item online</p></li>
<li><p>The total cost</p></li>
<li><p>What it will be used for</p></li>
</ol><p>Once the spending is consented to, the treasurer fills out the appropriate paperwork and submits the expense to ECE, where ECE will approve or not approve of the expense.</p>
<p>As of now, we ship to ECE in AV Williams, but we could probably start shipping to the Chemistry Building if we wanted to.</p>
<pre><code>We currently do not have money that is simply ours. It is against our purpose to charge students for access to materials and/or anything we do as a club. At times, when we can’t get a bus to a Hackathon, we do not officially promote the event, though we like to see people self-organize on Facebook.
</code></pre>
<p>The University and ECE have stated that we are not alowed</p>
<h2>
<a name="relations-sponsors-and-conflict" class="anchor" href="#relations-sponsors-and-conflict"><span class="octicon octicon-link"></span></a>Relations, Sponsors and Conflict</h2>
<h3>
<a name="how-to-deal-when-things-break-and-go-wrong" class="anchor" href="#how-to-deal-when-things-break-and-go-wrong"><span class="octicon octicon-link"></span></a>How to deal when things break and go wrong</h3>
<p>Inevitably, people will break things. We want to foster a culture that avoids punishment, as that will simply lead to things being unreported. If something is of minimal value, we won’t worry about it, as long as the person is not breaking things intentionally. If something is more valuable, and it was an accident, it is ok, we should just talk about it at the next organizers meeting. </p>
<h3>
<a name="conflict-resolution" class="anchor" href="#conflict-resolution"><span class="octicon octicon-link"></span></a>Conflict resolution</h3>
<p>Conflict will inevitably happen. We establish a culture that will work to recognize each other’s feelings and acknowledge that we are not purely rational creatures (NASCO Institute, 2008). Everyone here wants what is best for the group, we may just have different ways of going about it. If conflict comes up, one option is to find an arbiter that both can agree to sit in on discussions of both part’s feelings and positions.</p>
<h3>
<a name="outreach-sponsors-and-university-relations" class="anchor" href="#outreach-sponsors-and-university-relations"><span class="octicon octicon-link"></span></a>Outreach, sponsors and University Relations</h3>
<p>A general guideline and current procedures to how to go about this in a way that makes the group friends.</p>
<p>It is in the interest of the group to maintain good relations with those outside of the group. We maintain relations with the Heads of ECE, CS, the deans of Engineering and CMNS. We also maintain relationships with the staff of the Chemistry department, specifically the Chair, the Director of Operations, the Maintenance Mechanic, and so on. </p>
<pre><code>We are fine with corporate sponsors, currently Texas Instruments have donated equipment for us to hack on and with.
</code></pre>
<h3>
<a name="website-and-online-presence" class="anchor" href="#website-and-online-presence"><span class="octicon octicon-link"></span></a>Website and online presence</h3>
<p>The website domain is currently owned by Shariq Hashme, and it is pointed at the webhost of Zach Fogg.</p>
<h3>
<a name="donations-and-gaining-resources" class="anchor" href="#donations-and-gaining-resources"><span class="octicon octicon-link"></span></a>Donations and gaining Resources</h3>
<p>One major way that we can get equipment and supplies is dumpster diving on campus specifically at the dumpsters around the engineering area.</p>
<h1>
<a name="addendum" class="anchor" href="#addendum"><span class="octicon octicon-link"></span></a>Addendum</h1>
<h2>
<a name="usability-test-results" class="anchor" href="#usability-test-results"><span class="octicon octicon-link"></span></a>Usability Test Results</h2>
<h2>
<a name="glossary-of-terms" class="anchor" href="#glossary-of-terms"><span class="octicon octicon-link"></span></a>Glossary of Terms</h2>
<p>AV Williams: Building on UMD campus where the ECE and CS departments are located.</p>
<p>Collider: "Collider is a place for everyone to explore their ideas through building… It equally hackerspace, art studio, and laboratory. It’s a creative sandbox for playful invention." (Collider, 2014)</p>
<p>Hackathon: Specifically refers to college Hackathons, which are events held at or by students at a University. A Hackathon is a 24-48 hour event where college students come together with the purpose of making something by the end of the event.</p>
<p>Hackerspace: A space where Hackers (those who hack) can congregate, work together, and utilize shared resources.</p>
<p>Hacking: Refers to the idea of creatively remixing existing technologies in order to learn about them and make them do something new. In this context specifically does not refer to breaking into computer systems.</p>
<p>Makerspace: Essentially the same as Hackerspace, but a friendlier term.</p>
<h3>
<a name="acronyms" class="anchor" href="#acronyms"><span class="octicon octicon-link"></span></a>Acronyms</h3>
<p>CS: Department of Computer Science</p>
<p>CMNS: College of Computer, Mathematical, and Natural Sciences (at UMD)</p>
<p>DOTS: Department of Transportation Serv</p>
<p>ECE: The Department of Electrical & Computer Engineering</p>
<p>UMD: University of Maryland </p>
<h1>
<a name="works-cited" class="anchor" href="#works-cited"><span class="octicon octicon-link"></span></a>Works Cited</h1>
<p>Note: This is formatted with APA style. See: <a href="http://www.uni-leipzig.de/schliesser/files/apacrib.pdf">http://www.uni-leipzig.de/schliesser/files/apacrib.pdf</a></p>
<p>Bilandzic, M., & Foth, M. (2013). "Libraries as coworking spaces: Understanding user motivations and perceived barriers to social learning. <em>Library Hi Tech</em>, 254-273.</p>
<p>Collider. (2014). Collider Manifesto. College Park, Maryland.</p>
<p>Creative Commons. (2014, 4 17). <em>Attribution 4.0 International (CC BY 4.0)</em>. Retrieved from creativecommons: <a href="http://creativecommons.org/licenses/by/4.0/">http://creativecommons.org/licenses/by/4.0/</a></p>
<p>Groenendyk, ,., & Gallant, R. (2013). 3D printing and scanning at the Dalhousie University Libraries: a pilot project. <em>Library Hi Tech</em>, 34-41.</p>
<p>Gubbels, M. (2014, March 4). <em>Collider</em>. Retrieved from Collider facebook group: <a href="https://www.facebook.com/groups/1385113858377673/">https://www.facebook.com/groups/1385113858377673/</a></p>
<p>Hackers, T. (n.d.). <em>Terrapin Hackers Poster.</em> Terrapin hackers, College Park.</p>
<p>Hardin, G. (1968, December 13). The Tragedy of the Commons. <em>Science</em>, pp. 1243-1248.</p>
<p>Kostakis, V., Niaros, V., & Giotitsas, C. (2014). Production and governance in hackerspaces: A manifestation of Commons-based peer production in the physical realm? *International Journal of Cultural Studies *.</p>
<p>Maker Media. (2013). <em>Makerspace Playbook.</em> Maker Media.</p>
<p>Moilanen, J. (2012). Emerging Hackerspaces – Peer-production Generation. <em>IFIP Advances in Information and Communication Technology</em>, 94-111.</p>
<p>NASCO Institute. (2008). <em>Conflict: Fight, Flight or Opportunity.</em> </p>
<p><em>News & Events</em>. (2013, October 13). Retrieved from eng.umd.edu: <a href="http://www.eng.umd.edu/html/news/news_story.php?id=7695">http://www.eng.umd.edu/html/news/news_story.php?id=7695</a></p>
<p>Seravalli, A. (2012). <em>Infrastructuring for opening production, from participatory design to participatory making?</em> NYC: ACM.</p>
<p>Student Government Association. (2014, April 17). <em>Student Group Resource Center</em>. Retrieved from UMD SGA website: <a href="http://www.sga.umd.edu/studentgroups/new_groups.html">http://www.sga.umd.edu/studentgroups/new_groups.html</a></p>
<p>Various. (n.d.). <em>Bylaws</em>. Retrieved from wiki.hacdc.org: <a href="http://wiki.hacdc.org/index.php/Bylaws">http://wiki.hacdc.org/index.php/Bylaws</a></p>
</article>
</div>
</div>
<footer>
<div class="owner">
<p><a href="https://github.com/TerrapinHackers" class="avatar"><img src="https://avatars1.githubusercontent.com/u/7330907?s=60" width="48" height="48"/></a> <a href="https://github.com/TerrapinHackers">TerrapinHackers</a> maintains <a href="https://github.com/TerrapinHackers/TerrapinHackersReference">Terrapinhackersreference</a></p>
</div>
<div class="creds">
<small>This page generated using <a href="http://pages.github.com/">GitHub Pages</a><br/>theme by <a href="https://twitter.com/jonrohan/">Jon Rohan</a></small>
</div>
</footer>
</div>
<div class="current-section">
<a href="#top">Scroll to top</a>
<a href="https://github.com/TerrapinHackers/TerrapinHackersReference/tarball/master" class="tar">tar</a><a href="https://github.com/TerrapinHackers/TerrapinHackersReference/zipball/master" class="zip">zip</a><a href="" class="code">source code</a>
<p class="name"></p>
</div>
</body>
</html>