http://www.interlockroc.org/wiki/index.php?title=Special:Contributions/Fvox13&feed=atom&limit=50&target=Fvox13&year=&month= 2013-05-18T23:23:41Z From Interlock Rochester Wiki MediaWiki 1.16.0 http://www.interlockroc.org/wiki/index.php/Sexual_Harassment_Policy 2011-04-19T13:37:05Z

<p>Fvox13: removing some references to employment</p> <hr /> <div>''This is a draft document and has not yet been ratified.''<br /> <br /> Interlock Rochester is committed to providing a hackerspace that is free from sexual harassment. Sexual harassment is against the law and will not be tolerated. When Interlock determines that an allegation of sexual harassment is credible, it will take prompt and appropriate corrective action.<br /> <br /> All members and guests are required to comply with this policy. Members are also expected to behave professionally and to exercise good judgment in hackerspace-related relationships, whether with fellow members, officers, or guests. Further, all members are expected to take appropriate measures to prevent sexual harassment. Unwelcome behavior of a sexual nature should be stopped before it becomes severe or pervasive and rises to a violation of law.<br /> <br /> <br /> == What Is Sexual Harassment? ==<br /> Unwelcome sexual advances, requests for sexual favors, and other verbal or physical conduct of a sexual nature constitute sexual harassment when:<br /> # A membership decision affecting that individual is made because the individual submitted to or rejected the unwelcome conduct; or<br /> # The unwelcome conduct unreasonably interferes with an individual's use of the space or creates an intimidating, hostile, or abusive environment.<br /> <br /> Certain behaviors, such as conditioning member benefits upon acceptance of unwelcome actions of a sexual nature, are always wrong.<br /> <br /> Unwelcome actions such as the following are inappropriate and, depending on the circumstances, may in and of themselves meet the definition of sexual harassment or contribute to a hostile work environment:<br /> # Sexual pranks, or repeated sexual teasing, jokes, or innuendo, in person or via e-mail;<br /> # Verbal abuse of a sexual nature;<br /> # Touching or grabbing of a sexual nature;<br /> # Repeatedly standing too close to or brushing up against a person;<br /> # Repeatedly asking a person to socialize when the person has said no or has indicated he or she is not interested<br /> # Giving gifts or leaving objects that are sexually suggestive;<br /> # Repeatedly making sexually suggestive gestures;<br /> # Making or posting sexually demeaning or offensive pictures, cartoons or other materials in the space;<br /> <br /> A victim of sexual harassment can be a man or a woman. The victim can be of the same sex as the harasser. The harasser can be a member, guest, or other person.<br /> <br /> <br /> <br /> == Interlock's Responsibilities Under This Policy ==<br /> If an allegation of sexual harassment is received, or there is reason to believe sexual harassment is occurring, the officers will take the necessary steps to ensure that the matter is promptly investigated and addressed. If the allegation is determined to be credible, Interlock will take immediate and effective measures to end the unwelcome behavior. Interlock is committed to take action if it learns of possible sexual harassment, even if the individual does not wish to file a formal complaint.<br /> <br /> The President is the main contact point for questions or concerns about sexual harassment. The President has responsibility for investigating or overseeing investigations of alleged sexual harassment. The President is committed to ensuring that all investigations of sexual harassment are conducted in a prompt, thorough, and impartial manner.<br /> <br /> Persons who observe, are informed of, or reasonably suspect incidents of possible sexual harassment must immediately report such incidents to the President, which will either initiate or oversee a prompt investigation. Failure to report such incidents to the President will be considered a violation of this policy and may result in disciplinary action. The President will provide guidance as needed on investigating and handling the potential harassment. Other officers should take effective measures to ensure no further apparent or alleged harassment occurs pending completion of an investigation.<br /> <br /> Interlock Rochester will seek to protect the identities of the alleged victim and harasser, except as reasonably necessary (for example, to complete an investigation successfully). Interlock will also take the necessary steps to protect from retaliation those individuals who in good faith report incidents of potential sexual harassment. It is a violation of both federal law and this policy to retaliate against someone who has reported possible sexual harassment. Violators may be subject to disciplinary action.<br /> <br /> Members who have been found by Interlock to have subjected another member to unwelcome conduct of a sexual nature, whether such behavior meets the legal definition of sexual harassment or not, will be subject to discipline or other appropriate management action. Discipline will be appropriate to the circumstances, ranging from membership suspension through banning from the premises. A verbal or written admonishment, while not considered formal discipline, may also be considered.<br /> <br /> <br /> <br /> == Member and Guest Rights and Responsibilities Under This Policy ==<br /> Any person who believes he or she has been the target of sexual harassment is encouraged to inform the offending person orally or in writing that such conduct is unwelcome and offensive and must stop.<br /> <br /> If the person does not wish to communicate directly with the offending person, or if such communication has been ineffective, the person is encouraged to report the unwelcome conduct as soon as possible to any officer, who will take the appropriate action.</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Sexual_Harassment_Policy 2011-04-18T15:46:43Z

<p>Fvox13: </p> <hr /> <div>''This is a draft document and has not yet been ratified.''<br /> <br /> Interlock Rochester is committed to providing a hackerspace that is free from sexual harassment. Sexual harassment is against the law and will not be tolerated. When Interlock determines that an allegation of sexual harassment is credible, it will take prompt and appropriate corrective action.<br /> <br /> All members and guests are required to comply with this policy. Members are also expected to behave professionally and to exercise good judgment in hackerspace-related relationships, whether with fellow members, officers, or guests. Further, all members are expected to take appropriate measures to prevent sexual harassment. Unwelcome behavior of a sexual nature should be stopped before it becomes severe or pervasive and rises to a violation of law.<br /> <br /> <br /> == What Is Sexual Harassment? ==<br /> Unwelcome sexual advances, requests for sexual favors, and other verbal or physical conduct of a sexual nature constitute sexual harassment when:<br /> # A membership decision affecting that individual is made because the individual submitted to or rejected the unwelcome conduct; or<br /> # The unwelcome conduct unreasonably interferes with an individual's use of the space or creates an intimidating, hostile, or abusive environment.<br /> <br /> Certain behaviors, such as conditioning promotions, awards, training or other job benefits upon acceptance of unwelcome actions of a sexual nature, are always wrong.<br /> <br /> Unwelcome actions such as the following are inappropriate and, depending on the circumstances, may in and of themselves meet the definition of sexual harassment or contribute to a hostile work environment:<br /> # Sexual pranks, or repeated sexual teasing, jokes, or innuendo, in person or via e-mail;<br /> # Verbal abuse of a sexual nature;<br /> # Touching or grabbing of a sexual nature;<br /> # Repeatedly standing too close to or brushing up against a person;<br /> # Repeatedly asking a person to socialize when the person has said no or has indicated he or she is not interested<br /> # Giving gifts or leaving objects that are sexually suggestive;<br /> # Repeatedly making sexually suggestive gestures;<br /> # Making or posting sexually demeaning or offensive pictures, cartoons or other materials in the space;<br /> <br /> A victim of sexual harassment can be a man or a woman. The victim can be of the same sex as the harasser. The harasser can be a member, guest, or other person.<br /> <br /> <br /> <br /> == Interlock's Responsibilities Under This Policy ==<br /> If an allegation of sexual harassment is received, or there is reason to believe sexual harassment is occurring, the officers will take the necessary steps to ensure that the matter is promptly investigated and addressed. If the allegation is determined to be credible, Interlock will take immediate and effective measures to end the unwelcome behavior. Interlock is committed to take action if it learns of possible sexual harassment, even if the individual does not wish to file a formal complaint.<br /> <br /> The President is the main contact point for questions or concerns about sexual harassment. The President has responsibility for investigating or overseeing investigations of alleged sexual harassment. The President is committed to ensuring that all investigations of sexual harassment are conducted in a prompt, thorough, and impartial manner.<br /> <br /> Persons who observe, are informed of, or reasonably suspect incidents of possible sexual harassment must immediately report such incidents to the President, which will either initiate or oversee a prompt investigation. Failure to report such incidents to the President will be considered a violation of this policy and may result in disciplinary action. The President will provide guidance as needed on investigating and handling the potential harassment. Other officers should take effective measures to ensure no further apparent or alleged harassment occurs pending completion of an investigation.<br /> <br /> Interlock Rochester will seek to protect the identities of the alleged victim and harasser, except as reasonably necessary (for example, to complete an investigation successfully). Interlock will also take the necessary steps to protect from retaliation those individuals who in good faith report incidents of potential sexual harassment. It is a violation of both federal law and this policy to retaliate against someone who has reported possible sexual harassment. Violators may be subject to disciplinary action.<br /> <br /> Members who have been found by Interlock to have subjected another member to unwelcome conduct of a sexual nature, whether such behavior meets the legal definition of sexual harassment or not, will be subject to discipline or other appropriate management action. Discipline will be appropriate to the circumstances, ranging from membership suspension through banning from the premises. A verbal or written admonishment, while not considered formal discipline, may also be considered.<br /> <br /> <br /> <br /> == Member and Guest Rights and Responsibilities Under This Policy ==<br /> Any person who believes he or she has been the target of sexual harassment is encouraged to inform the offending person orally or in writing that such conduct is unwelcome and offensive and must stop.<br /> <br /> If the person does not wish to communicate directly with the offending person, or if such communication has been ineffective, the person is encouraged to report the unwelcome conduct as soon as possible to any officer, who will take the appropriate action.</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Sexual_Harassment_Policy 2011-04-18T15:43:49Z

<p>Fvox13: Created page with &quot;Interlock Rochester is committed to providing a hackerspace that is free from sexual harassment. Sexual harassment is against the law and will not be tolerated. When Interlock de...&quot;</p> <hr /> <div>Interlock Rochester is committed to providing a hackerspace that is free from sexual harassment. Sexual harassment is against the law and will not be tolerated. When Interlock determines that an allegation of sexual harassment is credible, it will take prompt and appropriate corrective action.<br /> <br /> All members and guests are required to comply with this policy. Members are also expected to behave professionally and to exercise good judgment in hackerspace-related relationships, whether with fellow members, officers, or guests. Further, all members are expected to take appropriate measures to prevent sexual harassment. Unwelcome behavior of a sexual nature should be stopped before it becomes severe or pervasive and rises to a violation of law.<br /> <br /> <br /> == What Is Sexual Harassment? ==<br /> Unwelcome sexual advances, requests for sexual favors, and other verbal or physical conduct of a sexual nature constitute sexual harassment when:<br /> # A membership decision affecting that individual is made because the individual submitted to or rejected the unwelcome conduct; or<br /> # The unwelcome conduct unreasonably interferes with an individual's use of the space or creates an intimidating, hostile, or abusive environment.<br /> <br /> Certain behaviors, such as conditioning promotions, awards, training or other job benefits upon acceptance of unwelcome actions of a sexual nature, are always wrong.<br /> <br /> Unwelcome actions such as the following are inappropriate and, depending on the circumstances, may in and of themselves meet the definition of sexual harassment or contribute to a hostile work environment:<br /> # Sexual pranks, or repeated sexual teasing, jokes, or innuendo, in person or via e-mail;<br /> # Verbal abuse of a sexual nature;<br /> # Touching or grabbing of a sexual nature;<br /> # Repeatedly standing too close to or brushing up against a person;<br /> # Repeatedly asking a person to socialize when the person has said no or has indicated he or she is not interested<br /> # Giving gifts or leaving objects that are sexually suggestive;<br /> # Repeatedly making sexually suggestive gestures;<br /> # Making or posting sexually demeaning or offensive pictures, cartoons or other materials in the space;<br /> <br /> A victim of sexual harassment can be a man or a woman. The victim can be of the same sex as the harasser. The harasser can be a member, guest, or other person.<br /> <br /> <br /> <br /> == Interlock's Responsibilities Under This Policy ==<br /> If an allegation of sexual harassment is received, or there is reason to believe sexual harassment is occurring, the officers will take the necessary steps to ensure that the matter is promptly investigated and addressed. If the allegation is determined to be credible, Interlock will take immediate and effective measures to end the unwelcome behavior. Interlock is committed to take action if it learns of possible sexual harassment, even if the individual does not wish to file a formal complaint.<br /> <br /> The President is the main contact point for questions or concerns about sexual harassment. The President has responsibility for investigating or overseeing investigations of alleged sexual harassment. The President is committed to ensuring that all investigations of sexual harassment are conducted in a prompt, thorough, and impartial manner.<br /> <br /> Persons who observe, are informed of, or reasonably suspect incidents of possible sexual harassment must immediately report such incidents to the President, which will either initiate or oversee a prompt investigation. Failure to report such incidents to the President will be considered a violation of this policy and may result in disciplinary action. The President will provide guidance as needed on investigating and handling the potential harassment. Other officers should take effective measures to ensure no further apparent or alleged harassment occurs pending completion of an investigation.<br /> <br /> Interlock Rochester will seek to protect the identities of the alleged victim and harasser, except as reasonably necessary (for example, to complete an investigation successfully). Interlock will also take the necessary steps to protect from retaliation those individuals who in good faith report incidents of potential sexual harassment. It is a violation of both federal law and this policy to retaliate against someone who has reported possible sexual harassment. Violators may be subject to disciplinary action.<br /> <br /> Members who have been found by Interlock to have subjected another member to unwelcome conduct of a sexual nature, whether such behavior meets the legal definition of sexual harassment or not, will be subject to discipline or other appropriate management action. Discipline will be appropriate to the circumstances, ranging from membership suspension through banning from the premises. A verbal or written admonishment, while not considered formal discipline, may also be considered.<br /> <br /> <br /> <br /> == Member and Guest Rights and Responsibilities Under This Policy ==<br /> Any person who believes he or she has been the target of sexual harassment is encouraged to inform the offending person orally or in writing that such conduct is unwelcome and offensive and must stop.<br /> <br /> If the person does not wish to communicate directly with the offending person, or if such communication has been ineffective, the person is encouraged to report the unwelcome conduct as soon as possible to any officer, who will take the appropriate action.</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Meetings 2011-02-26T20:31:10Z

<p>Fvox13: /* Agenda */</p> <hr /> <div>= Minutes =<br /> See [[MIBS_Simplified_Rules_of_Coordinated_Consensus_through_Chaos#The_Meeting_Agenda]] for agenda template<br /> <br /> == March 1, 2011 ==<br /> === Agenda ===<br /> <br /> # Approve draft minutes of the last meeting<br /> # Consent Agenda<br /> ## Approve/ratify [[Conflict of interest policy]]<br /> # Officer Reports<br /> ## [[President]]<br /> ## [[Vice-President]]<br /> ## Treasurer <br /> ## Secretary<br /> # [[Member Reports]]<br /> # Adjournment<br /> <br /> === Minutes ===<br /> NULL<br /> <br /> == February 1, 2011 ==<br /> === Agenda ===<br /> <br /> # Approve draft minutes of the last meeting<br /> # Consent Agenda<br /> ## Create New Membership levels<br /> ### Friends of Interlock - These are people on the Interlock mailing list or receiving the Interlock &quot;newsletter&quot; (if we ever create one).<br /> ### Non-Voting Member - People paying $25/month and signing a membership agreement will be allowed to use all the facilities at the space but will not have a vote on business matters and will not receive a key to the space.<br /> ### Full Member - People paying $50/month and signing a membership agreement will have 24x7 access to the space via a key, full use of all facilities and the right to vote on any and all business matters.<br /> ### Student Member - Full time matriculated students paying $35/month and signing a membership agreement will have all the rights and privileges of a full member.<br /> ##<br /> # Officer Reports<br /> ## [[President]]<br /> ## [[Vice-President]]<br /> ## Treasurer <br /> ## Secretary<br /> # [[Member Reports]]<br /> # Adjournment<br /> <br /> === Minutes ===<br /> ==== Initialization ====<br /> <br /> 19:13<br /> <br /> ==== Consent Agenda ====<br /> <br /> No objections: Passed<br /> <br /> ==== Officer Reports ====<br /> ===== President =====<br /> * Wiki=Spam<br /> ** We need long-term fix, accounts disabled right now<br /> ** 1st Global Hack-a-thon<br /> *** Stream out and in<br /> **Cupcake:<br /> ***Tube within-tube <br /> *** lost by postal service :(<br /> *** Well, it didn't get there yet<br /> * CNC board router<br /> ** Getting last set of bearings<br /> * Signup for lighting talks!<br /> =====VP=====<br /> * See wiki page <br /> <br /> =====Secretary=====<br /> *(nothing)<br /> <br /> =====Treasurer =====<br /> * Everybody paid (much rejoicing)<br /> ** ~$3000 in bank, $230 in cash <br /> ** Rent and Frontier to pay still<br /> ** Taxes and all the jazz too<br /> <br /> ==== Member Reports ====<br /> *Steve<br /> **Frontier sucks (we know this)<br /> *** met with owner of wireless ISP, could be taking care of Interlock!<br /> *** Next month's consent agenda will likely have new ISP<br /> *** Question about having both ISPs for a month to verify service<br /> <br /> *Ben:<br /> ** Failed switch caused most networking problems<br /> ** other problem due to frontier<br /> * Going to buy Phone card<br /> <br /> *Joe:<br /> * Zen kernel on black pedestal box<br /> ** Caused hardware errors :(<br /> * JustBill says another box gave him &quot;fits&quot;<br /> * Going to be making a box from other parts<br /> * Bio-diesel<br /> ** Ingredients <br /> *** Found NaOH (yay) <br /> *** May be making bio-diesel<br /> <br /> *Jamie:<br /> ** Thesis date: April 1st (no joke)<br /> ** Booksmart studios, On Anderson Ave<br /> <br /> == January 4, 2011 ==<br /> === Agenda ===<br /> <br /> # Approve draft minutes of the last meeting<br /> # Consent Agenda<br /> ## NULL<br /> # Officer Reports<br /> ## [[President]]<br /> ## [[Vice-President]]<br /> ## Treasurer <br /> ## Secretary<br /> # [[Member Reports]]<br /> # Adjournment<br /> <br /> === Minutes ===<br /> <br /> Attendance: Brian B. Alex, Ben, Brian S, Nick, Wayne, Carl, John, Mark, Carl, Jaimee, JustBill, Chris<br /> <br /> ==== Initialization ====<br /> <br /> 19:32<br /> <br /> ==== Consent Agenda ====<br /> <br /> NULL<br /> <br /> ==== Officer Reports ====<br /> #President:<br /> ## Not much<br /> ## Annual meeting, more follow-up needed<br /> ## CNC router, getting parts laser-cut<br /> ## Going to laser-cut factory, possible trip, going to Lima<br /> #VP:See wiki<br /> #Finance:15 members, 11 reg 3 student<br /> #Secretary: Alex's first meeting as secretary <br /> ==== Member Reports ====<br /> <br /> *Ben:<br /> ** new couch, new chair, new lockers, new shelves, cisco gear (for IPv6)<br /> ** presentation at 2600 on Friday<br /> ** chart of junk is gone, (can get cart back if needed)<br /> <br /> *Carl<br /> ** member levels<br /> *** more discussion tonight, to go on agenda next month<br /> <br /> *D.Joe<br /> ** Blew breaker (oh knowes!)<br /> ** Keep path to breaker open please<br /> ** Has web-power-switch <br /> *** if you want to use it talk to D.Joe (GPG-keys and such)<br /> *** Examples access point and project box<br /> <br /> *Bill<br /> ** Phone system is live <br /> ** Connecting with &quot;northwestern&quot; phone network<br /> ** looking for FSX FXO card<br /> ** VMware environment is up<br /> *** looking for 64-bit system with virtualizition key<br /> *** wishlist on the way<br /> ** Thursday is net-op meeting 7pm<br /> *** After Thursday meeting is show how to make power supply from ATX supply for ham<br /> <br /> <br /> ==== New Business ====<br /> <br /> No new business<br /> <br /> ==== Adjournment ====<br /> <br /> 19:43<br /> <br /> == December 7, 2010 ==<br /> === Agenda ===<br /> <br /> # Approve draft minutes of the last meeting<br /> # Consent Agenda<br /> ## NULL<br /> # Officer Reports<br /> ## [[President]]<br /> ## [[Vice-President]]<br /> ## Treasurer <br /> ## Secretary<br /> # [[Member Reports]]<br /> # Adjournment<br /> <br /> === Minutes ===<br /> <br /> Attendance: Brian B. Alex, Ben, Brian S, Nick, Wayne, Carl, John, Mark, Carl, Jaimee, JustBill, Chris<br /> <br /> ==== Initialization ====<br /> <br /> 19:32<br /> <br /> ==== Consent Agenda ====<br /> <br /> NULL<br /> <br /> ==== Officer Reports ====<br /> <br /> # [[President]]<br /> # [[Vice-President]]<br /> # Treasurer - 14 paying. Payouts even <br /> # Secretary - Mostly gave report on Network Meeting. Key points - Network meetings are now on the First Tuesday of the month. <br /> <br /> ==== Member Reports ====<br /> <br /> <br /> wayne - Sparkfun kit finally put together -- loves the workbench and tools that we have acquired. Will be converting Apple IIc power supply. Looking for 43cubic feet of helium for a good price for a balloon camera project. Interested in weather balloon project. <br /> <br /> Joe - We got a vmware ssh bash in host for remote access. pull down video screens up for projector <br /> <br /> Alex - Wheels are on robot. Needs a mech egineer to help mount motors on robot. Seeking help!!!!! <br /> <br /> ==== New Business ====<br /> <br /> No new business<br /> <br /> ==== Adjournment ====<br /> <br /> 19:41<br /> <br /> == November 2, 2010 ==<br /> === Agenda ===<br /> <br /> # Approve draft minutes of the last meeting<br /> # Consent Agenda<br /> ## Interlockroc.___ domain renewal: transfer all of the domains to their own GoDaddy account and update the contact information to use an email address that goes to the officer list. Renew interlocroc.org for 3 years. Renew interlockroc.net and interlockroc.com for 1 year.<br /> ## Soldering Equipment - Interlock part of purchase -- ~$125<br /> ### Purchase item #2 on [[Wishlist: Soldering]], -- already has 50% member pledges<br /> ### Purchase remaining items [[Wishlist: Soldering]] (items 1,3) when there is 50% member contributions.<br /> # Officer Reports<br /> ## [[President]]<br /> ## [[Vice-President]]<br /> ## Treasurer <br /> ## Secretary<br /> # [[Member Reports]]<br /> # New Business<br /> # Adjournment<br /> <br /> === Minutes ===<br /> <br /> Attendance: Brian B, Mark, Alex, Carl, JustBill, Brian S, Jay, Andrew, Steve<br /> <br /> ==== Initialization ====<br /> <br /> 19:24<br /> <br /> ==== Consent Agenda ====<br /> <br /> # Approved<br /> # move to new business<br /> <br /> ==== Officer Reports ====<br /> <br /> # [[President]]<br /> # [[Vice-President]]<br /> # Treasurer <br /> # Secretary<br /> <br /> ==== Member Reports ====<br /> <br /> Drew - vistited HackDC and enjoyed their hackerspace and their old style arcade game.<br /> <br /> Brian S - CAM pizza is solidfied for discount. Dial from the phone at the space and get a %25 discount. Mention Interlock from any other phone and get %15 off.<br /> <br /> Steve - fundraising for the HAM antenna for the roof. Possible starting of Technical HAM class based upon interest.<br /> <br /> ==== New Business ====<br /> <br /> From above #2b - Soldering extra's. After discussion no objection.<br /> <br /> ==== Adjournment ====<br /> <br /> 19:40<br /> <br /> == October 5, 2010 ==<br /> === Agenda ===<br /> <br /> # Approve draft minutes of the last meeting<br /> # Consent Agenda<br /> ## Spend $200 on promo drink tickets for the Rochester Security Summit after party, to be given out from the Interlock table situated in the summit's CTF room.<br /> ## Spend $150 to sponsor Barcamp Rochester. We will get our logo on their tshirt and website, as well as a table at the event where we can schmooze and sell shirts.<br /> ## Spend $150 to purchase the Harbor Freight tools listed here: [[Wishlist:_tools]]<br /> # Officer Reports<br /> ## [[President]]<br /> ## [[Vice-President]]<br /> ## Treasurer - We currently have maintained our membership level. We had a loss of one and a gain of one. We have enough funds to cover all three of consent agenda. <br /> ## Secretary - Treasurer had given my report.<br /> # [[Member Reports]]<br /> # Old Business<br /> ## Approve [[network acceptable use policy]] and its addition to the membership agreement.<br /> ## Approve mutual discounts with Coworking, and associated logistics.<br /> # New Business<br /> # Adjournment<br /> <br /> === Minutes ===<br /> <br /> Attendance: Drew, Nick, Brian, Joe, Ben, Carl, Mark, Bill, Jaimee, Wayne <br /> <br /> ==== Initialization ====<br /> <br /> 19:05<br /> <br /> ==== Consent Agenda ====<br /> <br /> # Approved<br /> # Approved<br /> # Moved to new business by Joe - After discussion it was Approved<br /> <br /> ==== Officer Reports ====<br /> <br /> # [[President]]<br /> # [[Vice-President]]<br /> # Treasurer - We currently have maintained our membership level. We had a loss of one and a gain of one. We have enough funds to cover all three of consent agenda. <br /> # Secretary - nothing to add.<br /> <br /> ==== Member Reports ====<br /> <br /> # Carl - Electronics class will begin soon. They will be 8:00 PM on Tuesdays and will run for at least 5 classes.<br /> # Drew - Posters for Barcamp will be put up and wanted to propagandize the Hungerford.<br /> # Mark &amp; Wayne - They have started a spotlight &quot;Batman&quot; project. May need some specialized lights. <br /> # Wayne - Working to put a showing of &quot;Get Lamp&quot; together.<br /> # Jaimee - Her show is Oct 07. 5-8 PM<br /> <br /> ==== Old Business ====<br /> <br /> # Approved<br /> # Approved<br /> <br /> ==== New Business ====<br /> <br /> # Consent Agenda 3 - Joe had a question regarding spending of money for money and future purchase of tools. Suggestions include cost matching. He will discuss outside of meeting and consent to purchase of current agenda list. <br /> <br /> ==== Adjournment ====<br /> <br /> 19:29<br /> <br /> == September 7, 2010 ==<br /> === Agenda ===<br /> # Approve draft minutes of the last meeting<br /> # Consent Agenda<br /> ## Approve [[network acceptable use policy]] and its addition to the membership agreement.<br /> ## Approve mutual discounts with Coworking.<br /> # Officer Reports<br /> ## [[President]]<br /> ## [[Vice-President]]<br /> ## Treasurer<br /> ## Secretary<br /> # [[Member Reports]]<br /> # New Business<br /> # Adjournment<br /> <br /> === Minutes ===<br /> Attendance: Carl, Ben, Nick, DeeJoe, Brian, Mark, Andrew, Chris, John<br /> <br /> ==== Initialization ====<br /> Meeting started at 8:15, and hour later than usual due to a scheduled class conflict.<br /> <br /> ==== Consent Agenda ====<br /> Network AUP and Coworking discounts are objected to by Deejoe and others. Moved to new business.<br /> <br /> ==== Officer Reports ====<br /> Officer reports are linked in the agenda above. No report from the Secretary or Treasurer.<br /> <br /> ==== Member Reports ====<br /> Ben gives a report on the new Asterisk box, and other networking developments.<br /> <br /> ==== New Business ====<br /> Network AUP is considered half-baked by most members in attendance. It is suggested that the language needs to be updated before it will be approved.<br /> <br /> Coworking discount numbers are generally acceptable, but the logistics of how to implement the discounts is not specified. That information will need to be specified before approval.<br /> <br /> ==== Adjournment ====<br /> Meeting adjourns at 8:30<br /> <br /> == August 3, 2010 ==<br /> === Agenda ===<br /> # Approve draft minutes of the last meeting<br /> # Consent Agenda<br /> ## Move Septembers meeting to 8:00 PM<br /> # Officer Reports<br /> ## [[President]]<br /> ## [[Vice-President]]<br /> ## Treasurer<br /> ## Secretary<br /> # [[Member Reports]] <br /> # Adjournment<br /> <br /> === Minutes ===<br /> Attendance: Bill, Wayne, Nick, Ben, Brian, Mark, Joe, and Carl<br /> <br /> ==== Initialization ====<br /> 19:10<br /> <br /> ==== Officer Reports ====<br /> President - See link above<br /> <br /> Vice President - See link above<br /> <br /> Treasurer - Members late with monies: 3, members 30+ days late: 3, members 60+ days late: 2. Reminders sent to all, door shutoff for 30+ and removed as member 60+. Please pay and email Treasurer if any issue. 11 members paid (10 regular and 1 student). <br /> <br /> Secretary - Proud Mary 19:11<br /> <br /> ==== Member Reports ====<br /> <br /> Carl - Informed group about the fairly busy Linux workshop this past weekend. Several helpers and people showed up to learn and install linux. Needed someone to make sure that Linux Workshop doors need to be open Aug 21st buy a member. JustBill volunteered. He is also thinking of setting up one of the Make Nights to do build your own NAS installs - more info to follow on mailing list. Carl has also volunteered to teach a basic electronics class after the upcoming Processing/Arduino class mentioned on the mailing list.<br /> <br /> Joe - LUGOR will be starting their meetings soon. See Joe for details.<br /> <br /> ==== Consent Agenda ====<br /> <br /> Due to upcoming Processing/Arduino class it was proposed to group to have Septembers Board meeting at 8:00 as to not interfere with the class. Nobody objected. Motion passed.<br /> <br /> ==== New Business ====<br /> <br /> Just a reminder that there is an upcoming 5 week class on Processing and Arduino. Many members have expressed interest and will be doing the class. More info [http://training.oreilly.com/arduino/] . See you there.<br /> <br /> ==== Adjournment ====<br /> <br /> 19:28<br /> <br /> == July 5, 2010 ==<br /> === Agenda ===<br /> # Approve draft minutes of the last meeting<br /> # Consent Agenda<br /> ## Renew our Meetup.com service at $72 for six more months<br /> ## Reimburse Beardicus for non-pre-ordered Interlock t-shirts (less than ten at the moment) and hold in &quot;inventory&quot; for future sale.<br /> # Officer Reports<br /> ## [[President]]<br /> ## [[Vice-President]]<br /> ## Treasurer<br /> ## Secretary<br /> # [[Member Reports]] <br /> # Adjournment<br /> <br /> === Minutes ===<br /> <br /> ==== Members Present ====<br /> Attendance: Carl, Mark, Ben, Brian, Wayne, Nick, Bill<br /> <br /> ==== Initialization ====<br /> 19:45<br /> <br /> ==== Officer Reports ====<br /> President - He made a summary of Interlock updates. We were at FOSSCON and held a table.<br /> <br /> Vice President - [[Vice-President#Officer_Report_7.2F6.2F2010| see report]]<br /> <br /> Treasurer - Multiple finances discussed. More detailed report to follow but it was about income, members, and total expenditures. <br /> <br /> Secretary - Hi My name is &quot;Just&quot;Bill and I'm the new secretary till next voting cycle. Please forgive me for any of my mistakes.<br /> <br /> ==== Member Reports ====<br /> <br /> Nick - Just wanted to announce that BinaryMan (Chris) received his HAM technical license.<br /> <br /> ==== Consent Agenda ====<br /> <br /> Moved to new business due to Treasurers report<br /> <br /> ==== New Business ====<br /> <br /> # Renew Meetup.com - Mark will float the cost and the Interlock will keep an open purchase order for reimbursement until fund get more soluble.<br /> # Reimbursement for T-Shirts. Same as #1 will keep open purchase order until funds are more available. Brian will fund until then.<br /> <br /> ==== Adjournment ====<br /> <br /> 20:06<br /> <br /> == June 1, 2010 ==<br /> === Agenda ===<br /> # Approve draft minutes of the last meeting<br /> # Officer Reports<br /> ## [[President]]<br /> ## [[Vice-President]]<br /> ## Treasurer<br /> # [[Member Reports]] <br /> # Adjournment<br /> <br /> === Minutes ===<br /> <br /> ==== Members Present ====<br /> Attendance: Carl, Nick, Mark, Brian, Steve, Bill, Ben, Wayne<br /> <br /> ==== Initialization ====<br /> President starts the meeting at 7:15. Minutes from last meeting are approved.<br /> <br /> ==== Officer Reports ====<br /> [[President]] gives his report (linked)<br /> [[Vice-President]] gives his report (linked)<br /> <br /> ==== Member Reports ====<br /> Steve gives a member report on an intranet portal he's developing for Interlock... wikis, blogs, files, events (and much much more!)<br /> <br /> ==== Adjournment ====<br /> Meeting adjourns at 7:30.<br /> <br /> === Addition ===<br /> Change in officers. Alan Dipert and Ashley McClelland have left the organzation. Brian Boucheron is the new president. We are still looking for a Secretary.<br /> <br /> == May 4, 2010 ==<br /> === Agenda ===<br /> # Approve draft minutes of the last meeting<br /> # The Consent Agenda<br /> ## Approve the [http://www.interlockroc.org/wiki/index.php?title=Bylaws&amp;oldid=1169 bylaws]<br /> # Officer Reports<br /> ## [[President]]<br /> ## [[Vice-President]]<br /> # [[Member Reports]] <br /> # [[Old Business]] <br /> # [[New Business]]<br /> # Adjournment<br /> <br /> === Minutes ===<br /> <br /> ==== Members Present ====<br /> Brian, Alan, Ashley, Mark, Alvaro, Carl, Ben, Steve, Nick, Rowan, Jim, Wayne<br /> <br /> ==== Initialization ====<br /> President starts the meeting at 7:08. Last meeting's draft minutes were approved.<br /> <br /> ==== Consent Agenda ====<br /> No objections.<br /> <br /> ==== Officer Reports ====<br /> [[President]] gives his report (linked)<br /> <br /> [[Vice-President]] gives his report (linked)<br /> <br /> The Treasurer gives her report. Membership is down 1 from last month, expenses are as per usual.<br /> <br /> ==== Member Reports ====<br /> Carl mentions the Linux workshops for the next two months (see the calendar)<br /> <br /> <br /> ==== Adjournment ====<br /> Meeting adjourns at 7:26.<br /> <br /> == April 20, 2010 (Special Meeting) ==<br /> === Agenda ===<br /> # The Consent Agenda<br /> ## Approve [[petty cash budget]] <br /> # [[Officer Reports]] <br /> ## [[President]]<br /> ## [[Vice-president]]<br /> ## [[Treasurer]]<br /> ## [[Secretary]]<br /> # [[Member Reports]] <br /> # [[Old Business]] <br /> # [[New Business]]<br /> # Adjournment<br /> <br /> === Minutes ===<br /> <br /> Members in attendance: Brian, Mark, Ashley, Alan, Joe, Jim, Rowan, Carl, <br /> <br /> President starts the meeting at 7:10<br /> <br /> ==== Consent Agenda ====<br /> Consent agenda passes without objection.<br /> <br /> ==== Adjournment ====<br /> Meeting is adjourned.<br /> <br /> == April 6, 2010 ==<br /> <br /> === Agenda ===<br /> <br /> # Draft minutes of the last meeting<br /> # The Consent Agenda<br /> ## Special meeting, April 20th to discuss improving [[Recruitment|recruitment]], modifying our [[Budget|budget]], improving our [[Finances|finances]].<br /> ## Approve [[Bylaws]]<br /> ## Approve [[Membership Agreement]]<br /> # [[Officer Reports]] <br /> ## [[President]]<br /> ## [[Vice-president]]<br /> ## [[Treasurer]]<br /> ### Approve [[Budget]]<br /> ## [[Secretary]]<br /> # [[Member Reports]] <br /> # [[Old Business]] <br /> # [[New Business]]<br /> ## [[Hospitality budget]]<br /> ## [[Cleaning supplies]]<br /> ## [[Hacker of The Month|Hacker of the Month]] Funds<br /> ## [[Inventory]]<br /> # Adjournment<br /> <br /> === Minutes ===<br /> Members Present: Brian, Mark, Steven, Carl, Ben, Nick, Alvaro, Rowan, Alan, Ashley, Tim<br /> <br /> The president begins the meeting at 7:08<br /> <br /> Minutes from the March 3 meeting are approved.<br /> <br /> ==== Consent Agenda ====<br /> Joe objects to passing the bylaws. Moved to new business.<br /> All other motions pass.<br /> <br /> ==== Officer Reports ====<br /> [[President]] gives his report (Linked)<br /> [[Vice-President]] gives his report (Linked)<br /> <br /> Treasurer gives her report on the state of our funds and membership. Budget can be viewed at the Google Docs site.<br /> <br /> Secretary has nothing to report<br /> <br /> ==== Member Reports ====<br /> Rowan reports on the IP web camera and LV jack boxes.<br /> <br /> Tim reports on networking. Network will be complete by 4/7/2010, minus boxes for jack.<br /> <br /> ==== Old Business ====<br /> NULL<br /> <br /> ==== New Business ====<br /> * Bylaws<br /> The issue stated is that the bylaws don't make it clear what the powers of the board of directors vs. the membership. Language is proposed to make this clearer.<br /> <br /> Rowan brings up a concern about term limits for board of directors and officers.<br /> <br /> Joe proposes that the board members be given some power for action between meetings.<br /> <br /> Bylaws are not passed and are deferred to the next regular meeting.<br /> <br /> * Hospitality budget is discussed, but not passed. Summary is that $20 would be budgeted each month for First Friday supplies and other essentials. Details will be provided at later meeting.<br /> <br /> ==== Adjournment ====<br /> Meeting is adjourned at 7:53<br /> <br /> == March 9, 2010 ==<br /> Lightning Talks:<br /> <br /> Signed Up: Alan(Machines that think), Alvaro(Orienteering, Remote Backup), Andrei(Contemporary Art), Ashley(Learning Programming), Beardicus(Wee Booklet), Ben(irssi+screen), Carl(Cat5, Soldering), Jason(Low Impact Local Network Recon), Justin(Go, XSS/XSRF Demo), Joe(Pymol Molecular Viewer), Mark(XSS/XSRF), Steve(Free Public Wifi), Remy(Open Video Chat Program team Intro)<br /> <br /> == March 2, 2010 ==<br /> <br /> Members Present: Brian, Mark, Ashley, Alan, Carl, Joe, Wayne, Nick, Ben, Steven<br /> <br /> The president begins the meeting at 7:11.<br /> <br /> === Consent Agenda ===<br /> <br /> NULL<br /> <br /> === Officer Reports ===<br /> <br /> (Reports were provided orally, with no hardcopy transcriptions)<br /> <br /> The President reports on the general status of the organization.<br /> <br /> The Vice President gives an update on the status of the networking project.<br /> <br /> The Secretary has nothing to report, and requests future officer reports be provided in writing for more comprehensive minutes.<br /> <br /> The Treasurer has nothing to report this month.<br /> <br /> === Member Reports ===<br /> <br /> Joe presents his knit n900 cozy and clues us in to virtualization plans for the space<br /> <br /> Steven nominates himself safety dictator, explains plans to abuse his power<br /> <br /> === Old Business ===<br /> <br /> NULL<br /> <br /> === New Business ===<br /> <br /> NULL<br /> <br /> === Adjournment ===<br /> <br /> TRUE<br /> <br /> == February 23, 2010 ==<br /> * Agenda<br /> ** Introductions<br /> ** Organization Updates<br /> ** Project Updates<br /> ** Open Announcements<br /> *** Lightning Talks<br /> <br /> == February 23, 2010 ==<br /> * Agenda<br /> ** Introductions<br /> ** Organization Updates<br /> *** Move in timeline<br /> *** MIBS reminder<br /> *** March 2nd first meeting<br /> ** Project Updates<br /> ** Open Announcements<br /> *** Lightning Talks<br /> <br /> == February 15, 2010 ==<br /> * Agenda<br /> ** Introductions<br /> ** 15 Min MIBS review/walkthrough<br /> ** Organization Updates<br /> ** Project Updates<br /> ** Open Announcements<br /> <br /> == February 9, 2010 ==<br /> * Agenda<br /> ** 15 Min MIBS review<br /> ** Introductions<br /> ** Last Week Meeting Review<br /> ** Organization Updates<br /> ** Project Updates<br /> ** Open Announcements<br /> <br /> == February 2, 2010 ==<br /> * Agenda<br /> ** Introductions<br /> ** Last Week Meeting Review<br /> ** Organization Updates<br /> *** Bank Account/Paypal<br /> *** Meeting Changes<br /> **** Consensus through Chaos <br /> **** Official Meetings monthly but weekly open nights<br /> **** Officer roles review<br /> **** Voting Scenarios<br /> ** Project Updates<br /> *** First Friday Organization<br /> *** Door Security System<br /> *** Other member projects<br /> ** Open Announcements<br /> <br /> == January 26, 2010 ==<br /> * Agenda<br /> ** Introductions<br /> ** Last Week Meeting Review<br /> ** Organization Updates<br /> *** Bank Account<br /> ** Project Updates<br /> *** Door/Security System<br /> ** Open Announcements<br /> * Minutes<br /> ** Bank account: in motion. Waiting on some paper work<br /> ** Door project: learning about the ibuttons<br /> ** Sneyha: outreach meeting. <br /> *** Need ideas for first friday<br /> *** planning on a green screen<br /> ** RemyD: Who else comes out for first friday?<br /> *** Sneyha: A ton of the people in the building<br /> ** Carmen: has a project related to inventoring computers<br /> ** Discussion about doing classes<br /> ** Alan: Haiti relief outreach<br /> ** Rowan: HAM radio group<br /> ** Alan: be kind on IRC<br /> ** RemyD: www.opensource.com - news portal for open source articles<br /> ** Sneha: wine tour<br /> ** RemyD: Stallman is coming to town on Feb 23<br /> ** Steve: Enable effing SSL on google apps!<br /> <br /> == January 19, 2010 ==<br /> * Agenda<br /> ** Introductions<br /> ** Last Week Meeting Review<br /> ** Organization Updates<br /> *** Changes to bylaws<br /> *** Changes to member agreement<br /> ** Project Updates<br /> ** Open Announcements<br /> * Minutes<br /> 1/19<br /> *introductions, alan, deejoe, carl, brian, steve, nick, josh, alex, ben, bill, ashley, mark, jon, chris, remy<br /> <br /> carl outreach summary:<br /> ** join first friday<br /> ** video commercial<br /> ** running robots<br /> ** barcamp in april<br /> ** lightning talks at barcamp<br /> ** fosscon - june - remyd is an organizer<br /> ** linux workshop outreach went well - 12 people came - next one in February<br /> ** maybe talk to Lugor about doing hands on workshop after a lugor discussion<br /> ** writing workshop to teach anyone how to write<br /> ** ashley: keep writing focused<br /> * lightning talks again<br /> *alan: want to also give back to the community like linux workshop<br /> * alan:bylaws and membership agreement<br /> *alan, ashley, mark, brian and others met to go over bylaws and mission statement<br /> * changes are on the wiki<br /> *ashley: maybe do a mock mibs walkthrough<br /> *alan: share the google doc to everyone<br /> * alan got the EIN<br /> * thursday mark, brian, ashley, alan, will be going to the bank<br /> *question: josh: how open are finances<br /> *answer: everyone: as open as you want to be. meetings will have <br /> *ben: if anyone has suggestions for the space design, make them known now<br /> *steve: internet connection<br /> ** the acct rep received fax<br /> ** she's going to let us know install date<br /> *alan: programming for beginners class<br /> ** work with python group in Rochester<br /> *brian: beginning electronics<br /> ** make magazine has beginner electronics book<br /> ** good for doing a class or group<br /> * dude: we can get cheap stuff from radio shack and the internet has parts<br /> *joe: bulk silly putty reminder<br /> *steve: bulk coffee/tea maker<br /> *chris: organizational membership to amazon<br /> ** you can pull out technical books<br /> ** view them online but access to TONS of books<br /> ** not sure on the costs<br /> *Brian: Pledgie<br /> ** people can join and pledge their amount<br /> ** when it gets the amount it does whatever they've been planning (silly putty)<br /> ** another space used it successfully<br /> <br /> == January 12, 2010 ==<br /> * Attended: Carl, Avezou, Mora, Steve, Brian, Chris, Rowan, Andre, Sneha, Remy, Shawn, Carmen, Josh, Gina, Jimmy, Christina, Alvaro, Rachel, Brian, Ashlee, Ben, Mark, Ryan, Justin, Nick, Alan, Alex<br /> * Agenda<br /> ** Introductions<br /> ** Last Week Meeting Review<br /> ** Organization Updates<br /> ** Voting:<br /> *** IRC<br /> ** Project Updates<br /> ** Open Announcements<br /> ** EVENT: [http://www.meetup.com/Rochester-Hackerspace/calendar/12121705/ Lightning Talks]<br /> <br /> == January 5, 2010 ==<br /> * Attended: Ryan, Dawn, Carl, Steve, Josh, Alvaro, Alan, Bryan, Joe, Andrei, John, Ashley, Justin, Rowan<br /> * Agenda<br /> ** Introductions<br /> ** Updates<br /> *** Recap of SCORE meeting (Alan)<br /> ** Anything else?<br /> * Discussed<br /> ** SCORE<br /> *** With lawyer, 501(3)c process 6mo - year, $1000 - $1500<br /> *** Importance of mission statement<br /> ** Separation of concerns: member agreement vs. bylaws<br /> *** agreement is for limiting liability and other bare minimums<br /> *** bylaws part culture, part rules<br /> *** bylaws are really only about starting and stopping processes<br /> *** we need a solid mission statement to define ourselves and guide decisions/priorities<br /> ** Outreach, community service, donation possibilities<br /> *** &quot;Linux Q &amp; A&quot; days<br /> <br /> == December 22, 2009 ==<br /> * Agenda<br /> ** NONE: relaxing discussion<br /> <br /> == December 15, 2009 ==<br /> <br /> * Attended: Brian, Jim, Nick, Avezou, Carl, Sneha, Steve, Ben, Ashley, Carmen, Joe, Bryan, Paul, Tim, Alvaro, JP, Joshua,<br /> * Agenda<br /> ** Introductions<br /> ** Updates/Announcements<br /> ** ISP Options: Steve S.<br /> ** Intro to Wordpress (brief): Ben W.<br /> ** Projects<br /> ** Discuss next weeks Lightning Talks<br /> ** Holiday events, potlucks, parties, hoedowns?<br /> ** Best time to meet in the future<br /> * Discussed:<br /> ** Introductions, met a few new prospects<br /> ** Ben's Wordpress intro presentation<br /> ** Discussion of our use of Wordpress and how we want to handle posting<br /> ** Steve's ISP presentation<br /> ** Wooby talks lightning, and projects<br /> ** Deejoe gives a passionate lightning talk about plastic bag storage<br /> <br /> == December 8, 2009 ==<br /> * Attended: Mark, Brian, Steve, Dan, Andrei, Joe, Carl, Carmen, Sneha, Matt, Ben, Bryan, Josh [...]<br /> * Agenda:<br /> **7: Introductions and updates, go over [http://wiki.interlockroc.org/index.php?title=MIBS_Simplified_Rules_of_Coordinated_Consensus_through_Chaos MIBS meeting rules]<br /> **7:30: Hackerspace Presentation: Mark<br /> **8: Move to new space<br /> * Discussed:<br /> ** Introductions<br /> ** Officers announced. Mostly people on the lease or incorporation paperwork.<br /> ** Mark presented a bit on MIBS rules<br /> ** [http://docs.google.com/present/view?id=dnbv9rr_42ft4q8vff Hackerspace presentation]<br /> ** Sneha discusses public outreach activities<br /> * Caravan to the temp space for discussion and beverages<br /> <br /> == December 1, 2009 ==<br /> * Attended: Carl, Ben, Jimmi, Kristina, Steve, Ashley, Andrei, <br /> * Discussed: <br /> ** Bylaws went over a lot of the details. <br /> ** Bylaws: Decided to have an official meeting once a month unless otherwise requested <br /> ** Discussed dues<br /> ** updated everyone on lease signing status<br /> ** Ashley updated us on documents for incorporation<br /> ** Voted on whether or not to get the temp space or skip it and wait for the real space. Agreed to get the temp<br /> ** Introduced new members discussed goals of the organization<br /> * Action Items:<br /> ** Directors: Sign lease and setup temp space<br /> <br /> == November 23, 2009 ==<br /> <br /> * Attended<br /> ** Mark, Brian, Ashley, Alan, Sneha, Carmen, Carl, Bryan, Ben, Jeremy, Rich<br /> * Video: [http://www.ustream.tv/recorded/2628387 Part 1]<br /> * Discussed<br /> ** Basement space at 1115 Main Street<br /> *** $390 + electricity<br /> *** Ready by February<br /> ** Temporary space available immediately<br /> *** $280 + electricity<br /> ** Network connectivity options<br /> *** Business class roadrunner $79 a month<br /> *** Netsville<br /> ** Dues<br /> *** Start payment 1st of December<br /> *** Application form<br /> ** Business checking accounts and accounting<br /> ** First Month's rent<br /> ** Logos<br /> ** Wiki/Website stuff<br /> *** maybe looking for a wiki with better ACLs<br /> *** decision to departmentalize functions - wiki, website, blog, etc<br /> ** Dues through paypal for first month<br /> ** Bryan shows his illuminated bidness card<br /> ** Discussion about who will be the incorporators<br /> ** Presentation ideas for future meetings<br /> ***Python intro class<br /> ***Wordpress tutorial<br /> ***Software Defined Radio<br /> **Ham radio discussion<br /> ** Future meetings may have first 1/2 hour as business-related matters, come afterwards if you're not interested in the nitty gritty of forming the space<br /> * Actions<br /> ** Mark: Setup paypal account and email address<br /> ** Mark: Put together a membership package<br /> ** Alan: Put membership form online<br /> ** Goal: Have membership dues on December 1st<br /> ** Goal: Sign lease on Monday November 30th<br /> <br /> == November 17, 2009 ==<br /> * Attended: Mark, Sneha, Carmen, Ashley, Alan, Jimmi, Krystina, James, Justin, Robert, Joe, Ben, JP, Brian, (David)<br /> * Recordings - [http://www.ustream.tv/recorded/2580888 Part 1]- [http://www.ustream.tv/recorded/2581335 Part 2]<br /> * 1st meeting streamed online (ustream)<br /> * Decided on Interlock as a group name.<br /> ** interlocroc.net, .com and .org domains have been acquired<br /> * Discussion about three potential locations<br /> ** Griffith Ave<br /> *** 3000/$1500 a month<br /> *** No security deposit<br /> *** Utilities = $200 a month<br /> *** A bit too pricey<br /> ** E Main St<br /> *** 1000/$450<br /> *** 2000/$725<br /> *** Utilities = $150 a month<br /> ** Village Gate<br /> *** 500/$325<br /> *** Utilities = $60 a month<br /> * Talking about the budget<br /> ** Would prefer it to be about $35, but it will probably be higher at first until we get more members<br /> ** Looking at 501.c3<br /> ** Contacts in Buffalo chapter could be useful with this business setup<br /> ** Dues<br /> *** $50 - Normal<br /> *** $35 - Student<br /> * Trip to Buffalo Chapter<br /> ** Visit to see what they have there<br /> ** After thanksgiving, on the weekend<br /> *** Important for sponsorships<br /> <br /> Action Items For Next week:<br /> * Form a holding company (LLC, S-Corp) to get a bank account<br /> * Focus on making the Main St. building work (talk to Felix, discuss details, find temp location)<br /> * Plan for best way to form an NFP<br /> * Create a focus group for developing a website<br /> <br /> ==November 11, 2009==<br /> *Location: Spot Coffee<br /> *Attended:<br /> **Mark, Brian B., PT, Sneha, Dan, Carl, Andrei, Bryan, Josh, Ashley, Alan, Carmen<br /> *Discussed:<br /> **Summary of goals thus far, for new attendees.<br /> **Updates from members about spaces scouted, etc. <br /> ***Sneha: 1000 square feet, 600 a month, Portland Ave., with storefront<br /> ***Look into spaces near the Public Market? High rent for RR55 ($900)<br /> ****Other spaces besides the refurbed railroad area? Space above cheese shop area?<br /> **Introductions<br /> **Show and Tell<br /> ***Bryan<br /> ****guitar hacks<br /> *****tuning geegaws<br /> *****patents<br /> ***Andrei<br /> ****[http://www.makershed.com/ProductDetails.asp?ProductCode=MSBM brain machine kit]<br /> ****circuit bent toy horn<br /> ***Mark<br /> ****lockpicking sets<br /> ****garmin gps units, wardriving discussion<br /> *****obligatory [http://www.imdb.com/title/tt0086567/ Wargames] shoutout<br /> ****defcon badges<br /> ****bump key discussion<br /> ***Brian B.<br /> ****bookbinding<br /> ****sketchbooks<br /> ****[http://www.ponoko.com/ Ponoko] business cards<br /> ****[http://www.ponoko.com/ Makerbot] contact: sample print will be mailed out this weekend, hackerspace discount is available<br /> ****laser cutting, found [http://www.classact.net/ Class Act Engraving] in Akron, NY. Epilog laser reseller<br /> ***Carmen<br /> ****suitcase computer<br /> **Random discussion<br /> ***Kegerator w/ Nagios monitoring<br /> <br /> *Actions<br /> **None specified<br /> <br /> == November 6, 2009 ==<br /> * Location: Spot Coffee<br /> * Attended:<br /> ** Mark, Carmen, Sneha, Ben, Brian B, Stephen, Bryan S, Andrei, Tom, Josh, David, Karl<br /> * Discussed:<br /> ** announcements from last week - flyers, wiki<br /> ** attendees' backgrounds and vision for the space<br /> ** rough plan of action re: naming, incorporation, non-profit filing<br /> ** future meeting ideas, including demos and presentations<br /> ** (EDIT)<br /> * Actions:<br /> ** contribute to the wiki<br /> ** think of names<br /> ** (EDIT)<br /> <br /> == October 28, 2009 ==<br /> * Location: Spot Coffee<br /> * Attended: Mark, Jeff, Carmen, Brian, Alan, Eric, Joe, Andrei, Bryan, Greg, <br /> * Discussed:<br /> ** ideas<br /> ** made flyers<br /> ** other spaces<br /> ** meet and greet<br /> * Actions:<br /> ** Mark: setup a wiki<br /> ** Mark: print out flyers<br /> <br /> == October 21, 2009 ==<br /> * Location: Spot Coffee<br /> * Attended:<br /> ** Jerel, Matt, Mark, Jeff, Greg, Jimmi, Krystina<br /> * Discussed:<br /> ** meet and greet<br /> ** buffalo hackerspace<br /> * Actions:</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Conflict_of_interest_policy 2011-02-16T03:02:35Z

<p>Fvox13: Created page with &quot;== Interlock Rochester Conflict of Interest Policy == ===Section 1: Purpose=== Interlock Rochester, Inc. is a non-profit, tax-exempt organization. Maintenance of its tax-exempt ...&quot;</p> <hr /> <div>== Interlock Rochester Conflict of Interest Policy ==<br /> <br /> ===Section 1: Purpose===<br /> Interlock Rochester, Inc. is a non-profit, tax-exempt organization. Maintenance of its tax-exempt status is important both for its continued financial stability and for public support. Therefore, the operations of Interlock Rochester, Inc. are subject to scrutiny by and accountable to governmental authorities as well as to members of the public.<br /> <br /> Consequently, there exists between Interlock Rochester, Inc. and its board, officers, and members, and the public a fiduciary duty, which carries with it a broad and unbending duty of loyalty and fidelity. The board, officers, and members have the responsibility of administering the affairs of Interlock Rochester, Inc. honestly and prudently, and of exercising their best care, skill, and judgment for the sole benefit of Interlock Rochester, Inc. Those persons shall exercise the utmost good faith in all transactions involved in their duties, and they shall not use their positions with Interlock Rochester, Inc. or knowledge gained therefrom for their personal benefit. The interests of the organization must be the first priority in all decisions and actions.<br /> <br /> <br /> <br /> ===Section 2: Persons Concerned===<br /> This statement is directed not only to directors and officers, but to all members who can influence the actions of Interlock Rochester, Inc.. For example, this would include all who make purchasing decisions, all voting members, and anyone who has proprietary information concerning Interlock Rochester, Inc.<br /> <br /> <br /> <br /> ===Section 3: Areas In Which Conflict May Arise===<br /> Conflicts of interest may arise in the relations of directors, officers, and members with any of the following third parties:<br /> # Persons and firms supplying goods and services to Interlock Rochester, Inc.<br /> # Persons and firms from whom Interlock Rochester, Inc. leases property and equipment.<br /> # Persons and firms with whom Interlock Rochester, Inc. is dealing or planning to deal in connection with the gift, purchase or sale of real estate, securities, or other property.<br /> # Competing or affinity organizations.<br /> # Donors and others supporting Interlock Rochester, Inc.<br /> # Agencies, organizations. and associations which affect the operations of Interlock Rochester, Inc.<br /> # Family members, friends, and other members.<br /> <br /> <br /> ===Section 4: Nature of Conflicting Interest===<br /> A conflicting interest may be defined as an interest, direct or indirect, with any persons or firms mentioned in Section 3. Such an interest might arise through:<br /> # Owning stock or holding debt or other proprietary interests in any third party dealing with Interlock Rochester, Inc..<br /> # Holding office, serving on the board, participating in management, or being otherwise employed (or formerly employed) with any third party dealing with Interlock Rochester, Inc..<br /> # Receiving remuneration for services with respect to individual transactions involving Interlock Rochester, Inc..<br /> # Using Interlock Rochester, Inc.’s time, personnel, equipment, supplies, or good will for other than Interlock Rochester, Inc.-approved activities, programs, and purposes.<br /> # Receiving personal gifts or loans from third parties dealing or competing with Interlock Rochester, Inc. Receipt of any gift is disapproved except gifts of a value less than $50, which could not be refused without discourtesy. No personal gift of money should ever be accepted.<br /> <br /> <br /> ===Section 5: Interpretation of This Statement of Policy===<br /> The areas of conflicting interest listed in Section 3, and the relations in those areas which may give rise to conflict, as listed in Section 4, are not exhaustive. Conflicts might arise in other areas or through other relations. It is assumed that the directors, officers, and members will recognize such areas and relation by analogy. The fact that one of the interests described in Section 4 exists does not necessarily mean that a conflict exists, or that the conflict, if it exists, is material enough to be of practical importance, or if material, that upon full disclosure of all relevant facts and circumstances it is necessarily adverse to the interests of Interlock Rochester, Inc. However, it is the policy of the board that the existence of any of the interests described in Section 4 shall be disclosed before any transaction is consummated. It shall be the continuing responsibility of the board, officers, and members to scrutinize their transactions and outside business interests and relationships for potential conflicts and to immediately make such disclosures.<br /> <br /> <br /> ===Section 6: Disclosure Policy and Procedure===<br /> Transactions with parties with whom a conflicting interest exists may be undertaken only if all of the following are observed:<br /> # The conflicting interest is fully disclosed;<br /> # The person with the conflict of interest is excluded from the discussion and approval of such transaction;<br /> # A competitive bid or comparable valuation exists; and<br /> # The board or a duly constituted committee thereof has determined that the transaction is in the best interest of the organization.<br /> Disclosure in the organization should be made to the President (or if she or he is the one with the conflict, then to the board chair), who shall bring the matter to the attention of the board or a duly constituted committee thereof. Disclosure involving directors should be made to the board chair, (or if she or he is the one with the conflict, then to the board vice-chair) who shall bring these matters to the board or a duly constituted committee thereof. The board or a duly constituted committee thereof shall determine whether a conflict exists and in the case of an existing conflict, whether the contemplated transaction may be authorized as just, fair, and reasonable to Interlock Rochester, Inc. The decision of the board or a duly constituted committee thereof on these matters will rest in their sole discretion, and their concern must be the welfare of Interlock Rochester, Inc. and the advancement of its purpose.<br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> ==Interlock Rochester Conflict of Interest Disclosure Statement==<br /> Preliminary note: In order to be more comprehensive, this statement of disclosure/questionnaire also requires you to provide information with respect to certain parties that are related to you. These persons are termed “affiliated persons” and include the following:<br /> # your spouse, domestic partner, child, mother, father, brother or sister; <br /> # any corporation or organization of which you are a board member, an officer, a partner, participate in management or are employed by, or are, directly or indirectly, a debt holder or the beneficial owner of any class of equity securities; and<br /> # any trust or other estate in which you have a substantial beneficial interest or as to which you serve as a trustee or in a similar capacity.<br /> <br /> ----<br /> <br /> # Name:<br /> # Capacity: board of directors, executive committee, officer, committee member, staff<br /> # Have you or any of your affiliated persons provided services or property to Interlock Rochester, Inc. in the past year? If yes, please describe the nature of the services or property and if an affiliated person is involved, the identity of the affiliated person and your relationship with that person<br /> # Have you or any of your affiliated persons purchased services or property from Interlock Rochester, Inc. in the past year? If yes, please describe the purchased services or property and if an affiliated person is involved, the identity of the affiliated person and your relationship with that person.<br /> # Please indicate whether you or any of your affiliated persons had any direct or indirect interest in any business transaction(s) in the past year to which Interlock Rochester, Inc. was or is a party? If yes, describe the transaction(s) and if an affiliated person is involved, the identity of the affiliated person and your relationship with that person.<br /> # Were you or any of your affiliated persons indebted to pay money to Interlock Rochester, Inc. at any time in the past year (other than travel advances or the like)? If yes, please describe the indebtedness and if an affiliated person is involved, the identity of the affiliated person and your relationship with that person.<br /> # In the past year, did you or any of your affiliated persons receive, or become entitled to receive, directly or indirectly, any personal benefits from Interlock Rochester, Inc. or as a result of your relationship with Interlock Rochester, Inc., that in the aggregate could be valued in excess of $1,000, that were not or will not be compensation directly related to your duties to Interlock Rochester, Inc.? If yes, please describe the benefit(s) and if an affiliated person is involved, the identity of the affiliated person and your relationship with that person.<br /> # Are you or any of your affiliated persons a party to or have an interest in any pending legal proceedings involving Interlock Rochester, Inc.? If yes, please describe the proceeding(s) and if an affiliated person is involved, the identity of the affiliated person and your relationship with that person.<br /> # Are you aware of any other events, transactions, arrangements or other situations that have occurred or may occur in the future that you believe should be examined by Interlock Rochester Inc.’s board or a duly constituted committee thereof in accordance with the terms and intent of Interlock Rochester Inc.’s conflict of interest policy? If yes, please describe the situation(s) and if an affiliated person is involved, the identity of the affiliated person and your relationship with that person.<br /> <br /> I HERBY CONFIRM that I have read and understand Interlock Rochester Inc.’s conflict of interest policy and that my responses to the above questions are complete and correct to the best of my information and belief. I agree that if I become aware of any information that might indicate that this disclosure is inaccurate or that I have not complied with this policy, I will notify the President immediately.<br /> ___________________________________ __________________<br /> <br /> Signature Date<br /> <br /> <br /> <br /> <br /> <br /> <br /> ==Interlock Rochester Gift Policy and Disclosure Form==<br /> As part of its conflict of interest policy, Interlock Rochester, Inc. requires that directors, officers and employees decline to accept certain gifts, consideration or remuneration from individuals or companies that seek to do business with Interlock Rochester, Inc. or are a competitor of it. This policy and disclosure form is intended to implement that prohibition on gifts.<br /> ===Section 1===<br /> “Responsible Person” is any person serving as an officer, employee or a member of the board of directors of Interlock Rochester, Inc.<br /> ===Section 2===<br /> “Family Member” is a spouse, domestic partner, parent, child or spouse of a child, or a brother, sister, or spouse of a brother or sister, of a Responsible Person.<br /> ===Section 3===<br /> “Contract or Transaction” is any agreement or relationship involving the sale or purchase of goods, services or rights of any kind, receipt of a loan or grant, or the establishment of any other pecuniary relationship. The making of a gift to Interlock Rochester, Inc. is not a “contract” or “transaction.”<br /> ===Section 4===<br /> Prohibited gifts, gratuities and entertainment. Except as approved by the Chairman of the Board or his designee or for gifts of a value less than $50 which could not be refused without discourtesy, no Responsible Person or Family Member shall accept gifts, entertainment or other favors from any person or entity which:<br /> # Does or seeks to do business with Interlock Rochester, Inc. or,<br /> # Does or seeks to compete with Interlock Rochester, Inc. or,<br /> # Has received, is receiving, or is seeking to receive a Contract or Transaction with Interlock Rochester, Inc.<br /> <br /> <br /> ===Gift Statement===<br /> I certify that I have read the above policy concerning gifts, and I agree that I will not accept gifts, entertainment or other favors from any individual or entity, which would be prohibited by the above policy. Following my initial statement, I agree to provide a signed statement at the end of each calendar year certifying that I have not received any such gifts, entertainment or other favors during the preceding year.<br /> _______________ ___________________<br /> Signature Date</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Amateur_radio 2010-12-21T15:55:34Z

<p>Fvox13: </p> <hr /> <div>== who we are ==<br /> Interlock has a number of licensed ham radio operators including:<br /> * [[User:Justbill | Bill]], KC2YPJ (General)<br /> * [[User:Ben_Woodruff | Ben]], N0BDW<br /> * [[User:Dhraakellian | Nick]], KC2YTG<br /> * [[User:IGadget | Rowan]], KC2KPI (General)<br /> * [[User:Fvox13 | Steve]], KC2YTC<br /> * [[User:Berticus | Brian]], KC2VVD<br /> * [[User:Butterb | John]], N2PMP (Extra)<br /> * [[User:alvarop | Alvaro]], KC2VVE<br /> * [[User:BinaryMan | Chris]], N2CDO<br /> * Tim, KB1POP (General)<br /> * Charlton (&quot;Vaughn&quot;), KC2ZLT<br /> <br /> == what we do ==<br /> We generally hang out on the Xerox repeater, KE2MK/R, as it is one of the few repeaters we are able to work on 2M/440 from rubber duck antennas on HTs from inside Interlock. We also occasionally use the Harris repeater.<br /> <br /> As of late the XARC repeater has been having some difficulties and so we are hanging out on MCARES/N2MPE (146.61) until the issues are resolved. Ben sent an email to some of the XARCers to see if there was anything we could do to help on 9/10/10.<br /> <br /> '''UPDATE''': 9/13/10 The issue with 145.29 has been resolved and I'm recommending that people switch back to it for their primary. The issue is that we had always used an RX PL tone which apparently got disabled. In order to get back on the air with Xerox you need to disable PL tones. There is still an issue with the volume on the TX of the repeater with XARC has been made aware of.<br /> <br /> '''UPDATE''': 2010-09-25 The volume issue on the 2-meter side appears to have been fixed. There is still no PL tone.<br /> <br /> === Xerox ARC Repeater ===<br /> * Output: 145.29 (you listen on this frequency)<br /> * Input: 144.69 (you transmit on this frequency) - negative offset<br /> * Output: 444.825<br /> * Input: 449.825 - positive offset<br /> * No PL tone required (RX PL 110.9 works to cut down intermod)<br /> * Echolink node #44856<br /> <br /> === Harris Repeater ===<br /> * Output: 444.400<br /> * Input: 449.400 - positive offset<br /> * TX PL 110.9<br /> <br /> === MCARES Repeater ===<br /> * Output: 146.610<br /> * Input: 146.010 (negative offset)<br /> * TX PL 110.9 (no RX PL)<br /> * No Echolink / IRLP but does have multiple receivers around Monroe County<br /> * Call sign is N2MPE, only IDs in morse. No roger beep. Control Op is Tony DiLettera from Radio Center.<br /> <br /> === Interlock Simplex ===<br /> * Frequency: 442.420 (no PL)<br /> * Note: this frequency is outside the normal step for 70cm, so you make have to do something funky to get your radio to tune it (like change your step for 70cm to 5Hz)<br /> * Ben will occasionally crossband repeat to/from one of the local repeaters (usually MCARES, see above) on this frequency so that those in the space can take advantage of the higher power transmitter. Please be careful to make sure this is not the case before attempting to use this as a simplex frequency.<br /> <br /> <br /> Xerox used to be Echolink enabled but is no longer. JD used to run Echolink on it over RF and may allow Interlock to run a similar setup, once we have an antenna. Information is flowing slowly on this though.<br /> <br /> None of our official unofficial repeaters support IRLP. Some of the other local repeaters do. If you are interested in IRLP, check out this site for a brief introduction on how to use it: http://k3bay.com/html/irlp.php<br /> <br /> == projects ==<br /> === antenna building ===<br /> We have ordered the parts needed to build [http://home.comcast.net/~buck0/ll_coolj.html 2-meter j-pole antennas]. We will be assembling them next Make Night, Thursday July 8th.<br /> Update: Antenna make night was a success. Thanks to all who attended. Please watch for similar events in the future!<br /> <br /> === [[roof antenna]] ===<br /> We have permission from Maguire to install an antenna on the roof as long as it is free-standing (ie, we don't bolt it to the roof). Also, the feed line can't whip in the wind or whack up against the building (so it needs to be secured somehow -- conduit?).<br /> <br /> === [[rochester repeater guide]] ===<br /> <br /> === [[general ham supplies]] ===<br /> Lets pass the hat around to purchase some supplies for use at the space. Powerpoles, cabling, adaptors, etc.</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Meetings 2010-12-07T18:24:32Z

<p>Fvox13: /* Agenda */</p> <hr /> <div>= Minutes =<br /> See [[MIBS_Simplified_Rules_of_Coordinated_Consensus_through_Chaos#The_Meeting_Agenda]] for agenda template<br /> <br /> == December 7, 2010 ==<br /> === Agenda ===<br /> <br /> # Approve draft minutes of the last meeting<br /> # Consent Agenda<br /> ## Fund matching for Ham SIG roof antenna project - $250<br /> # Officer Reports<br /> ## [[President]]<br /> ## [[Vice-President]]<br /> ## Treasurer <br /> ## Secretary<br /> # [[Member Reports]]<br /> # New Business<br /> # Adjournment<br /> <br /> === Minutes ===<br /> <br /> Attendance:<br /> <br /> ==== Initialization ====<br /> <br /> ==== Consent Agenda ====<br /> <br /> ==== Officer Reports ====<br /> <br /> # [[President]]<br /> # [[Vice-President]]<br /> # Treasurer <br /> # Secretary<br /> <br /> ==== Member Reports ====<br /> <br /> ==== New Business ====<br /> <br /> ==== Adjournment ====<br /> <br /> <br /> == November 2, 2010 ==<br /> === Agenda ===<br /> <br /> # Approve draft minutes of the last meeting<br /> # Consent Agenda<br /> ## Interlockroc.___ domain renewal: transfer all of the domains to their own GoDaddy account and update the contact information to use an email address that goes to the officer list. Renew interlocroc.org for 3 years. Renew interlockroc.net and interlockroc.com for 1 year.<br /> ## Soldering Equipment - Interlock part of purchase -- ~$125<br /> ### Purchase item #2 on [[Wishlist: Soldering]], -- already has 50% member pledges<br /> ### Purchase remaining items [[Wishlist: Soldering]] (items 1,3) when there is 50% member contributions.<br /> # Officer Reports<br /> ## [[President]]<br /> ## [[Vice-President]]<br /> ## Treasurer <br /> ## Secretary<br /> # [[Member Reports]]<br /> # New Business<br /> # Adjournment<br /> <br /> === Minutes ===<br /> <br /> Attendance:<br /> <br /> ==== Initialization ====<br /> <br /> ==== Consent Agenda ====<br /> <br /> ==== Officer Reports ====<br /> <br /> # [[President]]<br /> # [[Vice-President]]<br /> # Treasurer <br /> # Secretary<br /> <br /> ==== Member Reports ====<br /> <br /> ==== New Business ====<br /> <br /> ==== Adjournment ====<br /> <br /> == October 5, 2010 ==<br /> === Agenda ===<br /> <br /> # Approve draft minutes of the last meeting<br /> # Consent Agenda<br /> ## Spend $200 on promo drink tickets for the Rochester Security Summit after party, to be given out from the Interlock table situated in the summit's CTF room.<br /> ## Spend $150 to sponsor Barcamp Rochester. We will get our logo on their tshirt and website, as well as a table at the event where we can schmooze and sell shirts.<br /> ## Spend $150 to purchase the Harbor Freight tools listed here: [[Wishlist:_tools]]<br /> # Officer Reports<br /> ## [[President]]<br /> ## [[Vice-President]]<br /> ## Treasurer - We currently have maintained our membership level. We had a loss of one and a gain of one. We have enough funds to cover all three of consent agenda. <br /> ## Secretary - Treasurer had given my report.<br /> # [[Member Reports]]<br /> # Old Business<br /> ## Approve [[network acceptable use policy]] and its addition to the membership agreement.<br /> ## Approve mutual discounts with Coworking, and associated logistics.<br /> # New Business<br /> # Adjournment<br /> <br /> === Minutes ===<br /> <br /> Attendance: Drew, Nick, Brian, Joe, Ben, Carl, Mark, Bill, Jaimee, Wayne <br /> <br /> ==== Initialization ====<br /> <br /> 19:05<br /> <br /> ==== Consent Agenda ====<br /> <br /> # Approved<br /> # Approved<br /> # Moved to new business by Joe - After discussion it was Approved<br /> <br /> ==== Officer Reports ====<br /> <br /> # [[President]]<br /> # [[Vice-President]]<br /> # Treasurer - We currently have maintained our membership level. We had a loss of one and a gain of one. We have enough funds to cover all three of consent agenda. <br /> # Secretary - nothing to add.<br /> <br /> ==== Member Reports ====<br /> <br /> # Carl - Electronics class will begin soon. They will be 8:00 PM on Tuesdays and will run for at least 5 classes.<br /> # Drew - Posters for Barcamp will be put up and wanted to propagandize the Hungerford.<br /> # Mark &amp; Wayne - They have started a spotlight &quot;Batman&quot; project. May need some specialized lights. <br /> # Wayne - Working to put a showing of &quot;Get Lamp&quot; together.<br /> # Jaimee - Her show is Oct 07. 5-8 PM<br /> <br /> ==== Old Business ====<br /> <br /> # Approved<br /> # Approved<br /> <br /> ==== New Business ====<br /> <br /> # Consent Agenda 3 - Joe had a question regarding spending of money for money and future purchase of tools. Suggestions include cost matching. He will discuss outside of meeting and consent to purchase of current agenda list. <br /> <br /> ==== Adjournment ====<br /> <br /> 19:29<br /> <br /> == September 7, 2010 ==<br /> === Agenda ===<br /> # Approve draft minutes of the last meeting<br /> # Consent Agenda<br /> ## Approve [[network acceptable use policy]] and its addition to the membership agreement.<br /> ## Approve mutual discounts with Coworking.<br /> # Officer Reports<br /> ## [[President]]<br /> ## [[Vice-President]]<br /> ## Treasurer<br /> ## Secretary<br /> # [[Member Reports]]<br /> # New Business<br /> # Adjournment<br /> <br /> === Minutes ===<br /> Attendance: Carl, Ben, Nick, DeeJoe, Brian, Mark, Andrew, Chris, John<br /> <br /> ==== Initialization ====<br /> Meeting started at 8:15, and hour later than usual due to a scheduled class conflict.<br /> <br /> ==== Consent Agenda ====<br /> Network AUP and Coworking discounts are objected to by Deejoe and others. Moved to new business.<br /> <br /> ==== Officer Reports ====<br /> Officer reports are linked in the agenda above. No report from the Secretary or Treasurer.<br /> <br /> ==== Member Reports ====<br /> Ben gives a report on the new Asterisk box, and other networking developments.<br /> <br /> ==== New Business ====<br /> Network AUP is considered half-baked by most members in attendance. It is suggested that the language needs to be updated before it will be approved.<br /> <br /> Coworking discount numbers are generally acceptable, but the logistics of how to implement the discounts is not specified. That information will need to be specified before approval.<br /> <br /> ==== Adjournment ====<br /> Meeting adjourns at 8:30<br /> <br /> == August 3, 2010 ==<br /> === Agenda ===<br /> # Approve draft minutes of the last meeting<br /> # Consent Agenda<br /> ## Move Septembers meeting to 8:00 PM<br /> # Officer Reports<br /> ## [[President]]<br /> ## [[Vice-President]]<br /> ## Treasurer<br /> ## Secretary<br /> # [[Member Reports]] <br /> # Adjournment<br /> <br /> === Minutes ===<br /> Attendance: Bill, Wayne, Nick, Ben, Brian, Mark, Joe, and Carl<br /> <br /> ==== Initialization ====<br /> 19:10<br /> <br /> ==== Officer Reports ====<br /> President - See link above<br /> <br /> Vice President - See link above<br /> <br /> Treasurer - Members late with monies: 3, members 30+ days late: 3, members 60+ days late: 2. Reminders sent to all, door shutoff for 30+ and removed as member 60+. Please pay and email Treasurer if any issue. 11 members paid (10 regular and 1 student). <br /> <br /> Secretary - Proud Mary 19:11<br /> <br /> ==== Member Reports ====<br /> <br /> Carl - Informed group about the fairly busy Linux workshop this past weekend. Several helpers and people showed up to learn and install linux. Needed someone to make sure that Linux Workshop doors need to be open Aug 21st buy a member. JustBill volunteered. He is also thinking of setting up one of the Make Nights to do build your own NAS installs - more info to follow on mailing list. Carl has also volunteered to teach a basic electronics class after the upcoming Processing/Arduino class mentioned on the mailing list.<br /> <br /> Joe - LUGOR will be starting their meetings soon. See Joe for details.<br /> <br /> ==== Consent Agenda ====<br /> <br /> Due to upcoming Processing/Arduino class it was proposed to group to have Septembers Board meeting at 8:00 as to not interfere with the class. Nobody objected. Motion passed.<br /> <br /> ==== New Business ====<br /> <br /> Just a reminder that there is an upcoming 5 week class on Processing and Arduino. Many members have expressed interest and will be doing the class. More info [http://training.oreilly.com/arduino/] . See you there.<br /> <br /> ==== Adjournment ====<br /> <br /> 19:28<br /> <br /> == July 5, 2010 ==<br /> === Agenda ===<br /> # Approve draft minutes of the last meeting<br /> # Consent Agenda<br /> ## Renew our Meetup.com service at $72 for six more months<br /> ## Reimburse Beardicus for non-pre-ordered Interlock t-shirts (less than ten at the moment) and hold in &quot;inventory&quot; for future sale.<br /> # Officer Reports<br /> ## [[President]]<br /> ## [[Vice-President]]<br /> ## Treasurer<br /> ## Secretary<br /> # [[Member Reports]] <br /> # Adjournment<br /> <br /> === Minutes ===<br /> <br /> ==== Members Present ====<br /> Attendance: Carl, Mark, Ben, Brian, Wayne, Nick, Bill<br /> <br /> ==== Initialization ====<br /> 19:45<br /> <br /> ==== Officer Reports ====<br /> President - He made a summary of Interlock updates. We were at FOSSCON and held a table.<br /> <br /> Vice President - [[Vice-President#Officer_Report_7.2F6.2F2010| see report]]<br /> <br /> Treasurer - Multiple finances discussed. More detailed report to follow but it was about income, members, and total expenditures. <br /> <br /> Secretary - Hi My name is &quot;Just&quot;Bill and I'm the new secretary till next voting cycle. Please forgive me for any of my mistakes.<br /> <br /> ==== Member Reports ====<br /> <br /> Nick - Just wanted to announce that BinaryMan (Chris) received his HAM technical license.<br /> <br /> ==== Consent Agenda ====<br /> <br /> Moved to new business due to Treasurers report<br /> <br /> ==== New Business ====<br /> <br /> # Renew Meetup.com - Mark will float the cost and the Interlock will keep an open purchase order for reimbursement until fund get more soluble.<br /> # Reimbursement for T-Shirts. Same as #1 will keep open purchase order until funds are more available. Brian will fund until then.<br /> <br /> ==== Adjournment ====<br /> <br /> 20:06<br /> <br /> == June 1, 2010 ==<br /> === Agenda ===<br /> # Approve draft minutes of the last meeting<br /> # Officer Reports<br /> ## [[President]]<br /> ## [[Vice-President]]<br /> ## Treasurer<br /> # [[Member Reports]] <br /> # Adjournment<br /> <br /> === Minutes ===<br /> <br /> ==== Members Present ====<br /> Attendance: Carl, Nick, Mark, Brian, Steve, Bill, Ben, Wayne<br /> <br /> ==== Initialization ====<br /> President starts the meeting at 7:15. Minutes from last meeting are approved.<br /> <br /> ==== Officer Reports ====<br /> [[President]] gives his report (linked)<br /> [[Vice-President]] gives his report (linked)<br /> <br /> ==== Member Reports ====<br /> Steve gives a member report on an intranet portal he's developing for Interlock... wikis, blogs, files, events (and much much more!)<br /> <br /> ==== Adjournment ====<br /> Meeting adjourns at 7:30.<br /> <br /> === Addition ===<br /> Change in officers. Alan Dipert and Ashley McClelland have left the organzation. Brian Boucheron is the new president. We are still looking for a Secretary.<br /> <br /> == May 4, 2010 ==<br /> === Agenda ===<br /> # Approve draft minutes of the last meeting<br /> # The Consent Agenda<br /> ## Approve the [http://www.interlockroc.org/wiki/index.php?title=Bylaws&amp;oldid=1169 bylaws]<br /> # Officer Reports<br /> ## [[President]]<br /> ## [[Vice-President]]<br /> # [[Member Reports]] <br /> # [[Old Business]] <br /> # [[New Business]]<br /> # Adjournment<br /> <br /> === Minutes ===<br /> <br /> ==== Members Present ====<br /> Brian, Alan, Ashley, Mark, Alvaro, Carl, Ben, Steve, Nick, Rowan, Jim, Wayne<br /> <br /> ==== Initialization ====<br /> President starts the meeting at 7:08. Last meeting's draft minutes were approved.<br /> <br /> ==== Consent Agenda ====<br /> No objections.<br /> <br /> ==== Officer Reports ====<br /> [[President]] gives his report (linked)<br /> <br /> [[Vice-President]] gives his report (linked)<br /> <br /> The Treasurer gives her report. Membership is down 1 from last month, expenses are as per usual.<br /> <br /> ==== Member Reports ====<br /> Carl mentions the Linux workshops for the next two months (see the calendar)<br /> <br /> <br /> ==== Adjournment ====<br /> Meeting adjourns at 7:26.<br /> <br /> == April 20, 2010 (Special Meeting) ==<br /> === Agenda ===<br /> # The Consent Agenda<br /> ## Approve [[petty cash budget]] <br /> # [[Officer Reports]] <br /> ## [[President]]<br /> ## [[Vice-president]]<br /> ## [[Treasurer]]<br /> ## [[Secretary]]<br /> # [[Member Reports]] <br /> # [[Old Business]] <br /> # [[New Business]]<br /> # Adjournment<br /> <br /> === Minutes ===<br /> <br /> Members in attendance: Brian, Mark, Ashley, Alan, Joe, Jim, Rowan, Carl, <br /> <br /> President starts the meeting at 7:10<br /> <br /> ==== Consent Agenda ====<br /> Consent agenda passes without objection.<br /> <br /> ==== Adjournment ====<br /> Meeting is adjourned.<br /> <br /> == April 6, 2010 ==<br /> <br /> === Agenda ===<br /> <br /> # Draft minutes of the last meeting<br /> # The Consent Agenda<br /> ## Special meeting, April 20th to discuss improving [[Recruitment|recruitment]], modifying our [[Budget|budget]], improving our [[Finances|finances]].<br /> ## Approve [[Bylaws]]<br /> ## Approve [[Membership Agreement]]<br /> # [[Officer Reports]] <br /> ## [[President]]<br /> ## [[Vice-president]]<br /> ## [[Treasurer]]<br /> ### Approve [[Budget]]<br /> ## [[Secretary]]<br /> # [[Member Reports]] <br /> # [[Old Business]] <br /> # [[New Business]]<br /> ## [[Hospitality budget]]<br /> ## [[Cleaning supplies]]<br /> ## [[Hacker of The Month|Hacker of the Month]] Funds<br /> ## [[Inventory]]<br /> # Adjournment<br /> <br /> === Minutes ===<br /> Members Present: Brian, Mark, Steven, Carl, Ben, Nick, Alvaro, Rowan, Alan, Ashley, Tim<br /> <br /> The president begins the meeting at 7:08<br /> <br /> Minutes from the March 3 meeting are approved.<br /> <br /> ==== Consent Agenda ====<br /> Joe objects to passing the bylaws. Moved to new business.<br /> All other motions pass.<br /> <br /> ==== Officer Reports ====<br /> [[President]] gives his report (Linked)<br /> [[Vice-President]] gives his report (Linked)<br /> <br /> Treasurer gives her report on the state of our funds and membership. Budget can be viewed at the Google Docs site.<br /> <br /> Secretary has nothing to report<br /> <br /> ==== Member Reports ====<br /> Rowan reports on the IP web camera and LV jack boxes.<br /> <br /> Tim reports on networking. Network will be complete by 4/7/2010, minus boxes for jack.<br /> <br /> ==== Old Business ====<br /> NULL<br /> <br /> ==== New Business ====<br /> * Bylaws<br /> The issue stated is that the bylaws don't make it clear what the powers of the board of directors vs. the membership. Language is proposed to make this clearer.<br /> <br /> Rowan brings up a concern about term limits for board of directors and officers.<br /> <br /> Joe proposes that the board members be given some power for action between meetings.<br /> <br /> Bylaws are not passed and are deferred to the next regular meeting.<br /> <br /> * Hospitality budget is discussed, but not passed. Summary is that $20 would be budgeted each month for First Friday supplies and other essentials. Details will be provided at later meeting.<br /> <br /> ==== Adjournment ====<br /> Meeting is adjourned at 7:53<br /> <br /> == March 9, 2010 ==<br /> Lightning Talks:<br /> <br /> Signed Up: Alan(Machines that think), Alvaro(Orienteering, Remote Backup), Andrei(Contemporary Art), Ashley(Learning Programming), Beardicus(Wee Booklet), Ben(irssi+screen), Carl(Cat5, Soldering), Jason(Low Impact Local Network Recon), Justin(Go, XSS/XSRF Demo), Joe(Pymol Molecular Viewer), Mark(XSS/XSRF), Steve(Free Public Wifi), Remy(Open Video Chat Program team Intro)<br /> <br /> == March 2, 2010 ==<br /> <br /> Members Present: Brian, Mark, Ashley, Alan, Carl, Joe, Wayne, Nick, Ben, Steven<br /> <br /> The president begins the meeting at 7:11.<br /> <br /> === Consent Agenda ===<br /> <br /> NULL<br /> <br /> === Officer Reports ===<br /> <br /> (Reports were provided orally, with no hardcopy transcriptions)<br /> <br /> The President reports on the general status of the organization.<br /> <br /> The Vice President gives an update on the status of the networking project.<br /> <br /> The Secretary has nothing to report, and requests future officer reports be provided in writing for more comprehensive minutes.<br /> <br /> The Treasurer has nothing to report this month.<br /> <br /> === Member Reports ===<br /> <br /> Joe presents his knit n900 cozy and clues us in to virtualization plans for the space<br /> <br /> Steven nominates himself safety dictator, explains plans to abuse his power<br /> <br /> === Old Business ===<br /> <br /> NULL<br /> <br /> === New Business ===<br /> <br /> NULL<br /> <br /> === Adjournment ===<br /> <br /> TRUE<br /> <br /> == February 23, 2010 ==<br /> * Agenda<br /> ** Introductions<br /> ** Organization Updates<br /> ** Project Updates<br /> ** Open Announcements<br /> *** Lightning Talks<br /> <br /> == February 23, 2010 ==<br /> * Agenda<br /> ** Introductions<br /> ** Organization Updates<br /> *** Move in timeline<br /> *** MIBS reminder<br /> *** March 2nd first meeting<br /> ** Project Updates<br /> ** Open Announcements<br /> *** Lightning Talks<br /> <br /> == February 15, 2010 ==<br /> * Agenda<br /> ** Introductions<br /> ** 15 Min MIBS review/walkthrough<br /> ** Organization Updates<br /> ** Project Updates<br /> ** Open Announcements<br /> <br /> == February 9, 2010 ==<br /> * Agenda<br /> ** 15 Min MIBS review<br /> ** Introductions<br /> ** Last Week Meeting Review<br /> ** Organization Updates<br /> ** Project Updates<br /> ** Open Announcements<br /> <br /> == February 2, 2010 ==<br /> * Agenda<br /> ** Introductions<br /> ** Last Week Meeting Review<br /> ** Organization Updates<br /> *** Bank Account/Paypal<br /> *** Meeting Changes<br /> **** Consensus through Chaos <br /> **** Official Meetings monthly but weekly open nights<br /> **** Officer roles review<br /> **** Voting Scenarios<br /> ** Project Updates<br /> *** First Friday Organization<br /> *** Door Security System<br /> *** Other member projects<br /> ** Open Announcements<br /> <br /> == January 26, 2010 ==<br /> * Agenda<br /> ** Introductions<br /> ** Last Week Meeting Review<br /> ** Organization Updates<br /> *** Bank Account<br /> ** Project Updates<br /> *** Door/Security System<br /> ** Open Announcements<br /> * Minutes<br /> ** Bank account: in motion. Waiting on some paper work<br /> ** Door project: learning about the ibuttons<br /> ** Sneyha: outreach meeting. <br /> *** Need ideas for first friday<br /> *** planning on a green screen<br /> ** RemyD: Who else comes out for first friday?<br /> *** Sneyha: A ton of the people in the building<br /> ** Carmen: has a project related to inventoring computers<br /> ** Discussion about doing classes<br /> ** Alan: Haiti relief outreach<br /> ** Rowan: HAM radio group<br /> ** Alan: be kind on IRC<br /> ** RemyD: www.opensource.com - news portal for open source articles<br /> ** Sneha: wine tour<br /> ** RemyD: Stallman is coming to town on Feb 23<br /> ** Steve: Enable effing SSL on google apps!<br /> <br /> == January 19, 2010 ==<br /> * Agenda<br /> ** Introductions<br /> ** Last Week Meeting Review<br /> ** Organization Updates<br /> *** Changes to bylaws<br /> *** Changes to member agreement<br /> ** Project Updates<br /> ** Open Announcements<br /> * Minutes<br /> 1/19<br /> *introductions, alan, deejoe, carl, brian, steve, nick, josh, alex, ben, bill, ashley, mark, jon, chris, remy<br /> <br /> carl outreach summary:<br /> ** join first friday<br /> ** video commercial<br /> ** running robots<br /> ** barcamp in april<br /> ** lightning talks at barcamp<br /> ** fosscon - june - remyd is an organizer<br /> ** linux workshop outreach went well - 12 people came - next one in February<br /> ** maybe talk to Lugor about doing hands on workshop after a lugor discussion<br /> ** writing workshop to teach anyone how to write<br /> ** ashley: keep writing focused<br /> * lightning talks again<br /> *alan: want to also give back to the community like linux workshop<br /> * alan:bylaws and membership agreement<br /> *alan, ashley, mark, brian and others met to go over bylaws and mission statement<br /> * changes are on the wiki<br /> *ashley: maybe do a mock mibs walkthrough<br /> *alan: share the google doc to everyone<br /> * alan got the EIN<br /> * thursday mark, brian, ashley, alan, will be going to the bank<br /> *question: josh: how open are finances<br /> *answer: everyone: as open as you want to be. meetings will have <br /> *ben: if anyone has suggestions for the space design, make them known now<br /> *steve: internet connection<br /> ** the acct rep received fax<br /> ** she's going to let us know install date<br /> *alan: programming for beginners class<br /> ** work with python group in Rochester<br /> *brian: beginning electronics<br /> ** make magazine has beginner electronics book<br /> ** good for doing a class or group<br /> * dude: we can get cheap stuff from radio shack and the internet has parts<br /> *joe: bulk silly putty reminder<br /> *steve: bulk coffee/tea maker<br /> *chris: organizational membership to amazon<br /> ** you can pull out technical books<br /> ** view them online but access to TONS of books<br /> ** not sure on the costs<br /> *Brian: Pledgie<br /> ** people can join and pledge their amount<br /> ** when it gets the amount it does whatever they've been planning (silly putty)<br /> ** another space used it successfully<br /> <br /> == January 12, 2010 ==<br /> * Attended: Carl, Avezou, Mora, Steve, Brian, Chris, Rowan, Andre, Sneha, Remy, Shawn, Carmen, Josh, Gina, Jimmy, Christina, Alvaro, Rachel, Brian, Ashlee, Ben, Mark, Ryan, Justin, Nick, Alan, Alex<br /> * Agenda<br /> ** Introductions<br /> ** Last Week Meeting Review<br /> ** Organization Updates<br /> ** Voting:<br /> *** IRC<br /> ** Project Updates<br /> ** Open Announcements<br /> ** EVENT: [http://www.meetup.com/Rochester-Hackerspace/calendar/12121705/ Lightning Talks]<br /> <br /> == January 5, 2010 ==<br /> * Attended: Ryan, Dawn, Carl, Steve, Josh, Alvaro, Alan, Bryan, Joe, Andrei, John, Ashley, Justin, Rowan<br /> * Agenda<br /> ** Introductions<br /> ** Updates<br /> *** Recap of SCORE meeting (Alan)<br /> ** Anything else?<br /> * Discussed<br /> ** SCORE<br /> *** With lawyer, 501(3)c process 6mo - year, $1000 - $1500<br /> *** Importance of mission statement<br /> ** Separation of concerns: member agreement vs. bylaws<br /> *** agreement is for limiting liability and other bare minimums<br /> *** bylaws part culture, part rules<br /> *** bylaws are really only about starting and stopping processes<br /> *** we need a solid mission statement to define ourselves and guide decisions/priorities<br /> ** Outreach, community service, donation possibilities<br /> *** &quot;Linux Q &amp; A&quot; days<br /> <br /> == December 22, 2009 ==<br /> * Agenda<br /> ** NONE: relaxing discussion<br /> <br /> == December 15, 2009 ==<br /> <br /> * Attended: Brian, Jim, Nick, Avezou, Carl, Sneha, Steve, Ben, Ashley, Carmen, Joe, Bryan, Paul, Tim, Alvaro, JP, Joshua,<br /> * Agenda<br /> ** Introductions<br /> ** Updates/Announcements<br /> ** ISP Options: Steve S.<br /> ** Intro to Wordpress (brief): Ben W.<br /> ** Projects<br /> ** Discuss next weeks Lightning Talks<br /> ** Holiday events, potlucks, parties, hoedowns?<br /> ** Best time to meet in the future<br /> * Discussed:<br /> ** Introductions, met a few new prospects<br /> ** Ben's Wordpress intro presentation<br /> ** Discussion of our use of Wordpress and how we want to handle posting<br /> ** Steve's ISP presentation<br /> ** Wooby talks lightning, and projects<br /> ** Deejoe gives a passionate lightning talk about plastic bag storage<br /> <br /> == December 8, 2009 ==<br /> * Attended: Mark, Brian, Steve, Dan, Andrei, Joe, Carl, Carmen, Sneha, Matt, Ben, Bryan, Josh [...]<br /> * Agenda:<br /> **7: Introductions and updates, go over [http://wiki.interlockroc.org/index.php?title=MIBS_Simplified_Rules_of_Coordinated_Consensus_through_Chaos MIBS meeting rules]<br /> **7:30: Hackerspace Presentation: Mark<br /> **8: Move to new space<br /> * Discussed:<br /> ** Introductions<br /> ** Officers announced. Mostly people on the lease or incorporation paperwork.<br /> ** Mark presented a bit on MIBS rules<br /> ** [http://docs.google.com/present/view?id=dnbv9rr_42ft4q8vff Hackerspace presentation]<br /> ** Sneha discusses public outreach activities<br /> * Caravan to the temp space for discussion and beverages<br /> <br /> == December 1, 2009 ==<br /> * Attended: Carl, Ben, Jimmi, Kristina, Steve, Ashley, Andrei, <br /> * Discussed: <br /> ** Bylaws went over a lot of the details. <br /> ** Bylaws: Decided to have an official meeting once a month unless otherwise requested <br /> ** Discussed dues<br /> ** updated everyone on lease signing status<br /> ** Ashley updated us on documents for incorporation<br /> ** Voted on whether or not to get the temp space or skip it and wait for the real space. Agreed to get the temp<br /> ** Introduced new members discussed goals of the organization<br /> * Action Items:<br /> ** Directors: Sign lease and setup temp space<br /> <br /> == November 23, 2009 ==<br /> <br /> * Attended<br /> ** Mark, Brian, Ashley, Alan, Sneha, Carmen, Carl, Bryan, Ben, Jeremy, Rich<br /> * Video: [http://www.ustream.tv/recorded/2628387 Part 1]<br /> * Discussed<br /> ** Basement space at 1115 Main Street<br /> *** $390 + electricity<br /> *** Ready by February<br /> ** Temporary space available immediately<br /> *** $280 + electricity<br /> ** Network connectivity options<br /> *** Business class roadrunner $79 a month<br /> *** Netsville<br /> ** Dues<br /> *** Start payment 1st of December<br /> *** Application form<br /> ** Business checking accounts and accounting<br /> ** First Month's rent<br /> ** Logos<br /> ** Wiki/Website stuff<br /> *** maybe looking for a wiki with better ACLs<br /> *** decision to departmentalize functions - wiki, website, blog, etc<br /> ** Dues through paypal for first month<br /> ** Bryan shows his illuminated bidness card<br /> ** Discussion about who will be the incorporators<br /> ** Presentation ideas for future meetings<br /> ***Python intro class<br /> ***Wordpress tutorial<br /> ***Software Defined Radio<br /> **Ham radio discussion<br /> ** Future meetings may have first 1/2 hour as business-related matters, come afterwards if you're not interested in the nitty gritty of forming the space<br /> * Actions<br /> ** Mark: Setup paypal account and email address<br /> ** Mark: Put together a membership package<br /> ** Alan: Put membership form online<br /> ** Goal: Have membership dues on December 1st<br /> ** Goal: Sign lease on Monday November 30th<br /> <br /> == November 17, 2009 ==<br /> * Attended: Mark, Sneha, Carmen, Ashley, Alan, Jimmi, Krystina, James, Justin, Robert, Joe, Ben, JP, Brian, (David)<br /> * Recordings - [http://www.ustream.tv/recorded/2580888 Part 1]- [http://www.ustream.tv/recorded/2581335 Part 2]<br /> * 1st meeting streamed online (ustream)<br /> * Decided on Interlock as a group name.<br /> ** interlocroc.net, .com and .org domains have been acquired<br /> * Discussion about three potential locations<br /> ** Griffith Ave<br /> *** 3000/$1500 a month<br /> *** No security deposit<br /> *** Utilities = $200 a month<br /> *** A bit too pricey<br /> ** E Main St<br /> *** 1000/$450<br /> *** 2000/$725<br /> *** Utilities = $150 a month<br /> ** Village Gate<br /> *** 500/$325<br /> *** Utilities = $60 a month<br /> * Talking about the budget<br /> ** Would prefer it to be about $35, but it will probably be higher at first until we get more members<br /> ** Looking at 501.c3<br /> ** Contacts in Buffalo chapter could be useful with this business setup<br /> ** Dues<br /> *** $50 - Normal<br /> *** $35 - Student<br /> * Trip to Buffalo Chapter<br /> ** Visit to see what they have there<br /> ** After thanksgiving, on the weekend<br /> *** Important for sponsorships<br /> <br /> Action Items For Next week:<br /> * Form a holding company (LLC, S-Corp) to get a bank account<br /> * Focus on making the Main St. building work (talk to Felix, discuss details, find temp location)<br /> * Plan for best way to form an NFP<br /> * Create a focus group for developing a website<br /> <br /> ==November 11, 2009==<br /> *Location: Spot Coffee<br /> *Attended:<br /> **Mark, Brian B., PT, Sneha, Dan, Carl, Andrei, Bryan, Josh, Ashley, Alan, Carmen<br /> *Discussed:<br /> **Summary of goals thus far, for new attendees.<br /> **Updates from members about spaces scouted, etc. <br /> ***Sneha: 1000 square feet, 600 a month, Portland Ave., with storefront<br /> ***Look into spaces near the Public Market? High rent for RR55 ($900)<br /> ****Other spaces besides the refurbed railroad area? Space above cheese shop area?<br /> **Introductions<br /> **Show and Tell<br /> ***Bryan<br /> ****guitar hacks<br /> *****tuning geegaws<br /> *****patents<br /> ***Andrei<br /> ****[http://www.makershed.com/ProductDetails.asp?ProductCode=MSBM brain machine kit]<br /> ****circuit bent toy horn<br /> ***Mark<br /> ****lockpicking sets<br /> ****garmin gps units, wardriving discussion<br /> *****obligatory [http://www.imdb.com/title/tt0086567/ Wargames] shoutout<br /> ****defcon badges<br /> ****bump key discussion<br /> ***Brian B.<br /> ****bookbinding<br /> ****sketchbooks<br /> ****[http://www.ponoko.com/ Ponoko] business cards<br /> ****[http://www.ponoko.com/ Makerbot] contact: sample print will be mailed out this weekend, hackerspace discount is available<br /> ****laser cutting, found [http://www.classact.net/ Class Act Engraving] in Akron, NY. Epilog laser reseller<br /> ***Carmen<br /> ****suitcase computer<br /> **Random discussion<br /> ***Kegerator w/ Nagios monitoring<br /> <br /> *Actions<br /> **None specified<br /> <br /> == November 6, 2009 ==<br /> * Location: Spot Coffee<br /> * Attended:<br /> ** Mark, Carmen, Sneha, Ben, Brian B, Stephen, Bryan S, Andrei, Tom, Josh, David, Karl<br /> * Discussed:<br /> ** announcements from last week - flyers, wiki<br /> ** attendees' backgrounds and vision for the space<br /> ** rough plan of action re: naming, incorporation, non-profit filing<br /> ** future meeting ideas, including demos and presentations<br /> ** (EDIT)<br /> * Actions:<br /> ** contribute to the wiki<br /> ** think of names<br /> ** (EDIT)<br /> <br /> == October 28, 2009 ==<br /> * Location: Spot Coffee<br /> * Attended: Mark, Jeff, Carmen, Brian, Alan, Eric, Joe, Andrei, Bryan, Greg, <br /> * Discussed:<br /> ** ideas<br /> ** made flyers<br /> ** other spaces<br /> ** meet and greet<br /> * Actions:<br /> ** Mark: setup a wiki<br /> ** Mark: print out flyers<br /> <br /> == October 21, 2009 ==<br /> * Location: Spot Coffee<br /> * Attended:<br /> ** Jerel, Matt, Mark, Jeff, Greg, Jimmi, Krystina<br /> * Discussed:<br /> ** meet and greet<br /> ** buffalo hackerspace<br /> * Actions:</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Network_acceptable_use_policy 2010-11-20T18:19:17Z

<p>Fvox13: /* Web Access Policy */ Re-adding cp clause. This is fairly standard to include, and unless you do, people will do it...</p> <hr /> <div>=Network Acceptable Use Policy=<br /> <br /> == Definitions ==<br /> <br /> (This is a draft and has not been approved by legal council)<br /> <br /> * Production Network: Official Interlock approved and managed services. <br /> * Project Network: Interlock member network services managed by individuals<br /> * Guest Network: Interlock managed guest access for visitors and friends of Interlock. <br /> * Warzone: Information security sandbox zone that may have malicious services.<br /> <br /> == Preamble ==<br /> The rules that comprise this Code of Conduct apply to all areas of computer use at Interlock Rochester, including all computers, storage devices, networks, and network devices owned or managed by Interlock Rochester, including any for which Interlock Rochester contracts with a third party. The [[network infrastructure group]] is responsible for publishing, and in concert with members of the Interlock Rochester community, enforcing this Code.<br /> <br /> A variety of computer resources are currently available at Interlock Rochester, from local area networks that provide access to PC, Mac, and *nix based software, to wide area networks such as the Internet. All users are required to follow this Code of Conduct when using these resources.<br /> <br /> Any information stored on Interlock Rochester computers, or with third party providers under contract by the group, may be stored digitally in multiple live and backup sources and, aside from the usual difficulties of guaranteeing confidentiality, is always subject to &quot;discovery&quot; by means of subpoena. Although the group may seek appropriate legal counsel, users should assume that the group will cooperate with outside agencies investigating violations of local, state, or federal law, including but not limited to copyright infringement, child pornography, or other illegal content.<br /> <br /> Violation of the Code can lead to:<br /> * Suspension of membership privileges<br /> * Criminal Prosecution<br /> <br /> ==Rules of Conduct==<br /> ===All Networks===<br /> * You may not give out your password.<br /> * You may not let another person use your account.<br /> * You may not copy, retain, or distribute copyrighted or proprietary material without written consent of the copyright holder.<br /> * Individuals who store sensitive or confidential information on their computers are accountable for that information and must make sure the appropriate security (encryption, etc.) is in place.<br /> * Interlock Rochester reserves the right to remove any technical resource (computers, software, network devices, etc.) that it deems a risk to security, network, or over consumption of resources.<br /> * Interlock Rochester takes no responsibility for damage caused to personally owned equipment.<br /> * You may not possess or attempt to possess another user's password<br /> * You may not use false or misleading identification to gain access to any computing resource.<br /> * You may not use any computing resource that you are not authorized to use.<br /> * You may not use an account for any purpose other than that for which you are authorized.<br /> * You may not change, copy, delete, read or otherwise access files or software without permission of the owner (in the case of user files) or system administrator (in the case of system specific files).<br /> * You may not attempt to prevent others from accessing any computing resource.<br /> * You may not attempt to bypass accounting or security mechanisms, or attempt to circumvent protection schemes or uncover security loopholes. If you find a security loophole, you are required to report it to the network infrastructure group immediately.<br /> * You may not use any Interlock Rochester computing resource, including the network itself, to attack, disable, or gain unauthorized access to any other computing resource either on or off the Interlock Rochester network.<br /> * All personally owned equipment connected to the Interlock Rochester network is the responsibility of the owner of that equipment. We strongly encourage you to run effective and currently updated anti-virus software package and have all operating system patches installed.<br /> * You may not attempt to compromise the privacy of others. This includes, but is not limited to, the installation of traffic sniffers, key loggers, etc. or any other hardware or software designed to capture information which you are not authorized to have without the consent of the network infrastructure group.<br /> <br /> === Production and Project Network ===<br /> * You may only access this network if your are a member in good standing in the organization or have permission from the Network Infrastructure Group or Interlock as a whole<br /> <br /> === Guest Network ===<br /> * Members can offer access to the guest network to any visitors, guests, or friends of Interlock or the organization.<br /> <br /> === Warzone Network ===<br /> * See the Warzone Acceptable Use Policy<br /> <br /> ==Web Access Policy==<br /> The Production and Project networks shall have internet access. Regardless of network, the following rules apply:<br /> * Use of the Internet for any unlawful purpose is prohibited. This includes, but is not limited to:<br /> ** posting, storing, transmitting or disseminating information, data or material which is libelous, obscene, unlawful, threatening or defamatory, or which infringes the intellectual property rights of any person or entity, or which in any way constitutes or encourages conduct that would constitute a criminal offense, or otherwise violate any local, state, federal, or non-U.S. law, order, or regulation;<br /> ** initiate, perpetuate, or in any way participate in any pyramid or other illegal scheme;<br /> ** participate in the collection of e-mail addresses, screen names, or other identifiers of others (without their prior consent);<br /> ** transmission of child pornography<br /> <br /> ==Data Retention Policy==<br /> Interlock Rochester does not intentionally maintain any meaningful records about network users or computers and their associated network traffic unless compelled to do so by a legal order. Any data that is collected for network diagnostic or educational purposes is destroyed as soon as the diagnostic or educational session is complete. The only semi-permanent records we may opt to maintain are:<br /> * DHCP records (stored for the duration of the DHCP lease)<br /> ** This includes a correlation between a MAC address and IP address<br /> * Captive Portal Registration<br /> ** These records may include a correlation between a user account and an associated MAC address<br /> * Door access logs<br /> ** Correlation between a user account and when they unlocked the door to locations managed by Interlock. <br /> <br /> * Records containing member contact information and emergency contact information may be stored electronically and made available to other members of Interlock Rochester.<br /> * Information about current membership status may be made available to 3rd parties in the form of a true / false response when queried by a unique identifier.<br /> <br /> Traffic sniffing and logging is allowed on the &quot;warzone&quot; network, however Interlock Rochester itself makes no attempt to maintain these records.<br /> <br /> <br /> <br /> We reserve the right to collect and analyze traffic on Interlock Rochester networks for the purpose of diagnosing and troubleshooting network and bandwidth issues.<br /> <br /> <br /> [[category:policies]]</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Group_Orders 2010-11-20T18:18:09Z

<p>Fvox13: </p> <hr /> <div>=Adafruit=<br /> <br /> The group can get up to 40% off items at adafruit.com (usually about 10% though). Orders should be over $250 (after discount).<br /> <br /> {|<br /> | Name || Item Description &amp; ID || List Price<br /> |-<br /> | Blah || Blah || $11.11<br /> |}<br /> Total(not including discount): $11.11<br /> <br /> =[http://wouxun.us/ Wouxun]=<br /> {|<br /> | Name || Item Description &amp; ID || List Price<br /> |-<br /> | [[User:BinaryMan|BinaryMan]] || Ben's KG-UVD1P || $90<br /> |-<br /> | [[User:BinaryMan|BinaryMan]] || 1700mah Battery || $24<br /> |-<br /> | [[User:BinaryMan|BinaryMan]] || 12v Car Charger || $10<br /> |-<br /> | [[User:BinaryMan|BinaryMan]] || SMA - SO239 Adapter || $5<br /> |-<br /> | [[user:Berticus|Beardicus]] || KG-UV2D (2M/440)|| $107<br /> |-<br /> | [[user:Berticus|Beardicus]] || 1700mah Battery || $24<br /> |-<br /> | [[user:Berticus|Beardicus]] || Dual Slot Charger || $24<br /> |-<br /> | [[user:Berticus|Beardicus]] || SMA - SO239 Adapter || $5<br /> |-<br /> | [[user:Dhraakellian|Nick]] || 1700mAh Battery || $24<br /> |-<br /> | [[user:Dhraakellian|Nick]] || Dual Slot Charger || $24<br /> |-<br /> | [[user:Dhraakellian|Nick]] || 12v Car Charger || $10<br /> |-<br /> | [[user:Dhraakellian|Nick]] || Speaker Mic || $14<br /> |-<br /> | [[user:Dhraakellian|Nick]] || SMA - SO239 Adapter || $5<br /> |-<br /> | [[user:Ben Woodruff|Ben]] || 1700mAh Battery || $24<br /> |-<br /> | [[user:Ben Woodruff|Ben]] || KG-UV2D (2M/440) ** || $107<br /> |-<br /> | [[user:jkl|jkluebs]] || SMA - SO239 Adapter|| $5<br /> |-<br /> | [[user:jkl|jkluebs]] || SMA - SO239 Adapter|| $5<br /> |-<br /> | ''Total'' || || $378<br /> |}<br /> <br /> <br /> {|<br /> | Name || $$<br /> |-<br /> | [[User:BinaryMan|BinaryMan]] || $129<br /> |-<br /> | [[user:Berticus|Beardicus]] || $160<br /> |-<br /> | [[user:Dhraakellian|Nick]] || $77<br /> |-<br /> | [[user:Ben Woodruff|Ben]] || $133 *<br /> |-<br /> | ''Total'' || $497<br /> |}<br /> <br /> Shipping: $22 ($5.50 ea)</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Get_there_(guest) 2010-11-15T17:14:50Z

<p>Fvox13: </p> <hr /> <div>Welcome potential guests of Interlock! You are likely viewing this page because you are interested in attending one of our meetings or events. If you are already a member and have keys, see [[Get there | this page]].<br /> <br /> [[image:100_1340.jpg|thumb|right|E Main / N Goodman]]<br /> Our street address is 1115 East Main Street, Suite 42, Rochester, NY 14609. If you have a GPS this will likely get you into the parking lot.<br /> If you don't have a GPS, the easiest way to get to the building is via I-490. Take 490 in the appropriate direction to exit 17 for Goodman Street. Head north on South Goodman, which will (technically) turn into Circle St. Turn right onto East Main St and head east. You can enter the Hungerford parking lot (free parking) by taking a right at the first traffic light for North Goodman (it is the only thing on North Goodman that is south of East Main St).<br /> <br /> You could also take I-490 to the Inner Loop, and get off at Main Street. Turn away from downtown (East), and proceed down Main Street over the railroad tracks. Interlock will be on your right, Immediately after you cross the bridge.<br /> <br /> Interlock is located behind door #1 which is at the north east corner of the complex.<br /> [picture]<br /> <br /> Once inside door #1 head down the stairs to the basement.<br /> [picture]<br /> <br /> You will come to a second door that you will pass through.<br /> [picture]<br /> <br /> Go to the end of the hall and make a right.<br /> [picture]<br /> <br /> [[image:4524536749_40c20d00de_m.jpg|thumb|right|Our front doors]]<br /> We are on your right.<br /> <br /> If the door is closed, please knock. Any questions or concerns please call (585) 210-8HAX (+15852108425) and leave a message. One of our members will return your call as soon as possible.</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Community_Outreach 2010-11-10T19:11:42Z

<p>Fvox13: </p> <hr /> <div>=Interlock Rochester Community Outreach=<br /> <br /> A strong Community Outreach Program could be what sets InterlockRoc apart from other hackerspaces. Here is an idea in development. <br /> <br /> =Minutes=<br /> [[Outreach Meeting Minutes 1/18/10]]<br /> <br /> =Ideas=<br /> ==Young Technologist Mentoring Program==<br /> <br /> ===Concept===<br /> <br /> InterlockRoc members can volunteer to become mentors for students in high school around the Rochester region. Each mentor would guide a group of students to complete a project of their choosing. It would be left up to the mentor to choose how he/she wants to guide the students, what project/s he wants to do, and what the goals for the summer are. At the end of the summer all groups will come together to present their work. <br /> <br /> ===Logistics===<br /> <br /> Interlock will provide application forms to various high schools. They will distribute these applications to students who are interested in various fields of technology. The form could ask for a brief essay asking each student to describe their interests and types of projects that they would like to do over the summer. Based on their responses we would pair them with Interlock mentors. The forms could also provide a list of mentors to the students so that the students can go on our website to see what kind of stuff each mentor does. They can list their top three choices for mentors. <br /> <br /> ==Interlock YouTube Channel==<br /> *everything* should be recorded, as far as lighting talks, etc<br /> Also, members should record tutorials, etc, and upload under Interlock account.<br /> <br /> <br /> ==Jailbreaking a phone class==<br /> This is legal now, but it is still edgy. We'd have a class to show folks how to Jailbreak the iPhone, and root android phones, and such. Media would want to cover it because it is interesting news on the edge.<br /> <br /> <br /> <br /> ==Computer Repair==<br /> <br /> Credit to Ashley for this idea, I'm just writing it up. --[[User:Ben Woodruff|-- BW]] 13:54, 6 December 2009 (UTC)<br /> <br /> ===Concept===<br /> <br /> We could have a day / week where we offer to (attempt to) fix computers on a donation basis.<br /> <br /> ===Logistics===<br /> <br /> People from the Rochester community could bring their computers to us (or designated drop off locations), sign a release of liability, and we would take them back to the space and try to fix them.<br /> We would want to connect these computers to the internet in order to install updates, etc on them, but would not want to connect them to the production network.<br /> Limited to 1 computer per household. We don't want someone to bring in their truckload of broken computers and expect for us to fix them all.<br /> It should be made clear upfront that we are doing this on a volunteer donation basis and that it may take up to a week to get your computer back. There may also be some things we just can't/won't fix.<br /> <br /> ===Cost===<br /> <br /> Our costs will include: power, bandwidth (although this is not a direct cost), and any parts required for repair. If any parts were required we would have to pass that cost on to the customer.<br /> <br /> ==Linux Workshop==<br /> ===Concept===<br /> <br /> Currently I host a Linux for newbies group for the Rochester Computer Society. I would like to change this into a Linux workshop meeting. Instead of yet another monthly presentation meeting it would be a time when anyone with problems or questions can get help. It can be part of or held in conjunction with the above idea.<br /> <br /> ===Logistics===<br /> <br /> Once a month (or more if it becomes popular) we have an expert or two or more available at our space and invite anyone to bring in their questions or problems. They should bring in the computer they need help with. We would have them sign a waiver saying we will do our best but there are no guarantees and we can't be held liable. The waiver would also say that they have good backups or risk losing data. I envision it being more training than simply doing work for people. Explain what we are doing and show the customer how to diagnose problems, search the net for solutions, download software and install patches. I always try to empower the computer owner rather than make them dependent on me to fix every little thing. It cuts down on the emergency phone calls for help.<br /> <br /> I originally envisioned doing it for just Linux systems and using the Lugor Installfests as a model. But thinking about it more there is no reason to limit it to Linux. We have experts in all the OSes and a lot of us have been doing tech support for family and friends for anything computer or technology related. And of course fixing any computer problem pretty much follows the XKCD flowchart.<br /> <br /> If we wanted to combine this with the idea of doing computer repair that would make sense since most people can't determine on their own whether a problem is hardware of software. However, fixing hardware is trickier as it would require having spare parts on hand and/or ordering parts and waiting for delivery. Any replacement parts we supply whether recycled or newly purchased would require us to provide some guarantee that it works. What the guarantee is would have to be made very clear to the customer before providing the part. I am open to doing hardware repairs but we have to carefully plan out what we are going to offer and how we will deliver it.<br /> <br /> We can publicize the service via the computer user groups, schools, libraries, Sound Bytes and Computer Link Magazine. We can ask for donations but the main advantage to us is getting our name out there and build good will.<br /> <br /> ===Costs===<br /> <br /> Power and bandwidth are the only material costs. The biggest cost is, as usual, our time. I am willing to be the primary &quot;host&quot; of such a service but it would be useful to have a few more &quot;experts&quot; available. No one would have to be there every month or even for the whole time we are &quot;open for customers&quot;.<br /> <br /> --[[User:Cws|Cws]] 18:21, 18 December 2009 (UTC)</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Roof_antenna 2010-11-08T22:33:35Z

<p>Fvox13: </p> <hr /> <div>We would like to install a 2M/400 antenna (and possibly others) on the roof of the Hungerford building, where Interlock is in the basement. We have the go-ahead from the building owners. We are in desperate need of contributions in order to make this project possible! If we are going to do it, we want to do it right. Ideally we will use LMR400 feed-line and build a free-standing tower that is capable of hosting multiple antennas for future expansion<br /> <br /> <br /> == Bill of Materials ==<br /> * 2m/70cm J-Pole (donated by Alvaro)<br /> * 200ft LMR-400-DB $192.00 (we're not burying it, but DB is waterproof, and given our aggressive freeze-thaw cycles, a must)<br /> * 3 pcs EZ-400-UM Connectors $45 (need 3 in case we screw up the crimping? They're $15 apiece; it'd be a shame to not use one of them though...)<br /> <br /> == Things to figure out ==<br /> * What do we use for a tower?<br /> * What do we use to attach the cable to the building? Industrial velcro?<br /> * Would schedule 40 be a good choice for constructing the tower itself?<br /> * Do we need to put a strobe on top? Even if we don't have to, should we?<br /> <br /> <br /> == Finances ==<br /> * Ben / Bill have each pledged $50<br /> * Steve has pledged $75<br /> * Beardy: $50<br /> * Nick: $25<br /> <br /> Total: $250 of estimated $300<br /> <br /> Will Interlock match our contributions, even partially?<br /> <br /> WePay link: [https://www.wepay.com/public/view/35059]<br /> <br /> K2FX's preferred vendor: [http://www.rfparts.com/]<br /> <br /> == Construction ==<br /> * Based on a site survey by Rowan &amp; Steve, we need approximately 160-170 feet of cable. We're going to buy 200 feet to be safe.<br /> * We are planning on mounting the antenna on a pole that would extend approximately 20-30 feet above the highest point of the roof. This is the stair tower where the north-facing elements of the Nextel cell tower are attached. We would be on the opposite side of these antennae.<br /> * The pole would be attached in such a way that &lt;del&gt;one person&lt;/del&gt; two people could tip it over for servicing<br /> * Paul K2FX has agreed to come over and terminate our connectors with his special $400 tool. We just need to give him a call when we're ready.</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Resources_we_have_/_donations 2010-11-03T00:28:35Z

<p>Fvox13: /* Tools */</p> <hr /> <div>== What You Have Donated ==<br /> (Please only things that are worth more than approximately $20 or could be used for a project)<br /> * Table (painted)<br /> * Table<br /> * HP Older printer<br /> * Small component chest<br /> * 24&quot; x 36&quot; Whiteboard<br /> <br /> Steve:<br /> * Cisco Wireless AP<br /> <br /> Mark:<br /> * 4 x Linksys Routers<br /> * Various hacker books<br /> * 10 tables from RIT<br /> <br /> Bryan:<br /> * Two leather [http://leather-chairs.officechairs.com/Black-Leather-Guest-Chair-with-Mahogany-Finish-CH00213.aspx guest chairs]<br /> <br /> Ben:<br /> * Cisco PIX<br /> * 24 port switch<br /> * 5-7 computers<br /> * 4-5 CRT monitors<br /> * HP All-in-one Printer<br /> * Scanner<br /> * AirPort Express<br /> * Bag of cables<br /> * 5-port switches (handful)<br /> * 5-port hub<br /> <br /> Carl:<br /> * 3 bins of cables<br /> * Microwave<br /> * bulletin board<br /> * UNIX license plate<br /> <br /> Charles:<br /> * Cisco 2950 switch --[[User:Cprofitt|Cprofitt]] 03:33, 25 January 2010 (UTC)<br /> <br /> Rowan:<br /> * Kitchen Shelving<br /> <br /> Just Bill:<br /> * Symantec box re-purposed into an ESXi 3.5<br /> * Cheap $25 projector<br /> * Hacked working Xbox<br /> <br /> [[User:BinaryMan|Chris]]:<br /> * 5-speed drill press<br /> * Bench grinder<br /> * Cisco 2520 router<br /> * Xbox 360<br /> * Yellow vacuum cleaner<br /> * Brother HL-1440 B/W printer<br /> <br /> == What You Have at Home ==<br /> <br /> === IT Equipment ===<br /> * old Cisco gigantic switch<br /> * quad core sun box<br /> * 2 GHz workstation w/ 2 GB of RAM. need to add in a drive, probably a 100 or 80 GB for now. [[User:Cmd3187|Cmd3187]] 16:01, 8 December 2009 (UTC)<br /> * 950 MHz Thinkpad with broken screen. 40GB drive I think. Could be used for the auth system, since we could just mount it to the door or something. [[User:Cmd3187|Cmd3187]] 16:01, 8 December 2009 (UTC)<br /> * Big Enterasys network switch with all kinds of crazy fiber and copper connections in different, removable blades (--[[User:Fvox13|Fvox13]] 06:01, 2 December 2009 (UTC))<br /> * eMac G4 with 256MB RAM, DVD writer, 80GB (might be 60?) HDD -- Can bring in if there is a use for it. [[User:Tomkinsc|Tomkinsc]] 04:58, 3 January 2010 (UTC)<br /> * I can donate a G4 466mhz (Digital Audio) currently has 10.4 installed and misc hardware like CD drives/burners [[User:IGadget|IGadget]] 01:18, 7 January 2010 (UTC) <br /> * I have a spare split 66 block for terminating POTS lines and about 50 feet of 25 pair if needed. [[User:IGadget|IGadget]] 01:18, 7 January 2010 (UTC)<br /> * Apple LaserWriter 8500 currently in storage - It is network capable - postscript,16 ppm/duplexer and extra trays. [[User:IGadget|IGadget]] 05:01, 8 January 2010 (UTC)<br /> * Cisco 3550 switch --[[User:Cprofitt|Cprofitt]] 20:43, 18 January 2010 (UTC)<br /> * Cisco 2950 switch --[[User:Cprofitt|Cprofitt]] 03:33, 25 January 2010 (UTC)<br /> * Seagate 20GB IDE Drive --[[User:Cprofitt|Cprofitt]] 20:43, 18 January 2010 (UTC)<br /> * Hitachi Deskstar 82.3GB IDE Drive --[[User:Cprofitt|Cprofitt]] 20:43, 18 January 2010 (UTC)<br /> * Seagate 20GB IDE Drive --[[User:Cprofitt|Cprofitt]] 20:43, 18 January 2010 (UTC)<br /> * Seagate 60GB IDE Drive --[[User:Cprofitt|Cprofitt]] 20:43, 18 January 2010 (UTC)<br /> * Half-Height 19&quot; equipment cabinet -- [[User:Carl|Carl]]<br /> <br /> === Tools ===<br /> * [http://www.flickr.com/photos/bert_m_b/4086757469/ Marsh Model Q 1/4-inch Stencil Press] -- Brian B.<br /> * Small table saw -- Brian B.<br /> * Leader Oscilloscope LBO-522 -- Brian B.<br /> * 2x 25w soldering irons, a breadboard, lots of wiring, assorted electronics kits and tools --Alan<br /> * HP 1664A logic analyzer --Josh<br /> * Power supply/Variac --Josh<br /> * &lt;S&gt;Decade box [[User:Fvox13|Fvox13]] 21:42, 7 December 2009 (UTC) (donated 2010-11-01)&lt;/S&gt;<br /> * Dremel with attachments and flexible shaft -- Alvaro<br /> * Hakko 936 Soldering Station -- Alvaro<br /> * Tenma soldering station, power drill, drill bits, wrenches, etc. [[User:BinaryMan|BinaryMan]] 01:34, 4 September 2010 (UTC)<br /> <br /> === Furnishings ===<br /> * Rubbermaid work desk. Should not be used near hot things, its actually made out of plastic [[User:Cmd3187|Cmd3187]] 16:01, 8 December 2009 (UTC)<br /> * 3-shelf AV cart --Brian B.<br /> * 6ft rubbermaid folding table --Alan<br /> * 5'x8' whiteboard (it's big...) --Josh<br /> * Two regular wooden chairs, one rolling padded chair. --Josh<br /> * Maybe a set of couches- must consult neighbor --Josh<br /> * Dorm style couch once I get back into my storage garage. [[User:IGadget|IGadget]] 17:50, 6 January 2010 (UTC)<br /> <br /> === Services ===<br /> * I jerk cable as a side job... I'd love to do any low-voltage wiring, especially ethernet (--[[User:Fvox13|Fvox13]] 06:01, 2 December 2009 (UTC))<br /> * I pull cable as well and have a Jack Rapid for Leviton jacks. As well as all of the other tools like fishes, crimpers, and punchdown tools. [[User:IGadget|IGadget]] 17:47, 6 January 2010 (UTC)</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Resources_we_need_or_want 2010-11-02T23:34:11Z

<p>Fvox13: </p> <hr /> <div>=== Charitable Contributions ===<br /> See [http://interlockroc.org/contribute http://interlockroc.org/contribute] for more information.<br /> <br /> === Safety Items ===<br /> * Hearing protection (plugs/muffs)<br /> * Eye protection (facemask/teh goggles)<br /> * &lt;S&gt;First Aid kits&lt;/S&gt;<br /> * &lt;S&gt;Fire extinguisher&lt;/S&gt;<br /> <br /> === Fabrication Tools ===<br /> * &lt;S&gt;Drill Press - the one donated didn't have a drill&lt;/S&gt;<br /> * &lt;S&gt;Table Saw&lt;/S&gt;<br /> * &lt;S&gt;Power Drill (Corded or cordless, hammer option a plus) &lt;/S&gt;<br /> * Drill bit set<br /> * CNC machine<br /> * &lt;S&gt;Shop Vacuum&lt;/S&gt;<br /> * Laser Cutter/Engraver - used to make designs into tons of materials. Laptop cases, pieces of metal, cut thin wood and plastic. Usage could be sold to the public to raise money to pay for it<br /> * Propane and propane accessories (blow torches etc) (can we get a donation from Strickland Propane?)<br /> * Reprap - design and make 3 dimensional objects<br /> * Spot welder (there is a maker project for this)<br /> <br /> === Electronics Tools ===<br /> * &lt;S&gt;Oscilloscope&lt;/S&gt;<br /> * Multimeters<br /> * Signal Generators<br /> * Logic Analyzers<br /> * Power Supplies<br /> * Breadboards<br /> * Circuit Fabrication equipment (etchant, photoresist?)<br /> <br /> === Electronics &amp; Parts ===<br /> * [http://www.goldmine-elec-products.com/prodinfo.asp?number=G17225 Ginormous Surprise Box]<br /> * [http://www.sciplus.com/recommend.cfm/recommendid/3501 Surprise Box of Science] (sounds like a Bill Nye thing... :-) )<br /> * Multiple Arduino type IC's - great for learning about circuitry and random projects that come up. Could be an Arduino or one of the cheaper versions<br /> * XBee IC's - used for making interesting wireless devices [http://www.digi.com/products/wireless/point-multipoint/xbee-series1-module.jsp link]<br /> <br /> === Furnishings ===<br /> * Grill - for our summer hacker parties<br /> * Kegerator - for our summer hacker parties<br /> * Dark Room - for photo geeks<br /> * &lt;S&gt;Lockers - members can store personal property, keep their projects out of the way, and keep track of their things easier&lt;/S&gt;<br /> * Bike Parking - a rack or area to keep bikes<br /> * crash pad for powernaps (comfy [expensive] furniture from [http://www.studiooneup.com/ Studio One Up])<br /> * robotic pet for artificial companionship<br /> * spray booth - spray paint things into a well ventilated area so as not to die<br /> * &lt;s&gt;big ol' whiteboard (DIY with plexiglass or [http://www.rustoleum.com/CBGProduct.asp?pid=128 Dry erase paint])&lt;/s&gt;<br /> * Commercial Grade coffee maker (possibly one of [http://www.amazon.com/Bunn-Commercial-Automatic-Brewer/dp/B002WPUBWS these], or at least one of [http://www.amazon.com/gp/product/B000G9WK8K/ref=pd_lpo_k2_dp_sr_1?pf_rd_p=486539851&amp;pf_rd_s=lpo-top-stripe-1&amp;pf_rd_t=201&amp;pf_rd_i=B00012XCZW&amp;pf_rd_m=ATVPDKIKX0DER&amp;pf_rd_r=0B15WZTBBEARXDZ85CDR these]. Alternatively [http://www.amazon.com/Keurig-Single-Gourmet-Coffee-Brewing/dp/B001TKEUXI/ref=sr_1_3?ie=UTF8&amp;s=kitchen&amp;qid=1259736180&amp;sr=1-3 this]) Keep in mind that the Keurig has a higher per-cup cost, wheras the Bunn units are dirt cheap, after the initial outlay of a lot of money. --[[User:Fvox13|Fvox13]] 06:15, 4 December 2009 (UTC)<br /> * &lt;S&gt;Bookshelves&lt;/S&gt;<br /> * &lt;S&gt;Projector&lt;/S&gt;<br /> * &lt;S&gt;Workbenches w/ power strips and good lighting&lt;/S&gt;<br /> * Fans and/or cooling system - it's going to be hot in the basement with no open windows. Fans or a way to keep cool would be useful.<br /> <br /> === Computer/IT ===<br /> * &lt;s&gt;Servers (P4 or better. Prefer blades)&lt;/s&gt;<br /> * LCD monitors - uses less energy and space, easier to use during Linux workshops<br /> * Battery Backup System - for the servers and the network equipment. At least for integral production equipment<br /> <br /> === Radio (ham/amateur radio) ===<br /> * See [[Roof antenna]]<br /> * We will gladly accept any working ham gear in decent condition. Some of our licensed hams are completely without radios!</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Roof_antenna 2010-10-30T20:14:46Z

<p>Fvox13: </p> <hr /> <div>We would like to install a 2M/400 antenna (and possibly others) on the roof of the Hungerford building, where Interlock is in the basement. We have the go-ahead from the building owners. We are in desperate need of contributions in order to make this project possible! If we are going to do it, we want to do it right. Ideally we will use LMR400 feed-line and build a free-standing tower that is capable of hosting multiple antennas for future expansion<br /> <br /> <br /> == Bill of Materials ==<br /> * 2m/70cm J-Pole (donated by Alvaro)<br /> * 200ft LMR-400-DB $192.00 (we're not burying it, but DB is waterproof, and given our aggressive freeze-thaw cycles, a must)<br /> * 3 pcs EZ-400-UM Connectors $45 (need 3 in case we screw up the crimping? They're $15 apiece; it'd be a shame to not use one of them though...)<br /> <br /> == Things to figure out ==<br /> * What do we use for a tower?<br /> * What do we use to attach the cable to the building? Industrial velcro?<br /> * Would schedule 40 be a good choice for constructing the tower itself?<br /> * Do we need to put a strobe on top? Even if we don't have to, should we?<br /> <br /> <br /> == Finances ==<br /> * Ben / Bill have each pledged $50<br /> * Steve has pledged $75<br /> <br /> Total: $175 of estimated $300<br /> <br /> Will Interlock match our contributions, even partially?<br /> <br /> WePay link: [https://www.wepay.com/public/view/35059]<br /> <br /> K2FX's preferred vendor: [http://www.rfparts.com/]<br /> <br /> <br /> == Construction ==<br /> * Based on a site survey by Rowan &amp; Steve, we need approximately 160-170 feet of cable. We're going to buy 200 feet to be safe.<br /> * We are planning on mounting the antenna on a pole that would extend approximately 20-30 feet above the highest point of the roof. This is the stair tower where the north-facing elements of the Nextel cell tower are attached. We would be on the opposite side of these antennae.<br /> * The pole would be attached in such a way that one person could tip it over for servicing<br /> * Paul K2FX has agreed to come over and terminate our connectors with his special $400 tool. We just need to give him a call when we're ready.</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Roof_antenna 2010-10-30T19:15:38Z

<p>Fvox13: /* Bill of Materials */</p> <hr /> <div>We would like to install a 2M/400 antenna (and possibly others) on the roof of the Hungerford building, where Interlock is in the basement. We have the go-ahead from the building owners. We are in desperate need of contributions in order to make this project possible! If we are going to do it, we want to do it right. Ideally we will use LMR400 feed-line and build a free-standing tower that is capable of hosting multiple antennas for future expansion<br /> <br /> <br /> == Bill of Materials ==<br /> * 2m/70cm J-Pole (donated by Alvaro)<br /> * 200ft LMR-400-DB $192.00 (we're not burying it, but DB is waterproof, and given our aggressive freeze-thaw cycles, a must)<br /> * 3 pcs EZ-400-UM Connectors $45 (need 3 in case we screw up the crimping? They're $15 apiece; it'd be a shame to not use one of them though...)<br /> <br /> == Things to figure out ==<br /> * What do we use for a tower?<br /> * What do we use to attach the cable to the building?<br /> * Would schedule 40 be a good choice?<br /> * Do we need to put a strobe on top? Even if we don't have to, should we?<br /> <br /> <br /> == Finances ==<br /> * Ben / Bill have each pledged $50<br /> * Steve has pledged $75<br /> <br /> Total: $175 of estimated $300<br /> <br /> Will Interlock match our contributions, even partially?<br /> <br /> WePay link: [https://www.wepay.com/public/view/35059]<br /> <br /> K2FX's preferred vendor: [http://www.rfparts.com/]<br /> <br /> <br /> == Construction ==<br /> * Based on a site survey by Rowan &amp; Steve, we need approximately 160-170 feet of cable. We're going to buy 200 feet to be safe.<br /> * We are planning on mounting the antenna on a pole that would extend approximately 20-30 feet above the highest point of the roof. This is the stair tower where the north-facing elements of the Nextel cell tower are attached. We would be on the opposite side of these antennae.<br /> * The pole would be attached in such a way that one person could tip it over for servicing<br /> * Paul K2FX has agreed to come over and terminate our connectors with his special $400 tool. We just need to give him a call when we're ready.</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Roof_antenna 2010-10-30T19:13:56Z

<p>Fvox13: </p> <hr /> <div>We would like to install a 2M/400 antenna (and possibly others) on the roof of the Hungerford building, where Interlock is in the basement. We have the go-ahead from the building owners. We are in desperate need of contributions in order to make this project possible! If we are going to do it, we want to do it right. Ideally we will use LMR400 feed-line and build a free-standing tower that is capable of hosting multiple antennas for future expansion<br /> <br /> <br /> == Bill of Materials ==<br /> * 2m/70cm J-Pole (donated by Alvaro)<br /> * 200ft LMR-400-DB $192.00<br /> * 3 pcs EZ-400-UM Connectors $45 (need 3 in case we screw up the crimping? They're $15 apiece; it'd be a shame to not use one of them though...)<br /> <br /> <br /> <br /> == Things to figure out ==<br /> * What do we use for a tower?<br /> * What do we use to attach the cable to the building?<br /> * Would schedule 40 be a good choice?<br /> * Do we need to put a strobe on top? Even if we don't have to, should we?<br /> <br /> <br /> == Finances ==<br /> * Ben / Bill have each pledged $50<br /> * Steve has pledged $75<br /> <br /> Total: $175 of estimated $300<br /> <br /> Will Interlock match our contributions, even partially?<br /> <br /> WePay link: [https://www.wepay.com/public/view/35059]<br /> <br /> K2FX's preferred vendor: [http://www.rfparts.com/]<br /> <br /> <br /> == Construction ==<br /> * Based on a site survey by Rowan &amp; Steve, we need approximately 160-170 feet of cable. We're going to buy 200 feet to be safe.<br /> * We are planning on mounting the antenna on a pole that would extend approximately 20-30 feet above the highest point of the roof. This is the stair tower where the north-facing elements of the Nextel cell tower are attached. We would be on the opposite side of these antennae.<br /> * The pole would be attached in such a way that one person could tip it over for servicing<br /> * Paul K2FX has agreed to come over and terminate our connectors with his special $400 tool. We just need to give him a call when we're ready.</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Roof_antenna 2010-10-30T19:13:07Z

<p>Fvox13: </p> <hr /> <div>We would like to install a 2M/400 antenna (and possibly others) on the roof of the Hungerford building, where Interlock is in the basement. We have the go-ahead from the building owners. We are in desperate need of contributions in order to make this project possible! If we are going to do it, we want to do it right. Ideally we will use LMR400 feed-line and build a free-standing tower that is capable of hosting multiple antennas for future expansion<br /> <br /> <br /> == Bill of Materials ==<br /> * 2m/70cm J-Pole (donated by Alvaro)<br /> * 200ft LMR-400-DB $192.00<br /> * 3 pcs EZ-400-UM Connectors $45 (need 3 in case we screw up the crimping)<br /> <br /> <br /> <br /> == Things to figure out ==<br /> * What do we use for a tower?<br /> * What do we use to attach the cable to the building?<br /> * Would schedule 40 be a good choice?<br /> * Do we need to put a strobe on top? Even if we don't have to, should we?<br /> <br /> <br /> == Finances ==<br /> * Ben / Bill have each pledged $50<br /> * Steve has pledged $75<br /> <br /> Total: $175 of estimated $300<br /> <br /> Will Interlock match our contributions, even partially?<br /> <br /> WePay link: [https://www.wepay.com/public/view/35059]<br /> <br /> K2FX's preferred vendor: [http://www.rfparts.com/]<br /> <br /> <br /> == Construction ==<br /> * Based on a site survey by Rowan &amp; Steve, we need approximately 160-170 feet of cable. We're going to buy 200 feet to be safe.<br /> * We are planning on mounting the antenna on a pole that would extend approximately 20-30 feet above the highest point of the roof. This is the stair tower where the north-facing elements of the Nextel cell tower are attached. We would be on the opposite side of these antennae.<br /> * The pole would be attached in such a way that one person could tip it over for servicing<br /> * Paul K2FX has agreed to come over and terminate our connectors with his special $400 tool. We just need to give him a call when we're ready.</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Roof_antenna 2010-10-30T19:02:07Z

<p>Fvox13: </p> <hr /> <div>We would like to install a 2M/400 antenna (and possibly others) on the roof of the Hungerford building, where Interlock is in the basement. We have the go-ahead from the building owners. We are in desperate need of contributions in order to make this project possible! If we are going to do it, we want to do it right. Ideally we will use LMR400 feed-line and build a free-standing tower that is capable of hosting multiple antennas for future expansion<br /> <br /> <br /> == Bill of Materials ==<br /> * 2m/70cm J-Pole (donated by Alvaro)<br /> * 200ft LMR-400-DB $192.00<br /> * 3 pcs EZ-400-UM Connectors $45 (need 3 in case we screw up the crimping)<br /> <br /> <br /> <br /> == Things to figure out ==<br /> * What do we use for a tower?<br /> * What do we use to attach the cable to the building?<br /> * Would schedule 40 be a good choice?<br /> * Do we need to put a strobe on top? Even if we don't have to, should we?<br /> <br /> <br /> == Finances ==<br /> * Ben / Bill have each pledged $50<br /> * Steve has pledged $75<br /> <br /> Total: $175 of estimated $300<br /> <br /> Will Interlock match our contributions, even partially?<br /> <br /> WePay link: [https://www.wepay.com/public/view/35059]<br /> <br /> <br /> == Construction ==<br /> * Based on a site survey by Rowan &amp; Steve, we need approximately 160-170 feet of cable. We're going to buy 200 feet to be safe.<br /> * We are planning on mounting the antenna on a pole that would extend approximately 20-30 feet above the highest point of the roof. This is the stair tower where the north-facing elements of the Nextel cell tower are attached. We would be on the opposite side of these antennae.<br /> * The pole would be attached in such a way that one person could tip it over for servicing<br /> * Paul K2FX has agreed to come over and terminate our connectors with his special $400 tool. We just need to give him a call when we're ready.</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Ceiling_/_LED_Awesomeness 2010-08-15T07:49:09Z

<p>Fvox13: </p> <hr /> <div>== Problem(s) ==<br /> * Fluorescent lights are not l33t enough<br /> * Mood / situation lighting is important, especially when you're here late at night<br /> * Our neighbors above like to jump around, jump around, Jump up Jump up and get down, and leave dust all over the space as a result<br /> <br /> <br /> == Proposed Solution ==<br /> Based on some discussions with other members, and [http://ask.metafilter.com/155644/Mood-lights-FTW random strangers on the internet], I'd like to set up some kind of diffuse LED lighting.<br /> <br /> <br /> === Diffusers ===<br /> * We are going to staple white fabric between the beams. Once its up, we're not going to take it down.<br /> * Diffusers would be mounted between the beams. The bottom face of the beams would be exposed.<br /> * Diffusers would be mounted above the piping system, so as to preserve the paint job, and allow access to the space by the water from the sprinkler heads, should the need arise.<br /> <br /> <br /> === LEDs ===<br /> Each LED will ultimately be *individually addressable*<br /> * 6 of 4 LEDs each, per section of ceiling (as defined by the intersection of beams)<br /> * Each cluster would consist of 4 LEDs, one each of red, green, blue, and white<br /> * Each cluster would consist of 4 LEDs plugged into a 2x4 IDC (no soldering!)<br /> * Each cluster would be fed by a Category 5 network cable (cheaper) or ribbon cable (nicer)<br /> * Each section of ceiling would terminate to a 25-pin IDC connector. Two of these would plug into a 50-conductor ribbon cable, bundles of which would run down the North/South center beam in the ceiling. 50-conductor cables would plug into surface-mount or edge connectors on the control system<br /> <br /> === Control System ===<br /> We plan to create a control circuit, and fab out the manufacture of a PCB. PCB would need to have 10 50-conductor IDC pin blocks on it.<br /> <br /> <br /> === Costs ===<br /> * Found a source of 10mm bright LEDs. bestshop2008hk on eBay would provide 800 LEDs for $120.<br /> * Ribbon cables and IDC connectors would run about $200<br /> * PCB could run $50 or so.<br /> <br /> <br /> === Q &amp; A ===<br /> * How bright is this thing?<br /> ** Each LED puts out 20-40K MCD. Based on some really fuzzy math to convert that to lumens, we'd roughly have the equivalent light of a 40 watt lightbulb, per color, per ceiling grid (each grid is about 40 sq feet). TL;DR... pretty bright. We'd probably want to supplement with additional incandescent lamps or directed workspace lights; this project is intended to be bright, but not bright enough to do fine work.<br /> <br /> <br /> === Purchasing ===<br /> If you'd like to contribute, please give money to Steve Smith. He'll be coordinating an eBay order or two.<br /> <br /> <br /> === Assembly ===<br /> Once the stuff has all arrived, we're gonna need to hook up a bunch of LEDs and figure out a control mechanism. I'll need help with the circuit design.</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Projects 2010-06-08T20:19:45Z

<p>Fvox13: </p> <hr /> <div>==Project Process==<br /> * Brainstorm with other people on [[ideas]]<br /> * Send out an announcement (via Google Group) that you are interested in starting a new project.<br /> * Update the wiki, using the [[Projects_Template| project template]]<br /> * Update the President / Vice President on milestones so they can add it to the weekly project updates<br /> * Keep member collaboration centralized via one of the following tools:<br /> ** Bulletin / Message Board (software TBD, highly recommend SMF)<br /> ** Separate Google Groups mailing list<br /> ** &lt;insert tool here&gt; - only requirement is that all members have access to it. Bonus points if it integrates with the LDAP server.<br /> <br /> == [[Ceiling / LED Awesomeness]] ==<br /> <br /> == [[Official Friends of Interlock trophy]] ==<br /> <br /> == [[Hackerspace Security System]] ==<br /> <br /> == [[Interlock Shop Radio]] ==<br /> <br /> == [[ Kegerator ]] ==<br /> <br /> == [[ Phreaking ]] ==<br /> <br /> == Reprap/Makerbot Build ==<br /> Description: Berticus really wants to tinker with 3d printing, and thus desires access to either a Makerbot or the next generation Reprap Mendel.<br /> <br /> Details: [http://makerbot.com/ Makerbots] can be purchased for $750 or $950. The higher price reflects some premium features, mainly pre-assembled electronics, a power supply, and some extra plastic filament. Bots are currently rather backordered. Mendel parts are impossible to find. There seem to be no kits out there for the non-extruded parts (threaded rod, etc.), so even if we can find somebody to print us the plastic bits, it'll still be a bit of a pain to get everything together. Right now a Makerbot is probably the way to go, and we can use that to print out the Mendel parts to make a second bot for experimentation (developing new print heads and such).<br /> <br /> == Ashley's Silly Web Projects ==<br /> BedBugsHotels.com &lt;- looking to collab with someone to build something like bedbugregistry.com but not as lame, using googlemaps. started the site in rails, but have not got very far with this. pretty sure there's traffic waiting for a well developed site along these lines, and it could be fun?<br /> <br /> hotpinkwedding.com &lt;- no one is going to be interested in this topic, per se. But I'm interested in using and learning about different techniques to boost serp via experimentation, if anyone is into that. 700-800 unique visitors a month currently (and counting) :P<br /> <br /> simplerochester.com &lt;- websites hosted on AWS. Looking to redevelop the business model in a unique way and mess around with marketing.<br /> <br /> == Interlock Floor Coverings ==<br /> Problem: The floor is concrete, which while suited to welding, etc, is ugly and non-l33t.<br /> Solution: Come up with one or more floor coverings.<br /> <br /> Ideas:<br /> * LED Disco Dance Floor like [http://www.scotttorborg.com/disco-dance-floor/ this one] at MIT<br /> ** Maybe with an option to have solid colors or something less crazy, so we can use it more often than not<br /> * Section off part of the floor using 2x4s and put dirt and grass there (how do we grow grass with no light?)<br /> * Astroturf<br /> <br /> == [[Interlock Dumpster Diving Crew]] ==<br /> <br /> == [[Interlock Database]] ==<br /> Problem: With all the content that is being added to the space (materials, hardware, software, books, etc) we need a way to keep track of what we have.<br /> Solution: For the time being, a simple flat-file database (using googledocs) has been created. Please use form link(s) below to enter them.<br /> <br /> * Member Information can be filled out [https://spreadsheets.google.com/viewform?formkey=dGR0UURoQkJSdUZvRkNQNHFfYUI2TlE6MA here].<br /> * Books can be added to the library [https://spreadsheets.google.com/viewform?formkey=dDk5ajAxZUlCeVJaNExlU3Job1RqYlE6MA here].<br /> ** a brief summary can be viewed [https://spreadsheets.google.com/viewanalytics?formkey=dDk5ajAxZUlCeVJaNExlU3Job1RqYlE6MA here].<br /> * Hardware donations can be entered using the form [https://spreadsheets.google.com/viewform?formkey=dHFOa3E1clJwcmN0OHNsMzk0QmtTMUE6MA here].<br /> <br /> == System Management Software ==<br /> I have been looking around online at some potential system management setups that are open source, and sadly, there really are only a few command and script based ones like cfengine and puppet. I am thinking about creating a web-based system with agents for the workstations, so that a mixed-system shop could be maintained. I think this would be a really fun project because it would involve members that are more on the sys/net admin end as well as the developers. I have posted a few links below for additional information about this.<br /> * [http://en.wikipedia.org/wiki/List_of_systems_management_systems Wikipedia: List of Systems Management Systems]<br /> * [http://en.wikipedia.org/wiki/FCAPS Wikipedia: ISO model and framework for network management]<br /> <br /> [[Category:Projects]]</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Ceiling_/_LED_Awesomeness 2010-06-04T02:05:09Z

<p>Fvox13: Created page with '== Problem(s) == * Fluorescent lights are not l33t enough * Mood / situation lighting is important, especially when you're here late at night * Our neighbors above like to jump a…'</p> <hr /> <div>== Problem(s) ==<br /> * Fluorescent lights are not l33t enough<br /> * Mood / situation lighting is important, especially when you're here late at night<br /> * Our neighbors above like to jump around, jump around, Jump up Jump up and get down, and leave dust all over the space as a result<br /> <br /> <br /> == Proposed Solution ==<br /> Based on some discussions with other members, and [http://ask.metafilter.com/155644/Mood-lights-FTW random strangers on the internet], I'd like to set up some kind of diffuse LED lighting.<br /> <br /> <br /> === Diffusers ===<br /> * Question: Do we staple fabric between the beams, or do we rig up some kind of frosty plastic and treat it like a drop ceiling?<br /> * Diffusers would be mounted between the beams. The bottom face of the beams would be exposed.<br /> * Diffusers would be mounted above the piping system, so as to preserve the paint job, and allow access to the space by the water from the sprinkler heads, should the need arise.<br /> <br /> <br /> === LEDs ===<br /> * 6 - 8 clusters of 4 LEDs each, per section of ceiling (section == part defined by the intersection of beams)<br /> * Each cluster would consist of 4 LEDs, one each of red, green, blue, and white<br /> * Each cluster would be fed by a Category 5 network cable (8 conductors... 4 LEDs.... yeah...)<br /> <br /> <br /> === Control System ===<br /> Build this iteratively, so that we can get something up and running. Initial prototype could just be sliders (1 for each color of light, as a channel). Future versions could incorporate serial communications, arduini, debian boxen, etc. And zones. That would be cool.<br /> <br /> <br /> === Costs ===<br /> * 200 10mm Red LEDs: [http://www.hero-ledstore.com/super-bright-leds-ultra-brightness-10mm-led-100pcs-p-5.html $60 (2 x $30)]<br /> * 200 10mm Green LEDs: [http://www.hero-ledstore.com/super-bright-leds-ultra-brightness-10mm-led-100pcs-p-5.html $67 (2 x $33.50)]<br /> * 200 10mm Blue LEDs: [http://www.hero-ledstore.com/super-bright-leds-ultra-brightness-10mm-led-100pcs-p-5.html $66 (2 x $33)]<br /> * 200 10mm White LEDs: [http://www.hero-ledstore.com/super-bright-leds-ultra-brightness-10mm-led-100pcs-p-5.html $66 (2 x $33)]<br /> * Category 5 Ethernet Cable: Free / Cheap... is laying around the space<br /> * Fabric or frosty plastic stuff: $50 (guess)<br /> * Some sliders or control mechanism: $20?<br /> <br /> <br /> === Q &amp; A ===<br /> * How bright is this thing?<br /> ** Those LEDs are approximately 10,000 mcd. That's about 120 lumens. Your standard 40 watt lightbulb is usually 300-600 lumens. If we have 6 - 8 of each color in each ceiling section, that's 600-900 lumens per section. In other words, we'd have the equivalent light of a 40 watt lightbulb, per color, per ceiling grid (each grid is about 40 sq feet). TL;DR... pretty bright.<br /> <br /> <br /> === Purchasing ===<br /> If you'd like to contribute, please order or otherwise obtain one or more of the following items. Put your name next to the item when you order something so that we don't have duplicate purchases. If you want to order from someplace else, thats fine. Just make sure they're 10mm LEDs, and that the wavelengths/voltages/sizes all match.<br /> * [http://www.hero-ledstore.com/super-bright-leds-ultra-brightness-10mm-led-100pcs-p-5.html 1, 100pcs Bag of 10mm Red LEDs] Steve Smith<br /> * [http://www.hero-ledstore.com/super-bright-leds-ultra-brightness-10mm-led-100pcs-p-5.html 1, 100pcs Bag of 10mm Red LEDs] Steve Smith<br /> * [http://www.hero-ledstore.com/super-bright-leds-ultra-brightness-10mm-led-100pcs-p-5.html 1, 100pcs Bag of 10mm Green LEDs]<br /> * [http://www.hero-ledstore.com/super-bright-leds-ultra-brightness-10mm-led-100pcs-p-5.html 1, 100pcs Bag of 10mm Green LEDs]<br /> * [http://www.hero-ledstore.com/super-bright-leds-ultra-brightness-10mm-led-100pcs-p-5.html 1, 100pcs Bag of 10mm Blue LEDs]<br /> * [http://www.hero-ledstore.com/super-bright-leds-ultra-brightness-10mm-led-100pcs-p-5.html 1, 100pcs Bag of 10mm Blue LEDs]<br /> * [http://www.hero-ledstore.com/super-bright-leds-ultra-brightness-10mm-led-100pcs-p-5.html 1, 100pcs Bag of 10mm White LEDs]<br /> * [http://www.hero-ledstore.com/super-bright-leds-ultra-brightness-10mm-led-100pcs-p-5.html 1, 100pcs Bag of 10mm White LEDs]<br /> * A couple of bolts of white fabric and enough staples to get them to stay up on the ceiling OR Frosty plastic stuff and hardware to hang it<br /> * Sliders / Control Mechanism? Not sure what to buy here... suggest something!<br /> <br /> <br /> === Assembly ===<br /> Once the stuff has all arrived, we're gonna need to solder a ton of stuff. Just sayin'</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Build_Out 2010-03-17T19:38:32Z

<p>Fvox13: </p> <hr /> <div>=Space Build Out=<br /> We need to figure out what we need to do to make the space exactly how we'd like it. This includes painting, construction, building/putting together shelves, etc. Feel free to edit this page to discuss ideas and personal building projects.<br /> <br /> ==Build Out Dates==<br /> No dates have been set yet. Suggested dates:<br /> * April 3, 2010<br /> * April 10, 2010<br /> <br /> =Painting Projects=<br /> I think we can all agree that the white colored walls are drab and don't add anything to our space. We can make the space as vibrant as we are as a group!<br /> <br /> ==Pipes==<br /> A few people have already started painting the pipes in the room. We currently have some blue pipes, some black pipes and some lime and cyan pipes. We can paint the rest of the pipes to continue on and we can make new colors at junctions (or at different pipes.)<br /> <br /> * I think it would be really cool to have all of the pipes colored solidly along their entire length, which would create a very simple blend of colors as they cross over and under each other. --[[User:Amouravski|Amouravski]] 18:32, 17 March 2010 (UTC)<br /> <br /> * Pipes that have sprinkler heads on them need to be red, for safety / compliance issues.<br /> <br /> ==Walls==<br /> The walls are bland white, let's fix that. Keep in mind that one wall should remain white (for the time being) so that our projector has a surface to project on. Ideas include painting murals, putting more whiteboards on the walls (and actually mounting them) and getting a projector screen.<br /> <br /> <br /> ==Ceiling==<br /> The ceiling needs some work. Black seemed to work across the hall. Ditto for the columns.<br /> Steampunk-ness was suggested, but the amount of labor may be prohibitive, as would the necessary amount of ventilation to properly varnish the wood.<br /> <br /> <br /> ===Projector Screen===<br /> We should probably get a projector screen so that we can always be sure of having a good surface to project onto.<br /> Ideas?<br /> <br /> <br /> ===Murals===<br /> * Going along the lines of Freeside Atlanta, I would like to see more artistic expression around the space. I would like to see really interesting unique murals on the walls of our space. Something bold to look at that's not just white. --[[User:Amouravski|Amouravski]] 18:32, 17 March 2010 (UTC)<br /> * I'm planning on painting an optical illusion mural where if you stand at the front door and look towards the kitchen, then you will see a flat Interlock logo, but in reality, the logo is spread out over various items. It'll be cool. Trust me. --[[User:Amouravski|Amouravski]] 19:07, 17 March 2010 (UTC)<br /> <br /> ===Whiteboards===<br /> We discussed this awhile ago, but we should get more whiteboards so that we are able to both discuss things during seminars and the like. Multiple whiteboards would allow for one that acts purely as a didactic tool, one that is for events and agendas, others for side conversations, etc. Putting a whiteboard where the projector projects would allow for writing on the slides, etc.<br /> <br /> * Home Depot sells large sheets of effectively laminated particleboard, which I assume is for walls or floors, but it works really well as a whiteboard. I have one in my room. It is something like 12'x6' (will measure later) and cost about $15. The only thing is that we need to get a truck or something to transport them effectively. This is a cheap solution, without magnets, but light so that they can be easily mounted. --[[User:Amouravski|Amouravski]] 18:32, 17 March 2010 (UTC)<br /> <br /> ===Walls===<br /> Painting the walls an interesting color could add brightness to the space. Mixed with good lighting, we could create a good atmosphere. However, colored lights with white walls may be good enough.<br /> <br /> ==Columns==<br /> The columns we have in the space are ugly and stupid and ugly. Let's do something<br /> *My idea is to sand down the columns entirely, down to the bare wood and then find a good stain, something deep mahogany or so, and then stain the wood until it looks good (old, antique, hardcore) and then put a good clear finish on it. Then we can take the the sheet metal joints, sand those down, and then paint them bright metallic brass color on them and if that looks good, keep it as is, otherwise dirty it up with some stain and then voila! we have steampunk columns! --[[User:Amouravski|Amouravski]] 19:07, 17 March 2010 (UTC)<br /> *Oh yeah, we can also do this for all the ceiling beams, but that's quite a lot of work. However, if we actually do it, the space will look really cool and will have a really homey feel to it, even with the colorful pipes. --[[User:Amouravski|Amouravski]] 19:07, 17 March 2010 (UTC)<br /> <br /> =Lights=<br /> There have been several ideas about retooling the bright fluorescent lights we have hanging currently.<br /> * One idea is to replace the lights with LED lights, so that we could control the brightness and make the lights less harsh.<br /> * Another idea is to mount lights behind the rafters to help diffuse the light.<br /> * Not sure whether we should keep the lights and supplement them, or replace them entirely.<br /> <br /> Discuss.<br /> <br /> =Shelving=<br /> We have discussed shelving ideas but now we need to really put something together.<br /> * Cubby system is one idea, where people could store their own stuff, but also have space for our tools.<br /> * Big metal shelves. These would be immovable, and have lots of space. Fit against a wall, up to the ceiling, we could store quite a bit more.<br /> We are starting to get a lot of stuff in the space: paint, tools, wires, networking stuff, and it needs a home.<br /> <br /> =Construction=<br /> What kinds of things should we permanently add to the space?<br /> ==Projector Mount==<br /> Currently the projector rests on the table and it is finicky to adjust it to point at the correct space on the wall. It's also annoying in that it takes up space on the table. It could go on the ceiling or attached to a column, but ceiling is more out of the way.<br /> <br /> Presumably a mount should:<br /> * Allow for easy connection to VGA/DVI ports.<br /> * Be out of the way, which includes power, etc.<br /> * Allow for removal of the projector if we need it down for other purposes.<br /> <br /> I am not sure if we have a remote for the projector, but one would be helpful.<br /> <br /> =Kitchen Improvements=<br /> The kitchen is great, but we're not really utilizing the space as well as we could be.<br /> ==Shelving==<br /> We have a lot of stuff just kind of sitting on top of a small table and on top of the fridges. This is not optimal. Shelves (as well as drawers) could help make the kitchen clutter free and it may make the place better for cooking/preparing food.<br /> <br /> =Tables &amp; Chairs=<br /> The tables were recently painted, which is awesome, but what else could we do to make the seating/table arrangement better?<br /> <br /> =Floors=<br /> If we keep concrete as the floor material, we need to paint it yearly to keep the dust down. Other options may be carpet or tile, or mixes of all three.</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Ideas 2009-12-16T22:26:45Z

<p>Fvox13: /* Security */</p> <hr /> <div>This page can be anything. Please don't delete other peoples ideas and use the discussion tab at the top. <br /> <br /> == Structure ==<br /> see [[organization]]<br /> <br /> == Security ==<br /> * We need a way to determine who has access to what (no system should be accessible to only a single administrator)<br /> * W also need a secure way to share login information<br /> ** PGP/GPG is a popular option but OS X support is severely lacking<br /> ** [http://keepass.info/ KeePass] on a network share would be a good cross-platform option. Allows for 2-factor auth (key + password, for example)<br /> <br /> == Membership Benefits ==<br /> * local discounts<br /> ** Goldcrest Electronics<br /> * 24x7 access to space<br /> * secret handshake<br /> * free or discounted admission to special events and classes<br /> * colo space (NOT for production sites)<br /> * very high speed internet<br /> * Google Apps account at interlockroc.org<br /> <br /> == Events ==<br /> * Weekly open house<br /> * Flash mobs<br /> * Computer repair clinic<br /> * LAN parties<br /> * Parts swap<br /> * Group partnerships<br /> ** Rochester 2600<br /> ** Rochester Hackers<br /> ** Make Club<br /> ** OWASP<br /> * Geeky art exhibitions and gallery<br /> * Bike rides<br /> * Trips to nearby hackerspaces<br /> * Rake leaves<br /> * Kids robotic group<br /> * Bike repair<br /> * Computer repair<br /> * We sponsor events<br /> * United Rochester Hackers Convention(Multi-group uber meeting with OWASP, SPARSA, Geek Rochester, Pythonistas, Rochester Hackers, Rochester 2600, Make Club)<br /> * Lightning talks - 5 minutes to talk on one subject and move on<br /> * Geek prom<br /> <br /> == Classes ==<br /> * Programming<br /> ** Python<br /> ** Perl<br /> ** Ruby<br /> ** JAVA<br /> ** C++<br /> * Soldering<br /> * Arduino<br /> * Bookbinding? (Brian B. knows a bit about this)<br /> * 3d printing, CNC routing, Pen plotter tinkering<br /> * Screen Printing<br /> * Homebrewing (beer)?<br /> * Bike repair and modding ([http://www.ladyada.net/make/spokepov/ Spoke POV] kits, DIY headlamps)<br /> * DIY Instruments (cigar box ukulele, [http://www.vimeo.com/3913619 diy piezo pickups], theremins)<br /> * Photography <br /> ** controlling dSLRs via computers<br /> ** writing scripts for [http://chdk.wikia.com/wiki/CHDK CHDK] <br /> ** alternate firmware for many point and shoot digicams<br /> * Consumer router &quot;hacking&quot; (dd-wrt or tomato firmware flashing, how to optimize settings for your bittorrenting pleasure)<br /> * Programming in [http://processing.org/ Processing], and interfacing with the Arduino<br /> * Welding<br /> * Amateur radio related topics<br /> * Network Security/Forensics<br /> * Visual Data Analysis [http://secviz.org Secviz.org]<br /> * Linux (maybe partner with the Linux User Group of Rochester (LUGOR)<br /> * Learning about home renovation projects<br /> * Kids hardware classes (bristlebots)<br /> * Metasploit<br /> * VMware<br /> = Project Ideas =<br /> See Also: [[projects]]<br /> <br /> == Random Thoughts ==<br /> * I saw this high speed camera hack on wired science. It think this could be a cool project that wont take too long. There are detailed [http://www.pbs.org/kcet/wiredscience/story/68-high_speed_photos.html instructions on how to do this hack].<br /> * [http://www.evilmadscientist.com/article.php/bristlebot Bristle Bots]<br /> * [http://graffitiresearchlab.com/?page_id=6 Throwies]<br /> * [http://www.hactivist.com/flashpoint/ Flashpoint Cameras] - project a message on a wall for cheap<br /> * [http://www.waveprotocol.org/ Google Wave Server] - Openfire based?<br /> * Xen Cluster<br /> ** [http://www.oracle.com/us/technologies/virtualization/index.htm Oracle VM]<br /> ** [http://www.convirture.com/ ConVirt]<br /> * Kegerator - With a notification system for temp or something like that. Maybe via Twitter<br /> * Screenprinted T-shirts ([http://magicalnihilism.com/2009/11/07/get-excited-and-make-things/ This design] has been released for free. Perhaps put the hackerspace name on the back)<br /> * Capture The Flag InfoSec game<br /> * Old School BBS<br /> * Practically everything on [http://www.hackaday.com Hackaday] would be fair game<br /> ** [http://hackaday.com/2009/12/11/bender-keg-cooler/ Bender Keg Cooler]<br /> <br /> <br /> == Interlock as an ISP ==<br /> There has been some debate about this, especially since we're doing the whole non-profit thing, but a non-profit *is* allowed to make money, as long as certain rules are followed.<br /> <br /> Basically, any Internet connection worth getting is going to be mucho expensive, and rather than get 30 new members just to pay for the Internet, it would make a lot of sense to resell it. Based on how expensive RoadRunner is in this building (probably what most of our neighbors have), and how crappy the speed is, I think we could undercut their price and still make it worthwhile to do this. I really want to run a fiber line into our space... the Internet is pretty much at the core of a lot of what we're doing, and we don't want it to be the weak link. But the options are looking like a.) Get 30 more members b.) Resell our connection or c.) Settle for something that is a lot slower than what most of us have at home.<br /> <br /> === Comments ===<br /> <br /> One objection raised for this was that we would be on the hook to provide 24x7 support for our &quot;customers&quot;. Fortunately our customers are mostly business types that don't work in the middle of the night. We would still require some kind of rotating schedule to carry a notification device (used to be a pager) and be available for support calls. Luckily there would not be many calls.<br /> <br /> The other big objection is liability. There are laws dictating how much we need to spy on our customers and liability issues if we spy too much. The legal aspects would require in depth investigation to make sure we are &quot;safe&quot;. Someone thought dealing with court orders and subpoenas might be cumbersome but after having to deal with a couple they aren't that tedious or scary. What was scary was thinking one of my customers was into child porn. I don't think he really was but it makes you wonder.<br /> <br /> All in all it might be reasonable way to subsidize our internet addiction. I don't expect we would get that many customers even if we offer more for less. Most people don't want to change unless there is a real problem with their current provider. And they would only consider us if they thought they could trust us. Personal contact is a big plus in that respect. A flyer in the hall or under the door won't convince anyone and pushing &quot;sales&quot; calls will turn people off. The best way to gain customers is to be a good neighbor and offering good unbiased advice and helpful suggestions. Free tech support is good too but you have to be careful to strictly limit it or you become their unpaid IT department.<br /> --[[User:Cws|Cws]] 22:16, 12 December 2009 (UTC)</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Lcd_overhead 2009-12-16T22:24:01Z

<p>Fvox13: </p> <hr /> <div>We should make one! I might be able to get my hands on an overhead projector with a newish bulb. Lacking:<br /> <br /> * either a laptop screen with a working controller and VGA, or,<br /> * working 13-15&quot; lcd monitor<br /> ** If someone has a 15.4 inch laptop LCD that does 1920x1200, this would let us have HD, but still fit on a standard overhead projector bed<br /> <br /> We can probably put this together for $50-$100. Drop notes if you'd like to participate! -[[User:wooby]]<br /> <br /> Relevant links:<br /> <br /> * [http://www.instructables.com/id/Cheap-Improved-LCD-Overhead-Projector/ Cheap Improved LCD Overhead Projector]</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Door_Security_System 2009-12-16T19:28:12Z

<p>Fvox13: </p> <hr /> <div>Also see [[Infrastructure#Physical Security]]<br /> <br /> ==Description:==<br /> The space will need a better way to keep track of who has access to come and go as they please. Keys are not an option. Key fob systems and other RFID technologies offer a way to control what a person has access to. <br /> <br /> See: http://www.instructables.com/id/Arduino-RFID-Door-Lock/<br /> See: http://www.chinavasion.com/product_info.php/pName/facial-recognition-time-attendance-system-and-access-door-lock/<br /> <br /> == Requirements ==<br /> Details: Construct a system that uses an RFID reader to grant access to the main door. The fob is also used to open other areas of the space depending on the member. OPTIONAL: build in a second factor authentication system. OPTIONAL: Construct a man trap so only one member can enter at a time. <br /> * RFID reader<br /> * fob<br /> ** [http://www.yubico.com/products/yubikey/ Yubikey] could be used with an old laptop on the cheap<br /> * electronic locks<br /> * server to manage ACLS (LDAP server? See [[Infrastructure#Network]])<br /> * second factor authentication system (biometrics, pin pad, TBD)<br /> <br /> == Parts ==<br /> TBD</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Network_acceptable_use_policy 2009-12-16T18:37:23Z

<p>Fvox13: </p> <hr /> <div>=Network Acceptable Use Policy=<br /> <br /> (This is a draft and has not been approved by legal council)<br /> <br /> == Preamble ==<br /> The rules that comprise this Code of Conduct apply to all areas of computer use at Interlock Rochester, including all computers, storage devices, networks, and network devices owned or managed by Interlock Rochester, including any for which Interlock Rochester contracts with a third party. [[The network infrastructure group]] is responsible for publishing, and in concert with other members of the community, enforcing this Code.<br /> <br /> A variety of computer resources are currently available at Interlock Rochester, from local area networks that provide access to PC, Mac, and *nix based software, to wide area networks such as the Internet. All users are required to follow this Code of Conduct when using these resources.<br /> <br /> Any information stored on Interlock computers, or with third party providers under contract by the group, may be stored digitally in multiple live and backup sources and, aside from the usual difficulties of guaranteeing confidentiality, is always subject to &quot;discovery&quot; by means of subpoena. Although the group may seek appropriate legal counsel, users should assume that the group will cooperate with outside agencies investigating violations of local, state, or federal law, including but not limited to copyright infringement, child pornography, or other illegal content.<br /> <br /> Violation of the Code can lead to:<br /> * Suspension of membership privileges<br /> * Criminal Prosecution<br /> <br /> ==Rules of Conduct==<br /> ===All Networks===<br /> * You may not give out your password.<br /> * You may not let another person use your account.<br /> * You may not copy, retain, or distribute copyrighted or proprietary material without written consent of the copyright holder.<br /> * Individuals who store sensitive or confidential information on their computers are accountable for that information and must make sure the appropriate security (encryption, etc.) is in place.<br /> * Interlock Rochester reserves the right to remove any technical resource (computers, software, network devices, etc.) that it deems a security or network risk<br /> <br /> ===Production and Playground Networks===<br /> * You may not possess or attempt to possess another user's password<br /> * You may not use false or misleading identification to gain access to any computing resource.<br /> * You may not use any computing resource that you are not authorized to use.<br /> * You may not use an account for any purpose other than that for which you are authorized.<br /> * You may not change, copy, delete, read or otherwise access files or software without permission of the owner (in the case of user files) or system administrator (in the case of system specific files).<br /> * You may not attempt to prevent others from accessing any computing resource.<br /> * You may not attempt to bypass accounting or security mechanisms, or attempt to circumvent protection schemes or uncover security loopholes. If you find a security loophole, you are required to report it to the Infrastructure Team immediately.<br /> * You may not use any Interlock computing resource, including the network itself, to attack, disable, or gain unauthorized access to any other computing resource either on or off the Interlock network.<br /> * All personally owned equipment connected to the Interlock network must be running an effective and currently updated anti-virus software package and must have all operating system patches installed.<br /> * You may not attempt to compromise the privacy of others. This includes, but is not limited to, the installation of traffic sniffers, key loggers, etc. or any other hardware or software designed to capture information which you are not authorized to have.<br /> <br /> <br /> <br /> ==Web Access Policy==<br /> The Production and Playground networks shall have internet access. The Warzone network shall not. Regardless of network, the following rules apply:<br /> * Use of the Internet for any unlawful purpose is prohibited. This includes, but is not limited to:<br /> ** posting, storing, transmitting or disseminating information, data or material which is libelous, obscene, unlawful, threatening or defamatory, or which infringes the intellectual property rights of any person or entity, or which in any way constitutes or encourages conduct that would constitute a criminal offense, or otherwise violate any local, state, federal, or non-U.S. law, order, or regulation;<br /> ** initiate, perpetuate, or in any way participate in any pyramid or other illegal scheme;<br /> ** participate in the collection of e-mail addresses, screen names, or other identifiers of others (without their prior consent);<br /> ** transmission of child pornography<br /> * No Production Co-located Servers are allowed, with the exception of official Interlock Rochester services.<br /> <br /> <br /> <br /> <br /> <br /> ==Data Retention Policy==<br /> Interlock Rochester does not intentionally maintain any meaningful records about network users or computers and their associated network traffic unless compelled to do so by a legal order. Any data that is collected for network diagnostic or educational purposes is destroyed as soon as the diagnostic or educational session is complete. The only permanent / semi-permanent records we maintain are:<br /> * DHCP records (stored for the duration of the DHCP lease)<br /> ** This includes a correlation between a MAC address and IP address<br /> * Captive Portal Registration<br /> ** These records may include a correlation between a user account and an associated MAC address<br /> * Door access logs<br /> ** Correlation between a user account and when they unlocked the door to our 1115 Main St E location<br /> <br /> Traffic sniffing and logging is allowed on the &quot;warzone&quot; network, however Interlock Rochester itself makes no attempt to maintain these records.<br /> <br /> <br /> <br /> We reserve the right to collect and analyze traffic on Interlock Rochester networks for the purpose of diagnosing and troubleshooting network and bandwidth issues.</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Talk:Infrastructure 2009-12-14T18:29:58Z

<p>Fvox13: /* Internet Access */</p> <hr /> <div>==Network Project==<br /> I would like to take the lead on this. I want to ask at the next meeting what people's needs are for network(s) and bandwidth [I know personally I'd like to play with some high bandwidth VoIP stuff, so the more bandwidth we can afford the better, imo] and see if what we have outlined on the [[Infrastructure]] page meshes with what everyone else was thinking. --[[User:Ben Woodruff|-- BW]] 20:20, 2 December 2009 (UTC)<br /> <br /> ----<br /> <br /> Care to tag-team this? --[[User:Fvox13|Fvox13]] 14:05, 3 December 2009 (UTC)<br /> <br /> ----<br /> <br /> Help is always appreciated, Carl mentioned wanting to help as well. --[[User:Ben Woodruff|-- BW]] 15:04, 3 December 2009 (UTC)<br /> <br /> ---- <br /> <br /> Ben, looks like you've got a good handle on this. Nicely detailed proposals. Thanks for stepping up to lead this.<br /> <br /> The chief thing that springs to mind with regard to the RFC1918 address space allocations is that consumer level devices, which I think it's safe to say we'll have on hand at one time or another, typically use at least two of those ranges preferentially. Apple Airport base stations tend to use addresses in the 10.0.0.0/8 range, and non-Apple devices often plop themselves down in the 192.168.0.0/16 range. <br /> <br /> My suggestion, then, is to use 172.16.0.0/12 range for all of our private networks. That way, if something shows a 192.168.x.y or 10.x.y.z address, we'll know right away that it's coming from something other than our stuff. <br /> <br /> In that light, I propose 172.20.x.y for the production network, partitioned further as you suggest (perhaps spacing things out by 10s in the third octet instead of by 1s, to give some room in between), 172.30.x.y for the warzone. The mnemonic I have in mind for this is that .20 is an &quot;even&quot; multiple of 10, even meaning &quot;smooth&quot; and smooth being what one wants from a production environment. In contrast, .30 is an &quot;odd&quot; multiple of 10, odd being exciting, unusual, or even dangerous, depending on one's perspective, but certainly what one would expect from a &quot;warzone&quot;. In between these two we'd have 172.25.x.y, which would be the playground--not expected to be at all dangerous, but you must be this tall to enter this ride. <br /> <br /> The 10.0.0.0/8 space is pretty big, even if Apple does use part of it. From what I recall and can tell from a quick search, they tend to use 10.0.1.x addresses. I think it might be a good convention to pick some portion of the 10.0.0.0/8 space and then to recommend that people use it for setting up their own independent test networks, eg, if they are building a private network on a single hardware host to use with a collection of virtual machines on that host. If their stuff stays on their own network, no big deal. If they screw up somehow and one of their devices ends up on our network, again, it'll be easy to tell because it is in this distinct 10.0.0.0 region. I think 10.100.0.0 would be easy to remember to use, and well away from Apple's use.<br /> <br /> Within 192.168.0.0, I've seen use all over the range. Some devices I've had use 192.168.0.x range. Some 192.168.254.x. The Linksys NSLU2 &quot;slugs&quot; use 192.168.1.77. And those are just the ones I'm familiar with and can recall off the top of my head. So, I think we just leave this for use with those devices.<br /> <br /> Anyway, that's my suggestion, based on my experience. You may have experience with devices that tend to default to 172.16.0.0 too, making this a less useful scheme, for instance. <br /> <br /> [[User:Deejoe|Deejoe]] 16:07, 5 December 2009 (UTC)<br /> <br /> ---- <br /> <br /> Thanks much for the feedback Deejoe. I like your ideas. I don't know of any devices that are using the 172.x.x.x range by default so that all sounds good.<br /> <br /> Also, Fvox13, good point about Cat6a. Lets shoot for Cat6 with the expectation that we will probably end up with a bunch of cat5e and limited cat6, which we'll probably want to use for core equipment that doesn't have other interconnects.<br /> --[[User:Ben Woodruff|-- BW]] 00:37, 6 December 2009 (UTC)<br /> <br /> ----<br /> <br /> I was looking at the subnetting layout and thought I'd chip in my two cents, for what it's worth. When addressing core devices (switches, routers, servers, and so on), I've found putting them on the subnet right before the broadcast more design-friendly. It makes writing ACLs much more easier and flexible, along with making adding new equipment to the core layer faster. Any thoughts on this? --[[User:BinaryMan|BinaryMan]]<br /> <br /> ----<br /> <br /> I have heard of doing that BinaryMan but I wasn't sure what the benefits were. --[[User:Ben Woodruff|-- BW]] 14:37, 10 December 2009 (UTC)<br /> <br /> == Infrastructure Questions ==<br /> <br /> See [[questions_for_felix]], rather that duplicating content<br /> <br /> == Internet Access ==<br /> Talking to John day about NFP discounts and possible packages for our building zone<br /> --[[User:Antitree|Antitree]] 19:27, 3 December 2009 (UTC) <br /> <br /> ----<br /> <br /> Going to present our options tomorrow night. --[[User:Fvox13|Fvox13]] 18:29, 14 December 2009 (UTC)<br /> <br /> ----<br /> <br /> == Service Suggestions ==<br /> <br /> AirPort Express wireless AP (connected to stereo system for streaming music via AirTunes?)<br /> Can also act as a USB print server if we have a printer donated (USB is not the best option... we should consider an ethernet-enabled printer (maybe someone can donate?))<br /> --[[User:Ben Woodruff|Ben Woodruff]] 06:19, 2 December 2009 (UTC)<br /> <br /> ----<br /> <br /> Production network should have a more robust AP... maybe a Meru or Cisco? <br /> <br /> ----<br /> <br /> I agree, the problem is cost. I didn't see any mentions of a better AP on the donations page, so we may be stuck with what I've got for the time being. We will also probably want to offer guest wireless access at some point, through a different SSID, which will require an additional/different AP (the new Apple equipment can do it, but this one can't)<br /> <br /> ----<br /> <br /> I have a [http://www.vandis.com/docs/meru-ap100-ds.pdf Meru AP100] and a Cisco Aironet 1200 that I will be donating --[[User:Fvox13|Fvox13]] 18:23, 8 December 2009 (UTC)<br /> <br /> ----<br /> <br /> Does anyone know of a &quot;good&quot; captive portal type system like start.rit.edu or BlueSocket? I want something that can register MAC addresses with a DHCP server if proper credentials are supplied (auth w/ LDAP). Bonus points if it has optional static IP registration for servers and host management (remember which MACs belong to which users) --[[User:Ben Woodruff|-- BW]] 20:06, 8 December 2009 (UTC)<br /> <br /> ----<br /> <br /> I'm against captive portals, (Looks like you sort of agree, the way you said '&quot;good&quot; captive portal'), but [http://m0n0.ch/wall/ Monowall] might work --[[User:Fvox13|Fvox13]] 20:52, 8 December 2009 (UTC)<br /> <br /> ----<br /> <br /> You should be able to use something like PacketFence I would thing. That has an included registration system, so that the admin doesn't have to do as much. Here is a link to its [http://www.packetfence.org/tour/features.html Features]<br /> <br /> --[[User:Cmd3187|Cmd3187]] 21:11, 8 December 2009 (UTC)<br /> <br /> ----<br /> <br /> [http://nocat.net/ NoCatAuth] was developed for open-ish or community wireless networks. Might fit the bill. --[[User:Berticus|Berticus]] 21:24, 8 December 2009 (UTC)<br /> <br /> ----<br /> <br /> I like the looks of pfSense and PacketFence.<br /> Does anyone want to take charge of setting up the LDAP server and RADIUS authentication? It's something I'd like to observe on.<br /> --[[User:Ben Woodruff|-- BW]] 14:40, 10 December 2009 (UTC)<br /> <br /> ----<br /> <br /> I can probably setup a freeradius instance pretty easily. Though I will need to learn how to integrate it against openLDAP, since I have usually just set it up against shadow. I'll setup a sample one at home as a VM for now. Any preferences as to what VM container I use? I currently can work with QEMU, VMWare, Xen, KVM and Solaris Zones.<br /> --[[User:Cmd3187|Cmd3187]] 16:16, 11 December 2009 (UTC)<br /> <br /> ----<br /> <br /> I think VMWare is sort of the de facto option. As long as we can eventually convert it in to a VMWare image eventually that'd be cool. But whatever works.<br /> --[[User:Ben Woodruff|-- BW]] 17:51, 11 December 2009 (UTC)</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Meetings 2009-12-13T18:52:41Z

<p>Fvox13: </p> <hr /> <div>= Meeting Stream =<br /> * As of 11/17/09 the meetings will now be streamed live, so that if you can't attend physically, you can at least catch up with whats going on in the group - [http://www.ustream.tv/channel/rochester-hackerspace-meetings UStream.tv - Rochester Hackerspace]<br /> ** You'll need to login in order to chat. Integrates with facebook connect for auth.<br /> <br /> = Minutes =<br /> == December 15, 2009 ==<br /> * Agenda<br /> ** ISP Options: Steve S.<br /> <br /> == December 8, 2009 ==<br /> * Attended: Mark, Brian, Steve, Dan, Andrei, Joe, Carl, Carmen, Sneha, Matt, Ben, Bryan, Josh [...]<br /> * Agenda:<br /> **7: Introductions and updates, go over [http://wiki.interlockroc.org/index.php?title=MIBS_Simplified_Rules_of_Coordinated_Consensus_through_Chaos MIBS meeting rules]<br /> **7:30: Hackerspace Presentation: Mark<br /> **8: Move to new space<br /> * Discussed:<br /> ** Introductions<br /> ** Officers announced. Mostly people on the lease or incorporation paperwork.<br /> ** Mark presented a bit on MIBS rules<br /> ** [http://docs.google.com/present/view?id=dnbv9rr_42ft4q8vff Hackerspace presentation]<br /> ** Sneha discusses public outreach activities<br /> * Caravan to the temp space for discussion and beverages<br /> <br /> == December 1, 2009 ==<br /> * Attended: Carl, Ben, Jimmi, Kristina, Steve, Ashley, Andrei, <br /> * Discussed: <br /> ** Bylaws went over a lot of the details. <br /> ** Bylaws: Decided to have an official meeting once a month unless otherwise requested <br /> ** Discussed dues<br /> ** updated everyone on lease signing status<br /> ** Ashley updated us on documents for incorporation<br /> ** Voted on whether or not to get the temp space or skip it and wait for the real space. Agreed to get the temp<br /> ** Introduced new members discussed goals of the organization<br /> * Action Items:<br /> ** Directors: Sign lease and setup temp space<br /> <br /> == November 23, 2009 ==<br /> <br /> * Attended<br /> ** Mark, Brian, Ashley, Alan, Sneha, Carmen, Carl, Bryan, Ben, Jeremy, Rich<br /> * Video: [http://www.ustream.tv/recorded/2628387 Part 1]<br /> * Discussed<br /> ** Basement space at 1115 Main Street<br /> *** $390 + electricity<br /> *** Ready by February<br /> ** Temporary space available immediately<br /> *** $280 + electricity<br /> ** Network connectivity options<br /> *** Business class roadrunner $79 a month<br /> *** Netsville<br /> ** Dues<br /> *** Start payment 1st of December<br /> *** Application form<br /> ** Business checking accounts and accounting<br /> ** First Month's rent<br /> ** Logos<br /> ** Wiki/Website stuff<br /> *** maybe looking for a wiki with better ACLs<br /> *** decision to departmentalize functions - wiki, website, blog, etc<br /> ** Dues through paypal for first month<br /> ** Bryan shows his illuminated bidness card<br /> ** Discussion about who will be the incorporators<br /> ** Presentation ideas for future meetings<br /> ***Python intro class<br /> ***Wordpress tutorial<br /> ***Software Defined Radio<br /> **Ham radio discussion<br /> ** Future meetings may have first 1/2 hour as business-related matters, come afterwards if you're not interested in the nitty gritty of forming the space<br /> * Actions<br /> ** Mark: Setup paypal account and email address<br /> ** Mark: Put together a membership package<br /> ** Alan: Put membership form online<br /> ** Goal: Have membership dues on December 1st<br /> ** Goal: Sign lease on Monday November 30th<br /> <br /> == November 17, 2009 ==<br /> * Attended: Mark, Sneha, Carmen, Ashley, Alan, Jimmi, Krystina, James, Justin, Robert, Joe, Ben, JP, Brian, (David)<br /> * Recordings - [http://www.ustream.tv/recorded/2580888 Part 1]- [http://www.ustream.tv/recorded/2581335 Part 2]<br /> * 1st meeting streamed online (ustream)<br /> * Decided on Interlock as a group name.<br /> ** interlocroc.net, .com and .org domains have been acquired<br /> * Discussion about three potential locations<br /> ** Griffith Ave<br /> *** 3000/$1500 a month<br /> *** No security deposit<br /> *** Utilities = $200 a month<br /> *** A bit too pricey<br /> ** E Main St<br /> *** 1000/$450<br /> *** 2000/$725<br /> *** Utilities = $150 a month<br /> ** Village Gate<br /> *** 500/$325<br /> *** Utilities = $60 a month<br /> * Talking about the budget<br /> ** Would prefer it to be about $35, but it will probably be higher at first until we get more members<br /> ** Looking at 501.c3<br /> ** Contacts in Buffalo chapter could be useful with this business setup<br /> ** Dues<br /> *** $50 - Normal<br /> *** $35 - Student<br /> * Trip to Buffalo Chapter<br /> ** Visit to see what they have there<br /> ** After thanksgiving, on the weekend<br /> *** Important for sponsorships<br /> <br /> Action Items For Next week:<br /> * Form a holding company (LLC, S-Corp) to get a bank account<br /> * Focus on making the Main St. building work (talk to Felix, discuss details, find temp location)<br /> * Plan for best way to form an NFP<br /> * Create a focus group for developing a website<br /> <br /> ==November 11, 2009==<br /> *Location: Spot Coffee<br /> *Attended:<br /> **Mark, Brian B., PT, Sneha, Dan, Carl, Andrei, Bryan, Josh, Ashley, Alan, Carmen<br /> *Discussed:<br /> **Summary of goals thus far, for new attendees.<br /> **Updates from members about spaces scouted, etc. <br /> ***Sneha: 1000 square feet, 600 a month, Portland Ave., with storefront<br /> ***Look into spaces near the Public Market? High rent for RR55 ($900)<br /> ****Other spaces besides the refurbed railroad area? Space above cheese shop area?<br /> **Introductions<br /> **Show and Tell<br /> ***Bryan<br /> ****guitar hacks<br /> *****tuning geegaws<br /> *****patents<br /> ***Andrei<br /> ****[http://www.makershed.com/ProductDetails.asp?ProductCode=MSBM brain machine kit]<br /> ****circuit bent toy horn<br /> ***Mark<br /> ****lockpicking sets<br /> ****garmin gps units, wardriving discussion<br /> *****obligatory [http://www.imdb.com/title/tt0086567/ Wargames] shoutout<br /> ****defcon badges<br /> ****bump key discussion<br /> ***Brian B.<br /> ****bookbinding<br /> ****sketchbooks<br /> ****[http://www.ponoko.com/ Ponoko] business cards<br /> ****[http://www.ponoko.com/ Makerbot] contact: sample print will be mailed out this weekend, hackerspace discount is available<br /> ****laser cutting, found [http://www.classact.net/ Class Act Engraving] in Akron, NY. Epilog laser reseller<br /> ***Carmen<br /> ****suitcase computer<br /> **Random discussion<br /> ***Kegerator w/ Nagios monitoring<br /> <br /> *Actions<br /> **None specified<br /> <br /> == November 6, 2009 ==<br /> * Location: Spot Coffee<br /> * Attended:<br /> ** Mark, Carmen, Sneha, Ben, Brian B, Stephen, Bryan S, Andrei, Tom, Josh, David, Karl<br /> * Discussed:<br /> ** announcements from last week - flyers, wiki<br /> ** attendees' backgrounds and vision for the space<br /> ** rough plan of action re: naming, incorporation, non-profit filing<br /> ** future meeting ideas, including demos and presentations<br /> ** (EDIT)<br /> * Actions:<br /> ** contribute to the wiki<br /> ** think of names<br /> ** (EDIT)<br /> <br /> == October 28, 2009 ==<br /> * Location: Spot Coffee<br /> * Attended: Mark, Jeff, Carmen, Brian, Alan, Eric, Joe, Andrei, Bryan, Greg, <br /> * Discussed:<br /> ** ideas<br /> ** made flyers<br /> ** other spaces<br /> ** meet and greet<br /> * Actions:<br /> ** Mark: setup a wiki<br /> ** Mark: print out flyers<br /> <br /> == October 21, 2009 ==<br /> * Location: Spot Coffee<br /> * Attended:<br /> ** Jerel, Matt, Mark, Jeff, Greg, Jimmi, Krystina<br /> * Discussed:<br /> ** meet and greet<br /> ** buffalo hackerspace<br /> * Actions:</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Projects 2009-12-13T18:51:23Z

<p>Fvox13: </p> <hr /> <div>== Ideas for projects==<br /> moved to [[ideas]]<br /> <br /> == [[Hackerspace Security System]] ==<br /> <br /> == Reprap/Makerbot Build ==<br /> Description: Berticus really wants to tinker with 3d printing, and thus desires access to either a Makerbot or the next generation Reprap Mendel.<br /> <br /> Details: [http://makerbot.com/ Makerbots] can be purchased for $750 or $950. The higher price reflects some premium features, mainly pre-assembled electronics, a power supply, and some extra plastic filament. Bots are currently rather backordered. Mendel parts are impossible to find. There seem to be no kits out there for the non-extruded parts (threaded rod, etc.), so even if we can find somebody to print us the plastic bits, it'll still be a bit of a pain to get everything together. Right now a Makerbot is probably the way to go, and we can use that to print out the Mendel parts to make a second bot for experimentation (developing new print heads and such).<br /> <br /> === Comments ===<br /> <br /> <br /> == Ashley's Silly Web Projects ==<br /> BedBugsHotels.com &lt;- looking to collab with someone to build something like bedbugregistry.com but not as lame, using googlemaps. started the site in rails, but have not got very far with this. pretty sure there's traffic waiting for a well developed site along these lines, and it could be fun?<br /> <br /> hotpinkwedding.com &lt;- no one is going to be interested in this topic, per se. But I'm interested in using and learning about different techniques to boost serp via experimentation, if anyone is into that. 500-600 unique visitors a month currently.<br /> <br /> simplerochester.com &lt;- websites hosted on AWS. Looking to redevelop the business model in a unique way and mess around with marketing.<br /> <br /> <br /> == Electronics, parts, and keeping a bunch of stuff in stock ==<br /> Everyone who can afford it should buy one of each of these two boxes, and donate its contents to the space... plus we'll learn a *lot* just from sorting through the contents!<br /> * [http://www.goldmine-elec-products.com/prodinfo.asp?number=G17225 Ginormous Surprise Box]<br /> * [http://www.sciplus.com/recommend.cfm/recommendid/3501 Surprise Box of Science] (sounds like a Bill Nye thing... :-) )<br /> <br /> == INTERLOCK LED Windows ==<br /> Description: The windows at the temp space and the final space have double pane security glass. Light is diffused but one can imagine the possibilities<br /> <br /> Ideas:<br /> * Treat each pane as a pixel for pong, tetris, animated gifs, etc<br /> * Spell INTERLOCK in the glass<br /> * Game of Life pattern<br /> <br /> === Comments ===<br /> How many &quot;pixels&quot; do we have to work with? I seem to recall 3 high, maybe 12-16 long with a window interrupting four-ish blocks in the center. Letters are pretty tricky with just three vertical pixels. More abstract light patterns would be really cool though. --[[User:Berticus|Berticus]] 20:47, 8 December 2009 (UTC)<br /> <br /> Problem: our windows are obscured by shrubbery. So unless we're lighting them up from the outside for our own enjoyment within the space, this idea may be DOA. --[[User:Berticus|Berticus]] 19:42, 10 December 2009 (UTC)<br /> <br /> <br /> == Interlock Floor Coverings ==<br /> Problem: The floor is concrete, which while suited to welding, etc, is ugly and non-l33t.<br /> Solution: Come up with one or more floor coverings.<br /> <br /> Ideas:<br /> * LED Disco Dance Floor like [http://www.scotttorborg.com/disco-dance-floor/ this one] at MIT<br /> ** Maybe with an option to have solid colors or something less crazy, so we can use it more often than not<br /> * Section off part of the floor using 2x4s and put dirt and grass there (how do we grow grass with no light?)<br /> * Astroturf<br /> <br /> === Comments ===<br /> <br /> <br /> <br /> <br /> == Official Friends of Interlock trophy ==<br /> Description: When we visit other hackerspaces or form partnerships with other organizations, it would be cool to give them something that came from the hackerspace. The idea being that it's hand made, geeky, and shows off the Interlock logo in some way. <br /> <br /> Ideas:<br /> * That was easy button re-recorded to say a private message and repainted to have our logo<br /> * Robot of some kind (for Felix)<br /> * Draudio Pen<br /> <br /> === Comments ===<br /> How about some sort of abstract object trophy, that's actually just a piece of a larger objects. The different hackerspaces that received them would have to get together to put the final &quot;trophy&quot; together. Or perhaps they'd all combine into Voltron or Captain Planet. Some such. Or, instead of getting physically together perhaps all the spaces would 3d scan their objects and combine them that way. There'd have to be something extra to thwart that... electronic contacts in each piece that &quot;networked&quot; the larger object perhaps. Ramble complete. --[[User:Berticus|Berticus]] 20:52, 8 December 2009 (UTC)<br /> <br /> == Interlock Dumpster Diving Crew ==<br /> Description: A group of people willing and able to drive around looking for things to pick up on garbage day or legal dumpsters to dive into. <br /> <br /> Members:<br /> * Brian<br /> * Mark<br /> * Josh<br /> * Jimmi<br /> <br /> Targets:<br /> * [http://tinyurl.com/ydsasyh RIT Boneyard]<br /> * RIT dumpsters all across campus after students move out (May of each year)<br /> <br /> <br /> == Interlock as an ISP ==<br /> moved to [[ideas]]</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Ideas 2009-12-13T18:44:22Z

<p>Fvox13: /* Membership Benefits */</p> <hr /> <div>This page can be anything. Please don't delete other peoples ideas and use the discussion tab at the top. <br /> <br /> == Structure ==<br /> see [[organization]]<br /> <br /> == Security ==<br /> * We need a way to determine who has access to what (no system should be accessible to only a single administrator)<br /> * W also need a secure way to share login information<br /> ** PGP/GPG is a popular option but OS X support is severely lacking<br /> <br /> == Membership Benefits ==<br /> * local discounts<br /> ** Goldcrest Electronics<br /> * 24x7 access to space<br /> * secret handshake<br /> * free or discounted admission to special events and classes<br /> * colo space (NOT for production sites)<br /> * very high speed internet<br /> * Google Apps account at interlockroc.org<br /> <br /> == Events ==<br /> * Weekly open house<br /> * Flash mobs<br /> * Computer repair clinic<br /> * LAN parties<br /> * Parts swap<br /> * Group partnerships<br /> ** Rochester 2600<br /> ** Rochester Hackers<br /> ** Make Club<br /> ** OWASP<br /> * Geeky art exhibitions and gallery<br /> * Bike rides<br /> * Trips to nearby hackerspaces<br /> * Rake leaves<br /> * Kids robotic group<br /> * Bike repair<br /> * Computer repair<br /> * We sponsor events<br /> * United Rochester Hackers Convention(Multi-group uber meeting with OWASP, SPARSA, Geek Rochester, Pythonistas, Rochester Hackers, Rochester 2600, Make Club)<br /> * Lightning talks - 5 minutes to talk on one subject and move on<br /> * Geek prom<br /> <br /> == Classes ==<br /> * Programming<br /> ** Python<br /> ** Perl<br /> ** Ruby<br /> ** JAVA<br /> ** C++<br /> * Soldering<br /> * Arduino<br /> * Bookbinding? (Brian B. knows a bit about this)<br /> * 3d printing, CNC routing, Pen plotter tinkering<br /> * Screen Printing<br /> * Homebrewing (beer)?<br /> * Bike repair and modding ([http://www.ladyada.net/make/spokepov/ Spoke POV] kits, DIY headlamps)<br /> * DIY Instruments (cigar box ukulele, [http://www.vimeo.com/3913619 diy piezo pickups], theremins)<br /> * Photography <br /> ** controlling dSLRs via computers<br /> ** writing scripts for [http://chdk.wikia.com/wiki/CHDK CHDK] <br /> ** alternate firmware for many point and shoot digicams<br /> * Consumer router &quot;hacking&quot; (dd-wrt or tomato firmware flashing, how to optimize settings for your bittorrenting pleasure)<br /> * Programming in [http://processing.org/ Processing], and interfacing with the Arduino<br /> * Welding<br /> * Amateur radio related topics<br /> * Network Security/Forensics<br /> * Visual Data Analysis [http://secviz.org Secviz.org]<br /> * Linux (maybe partner with the Linux User Group of Rochester (LUGOR)<br /> * Learning about home renovation projects<br /> * Kids hardware classes (bristlebots)<br /> * Metasploit<br /> * VMware<br /> = Project Ideas =<br /> See Also: [[projects]]<br /> <br /> == Random Thoughts ==<br /> * I saw this high speed camera hack on wired science. It think this could be a cool project that wont take too long. There are detailed [http://www.pbs.org/kcet/wiredscience/story/68-high_speed_photos.html instructions on how to do this hack].<br /> * [http://www.evilmadscientist.com/article.php/bristlebot Bristle Bots]<br /> * [http://graffitiresearchlab.com/?page_id=6 Throwies]<br /> * [http://www.hactivist.com/flashpoint/ Flashpoint Cameras] - project a message on a wall for cheap<br /> * [http://www.waveprotocol.org/ Google Wave Server] - Openfire based?<br /> * Xen Cluster<br /> ** [http://www.oracle.com/us/technologies/virtualization/index.htm Oracle VM]<br /> ** [http://www.convirture.com/ ConVirt]<br /> * Kegerator - With a notification system for temp or something like that. Maybe via Twitter<br /> * Screenprinted T-shirts ([http://magicalnihilism.com/2009/11/07/get-excited-and-make-things/ This design] has been released for free. Perhaps put the hackerspace name on the back)<br /> * Capture The Flag InfoSec game<br /> * Old School BBS<br /> * Practically everything on [http://www.hackaday.com Hackaday] would be fair game<br /> ** [http://hackaday.com/2009/12/11/bender-keg-cooler/ Bender Keg Cooler]<br /> <br /> <br /> == Interlock as an ISP ==<br /> There has been some debate about this, especially since we're doing the whole non-profit thing, but a non-profit *is* allowed to make money, as long as certain rules are followed.<br /> <br /> Basically, any Internet connection worth getting is going to be mucho expensive, and rather than get 30 new members just to pay for the Internet, it would make a lot of sense to resell it. Based on how expensive RoadRunner is in this building (probably what most of our neighbors have), and how crappy the speed is, I think we could undercut their price and still make it worthwhile to do this. I really want to run a fiber line into our space... the Internet is pretty much at the core of a lot of what we're doing, and we don't want it to be the weak link. But the options are looking like a.) Get 30 more members b.) Resell our connection or c.) Settle for something that is a lot slower than what most of us have at home.<br /> <br /> === Comments ===<br /> <br /> One objection raised for this was that we would be on the hook to provide 24x7 support for our &quot;customers&quot;. Fortunately our customers are mostly business types that don't work in the middle of the night. We would still require some kind of rotating schedule to carry a notification device (used to be a pager) and be available for support calls. Luckily there would not be many calls.<br /> <br /> The other big objection is liability. There are laws dictating how much we need to spy on our customers and liability issues if we spy too much. The legal aspects would require in depth investigation to make sure we are &quot;safe&quot;. Someone thought dealing with court orders and subpoenas might be cumbersome but after having to deal with a couple they aren't that tedious or scary. What was scary was thinking one of my customers was into child porn. I don't think he really was but it makes you wonder.<br /> <br /> All in all it might be reasonable way to subsidize our internet addiction. I don't expect we would get that many customers even if we offer more for less. Most people don't want to change unless there is a real problem with their current provider. And they would only consider us if they thought they could trust us. Personal contact is a big plus in that respect. A flyer in the hall or under the door won't convince anyone and pushing &quot;sales&quot; calls will turn people off. The best way to gain customers is to be a good neighbor and offering good unbiased advice and helpful suggestions. Free tech support is good too but you have to be careful to strictly limit it or you become their unpaid IT department.<br /> --[[User:Cws|Cws]] 22:16, 12 December 2009 (UTC)</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Bylaws 2009-12-13T18:32:48Z

<p>Fvox13: /* Article VII: Dissolution */</p> <hr /> <div>Bylaws based on [http://wiki.hacdc.org/index.php/Bylaws HacDC]'s bylaws<br /> <br /> By law, this is the core governing document of Interlock Rochester. These bylaws were written to maximize the direct power of the membership as a whole, reducing the power of [[Board of Directors]] and the officers to as ceremonial and functional a role as possible.<br /> <br /> The Bylaws in effect are kept XXXXXXXXXX<br /> <br /> Amendments are handled as specified in [[#Article VII: Amendments | Article 7]]<br /> <br /> '''These Bylaws were a draft and waiting to be approved by the [[Incorporators]] ''' after consulting with prospective charter members.<br /> <br /> == Article I : Why We Exist ==<br /> <br /> === Section 1: General Purposes ===<br /> Interlock Rochester is a Not For Profit organization that focuses on providing a facility for its members to use to develop their personal interests in science, technology, and art in a collaborative, social environment. Projects include electronic engineering, computer programming, information security, wood working, crafts, digital art, technological research, and much more. The organization's space could be seen as a workshop, art studio, or open community lab. <br /> <br /> === Section 2: Specific Purposes ===<br /> Subject to and within the limits of Section 1, the corporation shall:<br /> # Provide a physical location that strives to afford the educational, technological, and collaborative requirements of its members<br /> # Collaborate on all forms of technology, culture, art and craft in new and interesting ways.<br /> #. Further the knowledge and experience of the public through talks, demonstrations, workshops, and public seminars pertaining to member crafts, skills, inventions, and discoveries.<br /> # Apply the results of its work to specific cultural, charitable and scientific causes.<br /> # Freely share its research and discoveries, using what is learned to teach others.<br /> # Recruit and develop talented members dedicated to these purposes.<br /> <br /> == Article II: Who We Are == <br /> <br /> === Section 1: Designation of Membership Classes ===<br /> <br /> Interlock Rochester has a voting membership class and a non-voting membership class.<br /> <br /> === Section 2: Voting Membership Class Qualifications ===<br /> <br /> Any person who supports the purposes laid out in Article I of these bylaws is qualified to become a member.<br /> <br /> === Section 3: Voting Membership Class Election ===<br /> <br /> Any member may nominate a qualified person to be a voting member. Any eligible person may be elected as a voting member at any regular meeting upon payment of their first periodic dues and visual approval of all members present. '''For purposes of these bylaws, all persons listed as [[Articles of Incorporation#Eighth Article : Names and Address of Members of the Initial Board of Directors | initial directors]] on the [[Articles of Incorporation | Articles of Incorporation]] shall be considered the initial voting members.'''<br /> <br /> === Section 4: Voting Membership Dues ===<br /> <br /> The amount, payment period, due date and acceptable methods for collection of dues shall be reviewed each year at the annual meeting. A majority vote of the members at any meeting may change the procedure and terms for payment of dues. Member dues may be waived for a three month period due to financial hardship or relocation by written petition signed by more than three quarters (3/4ths) of the Board of Directors. Payment of dues may be waived for any other reason only by voting members at a duly called meeting.<br /> <br /> === Section 5: Voting Membership Rights and Responsibilities ===<br /> <br /> Each voting member shall have an equal right to voice their opinion and vote their preference or abstain from voting in the affairs of the corporation. Each voting member shall exercise only one vote for each decision before the corporation. Votes should be exercised in person or via verifiable form of communication. Each voting member shall have reasonable inspection rights of corporate records. Each voting member shall be responsible for timely payment of dues, providing their current address, contact information, and preference for electronic receipt of communications. Each voting member is responsible for continuing to support the purposes of the corporation.<br /> <br /> === Section 6: Voting Membership Resignation and Termination ===<br /> <br /> Any voting member may resign by filing a written resignation with the Secretary. Resignation shall not relieve a voting member of unpaid dues or other monies owed. Voting membership may be suspended for non-payment of dues by the Treasurer. Any suspended voting member may restore their membership 90 days after suspension upon payment of dues owed and payable through one month beyond the end of the suspension period, or upon the granting of a dues waiver as outlined in Section 4. Voting membership may also be terminated for any reason by written petition signed by more than three quarters (3/4ths) of the voting members.<br /> <br /> === Section 7: Non-Voting Membership ===<br /> <br /> For fundraising and honorary purposes, the Treasurer may declare the qualifications for and appointment of non-voting members. Non-voting memberships and membership titles are subject to voting member approval. Non-voting members do not have the right to vote in affairs of the corporation nor do they have any responsibilities towards it. All other rights and responsibilities of non-voting members shall be explicitly stated by the Minister of Finance and subject to voting member approval, &lt;s&gt;except for the right to one (1) vegan chocolate chip cookie or a vegan baked good of equal or lesser nutritional value upon becoming a non-voting member.&lt;/s&gt;<br /> <br /> == Article III: How we meet ==<br /> <br /> === Section 1: Regular Meetings ===<br /> <br /> Regular meetings of voting members shall be held every First Tuesday at 19:30 local time at the registered office. A different meeting place may be designated by written petition signed by more than three quarters (3/4ths) of voting members. Regular meetings shall not take place on the day before, upon, or after a federal holiday unless specifically approved at the prior regular meeting or annual meeting. Meetings shall not take place on the day of a closure declared by the Office of Personnel Management.<br /> <br /> === Section 2: Annual Meetings ===<br /> <br /> An annual meeting of all members shall take place sometime in October, November, or December. The President shall select the date, time and place no later than November 30th of each year. The date, time and place of the annual meeting must be posted in the registered office and submitted to members electronically at least two weeks prior to the annual meeting. A petition signed by more than three quarters (3/4ths) of voting members and submitted to the Board of Directors before December 15th may specify a new date, time and place for the annual meeting. At the annual meeting, the voting members shall elect the Board of Directors, review and vote on the standing rules and policies of the corporation, receive reports on the activities of the corporation, approve the budget and determine the direction of corporation in the coming year.<br /> <br /> === Section 3: Special Meetings ===<br /> <br /> A petition presented to all voting members and signed by one third (1/3rd) of voting members may call a special meeting. Such a petition must include the date, time, place and agenda of the special meeting.<br /> <br /> === Section 4: Notice of Meetings ===<br /> <br /> The time and place of upcoming meetings shall be conspicuously posted at the registered office and electronically sent to all voting members. No notice is required for a regular meeting. Special meetings require 72 hours notice considered delivered only when all voting members are personally notified and given an opportunity to sign a special meeting petition.The agenda of the next upcoming meeting and minutes of the previous meeting shall be posted at the registered office and electronically submitted to all voting members at least 72 hours prior to any meeting.<br /> <br /> === Section 5: Quorum ===<br /> <br /> At a duly called meeting, at least 25% (one quarter) of the entire voting membership shall constitute a quorum.<br /> <br /> === Section 6: Voting ===<br /> <br /> When a quorum is present, all issues, except when otherwise specified in these bylaws, shall be decided by affirmative vote of more than 50% (one half) of the voting members present.<br /> <br /> === Section 7: Conduct of Meetings === <br /> <br /> All meetings shall follow the [[MIBS Simplified Rules of Coordinated Consensus through Chaos]] as approved at an annual meeting.<br /> <br /> == Article IV: The Officers ==<br /> <br /> === Section 1: Role, Number, Qualification, Term and Compensation ===<br /> <br /> There shall be four officers consisting of a President, Vice President, Secretary, and Treasurer. Each officer must be a voting member and each officer shall serve from the time of their election until their successor is elected and qualifies. No officer may serve more than 3 consecutive terms. No officer shall be compensated for their service as an officer, though the corporation may provide insurance and indemnity for officers as allowed by law.<br /> <br /> === Section 2: Duties of the President ===<br /> <br /> The President shall preside over all meetings or designate an alternate, attempt to achieve consensus in all decision-making, ensure the membership is informed of all relevant issues, and serve other duties of a President as required by law or custom.<br /> <br /> === Section 3: Duties of the Vice President ===<br /> <br /> The Vice President shall be primarily responsible for the information systems and communication processes of the corporation, coordinate the teams that manage and design those systems, draft policies and procedures for information system use, ensure effective communication and information exchange within the corporation, and serving all other duties of a Vice President as required by law or custom, including acting when the President is unable or unwilling to act. The Vice President shall assist the President in organizing meetings of the membership. He or she is responsible for enforcing the rules of meeting procedure as detailed in this documents. The Vice President is also responsible for providing notice of all meetings of the members and of the board of directors, pursuant to these bylaws.<br /> <br /> === Section 4: Duties of the Secretary ===<br /> <br /> The Secretary shall be responsible for membership records including membership and board meeting actions and petitions, sending out meeting announcements, posting and distributing copies of membership meeting minutes and relevant meeting agendas to the membership, assuring that corporate records are maintained, &lt;s&gt;assigning MIBS points to worthy members for a job well done&lt;/s&gt; and serving all other duties of a Secretary as required by law or custom.<br /> <br /> === Section 5: Duties of the Treasurer ===<br /> <br /> The Treasurer shall be custodian of corporate funds, collect dues, make a financial report for each meeting, assist in the preparation of the budget, '''develop fundraising plans''', make financial information available to members and the public, '''sneer at members who do not pay dues in a timely fashion and serve all other duties of a Treasurer as required by law or custom.'''<br /> <br /> === Section 6: Duties of the Officers as whole to provide an Annual Report ===<br /> <br /> The Ministers must prepare an annual report to be distributed at the annual meeting. The report should chronicle the activities of the corporation, including specific narratives on the corporation's work, the corporation's annual financial statements, relevant legal filings, and relevant copies of the organization's district and federal tax returns.<br /> <br /> === Section 7: Officers are Directors ===<br /> <br /> The Officers shall also serve as bona-fide directors on the Board of Directors. Election, resignation, removal and vacancies of the Ministers are handled in accordance with procedures laid out in Article V.<br /> <br /> == Article V: The Board of Directors ==<br /> <br /> === Section 1: Role, Size, Term and Compensation ===<br /> <br /> The board of directors shall consist of the four Officers as defined in Article IV and two at-large directors, all of whom are considered directors for the purposes of this article. All directors must be voting members of the corporation. Each director shall serve from the time of their election until their successor is elected and qualifies. No member may serve more than 3 consecutive terms on the board of directors. No director may be compensated for their service as a board member, though the corporation may provide insurance and indemnity for board members as allowed by law.<br /> <br /> === Section 2: Meetings ===<br /> <br /> The Board of Directors shall meet when necessary, provided all voting members receive notice sent electronically at least five business days prior to the meeting. All voting members may attend a meeting of the board of directors. The notice shall give the time, place, reason for calling the meeting and the agenda for said meeting. Notices shall be conspicuously posted at the registered office and electronically distributed to all members at least five business days prior to a meeting. Minutes shall follow the standing rules for meetings as approved at an annual meeting. Minutes of each board meeting shall be conspicuously posted at the registered office and electronically distributed to members within 48 hours. Minutes shall be considered approved when signed by all board members in attendance.<br /> <br /> === Section 3: Elections ===<br /> <br /> Each Voting Member present shall be given an opportunity to be a candidate for each officer position and each at-large director position on the board. If there is more than one candidate for an officer position, the candidate which obtains the highest number votes from voting members present shall be elected. If there are no candidates for an officer position, the outgoing officeholder may, if eligible, elect to serve another term or select any willing member to serve in that position. &lt;s&gt;If there is only one candidate for an officer position, the outgoing officeholder must perform a song chosen by the incoming officeholder at the karaoke bar of the incoming officeholder's choice.&lt;/s&gt; If fewer than two members are candidates for at-large director, those candidates are automatically elected and the remaining vacancies shall be filled by a random process selected by the outgoing Coordinator in Chief. If more than two members are candidates for at-large director, each voting member present shall rank the candidates. The two candidates obtaining the highest preferences from voting members present shall be elected. &lt;s&gt;If exactly two members are candidates for at-large director, the outgoing chairperson must immediately dance in a reasonably silly manner for at least two minutes.&lt;/s&gt;<br /> <br /> === Section 4: Quorum ===<br /> <br /> Two thirds of board members at a duly called board member meeting shall constitute a quorum.<br /> <br /> === Section 5: Voting ===<br /> <br /> All issues, except when otherwise specified in these bylaws, shall be decided by affirmative vote of more than half of the directors present at a duly held meeting.<br /> <br /> === Section 6: Resignation, Termination and Vacancies ===<br /> <br /> Any officer or director may resign by filing a written resignation with the Secretary or two other board members. An officer or at-large director may be terminated in their role by written petition signed by more than three quarters (3/4ths) of the voting membership. Vacancies on the board shall be filled at the next regular meeting using the applicable process outlined in Section 3.<br /> <br /> == Article VI: Committees ==<br /> <br /> &lt;s&gt;On or before September 30, the members shall nominate and approve an audit committee consisting of three voting members who are not members of the board of directors and have not served as a director for 180 days prior to appointment. The audit committee shall have full inspection rights to the affairs and documentation of the corporation. No audit committee shall be convened if the corporation has fewer than nine voting members. Otherwise, the board or voting members may not create committees or delegate their authority.&lt;/s&gt;<br /> <br /> <br /> == Article VII: Dissolution ==<br /> In the event of the dissolution of Interlock Rochester, the remaining members shall vote on beneficiaries to receive all remaining assets of the organization.<br /> <br /> == Article VIII: Amendments ==<br /> <br /> These bylaws may be amended only when an amendment proposal petition is approved at a membership meeting and signed by more than three quarters (3/4ths) of voting members. Written notice of such petition must be submitted electronically to all members and delivered to all members of the corporation physically in person or by registered mail to take effect.</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Projects 2009-12-11T18:07:37Z

<p>Fvox13: /* Ideas for projects */</p> <hr /> <div>== Ideas for projects==<br /> * I saw this high speed camera hack on wired science. It think this could be a cool project that wont take too long. There are detailed [http://www.pbs.org/kcet/wiredscience/story/68-high_speed_photos.html instructions on how to do this hack].<br /> * [http://www.evilmadscientist.com/article.php/bristlebot Bristle Bots]<br /> * [http://graffitiresearchlab.com/?page_id=6 Throwies]<br /> * [http://www.hactivist.com/flashpoint/ Flashpoint Cameras] - project a message on a wall for cheap<br /> * [http://www.waveprotocol.org/ Google Wave Server] - Openfire based?<br /> * Xen Cluster<br /> ** [http://www.oracle.com/us/technologies/virtualization/index.htm Oracle VM]<br /> ** [http://www.convirture.com/ ConVirt]<br /> * Kegerator - With a notification system for temp or something like that. Maybe via Twitter<br /> * Screenprinted T-shirts ([http://magicalnihilism.com/2009/11/07/get-excited-and-make-things/ This design] has been released for free. Perhaps put the hackerspace name on the back)<br /> * Capture The Flag InfoSec game<br /> * Old School BBS<br /> * Practically everything on [http://www.hackaday.com Hackaday] would be fair game<br /> ** [http://hackaday.com/2009/12/11/bender-keg-cooler/ Bender Keg Cooler]<br /> <br /> == Hackerspace Security System ==<br /> <br /> Also see [[Infrastructure#Physical Security]]<br /> <br /> Description: The space will need a better way to keep track of who has access to come and go as they please. Keys are not an option. Key fob systems and other RFID technologies offer a way to control what a person has access to. <br /> <br /> See: http://www.instructables.com/id/Arduino-RFID-Door-Lock/<br /> <br /> Details: Construct a system that uses an RFID reader to grant access to the main door. The fob is also used to open other areas of the space depending on the member. OPTIONAL: build in a second factor authentication system. OPTIONAL: Construct a man trap so only one member can enter at a time. <br /> * RFID reader<br /> * fob<br /> ** [http://www.yubico.com/products/yubikey/ Yubikey] could be used with an old laptop on the cheap<br /> * electronic locks<br /> * server to manage ACLS (LDAP server? See [[Infrastructure#Network]])<br /> * second factor authentication system (biometrics, pin pad, TBD)<br /> <br /> === Comments ===<br /> RFID tags sound great to me. A swipe card would be tolerable, but I don't think those are too robust (not that RFID are perfect). A man trap sounds like a space-hog to me, and a little bit overzealous for our purposes, especially if we're going to have open sessions and classes and such. Maybe all members should just flash their badges even if the door is already open? We could tie this into the irc bot so people could query who is at the space. That'd sortof incentivize proper &quot;status updating&quot; with the door. --[[User:Berticus|Berticus]] 01:30, 29 November 2009 (UTC)<br /> <br /> == Reprap/Makerbot Build ==<br /> Description: Berticus really wants to tinker with 3d printing, and thus desires access to either a Makerbot or the next generation Reprap Mendel.<br /> <br /> Details: [http://makerbot.com/ Makerbots] can be purchased for $750 or $950. The higher price reflects some premium features, mainly pre-assembled electronics, a power supply, and some extra plastic filament. Bots are currently rather backordered. Mendel parts are impossible to find. There seem to be no kits out there for the non-extruded parts (threaded rod, etc.), so even if we can find somebody to print us the plastic bits, it'll still be a bit of a pain to get everything together. Right now a Makerbot is probably the way to go, and we can use that to print out the Mendel parts to make a second bot for experimentation (developing new print heads and such).<br /> <br /> === Comments ===<br /> <br /> <br /> == Ashley's Silly Web Projects ==<br /> BedBugsHotels.com &lt;- looking to collab with someone to build something like bedbugregistry.com but not as lame, using googlemaps. started the site in rails, but have not got very far with this. pretty sure there's traffic waiting for a well developed site along these lines, and it could be fun?<br /> <br /> hotpinkwedding.com &lt;- no one is going to be interested in this topic, per se. But I'm interested in using and learning about different techniques to boost serp via experimentation, if anyone is into that. 500-600 unique visitors a month currently.<br /> <br /> simplerochester.com &lt;- websites hosted on AWS. Looking to redevelop the business model in a unique way and mess around with marketing.<br /> <br /> <br /> == Electronics, parts, and keeping a bunch of stuff in stock ==<br /> Everyone who can afford it should buy one of each of these two boxes, and donate its contents to the space... plus we'll learn a *lot* just from sorting through the contents!<br /> * [http://www.goldmine-elec-products.com/prodinfo.asp?number=G17225 Ginormous Surprise Box]<br /> * [http://www.sciplus.com/recommend.cfm/recommendid/3501 Surprise Box of Science] (sounds like a Bill Nye thing... :-) )<br /> <br /> == INTERLOCK LED Windows ==<br /> Description: The windows at the temp space and the final space have double pane security glass. Light is diffused but one can imagine the possibilities<br /> <br /> Ideas:<br /> * Treat each pane as a pixel for pong, tetris, animated gifs, etc<br /> * Spell INTERLOCK in the glass<br /> * Game of Life pattern<br /> <br /> === Comments ===<br /> How many &quot;pixels&quot; do we have to work with? I seem to recall 3 high, maybe 12-16 long with a window interrupting four-ish blocks in the center. Letters are pretty tricky with just three vertical pixels. More abstract light patterns would be really cool though. --[[User:Berticus|Berticus]] 20:47, 8 December 2009 (UTC)<br /> <br /> Problem: our windows are obscured by shrubbery. So unless we're lighting them up from the outside for our own enjoyment within the space, this idea may be DOA. --[[User:Berticus|Berticus]] 19:42, 10 December 2009 (UTC)<br /> <br /> == Official Friends of Interlock trophy ==<br /> Description: When we visit other hackerspaces or form partnerships with other organizations, it would be cool to give them something that came from the hackerspace. The idea being that it's hand made, geeky, and shows off the Interlock logo in some way. <br /> <br /> Ideas:<br /> * That was easy button re-recorded to say a private message and repainted to have our logo<br /> * Robot of some kind (for Felix)<br /> * Draudio Pen<br /> <br /> === Comments ===<br /> How about some sort of abstract object trophy, that's actually just a piece of a larger objects. The different hackerspaces that received them would have to get together to put the final &quot;trophy&quot; together. Or perhaps they'd all combine into Voltron or Captain Planet. Some such. Or, instead of getting physically together perhaps all the spaces would 3d scan their objects and combine them that way. There'd have to be something extra to thwart that... electronic contacts in each piece that &quot;networked&quot; the larger object perhaps. Ramble complete. --[[User:Berticus|Berticus]] 20:52, 8 December 2009 (UTC)<br /> <br /> == Interlock Dumpster Diving Crew ==<br /> Description: A group of people willing and able to drive around looking for things to pick up on garbage day or legal dumpsters to dive into. <br /> <br /> Members:<br /> * Brian<br /> * Mark<br /> * Josh<br /> * Jimmi<br /> <br /> Targets:<br /> * [http://tinyurl.com/ydsasyh RIT Boneyard]<br /> * RIT dumpsters all across campus after students move out (May of each year)<br /> <br /> <br /> == Interlock as an ISP ==<br /> There has been some debate about this, especially since we're doing the whole non-profit thing, but a non-profit *is* allowed to make money, as long as certain rules are followed.<br /> <br /> Basically, any Internet connection worth getting is going to be mucho expensive, and rather than get 30 new members just to pay for the Internet, it would make a lot of sense to resell it. Based on how expensive RoadRunner is in this building (probably what most of our neighbors have), and how crappy the speed is, I think we could undercut their price and still make it worthwhile to do this. I really want to run a fiber line into our space... the Internet is pretty much at the core of a lot of what we're doing, and we don't want it to be the weak link. But the options are looking like a.) Get 30 more members b.) Resell our connection or c.) Settle for something that is a lot slower than what most of us have at home.<br /> <br /> === Comments ===<br /> <br /> One objection raised for this was that we would be on the hook to provide 24x7 support for our &quot;customers&quot;. Fortunately our customers are mostly business types that don't work in the middle of the night. We would still require some kind of rotating schedule to carry a notification device (used to be a pager) and be available for support calls. Luckily there would not be many calls.<br /> <br /> The other big objection is liability. There are laws dictating how much we need to spy on our customers and liability issues if we spy too much. The legal aspects would require in depth investigation to make sure we are &quot;safe&quot;. Someone thought dealing with court orders and subpoenas might be cumbersome but after having to deal with a couple they aren't that tedious or scary. What was scary was thinking one of my customers was into child porn. I don't think he really was but it makes you wonder.<br /> <br /> All in all it might be reasonable way to subsidize our internet addiction. I don't expect we would get that many customers even if we offer more for less. Most people don't want to change unless there is a real problem with their current provider. And they would only consider us if they thought they could trust us. Personal contact is a big plus in that respect. A flyer in the hall or under the door won't convince anyone and pushing &quot;sales&quot; calls will turn people off. The best way to gain customers is to be a good neighbor and offering good unbiased advice and helpful suggestions. Free tech support is good too but you have to be careful to strictly limit it or you become their unpaid IT department.</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Talk:Infrastructure 2009-12-10T15:57:57Z

<p>Fvox13: /* Internet Access */</p> <hr /> <div>==Network Project==<br /> I would like to take the lead on this. I want to ask at the next meeting what people's needs are for network(s) and bandwidth [I know personally I'd like to play with some high bandwidth VoIP stuff, so the more bandwidth we can afford the better, imo] and see if what we have outlined on the [[Infrastructure]] page meshes with what everyone else was thinking. --[[User:Ben Woodruff|-- BW]] 20:20, 2 December 2009 (UTC)<br /> <br /> ----<br /> <br /> Care to tag-team this? --[[User:Fvox13|Fvox13]] 14:05, 3 December 2009 (UTC)<br /> <br /> ----<br /> <br /> Help is always appreciated, Carl mentioned wanting to help as well. --[[User:Ben Woodruff|-- BW]] 15:04, 3 December 2009 (UTC)<br /> <br /> ---- <br /> <br /> Ben, looks like you've got a good handle on this. Nicely detailed proposals. Thanks for stepping up to lead this.<br /> <br /> The chief thing that springs to mind with regard to the RFC1918 address space allocations is that consumer level devices, which I think it's safe to say we'll have on hand at one time or another, typically use at least two of those ranges preferentially. Apple Airport base stations tend to use addresses in the 10.0.0.0/8 range, and non-Apple devices often plop themselves down in the 192.168.0.0/16 range. <br /> <br /> My suggestion, then, is to use 172.16.0.0/12 range for all of our private networks. That way, if something shows a 192.168.x.y or 10.x.y.z address, we'll know right away that it's coming from something other than our stuff. <br /> <br /> In that light, I propose 172.20.x.y for the production network, partitioned further as you suggest (perhaps spacing things out by 10s in the third octet instead of by 1s, to give some room in between), 172.30.x.y for the warzone. The mnemonic I have in mind for this is that .20 is an &quot;even&quot; multiple of 10, even meaning &quot;smooth&quot; and smooth being what one wants from a production environment. In contrast, .30 is an &quot;odd&quot; multiple of 10, odd being exciting, unusual, or even dangerous, depending on one's perspective, but certainly what one would expect from a &quot;warzone&quot;. In between these two we'd have 172.25.x.y, which would be the playground--not expected to be at all dangerous, but you must be this tall to enter this ride. <br /> <br /> The 10.0.0.0/8 space is pretty big, even if Apple does use part of it. From what I recall and can tell from a quick search, they tend to use 10.0.1.x addresses. I think it might be a good convention to pick some portion of the 10.0.0.0/8 space and then to recommend that people use it for setting up their own independent test networks, eg, if they are building a private network on a single hardware host to use with a collection of virtual machines on that host. If their stuff stays on their own network, no big deal. If they screw up somehow and one of their devices ends up on our network, again, it'll be easy to tell because it is in this distinct 10.0.0.0 region. I think 10.100.0.0 would be easy to remember to use, and well away from Apple's use.<br /> <br /> Within 192.168.0.0, I've seen use all over the range. Some devices I've had use 192.168.0.x range. Some 192.168.254.x. The Linksys NSLU2 &quot;slugs&quot; use 192.168.1.77. And those are just the ones I'm familiar with and can recall off the top of my head. So, I think we just leave this for use with those devices.<br /> <br /> Anyway, that's my suggestion, based on my experience. You may have experience with devices that tend to default to 172.16.0.0 too, making this a less useful scheme, for instance. <br /> <br /> [[User:Deejoe|Deejoe]] 16:07, 5 December 2009 (UTC)<br /> <br /> ---- <br /> <br /> Thanks much for the feedback Deejoe. I like your ideas. I don't know of any devices that are using the 172.x.x.x range by default so that all sounds good.<br /> <br /> Also, Fvox13, good point about Cat6a. Lets shoot for Cat6 with the expectation that we will probably end up with a bunch of cat5e and limited cat6, which we'll probably want to use for core equipment that doesn't have other interconnects.<br /> --[[User:Ben Woodruff|-- BW]] 00:37, 6 December 2009 (UTC)<br /> <br /> ----<br /> <br /> I was looking at the subnetting layout and thought I'd chip in my two cents, for what it's worth. When addressing core devices (switches, routers, servers, and so on), I've found putting them on the subnet right before the broadcast more design-friendly. It makes writing ACLs much more easier and flexible, along with making adding new equipment to the core layer faster. Any thoughts on this? --[[User:BinaryMan|BinaryMan]]<br /> <br /> ----<br /> <br /> I have heard of doing that BinaryMan but I wasn't sure what the benefits were. --[[User:Ben Woodruff|-- BW]] 14:37, 10 December 2009 (UTC)<br /> <br /> == Infrastructure Questions ==<br /> <br /> See [[questions_for_felix]], rather that duplicating content<br /> <br /> == Internet Access ==<br /> Talking to John day about NFP discounts and possible packages for our building zone<br /> --[[User:Antitree|Antitree]] 19:27, 3 December 2009 (UTC) <br /> <br /> ----<br /> <br /> [http://www.fibertech.com/ Fibertech]: [http://en.wikipedia.org/wiki/Metro_Ethernet Metro Ethernet] network ends 1/2 mile from our location. :-( :-( :-( They would have to run a fair amount of fiber to service us. Rather than hit us with $25 - $30K for a buildout cost, they would be able to spread the cost over the course of a 3 or 5 year term (and we wouldn't have to pay *all* of that cost!) Still waiting for official quote, but it does sound expensive. --[[User:Fvox13|Fvox13]] 22:00, 9 December 2009 (UTC)<br /> <br /> ----<br /> <br /> [http://www.cogentco.com/us/ Cogent]: Offer [http://www.cogentco.com/us/pns_dedicated.php?Off off net] service by way of subcontracted T3 / sonet lines. Still waiting for quote, but I don't think they're a valid option, since the Fibertech guy says that Fibertech would be the subcontractor (!) and then Cogent would have to mark it up further. --[[User:Fvox13|Fvox13]] 21:35, 9 December 2009 (UTC)<br /> <br /> <br /> ----<br /> <br /> TW Telecom: Submitted a quote request. They offer Metro Ethernet as well. --[[User:Fvox13|Fvox13]] 21:35, 9 December 2009 (UTC)<br /> <br /> ----<br /> <br /> Frontier: Submitted a quote request. They offer Metro Ethernet, as well as more traditional telco solutions like DS1, DS3, DSL, etc. --[[User:Fvox13|Fvox13]] 22:00, 9 December 2009 (UTC)<br /> <br /> ----<br /> <br /> Meeting Frontier representative at the Space 12/11/2009 at 5pm. --[[User:Fvox13|Fvox13]] 15:57, 10 December 2009 (UTC)<br /> <br /> ----<br /> <br /> American Fiber Systems: Submitted Quote Request --[[User:Fvox13|Fvox13]] 13:59, 10 December 2009 (UTC)<br /> <br /> ----<br /> <br /> Netsville: Submitted Quote Request --[[User:Fvox13|Fvox13]] 13:59, 10 December 2009 (UTC)<br /> <br /> ----<br /> <br /> Paetec: Submitted Quote request --[[User:Fvox13|Fvox13]] 13:59, 10 December 2009 (UTC)<br /> <br /> ----<br /> <br /> <br /> <br /> <br /> Based on what I saw in the temp space, *somebody* has *something* running to our building... we just have to figure out who and what! This whole thing is ridiculous... it's like there's a power line running to our building and we call the power company and they're like &quot;That's not our power line; you have to call somebody else except we don't know who&quot;. Uggghhhh.... why aren't fiber providers regulated the same as other utilities?!? --[[User:Fvox13|Fvox13]] 13:58, 10 December 2009 (UTC)<br /> <br /> == Service Suggestions ==<br /> <br /> AirPort Express wireless AP (connected to stereo system for streaming music via AirTunes?)<br /> Can also act as a USB print server if we have a printer donated (USB is not the best option... we should consider an ethernet-enabled printer (maybe someone can donate?))<br /> --[[User:Ben Woodruff|Ben Woodruff]] 06:19, 2 December 2009 (UTC)<br /> <br /> ----<br /> <br /> Production network should have a more robust AP... maybe a Meru or Cisco? <br /> <br /> ----<br /> <br /> I agree, the problem is cost. I didn't see any mentions of a better AP on the donations page, so we may be stuck with what I've got for the time being. We will also probably want to offer guest wireless access at some point, through a different SSID, which will require an additional/different AP (the new Apple equipment can do it, but this one can't)<br /> <br /> ----<br /> <br /> I have a [http://www.vandis.com/docs/meru-ap100-ds.pdf Meru AP100] and a Cisco Aironet 1200 that I will be donating --[[User:Fvox13|Fvox13]] 18:23, 8 December 2009 (UTC)<br /> <br /> ----<br /> <br /> Does anyone know of a &quot;good&quot; captive portal type system like start.rit.edu or BlueSocket? I want something that can register MAC addresses with a DHCP server if proper credentials are supplied (auth w/ LDAP). Bonus points if it has optional static IP registration for servers and host management (remember which MACs belong to which users) --[[User:Ben Woodruff|-- BW]] 20:06, 8 December 2009 (UTC)<br /> <br /> ----<br /> <br /> I'm against captive portals, (Looks like you sort of agree, the way you said '&quot;good&quot; captive portal'), but [http://m0n0.ch/wall/ Monowall] might work --[[User:Fvox13|Fvox13]] 20:52, 8 December 2009 (UTC)<br /> <br /> ----<br /> <br /> You should be able to use something like PacketFence I would thing. That has an included registration system, so that the admin doesn't have to do as much. Here is a link to its [http://www.packetfence.org/tour/features.html Features]<br /> <br /> --[[User:Cmd3187|Cmd3187]] 21:11, 8 December 2009 (UTC)<br /> <br /> ----<br /> <br /> [http://nocat.net/ NoCatAuth] was developed for open-ish or community wireless networks. Might fit the bill. --[[User:Berticus|Berticus]] 21:24, 8 December 2009 (UTC)<br /> <br /> ----<br /> <br /> I like the looks of pfSense and PacketFence.<br /> Does anyone want to take charge of setting up the LDAP server and RADIUS authentication? It's something I'd like to observe on.<br /> --[[User:Ben Woodruff|-- BW]] 14:40, 10 December 2009 (UTC)</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Infrastructure 2009-12-10T14:00:25Z

<p>Fvox13: /* Internet */</p> <hr /> <div>=Interlock Rochester Infrastructure=<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Sub-group !! Lead !! Members<br /> |-<br /> | Power ||<br /> |-<br /> | Environment ||<br /> |-<br /> | Security || [[User:Antitree|Mark Manning]]<br /> |-<br /> | [[Network Infrastructure Group|Network]] || [[User:Ben Woodruff|Ben Woodruff]] || [[User:fvox13|Steve Smith]]<br /> |-<br /> |}<br /> <br /> ''' NOTE''': This page contains information with regard to network/server setup for the final space, not the temporary one. For the temp space, power distribution can be done with extension cords, while network access will be ad-hoc in nature.<br /> <br /> =Power=<br /> Overhead cord reels are a solution, but they must not remain plugged in at their source when not in use in order to comply with fire code. Cable trays are not a good solution for power. (They are a pain in the ass.)<br /> <br /> =Environmental=<br /> The space will need to have environmental controls in the event that servers will be kept in location. The general operating temperature of servers and network equipment should be around 75F. In order to ensure this, the purchase of an AC system will be necessary.<br /> <br /> '''Things we may need to acquire:'''<br /> *&lt;s&gt;Heater&lt;/s&gt; &lt;-- Heat is included<br /> *Air Conditioner<br /> *Dehumidifier<br /> *&lt;s&gt;Thermostat/Thermometer&lt;/s&gt; &lt;-- Usually bundled with AC<br /> <br /> =Network=<br /> <br /> The network infrastructure group will create and maintain the [[network acceptable use policy]]. The policy will be approved by the board of directors and then signed by every member who wants access to any of the following networks.<br /> <br /> In order to meet the demands of the group over time, the network will be segregated into 3 main segments:<br /> * &lt;span style=&quot;color: green&quot;&gt;Production&lt;/span&gt;<br /> * &lt;span style=&quot;color: red&quot;&gt;Warzone&lt;/span&gt;<br /> * &lt;span style=&quot;color: gold&quot;&gt;Playground&lt;/span&gt;<br /> <br /> Each main segment will have an associated color code for its jacks (as is seen above), both on the walls, as well as near the network equipment. Category 6 cabling would be preferred for the environment. Each wall plate should be 6 feet apart, and should contain at least 1 of each colored jacks. Every jack should had 2 drops associated with it. <br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Network/Mask !! Name !! Description<br /> |-<br /> | '''172.20.0.0/16''' || '''Production''' || '''Supernet slice for all production networks'''<br /> |-<br /> | 172.20.0.0/24 || Core || Core Equipment (routers, switches, etc)<br /> |-<br /> | 172.20.10.0/24 || Servers || Servers (LDAP, DHCP, DNS, etc - assuming not provided by router)<br /> |-<br /> | 172.20.20.0/24 || Wired Hosts || Shared workstations<br /> |-<br /> | 172.20.30.0/24 || Wireless Hosts || Registered Member laptops<br /> |- <br /> | 172.20.50.0/24 || Wireless Guests || Event Participants, Class registrants, etc - May be partitioned into a separate network, see below<br /> |-<br /> | '''172.25.0.0/16''' || '''Playground''' || '''Network specific for individual projects. Should be sliced further to /24 and /26 networks as needed'''<br /> |- <br /> | '''172.30.0.0/16''' || '''Warzone''' || '''A place where invasive network attacks can occur. Will be a stub network with no regular Internet access'''<br /> |}<br /> <br /> <br /> == Internet ==<br /> <br /> === Time Warner Cable ===<br /> Per your request-we can provide bandwidth Tier of 5mbps/384Kbps at the following rate:<br /> 1 year $88.20<br /> 2 year $84.00<br /> 3 year $79.95<br /> Install fee of $75.00<br /> <br /> We can offer 5Mbps/768 Kbps:<br /> 1 year $140.70<br /> 2 year $133.85<br /> 3 year $126.95<br /> Install fee of $75.00<br /> <br /> Total Cost(1 yr): $163.20<br /> <br /> <br /> * We are in discussion with other ISPs, including Cogent, Fibertech, Frontier, AFS, Netsville, Paetec, and TW Telecom. [[Talk:Infrastructure]]<br /> <br /> ==&lt;span style=&quot;color: green&quot;&gt;Production&lt;/span&gt;==<br /> The production network will be the main segment and will provide network access to Interlock's members. This network will be subdivided into 5 separate subnets, to help manage IP growth, and secure vital systems. The production network will not be used to perform penetration testing or other white hat hacking (port scans, IP sweeps, DoS, etc). The production network must have reliable uptime, as that other members will be dependent on it.<br /> <br /> === Change Control ===<br /> The infrastructure group will need to determine a method to log changes to the network. A consensus must be reached within the group before any change can be done on the production network. Change management will ''loosely'' follow [http://en.wikipedia.org/wiki/Change_Management_%28ITSM%29 ITIL Recommendations].<br /> <br /> === Access ===<br /> Access to core network equipment and topology will be restricted to those in the infrastructure group.<br /> <br /> === Services ===<br /> * RADIUS/LDAP Server<br /> ** Central Authentication repository<br /> ** Should be linked with Google Apps<br /> <br /> * Web Server<br /> ** Host the wiki, website, etc<br /> <br /> * CoLo Boxes<br /> ** Not intended to host production/high bandwidth websites<br /> ** Used for offsite backup<br /> <br /> * DHCP Server<br /> ** IP addresses will only be given out to know and trusted network adapters. <br /> ** A device registration system, like RIT's start.rit.edu, would be useful<br /> <br /> * DNS Server<br /> <br /> * File Server<br /> ** Access via SFTP, SMB, or WebDAV possibly<br /> <br /> * VPN Server<br /> ** Provide VPN access to the network. This needs to be decided as to whether this will be implemented, and the scope of the build.<br /> <br /> * Streaming Music Server<br /> ** Use a AirPort Extreme AP to play music via AirTunes<br /> <br /> * Image Server<br /> ** RIS or Ghost<br /> <br /> ==&lt;span style=&quot;color: red&quot;&gt;Warzone&lt;/span&gt;==<br /> * 172.30.x.y<br /> * No expectation of reliability<br /> * Relatively open access to equipment / no change management<br /> * No expectation of structure, very dynamic depending on project use etc, may use different IP address schemes if it doesn't connect to the other two networks in any way<br /> * Expect to have equipment probed / pen tested<br /> * No internet connectivity? Expect machines to be exploited / infected?<br /> * &quot;Rogue&quot; access points allowed (maybe include DHCP message that states you'd better be sure you want to connect to this network - want to be friendly with our neighbors)<br /> <br /> ==&lt;span style=&quot;color: gold&quot;&gt;Playground&lt;/span&gt;==<br /> * 172.25.x.y<br /> ** Each project should claim an address space (ie 172.25.15.y) so we can tell what traffic is coming from which projects<br /> * Temporary, dynamic, but more static and stable than the warzone<br /> * Change management much more loose than production network but there should be some expectation of reliability so please at least check with someone unless you're very sure of what you're doing<br /> * Access to the internet<br /> * Area to play with an test new technologies (for example, play with VOIP/SIP)<br /> <br /> == References ==<br /> * NEC 210.52<br /> <br /> =Physical Security=<br /> * We need to be able to &quot;deactivate&quot; keys, for non-payment etc<br /> * Multi-factor authentication (ie, fob + PIN)<br /> * Biometric stuff is really cool. Can we afford? [http://recognitionsystems.schlage.com/ Schlage Biometric systems]<br /> * Audit logging (twitter, website, dot matrix paper trail, etc)<br /> <br /> <br /> <br /> =Audio-Visual System=<br /> <br /> '''Audio'''<br /> *[http://www.bhphotovideo.com/c/product/541197-REG/Bogen_Communications_S810T725PG8W_Ceiling_Speaker_Assembly_with.html Public Address] system array across the ceiling<br /> *Two speakers rigged to the top corners of the room<br /> *Surround sound rigged to the top of the room (low priority)<br /> *Inputs to an audio mixer/home receiver<br /> *Sources: Microphone, CD/DVD, computers<br /> <br /> '''Video'''<br /> *Ceiling mounted projection<br /> *Screen<br /> *Sources: DVD, computers</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Talk:Infrastructure 2009-12-10T13:59:07Z

<p>Fvox13: /* Internet Access */</p> <hr /> <div>==Network Project==<br /> I would like to take the lead on this. I want to ask at the next meeting what people's needs are for network(s) and bandwidth [I know personally I'd like to play with some high bandwidth VoIP stuff, so the more bandwidth we can afford the better, imo] and see if what we have outlined on the [[Infrastructure]] page meshes with what everyone else was thinking. --[[User:Ben Woodruff|-- BW]] 20:20, 2 December 2009 (UTC)<br /> <br /> <br /> Care to tag-team this? --[[User:Fvox13|Fvox13]] 14:05, 3 December 2009 (UTC)<br /> <br /> Help is always appreciated, Carl mentioned wanting to help as well. --[[User:Ben Woodruff|-- BW]] 15:04, 3 December 2009 (UTC)<br /> <br /> ---- <br /> <br /> Ben, looks like you've got a good handle on this. Nicely detailed proposals. Thanks for stepping up to lead this.<br /> <br /> The chief thing that springs to mind with regard to the RFC1918 address space allocations is that consumer level devices, which I think it's safe to say we'll have on hand at one time or another, typically use at least two of those ranges preferentially. Apple Airport base stations tend to use addresses in the 10.0.0.0/8 range, and non-Apple devices often plop themselves down in the 192.168.0.0/16 range. <br /> <br /> My suggestion, then, is to use 172.16.0.0/12 range for all of our private networks. That way, if something shows a 192.168.x.y or 10.x.y.z address, we'll know right away that it's coming from something other than our stuff. <br /> <br /> In that light, I propose 172.20.x.y for the production network, partitioned further as you suggest (perhaps spacing things out by 10s in the third octet instead of by 1s, to give some room in between), 172.30.x.y for the warzone. The mnemonic I have in mind for this is that .20 is an &quot;even&quot; multiple of 10, even meaning &quot;smooth&quot; and smooth being what one wants from a production environment. In contrast, .30 is an &quot;odd&quot; multiple of 10, odd being exciting, unusual, or even dangerous, depending on one's perspective, but certainly what one would expect from a &quot;warzone&quot;. In between these two we'd have 172.25.x.y, which would be the playground--not expected to be at all dangerous, but you must be this tall to enter this ride. <br /> <br /> The 10.0.0.0/8 space is pretty big, even if Apple does use part of it. From what I recall and can tell from a quick search, they tend to use 10.0.1.x addresses. I think it might be a good convention to pick some portion of the 10.0.0.0/8 space and then to recommend that people use it for setting up their own independent test networks, eg, if they are building a private network on a single hardware host to use with a collection of virtual machines on that host. If their stuff stays on their own network, no big deal. If they screw up somehow and one of their devices ends up on our network, again, it'll be easy to tell because it is in this distinct 10.0.0.0 region. I think 10.100.0.0 would be easy to remember to use, and well away from Apple's use.<br /> <br /> Within 192.168.0.0, I've seen use all over the range. Some devices I've had use 192.168.0.x range. Some 192.168.254.x. The Linksys NSLU2 &quot;slugs&quot; use 192.168.1.77. And those are just the ones I'm familiar with and can recall off the top of my head. So, I think we just leave this for use with those devices.<br /> <br /> Anyway, that's my suggestion, based on my experience. You may have experience with devices that tend to default to 172.16.0.0 too, making this a less useful scheme, for instance. <br /> <br /> [[User:Deejoe|Deejoe]] 16:07, 5 December 2009 (UTC)<br /> <br /> ---- <br /> <br /> Thanks much for the feedback Deejoe. I like your ideas. I don't know of any devices that are using the 172.x.x.x range by default so that all sounds good.<br /> <br /> Also, Fvox13, good point about Cat6a. Lets shoot for Cat6 with the expectation that we will probably end up with a bunch of cat5e and limited cat6, which we'll probably want to use for core equipment that doesn't have other interconnects.<br /> --[[User:Ben Woodruff|-- BW]] 00:37, 6 December 2009 (UTC)<br /> <br /> I was looking at the subnetting layout and thought I'd chip in my two cents, for what it's worth. When addressing core devices (switches, routers, servers, and so on), I've found putting them on the subnet right before the broadcast more design-friendly. It makes writing ACLs much more easier and flexible, along with making adding new equipment to the core layer faster. Any thoughts on this? --[[User:BinaryMan|BinaryMan]]<br /> <br /> ----<br /> <br /> == Infrastructure Questions ==<br /> I am going to put the questions about the environment and power over into this talk section, so we can try and clean up the main page a little bit more. [[User:Cmd3187|Cmd3187]] 18:22, 8 December 2009 (UTC)<br /> <br /> === Power ===<br /> *What is the capacity of the power system the space on?<br /> *Is it shared with other tenants?<br /> *What kind of emergency power/lighting does the building have?<br /> *Is it our responsibility or the landlord's to increase/change electrical capacity?<br /> <br /> '''If so:'''<br /> <br /> *Do we have access to the electrical panel or disconnect/fuses from within the space?<br /> *Can we run our own conduit/wall boxes? (Wall conduit to comply with fire code)<br /> <br /> === Environmental ===<br /> *How is the space heated in the winter?<br /> *How is the space cooled in the summer?<br /> *What is the RG&amp;E budget for the space (assuming it can give some indication of the cost of heating/cooling)?<br /> *Will humidity be a problem?<br /> <br /> == Internet Access ==<br /> Talking to John day about NFP discounts and possible packages for our building zone<br /> --[[User:Antitree|Antitree]] 19:27, 3 December 2009 (UTC) <br /> <br /> ----<br /> <br /> [http://www.fibertech.com/ Fibertech]: [http://en.wikipedia.org/wiki/Metro_Ethernet Metro Ethernet] network ends 1/2 mile from our location. :-( :-( :-( They would have to run a fair amount of fiber to service us. Rather than hit us with $25 - $30K for a buildout cost, they would be able to spread the cost over the course of a 3 or 5 year term (and we wouldn't have to pay *all* of that cost!) Still waiting for official quote, but it does sound expensive. --[[User:Fvox13|Fvox13]] 22:00, 9 December 2009 (UTC)<br /> <br /> ----<br /> <br /> [http://www.cogentco.com/us/ Cogent]: Offer [http://www.cogentco.com/us/pns_dedicated.php?Off off net] service by way of subcontracted T3 / sonet lines. Still waiting for quote, but I don't think they're a valid option, since the Fibertech guy says that Fibertech would be the subcontractor (!) and then Cogent would have to mark it up further. --[[User:Fvox13|Fvox13]] 21:35, 9 December 2009 (UTC)<br /> <br /> <br /> ----<br /> <br /> TW Telecom: Submitted a quote request. They offer Metro Ethernet as well. --[[User:Fvox13|Fvox13]] 21:35, 9 December 2009 (UTC)<br /> <br /> ----<br /> <br /> Frontier: Submitted a quote request. They offer Metro Ethernet, as well as more traditional telco solutions like DS1, DS3, DSL, etc. --[[User:Fvox13|Fvox13]] 22:00, 9 December 2009 (UTC)<br /> <br /> ----<br /> <br /> American Fiber Systems: Submitted Quote Request --[[User:Fvox13|Fvox13]] 13:59, 10 December 2009 (UTC)<br /> <br /> ----<br /> <br /> Netsville: Submitted Quote Request --[[User:Fvox13|Fvox13]] 13:59, 10 December 2009 (UTC)<br /> <br /> ----<br /> <br /> Paetec: Submitted Quote request --[[User:Fvox13|Fvox13]] 13:59, 10 December 2009 (UTC)<br /> <br /> ----<br /> <br /> <br /> <br /> <br /> Based on what I saw in the temp space, *somebody* has *something* running to our building... we just have to figure out who and what! This whole thing is ridiculous... it's like there's a power line running to our building and we call the power company and they're like &quot;That's not our power line; you have to call somebody else except we don't know who&quot;. Uggghhhh.... why aren't fiber providers regulated the same as other utilities?!? --[[User:Fvox13|Fvox13]] 13:58, 10 December 2009 (UTC)<br /> <br /> == Service Suggestions ==<br /> <br /> AirPort Express wireless AP (connected to stereo system for streaming music via AirTunes?)<br /> Can also act as a USB print server if we have a printer donated (USB is not the best option... we should consider an ethernet-enabled printer (maybe someone can donate?))<br /> --[[User:Ben Woodruff|Ben Woodruff]] 06:19, 2 December 2009 (UTC)<br /> <br /> ----<br /> <br /> Production network should have a more robust AP... maybe a Meru or Cisco? <br /> <br /> ----<br /> <br /> I agree, the problem is cost. I didn't see any mentions of a better AP on the donations page, so we may be stuck with what I've got for the time being. We will also probably want to offer guest wireless access at some point, through a different SSID, which will require an additional/different AP (the new Apple equipment can do it, but this one can't)<br /> <br /> ----<br /> <br /> I have a [http://www.vandis.com/docs/meru-ap100-ds.pdf Meru AP100] and a Cisco Aironet 1200 that I will be donating --[[User:Fvox13|Fvox13]] 18:23, 8 December 2009 (UTC)<br /> <br /> ----<br /> <br /> Does anyone know of a &quot;good&quot; captive portal type system like start.rit.edu or BlueSocket? I want something that can register MAC addresses with a DHCP server if proper credentials are supplied (auth w/ LDAP). Bonus points if it has optional static IP registration for servers and host management (remember which MACs belong to which users) --[[User:Ben Woodruff|-- BW]] 20:06, 8 December 2009 (UTC)<br /> <br /> ----<br /> <br /> I'm against captive portals, (Looks like you sort of agree, the way you said '&quot;good&quot; captive portal'), but [http://m0n0.ch/wall/ Monowall] might work --[[User:Fvox13|Fvox13]] 20:52, 8 December 2009 (UTC)<br /> <br /> ----<br /> <br /> You should be able to use something like PacketFence I would thing. That has an included registration system, so that the admin doesn't have to do as much. Here is a link to its [http://www.packetfence.org/tour/features.html Features]<br /> <br /> --[[User:Cmd3187|Cmd3187]] 21:11, 8 December 2009 (UTC)<br /> <br /> ----<br /> [http://nocat.net/ NoCatAuth] was developed for open-ish or community wireless networks. Might fit the bill. --[[User:Berticus|Berticus]] 21:24, 8 December 2009 (UTC)</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Talk:Infrastructure 2009-12-10T13:58:08Z

<p>Fvox13: /* Internet Access */</p> <hr /> <div>==Network Project==<br /> I would like to take the lead on this. I want to ask at the next meeting what people's needs are for network(s) and bandwidth [I know personally I'd like to play with some high bandwidth VoIP stuff, so the more bandwidth we can afford the better, imo] and see if what we have outlined on the [[Infrastructure]] page meshes with what everyone else was thinking. --[[User:Ben Woodruff|-- BW]] 20:20, 2 December 2009 (UTC)<br /> <br /> <br /> Care to tag-team this? --[[User:Fvox13|Fvox13]] 14:05, 3 December 2009 (UTC)<br /> <br /> Help is always appreciated, Carl mentioned wanting to help as well. --[[User:Ben Woodruff|-- BW]] 15:04, 3 December 2009 (UTC)<br /> <br /> ---- <br /> <br /> Ben, looks like you've got a good handle on this. Nicely detailed proposals. Thanks for stepping up to lead this.<br /> <br /> The chief thing that springs to mind with regard to the RFC1918 address space allocations is that consumer level devices, which I think it's safe to say we'll have on hand at one time or another, typically use at least two of those ranges preferentially. Apple Airport base stations tend to use addresses in the 10.0.0.0/8 range, and non-Apple devices often plop themselves down in the 192.168.0.0/16 range. <br /> <br /> My suggestion, then, is to use 172.16.0.0/12 range for all of our private networks. That way, if something shows a 192.168.x.y or 10.x.y.z address, we'll know right away that it's coming from something other than our stuff. <br /> <br /> In that light, I propose 172.20.x.y for the production network, partitioned further as you suggest (perhaps spacing things out by 10s in the third octet instead of by 1s, to give some room in between), 172.30.x.y for the warzone. The mnemonic I have in mind for this is that .20 is an &quot;even&quot; multiple of 10, even meaning &quot;smooth&quot; and smooth being what one wants from a production environment. In contrast, .30 is an &quot;odd&quot; multiple of 10, odd being exciting, unusual, or even dangerous, depending on one's perspective, but certainly what one would expect from a &quot;warzone&quot;. In between these two we'd have 172.25.x.y, which would be the playground--not expected to be at all dangerous, but you must be this tall to enter this ride. <br /> <br /> The 10.0.0.0/8 space is pretty big, even if Apple does use part of it. From what I recall and can tell from a quick search, they tend to use 10.0.1.x addresses. I think it might be a good convention to pick some portion of the 10.0.0.0/8 space and then to recommend that people use it for setting up their own independent test networks, eg, if they are building a private network on a single hardware host to use with a collection of virtual machines on that host. If their stuff stays on their own network, no big deal. If they screw up somehow and one of their devices ends up on our network, again, it'll be easy to tell because it is in this distinct 10.0.0.0 region. I think 10.100.0.0 would be easy to remember to use, and well away from Apple's use.<br /> <br /> Within 192.168.0.0, I've seen use all over the range. Some devices I've had use 192.168.0.x range. Some 192.168.254.x. The Linksys NSLU2 &quot;slugs&quot; use 192.168.1.77. And those are just the ones I'm familiar with and can recall off the top of my head. So, I think we just leave this for use with those devices.<br /> <br /> Anyway, that's my suggestion, based on my experience. You may have experience with devices that tend to default to 172.16.0.0 too, making this a less useful scheme, for instance. <br /> <br /> [[User:Deejoe|Deejoe]] 16:07, 5 December 2009 (UTC)<br /> <br /> ---- <br /> <br /> Thanks much for the feedback Deejoe. I like your ideas. I don't know of any devices that are using the 172.x.x.x range by default so that all sounds good.<br /> <br /> Also, Fvox13, good point about Cat6a. Lets shoot for Cat6 with the expectation that we will probably end up with a bunch of cat5e and limited cat6, which we'll probably want to use for core equipment that doesn't have other interconnects.<br /> --[[User:Ben Woodruff|-- BW]] 00:37, 6 December 2009 (UTC)<br /> <br /> I was looking at the subnetting layout and thought I'd chip in my two cents, for what it's worth. When addressing core devices (switches, routers, servers, and so on), I've found putting them on the subnet right before the broadcast more design-friendly. It makes writing ACLs much more easier and flexible, along with making adding new equipment to the core layer faster. Any thoughts on this? --[[User:BinaryMan|BinaryMan]]<br /> <br /> ----<br /> <br /> == Infrastructure Questions ==<br /> I am going to put the questions about the environment and power over into this talk section, so we can try and clean up the main page a little bit more. [[User:Cmd3187|Cmd3187]] 18:22, 8 December 2009 (UTC)<br /> <br /> === Power ===<br /> *What is the capacity of the power system the space on?<br /> *Is it shared with other tenants?<br /> *What kind of emergency power/lighting does the building have?<br /> *Is it our responsibility or the landlord's to increase/change electrical capacity?<br /> <br /> '''If so:'''<br /> <br /> *Do we have access to the electrical panel or disconnect/fuses from within the space?<br /> *Can we run our own conduit/wall boxes? (Wall conduit to comply with fire code)<br /> <br /> === Environmental ===<br /> *How is the space heated in the winter?<br /> *How is the space cooled in the summer?<br /> *What is the RG&amp;E budget for the space (assuming it can give some indication of the cost of heating/cooling)?<br /> *Will humidity be a problem?<br /> <br /> == Internet Access ==<br /> Talking to John day about NFP discounts and possible packages for our building zone<br /> --[[User:Antitree|Antitree]] 19:27, 3 December 2009 (UTC) <br /> <br /> ----<br /> <br /> [http://www.fibertech.com/ Fibertech]: [http://en.wikipedia.org/wiki/Metro_Ethernet Metro Ethernet] network ends 1/2 mile from our location. :-( :-( :-( They would have to run a fair amount of fiber to service us. Rather than hit us with $25 - $30K for a buildout cost, they would be able to spread the cost over the course of a 3 or 5 year term (and we wouldn't have to pay *all* of that cost!) Still waiting for official quote, but it does sound expensive. --[[User:Fvox13|Fvox13]] 22:00, 9 December 2009 (UTC)<br /> <br /> ----<br /> <br /> [http://www.cogentco.com/us/ Cogent]: Offer [http://www.cogentco.com/us/pns_dedicated.php?Off off net] service by way of subcontracted T3 / sonet lines. Still waiting for quote, but I don't think they're a valid option, since the Fibertech guy says that Fibertech would be the subcontractor (!) and then Cogent would have to mark it up further. --[[User:Fvox13|Fvox13]] 21:35, 9 December 2009 (UTC)<br /> <br /> <br /> ----<br /> <br /> TW Telecom: Submitted a quote request. They offer Metro Ethernet as well. --[[User:Fvox13|Fvox13]] 21:35, 9 December 2009 (UTC)<br /> <br /> ----<br /> <br /> Frontier: Submitted a quote request. They offer Metro Ethernet, as well as more traditional telco solutions like DS1, DS3, DSL, etc. --[[User:Fvox13|Fvox13]] 22:00, 9 December 2009 (UTC)<br /> <br /> ----<br /> <br /> American Fiber Systems: Submitted Quote Request<br /> Netsville: Submitted Quote Request<br /> Paetec: Submitted Quote request<br /> --[[User:Fvox13|Fvox13]] 13:58, 10 December 2009 (UTC)<br /> <br /> ----<br /> <br /> <br /> <br /> <br /> Based on what I saw in the temp space, *somebody* has *something* running to our building... we just have to figure out who and what! This whole thing is ridiculous... it's like there's a power line running to our building and we call the power company and they're like &quot;That's not our power line; you have to call somebody else except we don't know who&quot;. Uggghhhh.... why aren't fiber providers regulated the same as other utilities?!? --[[User:Fvox13|Fvox13]] 13:58, 10 December 2009 (UTC)<br /> <br /> == Service Suggestions ==<br /> <br /> AirPort Express wireless AP (connected to stereo system for streaming music via AirTunes?)<br /> Can also act as a USB print server if we have a printer donated (USB is not the best option... we should consider an ethernet-enabled printer (maybe someone can donate?))<br /> --[[User:Ben Woodruff|Ben Woodruff]] 06:19, 2 December 2009 (UTC)<br /> <br /> ----<br /> <br /> Production network should have a more robust AP... maybe a Meru or Cisco? <br /> <br /> ----<br /> <br /> I agree, the problem is cost. I didn't see any mentions of a better AP on the donations page, so we may be stuck with what I've got for the time being. We will also probably want to offer guest wireless access at some point, through a different SSID, which will require an additional/different AP (the new Apple equipment can do it, but this one can't)<br /> <br /> ----<br /> <br /> I have a [http://www.vandis.com/docs/meru-ap100-ds.pdf Meru AP100] and a Cisco Aironet 1200 that I will be donating --[[User:Fvox13|Fvox13]] 18:23, 8 December 2009 (UTC)<br /> <br /> ----<br /> <br /> Does anyone know of a &quot;good&quot; captive portal type system like start.rit.edu or BlueSocket? I want something that can register MAC addresses with a DHCP server if proper credentials are supplied (auth w/ LDAP). Bonus points if it has optional static IP registration for servers and host management (remember which MACs belong to which users) --[[User:Ben Woodruff|-- BW]] 20:06, 8 December 2009 (UTC)<br /> <br /> ----<br /> <br /> I'm against captive portals, (Looks like you sort of agree, the way you said '&quot;good&quot; captive portal'), but [http://m0n0.ch/wall/ Monowall] might work --[[User:Fvox13|Fvox13]] 20:52, 8 December 2009 (UTC)<br /> <br /> ----<br /> <br /> You should be able to use something like PacketFence I would thing. That has an included registration system, so that the admin doesn't have to do as much. Here is a link to its [http://www.packetfence.org/tour/features.html Features]<br /> <br /> --[[User:Cmd3187|Cmd3187]] 21:11, 8 December 2009 (UTC)<br /> <br /> ----<br /> [http://nocat.net/ NoCatAuth] was developed for open-ish or community wireless networks. Might fit the bill. --[[User:Berticus|Berticus]] 21:24, 8 December 2009 (UTC)</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Talk:Infrastructure 2009-12-09T22:01:22Z

<p>Fvox13: /* Service Suggestions */</p> <hr /> <div>==Network Project==<br /> I would like to take the lead on this. I want to ask at the next meeting what people's needs are for network(s) and bandwidth [I know personally I'd like to play with some high bandwidth VoIP stuff, so the more bandwidth we can afford the better, imo] and see if what we have outlined on the [[Infrastructure]] page meshes with what everyone else was thinking. --[[User:Ben Woodruff|-- BW]] 20:20, 2 December 2009 (UTC)<br /> <br /> <br /> Care to tag-team this? --[[User:Fvox13|Fvox13]] 14:05, 3 December 2009 (UTC)<br /> <br /> Help is always appreciated, Carl mentioned wanting to help as well. --[[User:Ben Woodruff|-- BW]] 15:04, 3 December 2009 (UTC)<br /> <br /> ---- <br /> <br /> Ben, looks like you've got a good handle on this. Nicely detailed proposals. Thanks for stepping up to lead this.<br /> <br /> The chief thing that springs to mind with regard to the RFC1918 address space allocations is that consumer level devices, which I think it's safe to say we'll have on hand at one time or another, typically use at least two of those ranges preferentially. Apple Airport base stations tend to use addresses in the 10.0.0.0/8 range, and non-Apple devices often plop themselves down in the 192.168.0.0/16 range. <br /> <br /> My suggestion, then, is to use 172.16.0.0/12 range for all of our private networks. That way, if something shows a 192.168.x.y or 10.x.y.z address, we'll know right away that it's coming from something other than our stuff. <br /> <br /> In that light, I propose 172.20.x.y for the production network, partitioned further as you suggest (perhaps spacing things out by 10s in the third octet instead of by 1s, to give some room in between), 172.30.x.y for the warzone. The mnemonic I have in mind for this is that .20 is an &quot;even&quot; multiple of 10, even meaning &quot;smooth&quot; and smooth being what one wants from a production environment. In contrast, .30 is an &quot;odd&quot; multiple of 10, odd being exciting, unusual, or even dangerous, depending on one's perspective, but certainly what one would expect from a &quot;warzone&quot;. In between these two we'd have 172.25.x.y, which would be the playground--not expected to be at all dangerous, but you must be this tall to enter this ride. <br /> <br /> The 10.0.0.0/8 space is pretty big, even if Apple does use part of it. From what I recall and can tell from a quick search, they tend to use 10.0.1.x addresses. I think it might be a good convention to pick some portion of the 10.0.0.0/8 space and then to recommend that people use it for setting up their own independent test networks, eg, if they are building a private network on a single hardware host to use with a collection of virtual machines on that host. If their stuff stays on their own network, no big deal. If they screw up somehow and one of their devices ends up on our network, again, it'll be easy to tell because it is in this distinct 10.0.0.0 region. I think 10.100.0.0 would be easy to remember to use, and well away from Apple's use.<br /> <br /> Within 192.168.0.0, I've seen use all over the range. Some devices I've had use 192.168.0.x range. Some 192.168.254.x. The Linksys NSLU2 &quot;slugs&quot; use 192.168.1.77. And those are just the ones I'm familiar with and can recall off the top of my head. So, I think we just leave this for use with those devices.<br /> <br /> Anyway, that's my suggestion, based on my experience. You may have experience with devices that tend to default to 172.16.0.0 too, making this a less useful scheme, for instance. <br /> <br /> [[User:Deejoe|Deejoe]] 16:07, 5 December 2009 (UTC)<br /> <br /> ---- <br /> <br /> Thanks much for the feedback Deejoe. I like your ideas. I don't know of any devices that are using the 172.x.x.x range by default so that all sounds good.<br /> <br /> Also, Fvox13, good point about Cat6a. Lets shoot for Cat6 with the expectation that we will probably end up with a bunch of cat5e and limited cat6, which we'll probably want to use for core equipment that doesn't have other interconnects.<br /> --[[User:Ben Woodruff|-- BW]] 00:37, 6 December 2009 (UTC)<br /> <br /> ----<br /> <br /> == Infrastructure Questions ==<br /> I am going to put the questions about the environment and power over into this talk section, so we can try and clean up the main page a little bit more. [[User:Cmd3187|Cmd3187]] 18:22, 8 December 2009 (UTC)<br /> <br /> === Power ===<br /> *What is the capacity of the power system the space on?<br /> *Is it shared with other tenants?<br /> *What kind of emergency power/lighting does the building have?<br /> *Is it our responsibility or the landlord's to increase/change electrical capacity?<br /> <br /> '''If so:'''<br /> <br /> *Do we have access to the electrical panel or disconnect/fuses from within the space?<br /> *Can we run our own conduit/wall boxes? (Wall conduit to comply with fire code)<br /> <br /> === Environmental ===<br /> *How is the space heated in the winter?<br /> *How is the space cooled in the summer?<br /> *What is the RG&amp;E budget for the space (assuming it can give some indication of the cost of heating/cooling)?<br /> *Will humidity be a problem?<br /> <br /> == Internet Access ==<br /> Talking to John day about NFP discounts and possible packages for our building zone<br /> --[[User:Antitree|Antitree]] 19:27, 3 December 2009 (UTC) <br /> <br /> ----<br /> <br /> [http://www.fibertech.com/ Fibertech]: [http://en.wikipedia.org/wiki/Metro_Ethernet Metro Ethernet] network ends 1/2 mile from our location. :-( :-( :-( They would have to run a fair amount of fiber to service us. Rather than hit us with $25 - $30K for a buildout cost, they would be able to spread the cost over the course of a 3 or 5 year term (and we wouldn't have to pay *all* of that cost!) Still waiting for official quote, but it does sound expensive. --[[User:Fvox13|Fvox13]] 22:00, 9 December 2009 (UTC)<br /> <br /> ----<br /> <br /> [http://www.cogentco.com/us/ Cogent]: Offer [http://www.cogentco.com/us/pns_dedicated.php?Off off net] service by way of subcontracted T3 / sonet lines. Still waiting for quote, but I don't think they're a valid option, since the Fibertech guy says that Fibertech would be the subcontractor (!) and then Cogent would have to mark it up further. --[[User:Fvox13|Fvox13]] 21:35, 9 December 2009 (UTC)<br /> <br /> <br /> ----<br /> <br /> TW Telecom: Submitted a quote request. They offer Metro Ethernet as well. --[[User:Fvox13|Fvox13]] 21:35, 9 December 2009 (UTC)<br /> <br /> ----<br /> <br /> Frontier: Submitted a quote request. They offer Metro Ethernet, as well as more traditional telco solutions like DS1, DS3, DSL, etc. --[[User:Fvox13|Fvox13]] 22:00, 9 December 2009 (UTC)<br /> <br /> ----<br /> <br /> Based on what I saw in the temp space, *somebody* has *something* running to our building... we just have to figure out who and what!<br /> <br /> == Service Suggestions ==<br /> <br /> AirPort Express wireless AP (connected to stereo system for streaming music via AirTunes?)<br /> Can also act as a USB print server if we have a printer donated (USB is not the best option... we should consider an ethernet-enabled printer (maybe someone can donate?))<br /> --[[User:Ben Woodruff|Ben Woodruff]] 06:19, 2 December 2009 (UTC)<br /> <br /> ----<br /> <br /> Production network should have a more robust AP... maybe a Meru or Cisco? <br /> <br /> ----<br /> <br /> I agree, the problem is cost. I didn't see any mentions of a better AP on the donations page, so we may be stuck with what I've got for the time being. We will also probably want to offer guest wireless access at some point, through a different SSID, which will require an additional/different AP (the new Apple equipment can do it, but this one can't)<br /> <br /> ----<br /> <br /> I have a [http://www.vandis.com/docs/meru-ap100-ds.pdf Meru AP100] and a Cisco Aironet 1200 that I will be donating --[[User:Fvox13|Fvox13]] 18:23, 8 December 2009 (UTC)<br /> <br /> ----<br /> <br /> Does anyone know of a &quot;good&quot; captive portal type system like start.rit.edu or BlueSocket? I want something that can register MAC addresses with a DHCP server if proper credentials are supplied (auth w/ LDAP). Bonus points if it has optional static IP registration for servers and host management (remember which MACs belong to which users) --[[User:Ben Woodruff|-- BW]] 20:06, 8 December 2009 (UTC)<br /> <br /> ----<br /> <br /> I'm against captive portals, (Looks like you sort of agree, the way you said '&quot;good&quot; captive portal'), but [http://m0n0.ch/wall/ Monowall] might work --[[User:Fvox13|Fvox13]] 20:52, 8 December 2009 (UTC)<br /> <br /> ----<br /> <br /> You should be able to use something like PacketFence I would thing. That has an included registration system, so that the admin doesn't have to do as much. Here is a link to its [http://www.packetfence.org/tour/features.html Features]<br /> <br /> --[[User:Cmd3187|Cmd3187]] 21:11, 8 December 2009 (UTC)<br /> <br /> ----<br /> [http://nocat.net/ NoCatAuth] was developed for open-ish or community wireless networks. Might fit the bill. --[[User:Berticus|Berticus]] 21:24, 8 December 2009 (UTC)</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Talk:Infrastructure 2009-12-09T22:00:14Z

<p>Fvox13: /* Internet Access */</p> <hr /> <div>==Network Project==<br /> I would like to take the lead on this. I want to ask at the next meeting what people's needs are for network(s) and bandwidth [I know personally I'd like to play with some high bandwidth VoIP stuff, so the more bandwidth we can afford the better, imo] and see if what we have outlined on the [[Infrastructure]] page meshes with what everyone else was thinking. --[[User:Ben Woodruff|-- BW]] 20:20, 2 December 2009 (UTC)<br /> <br /> <br /> Care to tag-team this? --[[User:Fvox13|Fvox13]] 14:05, 3 December 2009 (UTC)<br /> <br /> Help is always appreciated, Carl mentioned wanting to help as well. --[[User:Ben Woodruff|-- BW]] 15:04, 3 December 2009 (UTC)<br /> <br /> ---- <br /> <br /> Ben, looks like you've got a good handle on this. Nicely detailed proposals. Thanks for stepping up to lead this.<br /> <br /> The chief thing that springs to mind with regard to the RFC1918 address space allocations is that consumer level devices, which I think it's safe to say we'll have on hand at one time or another, typically use at least two of those ranges preferentially. Apple Airport base stations tend to use addresses in the 10.0.0.0/8 range, and non-Apple devices often plop themselves down in the 192.168.0.0/16 range. <br /> <br /> My suggestion, then, is to use 172.16.0.0/12 range for all of our private networks. That way, if something shows a 192.168.x.y or 10.x.y.z address, we'll know right away that it's coming from something other than our stuff. <br /> <br /> In that light, I propose 172.20.x.y for the production network, partitioned further as you suggest (perhaps spacing things out by 10s in the third octet instead of by 1s, to give some room in between), 172.30.x.y for the warzone. The mnemonic I have in mind for this is that .20 is an &quot;even&quot; multiple of 10, even meaning &quot;smooth&quot; and smooth being what one wants from a production environment. In contrast, .30 is an &quot;odd&quot; multiple of 10, odd being exciting, unusual, or even dangerous, depending on one's perspective, but certainly what one would expect from a &quot;warzone&quot;. In between these two we'd have 172.25.x.y, which would be the playground--not expected to be at all dangerous, but you must be this tall to enter this ride. <br /> <br /> The 10.0.0.0/8 space is pretty big, even if Apple does use part of it. From what I recall and can tell from a quick search, they tend to use 10.0.1.x addresses. I think it might be a good convention to pick some portion of the 10.0.0.0/8 space and then to recommend that people use it for setting up their own independent test networks, eg, if they are building a private network on a single hardware host to use with a collection of virtual machines on that host. If their stuff stays on their own network, no big deal. If they screw up somehow and one of their devices ends up on our network, again, it'll be easy to tell because it is in this distinct 10.0.0.0 region. I think 10.100.0.0 would be easy to remember to use, and well away from Apple's use.<br /> <br /> Within 192.168.0.0, I've seen use all over the range. Some devices I've had use 192.168.0.x range. Some 192.168.254.x. The Linksys NSLU2 &quot;slugs&quot; use 192.168.1.77. And those are just the ones I'm familiar with and can recall off the top of my head. So, I think we just leave this for use with those devices.<br /> <br /> Anyway, that's my suggestion, based on my experience. You may have experience with devices that tend to default to 172.16.0.0 too, making this a less useful scheme, for instance. <br /> <br /> [[User:Deejoe|Deejoe]] 16:07, 5 December 2009 (UTC)<br /> <br /> ---- <br /> <br /> Thanks much for the feedback Deejoe. I like your ideas. I don't know of any devices that are using the 172.x.x.x range by default so that all sounds good.<br /> <br /> Also, Fvox13, good point about Cat6a. Lets shoot for Cat6 with the expectation that we will probably end up with a bunch of cat5e and limited cat6, which we'll probably want to use for core equipment that doesn't have other interconnects.<br /> --[[User:Ben Woodruff|-- BW]] 00:37, 6 December 2009 (UTC)<br /> <br /> ----<br /> <br /> == Infrastructure Questions ==<br /> I am going to put the questions about the environment and power over into this talk section, so we can try and clean up the main page a little bit more. [[User:Cmd3187|Cmd3187]] 18:22, 8 December 2009 (UTC)<br /> <br /> === Power ===<br /> *What is the capacity of the power system the space on?<br /> *Is it shared with other tenants?<br /> *What kind of emergency power/lighting does the building have?<br /> *Is it our responsibility or the landlord's to increase/change electrical capacity?<br /> <br /> '''If so:'''<br /> <br /> *Do we have access to the electrical panel or disconnect/fuses from within the space?<br /> *Can we run our own conduit/wall boxes? (Wall conduit to comply with fire code)<br /> <br /> === Environmental ===<br /> *How is the space heated in the winter?<br /> *How is the space cooled in the summer?<br /> *What is the RG&amp;E budget for the space (assuming it can give some indication of the cost of heating/cooling)?<br /> *Will humidity be a problem?<br /> <br /> == Internet Access ==<br /> Talking to John day about NFP discounts and possible packages for our building zone<br /> --[[User:Antitree|Antitree]] 19:27, 3 December 2009 (UTC) <br /> <br /> ----<br /> <br /> [http://www.fibertech.com/ Fibertech]: [http://en.wikipedia.org/wiki/Metro_Ethernet Metro Ethernet] network ends 1/2 mile from our location. :-( :-( :-( They would have to run a fair amount of fiber to service us. Rather than hit us with $25 - $30K for a buildout cost, they would be able to spread the cost over the course of a 3 or 5 year term (and we wouldn't have to pay *all* of that cost!) Still waiting for official quote, but it does sound expensive. --[[User:Fvox13|Fvox13]] 22:00, 9 December 2009 (UTC)<br /> <br /> ----<br /> <br /> [http://www.cogentco.com/us/ Cogent]: Offer [http://www.cogentco.com/us/pns_dedicated.php?Off off net] service by way of subcontracted T3 / sonet lines. Still waiting for quote, but I don't think they're a valid option, since the Fibertech guy says that Fibertech would be the subcontractor (!) and then Cogent would have to mark it up further. --[[User:Fvox13|Fvox13]] 21:35, 9 December 2009 (UTC)<br /> <br /> <br /> ----<br /> <br /> TW Telecom: Submitted a quote request. They offer Metro Ethernet as well. --[[User:Fvox13|Fvox13]] 21:35, 9 December 2009 (UTC)<br /> <br /> ----<br /> <br /> Frontier: Submitted a quote request. They offer Metro Ethernet, as well as more traditional telco solutions like DS1, DS3, DSL, etc. --[[User:Fvox13|Fvox13]] 22:00, 9 December 2009 (UTC)<br /> <br /> ----<br /> <br /> Based on what I saw in the temp space, *somebody* has *something* running to our building... we just have to figure out who and what!<br /> <br /> == Service Suggestions ==<br /> <br /> AirPort Express wireless AP (connected to stereo system for streaming music via AirTunes?)<br /> Can also act as a USB print server if we have a printer donated (USB is not the best option... we should consider an ethernet-enabled printer (maybe someone can donate?))<br /> --[[User:Ben Woodruff|Ben Woodruff]] 06:19, 2 December 2009 (UTC)<br /> <br /> ----<br /> <br /> Production network should have a more robust AP... maybe a Meru or Cisco? <br /> <br /> ----<br /> <br /> I agree, the problem is cost. I didn't see any mentions of a better AP on the donations page, so we may be stuck with what I've got for the time being. We will also probably want to offer guest wireless access at some point, through a different SSID, which will require an additional/different AP (the new Apple equipment can do it, but this one can't)<br /> <br /> ----<br /> <br /> I have a [http://www.vandis.com/docs/meru-ap100-ds.pdf Meru AP100] that I will be donating --[[User:Fvox13|Fvox13]] 18:23, 8 December 2009 (UTC)<br /> <br /> ----<br /> <br /> Does anyone know of a &quot;good&quot; captive portal type system like start.rit.edu or BlueSocket? I want something that can register MAC addresses with a DHCP server if proper credentials are supplied (auth w/ LDAP). Bonus points if it has optional static IP registration for servers and host management (remember which MACs belong to which users) --[[User:Ben Woodruff|-- BW]] 20:06, 8 December 2009 (UTC)<br /> <br /> ----<br /> <br /> I'm against captive portals, (Looks like you sort of agree, the way you said '&quot;good&quot; captive portal'), but [http://m0n0.ch/wall/ Monowall] might work --[[User:Fvox13|Fvox13]] 20:52, 8 December 2009 (UTC)<br /> <br /> ----<br /> <br /> You should be able to use something like PacketFence I would thing. That has an included registration system, so that the admin doesn't have to do as much. Here is a link to its [http://www.packetfence.org/tour/features.html Features]<br /> <br /> --[[User:Cmd3187|Cmd3187]] 21:11, 8 December 2009 (UTC)<br /> <br /> ----<br /> [http://nocat.net/ NoCatAuth] was developed for open-ish or community wireless networks. Might fit the bill. --[[User:Berticus|Berticus]] 21:24, 8 December 2009 (UTC)</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Infrastructure 2009-12-09T21:50:22Z

<p>Fvox13: /* Internet */</p> <hr /> <div>=Interlock Rochester Infrastructure=<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Sub-group !! Lead !! Members<br /> |-<br /> | Power ||<br /> |-<br /> | Environment ||<br /> |-<br /> | Security || [[User:Antitree|Mark Manning]]<br /> |-<br /> | [[Network Infrastructure Group|Network]] || [[User:Ben Woodruff|Ben Woodruff]] || [[User:fvox13|Steve Smith]]<br /> |-<br /> |}<br /> <br /> ''' NOTE''': This page contains information with regard to network/server setup for the final space, not the temporary one. For the temp space, power distribution can be done with extension cords, while network access will be ad-hoc in nature.<br /> <br /> =Power=<br /> Overhead cord reels are a solution, but they must not remain plugged in at their source when not in use in order to comply with fire code. Cable trays are not a good solution for power. (They are a pain in the ass.)<br /> <br /> =Environmental=<br /> The space will need to have environmental controls in the event that servers will be kept in location. The general operating temperature of servers and network equipment should be around 75F. In order to ensure this, the purchase of an AC system will be necessary.<br /> <br /> '''Things we may need to acquire:'''<br /> *&lt;s&gt;Heater&lt;/s&gt; &lt;-- Heat is included<br /> *Air Conditioner<br /> *Dehumidifier<br /> *&lt;s&gt;Thermostat/Thermometer&lt;/s&gt; &lt;-- Usually bundled with AC<br /> <br /> =Network=<br /> <br /> The network infrastructure group will create and maintain the [[network acceptable use policy]]. The policy will be approved by the board of directors and then signed by every member who wants access to any of the following networks.<br /> <br /> In order to meet the demands of the group over time, the network will be segregated into 3 main segments:<br /> * &lt;span style=&quot;color: green&quot;&gt;Production&lt;/span&gt;<br /> * &lt;span style=&quot;color: red&quot;&gt;Warzone&lt;/span&gt;<br /> * &lt;span style=&quot;color: gold&quot;&gt;Playground&lt;/span&gt;<br /> <br /> Each main segment will have an associated color code for its jacks (as is seen above), both on the walls, as well as near the network equipment. Category 6 cabling would be preferred for the environment. Each wall plate should be 6 feet apart, and should contain at least 1 of each colored jacks. Every jack should had 2 drops associated with it. <br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Network/Mask !! Name !! Description<br /> |-<br /> | '''172.20.0.0/16''' || '''Production''' || '''Supernet slice for all production networks'''<br /> |-<br /> | 172.20.0.0/24 || Core || Core Equipment (routers, switches, etc)<br /> |-<br /> | 172.20.10.0/24 || Servers || Servers (LDAP, DHCP, DNS, etc - assuming not provided by router)<br /> |-<br /> | 172.20.20.0/24 || Wired Hosts || Shared workstations<br /> |-<br /> | 172.20.30.0/24 || Wireless Hosts || Registered Member laptops<br /> |- <br /> | 172.20.50.0/24 || Wireless Guests || Event Participants, Class registrants, etc - May be partitioned into a separate network, see below<br /> |-<br /> | '''172.25.0.0/16''' || '''Playground''' || '''Network specific for individual projects. Should be sliced further to /24 and /26 networks as needed'''<br /> |- <br /> | '''172.30.0.0/16''' || '''Warzone''' || '''A place where invasive network attacks can occur. Will be a stub network with no regular Internet access'''<br /> |}<br /> <br /> <br /> == Internet ==<br /> <br /> === Time Warner Cable ===<br /> Per your request-we can provide bandwidth Tier of 5mbps/384Kbps at the following rate:<br /> 1 year $88.20<br /> 2 year $84.00<br /> 3 year $79.95<br /> Install fee of $75.00<br /> <br /> We can offer 5Mbps/768 Kbps:<br /> 1 year $140.70<br /> 2 year $133.85<br /> 3 year $126.95<br /> Install fee of $75.00<br /> <br /> Total Cost(1 yr): $163.20<br /> <br /> <br /> * We are in discussion with other ISPs, including Cogent, Fibertech, and TW Telecom. [[Talk:Infrastructure]]<br /> <br /> ==&lt;span style=&quot;color: green&quot;&gt;Production&lt;/span&gt;==<br /> The production network will be the main segment and will provide network access to Interlock's members. This network will be subdivided into 5 separate subnets, to help manage IP growth, and secure vital systems. The production network will not be used to perform penetration testing or other white hat hacking (port scans, IP sweeps, DoS, etc). The production network must have reliable uptime, as that other members will be dependent on it.<br /> <br /> === Change Control ===<br /> The infrastructure group will need to determine a method to log changes to the network. A consensus must be reached within the group before any change can be done on the production network. Change management will ''loosely'' follow [http://en.wikipedia.org/wiki/Change_Management_%28ITSM%29 ITIL Recommendations].<br /> <br /> === Access ===<br /> Access to core network equipment and topology will be restricted to those in the infrastructure group.<br /> <br /> === Services ===<br /> * RADIUS/LDAP Server<br /> ** Central Authentication repository<br /> ** Should be linked with Google Apps<br /> <br /> * Web Server<br /> ** Host the wiki, website, etc<br /> <br /> * CoLo Boxes<br /> ** Not intended to host production/high bandwidth websites<br /> ** Used for offsite backup<br /> <br /> * DHCP Server<br /> ** IP addresses will only be given out to know and trusted network adapters. <br /> ** A device registration system, like RIT's start.rit.edu, would be useful<br /> <br /> * DNS Server<br /> <br /> * File Server<br /> ** Access via SFTP, SMB, or WebDAV possibly<br /> <br /> * VPN Server<br /> ** Provide VPN access to the network. This needs to be decided as to whether this will be implemented, and the scope of the build.<br /> <br /> * Streaming Music Server<br /> ** Use a AirPort Extreme AP to play music via AirTunes<br /> <br /> * Image Server<br /> ** RIS or Ghost<br /> <br /> ==&lt;span style=&quot;color: red&quot;&gt;Warzone&lt;/span&gt;==<br /> * 172.30.x.y<br /> * No expectation of reliability<br /> * Relatively open access to equipment / no change management<br /> * No expectation of structure, very dynamic depending on project use etc, may use different IP address schemes if it doesn't connect to the other two networks in any way<br /> * Expect to have equipment probed / pen tested<br /> * No internet connectivity? Expect machines to be exploited / infected?<br /> * &quot;Rogue&quot; access points allowed (maybe include DHCP message that states you'd better be sure you want to connect to this network - want to be friendly with our neighbors)<br /> <br /> ==&lt;span style=&quot;color: gold&quot;&gt;Playground&lt;/span&gt;==<br /> * 172.25.x.y<br /> ** Each project should claim an address space (ie 172.25.15.y) so we can tell what traffic is coming from which projects<br /> * Temporary, dynamic, but more static and stable than the warzone<br /> * Change management much more loose than production network but there should be some expectation of reliability so please at least check with someone unless you're very sure of what you're doing<br /> * Access to the internet<br /> * Area to play with an test new technologies (for example, play with VOIP/SIP)<br /> <br /> == References ==<br /> * NEC 210.52<br /> <br /> =Physical Security=<br /> * We need to be able to &quot;deactivate&quot; keys, for non-payment etc<br /> * Multi-factor authentication (ie, fob + PIN)<br /> * Biometric stuff is really cool. Can we afford? [http://recognitionsystems.schlage.com/ Schlage Biometric systems]<br /> * Audit logging (twitter, website, dot matrix paper trail, etc)<br /> <br /> <br /> <br /> =Audio-Visual System=<br /> <br /> '''Audio'''<br /> *[http://www.bhphotovideo.com/c/product/541197-REG/Bogen_Communications_S810T725PG8W_Ceiling_Speaker_Assembly_with.html Public Address] system array across the ceiling<br /> *Two speakers rigged to the top corners of the room<br /> *Surround sound rigged to the top of the room (low priority)<br /> *Inputs to an audio mixer/home receiver<br /> *Sources: Microphone, CD/DVD, computers<br /> <br /> '''Video'''<br /> *Ceiling mounted projection<br /> *Screen<br /> *Sources: DVD, computers</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Projects 2009-12-09T21:48:10Z

<p>Fvox13: </p> <hr /> <div>== Ideas for projects==<br /> * I saw this high speed camera hack on wired science. It think this could be a cool project that wont take too long. There are detailed [http://www.pbs.org/kcet/wiredscience/story/68-high_speed_photos.html instructions on how to do this hack].<br /> * [http://www.evilmadscientist.com/article.php/bristlebot Bristle Bots]<br /> * [http://graffitiresearchlab.com/?page_id=6 Throwies]<br /> * [http://www.hactivist.com/flashpoint/ Flashpoint Cameras] - project a message on a wall for cheap<br /> * [http://www.waveprotocol.org/ Google Wave Server] - Openfire based?<br /> * Xen Cluster<br /> ** [http://www.oracle.com/us/technologies/virtualization/index.htm Oracle VM]<br /> ** [http://www.convirture.com/ ConVirt]<br /> * Kegerator - With a notification system for temp or something like that. Maybe via Twitter<br /> * Screenprinted T-shirts ([http://magicalnihilism.com/2009/11/07/get-excited-and-make-things/ This design] has been released for free. Perhaps put the hackerspace name on the back)<br /> * Capture The Flag InfoSec game<br /> * Old School BBS<br /> * Practically everything on [http://www.hackaday.com Hackaday] would be fair game<br /> <br /> == Hackerspace Security System ==<br /> <br /> Also see [[Infrastructure#Physical Security]]<br /> <br /> Description: The space will need a better way to keep track of who has access to come and go as they please. Keys are not an option. Key fob systems and other RFID technologies offer a way to control what a person has access to. <br /> <br /> Details: Construct a system that uses an RFID reader to grant access to the main door. The fob is also used to open other areas of the space depending on the member. OPTIONAL: build in a second factor authentication system. OPTIONAL: Construct a man trap so only one member can enter at a time. <br /> * RFID reader<br /> * fob<br /> ** [http://www.yubico.com/products/yubikey/ Yubikey] could be used with an old laptop on the cheap<br /> * electronic locks<br /> * server to manage ACLS (LDAP server? See [[Infrastructure#Network]])<br /> * second factor authentication system (biometrics, pin pad, TBD)<br /> <br /> === Comments ===<br /> RFID tags sound great to me. A swipe card would be tolerable, but I don't think those are too robust (not that RFID are perfect). A man trap sounds like a space-hog to me, and a little bit overzealous for our purposes, especially if we're going to have open sessions and classes and such. Maybe all members should just flash their badges even if the door is already open? We could tie this into the irc bot so people could query who is at the space. That'd sortof incentivize proper &quot;status updating&quot; with the door. --[[User:Berticus|Berticus]] 01:30, 29 November 2009 (UTC)<br /> <br /> == Reprap/Makerbot Build ==<br /> Description: Berticus really wants to tinker with 3d printing, and thus desires access to either a Makerbot or the next generation Reprap Mendel.<br /> <br /> Details: [http://makerbot.com/ Makerbots] can be purchased for $750 or $950. The higher price reflects some premium features, mainly pre-assembled electronics, a power supply, and some extra plastic filament. Bots are currently rather backordered. Mendel parts are impossible to find. There seem to be no kits out there for the non-extruded parts (threaded rod, etc.), so even if we can find somebody to print us the plastic bits, it'll still be a bit of a pain to get everything together. Right now a Makerbot is probably the way to go, and we can use that to print out the Mendel parts to make a second bot for experimentation (developing new print heads and such).<br /> <br /> === Comments ===<br /> <br /> <br /> == Ashley's Silly Web Projects ==<br /> BedBugsHotels.com &lt;- looking to collab with someone to build something like bedbugregistry.com but not as lame, using googlemaps. started the site in rails, but have not got very far with this. pretty sure there's traffic waiting for a well developed site along these lines, and it could be fun?<br /> <br /> hotpinkwedding.com &lt;- no one is going to be interested in this topic, per se. But I'm interested in using and learning about different techniques to boost serp via experimentation, if anyone is into that. 500-600 unique visitors a month currently.<br /> <br /> simplerochester.com &lt;- websites hosted on AWS. Looking to redevelop the business model in a unique way and mess around with marketing.<br /> <br /> <br /> == Electronics, parts, and keeping a bunch of stuff in stock ==<br /> Everyone who can afford it should buy one of each of these two boxes, and donate its contents to the space... plus we'll learn a *lot* just from sorting through the contents!<br /> * [http://www.goldmine-elec-products.com/prodinfo.asp?number=G17225 Ginormous Surprise Box]<br /> * [http://www.sciplus.com/recommend.cfm/recommendid/3501 Surprise Box of Science] (sounds like a Bill Nye thing... :-) )<br /> <br /> == INTERLOCK LED Windows ==<br /> Description: The windows at the temp space and the final space have double pane security glass. Light is diffused but one can imagine the possibilities<br /> <br /> Ideas:<br /> * Treat each pane as a pixel for pong, tetris, animated gifs, etc<br /> * Spell INTERLOCK in the glass<br /> * Game of Life pattern<br /> <br /> === Comments ===<br /> How many &quot;pixels&quot; do we have to work with? I seem to recall 3 high, maybe 12-16 long with a window interrupting four-ish blocks in the center. Letters are pretty tricky with just three vertical pixels. More abstract light patterns would be really cool though. --[[User:Berticus|Berticus]] 20:47, 8 December 2009 (UTC)<br /> <br /> == Official Friends of Interlock trophy ==<br /> Description: When we visit other hackerspaces or form partnerships with other organizations, it would be cool to give them something that came from the hackerspace. The idea being that it's hand made, geeky, and shows off the Interlock logo in some way. <br /> <br /> Ideas:<br /> * That was easy button re-recorded to say a private message and repainted to have our logo<br /> * Robot of some kind (for Felix)<br /> * Draudio Pen<br /> <br /> === Comments ===<br /> How about some sort of abstract object trophy, that's actually just a piece of a larger objects. The different hackerspaces that received them would have to get together to put the final &quot;trophy&quot; together. Or perhaps they'd all combine into Voltron or Captain Planet. Some such. Or, instead of getting physically together perhaps all the spaces would 3d scan their objects and combine them that way. There'd have to be something extra to thwart that... electronic contacts in each piece that &quot;networked&quot; the larger object perhaps. Ramble complete. --[[User:Berticus|Berticus]] 20:52, 8 December 2009 (UTC)<br /> <br /> == Interlock Dumpster Diving Crew ==<br /> Description: A group of people willing and able to drive around looking for things to pick up on garbage day or legal dumpsters to dive into. <br /> <br /> Members:<br /> * Brian<br /> * Mark<br /> * Josh<br /> * Jimmi<br /> <br /> Targets:<br /> * [http://tinyurl.com/ydsasyh RIT Boneyard]<br /> * RIT dumpsters all across campus after students move out (May of each year)<br /> <br /> <br /> == Interlock as an ISP ==<br /> There has been some debate about this, especially since we're doing the whole non-profit thing, but a non-profit *is* allowed to make money, as long as certain rules are followed.<br /> <br /> Basically, any Internet connection worth getting is going to be mucho expensive, and rather than get 30 new members just to pay for the Internet, it would make a lot of sense to resell it. Based on how expensive RoadRunner is in this building (probably what most of our neighbors have), and how crappy the speed is, I think we could undercut their price and still make it worthwhile to do this. I really want to run a fiber line into our space... the Internet is pretty much at the core of a lot of what we're doing, and we don't want it to be the weak link. But the options are looking like a.) Get 30 more members b.) Resell our connection or c.) Settle for something that is a lot slower than what most of us have at home.<br /> <br /> === Comments ===</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Talk:Infrastructure 2009-12-09T21:35:01Z

<p>Fvox13: /* Internet Access */</p> <hr /> <div>==Network Project==<br /> I would like to take the lead on this. I want to ask at the next meeting what people's needs are for network(s) and bandwidth [I know personally I'd like to play with some high bandwidth VoIP stuff, so the more bandwidth we can afford the better, imo] and see if what we have outlined on the [[Infrastructure]] page meshes with what everyone else was thinking. --[[User:Ben Woodruff|-- BW]] 20:20, 2 December 2009 (UTC)<br /> <br /> <br /> Care to tag-team this? --[[User:Fvox13|Fvox13]] 14:05, 3 December 2009 (UTC)<br /> <br /> Help is always appreciated, Carl mentioned wanting to help as well. --[[User:Ben Woodruff|-- BW]] 15:04, 3 December 2009 (UTC)<br /> <br /> ---- <br /> <br /> Ben, looks like you've got a good handle on this. Nicely detailed proposals. Thanks for stepping up to lead this.<br /> <br /> The chief thing that springs to mind with regard to the RFC1918 address space allocations is that consumer level devices, which I think it's safe to say we'll have on hand at one time or another, typically use at least two of those ranges preferentially. Apple Airport base stations tend to use addresses in the 10.0.0.0/8 range, and non-Apple devices often plop themselves down in the 192.168.0.0/16 range. <br /> <br /> My suggestion, then, is to use 172.16.0.0/12 range for all of our private networks. That way, if something shows a 192.168.x.y or 10.x.y.z address, we'll know right away that it's coming from something other than our stuff. <br /> <br /> In that light, I propose 172.20.x.y for the production network, partitioned further as you suggest (perhaps spacing things out by 10s in the third octet instead of by 1s, to give some room in between), 172.30.x.y for the warzone. The mnemonic I have in mind for this is that .20 is an &quot;even&quot; multiple of 10, even meaning &quot;smooth&quot; and smooth being what one wants from a production environment. In contrast, .30 is an &quot;odd&quot; multiple of 10, odd being exciting, unusual, or even dangerous, depending on one's perspective, but certainly what one would expect from a &quot;warzone&quot;. In between these two we'd have 172.25.x.y, which would be the playground--not expected to be at all dangerous, but you must be this tall to enter this ride. <br /> <br /> The 10.0.0.0/8 space is pretty big, even if Apple does use part of it. From what I recall and can tell from a quick search, they tend to use 10.0.1.x addresses. I think it might be a good convention to pick some portion of the 10.0.0.0/8 space and then to recommend that people use it for setting up their own independent test networks, eg, if they are building a private network on a single hardware host to use with a collection of virtual machines on that host. If their stuff stays on their own network, no big deal. If they screw up somehow and one of their devices ends up on our network, again, it'll be easy to tell because it is in this distinct 10.0.0.0 region. I think 10.100.0.0 would be easy to remember to use, and well away from Apple's use.<br /> <br /> Within 192.168.0.0, I've seen use all over the range. Some devices I've had use 192.168.0.x range. Some 192.168.254.x. The Linksys NSLU2 &quot;slugs&quot; use 192.168.1.77. And those are just the ones I'm familiar with and can recall off the top of my head. So, I think we just leave this for use with those devices.<br /> <br /> Anyway, that's my suggestion, based on my experience. You may have experience with devices that tend to default to 172.16.0.0 too, making this a less useful scheme, for instance. <br /> <br /> [[User:Deejoe|Deejoe]] 16:07, 5 December 2009 (UTC)<br /> <br /> ---- <br /> <br /> Thanks much for the feedback Deejoe. I like your ideas. I don't know of any devices that are using the 172.x.x.x range by default so that all sounds good.<br /> <br /> Also, Fvox13, good point about Cat6a. Lets shoot for Cat6 with the expectation that we will probably end up with a bunch of cat5e and limited cat6, which we'll probably want to use for core equipment that doesn't have other interconnects.<br /> --[[User:Ben Woodruff|-- BW]] 00:37, 6 December 2009 (UTC)<br /> <br /> ----<br /> <br /> == Infrastructure Questions ==<br /> I am going to put the questions about the environment and power over into this talk section, so we can try and clean up the main page a little bit more. [[User:Cmd3187|Cmd3187]] 18:22, 8 December 2009 (UTC)<br /> <br /> === Power ===<br /> *What is the capacity of the power system the space on?<br /> *Is it shared with other tenants?<br /> *What kind of emergency power/lighting does the building have?<br /> *Is it our responsibility or the landlord's to increase/change electrical capacity?<br /> <br /> '''If so:'''<br /> <br /> *Do we have access to the electrical panel or disconnect/fuses from within the space?<br /> *Can we run our own conduit/wall boxes? (Wall conduit to comply with fire code)<br /> <br /> === Environmental ===<br /> *How is the space heated in the winter?<br /> *How is the space cooled in the summer?<br /> *What is the RG&amp;E budget for the space (assuming it can give some indication of the cost of heating/cooling)?<br /> *Will humidity be a problem?<br /> <br /> == Internet Access ==<br /> Talking to John day about NFP discounts and possible packages for our building zone<br /> --[[User:Antitree|Antitree]] 19:27, 3 December 2009 (UTC) <br /> <br /> ----<br /> <br /> [http://www.fibertech.com/ Fibertech]: [http://en.wikipedia.org/wiki/Metro_Ethernet Metro Ethernet] network ends 1/2 mile from our location. :-( :-( :-( They would have to run a fair amount of fiber to service us. Rather than hit us with $25 - $30K for a buildout cost, they would be able to spread the cost over the course of a 3 or 5 year term (and we wouldn't have to pay *all* of that cost!) Still waiting for official quote, but it does sound expensive.<br /> <br /> ----<br /> <br /> [http://www.cogentco.com/us/ Cogent]: Offer [http://www.cogentco.com/us/pns_dedicated.php?Off off net] service by way of subcontracted T3 / sonet lines. Still waiting for quote, but I don't think they're a valid option, since the Fibertech guy says that Fibertech would be the subcontractor (!) and then Cogent would have to mark it up further. --[[User:Fvox13|Fvox13]] 21:35, 9 December 2009 (UTC)<br /> <br /> <br /> ----<br /> <br /> TW Telecom: Submitted a quote request. --[[User:Fvox13|Fvox13]] 21:35, 9 December 2009 (UTC)<br /> <br /> <br /> ----<br /> <br /> Based on what I saw in the temp space, *somebody* has *something* running to our building... we just have to figure out who and what!<br /> <br /> == Service Suggestions ==<br /> <br /> AirPort Express wireless AP (connected to stereo system for streaming music via AirTunes?)<br /> Can also act as a USB print server if we have a printer donated (USB is not the best option... we should consider an ethernet-enabled printer (maybe someone can donate?))<br /> --[[User:Ben Woodruff|Ben Woodruff]] 06:19, 2 December 2009 (UTC)<br /> <br /> ----<br /> <br /> Production network should have a more robust AP... maybe a Meru or Cisco? <br /> <br /> ----<br /> <br /> I agree, the problem is cost. I didn't see any mentions of a better AP on the donations page, so we may be stuck with what I've got for the time being. We will also probably want to offer guest wireless access at some point, through a different SSID, which will require an additional/different AP (the new Apple equipment can do it, but this one can't)<br /> <br /> ----<br /> <br /> I have a [http://www.vandis.com/docs/meru-ap100-ds.pdf Meru AP100] that I will be donating --[[User:Fvox13|Fvox13]] 18:23, 8 December 2009 (UTC)<br /> <br /> ----<br /> <br /> Does anyone know of a &quot;good&quot; captive portal type system like start.rit.edu or BlueSocket? I want something that can register MAC addresses with a DHCP server if proper credentials are supplied (auth w/ LDAP). Bonus points if it has optional static IP registration for servers and host management (remember which MACs belong to which users) --[[User:Ben Woodruff|-- BW]] 20:06, 8 December 2009 (UTC)<br /> <br /> ----<br /> <br /> I'm against captive portals, (Looks like you sort of agree, the way you said '&quot;good&quot; captive portal'), but [http://m0n0.ch/wall/ Monowall] might work --[[User:Fvox13|Fvox13]] 20:52, 8 December 2009 (UTC)<br /> <br /> ----<br /> <br /> You should be able to use something like PacketFence I would thing. That has an included registration system, so that the admin doesn't have to do as much. Here is a link to its [http://www.packetfence.org/tour/features.html Features]<br /> <br /> --[[User:Cmd3187|Cmd3187]] 21:11, 8 December 2009 (UTC)<br /> <br /> ----<br /> [http://nocat.net/ NoCatAuth] was developed for open-ish or community wireless networks. Might fit the bill. --[[User:Berticus|Berticus]] 21:24, 8 December 2009 (UTC)</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Bylaws 2009-12-09T20:38:55Z

<p>Fvox13: </p> <hr /> <div>Bylaws based on [http://wiki.hacdc.org/index.php/Bylaws HacDC]'s bylaws<br /> <br /> By law, this is the core governing document of Interlock Rochester. These bylaws were written to maximize the direct power of the membership as a whole, reducing the power of [[Board of Directors]] and the officers to as ceremonial and functional a role as possible.<br /> <br /> The Bylaws in effect are kept XXXXXXXXXX<br /> <br /> Amendments are handled as specified in [[#Article VII: Amendments | Article 7]]<br /> <br /> '''These Bylaws were approved by the [[Incorporators]] on XXXXXXX''' after consulting with prospective charter members.<br /> <br /> == Article I : Why We Exist ==<br /> <br /> === Section 1: General Purposes ===<br /> Interlock Rochester is a Not For Profit organization that focuses on providing a facility for its members to use to develop their personal interests in science, technology, and art in a collaborative, social environment. Projects include electronic engineering, computer programming, information security, wood working, crafts, digital art, technological research, and much more. The organization's space could be seen as a workshop, art studio, or open community lab. <br /> <br /> === Section 2: Specific Purposes ===<br /> Subject to and within the limits of Section 1, the corporation shall:<br /> # Provide a physical location that strives to afford the educational, technological, and collaborative requirements of its members<br /> # Collaborate on all forms of technology, culture, art and craft in new and interesting ways.<br /> #. Further the knowledge and experience of the public through talks, demonstrations, workshops, and public seminars pertaining to member crafts, skills, inventions, and discoveries.<br /> # Apply the results of its work to specific cultural, charitable and scientific causes.<br /> # Freely share its research and discoveries, using what is learned to teach others.<br /> # Recruit and develop talented members dedicated to these purposes.<br /> <br /> == Article II: Who We Are == <br /> <br /> === Section 1: Designation of Membership Classes ===<br /> <br /> Interlock Rochester has a voting membership class and a non-voting membership class.<br /> <br /> === Section 2: Voting Membership Class Qualifications ===<br /> <br /> Any person who supports the purposes laid out in Article I of these bylaws is qualified to become a member.<br /> <br /> === Section 3: Voting Membership Class Election ===<br /> <br /> Any member may nominate a qualified person to be a voting member. Any eligible person may be elected as a voting member at any regular meeting upon payment of their first periodic dues and visual approval of all members present. '''For purposes of these bylaws, all persons listed as [[Articles of Incorporation#Eighth Article : Names and Address of Members of the Initial Board of Directors | initial directors]] on the [[Articles of Incorporation | Articles of Incorporation]] shall be considered the initial voting members.'''<br /> <br /> === Section 4: Voting Membership Dues ===<br /> <br /> The amount, payment period, due date and acceptable methods for collection of dues shall be reviewed each year at the annual meeting. A majority vote of the members at any meeting may change the procedure and terms for payment of dues. Member dues may be waived for a three month period due to financial hardship or relocation by written petition signed by more than three quarters (3/4ths) of the Board of Directors. Payment of dues may be waived for any other reason only by voting members at a duly called meeting.<br /> <br /> === Section 5: Voting Membership Rights and Responsibilities ===<br /> <br /> Each voting member shall have an equal right to voice their opinion and vote their preference or abstain from voting in the affairs of the corporation. Each voting member shall exercise only one vote for each decision before the corporation. Votes should be exercised in person or via verifiable form of communication. Each voting member shall have reasonable inspection rights of corporate records. Each voting member shall be responsible for timely payment of dues, providing their current address, contact information, and preference for electronic receipt of communications. Each voting member is responsible for continuing to support the purposes of the corporation.<br /> <br /> === Section 6: Voting Membership Resignation and Termination ===<br /> <br /> Any voting member may resign by filing a written resignation with the Secretary. Resignation shall not relieve a voting member of unpaid dues or other monies owed. Voting membership may be suspended for non-payment of dues by the Treasurer. Any suspended voting member may restore their membership 90 days after suspension upon payment of dues owed and payable through one month beyond the end of the suspension period, or upon the granting of a dues waiver as outlined in Section 4. Voting membership may also be terminated for any reason by written petition signed by more than three quarters (3/4ths) of the voting members.<br /> <br /> === Section 7: Non-Voting Membership ===<br /> <br /> For fundraising and honorary purposes, the Treasurer may declare the qualifications for and appointment of non-voting members. Non-voting memberships and membership titles are subject to voting member approval. Non-voting members do not have the right to vote in affairs of the corporation nor do they have any responsibilities towards it. All other rights and responsibilities of non-voting members shall be explicitly stated by the Minister of Finance and subject to voting member approval, &lt;s&gt;except for the right to one (1) vegan chocolate chip cookie or a vegan baked good of equal or lesser nutritional value upon becoming a non-voting member.&lt;/s&gt;<br /> <br /> == Article III: How we meet ==<br /> <br /> === Section 1: Regular Meetings ===<br /> <br /> Regular meetings of voting members shall be held every First Tuesday at 19:30 local time at the registered office. A different meeting place may be designated by written petition signed by more than three quarters (3/4ths) of voting members. Regular meetings shall not take place on the day before, upon, or after a federal holiday unless specifically approved at the prior regular meeting or annual meeting. Meetings shall not take place on the day of a closure declared by the Office of Personnel Management.<br /> <br /> === Section 2: Annual Meetings ===<br /> <br /> An annual meeting of all members shall take place sometime in October, November, or December. The President shall select the date, time and place no later than November 30th of each year. The date, time and place of the annual meeting must be posted in the registered office and submitted to members electronically at least two weeks prior to the annual meeting. A petition signed by more than three quarters (3/4ths) of voting members and submitted to the Board of Directors before December 15th may specify a new date, time and place for the annual meeting. At the annual meeting, the voting members shall elect the Board of Directors, review and vote on the standing rules and policies of the corporation, receive reports on the activities of the corporation, approve the budget and determine the direction of corporation in the coming year.<br /> <br /> === Section 3: Special Meetings ===<br /> <br /> A petition presented to all voting members and signed by one third (1/3rd) of voting members may call a special meeting. Such a petition must include the date, time, place and agenda of the special meeting.<br /> <br /> === Section 4: Notice of Meetings ===<br /> <br /> The time and place of upcoming meetings shall be conspicuously posted at the registered office and electronically sent to all voting members. No notice is required for a regular meeting. Special meetings require 72 hours notice considered delivered only when all voting members are personally notified and given an opportunity to sign a special meeting petition.The agenda of the next upcoming meeting and minutes of the previous meeting shall be posted at the registered office and electronically submitted to all voting members at least 72 hours prior to any meeting.<br /> <br /> === Section 5: Quorum ===<br /> <br /> At a duly called meeting, at least 25% (one quarter) of the entire voting membership shall constitute a quorum.<br /> <br /> === Section 6: Voting ===<br /> <br /> When a quorum is present, all issues, except when otherwise specified in these bylaws, shall be decided by affirmative vote of more than 50% (one half) of the voting members present.<br /> <br /> === Section 7: Conduct of Meetings === <br /> <br /> All meetings shall follow the [[MIBS Simplified Rules of Coordinated Consensus through Chaos]] as approved at an annual meeting.<br /> <br /> == Article IV: The Officers ==<br /> <br /> === Section 1: Role, Number, Qualification, Term and Compensation ===<br /> <br /> There shall be four officers consisting of a President, Vice President, Secretary, and Treasurer. Each officer must be a voting member and each officer shall serve from the time of their election until their successor is elected and qualifies. No officer may serve more than 3 consecutive terms. No officer shall be compensated for their service as an officer, though the corporation may provide insurance and indemnity for officers as allowed by law.<br /> <br /> === Section 2: Duties of the President ===<br /> <br /> The President shall preside over all meetings or designate an alternate, attempt to achieve consensus in all decision-making, ensure the membership is informed of all relevant issues, and serve other duties of a President as required by law or custom.<br /> <br /> === Section 3: Duties of the Vice President ===<br /> <br /> The Vice President shall be primarily responsible for the information systems and communication processes of the corporation, coordinate the teams that manage and design those systems, draft policies and procedures for information system use, ensure effective communication and information exchange within the corporation, and serving all other duties of a Vice President as required by law or custom, including acting when the President is unable or unwilling to act. The Vice President shall assist the President in organizing meetings of the membership. He or she is responsible for enforcing the rules of meeting procedure as detailed in this documents. The Vice President is also responsible for providing notice of all meetings of the members and of the board of directors, pursuant to these bylaws.<br /> <br /> === Section 4: Duties of the Secretary ===<br /> <br /> The Secretary shall be responsible for membership records including membership and board meeting actions and petitions, sending out meeting announcements, posting and distributing copies of membership meeting minutes and relevant meeting agendas to the membership, assuring that corporate records are maintained, &lt;s&gt;assigning MIBS points to worthy members for a job well done&lt;/s&gt; and serving all other duties of a Secretary as required by law or custom.<br /> <br /> === Section 5: Duties of the Treasurer ===<br /> <br /> The Treasurer shall be custodian of corporate funds, collect dues, make a financial report for each meeting, assist in the preparation of the budget, '''develop fundraising plans''', make financial information available to members and the public, '''sneer at members who do not pay dues in a timely fashion and serve all other duties of a Treasurer as required by law or custom.'''<br /> <br /> === Section 6: Duties of the Officers as whole to provide an Annual Report ===<br /> <br /> The Ministers must prepare an annual report to be distributed at the annual meeting. The report should chronicle the activities of the corporation, including specific narratives on the corporation's work, the corporation's annual financial statements, relevant legal filings, and relevant copies of the organization's district and federal tax returns.<br /> <br /> === Section 7: Officers are Directors ===<br /> <br /> The Officers shall also serve as bona-fide directors on the Board of Directors. Election, resignation, removal and vacancies of the Ministers are handled in accordance with procedures laid out in Article V.<br /> <br /> == Article V: The Board of Directors ==<br /> <br /> === Section 1: Role, Size, Term and Compensation ===<br /> <br /> The board of directors shall consist of the four Officers as defined in Article IV and two at-large directors, all of whom are considered directors for the purposes of this article. All directors must be voting members of the corporation. Each director shall serve from the time of their election until their successor is elected and qualifies. No member may serve more than 3 consecutive terms on the board of directors. No director may be compensated for their service as a board member, though the corporation may provide insurance and indemnity for board members as allowed by law.<br /> <br /> === Section 2: Meetings ===<br /> <br /> The Board of Directors shall meet when necessary, provided all voting members receive notice sent electronically at least five business days prior to the meeting. All voting members may attend a meeting of the board of directors. The notice shall give the time, place, reason for calling the meeting and the agenda for said meeting. Notices shall be conspicuously posted at the registered office and electronically distributed to all members at least five business days prior to a meeting. Minutes shall follow the standing rules for meetings as approved at an annual meeting. Minutes of each board meeting shall be conspicuously posted at the registered office and electronically distributed to members within 48 hours. Minutes shall be considered approved when signed by all board members in attendance.<br /> <br /> === Section 3: Elections ===<br /> <br /> Each Voting Member present shall be given an opportunity to be a candidate for each officer position and each at-large director position on the board. If there is more than one candidate for an officer position, the candidate which obtains the highest number votes from voting members present shall be elected. If there are no candidates for an officer position, the outgoing officeholder may, if eligible, elect to serve another term or select any willing member to serve in that position. &lt;s&gt;If there is only one candidate for an officer position, the outgoing officeholder must perform a song chosen by the incoming officeholder at the karaoke bar of the incoming officeholder's choice.&lt;/s&gt; If fewer than two members are candidates for at-large director, those candidates are automatically elected and the remaining vacancies shall be filled by a random process selected by the outgoing Coordinator in Chief. If more than two members are candidates for at-large director, each voting member present shall rank the candidates. The two candidates obtaining the highest preferences from voting members present shall be elected. &lt;s&gt;If exactly two members are candidates for at-large director, the outgoing chairperson must immediately dance in a reasonably silly manner for at least two minutes.&lt;/s&gt;<br /> <br /> === Section 4: Quorum ===<br /> <br /> Two thirds of board members at a duly called board member meeting shall constitute a quorum.<br /> <br /> === Section 5: Voting ===<br /> <br /> All issues, except when otherwise specified in these bylaws, shall be decided by affirmative vote of more than half of the directors present at a duly held meeting.<br /> <br /> === Section 6: Resignation, Termination and Vacancies ===<br /> <br /> Any officer or director may resign by filing a written resignation with the Secretary or two other board members. An officer or at-large director may be terminated in their role by written petition signed by more than three quarters (3/4ths) of the voting membership. Vacancies on the board shall be filled at the next regular meeting using the applicable process outlined in Section 3.<br /> <br /> == Article VI: Committees ==<br /> <br /> &lt;s&gt;On or before September 30, the members shall nominate and approve an audit committee consisting of three voting members who are not members of the board of directors and have not served as a director for 180 days prior to appointment. The audit committee shall have full inspection rights to the affairs and documentation of the corporation. No audit committee shall be convened if the corporation has fewer than nine voting members. Otherwise, the board or voting members may not create committees or delegate their authority.&lt;/s&gt;<br /> <br /> <br /> == Article VII: Dissolution ==<br /> In the event of the dissolution of Interlock Rochester, the remaining members shall vote on a beneficiary to receive all remaining assets of the organization.<br /> <br /> <br /> == Article VIII: Amendments ==<br /> <br /> These bylaws may be amended only when an amendment proposal petition is approved at a membership meeting and signed by more than three quarters (3/4ths) of voting members. Written notice of such petition must be submitted electronically to all members and delivered to all members of the corporation physically in person or by registered mail to take effect.</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Ideas 2009-12-09T20:36:01Z

<p>Fvox13: /* Events */</p> <hr /> <div>This page can be anything. Please don't delete other peoples ideas and use the discussion tab at the top. <br /> <br /> == Structure ==<br /> How the hackerspace is managed<br /> * Form a corporation to hold money<br /> * Establish a bank account<br /> * Become a 501c3 non profit educational organization<br /> ** &lt;s&gt;Costs ($300)[http://www.hurwitassociates.com/l_s_initial_ny.php 1] &lt;/s&gt;<br /> ** Cost: $750 based on 5 year projection<br /> * &lt;s&gt;decide on officers and start paperwork&lt;/s&gt;<br /> ** Officers are decided, paperwork started<br /> * &lt;s&gt;Decide on dues<br /> ** All same price $$&lt;/s&gt;<br /> ** Dues decided: $50 normal, $35 + 6hrs required time donation w/ student discount<br /> * Members sign agreement to bylaws and insurance<br /> * Pay through PayPal<br /> ** Done: Setup 11/24 for donations paypal@interlockroc.org<br /> * &lt;s&gt;Decide whether to create a holding company for dues prior to 501(c)(3) completion&lt;/s&gt;<br /> ** Incorporation papers submitted on 11/25/09<br /> * Gather focus groups (e.g. home brewing, print screeners, photographers, network security) see classes<br /> * newsletter (blog, email, whatever)<br /> <br /> == Security ==<br /> * We need a way to determine who has access to what (no system should be accessible to only a single administrator)<br /> * W also need a secure way to share login information<br /> ** PGP/GPG is a popular option but OS X support is severely lacking<br /> <br /> == Membership Benefits ==<br /> * local discounts<br /> ** Goldcrest Electronics<br /> * 24x7 access to space<br /> * secret handshake<br /> * free or discounted admission to special events and classes<br /> * colo space (NOT for production sites)<br /> * very high speed internet<br /> ** Netsville<br /> ** Timewarner<br /> * Google Apps account at interlockroc.org<br /> <br /> == Events ==<br /> * Weekly open house<br /> * Flash mobs<br /> * Computer repair clinic<br /> * LAN parties<br /> * Parts swap<br /> * Group partnerships<br /> ** Rochester 2600<br /> ** Rochester Hackers<br /> ** Make Club<br /> ** OWASP<br /> * Geeky art exhibitions and gallery<br /> * Bike rides<br /> * Trips to nearby hackerspaces<br /> * Rake leaves<br /> * Kids robotic group<br /> * Bike repair<br /> * Computer repair<br /> * We sponsor events<br /> * United Rochester Hackers Convention(Multi-group uber meeting with OWASP, SPARSA, Geek Rochester, Pythonistas, Rochester Hackers, Rochester 2600, Make Club)<br /> * Lightning talks - 5 minutes to talk on one subject and move on<br /> * Geek prom<br /> <br /> == Classes ==<br /> * Programming<br /> ** Python<br /> ** Perl<br /> ** Ruby<br /> ** JAVA<br /> ** C++<br /> * Soldering<br /> * Arduino<br /> * Bookbinding? (Brian B. knows a bit about this)<br /> * 3d printing, CNC routing, Pen plotter tinkering<br /> * Screen Printing<br /> * Homebrewing (beer)?<br /> * Bike repair and modding ([http://www.ladyada.net/make/spokepov/ Spoke POV] kits, DIY headlamps)<br /> * DIY Instruments (cigar box ukulele, [http://www.vimeo.com/3913619 diy piezo pickups], theremins)<br /> * Photography <br /> ** controlling dSLRs via computers<br /> ** writing scripts for [http://chdk.wikia.com/wiki/CHDK CHDK] <br /> ** alternate firmware for many point and shoot digicams<br /> * Consumer router &quot;hacking&quot; (dd-wrt or tomato firmware flashing, how to optimize settings for your bittorrenting pleasure)<br /> * Programming in [http://processing.org/ Processing], and interfacing with the Arduino<br /> * Welding<br /> * Amateur radio related topics<br /> * Network Security/Forensics<br /> * Visual Data Analysis [http://secviz.org Secviz.org]<br /> * Linux (maybe partner with the Linux User Group of Rochester (LUGOR)<br /> * Learning about home renovation projects<br /> * Kids hardware classes (bristlebots)<br /> * Metasploit<br /> * VMware</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Infrastructure 2009-12-08T20:58:41Z

<p>Fvox13: </p> <hr /> <div>=Interlock Rochester Infrastructure=<br /> <br /> ''' NOTE''': This page contains information with regard to network/server setup for the final space, not the temporary one. For the temp space, power distribution can be done with extension cords, while network access will be ad-hoc in nature.<br /> <br /> {|<br /> |-<br /> ! Sub-group !! Lead<br /> |-<br /> | Power ||<br /> |-<br /> | Environment ||<br /> |-<br /> | Security || [[User:Antitree|Mark Manning]]<br /> |-<br /> | Network || [[User:Ben Woodruff|Ben Woodruff]]<br /> |-<br /> |}<br /> <br /> =Power=<br /> Overhead cord reels are a solution, but they must not remain plugged in at their source when not in use in order to comply with fire code. Cable trays are not a good solution for power. (They are a pain in the ass.)<br /> <br /> =Environmental=<br /> The space will need to have environmental controls in the event that servers will be kept in location. The general operating temperature of servers and network equipment should be around 75F. In order to ensure this, the purchase of an AC system will be necessary.<br /> <br /> '''Things we may need to acquire:'''<br /> *&lt;s&gt;Heater&lt;/s&gt; &lt;-- Heat is included<br /> *Air Conditioner<br /> *Dehumidifier<br /> *&lt;s&gt;Thermostat/Thermometer&lt;/s&gt; &lt;-- Usually bundled with AC<br /> <br /> =Network=<br /> In order to meet the demands of the group over time, the network will be segregated into 3 main segments:<br /> * &lt;span style=&quot;color: green&quot;&gt;Production&lt;/span&gt;<br /> * &lt;span style=&quot;color: red&quot;&gt;Warzone&lt;/span&gt;<br /> * &lt;span style=&quot;color: gold&quot;&gt;Playground&lt;/span&gt;<br /> <br /> Each main segment will have an associated color code for its jacks (as is seen above), both on the walls, as well as near the network equipment. Category 6 cabling would be preferred for the environment. Each wall plate should be 6 feet apart, and should contain at least 1 of each colored jacks. Every jack should had 2 drops associated with it. <br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Network/Mask !! Name !! Description<br /> |-<br /> | '''172.20.0.0/16''' || '''Production''' || '''Supernet slice for all production networks'''<br /> |-<br /> | 172.20.0.0/24 || Core || Core Equipment (routers, switches, etc)<br /> |-<br /> | 172.20.10.0/24 || Servers || Servers (LDAP, DHCP, DNS, etc - assuming not provided by router)<br /> |-<br /> | 172.20.20.0/24 || Wired Hosts || Shared workstations<br /> |-<br /> | 172.20.30.0/24 || Wireless Hosts || Registered Member laptops<br /> |- <br /> | 172.20.50.0/24 || Wireless Guests || Event Participants, Class registrants, etc - May be partitioned into a separate network, see below<br /> |-<br /> | '''172.25.0.0/16''' || '''Playground''' || '''Network specific for individual projects. Should be sliced further to /24 and /26 networks as needed'''<br /> |- <br /> | '''172.30.0.0/16''' || '''Warzone''' || '''A place where invasive network attacks can occur. Will be a stub network with no regular Internet access'''<br /> |}<br /> <br /> <br /> == Internet ==<br /> <br /> === Time Warner Cable ===<br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Package !! Download !! Upload !! Price<br /> |+ Most of these packages are only available in residential neighborhoods, oddly enough<br /> |-<br /> | Teleworker || 10 || 1.5 || $89.95<br /> |-<br /> | [https://www.twcbc.com/Rochester/Products/ProductDetails/home-business-solutions.ashx Home Business] || 15 || 2 || $109.95<br /> |}<br /> <br /> * We are in discussion with other ISPs, including Cogent and Fibertech. [[Talk:Infrastructure]]<br /> <br /> ==&lt;span style=&quot;color: green&quot;&gt;Production&lt;/span&gt;==<br /> The production network will be the main segment and will provide network access to Interlock's members. This network will be subdivided into 5 separate subnets, to help manage IP growth, and secure vital systems. The production network will not be used to perform penetration testing or other white hat hacking (port scans, IP sweeps, DoS, etc). The production network must have reliable uptime, as that other members will be dependent on it.<br /> <br /> === Change Control ===<br /> The infrastructure group will need to determine a method to log changes to the network. A consensus must be reached within the group before any change can be done on the production network. Change management will ''loosely'' follow [http://en.wikipedia.org/wiki/Change_Management_%28ITSM%29 ITIL Recommendations].<br /> <br /> === Access ===<br /> Access to core network equipment and topology will be restricted to those in the infrastructure group.<br /> <br /> === Services ===<br /> * RADIUS/LDAP Server<br /> ** Central Authentication repository<br /> ** Should be linked with Google Apps<br /> <br /> * Web Server<br /> ** Host the wiki, website, etc<br /> <br /> * CoLo Boxes<br /> ** Not intended to host production/high bandwidth websites<br /> ** Used for offsite backup<br /> <br /> * DHCP Server<br /> ** IP addresses will only be given out to know and trusted network adapters. <br /> ** A device registration system, like RIT's start.rit.edu, would be useful<br /> <br /> * DNS Server<br /> <br /> * File Server<br /> ** Access via SFTP, SMB, or WebDAV possibly<br /> <br /> * VPN Server<br /> ** Provide VPN access to the network. This needs to be decided as to whether this will be implemented, and the scope of the build.<br /> <br /> * Streaming Music Server<br /> ** Use a AirPort Extreme AP to play music via AirTunes<br /> <br /> * Image Server<br /> ** RIS or Ghost<br /> <br /> ==&lt;span style=&quot;color: red&quot;&gt;Warzone&lt;/span&gt;==<br /> * 172.30.x.y<br /> * No expectation of reliability<br /> * Relatively open access to equipment / no change management<br /> * No expectation of structure, very dynamic depending on project use etc, may use different IP address schemes if it doesn't connect to the other two networks in any way<br /> * Expect to have equipment probed / pen tested<br /> * No internet connectivity? Expect machines to be exploited / infected?<br /> * &quot;Rogue&quot; access points allowed (maybe include DHCP message that states you'd better be sure you want to connect to this network - want to be friendly with our neighbors)<br /> <br /> ==&lt;span style=&quot;color: gold&quot;&gt;Playground&lt;/span&gt;==<br /> * 172.25.x.y<br /> ** Each project should claim an address space (ie 172.25.15.y) so we can tell what traffic is coming from which projects<br /> * Temporary, dynamic, but more static and stable than the warzone<br /> * Change management much more loose than production network but there should be some expectation of reliability so please at least check with someone unless you're very sure of what you're doing<br /> * Access to the internet<br /> * Area to play with an test new technologies (for example, play with VOIP/SIP)<br /> <br /> == References ==<br /> * NEC 210.52<br /> <br /> =Physical Security=<br /> * We need to be able to &quot;deactivate&quot; keys, for non-payment etc<br /> * Multi-factor authentication (ie, fob + PIN)<br /> * Biometric stuff is really cool. Can we afford? [http://recognitionsystems.schlage.com/ Schlage Biometric systems]<br /> * Audit logging (twitter, website, dot matrix paper trail, etc)<br /> <br /> <br /> <br /> =Audio-Visual System=<br /> <br /> '''Audio'''<br /> *[http://www.bhphotovideo.com/c/product/541197-REG/Bogen_Communications_S810T725PG8W_Ceiling_Speaker_Assembly_with.html Public Address] system array across the ceiling<br /> *Two speakers rigged to the top corners of the room<br /> *Surround sound rigged to the top of the room (low priority)<br /> *Inputs to an audio mixer/home receiver<br /> *Sources: Microphone, CD/DVD, computers<br /> <br /> '''Video'''<br /> *Ceiling mounted projection<br /> *Screen<br /> *Sources: DVD, computers</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Talk:Infrastructure 2009-12-08T20:52:02Z

<p>Fvox13: </p> <hr /> <div>==Network Project==<br /> I would like to take the lead on this. I want to ask at the next meeting what people's needs are for network(s) and bandwidth [I know personally I'd like to play with some high bandwidth VoIP stuff, so the more bandwidth we can afford the better, imo] and see if what we have outlined on the [[Infrastructure]] page meshes with what everyone else was thinking. --[[User:Ben Woodruff|-- BW]] 20:20, 2 December 2009 (UTC)<br /> <br /> <br /> Care to tag-team this? --[[User:Fvox13|Fvox13]] 14:05, 3 December 2009 (UTC)<br /> <br /> Help is always appreciated, Carl mentioned wanting to help as well. --[[User:Ben Woodruff|-- BW]] 15:04, 3 December 2009 (UTC)<br /> <br /> ---- <br /> <br /> Ben, looks like you've got a good handle on this. Nicely detailed proposals. Thanks for stepping up to lead this.<br /> <br /> The chief thing that springs to mind with regard to the RFC1918 address space allocations is that consumer level devices, which I think it's safe to say we'll have on hand at one time or another, typically use at least two of those ranges preferentially. Apple Airport base stations tend to use addresses in the 10.0.0.0/8 range, and non-Apple devices often plop themselves down in the 192.168.0.0/16 range. <br /> <br /> My suggestion, then, is to use 172.16.0.0/12 range for all of our private networks. That way, if something shows a 192.168.x.y or 10.x.y.z address, we'll know right away that it's coming from something other than our stuff. <br /> <br /> In that light, I propose 172.20.x.y for the production network, partitioned further as you suggest (perhaps spacing things out by 10s in the third octet instead of by 1s, to give some room in between), 172.30.x.y for the warzone. The mnemonic I have in mind for this is that .20 is an &quot;even&quot; multiple of 10, even meaning &quot;smooth&quot; and smooth being what one wants from a production environment. In contrast, .30 is an &quot;odd&quot; multiple of 10, odd being exciting, unusual, or even dangerous, depending on one's perspective, but certainly what one would expect from a &quot;warzone&quot;. In between these two we'd have 172.25.x.y, which would be the playground--not expected to be at all dangerous, but you must be this tall to enter this ride. <br /> <br /> The 10.0.0.0/8 space is pretty big, even if Apple does use part of it. From what I recall and can tell from a quick search, they tend to use 10.0.1.x addresses. I think it might be a good convention to pick some portion of the 10.0.0.0/8 space and then to recommend that people use it for setting up their own independent test networks, eg, if they are building a private network on a single hardware host to use with a collection of virtual machines on that host. If their stuff stays on their own network, no big deal. If they screw up somehow and one of their devices ends up on our network, again, it'll be easy to tell because it is in this distinct 10.0.0.0 region. I think 10.100.0.0 would be easy to remember to use, and well away from Apple's use.<br /> <br /> Within 192.168.0.0, I've seen use all over the range. Some devices I've had use 192.168.0.x range. Some 192.168.254.x. The Linksys NSLU2 &quot;slugs&quot; use 192.168.1.77. And those are just the ones I'm familiar with and can recall off the top of my head. So, I think we just leave this for use with those devices.<br /> <br /> Anyway, that's my suggestion, based on my experience. You may have experience with devices that tend to default to 172.16.0.0 too, making this a less useful scheme, for instance. <br /> <br /> [[User:Deejoe|Deejoe]] 16:07, 5 December 2009 (UTC)<br /> <br /> ---- <br /> <br /> Thanks much for the feedback Deejoe. I like your ideas. I don't know of any devices that are using the 172.x.x.x range by default so that all sounds good.<br /> <br /> Also, Fvox13, good point about Cat6a. Lets shoot for Cat6 with the expectation that we will probably end up with a bunch of cat5e and limited cat6, which we'll probably want to use for core equipment that doesn't have other interconnects.<br /> --[[User:Ben Woodruff|-- BW]] 00:37, 6 December 2009 (UTC)<br /> <br /> ----<br /> <br /> == Infrastructure Questions ==<br /> I am going to put the questions about the environment and power over into this talk section, so we can try and clean up the main page a little bit more. [[User:Cmd3187|Cmd3187]] 18:22, 8 December 2009 (UTC)<br /> <br /> === Power ===<br /> *What is the capacity of the power system the space on?<br /> *Is it shared with other tenants?<br /> *What kind of emergency power/lighting does the building have?<br /> *Is it our responsibility or the landlord's to increase/change electrical capacity?<br /> <br /> '''If so:'''<br /> <br /> *Do we have access to the electrical panel or disconnect/fuses from within the space?<br /> *Can we run our own conduit/wall boxes? (Wall conduit to comply with fire code)<br /> <br /> === Environmental ===<br /> *How is the space heated in the winter?<br /> *How is the space cooled in the summer?<br /> *What is the RG&amp;E budget for the space (assuming it can give some indication of the cost of heating/cooling)?<br /> *Will humidity be a problem?<br /> <br /> == Internet Access ==<br /> Talking to John day about NFP discounts and possible packages for our building zone<br /> --[[User:Antitree|Antitree]] 19:27, 3 December 2009 (UTC) <br /> <br /> ----<br /> <br /> [http://www.fibertech.com/ Fibertech]: dedicated fiber circuit, instead of DOCSIS. I've submitted a request for a quote / more info... will update as I know more. <br /> --[[User:Fvox13|Fvox13]] 02:30, 5 December 2009 (UTC)<br /> <br /> ----<br /> <br /> My contact at Fibertech has been out of the office for the past couple of days. He will have a quote for us tomorrow. This would be through their [http://en.wikipedia.org/wiki/Metro_Ethernet Metro Ethernet] network. Sounds competitively priced... I think we should definitely hold off on the Internet decision until their quote comes through. <br /> --[[User:Fvox13|Fvox13]] 16:09, 8 December 2009 (UTC)<br /> <br /> ----<br /> <br /> [http://www.cogentco.com/us/ Cogent]: They don't appear to offer service in Rochester, but their fiber line goes through Rochester (on the way to Buffalo and Albany), and they offer &quot;[http://www.cogentco.com/us/pns_dedicated.php?Off off net]&quot; service by way of subcontracted T3 / sonet lines. <br /> --[[User:Fvox13|Fvox13]] 18:58, 5 December 2009 (UTC)<br /> <br /> ----<br /> <br /> Cogent is going to try and get a quote to me by Tuesday afternoon. Quote will cover 10 / 20 and 50 meg lines. <br /> --[[User:Fvox13|Fvox13]] 18:34, 7 December 2009 (UTC)<br /> <br /> == Service Suggestions ==<br /> <br /> AirPort Express wireless AP (connected to stereo system for streaming music via AirTunes?)<br /> Can also act as a USB print server if we have a printer donated (USB is not the best option... we should consider an ethernet-enabled printer (maybe someone can donate?))<br /> --[[User:Ben Woodruff|Ben Woodruff]] 06:19, 2 December 2009 (UTC)<br /> <br /> ----<br /> <br /> Production network should have a more robust AP... maybe a Meru or Cisco? <br /> <br /> ----<br /> <br /> I agree, the problem is cost. I didn't see any mentions of a better AP on the donations page, so we may be stuck with what I've got for the time being. We will also probably want to offer guest wireless access at some point, through a different SSID, which will require an additional/different AP (the new Apple equipment can do it, but this one can't)<br /> <br /> ----<br /> <br /> I have a [http://www.vandis.com/docs/meru-ap100-ds.pdf Meru AP100] that I will be donating --[[User:Fvox13|Fvox13]] 18:23, 8 December 2009 (UTC)<br /> <br /> ----<br /> <br /> Does anyone know of a &quot;good&quot; captive portal type system like start.rit.edu or BlueSocket? I want something that can register MAC addresses with a DHCP server if proper credentials are supplied (auth w/ LDAP). Bonus points if it has optional static IP registration for servers and host management (remember which MACs belong to which users) --[[User:Ben Woodruff|-- BW]] 20:06, 8 December 2009 (UTC)<br /> <br /> ----<br /> <br /> I'm against captive portals, (Looks like you sort of agree, the way you said '&quot;good&quot; captive portal'), but [http://m0n0.ch/wall/ Monowall] might work --[[User:Fvox13|Fvox13]] 20:52, 8 December 2009 (UTC)</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Infrastructure 2009-12-08T18:23:47Z

<p>Fvox13: /* Production */</p> <hr /> <div>=Infrastructure=<br /> <br /> ==Power==<br /> <br /> '''Questions:'''&lt;br&gt;<br /> *What is the capacity of the power system the space on?&lt;br&gt;<br /> *Is it shared with other tenants?&lt;br&gt;<br /> *What kind of emergency power/lighting does the building have?&lt;br&gt;<br /> *Is it our responsibility or the landlord's to increase/change electrical capacity?&lt;br&gt;<br /> '''If so:'''&lt;br&gt;<br /> *Do we have access to the electrical panel or disconnect/fuses from within the space?&lt;br&gt;<br /> *Can we run our own conduit/wall boxes? (Wall conduit to comply with fire code)&lt;br&gt;<br /> &lt;br&gt;<br /> Temporary power distribution can be done with extension cords. Overhead cord reels are a solution, but they must not remained plugged in at their source when not in use in order to comply with fire code. Cable trays are not a good solution for power. (They are a pain in the ass.)<br /> <br /> ==Environmental==<br /> <br /> '''Questions:'''<br /> *How is the space heated in the winter?<br /> *How is the space cooled in the summer?<br /> *What is the RG&amp;E budget for the space (assuming it can give some indication of the cost of heating/cooling)?<br /> *Will humidity be a problem?<br /> <br /> '''Things we may need to acquire:'''<br /> *Heater<br /> *Air Conditioner<br /> *Dehumidifier<br /> *Thermostat/Thermometer<br /> <br /> ==Network==<br /> * Project Lead: [[User:Ben Woodruff]] - assuming no one is opposed ([[Talk:Infrastructure]])<br /> * Networking in the temp space should be ad-hoc, at best. No sense investing in permanent infrastructure we'll be enjoying for a month.<br /> <br /> * Three distinct segregated networks<br /> * Separate colors of wires so we can tell at a glance which network we're plugging into (we can get colored keystone jacks, too)<br /> ** Production = Green<br /> ** Warzone = Red<br /> ** Playground = Yellow<br /> * Each network should also have a VERY different IP scheme<br /> ** Hey, there happen to be 3 private IP blocks in RFC 1918... 10.* 172.16-31.* and 192.168.*<br /> * Should be Cat 6 wired access, with drops throughout the space, no less than 6 feet apart (Similar to NEC 210.52)<br /> ** We want to limit the number of switches / hubs that are used beyond the core equipment, so it's better to be overkill here<br /> <br /> {|<br /> |-<br /> ! Network/Mask !! Name !! Description<br /> |-<br /> | '''172.20.0.0/16''' || '''Production''' || '''Supernet slice for all production networks'''<br /> |-<br /> | 172.20.0.0/24 || Core || Core Equipment (routers, switches, etc)<br /> |-<br /> | 172.20.10.0/24 || Servers || Servers (LDAP, DHCP, DNS, etc - assuming not provided by router)<br /> |-<br /> | 172.20.20.0/24 || Wired Hosts || Shared workstations<br /> |-<br /> | 172.20.30.0/24 || Wireless Hosts || Registered Member laptops<br /> |- <br /> | 172.20.50.0/24 || Wireless Guests || Event Participants, Class registrants, etc - May be partitioned into a separate network, see below<br /> |-<br /> | '''172.25.0.0/16''' || '''Playground''' || '''Network specific for individual projects. Should be sliced further to /24 and /26 networks as needed'''<br /> |- <br /> | '''172.30.0.0/16''' || '''Warzone''' || '''A place where invasive network attacks can occur. Will be a stub network'''<br /> |}<br /> <br /> === Internet ===<br /> * Time Warner Cable (not twtelcom)<br /> ** &quot;Teleworker&quot; Package: 10/1.5 $89.95 with a static IP<br /> ** &quot;Home Business&quot; Package: 15/2 $109.95 with a static IP [https://www.twcbc.com/Rochester/Products/ProductDetails/home-business-solutions.ashx]<br /> ** --[[User:Antitree|Antitree]] 19:27, 3 December 2009 (UTC) Talking to John day about NFP discounts and possible packages for our building zone<br /> ** Most of these packages are only available in residential neighborhoods, oddly enough<br /> * [http://www.fibertech.com/ Fibertech]: dedicated fiber circuit, instead of DOCSIS. I've submitted a request for a quote / more info... will update as I know more. --[[User:Fvox13|Fvox13]] 02:30, 5 December 2009 (UTC)<br /> ** My contact at Fibertech has been out of the office for the past couple of days. He will have a quote for us tomorrow. This would be through their [http://en.wikipedia.org/wiki/Metro_Ethernet Metro Ethernet] network. Sounds competitively priced... I think we should definitely hold off on the Internet decision until their quote comes through. --[[User:Fvox13|Fvox13]] 16:09, 8 December 2009 (UTC)<br /> * [http://www.cogentco.com/us/ Cogent]: They don't appear to offer service in Rochester, but their fiber line goes through Rochester (on the way to Buffalo and Albany), and they offer &quot;[http://www.cogentco.com/us/pns_dedicated.php?Off off net]&quot; service by way of subcontracted T3 / sonet lines. --[[User:Fvox13|Fvox13]] 18:58, 5 December 2009 (UTC)<br /> ** Cogent is going to try and get a quote to me by Tuesday afternoon. Quote will cover 10 / 20 and 50 meg lines. --[[User:Fvox13|Fvox13]] 18:34, 7 December 2009 (UTC)<br /> <br /> <br /> ===Production===<br /> * Change management - agreement of whatever group is going to be responsible for maintenance before making major changes<br /> * Access to core equipment limited to small group of network managers<br /> * No probing / pen testing<br /> * Reliable node-to-node and internet connectivity<br /> * Robust internally hosted network services (DHCP, DNS, SFTP, Images (RIS, Ghost), LDAP)<br /> ** Central LDAP host that contains authentication information for all members and is linked up with Google Apps<br /> ** Possibly a web server to host the wiki, website, etc<br /> ** Possibly light-weight co-lo boxes (offsite backup, etc) not intended to host production / high bandwidth websites (we will likely only have 1 external IP...)<br /> * AirPort Express wireless AP (connected to stereo system for streaming music via AirTunes?)<br /> ** Production network should have a more robust AP... maybe a Meru or Cisco? <br /> *** I agree, the problem is cost. I didn't see any mentions of a better AP on the donations page, so we may be stuck with what I've got for the time being. We will also probably want to offer guest wireless access at some point, through a different SSID, which will require an additional/different AP (the new Apple equipment can do it, but this one can't)<br /> ** I have a [http://www.vandis.com/docs/meru-ap100-ds.pdf Meru AP100] that I will be donating --[[User:Fvox13|Fvox13]] 18:23, 8 December 2009 (UTC)<br /> ** Can also act as a USB print server if we have a printer donated (USB is not the best option... we should consider an ethernet-enabled printer (maybe someone can donate?))<br /> ** Authentication through RADIUS + LDAP?<br /> * No unauthorized devices (APs, infected boxes, traffic sniffing tools, etc)<br /> ** Device registration system, like RIT's start.rit.edu ?<br /> * We have the ability to provide VPN access to this network. We will have to decide as a group if this is desirable and if it will be open to everyone or just the network management group<br /> <br /> ===Warzone===<br /> * 172.30.x.y<br /> * No expectation of reliability<br /> * Relatively open access to equipment / no change management<br /> * No expectation of structure, very dynamic depending on project use etc, may use different IP address schemes if it doesn't connect to the other two networks in any way<br /> * Expect to have equipment probed / pen tested<br /> * No internet connectivity? Expect machines to be exploited / infected?<br /> * &quot;Rogue&quot; access points allowed (maybe include DHCP message that states you'd better be sure you want to connect to this network - want to be friendly with our neighbors)<br /> <br /> ===Playground===<br /> * 172.25.x.y<br /> ** Each project should claim an address space (ie 172.25.15.y) so we can tell what traffic is coming from which projects<br /> * Temporary, dynamic, but more static and stable than the warzone<br /> * Change management much more loose than production network but there should be some expectation of reliability so please at least check with someone unless you're very sure of what you're doing<br /> * Access to the internet<br /> * Area to play with an test new technologies (for example, play with VOIP/SIP)<br /> <br /> ==Physical Security==<br /> * We need to be able to &quot;deactivate&quot; keys, for non-payment etc<br /> * Multi-factor authentication (ie, fob + PIN)<br /> * Biometric stuff is really cool. Can we afford? [http://recognitionsystems.schlage.com/ Schlage Biometric systems]<br /> * Audit logging (twitter, website, dot matrix paper trail, etc)<br /> <br /> <br /> <br /> ==Audio-Visual System==<br /> <br /> '''Audio'''<br /> *[http://www.bhphotovideo.com/c/product/541197-REG/Bogen_Communications_S810T725PG8W_Ceiling_Speaker_Assembly_with.html Public Address] system array across the ceiling<br /> *Two speakers rigged to the top corners of the room<br /> *Surround sound rigged to the top of the room<br /> *Inputs to an audio mixer/home receiver<br /> *Sources: Microphone, CD/DVD, computers<br /> <br /> '''Video'''<br /> *Ceiling mounted projection<br /> *Screen<br /> *Sources: DVD, computers</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Infrastructure 2009-12-08T16:14:53Z

<p>Fvox13: /* Network */</p> <hr /> <div>=Infrastructure=<br /> <br /> ==Power==<br /> <br /> '''Questions:'''&lt;br&gt;<br /> *What is the capacity of the power system the space on?&lt;br&gt;<br /> *Is it shared with other tenants?&lt;br&gt;<br /> *What kind of emergency power/lighting does the building have?&lt;br&gt;<br /> *Is it our responsibility or the landlord's to increase/change electrical capacity?&lt;br&gt;<br /> '''If so:'''&lt;br&gt;<br /> *Do we have access to the electrical panel or disconnect/fuses from within the space?&lt;br&gt;<br /> *Can we run our own conduit/wall boxes? (Wall conduit to comply with fire code)&lt;br&gt;<br /> &lt;br&gt;<br /> Temporary power distribution can be done with extension cords. Overhead cord reels are a solution, but they must not remained plugged in at their source when not in use in order to comply with fire code. Cable trays are not a good solution for power. (They are a pain in the ass.)<br /> <br /> ==Environmental==<br /> <br /> '''Questions:'''<br /> *How is the space heated in the winter?<br /> *How is the space cooled in the summer?<br /> *What is the RG&amp;E budget for the space (assuming it can give some indication of the cost of heating/cooling)?<br /> *Will humidity be a problem?<br /> <br /> '''Things we may need to acquire:'''<br /> *Heater<br /> *Air Conditioner<br /> *Dehumidifier<br /> *Thermostat/Thermometer<br /> <br /> ==Network==<br /> * Project Lead: [[User:Ben Woodruff]] - assuming no one is opposed ([[Talk:Infrastructure]])<br /> * Networking in the temp space should be ad-hoc, at best. No sense investing in permanent infrastructure we'll be enjoying for a month.<br /> <br /> * Three distinct segregated networks<br /> * Separate colors of wires so we can tell at a glance which network we're plugging into (we can get colored keystone jacks, too)<br /> ** Production = Green<br /> ** Warzone = Red<br /> ** Playground = Yellow<br /> * Each network should also have a VERY different IP scheme<br /> ** Hey, there happen to be 3 private IP blocks in RFC 1918... 10.* 172.16-31.* and 192.168.*<br /> * Should be Cat 6 wired access, with drops throughout the space, no less than 6 feet apart (Similar to NEC 210.52)<br /> ** We want to limit the number of switches / hubs that are used beyond the core equipment, so it's better to be overkill here<br /> <br /> <br /> === Internet ===<br /> * Time Warner Cable (not twtelcom)<br /> ** &quot;Teleworker&quot; Package: 10/1.5 $89.95 with a static IP<br /> ** &quot;Home Business&quot; Package: 15/2 $109.95 with a static IP [https://www.twcbc.com/Rochester/Products/ProductDetails/home-business-solutions.ashx]<br /> ** --[[User:Antitree|Antitree]] 19:27, 3 December 2009 (UTC) Talking to John day about NFP discounts and possible packages for our building zone<br /> ** Most of these packages are only available in residential neighborhoods, oddly enough<br /> * [http://www.fibertech.com/ Fibertech]: dedicated fiber circuit, instead of DOCSIS. I've submitted a request for a quote / more info... will update as I know more. --[[User:Fvox13|Fvox13]] 02:30, 5 December 2009 (UTC)<br /> ** My contact at Fibertech has been out of the office for the past couple of days. He will have a quote for us tomorrow. This would be through their [http://en.wikipedia.org/wiki/Metro_Ethernet Metro Ethernet] network. Sounds competitively priced... I think we should definitely hold off on the Internet decision until their quote comes through. --[[User:Fvox13|Fvox13]] 16:09, 8 December 2009 (UTC)<br /> * [http://www.cogentco.com/us/ Cogent]: They don't appear to offer service in Rochester, but their fiber line goes through Rochester (on the way to Buffalo and Albany), and they offer &quot;[http://www.cogentco.com/us/pns_dedicated.php?Off off net]&quot; service by way of subcontracted T3 / sonet lines. --[[User:Fvox13|Fvox13]] 18:58, 5 December 2009 (UTC)<br /> ** Cogent is going to try and get a quote to me by Tuesday afternoon. Quote will cover 10 / 20 and 50 meg lines. --[[User:Fvox13|Fvox13]] 18:34, 7 December 2009 (UTC)<br /> <br /> <br /> ===Production===<br /> * 172.20.x.y<br /> ** 172.20.0.y - core equipment (routers, switch management, etc)<br /> ** 172.20.10.y - servers (LDAP, DHCP, DNS, etc - assuming not provided by router)<br /> ** 172.20.20.y - wired hosts (shared workstation for research, etc?)<br /> ** 172.20.30.y - wireless hosts (member laptops)<br /> ** 172.20.50.y - wireless guests (event participants, class registrants, etc - may be partitioned into a separate network, see below)<br /> <br /> * Change management - agreement of whatever group is going to be responsible for maintenance before making major changes<br /> * Access to core equipment limited to small group of network managers<br /> * No probing / pen testing<br /> * Reliable node-to-node and internet connectivity<br /> * Robust internally hosted network services (DHCP, DNS, SFTP, Images (RIS, Ghost), LDAP)<br /> ** Central LDAP host that contains authentication information for all members and is linked up with Google Apps<br /> ** Possibly a web server to host the wiki, website, etc<br /> ** Possibly light-weight co-lo boxes (offsite backup, etc) not intended to host production / high bandwidth websites (we will likely only have 1 external IP...)<br /> * AirPort Express wireless AP (connected to stereo system for streaming music via AirTunes?)<br /> ** Production network should have a more robust AP... maybe a Meru or Cisco? <br /> *** I agree, the problem is cost. I didn't see any mentions of a better AP on the donations page, so we may be stuck with what I've got for the time being. We will also probably want to offer guest wireless access at some point, through a different SSID, which will require an additional/different AP (the new Apple equipment can do it, but this one can't)<br /> ** Can also act as a USB print server if we have a printer donated (USB is not the best option... we should consider an ethernet-enabled printer (maybe someone can donate?))<br /> ** Authentication through RADIUS + LDAP?<br /> * No unauthorized devices (APs, infected boxes, traffic sniffing tools, etc)<br /> ** Device registration system, like RIT's start.rit.edu ?<br /> * We have the ability to provide VPN access to this network. We will have to decide as a group if this is desirable and if it will be open to everyone or just the network management group<br /> <br /> ===Warzone===<br /> * 172.30.x.y<br /> * No expectation of reliability<br /> * Relatively open access to equipment / no change management<br /> * No expectation of structure, very dynamic depending on project use etc, may use different IP address schemes if it doesn't connect to the other two networks in any way<br /> * Expect to have equipment probed / pen tested<br /> * No internet connectivity? Expect machines to be exploited / infected?<br /> * &quot;Rogue&quot; access points allowed (maybe include DHCP message that states you'd better be sure you want to connect to this network - want to be friendly with our neighbors)<br /> <br /> ===Playground===<br /> * 172.25.x.y<br /> ** Each project should claim an address space (ie 172.25.15.y) so we can tell what traffic is coming from which projects<br /> * Temporary, dynamic, but more static and stable than the warzone<br /> * Change management much more loose than production network but there should be some expectation of reliability so please at least check with someone unless you're very sure of what you're doing<br /> * Access to the internet<br /> * Area to play with an test new technologies (for example, play with VOIP/SIP)<br /> <br /> ==Physical Security==<br /> * We need to be able to &quot;deactivate&quot; keys, for non-payment etc<br /> * Multi-factor authentication (ie, fob + PIN)<br /> * Biometric stuff is really cool. Can we afford? [http://recognitionsystems.schlage.com/ Schlage Biometric systems]<br /> * Audit logging (twitter, website, dot matrix paper trail, etc)<br /> <br /> <br /> <br /> ==Audio-Visual System==<br /> <br /> '''Audio'''<br /> *[http://www.bhphotovideo.com/c/product/541197-REG/Bogen_Communications_S810T725PG8W_Ceiling_Speaker_Assembly_with.html Public Address] system array across the ceiling<br /> *Two speakers rigged to the top corners of the room<br /> *Surround sound rigged to the top of the room<br /> *Inputs to an audio mixer/home receiver<br /> *Sources: Microphone, CD/DVD, computers<br /> <br /> '''Video'''<br /> *Ceiling mounted projection<br /> *Screen<br /> *Sources: DVD, computers</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Infrastructure 2009-12-08T16:13:28Z

<p>Fvox13: /* Internet */</p> <hr /> <div>=Infrastructure=<br /> <br /> ==Power==<br /> <br /> '''Questions:'''&lt;br&gt;<br /> *What is the capacity of the power system the space on?&lt;br&gt;<br /> *Is it shared with other tenants?&lt;br&gt;<br /> *What kind of emergency power/lighting does the building have?&lt;br&gt;<br /> *Is it our responsibility or the landlord's to increase/change electrical capacity?&lt;br&gt;<br /> '''If so:'''&lt;br&gt;<br /> *Do we have access to the electrical panel or disconnect/fuses from within the space?&lt;br&gt;<br /> *Can we run our own conduit/wall boxes? (Wall conduit to comply with fire code)&lt;br&gt;<br /> &lt;br&gt;<br /> Temporary power distribution can be done with extension cords. Overhead cord reels are a solution, but they must not remained plugged in at their source when not in use in order to comply with fire code. Cable trays are not a good solution for power. (They are a pain in the ass.)<br /> <br /> ==Environmental==<br /> <br /> '''Questions:'''<br /> *How is the space heated in the winter?<br /> *How is the space cooled in the summer?<br /> *What is the RG&amp;E budget for the space (assuming it can give some indication of the cost of heating/cooling)?<br /> *Will humidity be a problem?<br /> <br /> '''Things we may need to acquire:'''<br /> *Heater<br /> *Air Conditioner<br /> *Dehumidifier<br /> *Thermostat/Thermometer<br /> <br /> ==Network==<br /> * Project Lead: [[User:Ben Woodruff]] - assuming no one is opposed ([[Talk:Infrastructure]])<br /> * Networking in the temp space should be ad-hoc, at best. No sense investing in permanent infrastructure we'll be enjoying for a month.<br /> <br /> === Internet ===<br /> * Time Warner Cable (not twtelcom)<br /> ** &quot;Teleworker&quot; Package: 10/1.5 $89.95 with a static IP<br /> ** &quot;Home Business&quot; Package: 15/2 $109.95 with a static IP [https://www.twcbc.com/Rochester/Products/ProductDetails/home-business-solutions.ashx]<br /> ** --[[User:Antitree|Antitree]] 19:27, 3 December 2009 (UTC) Talking to John day about NFP discounts and possible packages for our building zone<br /> ** Most of these packages are only available in residential neighborhoods, oddly enough<br /> * [http://www.fibertech.com/ Fibertech]: dedicated fiber circuit, instead of DOCSIS. I've submitted a request for a quote / more info... will update as I know more. --[[User:Fvox13|Fvox13]] 02:30, 5 December 2009 (UTC)<br /> ** My contact at Fibertech has been out of the office for the past couple of days. He will have a quote for us tomorrow. This would be through their [http://en.wikipedia.org/wiki/Metro_Ethernet Metro Ethernet] network. Sounds competitively priced... I think we should definitely hold off on the Internet decision until their quote comes through. --[[User:Fvox13|Fvox13]] 16:09, 8 December 2009 (UTC)<br /> * [http://www.cogentco.com/us/ Cogent]: They don't appear to offer service in Rochester, but their fiber line goes through Rochester (on the way to Buffalo and Albany), and they offer &quot;[http://www.cogentco.com/us/pns_dedicated.php?Off off net]&quot; service by way of subcontracted T3 / sonet lines. --[[User:Fvox13|Fvox13]] 18:58, 5 December 2009 (UTC)<br /> ** Cogent is going to try and get a quote to me by Tuesday afternoon. Quote will cover 10 / 20 and 50 meg lines. --[[User:Fvox13|Fvox13]] 18:34, 7 December 2009 (UTC)<br /> <br /> <br /> * Three distinct segregated networks<br /> * Separate colors of wires so we can tell at a glance which network we're plugging into (we can get colored keystone jacks, too)<br /> ** Production = Green<br /> ** Warzone = Red<br /> ** Playground = Yellow<br /> * Each network should also have a VERY different IP scheme<br /> ** Hey, there happen to be 3 private IP blocks in RFC 1918... 10.* 172.16-31.* and 192.168.*<br /> * Should be Cat 6 wired access, with drops throughout the space, no less than 6 feet apart (Similar to NEC 210.52)<br /> ** We want to limit the number of switches / hubs that are used beyond the core equipment, so it's better to be overkill here<br /> <br /> ===Production===<br /> * 172.20.x.y<br /> ** 172.20.0.y - core equipment (routers, switch management, etc)<br /> ** 172.20.10.y - servers (LDAP, DHCP, DNS, etc - assuming not provided by router)<br /> ** 172.20.20.y - wired hosts (shared workstation for research, etc?)<br /> ** 172.20.30.y - wireless hosts (member laptops)<br /> ** 172.20.50.y - wireless guests (event participants, class registrants, etc - may be partitioned into a separate network, see below)<br /> <br /> * Change management - agreement of whatever group is going to be responsible for maintenance before making major changes<br /> * Access to core equipment limited to small group of network managers<br /> * No probing / pen testing<br /> * Reliable node-to-node and internet connectivity<br /> * Robust internally hosted network services (DHCP, DNS, SFTP, Images (RIS, Ghost), LDAP)<br /> ** Central LDAP host that contains authentication information for all members and is linked up with Google Apps<br /> ** Possibly a web server to host the wiki, website, etc<br /> ** Possibly light-weight co-lo boxes (offsite backup, etc) not intended to host production / high bandwidth websites (we will likely only have 1 external IP...)<br /> * AirPort Express wireless AP (connected to stereo system for streaming music via AirTunes?)<br /> ** Production network should have a more robust AP... maybe a Meru or Cisco? <br /> *** I agree, the problem is cost. I didn't see any mentions of a better AP on the donations page, so we may be stuck with what I've got for the time being. We will also probably want to offer guest wireless access at some point, through a different SSID, which will require an additional/different AP (the new Apple equipment can do it, but this one can't)<br /> ** Can also act as a USB print server if we have a printer donated (USB is not the best option... we should consider an ethernet-enabled printer (maybe someone can donate?))<br /> ** Authentication through RADIUS + LDAP?<br /> * No unauthorized devices (APs, infected boxes, traffic sniffing tools, etc)<br /> ** Device registration system, like RIT's start.rit.edu ?<br /> * We have the ability to provide VPN access to this network. We will have to decide as a group if this is desirable and if it will be open to everyone or just the network management group<br /> <br /> ===Warzone===<br /> * 172.30.x.y<br /> * No expectation of reliability<br /> * Relatively open access to equipment / no change management<br /> * No expectation of structure, very dynamic depending on project use etc, may use different IP address schemes if it doesn't connect to the other two networks in any way<br /> * Expect to have equipment probed / pen tested<br /> * No internet connectivity? Expect machines to be exploited / infected?<br /> * &quot;Rogue&quot; access points allowed (maybe include DHCP message that states you'd better be sure you want to connect to this network - want to be friendly with our neighbors)<br /> <br /> ===Playground===<br /> * 172.25.x.y<br /> ** Each project should claim an address space (ie 172.25.15.y) so we can tell what traffic is coming from which projects<br /> * Temporary, dynamic, but more static and stable than the warzone<br /> * Change management much more loose than production network but there should be some expectation of reliability so please at least check with someone unless you're very sure of what you're doing<br /> * Access to the internet<br /> * Area to play with an test new technologies (for example, play with VOIP/SIP)<br /> <br /> ==Physical Security==<br /> * We need to be able to &quot;deactivate&quot; keys, for non-payment etc<br /> * Multi-factor authentication (ie, fob + PIN)<br /> * Biometric stuff is really cool. Can we afford? [http://recognitionsystems.schlage.com/ Schlage Biometric systems]<br /> * Audit logging (twitter, website, dot matrix paper trail, etc)<br /> <br /> <br /> <br /> ==Audio-Visual System==<br /> <br /> '''Audio'''<br /> *[http://www.bhphotovideo.com/c/product/541197-REG/Bogen_Communications_S810T725PG8W_Ceiling_Speaker_Assembly_with.html Public Address] system array across the ceiling<br /> *Two speakers rigged to the top corners of the room<br /> *Surround sound rigged to the top of the room<br /> *Inputs to an audio mixer/home receiver<br /> *Sources: Microphone, CD/DVD, computers<br /> <br /> '''Video'''<br /> *Ceiling mounted projection<br /> *Screen<br /> *Sources: DVD, computers</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Infrastructure 2009-12-08T16:12:54Z

<p>Fvox13: /* Network */</p> <hr /> <div>=Infrastructure=<br /> <br /> ==Power==<br /> <br /> '''Questions:'''&lt;br&gt;<br /> *What is the capacity of the power system the space on?&lt;br&gt;<br /> *Is it shared with other tenants?&lt;br&gt;<br /> *What kind of emergency power/lighting does the building have?&lt;br&gt;<br /> *Is it our responsibility or the landlord's to increase/change electrical capacity?&lt;br&gt;<br /> '''If so:'''&lt;br&gt;<br /> *Do we have access to the electrical panel or disconnect/fuses from within the space?&lt;br&gt;<br /> *Can we run our own conduit/wall boxes? (Wall conduit to comply with fire code)&lt;br&gt;<br /> &lt;br&gt;<br /> Temporary power distribution can be done with extension cords. Overhead cord reels are a solution, but they must not remained plugged in at their source when not in use in order to comply with fire code. Cable trays are not a good solution for power. (They are a pain in the ass.)<br /> <br /> ==Environmental==<br /> <br /> '''Questions:'''<br /> *How is the space heated in the winter?<br /> *How is the space cooled in the summer?<br /> *What is the RG&amp;E budget for the space (assuming it can give some indication of the cost of heating/cooling)?<br /> *Will humidity be a problem?<br /> <br /> '''Things we may need to acquire:'''<br /> *Heater<br /> *Air Conditioner<br /> *Dehumidifier<br /> *Thermostat/Thermometer<br /> <br /> ==Network==<br /> * Project Lead: [[User:Ben Woodruff]] - assuming no one is opposed ([[Talk:Infrastructure]])<br /> * Networking in the temp space should be ad-hoc, at best. No sense investing in permanent infrastructure we'll be enjoying for a month.<br /> <br /> === Internet ===<br /> ** Time Warner Cable (not twtelcom)<br /> *** &quot;Teleworker&quot; Package: 10/1.5 $89.95 with a static IP<br /> *** &quot;Home Business&quot; Package: 15/2 $109.95 with a static IP [https://www.twcbc.com/Rochester/Products/ProductDetails/home-business-solutions.ashx]<br /> *** --[[User:Antitree|Antitree]] 19:27, 3 December 2009 (UTC) Talking to John day about NFP discounts and possible packages for our building zone<br /> *** Most of these packages are only available in residential neighborhoods, oddly enough<br /> ** [http://www.fibertech.com/ Fibertech]: dedicated fiber circuit, instead of DOCSIS. I've submitted a request for a quote / more info... will update as I know more. --[[User:Fvox13|Fvox13]] 02:30, 5 December 2009 (UTC)<br /> *** My contact at Fibertech has been out of the office for the past couple of days. He will have a quote for us tomorrow. This would be through their [http://en.wikipedia.org/wiki/Metro_Ethernet Metro Ethernet] network. Sounds competitively priced... I think we should definitely hold off on the Internet decision until their quote comes through. --[[User:Fvox13|Fvox13]] 16:09, 8 December 2009 (UTC)<br /> ** [http://www.cogentco.com/us/ Cogent]: They don't appear to offer service in Rochester, but their fiber line goes through Rochester (on the way to Buffalo and Albany), and they offer &quot;[http://www.cogentco.com/us/pns_dedicated.php?Off off net]&quot; service by way of subcontracted T3 / sonet lines. --[[User:Fvox13|Fvox13]] 18:58, 5 December 2009 (UTC)<br /> *** Cogent is going to try and get a quote to me by Tuesday afternoon. Quote will cover 10 / 20 and 50 meg lines. --[[User:Fvox13|Fvox13]] 18:34, 7 December 2009 (UTC)<br /> <br /> <br /> * Three distinct segregated networks<br /> * Separate colors of wires so we can tell at a glance which network we're plugging into (we can get colored keystone jacks, too)<br /> ** Production = Green<br /> ** Warzone = Red<br /> ** Playground = Yellow<br /> * Each network should also have a VERY different IP scheme<br /> ** Hey, there happen to be 3 private IP blocks in RFC 1918... 10.* 172.16-31.* and 192.168.*<br /> * Should be Cat 6 wired access, with drops throughout the space, no less than 6 feet apart (Similar to NEC 210.52)<br /> ** We want to limit the number of switches / hubs that are used beyond the core equipment, so it's better to be overkill here<br /> <br /> ===Production===<br /> * 172.20.x.y<br /> ** 172.20.0.y - core equipment (routers, switch management, etc)<br /> ** 172.20.10.y - servers (LDAP, DHCP, DNS, etc - assuming not provided by router)<br /> ** 172.20.20.y - wired hosts (shared workstation for research, etc?)<br /> ** 172.20.30.y - wireless hosts (member laptops)<br /> ** 172.20.50.y - wireless guests (event participants, class registrants, etc - may be partitioned into a separate network, see below)<br /> <br /> * Change management - agreement of whatever group is going to be responsible for maintenance before making major changes<br /> * Access to core equipment limited to small group of network managers<br /> * No probing / pen testing<br /> * Reliable node-to-node and internet connectivity<br /> * Robust internally hosted network services (DHCP, DNS, SFTP, Images (RIS, Ghost), LDAP)<br /> ** Central LDAP host that contains authentication information for all members and is linked up with Google Apps<br /> ** Possibly a web server to host the wiki, website, etc<br /> ** Possibly light-weight co-lo boxes (offsite backup, etc) not intended to host production / high bandwidth websites (we will likely only have 1 external IP...)<br /> * AirPort Express wireless AP (connected to stereo system for streaming music via AirTunes?)<br /> ** Production network should have a more robust AP... maybe a Meru or Cisco? <br /> *** I agree, the problem is cost. I didn't see any mentions of a better AP on the donations page, so we may be stuck with what I've got for the time being. We will also probably want to offer guest wireless access at some point, through a different SSID, which will require an additional/different AP (the new Apple equipment can do it, but this one can't)<br /> ** Can also act as a USB print server if we have a printer donated (USB is not the best option... we should consider an ethernet-enabled printer (maybe someone can donate?))<br /> ** Authentication through RADIUS + LDAP?<br /> * No unauthorized devices (APs, infected boxes, traffic sniffing tools, etc)<br /> ** Device registration system, like RIT's start.rit.edu ?<br /> * We have the ability to provide VPN access to this network. We will have to decide as a group if this is desirable and if it will be open to everyone or just the network management group<br /> <br /> ===Warzone===<br /> * 172.30.x.y<br /> * No expectation of reliability<br /> * Relatively open access to equipment / no change management<br /> * No expectation of structure, very dynamic depending on project use etc, may use different IP address schemes if it doesn't connect to the other two networks in any way<br /> * Expect to have equipment probed / pen tested<br /> * No internet connectivity? Expect machines to be exploited / infected?<br /> * &quot;Rogue&quot; access points allowed (maybe include DHCP message that states you'd better be sure you want to connect to this network - want to be friendly with our neighbors)<br /> <br /> ===Playground===<br /> * 172.25.x.y<br /> ** Each project should claim an address space (ie 172.25.15.y) so we can tell what traffic is coming from which projects<br /> * Temporary, dynamic, but more static and stable than the warzone<br /> * Change management much more loose than production network but there should be some expectation of reliability so please at least check with someone unless you're very sure of what you're doing<br /> * Access to the internet<br /> * Area to play with an test new technologies (for example, play with VOIP/SIP)<br /> <br /> ==Physical Security==<br /> * We need to be able to &quot;deactivate&quot; keys, for non-payment etc<br /> * Multi-factor authentication (ie, fob + PIN)<br /> * Biometric stuff is really cool. Can we afford? [http://recognitionsystems.schlage.com/ Schlage Biometric systems]<br /> * Audit logging (twitter, website, dot matrix paper trail, etc)<br /> <br /> <br /> <br /> ==Audio-Visual System==<br /> <br /> '''Audio'''<br /> *[http://www.bhphotovideo.com/c/product/541197-REG/Bogen_Communications_S810T725PG8W_Ceiling_Speaker_Assembly_with.html Public Address] system array across the ceiling<br /> *Two speakers rigged to the top corners of the room<br /> *Surround sound rigged to the top of the room<br /> *Inputs to an audio mixer/home receiver<br /> *Sources: Microphone, CD/DVD, computers<br /> <br /> '''Video'''<br /> *Ceiling mounted projection<br /> *Screen<br /> *Sources: DVD, computers</div>

Fvox13 http://www.interlockroc.org/wiki/index.php/Infrastructure 2009-12-08T16:09:07Z

<p>Fvox13: </p> <hr /> <div>=Infrastructure=<br /> <br /> ==Power==<br /> <br /> '''Questions:'''&lt;br&gt;<br /> *What is the capacity of the power system the space on?&lt;br&gt;<br /> *Is it shared with other tenants?&lt;br&gt;<br /> *What kind of emergency power/lighting does the building have?&lt;br&gt;<br /> *Is it our responsibility or the landlord's to increase/change electrical capacity?&lt;br&gt;<br /> '''If so:'''&lt;br&gt;<br /> *Do we have access to the electrical panel or disconnect/fuses from within the space?&lt;br&gt;<br /> *Can we run our own conduit/wall boxes? (Wall conduit to comply with fire code)&lt;br&gt;<br /> &lt;br&gt;<br /> Temporary power distribution can be done with extension cords. Overhead cord reels are a solution, but they must not remained plugged in at their source when not in use in order to comply with fire code. Cable trays are not a good solution for power. (They are a pain in the ass.)<br /> <br /> ==Environmental==<br /> <br /> '''Questions:'''<br /> *How is the space heated in the winter?<br /> *How is the space cooled in the summer?<br /> *What is the RG&amp;E budget for the space (assuming it can give some indication of the cost of heating/cooling)?<br /> *Will humidity be a problem?<br /> <br /> '''Things we may need to acquire:'''<br /> *Heater<br /> *Air Conditioner<br /> *Dehumidifier<br /> *Thermostat/Thermometer<br /> <br /> ==Network==<br /> * Project Lead: [[User:Ben Woodruff]] - assuming no one is opposed ([[Talk:Infrastructure]])<br /> * Networking in the temp space should be ad-hoc, at best. No sense investing in permanent infrastructure we'll be enjoying for a month.<br /> <br /> * Internet<br /> ** Time Warner Cable (not twtelcom)<br /> *** &quot;Teleworker&quot; Package: 10/1.5 $89.95 with a static IP<br /> *** &quot;Home Business&quot; Package: 15/2 $109.95 with a static IP [https://www.twcbc.com/Rochester/Products/ProductDetails/home-business-solutions.ashx]<br /> *** --[[User:Antitree|Antitree]] 19:27, 3 December 2009 (UTC) Talking to John day about NFP discounts and possible packages for our building zone<br /> ** Talking to [http://www.fibertech.com/ Fibertech] as well. This would be a dedicated fiber circuit, instead of DOCSIS. I've submitted a request for a quote / more info... will update as I know more. --[[User:Fvox13|Fvox13]] 02:30, 5 December 2009 (UTC)<br /> *** My contact at Fibertech has been out of the office for the past couple of days. He will have a quote for us tomorrow. This would be through their [http://en.wikipedia.org/wiki/Metro_Ethernet Metro Ethernet] network. Sounds competitively priced... I think we should definitely hold off on the Internet decision until their quote comes through. --[[User:Fvox13|Fvox13]] 16:09, 8 December 2009 (UTC)<br /> ** I'm also talking with [http://www.cogentco.com/us/ Cogent]. They don't appear to offer service in Rochester, but their fiber line goes through Rochester (on the way to Buffalo and Albany), and they offer &quot;[http://www.cogentco.com/us/pns_dedicated.php?Off off net]&quot; service by way of subcontracted T3 / sonet lines. --[[User:Fvox13|Fvox13]] 18:58, 5 December 2009 (UTC)<br /> *** Cogent is going to try and get a quote to me by Tuesday afternoon. Quote will cover 10 / 20 and 50 meg lines. --[[User:Fvox13|Fvox13]] 18:34, 7 December 2009 (UTC)<br /> <br /> <br /> * Three distinct segregated networks<br /> * Separate colors of wires so we can tell at a glance which network we're plugging into (we can get colored keystone jacks, too)<br /> ** Production = Green<br /> ** Warzone = Red<br /> ** Playground = Yellow<br /> * Each network should also have a VERY different IP scheme<br /> ** Hey, there happen to be 3 private IP blocks in RFC 1918... 10.* 172.16-31.* and 192.168.*<br /> * Should be Cat 6 wired access, with drops throughout the space, no less than 6 feet apart (Similar to NEC 210.52)<br /> ** We want to limit the number of switches / hubs that are used beyond the core equipment, so it's better to be overkill here<br /> <br /> ===Production===<br /> * 172.20.x.y<br /> ** 172.20.0.y - core equipment (routers, switch management, etc)<br /> ** 172.20.10.y - servers (LDAP, DHCP, DNS, etc - assuming not provided by router)<br /> ** 172.20.20.y - wired hosts (shared workstation for research, etc?)<br /> ** 172.20.30.y - wireless hosts (member laptops)<br /> ** 172.20.50.y - wireless guests (event participants, class registrants, etc - may be partitioned into a separate network, see below)<br /> <br /> * Change management - agreement of whatever group is going to be responsible for maintenance before making major changes<br /> * Access to core equipment limited to small group of network managers<br /> * No probing / pen testing<br /> * Reliable node-to-node and internet connectivity<br /> * Robust internally hosted network services (DHCP, DNS, SFTP, Images (RIS, Ghost), LDAP)<br /> ** Central LDAP host that contains authentication information for all members and is linked up with Google Apps<br /> ** Possibly a web server to host the wiki, website, etc<br /> ** Possibly light-weight co-lo boxes (offsite backup, etc) not intended to host production / high bandwidth websites (we will likely only have 1 external IP...)<br /> * AirPort Express wireless AP (connected to stereo system for streaming music via AirTunes?)<br /> ** Production network should have a more robust AP... maybe a Meru or Cisco? <br /> *** I agree, the problem is cost. I didn't see any mentions of a better AP on the donations page, so we may be stuck with what I've got for the time being. We will also probably want to offer guest wireless access at some point, through a different SSID, which will require an additional/different AP (the new Apple equipment can do it, but this one can't)<br /> ** Can also act as a USB print server if we have a printer donated (USB is not the best option... we should consider an ethernet-enabled printer (maybe someone can donate?))<br /> ** Authentication through RADIUS + LDAP?<br /> * No unauthorized devices (APs, infected boxes, traffic sniffing tools, etc)<br /> ** Device registration system, like RIT's start.rit.edu ?<br /> * We have the ability to provide VPN access to this network. We will have to decide as a group if this is desirable and if it will be open to everyone or just the network management group<br /> <br /> ===Warzone===<br /> * 172.30.x.y<br /> * No expectation of reliability<br /> * Relatively open access to equipment / no change management<br /> * No expectation of structure, very dynamic depending on project use etc, may use different IP address schemes if it doesn't connect to the other two networks in any way<br /> * Expect to have equipment probed / pen tested<br /> * No internet connectivity? Expect machines to be exploited / infected?<br /> * &quot;Rogue&quot; access points allowed (maybe include DHCP message that states you'd better be sure you want to connect to this network - want to be friendly with our neighbors)<br /> <br /> ===Playground===<br /> * 172.25.x.y<br /> ** Each project should claim an address space (ie 172.25.15.y) so we can tell what traffic is coming from which projects<br /> * Temporary, dynamic, but more static and stable than the warzone<br /> * Change management much more loose than production network but there should be some expectation of reliability so please at least check with someone unless you're very sure of what you're doing<br /> * Access to the internet<br /> * Area to play with an test new technologies (for example, play with VOIP/SIP)<br /> <br /> ==Physical Security==<br /> * We need to be able to &quot;deactivate&quot; keys, for non-payment etc<br /> * Multi-factor authentication (ie, fob + PIN)<br /> * Biometric stuff is really cool. Can we afford? [http://recognitionsystems.schlage.com/ Schlage Biometric systems]<br /> * Audit logging (twitter, website, dot matrix paper trail, etc)<br /> <br /> <br /> <br /> ==Audio-Visual System==<br /> <br /> '''Audio'''<br /> *[http://www.bhphotovideo.com/c/product/541197-REG/Bogen_Communications_S810T725PG8W_Ceiling_Speaker_Assembly_with.html Public Address] system array across the ceiling<br /> *Two speakers rigged to the top corners of the room<br /> *Surround sound rigged to the top of the room<br /> *Inputs to an audio mixer/home receiver<br /> *Sources: Microphone, CD/DVD, computers<br /> <br /> '''Video'''<br /> *Ceiling mounted projection<br /> *Screen<br /> *Sources: DVD, computers</div>

Fvox13