params.json

{"name":"Terrapinhackersreference","tagline":"A reference work on how the Terrapin Hackers club is set up","body":"Contents\r\n\r\n[[TOC]]\r\n\r\n(Bilandzic & Foth, 2013)(News & Events, 2013)(Kostakis, Niaros, & Giotitsas, 2014)\r\n\r\n(Gubbels, 2014)\r\n\r\n# Preface\r\n\r\n\tThe work is separated into several sections in order to make it generally readable. They are:\r\n\r\nGoal and Metaorganization, which covers the overarching goal of the group and how the Organizers are organized.\r\n\r\nRunning Hacking, which covers the meat of what we do- get people hacking.\r\n\r\nEquipment, Inventory, and Money covers our ideas about equipment, what to get and how to get it.\r\n\r\nRelations, Sponsors, and Conflict covers most of what remains, Terrapin Hackers’ relations to the outside world and to each other.\r\n\r\n\tThis 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). \r\n\r\nA 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.\r\n\r\n# Cover Letter\r\n\r\nHello 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. \r\n\r\n# The Manual\r\n\r\n## Goal and Meta-organization \r\n\r\n### The overall goal Terrapin Hackers\r\n\r\nThe 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.\r\n\r\nTo this end, we provide the resources needed and generally try to lower the barrier to entry for everyone.\r\n\r\n### Organization of the organizers of Terrapin Hackers\r\n\r\nThe 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.\r\n\r\nThe Organizers maintain a shared Google Drive folder, make sure you have access to it when you become an Organizer!\r\n\r\nIt 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. \r\n\r\nThere are several permanent positions, which are described here:\r\n\r\nPresident: 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\r\n\r\nVice President: The duty of the Vice President is to assist the President in any of her duties.  The Vice Presidency is an elected position. \r\n\r\nTreasurer: 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\r\n\r\nHacktorial Organizer: Is the point person for coordinating and organizing Hacktorials. See: Section on Hacktorials.\r\n\r\nHack Night Organizer: Is the point person for organizing and welcoming people to Hack Night. See Section on Hack Nights.\r\n\r\nHackathon Organizer: Is the point person for getting busses to and from Hackathons. See: Section on Hackathons.\r\n\r\nHardware Organizer: In charge of keeping inventory and working with Collider to optimize hacking. See: Section on Hardware.\r\n\r\nWebsite/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 @TerrapinHackers 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.\r\n\r\nCollider 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.\r\n\r\n### Organizers Meeting Guidelines \r\n\r\nThese 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.\r\n\r\n1. 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. \r\n\r\n2. 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.\r\n\r\n3. 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.\r\n\r\n4. 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.\r\n\r\n5. 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.\r\n\r\n### University Required Ephemera \r\n\r\nTerrapin 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). \r\n\r\nOfficial Sponsor: Bryan Quinn; bquinn[at]umd[dot]edu ; 1411 A.V. Williams\r\n\r\nThe official contact Address: 1411 A.V. Williams\r\n\r\nThe official phone number: Shariq Hashme’s number \r\n\r\nThe official mission statement: Unknown\r\n\r\nThe official email address: Unknown\r\n\r\nThe official website: terrapinhackers.com\r\n\r\n## Running Hacking\r\n\r\n### Running hack nights\r\n\r\n \"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)\r\n\r\nHack nights are all about getting people to make things. We often advertise it as a mini Hackathon for 4 hours on a weekday. \r\n\r\nSet 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.\r\n\r\nDuring 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.\r\n\r\nOne 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.\r\n\r\n### Organizing Hackathon trips\r\n\r\n \"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)\r\n\r\nThe 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.\r\n\r\nThe 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. \r\n\r\nWe 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.  \r\n\r\nWe 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. \r\n\r\nWe 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.\r\n\r\nWe have previously used McLean, DOTS, and US Coachways as our charter bus sources.\r\n\r\n[http://mcleanbus.com/](http://mcleanbus.com/)\r\n\r\n[www.transportation.umd.edu/charter_req.html](http://www.transportation.umd.edu/charter_req.html)\r\n\r\n[https://www.uscoachways.com/](https://www.uscoachways.com/) \r\n\r\n### Running hacktorials\r\n\r\nHacktorials 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.  \r\n\r\nCurrently, 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. \r\n\r\nThe 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. \r\n\r\nCurrently 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 \r\n\r\nPreviously, 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.\r\n\r\n### Public Hacks\r\n\r\nPublic 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.\r\n\r\n### How to encourage projects\r\n\r\nThe 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)\r\n\r\n## Equipment, Inventory, and Money\r\n\r\nWhat equipment we have and how to deal with it\r\n\r\nTerrapin 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.\r\n\r\nKeeping 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.\r\n\r\nCurrently, 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.\r\n\r\n\tThe 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.\r\n\r\n\tThe 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. \r\n\r\n### What items we should buy\r\n\r\nIf/when money becomes available, this will be a flexible list of the priority items to obtain, as well as a general list of consumables.\r\n\r\nConsumables, or items we should reasonably have to replace every so often:\r\n\r\n<table>\r\n  <tr>\r\n    <td>LEDs (Tri-Color)</td>\r\n    <td>First Aid Kit supplies</td>\r\n  </tr>\r\n  <tr>\r\n    <td>LEDs (Single Color)</td>\r\n    <td>Hot Glue</td>\r\n  </tr>\r\n  <tr>\r\n    <td>Resistors</td>\r\n    <td>Wire (Various)</td>\r\n  </tr>\r\n  <tr>\r\n    <td>Capacitors</td>\r\n    <td>Breadboards (Var. sizes)</td>\r\n  </tr>\r\n  <tr>\r\n    <td>Batteries</td>\r\n    <td>Sandpaper</td>\r\n  </tr>\r\n  <tr>\r\n    <td>Tape</td>\r\n    <td>Blades for saws</td>\r\n  </tr>\r\n  <tr>\r\n    <td>Drill Bits</td>\r\n    <td>String</td>\r\n  </tr>\r\n  <tr>\r\n    <td>Drill Tips</td>\r\n    <td>Cardboard</td>\r\n  </tr>\r\n</table>\r\n\r\n\r\n### Spending Money\r\n\r\nMoney 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.\r\n\r\nProposed 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:\r\n\r\n1. The item being purchased\r\n\r\n2. A link to the item online\r\n\r\n3. The total cost\r\n\r\n4. What it will be used for\r\n\r\nOnce 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.\r\n\r\nAs of now, we ship to ECE in AV Williams, but we could probably start shipping to the Chemistry Building if we wanted to.\r\n\r\n\tWe 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.\r\n\r\nThe University and ECE have stated that we are not alowed\r\n\r\n## Relations, Sponsors and Conflict\r\n\r\n### How to deal when things break and go wrong\r\n\r\nInevitably, 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.  \r\n\r\n### Conflict resolution\r\n\r\nConflict 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.\r\n\r\n### Outreach, sponsors and University Relations\r\n\r\nA general guideline and current procedures to how to go about this in a way that makes the group friends.\r\n\r\nIt 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. \r\n\r\n\tWe are fine with corporate sponsors, currently Texas Instruments have donated equipment for us to hack on and with.  \r\n\r\n### Website and online presence\r\n\r\nThe website domain is currently owned by Shariq Hashme, and it is pointed at the webhost of Zach Fogg.\r\n\r\n### Donations and gaining Resources\r\n\r\nOne major way that we can get equipment and supplies is dumpster diving on campus specifically at the dumpsters around the engineering area.\r\n\r\n# Addendum\r\n\r\n## Usability Test Results\r\n\r\n## Glossary of Terms\r\n\r\nAV Williams: Building on UMD campus where the ECE and CS departments are located.\r\n\r\nCollider: \"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)\r\n\r\nHackathon: 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.\r\n\r\nHackerspace: A space where Hackers (those who hack) can congregate, work together, and utilize shared resources.\r\n\r\nHacking: 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.\r\n\r\nMakerspace: Essentially the same as Hackerspace, but a friendlier term.\r\n\r\n### Acronyms\r\n\r\nCS: Department of Computer Science\r\n\r\nCMNS: College of Computer, Mathematical, and Natural Sciences (at UMD)\r\n\r\nDOTS: Department of Transportation Serv\r\n\r\nECE: The Department of Electrical & Computer Engineering\r\n\r\nUMD: University of Maryland \r\n\r\n## Transcripts of interviews\r\n\r\nA note on the interviews: They were conducted in the informal medium of Facebook chat, therefore the appropriate parlance to the medium was used. This parlance is not always grammatically correct.\r\n\r\n### Interview with Shariq Hashme 4/7/14\r\n\r\nEric Weiss\r\n\r\nI have some questions about Terrapin Hackers for you that I am going to use for a guide on running Terrapin Hackers, if that's cool\r\n\r\n1.\tWhat is your vision for the purpose of Terrapin Hackers/Collider?\r\n\r\nShariq Hashme explain what you mean by vision\r\n\r\nEric Weiss Why did you start Terrapin Hackers?\r\n\r\nShariq Hashme For lots of different reasons. I thought it would be cool if people would hack at Maryland. I thought starting a student organization would enable that. I wanted to do interesting things.\r\n\r\nGenerally I think making things is pretty awesome and self empowering It's hard to say why. The real answer is because I thought it would be total awesomeness.\r\n\r\nEric Weiss Seems legit. Where do you see the balance between spending time making things and spending time teaching others?\r\n\r\nShariq Hashme I think people should make things with others to teach them how to make things\r\n\r\nVersus lecturing or lessons So make, make, make I guess And don't forget to step back and think about it all once in a while, maybe with others, maybe on your own\r\n\r\nEric Weiss 6.\tWhat infrastructure is needed to get students involved and making things?\r\n\r\nShariq Hashme at first I thought infrastructure was needed infrastructure isn't needed but it's nice people are needed  inspiring people people to get others to go to hackathons people who make millions/billions of dollars because of the \"hacker mindset\" and tell students in college they can do the same if they persist things like space and hardware definitely help. but they shouldn't be the focus. the focus shouldn't be money either. the focus should be hacking.\r\n\r\nEric Weiss KK. Given ideal conditions, where would you like to see Terrapin Hackers in a year, 5 years?\r\n\r\nShariq Hashme a huge network of active hackers (i.e, lots of hacks, lots of hackathon participation, potentially some interesting startups) (huge => 1000+) lots of amazing things accomplished by people who connected through terrapin hackers useful and interesting thoughts coming out of the network, which influence people globally \r\n\r\nEric Weiss 9.\tHow can we foster better projects and learning at hackathons?\r\n\r\nShariq Hashme more people to hackathons more thinking about hacking talking to more people about hacking/hackathons leaders of terrapin hackers should identify as hackers, and aspire to be great hackers - i.e, lots of hacking lead by example take all feedback very seriously try to enable others to take on big projects\r\n\r\nEric Weiss What do you see as the difference between Terrapin Hackers and Collider?\r\n\r\n Shariq Hashme There will soon be a doc released about this Collider is a space for student organizations to work in. Terrapin Hackers is a student organization consisting of hackers. Collider enters into contracts with student organizations All that doesn't mean much until this new student organization starts working in Collider. Then it'll make sense\r\n\r\nEric Weiss What was your role in Terrapin Hackers, and what is your role now? \r\n\r\nShariq Hashme I was president, meaning all responsibility fell squarely on my shoulders and I had to do my best to delegate Now I act in the capacity of an advisor/overseer I largely left my position so that others would step up and do more, and so that the organization would continue to exist long after I'm gone\r\n\r\nEric Weiss What do you see as the ideal Organization of Terrapin Hackers?\r\n\r\nShariq Hashme An organization decided by active hackers with fellow hackers in mind. That can, will, and should change. No need to have excessive structure. Focus on hacking.\r\n\r\nEric Weiss Who were you in contact with to Start Terrapin Hackers?\r\n\r\nShariq Hashme What do you mean?\r\n\r\nEric Weiss This question is more private, but who Were your contacts at the University?\r\n\r\nShariq Hashme I previously had no \"contacts\" other than Bryan Quinn who I had worked with through the Alumni Cup I later got to know a bunch of people in university administration, ECE, and CS\r\n\r\nEric Weiss Who?\r\n\r\nShariq Hashme chairs of ECE CSdeans of CMNS EGRLee Turner university relationsStacey university relationsso many peoplepretty much everyone\r\n\r\nEric Weiss Basically who should the Organizers stay in contact with?\r\n\r\nShariq Hashme chairs of ECE and CS everyone else will come by themselves\r\n\r\nEric Weiss ok 7.\tWhat can be done about the blank canvas problem, where there is anything you can do, so it is hard to do anything at all?\r\n\r\nShariq Hashme ? are you asking me what should organizers do\r\n\r\nEric Weiss sure, what do you see as solutions?\r\n\r\nShariq Hashme i don't think organizers should do anything to \"solve\" that problem just focus on hacking\r\n\r\nhacking is not working on projects hacking is messing around with technology, without necessarily having a goal in mind \r\n\r\nEric Weiss OK How important is and how can we get more people outside of STEM fields to become involved?\r\n\r\nShariq Hashme Major is irrelevant to what people can and can't do More people should hack Allowing more majors to call themselves hackers means more hackers In that sense it's good People of the same major can have vastly different backgrounds. Majors don't influence background. Diverse background is arguably useful. Diverse backgrounds*\r\n\r\nEric Weiss Can you walk me through the process (in as much detail as you like) of starting Terrapin Hackers and winning MLH?\r\n\r\nShariq Hashme basically getting lots of ppl to go to hackathons and lots of thinking and a whole semester of work\r\n\r\nEric Weiss If you have time, I'd like to go into the details of what it took, if only for posterity\r\n\r\nShariq Hashme sure\r\n\r\n### Interview with Ibrahim Hashme 4/17/14\r\n\r\n Eric Weiss What do you see as the purpose of Terrapin Hackers? Collider?\r\n\r\nIbrahim Hashme Can you  shoot me all the questions now ill get back to you in the morning? About to pass out \r\n\r\nEric Weiss sure\r\n\r\nEric Weiss\r\n\r\n1.\tWhat is your vision for the purpose of Terrapin Hackers/Collider?\r\n\r\n2.\tWhat are the procedures for your role?\r\n\r\n3.\tWho are you  in contact with to do this?\r\n\r\n4.\tWhat is your position and what responisbilities does it entail?\r\n\r\n5.\tWhat infrastructure is needed to get students involved?\r\n\r\n6.\tWhat can be done about the blank canvas problem, where there is anything you can do, so it is hard to do anything at all?\r\n\r\n7.\tHow can resources be split between teaching people the basics and having the experienced actually get things done ?\r\n\r\n8.\tHow can we foster better projects and learning at hackathons?\r\n\r\n9.\tWhat other information do you want passed on?\r\n\r\nToday\r\n\r\nIbrahim Hashme skipping the first one, im not really a visionary procedures for my roles are actually very simple, I look around for people who have interesting skills and ask whether or not theyd be interested in giving a hacktorial, and usually get positive responses. So far I have been asking friends to do hacktorials, and next weeks will be the first from someone i dont know. Using friends for this is much easier than finding new people. position, head of hacktorials? responsibilities - ensuring there is someone ready to give a hacktorial every wednesday, ensuring people are aware and willing to attend it, ensuring a room is secured infrastructure is just based off one to one interactions blank canvas wasnt a problem for me, simply because I was willing to reach out. Ensuring the head of hacktorials is an outreaching person is essential. 7/8/9 dont really have anything to say about\r\n\r\nEric Weiss Run me through the process of getting a hacktorial ready- like you are training your replacement\r\n\r\nIbrahim Hashme I was close to many people in the \"hacking\" community, and just approached friends. I haven't really developed a method for when I don't have someone in mind.\r\n\r\nEric Weiss Once you have selected someone?\r\n\r\nIbrahim Hashme The initial method with arthur was have the present present to a board of three and they would judge/make suggestions this fell apart fairly quickly I just ensure there is someone ready for a hacktorials still working on developing a method \r\n\r\nEric Weiss What do you have so far/what are you thinking of implementing?\r\n\r\nIbrahim Hashme A system of approach Where uhh People can apply to give hacktorials thats a bit too ambitious considering i have to go around searching for hacktorials so maybe a system where finding people with specific skills is easier\r\n\r\nEric Weiss ok so what do you do to keep on people?\r\n\r\nIbrahim Hashme as in make sure they are ready?\r\n\r\nEric Weiss yea\r\n\r\nIbrahim Hashme ive only had to do that once, other than that it was people who ive seen implement the skills they were going to teach and I knew had the ability to wing a great hacktorials when i had to make sure someone was ready i just asked for a quick demo\r\n\r\nEric Weiss  when?\r\n\r\nIbrahim Hashme yeah only had to do it oncefor johns hacktorial\r\n\r\nEric Weissor, how long before do you have a demo?\r\n\r\nIbrahim Hashmeended up helping him throughout too, so i guess thats another thing. Be willing to help out throughout the hacktorialoh i did it a few hours before the actual thingThats something else that needs to be figured outi mean putting measures into effectwhich ensure high quality hacktorialsalso make them less approachable to people willing to do themIve been mostly running on trust so far-definitely not reliable\r\n\r\nEric Weissok, okWhen would you like the reviews to be, ideally?\r\n\r\nIbrahim Hashmehmm making them a set thingIm actually against the ideaThey should definitely exist, but be an agreement between the hacktorial facilitator and hacktorial headevery week\r\n\r\nEric Weissso what, exactly?\r\n\r\nIbrahim Hashmeas in\"Hey lets meet here at this time, does that work for you\"\"Yes it does\"Anyways im about to shower and head for collider, get back to you then\r\n\r\nEric Weissok, thanks!\r\n\r\n# Works Cited\r\n\r\nNote: This is formatted with APA style. See: http://www.uni-leipzig.de/schliesser/files/apacrib.pdf\r\n\r\nBilandzic, M., & Foth, M. (2013). \"Libraries as coworking spaces: Understanding user motivations and perceived barriers to social learning. *Library Hi Tech*, 254-273.\r\n\r\nCollider. (2014). Collider Manifesto. College Park, Maryland.\r\n\r\nCreative Commons. (2014, 4 17). *Attribution 4.0 International (CC BY 4.0)*. Retrieved from creativecommons: http://creativecommons.org/licenses/by/4.0/\r\n\r\nGroenendyk, ,., & Gallant, R. (2013). 3D printing and scanning at the Dalhousie University Libraries: a pilot project. *Library Hi Tech*, 34-41.\r\n\r\nGubbels, M. (2014, March 4). *Collider*. Retrieved from Collider facebook group: https://www.facebook.com/groups/1385113858377673/\r\n\r\nHackers, T. (n.d.). *Terrapin Hackers Poster.* Terrapin hackers, College Park.\r\n\r\nHardin, G. (1968, December 13). The Tragedy of the Commons. *Science*, pp. 1243-1248.\r\n\r\nKostakis, 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 *.\r\n\r\nMaker Media. (2013). *Makerspace Playbook.* Maker Media.\r\n\r\nMoilanen, J. (2012). Emerging Hackerspaces – Peer-production Generation. *IFIP Advances in Information and Communication Technology*, 94-111.\r\n\r\nNASCO Institute. (2008). *Conflict: Fight, Flight or Opportunity.* \r\n\r\n*News & Events*. (2013, October 13). Retrieved from eng.umd.edu: http://www.eng.umd.edu/html/news/news_story.php?id=7695\r\n\r\nSeravalli, A. (2012). *Infrastructuring for opening production, from participatory design to participatory making?* NYC: ACM.\r\n\r\nStudent Government Association. (2014, April 17). *Student Group Resource Center*. Retrieved from UMD SGA website: http://www.sga.umd.edu/studentgroups/new_groups.html\r\n\r\nVarious. (n.d.). *Bylaws*. Retrieved from wiki.hacdc.org: http://wiki.hacdc.org/index.php/Bylaws\r\n\r\n","google":"","note":"Don't delete this file! It's used internally to help with page regeneration."}