http://wiki.freegeek.org/api.php?action=feedcontributions&user=Alamb&feedformat=atomFreekiWiki - User contributions [en]2024-03-29T08:53:29ZUser contributionsMediaWiki 1.35.1http://wiki.freegeek.org/index.php?title=2012_December_Newsletter&diff=656302012 December Newsletter2012-12-21T01:54:44Z<p>Alamb: /* Free Geek Charitable Contributions 101 */</p>
<hr />
<div>==The Freekbox Gets a Makeover==<br />
If you visited Free Geek on December 4 and heard disco music blaring while volunteers and staff competed head-to-head on Super Tux Kart in the classroom (yes, it’s an open source game very similar to Super Mario Kart), you luckily stumbled into the Holi-Distro party. Generally, our holiday party is a chance to unwind with other Free Geek community members, perhaps participate in a white elephant gift exchange, and celebrate the many accomplishments of the year. This year though, things were a little different as we were also celebrating the release of a new Linux distribution on Free Geek computers.<br />
<br />
Linux, an open-source operating system, has many different distributions (http://en.wikipedia.org/wiki/Linux_distros#Popular_distributions), or distros, maintained by various groups throughout the world. Each of these distros is updated, much like you see on other proprietary operating systems, on a regular basis. Since 2006, Free Geek has used Ubuntu (http://www.ubuntu.com/), currently the most widely-adopted version of Linux, on all of our computers with an operating system. We chose this version for its ease of use and the robust support afforded by the greater Linux community and Canonical, the company responsible for Ubuntu Linux. Unfortunately, the version of Ubuntu we’ve been using since 2010, 10.04 Lucid Lynx, will only be officially supported until April, 2013. To plan for this transition, several Free Geek staff and interns formed the Distro Committee to research, test, de-bug, and document the next version of Linux for our computers.<br />
<br />
First, the committee set out to define priorities for the new operating system. We talked to representatives of various areas of Free Geek including Tech Support, the Build Program, Education, and the Thrift Store. We also polled a wide cross-section of our computer users to discover what was important to them and how they use their computers. Major priorities for this new distro included a long support cycle (so we wouldn’t have to go through this process too often), compatibility with a wide range of old and new computer systems, and ease of use for both beginners and experienced computer users. Armed with these criteria, our intrepid Distro Interns began exploring and testing many of the various available Linux distributions. (Find out more about one of the lead Distro Interns, Ben Koening, in this newsletter’s Volunteer Spotlight (http://www.freegeek.org/newsletter/2012/12/volunteer-spotlight-ben-koenig/.))<br />
<br />
After collecting tons of data on various distributions, the intern team ultimately recommended that Free Geek adopt Xubuntu 12.04 (http://xubuntu.org/) (although it’s officially pronounced “zoo-bun-too”, plenty of people call it “ex-oo-bun-too”.) As you can likely tell from the name, this is a branch of the original Ubuntu distro. Unlike Ubuntu 12.04, which comes with the new-to-users Unity Interface (http://unity.ubuntu.com/), Xubuntu uses Xfce (http://www.xfce.org/) to control the way the operating system looks. This version was selected for many reasons including the same five-year support of Ubuntu 12.04, speed on both old and new systems, and an interface very similar to the one our users became familiar with in Ubuntu 10.04.<br />
<br />
Although this new distro is officially supported for the next five years, that doesn’t mean you’re necessarily going to see it on our computers for that long. The Distro Interns will continue to work on documentation for Free Geek and look to new developments in the world of Linux computing in order to facilitate further changes as needed. Free Geek would like to thank our Distro Interns for all the hard work they continue to put into ensuring a satisfying computing experience for all Free Geek community members. If you happen to come across one of our Distro Interns (they’re hard to spot unless you know the secret Distro handshake…kidding!), please do the same!<br />
<br />
<br />
==Free Geek Charitable Contributions 101==<br />
Every day at the Free Geek Donations desk, our visitors ask all kinds of questions about our volunteer programs and our organizational structure. We love questions! They show that our patrons are interested in being informed about their chosen causes, and in spending their dollars wisely. Read on for responses to some of the questions we hear most frequently.<br />
<br />
* Q: “If Free Geek makes money from selling electronics in the Thrift Store, why do you also ask for contributions at the Donations Desk?”<br />
* A: First of all, we are incredibly grateful to you, our donors, for your support of technology reuse in the larger community. If you choose not to contribute funds, your hardware donation is no less valuable or appreciated as a result. However, as a 501(c)3 nonprofit, Free Geek relies on a variety of revenue streams, one of them being charitable contributions, to support our volunteer programs and operating expenses. The suggested values we offer at the Donations Desk are based on the costs we incur from processing materials through Receiving. These costs are the same whether a donated item ends up in the Thrift Store or the Recycling Warehouse.<br />
<br />
* Q: “How do contributions stack up against your other sources of revenue?”<br />
* A: We earn about 65% of our revenue through sales in our Thrift Store, bulk sales and online sales. Another 20% comes from recycling vendor payments and pickup fees. The remaining 15% comes from individual contributions, many of which are made at the Donations desk, but some are also sent to us in the mail or transacted through our Paypal account (https://www.paypal.com/us/cgi-bin/webscr?cmd=_flow&SESSION=db7I3WQ56rjnMnHobewXIWW3Nvpuj7Ba2220Qzi71fd-GlCiHg0bVLLZ1n4&dispatch=5885d80a13c0db1f8e263663d3faee8d0b7e678a25d883d0fa72c947f193f8fd). A portion of recycling expenses that would otherwise affect our budget and our donors’ pocketbooks are also offset by our membership in the Oregon E-cycles program.<br />
<br />
* Q: “How can I stay informed about how Free Geek is using the contributions and other revenue you receive?”<br />
* A: There are various ways to keep tabs on our operations, programs and financials. You can obtain a free copy of our most recent IRS 990 forms on the NCSS website (http://nccsdataweb.urban.org/orgs/profile/931292010#forms). If you want to follow the progress of our projects and programs on the ground, look no further than our meeting minutes. Minutes from all Free Geek committees and working groups (short of confidential business and executive sessions) are available to the public via subscription to our Minutes email list (http://lists.freegeek.org/listinfo/minutes). Our board of directors is also receptive to answering questions from the public; inquiries about board business and the steering of Free Geek as a whole can be directed to board-discuss AT lists DOT freegeek DOT org (http://lists.freegeek.org/listinfo/board-discuss). Lastly, if you have a question and aren’t sure where it should be directed, email info AT freegeek DOT org, and a staff member will follow up with you promptly.<br />
<br />
==Hardware Grants Spotlight: Computers in Schools==<br />
What is the value of a Hardware Grant from Free Geek? Current tax code does not allow us to assign monetary value to computers we disburse to nonprofits, schools and community change organizations through our Hardware Grants program. However, a staff person at one of our recent grant recipient organizations did take it upon himself to sum up the value of our hardware grants in terms of additional teaching capacity. Paul Shearer was working as the IBM School Mentor in the Lake Oswego School District when he received a large assortment of computers for his program:<br />
<br />
“Five (5) Free Geek grant computers per month can provide sixty (60) computers in 12 months which can provide a school with two (2) student labs of thirty (30) computers each and save the school $42,000 cash. That can be enough savings to help fund one teacher for a full year.<br />
<br />
Free Geek has provided over two hundred (200) grant computers to LOSD in the past three years and that has provided a savings of $140,000 cash which is enough to fund two master high school teachers for one full year and at some schools could help fund up to three starting teachers for a full year.”<br />
<br />
Lake Oswego is not the only educational institution to have benefited from Free Geek’s Hardware Grants program. So far in 2012, we have granted out free laptops and computers (http://www.freegeek.org/about/grants/) (along with monitors, keyboards and mouses) to over 45 educational programs. Included in these disbursements were over 526 systems and 69 laptops! That can translate to thousands of saved dollars that, rather than being spent on technical infrastructure, can go directly to educating the youth of the greater Portland area. It’s also a whole lot of computers being reused instead of recycled, or worse, improperly discarded.<br />
<br />
Recipients of Free Geek hardware grants this year include (but certainly aren’t limited to):<br />
Agia Sophia Academy<br />
Ano’s Art Academy<br />
Astor K-8 school<br />
Atlas Immersion Academy<br />
Ballston Community School<br />
Bethel Christian School<br />
Childswork Learning Center Inc.<br />
Conestoga Middle School<br />
Emmanuel Christian Academy<br />
Escuela Viva<br />
FIRST Robotics Competition Team 1432<br />
Forest Grove High School Speech and Debate<br />
Grandhaven Elementary<br />
Hope Chinese Charter School<br />
Lanai High And Elementary<br />
Leadership and Entrepreneurship Public Charter High School<br />
Lewis and Clark High School<br />
Mount Adams School District<br />
Northwest Children’s Theater and School<br />
Pioneer Montessori School<br />
Portland Public Schools<br />
Portland Village School<br />
Portland Youth Builders<br />
Reynolds Learning Academy: East Campus<br />
Sunstone Montessori School<br />
Tucker-Maxon Oral School<br />
Village Free School<br />
Wahkiakum School District<br />
<br />
<br />
==Staff Spotlight: Kevin Wright==<br />
In this edition of the Free Geek Gnusletter, we profile Kevin Wright, known by many since April 2012 as one of our always hard-working and friendly Receiving and Prebuild Associates. Naturally, the Gnusletter staff was thrilled to sit down with Kevin to find out what makes her tick and how she found her way to Free Geek. Prepare to be delighted and amazed, and say hi to Kevin when you see her around the building!<br />
<br />
* FG: What led or inspired you to get involved with Free Geek, and how did you end up working on the staff?<br />
* KW: I was in school and realized that after two years as a Computer Science student we had never opened a computer and looked inside! I was having a really hard time connecting the dots between the hardware and what we were learning from labs and books, so I told one of my teachers that I needed some hands-on time with a computer I could break or take apart, and he sent me to Free Geek. I never left. I started as a volunteer, then became an intern, then a temporary employee and finally got hired full-time.<br />
<br />
* FG: What is your favorite thing about your job?<br />
* KW: I love that at Free Geek we don’t judge people by the way they look, act, or dress. To me it seems like everyone is welcome to come in and try their hand at whatever takes their fancy. We do our best to teach anyone who wants to learn.<br />
<br />
* FG: Can you tell our readers something about you that might surprise them?<br />
* KW: I love to surf, and usually try to get to some good water a few times a year. My mom was a surfer in the 60′s and she taught my brothers and me. I enjoy Kihei beach, and Kahului Harbor in Maui, but will try any beach. I am also a pretty good bow hunter and try to get out in the field as much as I can. Growing up, my family hunted everything we could eat. I have the most fun hunting with a bow because i think it is the most fair. You can stand across a canyon with a rifle and catch a deer, but with a bow you have to actually hunt.<br />
<br />
* FG: Have you learned any tips about working with computers that you think our readers may want to know?<br />
* KW: There is no “cheating” in computers! By which I mean that whatever you’re trying to figure out, there is documentation online somewhere that contains the answer, or someone else at Free Geek has had that problem and is usually willing to help. Volunteers who try to speed through the process without asking questions might miss out on important information and end up shooting themselves in the foot. My advice is to take it slow, ask questions and don’t be embarrassed if you don’t already know the answer to the problem you’re trying to solve.<br />
<br />
* FG: Would you rather fight 100 duck-sized horses or one horse-sized duck, and why?<br />
* KW: If I saw a horse-sized duck I would try to ride it!<br />
<br />
==Volunteer Spotlight: Ben Koenig==<br />
If you came to this year’s HoliDistro disco party, you would have found Ben Koenig in the classroom leading some gaming activities and showcasing Free Geek’s new release of Xubuntu 12.04 free and open source operating system. How did Ben attain this prestigious and important role? He started volunteering at Free Geek about three years ago, quickly advancing through the Build program, and moving on to intern in Tech Support, where he continues to serve today.<br />
<br />
Ben’s higher focus since November of 2011 has been the Distribution Committee, or “Distro.” Along with fellow volunteers Larry, Tim, and Tanvi, Ben was tasked with testing and choosing the best Linux OS distribution for Free Geek to replace Ubuntu Lucid 10.04. “Mostly our target has been to find a distro amongst a set of predetermined user-friendly distributions,” says Ben.<br />
<br />
In addition to all his great work on the Distro Committee, Ben also teaches the Linux Playground class. In this class, Ben sets up eight laptops with a different Linux distribution on each so volunteers can experiment with them. He describes it as “a lot of fun, and a great way to see and use a particular distro before you install it on your own machine.”<br />
<br />
How did Ben become so Linux-savvy? His father is an avid Linux user and got him started at an early age. Ben now has three operating systems on his computer and has even created an app for android called Freedom Zing. He designed it for elections and it comes with 70 random zingers to use against either conservatives or liberals. Equal-opportunity zinging can be accessed via a quick search of “Freedom Zing” on Google Play.<br />
<br />
Some fun facts about Ben that you may not know: he has lived in every corner of the US, takes three buses and a Max to Free Geek, and not only teaches chess to youth, he can even play it blindfolded! He told the interviewer that his favorite thing about volunteering at Free Geek is “being around all the computer and open source stuff and talking to people who also know about Linux, and having the community to interact with on that level.” Thanks to Ben for being such a star volunteer!</div>Alambhttp://wiki.freegeek.org/index.php?title=2012_December_Newsletter&diff=656292012 December Newsletter2012-12-21T01:53:44Z<p>Alamb: /* Staff Spotlight: Kevin Wright */</p>
<hr />
<div>==The Freekbox Gets a Makeover==<br />
If you visited Free Geek on December 4 and heard disco music blaring while volunteers and staff competed head-to-head on Super Tux Kart in the classroom (yes, it’s an open source game very similar to Super Mario Kart), you luckily stumbled into the Holi-Distro party. Generally, our holiday party is a chance to unwind with other Free Geek community members, perhaps participate in a white elephant gift exchange, and celebrate the many accomplishments of the year. This year though, things were a little different as we were also celebrating the release of a new Linux distribution on Free Geek computers.<br />
<br />
Linux, an open-source operating system, has many different distributions (http://en.wikipedia.org/wiki/Linux_distros#Popular_distributions), or distros, maintained by various groups throughout the world. Each of these distros is updated, much like you see on other proprietary operating systems, on a regular basis. Since 2006, Free Geek has used Ubuntu (http://www.ubuntu.com/), currently the most widely-adopted version of Linux, on all of our computers with an operating system. We chose this version for its ease of use and the robust support afforded by the greater Linux community and Canonical, the company responsible for Ubuntu Linux. Unfortunately, the version of Ubuntu we’ve been using since 2010, 10.04 Lucid Lynx, will only be officially supported until April, 2013. To plan for this transition, several Free Geek staff and interns formed the Distro Committee to research, test, de-bug, and document the next version of Linux for our computers.<br />
<br />
First, the committee set out to define priorities for the new operating system. We talked to representatives of various areas of Free Geek including Tech Support, the Build Program, Education, and the Thrift Store. We also polled a wide cross-section of our computer users to discover what was important to them and how they use their computers. Major priorities for this new distro included a long support cycle (so we wouldn’t have to go through this process too often), compatibility with a wide range of old and new computer systems, and ease of use for both beginners and experienced computer users. Armed with these criteria, our intrepid Distro Interns began exploring and testing many of the various available Linux distributions. (Find out more about one of the lead Distro Interns, Ben Koening, in this newsletter’s Volunteer Spotlight (http://www.freegeek.org/newsletter/2012/12/volunteer-spotlight-ben-koenig/.))<br />
<br />
After collecting tons of data on various distributions, the intern team ultimately recommended that Free Geek adopt Xubuntu 12.04 (http://xubuntu.org/) (although it’s officially pronounced “zoo-bun-too”, plenty of people call it “ex-oo-bun-too”.) As you can likely tell from the name, this is a branch of the original Ubuntu distro. Unlike Ubuntu 12.04, which comes with the new-to-users Unity Interface (http://unity.ubuntu.com/), Xubuntu uses Xfce (http://www.xfce.org/) to control the way the operating system looks. This version was selected for many reasons including the same five-year support of Ubuntu 12.04, speed on both old and new systems, and an interface very similar to the one our users became familiar with in Ubuntu 10.04.<br />
<br />
Although this new distro is officially supported for the next five years, that doesn’t mean you’re necessarily going to see it on our computers for that long. The Distro Interns will continue to work on documentation for Free Geek and look to new developments in the world of Linux computing in order to facilitate further changes as needed. Free Geek would like to thank our Distro Interns for all the hard work they continue to put into ensuring a satisfying computing experience for all Free Geek community members. If you happen to come across one of our Distro Interns (they’re hard to spot unless you know the secret Distro handshake…kidding!), please do the same!<br />
<br />
<br />
==Free Geek Charitable Contributions 101==<br />
Every day at the Free Geek Donations desk, our visitors ask all kinds of questions about our volunteer programs and our organizational structure. We love questions! They show that our patrons are interested in being informed about their chosen causes, and in spending their dollars wisely. Read on for responses to some of the questions we hear most frequently.<br />
<br />
Q: “If Free Geek makes money from selling electronics in the Thrift Store, why do you also ask for contributions at the Donations Desk?”<br />
A: First of all, we are incredibly grateful to you, our donors, for your support of technology reuse in the larger community. If you choose not to contribute funds, your hardware donation is no less valuable or appreciated as a result. However, as a 501(c)3 nonprofit, Free Geek relies on a variety of revenue streams, one of them being charitable contributions, to support our volunteer programs and operating expenses. The suggested values we offer at the Donations Desk are based on the costs we incur from processing materials through Receiving. These costs are the same whether a donated item ends up in the Thrift Store or the Recycling Warehouse.<br />
<br />
Q: “How do contributions stack up against your other sources of revenue?”<br />
A: We earn about 65% of our revenue through sales in our Thrift Store, bulk sales and online sales. Another 20% comes from recycling vendor payments and pickup fees. The remaining 15% comes from individual contributions, many of which are made at the Donations desk, but some are also sent to us in the mail or transacted through our Paypal account (https://www.paypal.com/us/cgi-bin/webscr?cmd=_flow&SESSION=db7I3WQ56rjnMnHobewXIWW3Nvpuj7Ba2220Qzi71fd-GlCiHg0bVLLZ1n4&dispatch=5885d80a13c0db1f8e263663d3faee8d0b7e678a25d883d0fa72c947f193f8fd). A portion of recycling expenses that would otherwise affect our budget and our donors’ pocketbooks are also offset by our membership in the Oregon E-cycles program.<br />
<br />
Q: “How can I stay informed about how Free Geek is using the contributions and other revenue you receive?”<br />
A: There are various ways to keep tabs on our operations, programs and financials. You can obtain a free copy of our most recent IRS 990 forms on the NCSS website (http://nccsdataweb.urban.org/orgs/profile/931292010#forms). If you want to follow the progress of our projects and programs on the ground, look no further than our meeting minutes. Minutes from all Free Geek committees and working groups (short of confidential business and executive sessions) are available to the public via subscription to our Minutes email list (http://lists.freegeek.org/listinfo/minutes). Our board of directors is also receptive to answering questions from the public; inquiries about board business and the steering of Free Geek as a whole can be directed to board-discuss AT lists DOT freegeek DOT org (http://lists.freegeek.org/listinfo/board-discuss). Lastly, if you have a question and aren’t sure where it should be directed, email info AT freegeek DOT org, and a staff member will follow up with you promptly.<br />
<br />
==Hardware Grants Spotlight: Computers in Schools==<br />
What is the value of a Hardware Grant from Free Geek? Current tax code does not allow us to assign monetary value to computers we disburse to nonprofits, schools and community change organizations through our Hardware Grants program. However, a staff person at one of our recent grant recipient organizations did take it upon himself to sum up the value of our hardware grants in terms of additional teaching capacity. Paul Shearer was working as the IBM School Mentor in the Lake Oswego School District when he received a large assortment of computers for his program:<br />
<br />
“Five (5) Free Geek grant computers per month can provide sixty (60) computers in 12 months which can provide a school with two (2) student labs of thirty (30) computers each and save the school $42,000 cash. That can be enough savings to help fund one teacher for a full year.<br />
<br />
Free Geek has provided over two hundred (200) grant computers to LOSD in the past three years and that has provided a savings of $140,000 cash which is enough to fund two master high school teachers for one full year and at some schools could help fund up to three starting teachers for a full year.”<br />
<br />
Lake Oswego is not the only educational institution to have benefited from Free Geek’s Hardware Grants program. So far in 2012, we have granted out free laptops and computers (http://www.freegeek.org/about/grants/) (along with monitors, keyboards and mouses) to over 45 educational programs. Included in these disbursements were over 526 systems and 69 laptops! That can translate to thousands of saved dollars that, rather than being spent on technical infrastructure, can go directly to educating the youth of the greater Portland area. It’s also a whole lot of computers being reused instead of recycled, or worse, improperly discarded.<br />
<br />
Recipients of Free Geek hardware grants this year include (but certainly aren’t limited to):<br />
Agia Sophia Academy<br />
Ano’s Art Academy<br />
Astor K-8 school<br />
Atlas Immersion Academy<br />
Ballston Community School<br />
Bethel Christian School<br />
Childswork Learning Center Inc.<br />
Conestoga Middle School<br />
Emmanuel Christian Academy<br />
Escuela Viva<br />
FIRST Robotics Competition Team 1432<br />
Forest Grove High School Speech and Debate<br />
Grandhaven Elementary<br />
Hope Chinese Charter School<br />
Lanai High And Elementary<br />
Leadership and Entrepreneurship Public Charter High School<br />
Lewis and Clark High School<br />
Mount Adams School District<br />
Northwest Children’s Theater and School<br />
Pioneer Montessori School<br />
Portland Public Schools<br />
Portland Village School<br />
Portland Youth Builders<br />
Reynolds Learning Academy: East Campus<br />
Sunstone Montessori School<br />
Tucker-Maxon Oral School<br />
Village Free School<br />
Wahkiakum School District<br />
<br />
<br />
==Staff Spotlight: Kevin Wright==<br />
In this edition of the Free Geek Gnusletter, we profile Kevin Wright, known by many since April 2012 as one of our always hard-working and friendly Receiving and Prebuild Associates. Naturally, the Gnusletter staff was thrilled to sit down with Kevin to find out what makes her tick and how she found her way to Free Geek. Prepare to be delighted and amazed, and say hi to Kevin when you see her around the building!<br />
<br />
* FG: What led or inspired you to get involved with Free Geek, and how did you end up working on the staff?<br />
* KW: I was in school and realized that after two years as a Computer Science student we had never opened a computer and looked inside! I was having a really hard time connecting the dots between the hardware and what we were learning from labs and books, so I told one of my teachers that I needed some hands-on time with a computer I could break or take apart, and he sent me to Free Geek. I never left. I started as a volunteer, then became an intern, then a temporary employee and finally got hired full-time.<br />
<br />
* FG: What is your favorite thing about your job?<br />
* KW: I love that at Free Geek we don’t judge people by the way they look, act, or dress. To me it seems like everyone is welcome to come in and try their hand at whatever takes their fancy. We do our best to teach anyone who wants to learn.<br />
<br />
* FG: Can you tell our readers something about you that might surprise them?<br />
* KW: I love to surf, and usually try to get to some good water a few times a year. My mom was a surfer in the 60′s and she taught my brothers and me. I enjoy Kihei beach, and Kahului Harbor in Maui, but will try any beach. I am also a pretty good bow hunter and try to get out in the field as much as I can. Growing up, my family hunted everything we could eat. I have the most fun hunting with a bow because i think it is the most fair. You can stand across a canyon with a rifle and catch a deer, but with a bow you have to actually hunt.<br />
<br />
* FG: Have you learned any tips about working with computers that you think our readers may want to know?<br />
* KW: There is no “cheating” in computers! By which I mean that whatever you’re trying to figure out, there is documentation online somewhere that contains the answer, or someone else at Free Geek has had that problem and is usually willing to help. Volunteers who try to speed through the process without asking questions might miss out on important information and end up shooting themselves in the foot. My advice is to take it slow, ask questions and don’t be embarrassed if you don’t already know the answer to the problem you’re trying to solve.<br />
<br />
* FG: Would you rather fight 100 duck-sized horses or one horse-sized duck, and why?<br />
* KW: If I saw a horse-sized duck I would try to ride it!<br />
<br />
==Volunteer Spotlight: Ben Koenig==<br />
If you came to this year’s HoliDistro disco party, you would have found Ben Koenig in the classroom leading some gaming activities and showcasing Free Geek’s new release of Xubuntu 12.04 free and open source operating system. How did Ben attain this prestigious and important role? He started volunteering at Free Geek about three years ago, quickly advancing through the Build program, and moving on to intern in Tech Support, where he continues to serve today.<br />
<br />
Ben’s higher focus since November of 2011 has been the Distribution Committee, or “Distro.” Along with fellow volunteers Larry, Tim, and Tanvi, Ben was tasked with testing and choosing the best Linux OS distribution for Free Geek to replace Ubuntu Lucid 10.04. “Mostly our target has been to find a distro amongst a set of predetermined user-friendly distributions,” says Ben.<br />
<br />
In addition to all his great work on the Distro Committee, Ben also teaches the Linux Playground class. In this class, Ben sets up eight laptops with a different Linux distribution on each so volunteers can experiment with them. He describes it as “a lot of fun, and a great way to see and use a particular distro before you install it on your own machine.”<br />
<br />
How did Ben become so Linux-savvy? His father is an avid Linux user and got him started at an early age. Ben now has three operating systems on his computer and has even created an app for android called Freedom Zing. He designed it for elections and it comes with 70 random zingers to use against either conservatives or liberals. Equal-opportunity zinging can be accessed via a quick search of “Freedom Zing” on Google Play.<br />
<br />
Some fun facts about Ben that you may not know: he has lived in every corner of the US, takes three buses and a Max to Free Geek, and not only teaches chess to youth, he can even play it blindfolded! He told the interviewer that his favorite thing about volunteering at Free Geek is “being around all the computer and open source stuff and talking to people who also know about Linux, and having the community to interact with on that level.” Thanks to Ben for being such a star volunteer!</div>Alambhttp://wiki.freegeek.org/index.php?title=2012_December_Newsletter&diff=656282012 December Newsletter2012-12-21T01:48:54Z<p>Alamb: /* The Freekbox Gets a Makeover */</p>
<hr />
<div>==The Freekbox Gets a Makeover==<br />
If you visited Free Geek on December 4 and heard disco music blaring while volunteers and staff competed head-to-head on Super Tux Kart in the classroom (yes, it’s an open source game very similar to Super Mario Kart), you luckily stumbled into the Holi-Distro party. Generally, our holiday party is a chance to unwind with other Free Geek community members, perhaps participate in a white elephant gift exchange, and celebrate the many accomplishments of the year. This year though, things were a little different as we were also celebrating the release of a new Linux distribution on Free Geek computers.<br />
<br />
Linux, an open-source operating system, has many different distributions (http://en.wikipedia.org/wiki/Linux_distros#Popular_distributions), or distros, maintained by various groups throughout the world. Each of these distros is updated, much like you see on other proprietary operating systems, on a regular basis. Since 2006, Free Geek has used Ubuntu (http://www.ubuntu.com/), currently the most widely-adopted version of Linux, on all of our computers with an operating system. We chose this version for its ease of use and the robust support afforded by the greater Linux community and Canonical, the company responsible for Ubuntu Linux. Unfortunately, the version of Ubuntu we’ve been using since 2010, 10.04 Lucid Lynx, will only be officially supported until April, 2013. To plan for this transition, several Free Geek staff and interns formed the Distro Committee to research, test, de-bug, and document the next version of Linux for our computers.<br />
<br />
First, the committee set out to define priorities for the new operating system. We talked to representatives of various areas of Free Geek including Tech Support, the Build Program, Education, and the Thrift Store. We also polled a wide cross-section of our computer users to discover what was important to them and how they use their computers. Major priorities for this new distro included a long support cycle (so we wouldn’t have to go through this process too often), compatibility with a wide range of old and new computer systems, and ease of use for both beginners and experienced computer users. Armed with these criteria, our intrepid Distro Interns began exploring and testing many of the various available Linux distributions. (Find out more about one of the lead Distro Interns, Ben Koening, in this newsletter’s Volunteer Spotlight (http://www.freegeek.org/newsletter/2012/12/volunteer-spotlight-ben-koenig/.))<br />
<br />
After collecting tons of data on various distributions, the intern team ultimately recommended that Free Geek adopt Xubuntu 12.04 (http://xubuntu.org/) (although it’s officially pronounced “zoo-bun-too”, plenty of people call it “ex-oo-bun-too”.) As you can likely tell from the name, this is a branch of the original Ubuntu distro. Unlike Ubuntu 12.04, which comes with the new-to-users Unity Interface (http://unity.ubuntu.com/), Xubuntu uses Xfce (http://www.xfce.org/) to control the way the operating system looks. This version was selected for many reasons including the same five-year support of Ubuntu 12.04, speed on both old and new systems, and an interface very similar to the one our users became familiar with in Ubuntu 10.04.<br />
<br />
Although this new distro is officially supported for the next five years, that doesn’t mean you’re necessarily going to see it on our computers for that long. The Distro Interns will continue to work on documentation for Free Geek and look to new developments in the world of Linux computing in order to facilitate further changes as needed. Free Geek would like to thank our Distro Interns for all the hard work they continue to put into ensuring a satisfying computing experience for all Free Geek community members. If you happen to come across one of our Distro Interns (they’re hard to spot unless you know the secret Distro handshake…kidding!), please do the same!<br />
<br />
<br />
==Free Geek Charitable Contributions 101==<br />
Every day at the Free Geek Donations desk, our visitors ask all kinds of questions about our volunteer programs and our organizational structure. We love questions! They show that our patrons are interested in being informed about their chosen causes, and in spending their dollars wisely. Read on for responses to some of the questions we hear most frequently.<br />
<br />
Q: “If Free Geek makes money from selling electronics in the Thrift Store, why do you also ask for contributions at the Donations Desk?”<br />
A: First of all, we are incredibly grateful to you, our donors, for your support of technology reuse in the larger community. If you choose not to contribute funds, your hardware donation is no less valuable or appreciated as a result. However, as a 501(c)3 nonprofit, Free Geek relies on a variety of revenue streams, one of them being charitable contributions, to support our volunteer programs and operating expenses. The suggested values we offer at the Donations Desk are based on the costs we incur from processing materials through Receiving. These costs are the same whether a donated item ends up in the Thrift Store or the Recycling Warehouse.<br />
<br />
Q: “How do contributions stack up against your other sources of revenue?”<br />
A: We earn about 65% of our revenue through sales in our Thrift Store, bulk sales and online sales. Another 20% comes from recycling vendor payments and pickup fees. The remaining 15% comes from individual contributions, many of which are made at the Donations desk, but some are also sent to us in the mail or transacted through our Paypal account (https://www.paypal.com/us/cgi-bin/webscr?cmd=_flow&SESSION=db7I3WQ56rjnMnHobewXIWW3Nvpuj7Ba2220Qzi71fd-GlCiHg0bVLLZ1n4&dispatch=5885d80a13c0db1f8e263663d3faee8d0b7e678a25d883d0fa72c947f193f8fd). A portion of recycling expenses that would otherwise affect our budget and our donors’ pocketbooks are also offset by our membership in the Oregon E-cycles program.<br />
<br />
Q: “How can I stay informed about how Free Geek is using the contributions and other revenue you receive?”<br />
A: There are various ways to keep tabs on our operations, programs and financials. You can obtain a free copy of our most recent IRS 990 forms on the NCSS website (http://nccsdataweb.urban.org/orgs/profile/931292010#forms). If you want to follow the progress of our projects and programs on the ground, look no further than our meeting minutes. Minutes from all Free Geek committees and working groups (short of confidential business and executive sessions) are available to the public via subscription to our Minutes email list (http://lists.freegeek.org/listinfo/minutes). Our board of directors is also receptive to answering questions from the public; inquiries about board business and the steering of Free Geek as a whole can be directed to board-discuss AT lists DOT freegeek DOT org (http://lists.freegeek.org/listinfo/board-discuss). Lastly, if you have a question and aren’t sure where it should be directed, email info AT freegeek DOT org, and a staff member will follow up with you promptly.<br />
<br />
==Hardware Grants Spotlight: Computers in Schools==<br />
What is the value of a Hardware Grant from Free Geek? Current tax code does not allow us to assign monetary value to computers we disburse to nonprofits, schools and community change organizations through our Hardware Grants program. However, a staff person at one of our recent grant recipient organizations did take it upon himself to sum up the value of our hardware grants in terms of additional teaching capacity. Paul Shearer was working as the IBM School Mentor in the Lake Oswego School District when he received a large assortment of computers for his program:<br />
<br />
“Five (5) Free Geek grant computers per month can provide sixty (60) computers in 12 months which can provide a school with two (2) student labs of thirty (30) computers each and save the school $42,000 cash. That can be enough savings to help fund one teacher for a full year.<br />
<br />
Free Geek has provided over two hundred (200) grant computers to LOSD in the past three years and that has provided a savings of $140,000 cash which is enough to fund two master high school teachers for one full year and at some schools could help fund up to three starting teachers for a full year.”<br />
<br />
Lake Oswego is not the only educational institution to have benefited from Free Geek’s Hardware Grants program. So far in 2012, we have granted out free laptops and computers (http://www.freegeek.org/about/grants/) (along with monitors, keyboards and mouses) to over 45 educational programs. Included in these disbursements were over 526 systems and 69 laptops! That can translate to thousands of saved dollars that, rather than being spent on technical infrastructure, can go directly to educating the youth of the greater Portland area. It’s also a whole lot of computers being reused instead of recycled, or worse, improperly discarded.<br />
<br />
Recipients of Free Geek hardware grants this year include (but certainly aren’t limited to):<br />
Agia Sophia Academy<br />
Ano’s Art Academy<br />
Astor K-8 school<br />
Atlas Immersion Academy<br />
Ballston Community School<br />
Bethel Christian School<br />
Childswork Learning Center Inc.<br />
Conestoga Middle School<br />
Emmanuel Christian Academy<br />
Escuela Viva<br />
FIRST Robotics Competition Team 1432<br />
Forest Grove High School Speech and Debate<br />
Grandhaven Elementary<br />
Hope Chinese Charter School<br />
Lanai High And Elementary<br />
Leadership and Entrepreneurship Public Charter High School<br />
Lewis and Clark High School<br />
Mount Adams School District<br />
Northwest Children’s Theater and School<br />
Pioneer Montessori School<br />
Portland Public Schools<br />
Portland Village School<br />
Portland Youth Builders<br />
Reynolds Learning Academy: East Campus<br />
Sunstone Montessori School<br />
Tucker-Maxon Oral School<br />
Village Free School<br />
Wahkiakum School District<br />
<br />
<br />
==Staff Spotlight: Kevin Wright==<br />
In this edition of the Free Geek Gnusletter, we profile Kevin Wright, known by many since April 2012 as one of our always hard-working and friendly Receiving and Prebuild Associates. Naturally, the Gnusletter staff was thrilled to sit down with Kevin to find out what makes her tick and how she found her way to Free Geek. Prepare to be delighted and amazed, and say hi to Kevin when you see her around the building!<br />
<br />
FG: What led or inspired you to get involved with Free Geek, and how did you end up working on the staff?<br />
KW: I was in school and realized that after two years as a Computer Science student we had never opened a computer and looked inside! I was having a really hard time connecting the dots between the hardware and what we were learning from labs and books, so I told one of my teachers that I needed some hands-on time with a computer I could break or take apart, and he sent me to Free Geek. I never left. I started as a volunteer, then became an intern, then a temporary employee and finally got hired full-time.<br />
<br />
FG: What is your favorite thing about your job?<br />
KW: I love that at Free Geek we don’t judge people by the way they look, act, or dress. To me it seems like everyone is welcome to come in and try their hand at whatever takes their fancy. We do our best to teach anyone who wants to learn.<br />
<br />
FG: Can you tell our readers something about you that might surprise them?<br />
KW: I love to surf, and usually try to get to some good water a few times a year. My mom was a surfer in the 60′s and she taught my brothers and me. I enjoy Kihei beach, and Kahului Harbor in Maui, but will try any beach. I am also a pretty good bow hunter and try to get out in the field as much as I can. Growing up, my family hunted everything we could eat. I have the most fun hunting with a bow because i think it is the most fair. You can stand across a canyon with a rifle and catch a deer, but with a bow you have to actually hunt.<br />
<br />
FG: Have you learned any tips about working with computers that you think our readers may want to know?<br />
KW: There is no “cheating” in computers! By which I mean that whatever you’re trying to figure out, there is documentation online somewhere that contains the answer, or someone else at Free Geek has had that problem and is usually willing to help. Volunteers who try to speed through the process without asking questions might miss out on important information and end up shooting themselves in the foot. My advice is to take it slow, ask questions and don’t be embarrassed if you don’t already know the answer to the problem you’re trying to solve.<br />
<br />
FG: Would you rather fight 100 duck-sized horses or one horse-sized duck, and why?<br />
KW: If I saw a horse-sized duck I would try to ride it!<br />
<br />
==Volunteer Spotlight: Ben Koenig==<br />
If you came to this year’s HoliDistro disco party, you would have found Ben Koenig in the classroom leading some gaming activities and showcasing Free Geek’s new release of Xubuntu 12.04 free and open source operating system. How did Ben attain this prestigious and important role? He started volunteering at Free Geek about three years ago, quickly advancing through the Build program, and moving on to intern in Tech Support, where he continues to serve today.<br />
<br />
Ben’s higher focus since November of 2011 has been the Distribution Committee, or “Distro.” Along with fellow volunteers Larry, Tim, and Tanvi, Ben was tasked with testing and choosing the best Linux OS distribution for Free Geek to replace Ubuntu Lucid 10.04. “Mostly our target has been to find a distro amongst a set of predetermined user-friendly distributions,” says Ben.<br />
<br />
In addition to all his great work on the Distro Committee, Ben also teaches the Linux Playground class. In this class, Ben sets up eight laptops with a different Linux distribution on each so volunteers can experiment with them. He describes it as “a lot of fun, and a great way to see and use a particular distro before you install it on your own machine.”<br />
<br />
How did Ben become so Linux-savvy? His father is an avid Linux user and got him started at an early age. Ben now has three operating systems on his computer and has even created an app for android called Freedom Zing. He designed it for elections and it comes with 70 random zingers to use against either conservatives or liberals. Equal-opportunity zinging can be accessed via a quick search of “Freedom Zing” on Google Play.<br />
<br />
Some fun facts about Ben that you may not know: he has lived in every corner of the US, takes three buses and a Max to Free Geek, and not only teaches chess to youth, he can even play it blindfolded! He told the interviewer that his favorite thing about volunteering at Free Geek is “being around all the computer and open source stuff and talking to people who also know about Linux, and having the community to interact with on that level.” Thanks to Ben for being such a star volunteer!</div>Alambhttp://wiki.freegeek.org/index.php?title=2012_December_Newsletter&diff=656272012 December Newsletter2012-12-21T01:40:43Z<p>Alamb: Created page with "==The Freekbox Gets a Makeover== If you visited Free Geek on December 4 and heard disco music blaring while volunteers and staff competed head-to-head on Super Tux Kart in the cl…"</p>
<hr />
<div>==The Freekbox Gets a Makeover==<br />
If you visited Free Geek on December 4 and heard disco music blaring while volunteers and staff competed head-to-head on Super Tux Kart in the classroom (yes, it’s an open source game very similar to Super Mario Kart), you luckily stumbled into the Holi-Distro party. Generally, our holiday party is a chance to unwind with other Free Geek community members, perhaps participate in a white elephant gift exchange, and celebrate the many accomplishments of the year. This year though, things were a little different as we were also celebrating the release of a new Linux distribution on Free Geek computers.<br />
<br />
Linux, an open-source operating system, has many different distributions (http://en.wikipedia.org/wiki/Linux_distros#Popular_distributions), or distros, maintained by various groups throughout the world. Each of these distros is updated, much like you see on other proprietary operating systems, on a regular basis. Since 2006, Free Geek has used Ubuntu (http://www.ubuntu.com/), currently the most widely-adopted version of Linux, on all of our computers with an operating system. We chose this version for its ease of use and the robust support afforded by the greater Linux community and Canonical, the company responsible for Ubuntu Linux. Unfortunately, the version of Ubuntu we’ve been using since 2010, 10.04 Lucid Lynx, will only be officially supported until April, 2013. To plan for this transition, several Free Geek staff and interns formed the Distro Committee to research, test, de-bug, and document the next version of Linux for our computers.<br />
<br />
First, the committee set out to define priorities for the new operating system. We talked to representatives of various areas of Free Geek including Tech Support, the Build Program, Education, and the Thrift Store. We also polled a wide cross-section of our computer users to discover what was important to them and how they use their computers. Major priorities for this new distro included a long support cycle (so we wouldn’t have to go through this process too often), compatibility with a wide range of old and new computer systems, and ease of use for both beginners and experienced computer users. Armed with these criteria, our intrepid Distro Interns began exploring and testing many of the various available Linux distributions. (Find out more about one of the lead Distro Interns, Ben Koening, in this newsletter’s Volunteer Spotlight (http://www.freegeek.org/newsletter/2012/12/volunteer-spotlight-ben-koenig/.))<br />
<br />
After collecting tons of data on various distributions, the intern team ultimately recommended that Free Geek adopt Xubuntu 12.04 (http://xubuntu.org/) (although it’s officially pronounced “zoo-bun-too”, plenty of people call it “ex-oo-bun-too”.) As you can likely tell from the name, this is a branch of the original Ubuntu distro. Unlike Ubuntu 12.04, which comes with the new-to-users Unity Interface (http://unity.ubuntu.com/), Xubuntu uses Xfce (http://www.xfce.org/) to control the way the operating system looks. This version was selected for many reasons including the same five-year support of Ubuntu 12.04, speed on both old and new systems, and an interface very similar to the one our users became familiar with in Ubuntu 10.04.<br />
<br />
Although this new distro is officially supported for the next five years, that doesn’t mean you’re necessarily going to see it on our computers for that long. The Distro Interns will continue to work on documentation for Free Geek and look to new developments in the world of Linux computing in order to facilitate further changes as needed. Free Geek would like to thank our Distro Interns for all the hard work they continue to put into ensuring a satisfying computing experience for all Free Geek community members. If you happen to come across one of our Distro Interns (they’re hard to spot unless you know the secret Distro handshake…kidding!), please do the same!</div>Alambhttp://wiki.freegeek.org/index.php?title=Newsletter&diff=65626Newsletter2012-12-21T01:34:59Z<p>Alamb: /* Newsletter Archive */</p>
<hr />
<div>==Email Administration==<br />
Prior to newsletter publishing, all emails from the signup sheets at the front desk should be input online.<br />
#Create a list of emails from signup sheets - one per line, no extra information or punctuation<br />
#Go to Newsletter email admin page (if you don't have the password, find someone who does to accomplish this): http://lists.freegeek.org/admin/e-newsletter/general<br />
#Click on "Membership Management" after logging in to the above webpage<br />
#Then click on "Mass Subscription."<br />
#Paste the list of emails into the box below the text "Enter one address per line below..."<br />
#Click the Submit Your Changes button at the bottom of the page.<br />
<br />
<br />
Emails including the following should be sent to the e-newsletter list and paidworkers preferably on a Tuesday or Thursday afternoon before 4:00:<br />
*Summary of included articles<br />
*Link to the updated newsletter<br />
*Link to corresponding plaintext wiki page (see end of publishing directions, below)<br />
<br />
==Updating the Newsletter/Adding Articles==<br />
We upload five articles to the newsletter every news cycle (two feature articles and three side articles).<br />
<br />
#Sign in at http://www.freegeek.org/newsletter/wp-admin<br />
#Click on "Add New" under "Posts" in the sidebar.<br />
#Add title to post.<br />
#In the right-hand column:<br />
##Click "edit" next to "Publish immediately" under "Publish" on the right-hand side of the page<br />
###Change to the date of publication for the Newsletter (preferably a Thursday). All articles should have the same date.<br />
###*Times should be set to the following (this is essential as it dictates the article order/location on the website):<br />
###**First feature-7:05<br />
###**Second feature-7:03<br />
###**First sub-article (Other/hardware grants spotlight)-7:11<br />
###**Second sub-article (Volunteer spotlight) - 7:09<br />
###**Third sub-article (Staff spotlight) - 7:07<br />
##Choose only one category under the Categories option that correlates with the article type.<br />
##If this is a featured article, include "featured" under Post Tags.<br />
##Set the "Featured Image" for the article by clicking "Set featured image."<br />
##*Featured posts should have a unique image that relates to the article. This may also be included in the article.<br />
##*Sub-articles should use the correlating title image, found under the "Media Library" option.<br />
##*After uploading or choosing your image, click the "Use as featured image" link near the bottom of the dialogue box then click the "Save all changes" button.<br />
#Insert (or type) the content of your article under "Upload/Insert"<br />
#If you'd like to control the front page preview copy the first part of your text (or whatever you want to show as the "teaser" on the front page) into the Excerpt box. This excerpt should be no longer than 210 characters. You can use an [https://www.google.com/webhp?pq=online+character+counter#hl=en&tok=kXG4yG1S95aZyt3T7k8vMA&cp=12&gs_id=1e&xhr=t&q=online+character+counter&fp=1&bav=on.2,or.r_gc.r_pw.r_cp.,cf.osb&cad=b online character counter] to check how many characters are in your excerpt<br />
#Click the blue publish button to publish your article at a future date or review your article by clicking the grey preview button<br />
#Include a plaintext copy of your article (with necessary hyperlinks included in parenthesis) one the corresponding page of the Wiki.<br />
#*There should only be one page per newsletter; you may need to create this<br />
#*Articles should be presented in the same order they are found on the website<br />
#*The page should be titled YEAR_MONTH_Newsletter (e.g. 2012 February Newsletter)<br />
#*The page should be tagged with the "Newsletter" category<br />
<br />
==Newsletter Archive==<br />
<br />
* [[2012 February Newsletter]]<br />
* [[2012 May Newsletter]]<br />
* [[2012 September Newsletter]]<br />
* [[2012 December Newsletter]]<br />
<br />
[[Category:PR]][[Category:Newsletter]]</div>Alambhttp://wiki.freegeek.org/index.php?title=Tabling&diff=65551Tabling2012-12-14T20:13:21Z<p>Alamb: /* What's on the table? (Required Supplies) */</p>
<hr />
<div>On occasion, Free Geek representatives go to events and staff a table full of information about our organization. The [[PR]] committee oversees these trips.<br />
<br />
Right now, we only tend to accept tabling opportunities if we can find an appropriate core volunteer to staff the table, as there's often little publicity that actually happens. We're trying to track how successful each of these events has been, though.<br />
<br />
==What is stocked in each of the two Tabling Bins? (Required Supplies)==<br />
*1 manila folder containing:<br />
**Adoption Program Info (1/2 size) Sheets (English)<br />
**Build Program Info Sheets (English)<br />
**Build Program Info (1/2 size) Sheets (English)<br />
*1 manila folder containing:<br />
**Build Program sheets (Spanish)<br />
**Adoption Program sheets (Spanish)<br />
*1 manila folder containing:<br />
**Other Local Recyclers sheets<br />
*Brochures in both English and Español<br />
*Hazardous Materials fact sheets<br />
*Plug Into Portland flyers<br />
*ReusePDX promo flyers<br />
*Outreach Training/Talking Points Packet<br />
*Free Geek FAQ Printout<br />
*Biz cards for Ed/Grants Coordinator, Contributor Relations Coordinator, Volunteer/Front Desk Coordinator, and Generic Info<br />
*Thrift Store biz cards<br />
*Remit (mail donation) envelopes<br />
*1 clipboard<br />
*1 black tablecloth<br />
*1 black Free Geek shiny nylon/canvas sign<br />
*FG Stickers Large and Small<br />
*1 plastic sign stand<br />
*1 brochure holder<br />
*1 pair scissors<br />
*1 roll of twine<br />
*Supply of rubber bands<br />
*large paper clips<br />
*large safety pins<br />
*Pens (ballpoint & sharpie)<br />
*1 click counter (to track number of contacts)<br />
*Temp tattoos<br />
*2 Welcome to Free Geek DVDs<br />
*3 sticks of RAM<br />
*3-4 heat sinks for biz cards<br />
*2 motherboards<br />
*Donation jar<br />
*Donation receipt log sheets <br />
*Paper receipts for contributions<br />
*DBAN discs<br />
*Distro CDs<br />
*1 zip drive box<br />
*Map of other Free Geeks<br />
*(New) Mailing lists signup sheet (11x17)<br />
<br />
To Develop on Outreach Wiki:<br />
*Talking points page http://wiki.freegeek.org/index.php/Media_Talking_Points<br />
*Required Materials/Suggested Talking Points for Types of Events (I don't think this page exists) ** I also don't think this page exists. Would probably pull information similar to that found on the Talking points page as well as the Free Geek FAQ: http://wiki.freegeek.org/index.php/Free_Geek_FAQ ** Would need to be<br />
organized by event-type (school event, Earth Day, etc.)<br />
<br />
==Where to table?==<br />
Here's a list of places we've staffed a table with some info so we can figure out if we want to do it again next year. Please use this format if you list an event:<br />
* Event name/Organization<br />
* Date<br />
* Who staffed the Free Geek table<br />
* Approx. how many people attended the event?<br />
* How many people did he/she talk to?<br />
* Should we do it again (be brutal!)?<br />
<br />
[[Category:PR]]<br />
[[Category: Tabling]]</div>Alambhttp://wiki.freegeek.org/index.php?title=Dead_trees&diff=65474Dead trees2012-12-08T00:06:03Z<p>Alamb: /* Volunteer Info */</p>
<hr />
<div>This page is an index for files that need to look a certain way when printed out, for example forms and brochures where the page layout is very important. <br />
<br />
There are a variety of applications that can produce these printouts, including Openoffice, Glabels, and Gnumeric. please install the freegeek-deadtrees package in order to ensure that you have them all installed. if you include files on this page that are not supported by the above mentioned programs, please inform one of the [[Technocrats]].<br />
<br />
If there are files listed here that don't need to look a certain way when printed out, they should probably just be moved to a regular wiki page.<br />
<br />
There are some files here that were originally [[Dead trees#html (switch formats):|uploaded]] as postscript files only. (The old system had a place for source files, but some authors did not commit their source files.) In those cases, the postscript file should be used as a basis for re-creating the document using open office or another appropriate application.)<br />
<br />
To use these files click on the link. If your computer is properly configured your application will open the document. You may need to install additional software and/or configure your browser to do this.<br />
<br />
; [[Media:General_conduct_guidelines.odt|General Conduct Guidelines]]<br />
:Rules of conduct while at FREE GEEK to ensure we are all treated with respect while we're here.<br />
; [[Media:Standard-orgchart.odg| Org Chart]]<br />
: Standard version of organizational chart of departments, areas, and workers at Free Geek.<br />
; [[Media:Borrow-form.odt|Borrow Form]]<br />
:Form used to authorize borrowing of items.<br />
<br />
<br />
==Adoption Program Information==<br />
; [[Media:Spanish_Volunteer_Information-1.odt|Information for Spanish-speaking volunteers]] <br />
: This is the information about Free Geek in Spanish that we can hand out at the Front Desk. <br />
<br />
; [[Media:Adoption_Program_Information.odt|Adoption Packet]]<br />
: This is the information we give to all volunteers interested in the Adoption Program! Please note that this document must be printed double-sided and then cut in half.<br />
<br />
; [[Media:Adoption_Program_Information-1.odt|Spanish Adoption Packet]] <br />
: This is the Spanish version of the Adoption Packet. <br />
<br />
; [[Media:Adoption_exit_survey.odt|Adoption Exit Survey]]<br />
: For feedback from outgoing adopters.<br />
<br />
; [[Media:Group_Volunteering_at_FG-2.odt|Group Volunteering]]<br />
: For Groups interested in Group Volunteering.<br />
<br />
== Beancounting ==<br />
; [[Media:Till-worksheet.gnumeric|Till worksheet]]<br />
: This is a spreadsheet that can be used to count money in the tills at the end of a cashier's shift, and also for beancounting the following day. It is filled out and printed out at the end of the cashier's shift (and then included in the till), and it is filled out and printed out to include in the daily transaction books by the beancounters.<br />
<br />
; [[Media:Endofshiftform.gnumeric|End of shift form]]<br />
: Blank copies of this form are kept at the beancounting desk in the Escape Hatch. They are partially filled out when preparing a till to show how much money the till started with. In case the network is unavailable, this form can be used instead of the till worksheet to close the till at the end of the day.<br />
<br />
; [[Media:Deposit_sanity_check.gnumeric|Deposit sanity check]]<br />
: This is a way of quickly checking if your deposit matches the amount of the till worksheets.<br />
<br />
; [[Media:Inventory-sheet.gnumeric|Inventory Sheet]] <br />
: This is used by the talliers at the end of the month during the gizmo inventory.<br />
<br />
; [[Media:adjustnotice.odt|Adjustment Notice]]<br />
: This is used to notify the till closers that there needs to be a non-database adjustment to the till.<br />
<br />
==Build Program Information==<br />
; [[Media:Build_Packet.odt|Build Packet]]<br />
: Information for volunteers interested in becoming build volunteers. Please note that this document should be printed double-sided.<br />
<br />
; [[Media:Build_Packet_Spanish.odt|Spanish Build Packet]] <br />
: Information for volunteers interested in Spanish Build. Please note that the document should be printed double-sided. <br />
<br />
; [[Media:Spanish_Build_Quality_Control_Checklist_.odt |Spanish Build Quality Control Checklist]] <br />
: Spanish Build Quality Control Checklist. <br />
<br />
; <s>[[Media:Builder_Status_Sheet.odt|Builder's Status Sheet]]</s><br />
: DEFUNCT; Build status records now stored in FGDB. (Or [[Media:Builder_Status_Sheet-prototype.odt|a prototype]])<br />
<br />
; <s>[[Media:Schedule-build1.odt|Build Schedule]]</s><br />
: Build and Post-Build sign-in sheets that live on a clipboard at the Volunteer Desk. <br />
<br />
; [[Media:washyerhands.odt|Build Signage]]<br />
: A copy of the reminder to volunteers to wash their hands, to be coupled with the Toxins chart (under "Tabling").<br />
<br />
; [[Media:BuildInstructorOrientation.odt|Build Instructor Orientation]]<br />
: Checklist for new Build Instructors<br />
<br />
; [[Media:Teaching_Philosophy.odt|Build Teaching Philosophy]]<br />
: Teaching philosophy of the Build program.<br />
<br />
; [[Media:Build_Checklist.odt|Build Checklist]]<br />
: Assembly and QC Checklists<br />
<br />
; [[Media:Basiccheck.odt|Basiccheck Check List]]<br />
: Basiccheck Checklist Packet <br />
<br />
; [[Media:HOLD-_Build_In_Progress_Labels_(Print_on_Regular_Paper).odt|HOLD: Build In Progress Labels]]<br />
: Labels for storage of systems mid-QC/Assembly on shelves below the Build bench (Print on Regular Paper)<br />
:[[Hold In-Progress Color Code Guide]]<br />
<br />
; [[Media:warehouse_signage.svg|Build Shelves Warehouse Signage]]<br />
: Sign warning against opening systems in the warehouse without instructor supervision.<br />
<br />
===Specs and information===<br />
; [[Media:Certevaltrainers.odt|Certified Eval Trainers]]<br />
: List of staff, subs, and volunteers who are Eval instructors<br />
<br />
; [[Media:Build-specs.odt | Build Specs]]<br />
: The current build specs in an easy to print form. Please use our color printer (Dazzle) to print these.<br />
<br />
; [[Media:TechSupportPolicy_Build.odt | Tech Support Policy for Builders]]<br />
: This Tech support policy should be given to builders when they take home their FreekBox.<br />
<br />
; [[Media:Post-Build-Application.odt | Post-Build Area Application]]<br />
: This is the Application needed for Builders to move on to Post-Build areas. MAKE SURE TO PRINT THIS DOUBLE SIDED!<br />
<br />
; [[Media:Warehouse-proc-tally.odt | Processor Tally Sheet]]<br />
: This is the tally sheet for our experiment in gathering data on incoming processors before they're processed in SysEval.<br />
<br />
; [[Media:Ram_chart.pdf | RAM Chart]]<br />
: Chart with speeds for DDR, DDR2, and DDR3 with diagrams detailing differences in DIMM and SODIMM.<br />
<br />
; [[Media:Laptop-output-tally.odt | Laptop Output Tally Sheet]]<br />
: This is a tally sheet to keep track of Laptop Output between the Store and HW Grants<br />
<br />
===Labels===<br />
; [[Media:Freekbox-keeper.glabels|Freekbox Keeper Label]]<br />
: Keeper label for desktop systems that fall within Freekbox specs. Should be printed on ''yellow'' paper if non-FG-PDX and ''orange'' paper if FG-PDX.<br />
<br />
; [[Media:Highend-keeper.glabels|Highend Keeper Label]]<br />
: Keeper label for desktop systems that fall within Highend specs. Should be printed on ''green'' paper<br />
<br />
; [[Media:Regular-keeper.glabels|Regular Keeper Label]]<br />
: Keeper label for desktop systems that fall within Regular specs. Should be printed on ''blue'' paper<br />
<br />
; <strike>[[Media:Keeper.glabels|Keeper (Green Light) Labels-5963 or 5163]]</strike><br />
:Old Prebuild keeper labels. Mothballed as of 28 Nov 2012<br />
<br />
; [[Media:Fg-pdx.glabels|FG-PDX Labels-5167]]<br />
:These are the labels that designate that the computer came from the city.<br />
<br />
; [[Media:PYB-FGPDX_Label.glabels|PYB/FG-PDX Labels - 5167]]<br />
:These are the labels for the FG-PDX systems to be granted to Portland Youth Builders<br />
<br />
; [[Media:Recycle.glabels|Reason for Recycle Labels-5962 or 5162]]<br />
:These are the labels used in system evaluation to indicate a system is to be recycled and why. They belong in the system evaluation area.<br />
<br />
; [[Media:Rejected.glabels|Reject Labels-5962 or 5162]]<br />
:These are the labels used throughout the building (except in system evaluation) to indicate a system is to be recycled and why. They belong in the build area.<br />
<br />
; [[Media:Hold.glabels|Hold Labels-5962 or 5162]]<br />
:These are the labels used in system evaluation to indicate a system is to being held for special consideration. They belong in the system evaluation area.<br />
<br />
; [[Media:Uncovered.glabels|Uncovered Electronic Device Labels-5167]]<br />
:These are used to mark CEDs from uncovered entities (other than the first seven).<br />
<br />
; [[Media:Laptop_keeper_2.glabels|Laptop Keeper]] <br />
: New, Avery-free Laptop Keeper labels (10 Jan 2012) (Old labels used Avery Labels 5963 or 5163)<br />
<br />
; [[Media:Laptoprecycle.glabels|Laptop Recycle Labels-5962 or 8462 or 5162]]<br />
<br />
; [[Media:HardDriveRemoved.glabels|Hard Drive Removed labels-5167]]<br />
: Little labels for recycle laptops and for devices from system eval that are not systems but may have had hard drives.<br />
<br />
; [[Media:MotherboardLabels.glabels|MoBo Labels-5963 or 8463 or 5163]]<br />
:These are the labels used in Advanced Testing to indicate a MoBo that is Tested and good. They belong in the Advanced testing area.<br />
<br />
; [[Media:As-Is_laptop_label.glabels|As-Is Laptop Labels--Avery 5963 Shipping Labels]]<br />
<br />
; [[Media:Scraptops.glabels|"Scraptops" Parts Laptop labels--Avery 5963 Shipping Labels]]<br />
<br />
; [[Media:password_only.glabels|Password=Freegeeks -- Avery Return Address Labels 5167]]<br />
: ''NOTE: Updated version of the password labels for Laptops & Systems''<br />
<br />
; [[Media:User_password.glabels|Username and Password Labels--Avery 5167]]<br />
: ''NOTE: Needs to be updated. Nowhere will the user normally encounter the Username OEM. Probably should be changed to "Default User; Password: "''<br />
<br />
; [[Media:Parts_Only_Laptop.glabels|Label for "Parts Only Laptop"--Avery 5963]]<br />
<br />
; [[Media:DNR.glabels|Do Not Retest Labels]] (Avery return address)<br />
: Labels used to mark items for recycling<br />
<br />
; [[Media:New_laptop_hdd_label.glabels|New Laptop HDD Labels]] (Avery return address)<br />
: Labels to distinguish laptop HDDs ordered online<br />
<br />
===HOWTO Print Labels===<br />
*Open browser, go to Free Geek Wiki.(http://wiki)<br />
*Search for "deadtrees".<br />
*Go to section for Labels.<br />
*Find desired label (if unsure, go by description given). Once you have found desired label/s, look at the number next to label title. This is the label size code. See label boxes next to printer.<br />
*Get desired number of blank label sheets of the correct label size. This number is in upper right-hand corner of label sheet. (ex. Label sheets for Keepers are numbered 5963 or 5163)<br />
*Place sheet/s in top (front) tray of Library printer, face up.<br />
*Click on desired label type, then on "OK". This opens glabels screen. Wait for form to appear.<br />
*Press Ctrl-p and select desired number of copies, up to 10.<br />
*Check the "printer" tab to make sure printer is set to "label".<br />
*Press "print".<br />
<br />
== Distribution ==<br />
;[[Media:FGShortSurvey.pdf|Distro Short Survey]]<br />
: Survey to collect data on end user needs, demographics and computer use history<br />
<br />
;[[Distro Survey Promotion Flyer]]<br />
: Promotion flyer for 2012 Distro Survey participation<br />
<br />
==Donations Desk==<br />
<br />
; [[Media:Credit Card Receipt Form.odt|Credit card receipt form]]<br />
: Used when purchasing items with the debit card. <br />
<br />
; [[Media:reimbursement.odt|Reimbursement Form]]<br />
: To reimburse people from the store or front desk tills for purchases made, etc., includes form for petty cash withdrawal.<br />
<br />
; [[Media:Mileage.gnumeric|Mileage reimbursement form]]<br />
: This lives at the front desk and is used to show how much money was spent on reimbursements for Free Geek business travel. It is completed after the trip when the money is reimbursed to the traveler.<br />
<br />
; [[Media:Privacy sign.odt|Privacy Sign]]<br />
: First version! 1/14/2010: "FREE GEEK respects your privacy and takes it very seriously. We will not sell or share your personal information with anyone, and we respect the wishes of all donors in terms of privacy and solicitations. FREE GEEK is committed to earning and keeping your trust."<br />
<br />
; [[Media:Donor FAQ-edit.odt|Donor FAQ Brochure]]<br />
: To provide donors with all sorts of info regarding donating hardware, ranging from Oregon E-cycles info to hard drive wiping suggestions.<br />
<br />
; [[Media:Contribution-receipt.odt|Contribution Receipt]]<br />
: For when someone donates money (without gizmos) and wants a nice official receipt. '''We can enter these kinds of donations in the database now!''' But if the database is down and you need a donations receipt, download this, fill it out, print two copies -- one for the contributor, and one to put in the till.<br />
<br />
; [[Media:Contractor_Log.ods| Visitor Log]]<br />
: Please have any visitor, like a contractor, new vendor, special person getting a tour outside of regular tours, sign in and out on this log. This log is to determine who is in the building besides paid staff and signed in volunteers in case of an emergency.<br />
<br />
; [[Media:Receipt-log.odt|Receipt log]]<br />
: For use by hardware donations workers and the front desk and at pickup events. This should be filled out so a normal receipt can be entered when the database is again accessible.<br />
<br />
; [[Media:Paper-receipt.odt|Generic donation form]]<br />
: For use by hardware donations workers and the front desk and at pickup events. This can be given to donors in lieu of a regular receipt.<br />
<br />
; [[Media:TourSchedule.odt|Tour Schedule]]<br />
: For weekly scheduling of the tour.<br />
<br />
; [[Media:Other_recyclers.odt|Other Recyclers]]<br />
:A list of recyclers who take the items we do not: styrofoam, fluorescent lights, microwaves, copiers, etc.<br />
<br />
==Education==<br />
; [[Media:Current_Classes_Trifold.pdf|Current Class Trifold (PDF)]] (Class Brochure)<br />
; [[Media:Current_Classes_Trifold.odt|Current Class Trifold (ODT)]] - Do not print, only for editing purposes<br />
: Current class schedule and descriptions - if these are not current, please tell the Education Coordinator (Darren) - Please print on colored paper of current month, if possible. (March's color is hot pink!)<br />
; [[Media:Getting Started with your Free Geek Computer Handout.odt|Getting Started with Your Free Geek Computer Handout]]<br />
: How to install proprietary software using the command line<br />
; [[Media:Getting_Started_with_your_Free_Geek_Computer_Handout_Spanish.odt|Getting Started with you Free Geek Computer In Spanish]]<br />
: How to install proprietary software for Spanish-speaking volunteers/buyers<br />
; [[Media:Plug_Into_Portland_.odt|Plug into Portland]]<br />
: Adoption program for Portland-area students who volunteer through their schools.<br />
; [[Media:Teacher questions.odt|New Teacher Form]]<br />
; [[Media:Manual_v1.0.odt|10.04 Manual]]<br />
:The most recent version of the manual that is shipping with all of our systems.<br />
<br />
'''Deprecated (currently unused)'''<br />
; [[Media:Classes at free geek.odt|Class Descriptions]]<br />
<br />
; [[Media:Newclassforms.odt|Adoption Class Forms]] <br />
: New! To be used for our adoption classes. Space for students and auditors is clearly marked, with call-back directions and ample notation space.<br />
; [[Media:Monthlyclassforms.odt|Monthly Class Forms]] <br />
: This can be used for any of our monthly class sessions, just print out, fill in and file in the appropriate class book. Use for Adoption, Command Line and the various monthly classes we offer. Only one session of any given class is listed per page for simplicity. Space for students and auditors is clearly marked, with call-back directions and ample notation space.<br />
; [[Media:Getting Started description.odt|Getting Started Class Descriptions]]<br />
; [[Media:Class at Free Geek for Hardware Grants.odt| Classes at Free Geek for Hardware Grants Recipients]]<br />
: This is a flyer to give out to grant recipients that explains what classes are available at Free Geek.<br />
<br />
== Hardware Grants ==<br />
* [[Media:Class at Free Geek for Hardware Grants.odt| Classes at Free Geek for Hardware Grants Recipients]]<br />
: This is a flyer to give out to grant recipients that explains what classes are available at Free Geek.<br />
<br />
* [[Media:Donationlettertemplate.odt| Donation Letter]]<br />
: Sometimes organizations request a donation letter stating the items that Free Geek granted them. Here is a template to be filled in and signed by the grant shepherd and then given to the organization, whether via fax, mail, or in person.<br />
<br />
== Hardware Testing ==<br />
; [[Media:Power_Adapter_Sorting_2.0.odg|Power Adapter Sorting 2.0]]<br />
: NOT Currently used by Hardware Testing<br />
<br />
; [[Media: Tested By Stickers.glabels|Tested By Stickers--Avery 5167]]<br />
: Little stickers with space for initials of tester.<br />
<br />
; [[Media:Powers_ON_Untested_Labels.pdf|Powers On/Untested Stickers--Avery 5167]]<br />
: Little stickers.<br />
<br />
; Tested Cell Phone Labels - 5963 or 8463 or 5163<br />
: Hardware Testing labels for tested phones being sent to the store.<br />
<br />
; [[Media:NoProc.glabels|No Processor Labels - Avery 5167]]<br />
: Hardware Testing labels for tested phones being sent to the store.<br />
<br />
; [[Media:Hard_drive_labels.glabels|Hard drive tested stickers--Avery 5167]]<br />
: Little stickers that say "___ Gigabytes" & "Tested by ___" [[User:Koopa|Ian]] 00:15, 22 April 2009 (UTC)<br />
<br />
; [[Media:Mobo_Label.pdf|Tested motherboard stickers]]<br />
: Stickers with details on tested motherboards<br />
<br />
; [[Media:Optical-drive-labels.glabels|Tested Optical Drive Labels - Avery 5167]]<br />
: Stickers for marking what functions a tested optical drive performs.<br />
<br />
; [[Media:Power_Adapter_Tracking_Slip.odt|Power Adapter Tracking Slip]]<br />
: Tracking Slip for Power Adapters as they wend their way thru FreeGeek.<br />
<br />
; [[Media:AdvTestIntrnChecklist.gnumeric|Hardware Test Intern Tasks Checklist]]<br />
<br />
===RAM Testing===<br />
; [[Media: Tested by RAM.glabels|Tested by Stickers - RAM --Avery 5167]]<br />
: Little stickers for tested RAM<br />
<br />
; [[Media: MemTest_Station_Labels_DDR.pdf|Memory Testing Station Labels - DDR --Avery 5963]]<br />
; [[Media: MemTest_Station_Labels_DDR2.pdf|Memory Testing Station Labels - DDR2 --Avery 5963]]<br />
; [[Media: MemTest_Station_Labels_DDR3.pdf|Memory Testing Station Labels - DDR3 --Avery 5963]]<br />
: Labels to put on Memory Testing Stations that describe what type/speed/capacity of RAM that station can test. Print on Avery 5963 labels and put on the power supply of the station you are labeling.<br />
<br />
==help.freegeek.org==<br />
* [[Media:Install_Hard_Drive.pdf| How to Install and Format a Hard Drive]]. Handout in pdf form. This a trifold leaflet. It needs to be printed Double sided -- flip short side.<br />
<br />
==Inreach==<br />
; [[Media:Adoption_Certificate.odt|Adoption Certificate]]<br />
: To be filled out by staff and/or adoption teachers and distributed with system and a button as proof of completion of program and earning a computer.<br />
<br />
; [[Media:Build_Certificate.odt|Build Certificate]]<br />
: To be filled out by staff and/or build instructors and distributed with system and a button as proof of completion of program and earning a computer.<br />
<br />
== Library ==<br />
* [[Media:Free geek library sign.odt| How to Check Out books from Library]]<br />
: How to check out books from the Free Geek Library<br />
<br />
* [[Media:computer_login.ods| Library Computer Lab Login Sheet]]<br />
: Blank login sheets for computer lab. Double-sided. Print as needed.<br />
<br />
;[[Media:Acceptable_use_policy.odt|Acceptable Use Policy]]<br />
: This is posted on the wall next to public access terminals and should reflect the actual [[Acceptable Use Policy]] on this wiki. It also warns users about limits to using the public terminals.<br />
<br />
== Mac Land ==<br />
See [[MacBuild Documents]]<br />
<br />
== Office ==<br />
<br />
; [[Media:Employee_emergency_info.odt|Employee Emergency Injury Information]]<br />
:Print out on bluish paper and cut apart. Have these printouts on hand with Incident/Accident Reports, located in the BLUE folder at the VOLUNTEER DESK. Follow [http://wiki.freegeek.org/index.php/Injury_Logging_Procedure this link] for the emergency injury process in detail. This card will be handed off to an injured employee to seek treatment.<br />
<br />
; [[Media:Volunteer_emergency_info.odt|Volunteer Emergency Injury Information]]<br />
:Print out on reddish paper and cut apart. Have these printouts on hand with Special Risk Accident Claim Form reports, located in the RED folder on Richard's desk. Follow [http://wiki.freegeek.org/index.php/Injury_Logging_Procedure this link] for the emergency injury process in detail. This card will be handed off to the injured volunteer to seek treatment.<br />
<br />
; [[Media:supply.odt|Supply Replacement List]]<br />
<br />
; [[Media:Ombudsman.odt|The Role of The Ombudsman]]<br />
: Posted at the Donor Desk, Volunteer Desk and Thrift Store - shows the current Ombudsman and HR members who can serve as alternative Ombudsmen.<br />
<br />
; [[Media:Conflict-of-interest-agreement.odt|Conflict of Interest Agreement]]<br />
<br />
; [[Media:Statecontinuationletter.odt|State Continuation Election Form]]<br />
: For health plan administrator use. Signed by outgoing employees who were covered by our health plan.<br />
<br />
; [[Media:Letterhead.odt|Blank letterhead - slogan is "COMPUTERS INTERNET EDUCATION THRU RECYCLING"]]<br />
: Do not use for evil purposes.<br />
<br />
; [[Media:new_letterhead.odt|Blank letterhead - New! - slogan is "Helping the needy get nerdy since the beginning of the third millenium..."]]<br />
: Do not use for evil purposes.<br />
<br />
; [[Media:Faxcover.odt|Fax Cover Sheet]]<br />
<br />
; [[Media:Determination-letter.png| Letter of Determination]]<br />
: This is the letter from the IRS that shows we are a 501(c)(3) tax-exempt organization.<br />
<br />
==Outreach== <br />
; [[Media:Spanish_Outreach_1.odt|Spanish Build Outreach Flier]] <br />
: This is the bilingual outreach flier for the Spanish Build program. <br />
; [[Media:Free_geek_hi-res.svg|Free Geek Logo]]<br />
: Scalable Vector Graphic of Free Geek's logo.<br />
<br />
; [[Model Release/Permission for Photography]]<br />
: For using a picture of anyone in print, on website, etc. File these forms in PR cabinet, or hand to PR member. Photo release forms are not required for all printed pictures. See [http://fairuse.stanford.edu/Copyright_and_Fair_Use_Overview/chapter12/12-b.html When to use a Release] for more information.<br />
<br />
; <s>[[Media:Photo_Release_Form.pdf|Photo Release Form]]</s> - Do not use. Superseded by above.<br />
: For using a picture of an adult in print, on website, etc. File these forms in PR cabinet, or hand to PR member.<br />
<br />
; <s>[[Media:Minor_Photo_Release_Form.pdf|Minor Photo Release Form]]</s> - Do not use. Superseded by above.<br />
: To be signed by parent before using a picture of an minor in print, on website, etc. File these forms in PR cabinet, or hand to PR member.<br />
<br />
; [[Media:Adoption-outreach.odg|Adoption Outreach Flyer]]<br />
: Earn-a-computer tear-off sheets. Outreach. For hardware grants use. Given to organizations receiving grants from us. Outreach.<br />
<br />
; [[Media:Donor_email_signup.odt|Donor email signup]]<br />
: For PR to collect donor emails for quarterly email newsletter.<br />
<br />
; [[Media:Spanish Etiquette .odt|Spanish Etiquette Brochure]] <br />
: The Etiquette Brochure translated. <br />
; [[Media:TriFoldBrochureTEMPLATE.odt|Tri-Fold Brochure Template]]<br />
: '''Note:''' To print these correctly, make sure to select "Short Edge (Flip)" under Duplex options (look under "Properties" to find Duplex options)<br />
<br />
; [[Media:Thanks.odt|Thank You Template]]<br />
: Thank you letter template to be mailed out for donations over $100, with or without hardware. See [[Processing Monetary Donations]] for further instructions or an e-mail template.<br />
<br />
=== Tabling ===<br />
; [[Media:Outreach_Final_Document.odt|Informational Packet and Training for Tabling Events]]<br />
<br />
; [[Media:Offsite_donation_receipt.odt|Offsite Donation Receipt]]<br />
: Small receipts to give to offsite donors<br />
<br />
; [[Media:Offsite_Donation_Receipt_Log.odt|Offsite Donation Receipt Log]]<br />
: Log of donations for input in the database<br />
<br />
; [[Media:Newsletter_signup.odt|Newsletter sign up]]<br />
: Signup sheet for regular Free Geek newsletter<br />
<br />
; [[Media:Programs_short.odt|Programs_short]]<br />
: Quick explanation of Free Geek, adoption, and build programs.<br />
<br />
; [[Media:Toxins.odg|Toxins]] (hazardous materials)<br />
: Chart explaining toxins present in computers.<br />
<br />
; [[Media:g2g brochure.odt|Girls2Geeks Brochure]] <br />
<br />
; [[Media:Plug_Into_Portland_.odt|Information about Plug Into Portland]]<br />
<br />
; [[Media:Outreach_events_volunteer_log.odt|Outreach and Tabling Events Volunteer Log]]<br />
<br />
==Prebuild Program Information==<br />
;[[Media:Toolbox-checkout.gnumeric|Tool Box Checkout]]<br />
: Used to check toolboxes out to volunteers in prebuild.<br />
<br />
; [[Media:card sorting cards.gnumeric|Card Sorting Lesson Box Cards]]<br />
: Laminated cards that pre-build volunteers use to label computer cards sorted by connector and appropriate card slot.<br />
<br />
; [[Media:ram sorting card.gnumeric|Ram Sorting Lesson Box Cards]]<br />
: Laminated cards used to label different types of ram.<br />
<br />
; [[Media:Priority Signs.odg|Work on these first]]<br />
: Signs hung above the stack of computers in System Evaluation to let volunteers know they should prioritize these particular rows.<br />
<br />
; [[Media:Prebuild-hdd-autorecycle.svg|HDD Autorecycle Gauge]]<br />
: Signage for indicating what size HDDs need to be auto-recycled. (SVG format, drawn in Inkscape)<br />
<br />
==Printers==<br />
; [[Media:Printer_Fresh_Used_Ink_Scanner.pdf|Printer Test Page]]<br />
: Print this as a test page and attach to store and grant ready printers<br />
<br />
; [[Media:Printer_scanner_as_is_no_ink.pdf|Printer As is test page]]<br />
: Print this as for tested printers that are to be sold with No Ink<br />
<br />
; [[Media:Printer_Scanner_Test_Page.pdf|Scanner test page]]<br />
: Print this page for tested scanners.<br />
<br />
; [[Media:Printer_Fax_Test_Page.pdf|Fax Test Page]]<br />
: Print and Fax this as a test page then attach to store and grant ready Fax machines.<br />
<br />
; [[Media:Printer_Sales_Form.pdf | Printers vendors Sales Tally Sheet]]<br />
: This page is to be printed out for the vendors to record there purchases from Printer land.<br />
<br />
== Receiving ==<br />
; [[Media:Receiving-slip.gnumeric|Hardware Contribution Slip aka Tally Sheet (tally sheet)]]<br />
: Current "receiving-donation-form", for use by hardware donations workers and the front desk<br />
<br />
; [[Media:Uncovered.glabels|Uncovered Electronic Device Labels-5167]]<br />
:These are used to mark CEDs from uncovered entities (other than the first seven). Print these on Dazzle in the Wine Cellar - one at a time!<br />
<br />
; [[Media:Other_recyclers.odt|Other Recyclers]]<br />
:A list of recyclers who take the items we do not: styrofoam, fluorescent lights, microwaves, copiers, etc. <br />
<br />
; [[Media:ReceivingOpenCloseList.odt|Opening/Closing Checklist]]<br />
:A list of tasks to be completed before opening and after closing. Should be posted in Receiving near the laptop, and staff members should sign when tasks are completed.<br />
<br />
; [[Media:Keyboard Testing.odt|Keyboard Testing]]<br />
: Updated 4/27/2010 [[User:Brittany|Brittany]] 01:15, 30 April 2010 (UTC)<br />
<br />
; [[Media:Mouse Testing.odt|Mouse Testing]]<br />
: This is no longer in use.<br />
: Updated version can be found on the here: [[Mouse Testing]]<br />
<br />
; [[Media:SpeakerTestingInstructions.odt|Speaker Testing Instructions]]<br />
:Step-by-step instructions for testing speakers in the Basic Testing area of Receiving. --[[User:Scrump|Scrump]] 00:10, 3 August 2012 (UTC)<br />
<br />
; [[Media:Items we do not take.odt|Items we do not take]]<br />
: A visual guide to items we do NOT accept in hardware donations: microwaves, smoke detectors, large appliances, florescent light bulbs, styrofoam, and batteries.<br />
<br />
; [[Media:Printer Triage Modified.odt|Printer Triage Modified]]<br />
: This is no longer in use.<br />
<br />
; [[Media:Special requests.odt|Special Requests for Receiving]]<br />
: This is no longer in use.<br />
<br />
; [[Media:Staff_FYI.odt|Staff Update FYI]] - <br />
: A template for letting receiving staff know when things change. Includes staff members' names as of Nov. 09.<br />
<br />
; [[Media:Testing Stations.odt|Testing Stations]]<br />
: Signs for Mouse Testing, Keyboard Testing, and Speaker Testing.<br />
: Additional Receiving box signs for Keyboard Testing can be found here: [[Keyboards (Receiving)]]<br />
: Additional Receiving box signs for Mouse Testing can be found here: [[Mouse Testing]]<br />
<br />
; [[Media:Wash Your Hands.odt|Wash Your Hands]]<br />
: Seriously, guys. They're filthy.<br />
<br />
; [[Media:Tallysheetcrt.odt|Tally Sheet Clarification]]<br />
: A visual aid to help clarify between Systems w/CRTs (or Systems w/LCDs) vs. Systems and their separate monitors<br />
<br />
; [[Media:Stealing is a crime.odt|Stealing From This Donation Site Is a Crime]]<br />
: A sign for the donations door (as well as the info/volunteering door) to let people know that stealing from this donation site is a crime.<br />
<br />
;[[Media:No dumping sign.odt|No Dumping sign]]<br />
: A sign for the donations door (as well as the info/volunteering door) to let people know that leaving donations other than during business hours is considered illegal dumping.<br />
<br />
;[[Media:Solid state hard drive.odt|Solid State Hard Drive vs. Laptop SODIMM]]<br />
: One needs to be locked up b/c of personal info, the other does not.<br />
<br />
=== Receiving Box Labels ===<br />
All receiving box labels can be found here: [[Receiving Boxes]]<br />
<br />
==Recycling==<br />
<br />
; [[Media:OutgoingMaterialsReport.odt|Outgoing Materials Report]]<br />
: Use for all shipments from Recycling<br />
; [[Media:Shipment ID.odt|Shipment ID]]<br />
: To identify gaylords and what's in them<br />
; [[Media:Twice_Weekly_Forklift_Checklist.odt|Twice Weekly Forklift Checklist]]<br />
: Forklift must pass this checklist before use<br />
; [[Media:WhoGetsWhat.odt|Who Gets What]]<br />
: Which Vendor gets which commodity<br />
; [[Media:MonitorTestRunTime.ods|Monitor Test RunTime]]<br />
: Monitor Test uses this to make sure they run the Monitor for at least 1 hour<br />
; [[Media:ToolKitChkOutChkIn.odt|ToolKit CheckOut/CheckIn]]<br />
: ToolKit Checkout/Checkin Form<br />
; [[Media:CRT_Inventory.odt|CRT Inventory form]] - OBSOLETE<br />
: Record how many CRT Monitors are waiting to go into the gaylords<br />
; [[Media:WarehouseChecklist.odt|Warehouse Closing Checklist]]<br />
: Use at end of business day in Recycling. Posted at back door.<br />
; [[Media:Warehouse_used_glove_notice.odt|Used glove notice]]<br />
: Label the used glove bin and post the notice that gloves are used/please wash hands.<br />
; [[Media:WrhsVolIntrnChcklst.gnumeric|Warehouse Volunteer Intern Checklist]]<br />
: Checklist of all warehouse tasks available to a volunteer intern, used to track progress.<br />
<br />
==Sales: Online / Bulk==<br />
; [[Media:Bulk sales tally sheet.ods| Bulk sales tally sheet]]<br />
:This sheet should be delivered to the thrift store with merchandise that is being sold as a "bulk sale". If an invoice has already been made for the sale in the database this form is not necessary.<br />
<br />
; [[Media:Online sales tally sheet (for in store pickups).ods| Online sales tally sheet (for in store pickups)]]<br />
:This sheet should be delivered to the thrift store with merchandise that is being sold as an "Online sale". If payment, or an invoice (in our database) has already been made for the sale, a copy should be attached to this sheet.<br />
<br />
; [[Media:FG_insert_for_Amazon.odt| Feedback request to include in Amazon sales shipments.]]<br />
<br />
<br />
; [[Media:FG insert for Ebay.odt| Feedback request to include in Ebay sales shipments.]]<br />
<br />
<br />
<br />
; [[Media:Ebay_intial_eval_form.odt| eBay evaluation form]]<br />
: A work in progress<br />
;[[Media:Online_sales.glabels|Online Sales Label]]<br />
:Something to stick on items for sale so we know what's what.<br />
<br />
==Server Build==<br />
Labels we use in the build and QC process:<br />
; [[Media:Server_Specs.pdf|Server Spec Labels]]<br />
; [[Media:Server_Build-QC_Checklist.pdf|Server Build/QC Checklist sheets]]<br />
; [[Media:Server_Labels_S1-S80.pdf|Server Tags S1 - S80]]<br />
; [[Media:Server_Labels_S81-S160.pdf|Server Tags S81 - S160]]<br />
<br />
<br />
==Spanish Information==<br />
;[[Media:Spanish Volunteer Information.odt|Spanish Info Form]]<br />
:For all Spanish speakers interested in volunteering at Free Geek.<br />
<br />
; [[Media:Voluntarios_-1.odt|Spanish Volunteer Orientation Packet]] <br />
:Orientation Packet for Spanish-speaking folks. <br />
<br />
; [[Media:Volunteer_application_spanish.odg|Spanish Volunteer Application]] <br />
:Application for Spanish-speaking folks.<br />
<br />
; [[Media:FG_Brochure_esp.odt|Free Geek Spanish Brochure]]<br />
: Spanish version of the Free Geek Brochure for editing<br />
<br />
; [[Media:FG_Brochure_esp.pdf|Free Geek Spanish Brochure]]<br />
: Spanish version of the Free Geek Brochure '''for printing'''<br />
<br />
== Supported formats ==<br />
We currently support these formats for upload:<br />
* OpenOffice Graphics files (.odg)<br />
* OpenOffice Text files (.odt)<br />
* Gnumeric spreadsheet files (.gnumeric)<br />
* Glabels label files (.glabels)<br />
* Portable Network Graphic (.png)<br />
* Portable Document Format (.pdf)<br />
<br />
Most other formats are not supported for upload.<br />
<br />
If the files listed below are not being used, we should simply archive their old PS files and remove them from this list. Otherwise, we should take measures to get versions in supported formats uploaded.<br />
<br />
=== html (switch formats): ===<br />
(We will not support the upload of HTML files. Switch the format to something else and we will upload that instead. Links to the postscript and the most recent html files are included.)<br />
* build-qc.html [http://web.freegeek.org/deadtrees/mulch/ps/build-qc.ps] [http://dev.freegeek.org/projects/deadtrees/browser/trunk/mulch/sources/build-qc.html?format=raw]<br />
* burninbatch.html [http://web.freegeek.org/deadtrees/mulch/ps/burninbatch.ps][http://dev.freegeek.org/projects/deadtrees/browser/trunk/mulch/sources/burninbatch.html?format=raw]<br />
* specs.html [http://web.freegeek.org/deadtrees/mulch/ps/specs.ps] [http://dev.freegeek.org/projects/deadtrees/browser/trunk/mulch/sources/specs.html?format=raw]<br />
<br />
==Tally Sheets==<br />
; [[Media:Generic-tally.gnumeric|Generic tally sheet]]<br />
: This is the recycling tally sheet that could be used anywhere. It tracks how many recycle gizmos we send out. Data entry volunteers can use this to enter data in the database.<br />
<br />
; [[Media:Evaltally.gnumeric|Evaluation Tally sheet]]<br />
: This is the system evaluation tally sheet that hangs on the cart in system evaluation. It tracks how many '''regular''' keeper and how many recycle systems we send to the warehouse. Data entry volunteers use this to enter data in the database<br />
<br />
; [[Media:Eval-misc-tally.gnumeric|Misc Eval tally sheet]]<br />
: This is the system evaluation tally sheet that hangs '''above''' the cart in system evaluation. It tracks how many '''irregular''' recycle systems we send to the warehouse. (These irregular systems are macs, or have integrated monitors.) Data entry volunteers use this to enter data in the database.<br />
<br />
; [[Media:Inventory-tally.gnumeric|Inventory Tally Sheet]]<br />
: This is used during inventory at the end of the month.<br />
<br />
; [[Media:Mac-tally.gnumeric|Macintosh Tally Sheet]]<br />
: This is used to mark Macintosh Systems as recycled.<br />
<br />
; [[Media:CRT-Monitor-tally.gnumeric|CRT (and LCD) Monitor Tally Sheet]]<br />
: This is used to mark CRT Monitors as recycled. It also has room for LCD Monitors since they may be moving to the warehouse.)<br />
<br />
; [[Media:TV-tally.gnumeric|TV Tally Sheet]]<br />
: This is used to mark CRT and LCD TVs as recycled.<br />
<br />
; [[Media:Monitor-tv-tally.gnumeric|Monitor and TV Tally Sheet]]<br />
: More generic. This is used to mark CRT and LCD monitors and TVs as recycled.<br />
<br />
; [[Media:Laptop-tally.gnumeric|Laptop Tally Sheet]]<br />
: This is used to mark Laptops (Mac and Non-Mac) as recycled.<br />
<br />
; [[Media:Printerland-tally.gnumeric|Printerland Tally Sheet]]<br />
: This is used to mark gizmos typically found in Printerland as recycled.<br />
<br />
; [[Media:LCD_test_tally.gnumeric|LCD Monitor Recycling Tally Sheet]]<br />
: This is used to tally LCDs sent to recycling.<br />
<br />
; [[Media:InventoryTags.odt|Inventory Tags]]<br />
: These are used to lable gizmos as being disbursed to infrastructure.<br />
: Print on #4013 labels.<br />
<br />
==Tech Support==<br />
; [[Media:Intake_Form.pdf|Tech Support Intake Form]]<br />
:For use when a computer is left at Tech Support to record the adopters name and contact info. Use this to screen for tech support and gather as much info as possible to make their lives a little easier. This now contains two sheets for ease of printing.<br />
; [[Media:Running_windows_programs_in_ubuntu.pdf|Ubuntu for windows converts]]<br />
:Handout for wine Class, or any volunteers wanting general info on running windows programs.<br />
; [[Media:support_outgoing_form.odt| Tech Support Outgoing Form]]<br />
: Use this when a system is leaving tech support and going to build or laptop build<br />
; [[Media:ts_store_credit_form.odt|Store Credit Form]]<br />
: Use this when issuing store credit for a failed system.<br />
;[[Media:New_procedures.pdf|Intake Procedure & Workflow]]<br />
:Intake procedure and work flow for Tech Support<br />
; [[Media:TechSupportPhones.odt|Phone Guide]]<br />
: How to use the Tech Support phones<br />
;[[Media:Tech_support_card.pdf|Tech Support card]]<br />
; Tech Support Card -- you can upload this to Bear Printing to get more cards printed.<br />
; [[Media:New-user-guide-BETA1-20100826.odt| New User Guide (BETA)]]<br />
; See also: help.freegeek.org (further down page)<br />
; [[Media:Tech_Support_Instructionsf_or_Front_Desk.odt| Tech Support Information for Front Desk]]<br />
: Instructions for Front Desk on how to properly intake new boxes and fill in RT forms.<br />
<br />
== Thrift Store ==<br />
See [[Store Docs]]<br />
<br />
==Volunteer Desk==<br />
===Volunteer Info===<br />
; [[Media:Volunteer_orientation_packet.odt|Volunteer Orientation Packet]]<br />
:Orientation packet to go home with each new volunteer when taking their first tour.<br />
<br />
; [[Media:Volunteer_application.odg|Volunteer Application]]<br />
:Application to be completed in full (all bold field required) by new volunteers, after reading the Volunteer Orientation Packet.<br />
<br />
; [[Media:Volunteering_for_school_credit_guidelines.odt|Volunteering for School Credit]]<br />
:Please hand this form to people interested in volunteering for high school or college credit.<br />
<br />
; [[Media:Comm_svc_info_sheet.odt|Community Service Info Sheet]]<br />
:Give this information sheet to all volunteers inquiring about doing Court Community Service with us.<br />
<br />
; [[Media:Group_Volunteering_at_FG-2.odt|Group Volunteering]]<br />
: Details and contact information for Groups interested in Group Volunteering.<br />
<br />
; [[Media:Group Volunteer Form.odt|Group Volunteer Form]]<br />
: This is the form that is given to large groups when they come to volunteer. They should fill this out before/while they volunteer. They should fill out a new form each time they come to volunteer.<br />
<br />
; [[Media:FG_brochure_grayscale.odt|Free Geek Brochure (Grayscale)]]<br />
: These are for the general public to learn more about Free Geek. For printing: Select Print, in the print box, select properties, under the paper tab, select "short edge (flip)" in the duplex space, select OK. Now enter the number of copies you want and click "collate." Press OK. It is always good to print a few first to make sure layout is right.<br />
<br />
; [[Media:FG_brochure_color.odt|Free Geek Brochure (Color)]]<br />
: This is the fancier color version of the brochure (for tabling, outreach, etc.). For printing: Select Print, in the print box, select properties, under the paper tab, select "short edge (flip)" in the duplex space, select OK. Now enter the number of copies you want and click "collate." Press OK. It is always good to print a few first to make sure layout is right.<br />
<br />
; [[Media:Current_Classes_Trifold.pdf|Current Class Trifold (PDF)]] (Class Brochure)<br />
: Current class schedule and descriptions - if these are not current, please tell the Education Coordinator (Darren) - Please print on colored paper of current month, if possible.<br />
<br />
; [[Media:Email_lists_signup.odt|Email Lists SignUp Sheet]]<br />
: This signup sheet for public email lists is posted on the Tech Support window by the volunteer desk. Print on 11x17 paper.<br />
<br />
; [[Media:Application_instruction_halfsheet.odt|Volunteer Intern Application Instructions Halfsheet]]<br />
: Please print this out to give to prospective volunteer interns.<br />
<br />
===Other Volunteer Desk Info===<br />
; [[Media:Styrofoam_recycling.odt|Styrofoam Recycling Information]]<br />
: To provide donors with information regarding styrofoam recycling.<br />
<br />
;[[Media:Class cards.odt|Reminder Cards]]<br />
:These reminder cards can be used for shifts or for classes. <br />
<br />
; [[Media:FD_EQUIPMENT_FORM.odt|Equipment Pass]]<br />
: When people want to bring tools, laptops, PCs, etc. into the building please use this form.<br />
<br />
; [[Media:Mental-health-crisis.jpg|Mental Health Crisis Information Poster]]<br />
: Post in bathrooms, behind volunteer and donor desk, etc.<br />
<br />
==Routine Facilities==<br />
; [[Media:After-hours-access-log.gnumeric|After hours access log]]<br />
:After hours access sign in and sign out log, located near the alarm access panel near the meeting room.<br />
; [[Media:Cleaning-log.gnumeric|Cleaning log]]<br />
:Cleaning log, located in each bathroom and kitchen for recording daily status.<br />
; [[Media:FG_Vehicle_Checklist.odt|FG Vehicle Checklist]]<br />
:Monthly Checklist for Free Geek Truck to be filled out at the beginning of each month and saved in a folder.<br />
<br />
==Obsolete?==<br />
* [[Media:Store_Agreement.odt]] [[User:Koopa|Ian]] 21:34, 16 December 2010 (UTC)<br />
* [[Media:Classsched1.odg]] <br />
* [[Media:Classsched2.odg]]<br />
* [[Media:Schedule-adv-testing.odt]]<br />
* [[Media:Schedule-class-adoption.odt]]<br />
* [[Media:Schedule-class-commandline.odt]]<br />
* [[Media:Schedule-class-linux.odt|Schedule Class]]<br />
* [[Media:2008 geek brochureFINAL.pdf|2008 Contributions Brochure]]<br />
* [[Media:Community Recipients and Testimonials.odt|Community Recipients and Testimonials]] ([[Media:Community Recipients and Testimonials.pdf|PDF]])<br />
<br />
* [[Media:Legal_Adoption_Schedule-2.odt|Legal-size Adoption Schedule]] - Schedule and sign-in sheet (legal sized paper) for the 24 hour adoption program. Print on VOLPRINT1. <br />
* [[Media:Prebuild_Schedule.gnumeric|Prebuild schedule]] - This is the schedule used to sign up volunteers for Hardware ID and System Evaluation ("Pre-Build"). It lives on a clipboard at the Volunteer Desk.<br />
* [[Media:Schedule-build1.odt|Build Schedule]] - Build and Post-Build sign-in sheets that live on a clipboard at the Volunteer Desk.<br />
* [[Media:Builders_Clipboard_Cover.odt|Cover Sheet to the Build Schedule]] - Cover page for the Builder's Clipboard.<br />
* [[Media:Newclassforms.odt|Adoption Class Forms]] - New! To be used for our adoption classes. Space for students and auditors is clearly marked, with call-back directions and ample notation space.<br />
* [[Media:Monthlyclassforms.odt|Monthly Class Forms]] - This can be used for any of our monthly class sessions, just print out, fill in and file in the appropriate class book. Use for Adoption, Command Line and the various monthly classes we offer. Only one session of any given class is listed per page for simplicity. Space for students and auditors is clearly marked, with call-back directions and ample notation space.<br />
; [[Media:Borrow book.odt|Borrow book log sheets]]</div>Alambhttp://wiki.freegeek.org/index.php?title=File:Email_lists_signup.odt&diff=65473File:Email lists signup.odt2012-12-07T23:59:14Z<p>Alamb: This is the sign-up sheet for adding volunteers & other visitors to public email lists.</p>
<hr />
<div>This is the sign-up sheet for adding volunteers & other visitors to public email lists.</div>Alambhttp://wiki.freegeek.org/index.php?title=Social_Media&diff=65440Social Media2012-12-07T02:08:48Z<p>Alamb: </p>
<hr />
<div>This page exists to document the social media accounts, practices and strategies in use at Free Geek. It is maintained by the PR Committee.<br />
<br />
==Social Media Accounts==<br />
Free Geek currently maintains the following social media accounts:<br />
* Facebook (https://www.facebook.com/freegeekmothership)<br />
* Twitter (https://twitter.com/freegeekpdx)<br />
* Thrift Store Twitter (https://twitter.com/fgthriftstore, maintained largely by Thrift Store staff)<br />
* Linkedin (Profile Name: Free Geek Portland)<br />
<br />
We maintain these accounts through a consolidated account with Hootsuite.com.<br />
<br />
==Posting Schedule==<br />
Currently there is no set schedule for most of our social media postings, many of which correspond to the following topics (this is not an exhaustive list):<br />
* Announcements of Free Geek holiday closures and other deviations from our normal business hours<br />
* Free Geek events<br />
* Special sales and promotions<br />
* Profiles of, and news updates from hardware grant recipients<br />
* Cross-posts from other Reuse organizations both local and international<br />
* Stories in the news related to technology, free&open-source issues, environmental stewardship, and education<br />
<br />
We generally try to post updates to Facebook and Twitter in particular at least 2-3 times per week. All PR members are encouraged to monitor our social media pages and publish posts (containing relevant content!) when they notice that it's been more than 2 business days since the most recent update.<br />
<br />
We are working on a schedule for targeted social media blasts corresponding to each month of the year and typical trending needs associated with each. The work-in-progress schedule is as follows:<br />
* January: Call for Volunteers (theme: New Year's Resolutions)<br />
* February: Call for $$ Contributions (theme: Valentine's Day Free Geek love)<br />
* March: Call for Volunteers esp. Women and Youth (theme: Women's History Month/Women in STEM)<br />
* April: Call for Hardware Donations (theme: Spring Cleaning!)<br />
* May: <br />
* June:<br />
* July: Call for $$ Contributions (theme: vacation time, giving is an alternative to volunteering)<br />
* August: Call for Class Sign-Ups (theme: back-to-school season)<br />
* September: Call for Thrift Store shoppers (theme: back-to-school sales specials)<br />
* October:<br />
* November: Call for Thrift Store shoppers (theme: gift-giving with the Earth in mind)<br />
* December: Call for $$ Contributions (theme: holiday/end-of-year giving)<br />
<br />
Amelia's ideas for May/June/October: <br />
* Tell-a-friend ("Do you know someone who might benefit from our recycling/grants/volunteer/education/sales programs? Tell them about us!)<br />
<br />
==Social Media Strategy==<br />
This is a work-in-progress. Stay tuned for updates!<br />
<br />
<br />
<br />
<br />
<br />
[[Category:PR]]</div>Alambhttp://wiki.freegeek.org/index.php?title=Social_Media&diff=65439Social Media2012-12-07T02:07:42Z<p>Alamb: Created page with "This page exists to document the social media accounts, practices and strategies in use at Free Geek. It is maintained by the PR Committee. ==Social Media Accounts== Free Geek c…"</p>
<hr />
<div>This page exists to document the social media accounts, practices and strategies in use at Free Geek. It is maintained by the PR Committee.<br />
<br />
==Social Media Accounts==<br />
Free Geek currently maintains the following social media accounts:<br />
* Facebook (https://www.facebook.com/freegeekmothership)<br />
* Twitter (https://twitter.com/freegeekpdx)<br />
* Thrift Store Twitter (https://twitter.com/fgthriftstore, maintained largely by Thrift Store staff)<br />
* Linkedin (Profile Name: Free Geek Portland)<br />
<br />
We maintain these accounts through a consolidated account with Hootsuite.com.<br />
<br />
==Posting Schedule==<br />
Currently there is no set schedule for most of our social media postings, many of which correspond to the following topics (this is not an exhaustive list):<br />
* Announcements of Free Geek holiday closures and other deviations from our normal business hours<br />
* Free Geek events<br />
* Special sales and promotions<br />
* Profiles of, and news updates from hardware grant recipients<br />
* Cross-posts from other Reuse organizations both local and international<br />
* Stories in the news related to technology, free&open-source issues, environmental stewardship, and education<br />
<br />
We generally try to post updates to Facebook and Twitter in particular at least 2-3 times per week. All PR members are encouraged to monitor our social media pages and publish posts (containing relevant content!) when they notice that it's been more than 2 business days since the most recent update.<br />
<br />
We are working on a schedule for targeted social media blasts corresponding to each month of the year and typical trending needs associated with each. The work-in-progress schedule is as follows:<br />
* January: Call for Volunteers (theme: New Year's Resolutions)<br />
* February: Call for $$ Contributions (theme: Valentine's Day Free Geek love)<br />
* March: Call for Volunteers esp. Women and Youth (theme: Women's History Month/Women in STEM)<br />
* April: Call for Hardware Donations (theme: Spring Cleaning!)<br />
* May: <br />
* June:<br />
* July: Call for $$ Contributions (theme: vacation time, giving is an alternative to volunteering)<br />
* August: Call for Class Sign-Ups (theme: back-to-school season)<br />
* September: Call for Thrift Store shoppers (theme: back-to-school sales specials)<br />
* October:<br />
* November: Call for Thrift Store shoppers (theme: gift-giving with the Earth in mind)<br />
* December: Call for $$ Contributions (theme: holiday/end-of-year giving)<br />
<br />
Amelia's ideas for May/June/October: <br />
* Tell-a-friend ("Do you know someone who might benefit from our recycling/grants/volunteer/education/sales programs? Tell them about us!)<br />
<br />
==Social Media Strategy==<br />
This is a work-in-progress. Stay tuned for updates!<br />
<br />
<br />
<br />
<br />
<br />
[Category:PR]</div>Alambhttp://wiki.freegeek.org/index.php?title=Keyholders&diff=64750Keyholders2012-10-23T22:21:34Z<p>Alamb: /* T keys */</p>
<hr />
<div>{{RightTOC}}<br />
<br />
== How to get a key ==<br />
* ''Staff amended this to cover apprentices on [http://lists.freegeek.org/pipermail/minutes/2008-March/ March 28, 2008]''<br />
<br />
Core volunteers that need an external key can ask to be granted a key by the staff collective by sending a message to staff@freegeek.org and indicating what they need the key for. The collective will discuss the matter at the next possible staff meeting. Paid interns are granted keys as needed subject to review by the staff collective. If a keyholder loses a key, they must reapply to the staff collective.<br />
<br />
For further information on who gets keys and how check out the [[After Hours Access Policy]]. If you have a key, also read the [[After Hours Access Procedure]].<br />
<br />
=== Notes ===<br />
''All members of the staff collective have keys to both the external (F) and internal (I) doors in the building. Additionally, paid apprentices, other staff, and core volunteers also have these keys as needed, typically (E) or (F) and possibly (I) keys.''<br />
<br />
Some people who used to be keyholders no longer need them. Also, we were unable to adequately review all the previous keyholders. Anyone not on the list who wants a key should send a message requesting one to staff the (see above).<br />
<br />
== Lists of keyholders ==<br />
E and F keyholders need to read and understand the [[After Hours Access Procedure]].<br />
<br />
''Italic names'' = allotted but not handed out yet.<br />
<br />
'''Note: E and F keyholders also need a PIN to arm or disarm the alarm system if they might enter or exit the building after hours. All E and F keyholders should be on the locks list.<br />
<br />
=== F keys ===<br />
'''Do not give out F keys without consulting with Richard. He's in the process of re-numbering the key & alarm code system.''' -djk 6/1/12<br />
<br><br />
''NOTE: ['''F''']ree Geek keys work on '''all''' external doors including the '''after hours access door''' (near the meeting room).''<br />
<br />
* (#1F) '''DO NOT GIVE OUT THIS KEY!! This ADMIN key is kept in the safe for making copies.'''<br />
* (#2F) Austin Crouch<br />
* (#3F) Amelia Lamb<br />
* (#4F) ''in safe''<br />
* (#5F) Liane Kocka<br />
* (#6F) Misty Falls<br />
* (#7F) Richard Seymour<br />
* (#8F) Paul Munday<br />
* (#9F) Darren Heiber<br />
* (#10F) Darryl Kan<br />
* (#11F) Brian Keefer<br />
* (#12F) McGuire Bearing/Jim Conley<br />
* (#13F) Kevin Wright<br />
* (#14F) Aradan Thompson<br />
* (#15F) Elizabeth Swager<br />
* (#16F) Stephen Getman<br />
* (#17F) Liliana Gaitan<br />
* (#18F) Robert Taylor<br />
* (#19F) ''in safe''<br />
* (#20F) Sean Ellefson<br />
* (#21F) Cynthia Prevatte<br />
* (#22F) Lynnae Griffiths<br />
* (#23F) ''in safe''<br />
* (#24F) ''in safe''<br />
* (#25F) Cliff Fortune<br />
* (#26F) Mark Kille<br />
* (#27F) Omar Vargas<br />
* (#28F) '''LOST!'''<br />
* (#29F) Patrick Sullivan<br />
* (#30F) ''in safe'' <br />
* (#31F) ''in safe'' <br />
* (#32F) ''in safe'' <br />
* (#33F) ''in safe'' <br />
* (#34F) ''in safe'' <br />
* (#35F) ''in safe'' <br />
* (#36F) ''in safe'' <br />
* (#37F) Eli Wisnievitz<br />
* (#38F) Ashley Sue Masoomian<br />
* (#39F) Jake Taasevigen<br />
* (#40F) John Ashcraft<br />
* (#41F) James Pella<br />
* (#42F) Michael Westwind<br />
* (#43F) Ryan Niebur<br />
* (#44F) Vagrant Cascadian<br />
* (#45F) Santiago del Carmona<br />
<br />
=== E keys ===<br />
''NOTE: "E" indicates a key for the '''E'''xternal '''after hours access door''' (near the meeting room).''<br />
<br />
* (#85E) ''in safe''<br />
* (#86E) ''in safe''<br />
* (#87E) ''in safe''<br />
* (#88E) ''in safe''<br />
* (#89E) Kelly Forest<br />
* (#90E) Michael Dexter (PLUG Advanced Topics)<br />
* (#91E) Evie Strohmeyer<br />
* (#92E) '''reserved for Ben Kerensa (groups)<br />
* (#93E) Eco Janitorial Solutions<br />
* (#94E) Eric Wilhelm (perlmongers)<br />
* (#95E) Bob Griggs<br />
* (#96E) Jason Owen<br />
* (#97E) John Jason Jordan (PLUG Clinic)<br />
* (#98E) Kenny McElroy<br />
* (#99E) '''DO NOT GIVE OUT THIS KEY!! This ADMIN key is kept in the safe for making copies.<br />
<br />
=== I keys ===<br />
''(NOTE: "I" indicates an '''I'''nternal key, used to protect money, and confidential papers.)''<br />
<br />
* (#01I) '''LOST!''' ''(Amelia will keep an eye out for it)''<br />
* (#02I) '''DO NOT GIVE OUT THIS KEY!! This ADMIN key is kept in the safe for making copies.'''<br />
* (#03I) ''in safe''<br />
* (#04I) John Ashcraft<br />
* (#05I) Liane Kocka<br />
* (#06I) Misty Falls<br />
* (#07I) Richard Seymour<br />
* (#08I) Michael Westwind<br />
* (#09I) Austin Crouch<br />
* (#10I) Darryl Kan<br />
* (#11I) Paul Munday<br />
* (#12I) Evie Strohmeyer<br />
* (#13I) Brian Keefer<br />
* (#14I) Ryan Niebur<br />
* (#15I) Vagrant Cascadian<br />
* (#16I) ''in safe''<br />
* (#17I) Patrick Sullivan<br />
* (#18I) Jason Owen<br />
* (#19I) Amelia Lamb<br />
* (#20I) Sean Ellefson<br />
* (#21I) Elizabeth Swager<br />
* (#22I) Cliff Fortune <br />
* (#23I) John McNamee<br />
* (#24I) Jake Taasevigen<br />
* (#25I) Santiago del Carmona<br />
* (#26I) ''in safe''<br />
* (#27I) Cynthia Prevatte<br />
* (#28I) Robert Taylor<br />
* (#29I) ''This key was recycled on 12/17/2011 because it didn't work on the Escape Hatch door.''<br />
* (#30I) Omar Vargas<br />
* (#31I) Darren Heiber<br />
* (#32I) ''in safe''<br />
* (#33I) Liliana Gaitan<br />
* (#34I) Mark Kille<br />
* (#35I) Stephen Getman<br />
* (#36I) Kevin Wright<br />
* (#37I) Lynnae Griffiths<br />
* (#38I) '''LOST!'''<br />
* (#39I) McGuire Bearing/Jim Conley<br />
* (#40I) Aradan Thompson<br />
* (#41I) James Pella<br />
* (#42I) Ashley Sue Masoomian<br />
* (#43I) Eli Wisnievitz<br />
* (#44I) ''in safe''<br />
* (#45I) ''in safe''<br />
* (#46I) ''in safe''<br />
* (#47I) ''in safe''<br />
* (#48I) ''in safe''<br />
* (#49I) ''in safe''<br />
* (#50I) ''in safe''<br />
<br />
=== T keys ===<br />
''This is the T key to the '''T'''ARDIS and other areas that contain "shiny" objects. Keys are issued at the discretion of the Production Committee and are provided to instructors in Build/Laptop/Macbuild and to point people in Advanced Testing.''<br />
<br />
* (T#1) Tom McCann<br />
* (T#2) Camille Huffman<br />
* (T#3) Robert Perry (Tex)<br />
* (T#4) Larry Lloyd<br />
* (T#5) Dennis Jones<br />
* (T#6) Blaine Deatherage-Newsom<br />
* (T#7) Eric Klotter<br />
* (T#8) Steve Van Dusen<br />
* (T#9) Nate Lee<br />
* (T#10) Kurt Krueger<br />
* (T#11) '''MISSING'''<br />
* (T#12) '''DO NOT GIVE OUT THIS KEY!! This ADMIN key is kept in the safe for making copies.'''<br />
* (T#13) Ron Escano<br />
* (T#14) Roy Marshall<br />
* (T#15) Max Schwarz<br />
* (T#16) John Franko<br />
* (T#17) Mary Meier<br />
* (T#18) Charlie MacCarthy<br />
* (T#19) Tara Nelson<br />
* (T#20) Jackson Tate<br />
* (T#21) John Gram<br />
* (T#22) Michael McCall<br />
* (T#23) ''in safe''<br />
* (T#24) "Lalo" Luis Eduardo Garza Crespo<br />
* (T#25) Daniel Lingle<br />
* (T#26) Howard Thompson<br />
* (T#27) ''in safe''<br />
<br />
=== Tech Support (S) ===<br />
These '''S'''upport keys are regular sized.<br />
<br />
* (S#1) In Tech Support<br />
* (S#2) '''DO NOT GIVE OUT THIS KEY!! This ADMIN key is kept in the safe for making copies.'''<br />
* (S#3) ''in safe''<br />
<br />
=== Personnel File Cabinet ===<br />
* (P#1) Stephen Getman<br />
* (P#2) Richard Seymour<br />
* (P#3) ''in safe''<br />
* (P#4) ''in safe<br />
* (P#5) Mark Kille<br />
* (P#6) Liane Kocka<br />
* (P#7) '''LOST!'''<br />
* (P#8) ''in safe''<br />
<br />
=== Staff Safe (S) ===<br />
''The '''S'''afe keys are smaller than the other S keys (above).''<br />
* (#1S) Darryl Kan<br />
* (#2S) Liane Kocka<br />
* (#3S) Amelia Lamb<br />
* (#4S) Darren Heiber<br />
* (#5S) Richard Seymour<br />
* (#6S) Mark Kille<br />
* (#7S) Sean Ellefson<br />
* (#8S) Michael Westwind<br />
* (#9S) Brian Keefer<br />
* (#10S) '''LOST!'''<br />
* (#11S) Cynthia Prevatte<br />
* (#12S) ''in safe''<br />
* (#13S) ''in safe''<br />
* (#14S) '''LOST!'''<br />
* (#15S) ''in safe''<br />
* (#16S) Stephen Getman<br />
<br />
=== Truck Keys ===<br />
The GMC box Truck has "Sets of Keys". There are 3 keys in each set. One for driving and doors, one for lock, and one for the gas tank.<br />
* Master copy unnumbered: '''dont give out!'''<br />
* (1) Liane Kocka<br />
* (2) Austin Crouch<br />
* (3) Darryl Kan<br />
* (4) ''in safe<br />
<br />
=== Forklift Keys ===<br />
This includes a forklift key, and a key to the padlock on the small hanging cabinet on the wall near the forklift charger. These keys are not numbered.<br />
* Master copy unnumbered: '''dont give out!'''<br />
* Cliff Fortune<br />
* Darryl Kan<br />
* ''in safe''<br />
* John Ashcraft<br />
* Liane Kocka<br />
<br />
=== C Keys ===<br />
''(the "C" key is for the secure Supply Cabinet in the store's back room)''<br />
* (#C1) ''MISSING''<br />
* (#C2) ''was twisted, then recycled''<br />
* (#C3) ''MISSING''<br />
* (#C4) ''MISSING''<br />
* (#C5) ''in safe<br />
* (#C6) ''in safe''<br />
* (#C7) ''in safe<br />
* (#C8) ''MISSING''<br />
* (#C9) Michael Westwind<br />
* (#C10) Liane Kocka<br />
* (#C11) ''in safe''<br />
* (#C12) ''MISSING''<br />
* (#C13) ''in safe<br />
* (#C14) Lynnae Griffiths<br />
* (#C15) Brian Keefer<br />
<br />
=== Monkey House Locker ===<br />
The monkey house locker is in the monkey house. It is a lateral file cabinet. Keys are mostly silver with no numbers or identifying marks.<br />
# Master Key - Gold colored key marked "STEELCASE GRAND RAPIDS MICHIGAN" on front, "FR433" on back. ''in safe<br />
# ''in safe''<br />
# Tom Wolcott<br />
# ''missing? (was Greg K's)''<br />
# Darren Heiber<br />
# Liliana Gaitan<br />
# Misty Fall<br />
# Nate Lee<br />
<br />
=== HR keys ===<br />
* HR-A<br />
** Mark Kille<br />
** ''in safe''<br />
** ''in safe''<br />
* HR-B<br />
** Richard Seymour<br />
** ''in safe''<br />
** ''in safe''<br />
<br />
=== Classic Gaming Library or CGL ===<br />
The Classic Gaming Library is upstairs adjacent to the Wine Cellar. This door operates on the "I" key as of 12/1/2011.<br />
<br />
== Re-keying the locks ==<br />
* If you're re-keying the locks, check this page to estimate how many new keys will be needed. Remember to take into account non Free Geekers with keys (the landlord, user group reps, etc.)<br />
* It is customary for the staff collective to reevaluate who still needs keys. This will affect the number of keys needed.<br />
* Also, if there are upcoming needs for keys such as hirings, interns, etc. There also may be folks leaving who will add to the available pool of keys.<br />
* Other key requests will undoubtedly be made, so having a few extra keys made is good. (They should be kept in the safe.)<br />
* The keys should be numbered so they can be kept track of. The locksmith can do this. Our current locksmith (Atlasta Lock and Key) does this for no charge.<br />
* Before the locks are re-keyed it is very important that all keyholders be notified so that folks who need access are not locked out. This is especially important for keyholders who are not on staff, as they are most likely to be forgotten.<br />
* Be sure to review the [[List of locks]].<br />
<br />
[[Category:Locks]]</div>Alambhttp://wiki.freegeek.org/index.php?title=Assembly_checklist&diff=64644Assembly checklist2012-10-13T18:49:29Z<p>Alamb: </p>
<hr />
<div>There is a version of this checklist in Spanish for use in Spanish Build; that version is located (combined with QC) [[Build Checklists en Español|here]].<br />
<br />
'''Work through every step as well as you can, and then ask a neighbor or your build instructor if you still have questions.''' Try and learn the reason for each of the steps: this knowledge will come in handy later when, inevitably, things aren't going as smoothly.<br />
<br />
'''Use your resources!''' There are lots available to you - your neighbor, the Build assistants and instructors and, of course, the internet. Searching the web for answers to the challenge you are facing is one of the best ways to learn. You can also access tips and troubleshooting ideas on our wiki (http://wiki.freegeek.org) under [[Build tips]] or in our Troubleshooting Guide (http://wiki.freegeek.org/index.php/Build_Troubleshooting_Guide). <br />
<br />
Supplies like cards, rails, hard drives, cleaning supplies, etc. can be found on the metal racks in the center of the build workshop. Here you will also find a box containing an assortment of common DDR memory.<br />
{| border="2" fontname="Nimbus Sans" fontsize="12"<br />
|-<br />
== BEFORE YOU POWER ON ==<br />
----<br />
'''Check what needs to be built on the white board''' <br />
* Head to the warehouse and scope out a system you would like to build. <br />
*'''Be sure to pay attention to the Green Light label.''' It will give you a lot of important information, like the type of video, if it did not POST, if the processor is Dual Core, etc. Make sure that the box you are about to Build is appropriate for its spec.<br />
* If everything looks good, Grab the system from the warehouse, take it back to your build station, and figure out how to pop it open. <br />
----<br />
'''Check capacitors'''<br />
* Visually inspect motherboard capacitors for bulges/leaks. If you find one, ask your instructor for a "Rejected" sticker. <br />
----<br />
'''Secure the case'''<br />
* Cover any open bays or slots. Replace any other missing case parts. (You can substitute a CD-ROM drive if no compatible bay cover is available.) Some cases require specific (proprietary) parts. If we don't have extras on hand, we unfortunately have to recycle them... <br />
* Ensure that all components are securely fastened.<br />
* Check for/remove any loose screws or unnecessary cables. If you're unsure of how to do this, ask an instructor.<br />
----<br />
'''Is there Microsoft Branding (Certificates of Authenticity)? Asset tags? (identifying the last owner)? Or branded hardware tags on the faceplate (identifying original components such as RAM, HDD, Optical Drive etc)?'''<br />
* If there are, remove them. '''DO NOT remove FG-PDX, "uncovered electronic device" Processor/graphics tags or Green Light stickers.'''<br />
----<br />
'''Clean and vacuum out box'''<br />
* There is a vacuum available on the Build supply shelf by the cleaning supplies. The most effective way to clean out a box is to use a paint brush to kick up the dust while vacuuming.<br />
----<br />
'''Test battery'''<br />
* Grab a voltmeter and set it to DCV=20. Place one wand on the battery itself and one wand on a metal part of the case. The battery passes if its voltage shows as 3.0 or greater. <br />
----<br />
'''Install RAM'''<br />
* For DDR2, try speed 533 (PC2-4200) first. If that doesn't work, try other numbers. Sometimes the BIOS will tell you the needed speed.<br />
* If your system's memory slots will not accept DDR2 memory, they will require another type. DDR3 is acceptable - ask your instructor for DDR3 RAM. DDR1 systems should be rejected and sent back to Prebuild as yellow-light systems.<br />
** NOTE: Usually RAM should be paired in dual channels for higher performance (i.e., 2 sticks of RAM used in specific slots, often color-coded). Make sure you try all combinations of slots if you are having trouble getting the system to recognize the RAM, and consult an Instructor if you're still having trouble.<br />
* Write down what type and speed of RAM you installed; this info will come in handy later.<br />
----<br />
'''Install video card if needed'''<br />
* You do not need to install a video card if there is functional onboard video. <br />
* Ask an instructor if you need a PCI-e card; AGP cards are available in the Build room.<br />
----<br />
'''Initial power on''' <br />
* See if expected memory value is displayed during POST or in BIOS. <br />
----<br />
'''Power down'''<br />
----<br />
'''Remove floppy drive if possible'''<br />
* Remove the floppy drive if you can find a matching face plate to cover it. If there are no covers available, you can leave the drive in, but make sure it is unplugged from the motherboard and power supply. Make sure the floppy drive (sometimes called Diskette) is disabled in BIOS and removed from the boot sequence if possible. <br />
----<br />
'''Check for onboard NIC ((Network Interface Card, or ethernet.)'''<br />
* If none can be found, install a network card.<br />
----<br />
'''Install hard drive'''<br />
* Get the appropriately sized (according to spec sheet) hard drive from the supply shelf, or from an instructor. Also check to see if you need an IDE or SATA hard drive and make sure you have the necessary cables and power connections.<br />
* Install the hard drive and attach it to the power supply and motherboard. (If the drive has IDE connections, make sure the jumper is set to the Master position. Ask an instructor for more info.)<br />
* You will need to ask an instructor for any hard drives higher than 120 GB.<br />
----<br />
'''Install sound card if needed'''<br />
* If there's onboard sound, there's no need to install a sound card.<br />
----<br />
'''Install CD/CDRW/DVD/DVD-RW Drive(s)'''<br />
* If there are already optical drives installed in your system, take a look at their face-plates to determine their capabilities. If the drives are within spec for the box you're building and have IDE connections, confirm they're properly jumpered as Master/Slave, or just Master if there's only one drive. <br />
* If the the drives are outside of spec, pull them out and sort them into the appropriate boxes on the Build shelves. Replace with appropriate drives as needed.<br />
---- <br />
'''Cover open slots and bays'''<br />
* Make sure you have coverings for all spaces that will not be filled with a card or drive. Look at similar cases for examples of what case pieces may look like. Be sure that these are screwed in tight and test them by pushing on each with your finger. If a slot cover falls out while a computer is on it can '''short out the motherboard.'''<br />
----<br />
<br />
== BOOT AND [[Entering BIOS|ENTER BIOS]] ==<br />
----<br />
'''Attach monitor, keyboard, mouse, network, sound and power cords'''<br />
----<br />
'''Enter BIOS setup'''<br />
* Turn on the computer. The keystroke to enter BIOS should be displayed on the flash screen, before bootup, as well as the Boot Menu key, if applicable. If no flash screen appears, you have to guess the BIOS keystroke. Delete, Escape, Enter, F1, F2, F9, F10, and F12 are typical. <br />
* Get into BIOS, and '''write down both the BIOS and Boot Menu keystrokes;''' this info will come in handy later.<br />
----<br />
'''Check date and time''' <br />
* Check date and time in BIOS and change to the correct time if needed.<br />
----<br />
'''Restore BIOS defaults'''<br />
* You might need to search around to find the BIOS values that need checking. While you search, enjoy the pleasure of learning about BIOS configuration! <br />
----<br />
'''Detect hard drive'''<br />
* Search BIOS to see if it is recognizing the hard drive. <br />
----<br />
'''Set boot order'''<br />
* It should be: '''1st-CD-ROM'''; '''2nd-Hard drive. If possible, disable all other boot devices such as floppy drive or network boot from the boot sequence.<br />
----<br />
'''Where possible, edit any/all of the following settings:'''<br />
* Enable USB ports<br />
* Enable Hyper-threading<br />
* Disable Quick Boot<br />
* Disable Logo Display (Sometimes called Silent or Quiet Boot)<br />
* Disable Plug & Play OS<br />
* SATA Operation: set to RAID Autodetect/AHCI<br />
----<br />
'''Save and exit BIOS'''<br />
* The system should reboot to the Ubuntu operating system. <br />
----<br />
<br />
== HARDWARE AND SOFTWARE TESTING ==<br />
----<br />
'''Login to the system'''<br />
* username will be '''Default User''' <br />
* password = '''freegeek''' <br />
----<br />
'''Check for 64-bit capability'''<br />
* From a terminal, type "'''sudo lshw -c processor | grep width'''" and press enter. Type the password: "freegeek" and press enter again. (Don't worry that the password text doesn't show on the screen; it is hidden for security reasons.)<br />
* The reading you get should be "width: 64." If your system reads "width: 32" instead, check with your instructor; this system will have to be recycled.<br />
----<br />
'''Run "basiccheck"''' <br />
* From a terminal, type "'''basiccheck'''" Read through each of the tests and verify that they pass. When the last test is finished, close the terminal.<br />
* Refer to the basiccheck checklists hanging on the supply shelves to help determine whether each test passes or not. <br />
----<br />
'''Learn to install a program through command line'''<br />
* Open up a terminal and type "sudo apt-get install gimp" and press "Enter." This will install the photo editing program called Gimp. You may have to type "freegeek" and press enter again for the installation to proceed.<br />
----<br />
'''Learn to install a program through the Graphical User Interface (GUI - the mouse)'''<br />
* The first place to look for software to add is in the Ubuntu Software Center (Applications>Ubuntu Software Center). This gives you access to the Ubuntu supported applications plus many others. Search for "k3b" and install it. K3b is a CD/DVD authoring program.<br />
----<br />
'''Test USB ports'''<br />
* Plug in a USB mouse, see that the cursor moves and can interact with things. Repeat with all USB ports, including front ports, if any.<br />
----<br />
'''Play an audio CD'''<br />
* Do you hear what you expect? Is it loud enough to be heard easily? Repeat for each CD-ROM drive. Repeat for additional sound ports. <br />
* Note if any standard sound ports do not work. These will need to be covered with electrical tape. If all onboard sound does not work, install a sound card.<br />
----<br />
'''Read data CD'''<br />
* If your file browser sees files on the drive, the CD-ROM can read files. Repeat for each CD-ROM drive. <br />
----<br />
'''If you have a DVD Drive, Read DVD'''<br />
* If your file browser sees the file, the DVD-ROM can read files. If you are prompted to search for suitable plugins or codecs, '''please do not do this!''' The test still passes. Repeat for each DVD-ROM drive.<br />
----<br />
'''If you have an Optical Drive with CD-RW function, Test CD Writing'''<br />
* Insert a CD-RW disc into the drive and open Brasero Disc Burning (under '''Applications >> Sound & Video'''.) Select '''Data Project''', click on the green +, then select '''examples.desktop''' and click '''Add'''. Click '''Burn''' in the lower right-hand corner. A new window will pop-up with a few options. If available, select '''Use burnproof''' and '''Burn the image directly without saving it to disc''' and click '''Burn'''. When the disc is done, verify that it contains the examples file by re-inserting the disc and seeing what pops up on the desktop. <br />
* Blank the disc using Brasero by selecting '''Tools >> Blank'''. If available, '''uncheck the "Fast Blank" option.''' If blanking does not work, the drive may still be completely functional! Ask your instructor about software bug workarounds. <br />
----<br />
'''If you have an Optical Drive with DVD-RW function, Test DVD Writing'''<br />
* Insert a DVD-RW disc into the drive and in the Brasero file browser follow the same steps as above to burn a data project. When the disc is done, verify that it contains the examples file by re-inserting the disc and seeing what pops up on the desktop.<br />
*Blank the disc using Brasero by selecting '''Tools >> Blank'''. If available, '''uncheck "Fast Blank."''' Again, blanking errors may not indicate a bad drive. Ask your instructor for more information. <br />
----<br />
'''Test for booting from live CD'''<br />
* Place Live CD in drive and restart the computer. The system should boot from the live CD. <br />
* Select language: English. Scroll down on the following screen to '''Boot to first hard drive''' and press enter. This should take you to the normal Ubuntu log-in screen. <br />
----<br />
'''Remove all CDs and DVDs from the drive(s)''' <br />
----<br />
'''Reboot the system'''<br />
* Open a terminal and type '''sudo reboot.''' Wait while it reboots, and ensure that the system powers on and offers a login screen without user intervention (e.g. requiring you to "press F1 to boot.") <br />
* If it doesn't boot smoothly, double-check your boot priority options in BIOS and try again.<br />
----<br />
'''Run "printme" from terminal'''<br />
* From a terminal, type "'''printme,'''" this will generate a questionnaire in Command Line. <br />
* Refer to your written notes for the RAM type and speed, the BIOS key and Boot Menu key, if applicable. <br />
* '''When it asks what is notable about this system, refer to the white board for what should be included, and ask your instructor for any needed clarification.''' Press enter to create a web document.<br />
---- <br />
'''Check in with Build Instructor''' <br />
* The Build Instructor will check the printme and edit it to sign it off. <br />
* Your instructor may ask you to replace certain components, which will require re-running the "printme" form. Some changes may also need to be made in the web browser. If your instructor gives the "thumbs-up," proceed to the next step. <br />
----<br />
'''Save Printme to the desktop'''<br />
* After your Build Instructor has inspected the system, click "Print" from the printme on the web document. "Choose "Print to File" and select "Desktop" as the folder in which to save it. Name the file "Build Printme" and click print. <br />
----<br />
'''Shut down system and place on QC shelf'''<br />
* Open a terminal and type "sudo halt" then press enter. When the system has shut down, unplug all cables, double-check that the case is secured properly, and place it on the QC shelf in the Build room.<br />
----<br />
'''Clean up work area if it is your last Assembly of the day'''<br />
* Please put all tools away, throw out any garbage or sticker remains, put screws in the appropriate bins, wrap cords around your keyboard and mouse, turn off your speakers and monitor, and generally straighten up.<br />
<br />
== Thank You For Volunteering! ==<br />
* If you are interested in further learning opportunities after finishing the Build program, ask your instructor about '''Post-Build options!'''<br />
* We want to know what you think! Go to '''http://freegeek.limequery.com/48992/lang-en''' to fill out the '''Build Program Exit Survey.'''<br />
<br />
<br />
<noinclude>[[Category:Build]]</noinclude></div>Alambhttp://wiki.freegeek.org/index.php?title=QC_checklist&diff=64643QC checklist2012-10-13T18:47:54Z<p>Alamb: </p>
<hr />
<div>There is a version of this checklist in Spanish for use in Spanish Build; that version is located (combined with Assembly) [[Build Checklists en Español|here]].<br />
<br />
'''Welcome to the Build Workshop!''' Quality checking a few systems that others have built will be your first step, then you'll be ready to move on to assembling and checking software on systems. <br />
<br />
'''Work through every step as well as you can, and then ask a neighbor or your Build instructor if you still have questions.''' Try and learn the reason for each of the steps: this knowledge will come in handy later when, inevitably, things aren't going as smoothly.<br />
<br />
'''Use your resources!''' There are lots available to you - your neighbor, the Build assistants and instructors and, of course, the internet. Searching the web for answers to the challenge you are facing is one of the best ways to learn. You can also access tips and troubleshooting ideas on our wiki (http://wiki.freegeek.org) under [[Build tips]] or in our Troubleshooting Guide (http://wiki.freegeek.org/index.php/Build_Troubleshooting_Guide). <br />
{| border="2" fontname="Nimbus Sans" fontsize="12"<br />
|-<br />
== BEFORE YOU POWER ON ==<br />
----<br />
'''Check what needs to be quality checked'''<br />
* Grab a system from the QC shelves in the build room, and carry it to an open Build station.<br />
----<br />
'''Do you hear a rattling noise, caused by a screw or other loose component, upon moving the system?''' <br />
* If so, find the culprit and secure/remove it. <br />
----<br />
'''Is the case properly put together and secure?''' <br />
* If not, fix it!<br />
----<br />
'''Are all slots and bays covered?''' <br />
* If not, cover 'em! Check to make sure they're screwed in tightly by pushing on each one with your finger - if a slot cover falls out it can '''short out the motherboard.'''<br />
----<br />
'''Do you see more than one video, sound, or network ports?''' <br />
* Later, when you're testing audio, headphone jacks and standard sound ports should be tested.<br />
* Orange/Black/Gray sound ports are surround sound and do not need to be tested. <br />
*Any damaged ports will need to be covered with electrical tape or port covers. If you see two identical uncovered ports, one integrated and one on a card, ask your instructor how to proceed.<br />
----<br />
'''Is there Microsoft Branding? (Certificates of Authenticity) Asset tags (identifying the last owner)? Or branded hardware tags on the faceplate (identifying original components such as RAM, HDD, Optical Drive etc)?'''<br />
* If there is, take them off. '''DO NOT remove FG-PDX, "uncovered electronic device" Processor/graphics tags or Green Light stickers.'''<br />
----<br />
'''Is the system exterior clean?''' <br />
* If not, use cleaner and rag to clean. The vacuum cleaner will help remove dust clogged in case fans. Hand sanitizer, Goo Gone and/or isopropyl (rubbing) alcohol can help loosen any stickers; ask your instructor where to find scraping tools to remove them.<br />
----<br />
'''Open up the system and check inside for:'''<br />
# Blown capacitors (If found, the system must be rejected!)<br />
# What type of DDR RAM your system has installed - write this down<br />
# The RAM speed (will be the second number on the sticker) - write this down<br />
# Any dust accumulation - please vacuum or brush it out!<br />
<br />
== BOOT AND [[Entering BIOS|ENTER BIOS]] ==<br />
----<br />
'''Get into BIOS (Setup)''' <br />
* Turn on the computer. If you see a flash screen before boot-up, it will give the keystroke to enter BIOS, and the keystroke for a Boot Menu, if applicable. Delete, Escape, F1, F2, F9, F10, F12 and Enter are typical. <br />
*Get into BIOS, and write down both the BIOS and Boot Menu keystrokes; this info will come in handy later. <br />
*If you see "'''Ubuntu'''" on your screen, you have gone too far; reboot from the power button icon on the bottom-right corner of the screen, and try again. All BIOS are different. Feel free to explore how the BIOS you're using is set up. <br />
----<br />
'''Check boot order''' <br />
* It should be: '''1st- CD-ROM'''; '''2nd-Hard Drive'''. If possible, disable other boot device options, such as floppy (sometimes called Diskette), network, or USB. Depending on the BIOS model, you may need to enable active drive ports and disable inactive ones, in addition to arranging them in the boot sequence.<br />
----<br />
'''If possible, edit the following setting:'''<br />
* Enable Quick Boot<br />
----<br />
'''Save and exit BIOS'''<br />
* The system should boot to the Ubuntu operating system.<br />
----<br />
<br />
== HARDWARE AND SOFTWARE TESTING ==<br />
----<br />
'''Login to the system'''<br />
* username will be '''Default User''' <br> password = '''freegeek''' <br />
----<br />
'''What Specification Category does the system fall under?'''<br />
* Compare the CPU speed listed on the system's Green Light sticker with the '''FREE GEEK Specification Sheet,''' or "Spec Sheet," on the wall to determine the category of specifications, or "specs," to which the system should be built. (Keep in mind that FG-PDX's are determined by their sticker, not their processor.) If you aren't sure what type of box you are working with, please check with your instructor to see how to proceed.<br />
----<br />
'''Is the system standard?''' <br />
* Check the '''Spec Sheet''' on the wall to see what else should be installed for your spec category, then compare your system's spec category to the '''Build Printme''' document saved to the Desktop. Does the box have any parts that are extra, or missing, or built to incorrect specifications? Take out and replace parts as necessary to ensure that all specs are correct, paying special attention to properly seating/securing parts to ensure that they won't come loose. Ask an instructor if you are unsure how to do this.<br />
----<br />
'''Update the software'''<br />
* Click on '''System''' >> '''Administration''' >> '''Update Manager'''. When the Update Manager pops up, click "Check" to find updates, then if any updates appear, click "Install All." It may take some time to download and install packages, so feel free to continue on with other steps while this runs in the background.<br />
----<br />
'''Drag the terminal icon to the top panel'''<br />
* Go to '''Applications''' >> '''Accessories''' >> '''Terminal'''. Use the mouse to click and hold the button down over the Terminal icon, drag, then release the mouse button when the icon hovers over the black panel along the top of the screen.<br />
----<br />
'''Stress test the system for a few minutes''' <br />
* Open a terminal and run "'''stress-test'''". Wait a few minutes while it runs, and look for error messages. If you want to know more about what it's doing, open up another terminal and run "man stress". This may take some time; feel free to continue on to the next step while you wait.<br />
----<br />
'''Run "basiccheck"''' <br />
* Click on the terminal icon to open it. Type "'''basiccheck'''", then press enter to begin the program. There are basiccheck checklists hanging on the supply shelves which will help with verifying whether each test passes or not. Feel free to ask your peers and the instructor what parts of basiccheck mean so that you understand what each test is checking. When you're finished, close the terminal.<br />
----<br />
'''Test USB'''<br />
* Plug in a USB mouse, see that the cursor moves and can interact with things. <br />
* Repeat with all USB ports, including ports on the front of the system, if any.<br />
* If any ports don't work, they may need to be enabled in BIOS; ask your instructor how to proceed.<br />
----<br />
'''Check date and time''' <br />
* Displayed in the right corner of your top panel. If incorrect:<br />
# Make sure network cable is plugged in.<br />
# Right-click on the time and then click the "Preferences" button.<br />
# Click on the "Time Settings" button.<br />
# Manually adjust date and time. Press "Set System Time" to save, then close the Clock Preferences window.<br />
----<br />
'''Play an audio CD''' <br />
* Do you hear what you expect? Is it loud enough to be heard easily? Repeat for each optical drive. Also repeat for any additional sound ports. If any sound ports (typically colored green, sometimes blue) don't play audio, cover them up with port covers or electrical tape. '''If you have functional onboard sound, and a sound card, the card will need to be removed and replaced with a slot cover.'''<br />
* If you have surround sound ports (usually orange and gray) ignore them; we do not have the means to test this function. <br />
----<br />
'''Read data CD''' <br />
* If your file browser (listed under '''Places''' in the top panel) sees files on the drive, it can read data files. Repeat for each optical drive. <br />
----<br />
'''If you have a DVD Drive, Read DVD''' <br />
* If your file browser sees the file, the DVD-ROM can read files. If you are prompted to search for a suitable plugin or codec, '''please do not do this!''' The test still passes. Repeat for each DVD-ROM drive.<br />
----<br />
'''If you have an Optical Drive with CD-RW function, Test CD Writing'''<br />
* Insert a CD-RW disc into the drive and open Brasero Disc Burning (under '''Applications''' >> '''Sound & Video'''.) Select '''Data Project''', click on the green '''+''', then select '''examples.desktop''' and click '''Add'''. Click '''Burn''' in the lower right-hand corner. A new window will pop-up with a few options. If available, select '''Use burnproof''' and '''Burn the image directly without saving it to disc''' and click '''Burn'''. When the disc is done, verify that it contains the file by re-inserting the disc and seeing what pops up on the desktop.<br />
* Blank the disc using Brasero by selecting '''Tools''' >> '''Blank'''. If available, '''uncheck the "Fast Blank" option.''' If blanking does not work, the drive may still be completely functional! Ask your instructor about software bug workarounds. <br />
----<br />
'''If you have an Optical Drive with DVD-RW function, Test DVD Writing'''<br />
* Insert a DVD-RW disc into the drive and in the Brasero file browser follow the same steps as above to burn a data project. When the disc is done, verify that it contains the file by re-inserting the disc and seeing what pops up on the desktop.<br />
* Blank the disc using Brasero by selecting '''Tools''' >> '''Blank'''. If available, uncheck "Fast Blank." Again, blanking errors may not indicate a bad drive. Ask your instructor for more information.<br />
----<br />
'''Test for booting from live CD'''<br />
* Place Live CD in drive and restart the computer. The system should boot from the live CD. <br />
* Select language: English. Scroll down on the following screen to '''Boot to first hard drive''' and press enter. This should take you to the normal Ubuntu log-in screen. <br />
---- <br />
'''Remove all CDs and DVDs from the drive(s)'''<br />
----<br />
'''Reboot the system'''<br />
* Open a terminal and type '''sudo reboot.''' Wait while it reboots, and ensure that the system powers on and offers a login screen without user intervention (e.g. requiring you to "press F1 to boot.") <br />
* If it doesn't boot smoothly, double-check your boot priority options in BIOS and try again.<br />
----<br />
'''Run "printme" from terminal'''<br />
* From a terminal, type "'''printme,'''" this will generate a questionnaire in Command Line. <br />
* Refer to your written notes for the RAM type and speed, the BIOS key and Boot Menu key, if applicable. <br />
* '''When it asks what is notable about this system, refer to the white board for what should be included, and ask your instructor for any needed clarification.''' Press enter to create a web document.<br />
----<br />
'''Copy system ID (IMPORTANT!)'''<br />
* Copy the system ID from the printme onto a blank sticker and put it on back of computer, ideally in a location that isn't covering any fans, other ventilation, or removable case parts such as slot covers.<br />
----<br />
'''Add Free Geek Sticker'''<br />
* Affix on the front of the system, in a sensible location! (Usually adjacent to or above/below the Processor tag)<br />
----<br />
'''Check in with Build Instructor''' <br />
* The Build Instructor will check the printme and edit it to sign it off. <br />
* Your instructor may ask you to replace certain components, which will require re-running the "printme" form. Some changes may also need to be made in the web browser. If your instructor gives the "thumbs-up," proceed to the next step. <br />
----<br />
'''Save Printme to the Desktop'''<br />
* After your Build Instructor has inspected the system, click "Print" in the browser that opens. Choose "Print to file." Save the file to the Desktop and name it "QC Printme", then click "Print" to save. Click on the QC Printme icon on the Desktop to open it up. <br />
----<br />
'''Enable network printers:'''<br />
* Go to '''System>>Administration>>Printing'''<br />
* Select '''Server>>Settings''' and check the box marked <i>Show Printers Shared by Other Systems</i> and click OK.<br />
* Wait for a few moments and click the refresh icon. A selection of printers should appear.<br />
----<br />
'''Print a hard copy of Printme'''<br />
* Close the "Printing - localhost" window that opens and select the "build" printer from the Print menu once it appears. Click Print and retrieve the sheet from the printer in the back (SW) corner of the room. <br />
* Have your Build Instructor sign off on the printed sheet. Then fold it in half (lengthwise) and tape it to the top of the system (the side of the page with the instructor's initials facing up.)<br />
----<br />
'''Shut down and shelve the system''' <br />
* Open a terminal and type "sudo halt" then press enter. When the system has shut down, unplug all cables, double-check that the case is secured properly, and ask a build instructor where to put the system once shutdown is complete. <br />
----<br />
'''Clean up work area if it is your last QC of the day''' <br />
* Please put all tools away, throw out any garbage or sticker remains, put screws in the appropriate bins, wrap cords around your keyboard and mouse, turn off your speakers and monitor, and generally straighten up. <br />
|}<br />
<br />
<br />
<br />
<noinclude>[[Category:Build]]</noinclude></div>Alambhttp://wiki.freegeek.org/index.php?title=QC_Checklist_en_Espanol&diff=64642QC Checklist en Espanol2012-10-13T18:42:57Z<p>Alamb: </p>
<hr />
<div>This page is for storing the combined QC and Assembly procedures in Spanish. See the English versions [[QC checklist|here]] (QC), and [[Assembly checklist|here]] (Assembly).<br />
<br />
='''QC CHECKLIST EN ESPAÑOL'''=<br />
<br />
'''Bienvenidos al Taller de Construcción''' El primer paso es el control de calidad (quality control). <br />
Después de control de calidad, usted estará listo para armar y probar el software de otras computadoras. <br />
<br />
'''Trabaje a través de cada paso lo mejor que pueda, y luego pídale a su vecino o a su instructor de construcción ayuda si usted tiene preguntas.''' Trate de aprender la razón de cada uno de los pasos: este conocimiento será útil más tarde, cuando, inevitablemente, las cosas no vayan tan bien.<br />
<br />
'''Utilice sus recursos!''' Hay muchos recursos para usted - su vecino, los asistentes, los instructores de construcción y, por supuesto, el Internet. Se puede acceder a consejos y soluciones de problemas e ideas en nuestro wiki:(http://wiki.freegeek.org) en la página “Build tips”. o en nuestra guia de problemas (http://wiki.freegeek.org/index.php/Build_Troubleshooting_Guide)<br />
<br />
{| border="2" fontname="Nimbus Sans" fontsize="12"<br />
|-<br />
==ANTES DE ENCENDER== <br />
----<br />
'''Averigue que sistemas son para el control de calidad''' <br />
* Luego tome un sistema de los estantes de QC en la sala de Build y llévelo a una estación disponible. <br />
----<br />
'''¿Oye un sonido causado por un tornillo o algún otro componente cuando se mueve el sistema?'''<br />
* Si es así, encuente al culpable y asegúrelo/elimínelo. <br />
----<br />
'''¿Está el armazón (case) bien colocado y seguro?''' <br />
* ¡Si no, arréglelo!<br />
----<br />
'''¿Están todas las ranuras y puertos cubiertos?''' <br />
* ¡Si no, cúbralas! Compruebe que todo esté asegurado, apriete cada uno con su dedo. Si una tapa de la ranura se cae, '''puede causar un corto circuito en la tarjeta madre (motherboard)'''. <br />
----<br />
'''¿Ve usted mas de un puerto de vídeo, sonido o de red?''' <br />
* Los enchufes para audífonos y los puertos regulares de sonido deben ser probados.<br />
* Los puertos de sonido amarillo/negro/gris son de sonido envolvente y no necesitan ser probados.<br />
* Todos los puertos dañados necesitan ser cubiertos con cinta aislante o con cubre puertos. Si usted observa dos puertos idénticos descubiertos, uno integrado y otro en una tarjeta, pregunte a un instructor sobre como proceder.<br />
----<br />
'''¿Hay etiquetas de Microsoft? (Certificados de Autenticidad) ¿Etiquetas de activo (identificación del último propietario)? O las etiquetas de marca del hardware en la placa frontal (que identifican los componentes originales tales como RAM, HDD, Optical drives, etc)'''<br />
* Si los hay, retírelos.'''NO QUITE las etiquetas "FG-PDX", “Uncovered Electronic Device” o “Green Light”.''' <br />
----<br />
'''¿Está el exterior del sistema limpio?''' <br />
* Si no, use un limpiador o un trapo de limpiar. La aspiradora ayudará a eliminar el polvo de las cajas de los ventiladores, desinfectante para las manos Goo Gone y/o alcohol isopropilico pueden ayudar para quitar las etiquetas. Pregunte a un instructor donde encontrar estos materiales.<br />
----<br />
'''Abra el sistema y revise:''' <br />
# Si hay capacitores abombados (si los encuentra, el sistema debe ser rechazado).<br />
# Si la memoria RAM es DDR o DDR2 - escriba los datos en un papel. <br />
# La velocidad de la memoria RAM (este va a ser el segundo número en la etiqueta) - escriba los datos en un papel. <br />
# Cualquier acumulación de polvo - utilize la aspiradora o un cepillo para limpiar <br />
<br />
== ARRANQUE Y ENTRE A BIOS ==<br />
----<br />
'''Entre a BIOS (Setup).''' <br />
*Encienda la computadora. Si ve un mensaje en la pantalla antes de arrancar le avisará que tecla usar para entrar a BIOS y la tecla para arrancar. Estas pueden ser "Del","Esc", F1, F2, F9, F10 y F12.<br />
*Entre a BIOS, y escriba los nombres de las teclas para Bios y para arrancar. Esta información le servirá más tarde.<br />
*Si aparece '''"Ubuntu"''' en la pantalla, significa que ha ido demasiado lejos, reinicie desde el botón de encendido en la esquina inferior derecha de la pantalla. Todos los BIOS son diferentes. Siéntase libre de explorar la configuración del BIOS que esté utilizando. <br />
----<br />
'''Compruebe el orden de inicio.''' <br />
* Debe ser: '''Primero CD-ROM; segundo disco duro (hard drive)'''. Si es posible deshabilite las demás opciones de arranque del dispositivo, como una unidad de disquete, network o USB. Dependiendo del modelo del BIOS, puede ser que necesite activar los puertos inactivos y deshabilitar los puertos activos en la unidad, ademas de ordenarlos en la secuenciua de arranque. <br />
----<br />
'''Guarde y salga de BIOS''' <br />
* El sistema tiene que arrancar con el sistema operativo Ubuntu.<br />
----<br />
<br />
== HARDWARE Y PRUEBAS DE SOFTWARE ==<br />
----<br />
'''Entre al sistema'''<br />
* usuario es '''Default User''' <br> clave = '''freegeek'''<br />
----<br />
'''¿Bajo que categoría cabe este sistema?'''<br />
* Compare la velocidad del CPU que se encuentra en la etiqueta de Green Light con la '''hoja de especificaciones de FREE GEEK''' o "Spec Sheet"en la pared para determinar la categoría o especificaciones en las que este sistema tiene que ser construido. (Tenga presente que los sistemas FG-PDX se determinan por la etiqueta y no por la velocidad del procesador). Si no está seguro del tipo de sistema en que está trabajando, por favor consulte con un instructor para saber como proceder.<br />
----<br />
'''¿Es el sistema estándar?'''<br />
* Revise la '''hoja de especificaciones''' en la pared para ver qué tiene que ser instalado en el tipo de computadora con la que usted esté trabajando. A continuación, compare la categoría de especificaciones de su sistema con el documento '''“Build Printme”''' del desktop. ¿Hay partes extras o ausentes en la caja, o esta construida con especificaciones incorrectas? Saque y reemplace las partes necesarias para asegurarse que las especificaciones son correctas, ponga especial atención en que las partes estén bien aseguradas/colocadas y que no estén sueltas. Pregunte a un instructor si no esta seguro de como hacerlo.<br />
----<br />
'''Actualice el software''' <br />
* Pulse '''System >> Administration >> Update Manager.''' Cuando la opción de actualizar aparece, pulse “Check” para encontrar actualizaciones, y si alguna actualización aparece pulse “Install All”. A veces el sistema demora para descargar e instalar los paquetes, así que siéntase libre para continuar con los otros pasos mientras esto sucede en la computadora.<br />
----<br />
'''Arrastre el icono del terminal y póngalo en el panel superior''' <br />
* Vaya a '''Applications >> Accessories >> Terminal.''' Use el ratón y mantenga pulsado el botón sobre el icono "Terminal", arrastre y suelte el botón del ratón cuando el puntero del icono flote sobre el panel negro en la parte superior de la pantalla. <br />
----<br />
'''Ejecute "Stress test" al sistema por unos minutos''' <br />
* Abra un terminal y ejecute '''stress test'''. Espere unos pocos minutos mientras funciona y busque por mensajes de error. Si quiere saber más sobre lo que está pasando, abra otro terminal y ejecute “man stress” Esto puede demorarse, siéntase libre de continuar con el siguiente paso mientras espera. <br />
----<br />
'''Ejecute "basiccheck"''' <br />
* Pulse en el icono "terminal" para abrirlo. pulse '''"basiccheck"''' y luego “Enter” para ejecutar el programa. Hay listas colgadas en los estantes para comprobar basiccheck, que nos ayudarán a verificar si cada prueba se supera o no. Usted puede preguntar a sus vecinos/as y al instructor qué significa las diferentes pruebas de basiccheck para que entienda claramente lo que trata de comprobar. Cuando termine, cierre el terminal. <br />
----<br />
'''Pruebe los puertos USB''' <br />
* Conecte un ratón USB, fíjese que el cursor se mueva y pueda interactuar con los iconos. <br />
* Repita el procedimiento con todos los puertos USB, incluidos los puertos en la parte frontal del sistema, si los hay.<br />
* Si alguno de los puertos no funciona, puede ser que necesiten ser habilitados en BIOS. Pregunte a un instructor sobre como hacerlo.<br />
----<br />
'''Revise la fecha y hora.'''<br />
*Revise la fecha y la hora en la esquina superior derecha. Si es incorrecto:<br />
<br />
1. Asegúrese que el cable de la red está conectado. <br />
<br />
2. Pulse en la hora y luego en “preferences” <br />
<br />
3. Pulse el botón "Time Settings”<br />
<br />
4. Manualmente ajuste la fecha y la hora, pulse “Set System Time” para guardar y luego cierre la ventana de Clock Preferences. <br />
----<br />
'''Ponga un audio CD''' <br />
* ¿Se oye lo que esperaba? ¿Es el sonido suficientemente alto para oír con facilidad? Repita el proceso para cada unidad de disco óptico. También repita en cada puerto de sonido adicional. Si algún puerto de sonido (generalmente marcados con verde, algunas veces azul) no toca audio, cúbralos con cubre puertos o con cinta eléctrica. '''Si el sonido esta funcionando desde en el sistema, y hay una tarjeta de sonido, la tarjeta tiene que ser retirada y cubierto el espacio'''<br />
* si exixten puertos para surround sound (sonido envolvente) (generalmente anaranjado o gris) ignórelos No hay forma de probar esta función. <br />
----<br />
'''Lector de disco con datos''' <br />
* Si su navegador de archivos (que esta bajo '''Places''' en el panel superior) ve los archivos en el disco, puede leer archivos de datos. Repita esto para cada unidad de disco óptico.<br />
----<br />
'''Si tiene una unidad de DVD, lea el DVD'''<br />
* Si el navegador de archivos ve el archivo, el DVD-ROM puede leer documentos, Si aparece un mensaje para que busque “los plugins o codecs” adecuados, '''¡por favor no lo haga!''' la unidad funciona. Repita para cada unidad DVD-ROM. <br />
----<br />
'''Si tiene una unidad óptica con función CD-RW, pruebe el CD Writing''' <br />
* Ponga un disco CD-RW en la unidad de disco y abra el programa “Brasero Disc Burning” (Vaya a Applications >>Sound & Video.) Seleccione '''Data Project''' pulse en la tecla verde '''+''', y seleccione '''examples.desktop''' y pulse '''Add'''. Pulse '''Burn''' en la parte inferior derecha de la pantalla. Aparecerá una nueva pantalla con pocas opciones. Si esta disponible, seleccione '''Use burnproof''' y '''Burn the image directly without saving it to disk''' y pulse '''Burn'''. Cuando acabe el disco, verifique que contiene los documentos reinsertando el disco y revisando lo que aparece en el desktop.<br />
* Borre el disco utilizando el programa “Brasero”, seleccione ''''Tools>>Blank'''. Si no se borra, la unidad todavía puede estar funcionando bien. Pregunte a un instructor acerca de soluciones de errores de software. <br />
----<br />
'''Si tiene una unidad óptica con DVD-RW, pruebe el DVD Writing''' <br />
* Ponga un disco DVD-RW en la unidad de DVD, en el navegador de “Brasero” siga los mismos pasos arriba descritos para quemar un proyecto de datos. Cuando acabe el disco, verifique que contiene los documentos reinsertando el disco y revisando lo que se ve en el desktop.<br />
* Borre el disco utilizando el programa “Brasero”, seleccione '''Tools > Blank'''. Si está disponible, desmarque "Fast Blank”. De nuevo los errores de borrado no pueden significar una mala unidad. Pregunte a un instructor para mayor información. <br />
----<br />
'''Prueba de arranque desde un “Live CD”''' <br />
* Coloque un “Live CD” en la unidad y reinicie la computadora. El sistema tiene que arrancar desde el “Live CD”.<br />
* Seleccione el idioma: Inglés. Desplácese hacia abajo en la siguiente pantalla para '''Boot to firts hard drive''' y pulse “enter”, esto le llevará a la pantalla de registro de Ubuntu.<br />
----<br />
'''Retire todos los discos CD y DVD de la/s unidad/es''' <br />
----<br />
'''Reinicie el sistema'''<br />
* Abra un terminal y pulse '''sudo reboot'''. Espere mientras se reinicia y asegúrese que el sistema se encienda y muestre una pantalla de acceso sin intervención del usuario (por ejemplo, requiere que pulse F1 para arrancar). <br />
* Si no arranca fácilmente, compruebe sus opciones de prioridad en BIOS y trate de nuevo.<br />
----<br />
'''Ejecute "printme" desde el terminal'''<br />
* Desde un terminal, escriba '''printme''', esto generará un cuestionario en línea de comandos.<br />
* Consulte con sus notas escritas para el tipo de memoria RAM y velocidad, la clave de BIOS y la clave del Menu, si se aplica.<br />
* '''Cuando se le pregunta qué es notable acerca de este sistema, consulte en la pizarra para saber lo que se tiene que incluir y pregunte a su instructor en caso de dudas'''. Pulse “enter” para crear un documento web.<br />
----<br />
'''Copie la identificación del sistema. (¡MUY IMPORTANTE!)''' <br />
* Copie la identificación del sistema desde el “printme” en una etiqueta en blanco y colóquela en la parte de atrás de la computadora, el sitio ideal es donde no este cubriendo ventiladores u otro tipo de ventilación o partes movibles como las cubiertas de ranuras. <br />
----<br />
'''Coloque la etiqueta de “Free Geek”''' <br />
* Póngala en la parte delantera del sistema, en un sitio adecuado. (Generalmente junto o debajo de la etiqueta del procesador). <br />
----<br />
'''Consulte con un instructor de Build'''<br />
* El instructor revisará y editará el “printme” para firmarlo.<br />
* Su instructor le puede pedir que reemplace ciertos componentes, que requerirán volver a ejecutar el "printme". Se puede necesitar que algunos cambios sean hechos en el navegador de web. Si el instructor da el "visto bueno", continúe con el siguiente paso. <br />
----<br />
'''Guarde “Printme” en el “Desktop”'''<br />
* Después de que un instructor de Build haya inspeccionado el sistema, pulse "Print" en la ventana que se abre. Seleccione la opción "Print to file." Guarde el archivo en el “Desktop” y dele el nombre "Printme QC" y pulse "Print" para guardar. Pulse el icono “Printme QC” en el “Desktop” para abrirlo.<br />
----<br />
'''Habilite las impresoras de la red:'''<br />
* Vaya a '''System>>Administration>>Printing'''<br />
* Seleccione '''Server >>Settings''' y marque la casilla ''Show Printers Shared by Other Systems'' y pulse OK.<br />
* Espere unos momentos y pulse el icono refresh. Debe aparecer una selección de impresoras. <br />
----<br />
'''Imprima una copia de PrintMe'''<br />
* Cierre la ventana "Printing - localhost" que se abre y seleccione la impresora "build" del menú de impresoras una vez que aparece. Pulse “Print” y obtenga la hoja de la impresora en la esquina oeste del cuarto.<br />
* Pida al instructor de Build firmar en la hoja impresa. Luego dóblela por la mitad (longitudinalmente) y péguela en la parte superior del sistema (el lado de la página con las iniciales del instructor va hacia arriba).<br />
----<br />
'''Apague y ponga el sistema en el estante adecuado'''<br />
* Abra un terminal y escriba "sudo halt", luego pulse Enter. Cuando el sistema se ha apagado, desconecte todos los cables, compruebe que el armazón este bien cerrado y asegurado y pregunte a un instructor dónde colocar el sistema una vez que se haya apagado completamente. <br />
----<br />
'''Limpie el área de trabajo si es la útima computadora del día''' <br />
* Por favor, guarde todas las herramientas, tire la basura o cualquier adhesivo que haya quedado, ponga los tornillos en los contenedores apropiados, envuelva los cables alrededor del teclado y del ratón, apague las bocinas y las pantallas y en general arregle el área.<br />
----<br />
<br />
='''GUIA DE CONSTRUCCION'''= <br />
'''Trabaje a través de cada paso lo mejor que pueda, y luego pídale a su vecino o a su instructor de construcción ayuda si usted tiene preguntas.''' Trate de aprender la razón de cada uno de los pasos: este conocimiento será útil más tarde, cuando, inevitablemente, las cosas no vayan tan bien.<br />
<br />
'''Utilice sus recursos''' Hay muchos recursos para usted - su vecino, los asistentes, los instructores de construcción y, por supuesto, el Internet. Se puede acceder a consejos y soluciones de problemas e ideas en nuestro wiki:(http://wiki.freegeek.org) en la página “Build tips”. o en nuestra guia de problemas (http://wiki.freegeek.org/index.php/Build_Troubleshooting_Guide)<br />
<br />
Suministros como tarjetas (cards), rails, discos duros (hard drives), etc. se encuentran en los estantes metálicos ubicados en el centro del taller de construcción. Aquí también se encuentra una caja que contiene una variedad de memorias DDR y DDR2. <br />
{| border="2" fontname="Nimbus Sans" fontsize="12"<br />
|-<br />
==ANTES DE ENCENDER== <br />
----<br />
'''En el pizarrón blanco, encuentre en que tiene que trabajar''' <br />
* Vaya a la bodega escoja un sistema que le gustaría construir. <br />
*'''Ponga atención a la etiqueta “Green Light”.''' Esta le dará importante información, como el tipo de video, si no "POST" (presentó la información), si el procesador (processor) es Dual Core, etc. Asegurece que el sistema que usted va a armar es apropiado para estas especificaciones. <br />
* Si todo se ve bien, traiga una computadora de la bodega al taller de construcción y encuentre una manera de abrirlo. <br />
----<br />
'''Revise los condensadores eléctricos''' <br />
*Inspeccione visualmente los condensadores eléctricos de la tarjeta madre (motherboard) por bultos o fugas. Si encuentra algo, pida al instructor una etiqueta "Rejected". <br />
----<br />
'''Asegure el armazón'''<br />
* Cubra los compartimentos o ranuras abiertas Sustituya las piezas que le faltan al armazón. (Se puede sustituir una unidad de CD-ROM si no encuentra una cubierta disponible). Algunas armazones requieren partes específicas (de fábrica). Si no tenemos extras a la mano, lamentablemente tenemos que reciclar ...<br />
* Revise de que todos los componentes estén bien asegurados.<br />
* Revise/retire cualquier tornillo flojo o cables innecesarios. Si no está seguro de cómo hacer esto, consulte con un instructor. <br />
----<br />
'''¿Hay marcas de Microsoft? ¿(Certificados de Autenticidad) etiquetas de activo (identificación del último propietario)? ¿O etiquetas de marca de hardware en la placa frontal (identificación de los componentes originales, como RAM, disco duro, unidad óptica, etc)?'''<br />
*Si lo hay, retírelos. '''NO QUITE ninguna atiqueta “FG-PDX”, “Uncovered Electronic Device” ni las etiquetas “Green Light”.''' <br />
----<br />
'''Limpie y aspire el sistema'''<br />
* hay una aspiradora disponible en el estante de "Build" cerca de los artículos de limpieza. La manera más efectiva de limpiar un sistema es utilizar una brocha limpia para mover el polvo mientras se aspira.<br />
----<br />
'''Pruebe la batería'''<br />
* Tome un voltímetro y póngalo en DCV=20, coloque una terminal del voltímetro en la batería y la otra en la parte metálica del armazón. La batería está utilizable si el voltímetro muestra 3.0 o más.. <br />
----<br />
'''Instale el RAM'''<br />
* Para DDR2, primero intente una velocidad de 533 (PC3200). Si eso no funciona, pruebe otros números. A veces BIOS le indicará la velocidad necesaria.<br />
* Si las ranuras de memoria del sistema no aceptan la memoria DDR2, se necesita otro tipo. DDR3 es aceptable - pregunte a su instructor por DDR3 RAM. Los sistemas con DDR1 tienen que ser rechazados y devueltos a Prebuild como sistemas “yellow-light”.<br />
** NOTA: Generalmente el RAM debe ser emparejado en dos canales para un mayor rendimiento (es decir, 2 tabletas de RAM utilizadas en ranuras específicas, a menudo con código de color). Asegúrece de probar todas las combinaciones de ranuras si usted tiene problemas para conseguir que el sistema reconozca la memoria RAM y consulte a un instructor si tiene mas problemas.<br />
* Anote el tipo y la velocidad del RAM instalado, esta información será muy útil más adelante. <br />
----<br />
'''Instale una tarjeta de vídeo si es necesario''' <br />
*No se necesita instalar una tarjeta AGP si hay vídeo “onboard”. <br />
* Pregunte a un instructor si se necesita una tarjeta PCI-e. Hay tarjetas AGP disponibles en el taller de construcción.<br />
----<br />
'''Encienda el sistema''' <br />
*Encienda el sistema para ver si aparece el valor deseado de la memoria en el POST o en la BIOS. <br />
----<br />
'''Apague el sistema''' <br />
----<br />
'''retire la unidad de disco “floppy” si es posible'''<br />
* Retire la unidad de disco “floppy” si puede hallar una tapa adecuada para cubrir el espacio. Si no hay tapas, se puede dejar la unidad de disco pero asegúrese que no esté conectado al "Motherboard" o a la fuente de poder. Asegúrese de que la unidad de disco “floppy” esté deshabilitada en BIOS y remuévalo de la secuencia de “boot” si es posible. <br />
----<br />
'''Compruebe si hay "NIC" (tarjeta de interfaz de Red o ethernet)''' <br />
* si no la encuentra, instale una tarjeta de Red. <br />
----<br />
'''Instale el disco duro (hard drive)''' <br />
* Tome un disco duro con el tamaño apropiado del estante de suministros (según la hoja de especificaciones), o pidáselo a un instructor. Revise si necesita un disco duro con IDE o con SATA y asegúrese que tiene los cables y las conexiones eléctricas necesarias<br />
* Instale la unidad de disco duro y conéctelo a la fuente de alimentación y la tarjeta madre. (Si la unidad tiene conexiones IDE, asegúrese de que el “Jumper” está en la posición “Master”. Pregunte a un instructor para obtener más información).<br />
* Necesita preguntar a un instructor para los discos duros mayores de 120 GB. <br />
----<br />
'''Instale la tarjeta de sonido si es necesaria''' <br />
*Si hay sonido “onboard”, no se nevesita instalar una tarjeta de sonido. <br />
----<br />
'''Instale la/s unidad/es de disco óptico CD/CDRW/DVD/DVD-RW''' <br />
* Si ya hay unidades ópticas instaladas en su sistema, revise la fachada para determinar sus capacidades. Si las unidades están dentro de las especificaciones para el sistema que está construyendo y tienen conexiones IDE, asegúrese de que estén conectados como “Master/Slave” o simplemente “Master” si sólo hay una unidad.<br />
* Si las unidades están fuera de las especificaciones, sáquelos y clasifiquelos en las cajas correspondientes en los estantes de Build. Reemplace con unidades apropiadas según sea necesario. <br />
----<br />
'''Tape las ranuras y bahías abiertas''' <br />
* Asegúrese de tener cubiertas para todos los espacios que no se llenarán con una tarjeta o unidad de disco. Mire en los sistemas similares para saber que piezas se ven parecidas. Asegúrese que los tornillos estén bien apretados y pruebe tocándolos a cada uno con su dedo. Si la tapa de una ranura cae cuando un computador está encendido, '''puede causar un corto circuito en la tarjeta madre.''' <br />
----<br />
<br />
==ARRANQUE Y ENTRE A BIOS== <br />
----<br />
'''Conecte el monitor, el teclado, el ratón, la Red, el sonido y los cables de poder.''' <br />
----<br />
'''Entre en la configuración de BIOS''' <br />
*Encienda la computadora. Hay una tecla específica para entrar en BIOS debe aparecer en la pantalla antes de arrancar, así como también la tecla del menú de arranque si es aplicable. Si no aparece una pantalla, tiene que adivinar la tecla: Del, Esc, Enter, F1, F2, F9, F10 y F12 son las típicas.<br />
* Entre a BIOS y '''escriba las teclas para entrar a BIOS y para el Boot Menu''' porque las va a necesitar mas tarde. <br />
----<br />
'''Revise la fecha y la hora''' <br />
*Revise la fecha y la hora en BIOS y cámbielas si es necesario. <br />
----<br />
'''Restablezca las opciones de BIOS''' <br />
*A veces se tiene que buscar en BIOS para encontrar lo que se necesita cambiar. Mientras busca, disfrute del placer de aprender acerca de la configuración BIOS. <br />
----<br />
'''Detecte el disco duro''' <br />
*Busque en BIOS para ver si la computadora reconoce el disco duro. <br />
----<br />
'''Asignar la aecuancia de cargar ("boot”)''' <br />
*Tiene que ser: '''1ro-CD-ROM; 2do-El disco duro. Si es posible deshabilite todos los otros dispositivos como la unidad de disco “floppy” o el “network boot” de la sequencia de cargar.''' <br />
----<br />
'''Cuando sea posible, modifique cualquiera/todos de los siguentes pasos'''<br />
* Habilite los puertos USB<br />
* Habilite Hyper-thre<br />
'''Guarde los cambios y salir de la BIOS''' <br />
*La computadora debería cargar el sistema oporativo Ubuntu. <br />
----<br />
<br />
==PROBAR EL HARDWARE Y SOFTWARE== <br />
----<br />
'''Entrar al sistema''' <br />
*usuario = Default User <br />
*clave = freegeek <br />
----<br />
'''Hacer el “basiccheck”''' <br />
*Desde un terminal, tecle '''“basiccheck”'''. Lea por cada uno de las pruebas y verifique que se comprueben. <br />
----<br />
'''Aprender a instalar programas por el usuario gráfico interface (GUI – el ratón)''' <br />
*Para añadir software, primero busque en el centro de software Ubuntu (Applications>Ubuntu Software Center). Así se ven las aplicaciones apyoadas por *Ubuntu, más muchas otras. Busque '''"k3b"''' e instálela. K3b es un programa escritor de CD/DVD. <br />
----<br />
'''Aprender a instalar programas por la línea de comando “command line”''' <br />
*Abra un terminal y tecle '''"sudo apt-get install gimp"''' y oprima '''“Enter”'''. Así usted instala el programa que se llama Gimp. <br />
----<br />
'''Probar un disco CD de audio''' <br />
*Ponga un disco de sonido en la unidad de disco CD-ROM. Se escucha lo que usted espera? Es el sonido suficientamente alto para oir con facilidad? Repita el proceso para cada unidad de disco CD-ROM. Repita para cada puerto de sonido adicional. <br />
*Pregúntele al instructor de Build si la computadora con que usted está trabajando tiene surround sound (sonido envolvente). Generelmente el surround sound va a ser anaranjado o gris. <br />
----<br />
'''Probar un disco de data''' <br />
*Ponga un disco de data en la unidad de disco CD-ROM. Si el navegador lee el archivo, la unidad de disco CD-ROM funciona correctamente. Repita para cada unidad de disco optical. <br />
----<br />
'''Probar un DVD (solamente las unidades de disco DVD/DVD-RW)''' <br />
*Ponga un disco DVD en la unidad de disco DVD-ROM. Si el navegador lee el archivo, la unidad de disco DVD-ROM funciona correctamente. Si aparece un mensaje para que usted busque '''“los plugins o codecs”''' adecuados, por favor no haga esto! Todavía funciona la unidad de disco DVD. Repita para cada unidad de disco DVD-ROM. <br />
---- <br />
'''Probar la grabación de CD (solamente las unidades CD-RW/combo)''' <br />
*Ponga un disco CD-RW en la unidad de disco y abra el programa '''“Brasero Disc Burning”''' (Vaya a Applications > Sound > Video). Seleccione '''“Data Project”''' y después '''“examples.desktop”'''. Haga clik en '''“Burn”''' que aparece en la parte inferior derecha de la pantalla. Cuando acabe el disco, introduzca el disco otra vez para verificar que contenga el archivo de ejemplos, el archivo debería aparecer en el escritorio de la computadora. <br />
*Ahora, utilizando el programa '''“Brasero”''', seleccione '''“Tools > Blank”'''. Este proceso hace que el disco se quede sin ninguna información grabada. <br />
---- <br />
'''Probar la grabación de los discos DVD (solamente las unidades DVD-RW)''' <br />
*Ponga un disco DVD-RW en la unidad de disco DVD. En el programa '''“Brasero”''', seleccione '''“File > start new project”'''. Haga clik en “Burn” que aparece en la parte inferior derecha de la pantalla. Cuando acabe el disco, introduzca el disco otra vez para verificar que contenga el archivo de ejemplos, el archivo debería aparecer en el escritorio de la computadora. <br />
*Ahora, utilizando el programa “Brasero”, seleccione '''“Tools > Blank”'''. Este proceso hace que el disco se quede sin ninguna información grabada. <br />
---- <br />
'''Sacar todos los discos CD y DVD de las unidades de disco''' <br />
----<br />
'''Probar los puertos USB''' <br />
*Conecte un ratón USB y vea que interactúe con los íconos y demás rasgos de la pantalla. Repita para todos los puertos USB. <br />
----<br />
'''Cargar el sistema operotivo de un disco CD “live”''' <br />
*Ponga un disco CD del sistema operativo Ubuntu en la unidad de disco y reinicie la computadora. El sistema debería cargar del disco. Permita que carque a la primera pantalla de instalación Ubuntu. Si llega a la pantalla de instalación, significa que funciona bien. Expulse el disco y oprima '''CTRL+ALT+DEL''' para reiniciar. <br />
----<br />
'''Imprimir "printme" del terminal''' <br />
*Desde un terminal, tecle "printme". Un formulario aparecerá en el navegador. Revise el pizarón para ver qué hay que apuntar en el espacio para las notas (cualquier cosa especial o diferente de la computadora, incluyendo cómo entrar a la BIOS). <br />
----<br />
'''Hablar con el/la instructor/a de Build antes de apagar su computadora.''' <br />
*El/La instructor/a de Build va a revisar la hoja “print me” y editarla para que esté lista para imprimir. <br />
----<br />
'''Imprima la hoja “print me”.''' <br />
----<br />
'''Lea la data en la hoja “print me”, y después haga clik en “print”.''' <br />
*Lea la data en la hoja "'''print me'''”. <br />
*Haga clik en “'''print'''”. <br />
*Escoja "'''Print to File'''" de la lista de impresoras. <br />
*Escoja "'''Desktop'''" para guardar el documento. <br />
*Dele al archivo el nombre "'''Build Printme'''" y haga clik en “'''print'''”. <br />
----<br />
'''Apague el sistema y ponga las piezas en la plataforma adecuada.''' <br />
*Utilice los controles de software para apagar el sistema (ya sea '''“sudo halt”''' o desde el menú del sistema en la parte superior). <br />
*Pregunte dónde colocar el sistema. <br />
----<br />
'''Limpie el área de trabajo si es su último control de calidad del día.'''<br />
*Por favor, guarde todas las herramientas, tire la basura o cualquier adhesivo que permanezca, ponga los tornillos en los contenedores apropiados y envuelva los cables del teclado y el ratón y en general limpie el área. <br />
|}<br />
<br />
English Version: [[Build_Checklists]]<br />
<br />
Vercion Español: [[Build_Checklists_en_Español]]<br />
<br />
[[Category:Spanish Build Documents]]<br />
[[Category: Build]]</div>Alambhttp://wiki.freegeek.org/index.php?title=2012_Website_Redesign&diff=646272012 Website Redesign2012-10-12T01:07:19Z<p>Alamb: </p>
<hr />
<div>This page was created to start collecting information for a website redesign, as proposed by the PR Committee. <br />
<br />
== New and Improved Features/Structure ==<br />
* "Free Geek in the Media" page with links to media features, flexible archival settings<br />
* Option whether or not to post new page content in that page's category page feed (e.g. option not to include Media posts in main News feed)<br />
* "Large Donors/Partners" page listing individual donations over a certain amount, institutional and in-kind donors, corporate logos?<br />
* Newsletter sign-up button<br />
* Streaming Twitter/Facebook feed<br />
* Seperate pages for institutional and individual donors<br />
* Bold donate button on front page<br />
* Address and hours on front page (and footer of every page).<br />
* Links to wiki, possibly other outward facing services<br />
* "Digital Tour": Area highlights w/ photos, more expository descriptions<br />
* Integrate Inreach programs (e.g., Star Volunteers, Events, etc)<br />
* Must be mobile-friendly!<br />
* Presence for current certifications<br />
* Incorporate Spanish pages (or...whole separate Spanish website).<br />
* Submenus<br />
* RSS feed<br />
* Photo area (Flickr account link?)<br />
* Header on every page: Logo, Hours/Location/Phone, Link to directions, Social Media Buttons <br />
* Footer on every page: Text Navigation and Search bar<br />
* No Blog looking content, except on community news page<br />
* Full articles on community news page.<br />
* Currents news on Home page with fully flexible posting options<br />
<br />
== Technical/Maintenance ==<br />
* Easy/quick for staff and volunteers to maintain<br />
* Admin: pretty easy to learn to administer, easy to add users and privileges, easy to make new pages, easy to change layout of old pages<br />
* Accessible in Debian (for server hosting)<br />
* Analytics to view click-throughs to individual posts, and internal navigation between individual pages and posts<br />
* Quick loading for dial-up users<br />
* Limit JavaScript<br />
* More cohesive method/procedure to maintain site<br />
* Ability to integrate with RT<br />
* Ideal: site that can produce static pages without having to send them to a database for backup<br />
<br />
== Layout/Design ==<br />
* Press area expanded to include links to FG in the news, articles, FG YouTube page, link to reddit?<br />
* Corporate hardware donor and Financial donor thanks page<br />
* Friends/Partners links<br />
* Links to other Free Geeks and similar organizations<br />
* Harmful stuff in computers page<br />
* Photo area<br />
* Map images with links - Google, Trimet, Bicycle<br />
* More prominent hours, location, phone number on front page<br />
* Little to no scroll on front page<br />
* Keep current Logo (Remove pictures and just use the Free Geek logo), Choose colors/fonts that flow nicely from the logo.<br />
* Muted colors, New Scheme (Green ?), Fading colors/gradients<br />
* Front page has link to Spanish Program Info page listing hours, Spanish tour times, basic descriptions of Build and Adoption in Spanish<br />
<br />
== Branding ==<br />
* Reuse/Recycling<br />
* Community<br />
* Environmentalism<br />
* Casual<br />
* Empowered<br />
* Open Source<br />
* Global, diverse, accessible<br />
* Creative<br />
* Comfortable with change<br />
* Sustainable/Green<br />
* Community Resource<br />
* Fun<br />
* Cooperative Learning<br />
<br />
== Current Website Issues ==<br />
* Busy (Make new site Clean)<br />
* Dated (Make new site Modern)<br />
* Constrained (Make new site Flexible)<br />
* Intelligent and fun (writing style)<br />
* Some elements are easy to use (Build on this)<br />
<br />
[[Category:2012 Website Redesign Project]]</div>Alambhttp://wiki.freegeek.org/index.php?title=Website_Feedback_from_Volunteers&diff=64511Website Feedback from Volunteers2012-10-05T20:02:10Z<p>Alamb: /* What volunteers expect/want to see on a websites home page */</p>
<hr />
<div>The website redesign team conducted interviews with ten volunteers on Wednesday Oct. 3 to find out their feelings about Free Geek, what they expect to see in our website and what kind of layout/design would be suitable to their needs. Here are the notes from those conversations.<br />
<br />
== What volunteers think about Free Geek == <br />
Volunteering, Laptop exchange, helping community, helping to put computers in schools and in the homes of lower income individuals, recycling, cleaner environment, Reuse of older computers and their parts instead of recycling them, social service opportunities, working with start-ups and other non profit organizations, educational and learning opportunities, technical support, wide variety of<br />
classes, eWaste and how it affects the environment, free geek is a community technology center.<br />
<br />
== How volunteers generally use the Internet == <br />
Research, check for spelling errors, reference, learning opportunities, general browsing, access various types of Wiki pages, email and communication, keep in contact with others (social media, etc), news, blogs and forums, literature, scheduling, manage websites, update computers (searching for updates, drivers, etc), videos, Netflix, entertainment, Skype, school, gaming.<br />
<br />
== What volunteers expect/want to see on a website's home page ==<br />
Information about the site and the company in general, contact information including address or a clear contact link, phone number, and hours of operation, what the site or business offers, clear and easy to use navigation, search bar, support information or a clear support page link, social media links, little to no scrolling.<br />
<br />
== The information and features that volunteers found most useful on the current free geek site ==<br />
Address; hours; volunteer information; link to thrift store; Wiki pages<br />
<br />
==Information that volunteers found difficult to find on the current site ==<br />
Phone number<br />
<br />
== Aspects of the site that volunteers don't like ==<br />
Font/color scheme (too basic looking);navigation needs to be cleaned up and made more consistent across site clearly marked, and more easy to understand navigation; website resembles a blog; Wiki pages: are out of date, no link from Free Geek site, should be a linear structure, and should be created using Moodle; too much scrolling.<br />
<br />
== Things volunteers would like to see on the website ==<br />
Photos of staff (but omit last name for security?), different departments and building layout; Online scheduling for volunteer time- or the ability to view the schedule online, online tracking of hours, link to email/easier way to contact someone if volunteer will be late or will miss a shift; volunteers should be notified on the website that closed toed shoes are required, and that they get a 20% discount at the thrift store; within technical support information: website should say there is a fee for repair of items not purchased at Free Geek and include a description of the tech support process, also should provide links to alternative repair shops that Free Geek recommends; list of and links to major partners of Free Geek; In the Build Program, website should include link to motherboard schematics, and process to determine if a part is good or bad; instructional videos; technical info about PCs and Ubuntu; more colorful icons; add end dates for posts; more prominent closure notices; recycling: lists of what Free Geek will and will not accept, statistics and information about benefits to the environment; thrift store prices; more detailed instructions (in layman's terms) regarding the Hardware Grant, particularly the application, let them know that they are limited to 3 in a 90 day period; links to social media, including like and share buttons/more active social media presence; link to tech support and class<br />
list should be on front page of website; use 301 redirects; better search capabilities and more than one way to access information; website should be designed in a way that is mindful of lower resolution monitors and slower PCs; combine contribution/volunteer icons on front page; more frequent updates of pictures and content; simplified contact page; explanation of what Free Geek does; Use F pattern for more important information; don't use high bandwidth items; ability to check online for class vacancies; On<br />
grant form we should add a box so that they can let us know if they plan to keep Linux or not and let them know that support is only for hardware and Linux, let them know that we don't ship and that equipment cannot be picked up by a shipping company;<br />
<br />
== Things volunteers believe should not be included on the website == <br />
Music, Flash, excessive amount of colors.<br />
<br />
== Forms ==<br />
For the most part most volunteers found the forms on the site easy to use and to understand, however there was one volunteer that said the internship area of the current site could use some cleaning up and that the forms on the current site were clunky and needed to be redefined.<br />
<br />
== Search Function ==<br />
Not all the volunteers have used the search function on the current site. Some of the volunteers liked it a good deal and said that it worked well, while others noted that the search was poorly located and that a fixed width should not be used on the bar so it will not go outside of its container.<br />
<br />
[[Category:2012 Website Redesign Project]]</div>Alambhttp://wiki.freegeek.org/index.php?title=Website_Feedback_from_Volunteers&diff=64509Website Feedback from Volunteers2012-10-05T19:43:20Z<p>Alamb: </p>
<hr />
<div>The website redesign team conducted interviews with ten volunteers on Wednesday Oct. 3 to find out their feelings about Free Geek, what they expect to see in our website and what kind of layout/design would be suitable to their needs. Here are the notes from those conversations.<br />
<br />
== What volunteers think about Free Geek == <br />
Volunteering, Laptop exchange, helping community, helping to put computers in schools and in the homes of lower income individuals, recycling, cleaner environment, Reuse of older computers and their parts instead of recycling them, social service opportunities, working with start-ups and other non profit organizations, educational and learning opportunities, technical support, wide variety of<br />
classes, eWaste and how it affects the environment, free geek is a community technology center.<br />
<br />
== How volunteers generally use the Internet == <br />
Research, check for spelling errors, reference, learning opportunities, general browsing, access various types of Wiki pages, email and communication, keep in contact with others (social media, etc), news, blogs and forums, literature, scheduling, manage websites, update computers (searching for updates, drivers, etc), videos, Netflix, entertainment, Skype, school, gaming.<br />
<br />
== What volunteers expect/want to see on a websites home page ==<br />
Information about the site and the company in general, contact information including address or a clear contact link, phone number, and hours of operation, what the site or business offers, clear and easy to use navigation, search bar, support information or a clear support page link, social media links, little to no scrolling.<br />
<br />
== The information and features that volunteers found most useful on the current free geek site ==<br />
Address; hours; volunteer information; link to thrift store; Wiki pages<br />
<br />
==Information that volunteers found difficult to find on the current site ==<br />
Phone number<br />
<br />
== Aspects of the site that volunteers don't like ==<br />
Font/color scheme (too basic looking);navigation needs to be cleaned up and made more consistent across site clearly marked, and more easy to understand navigation; website resembles a blog; Wiki pages: are out of date, no link from Free Geek site, should be a linear structure, and should be created using Moodle; too much scrolling.<br />
<br />
== Things volunteers would like to see on the website ==<br />
Photos of staff (but omit last name for security?), different departments and building layout; Online scheduling for volunteer time- or the ability to view the schedule online, online tracking of hours, link to email/easier way to contact someone if volunteer will be late or will miss a shift; volunteers should be notified on the website that closed toed shoes are required, and that they get a 20% discount at the thrift store; within technical support information: website should say there is a fee for repair of items not purchased at Free Geek and include a description of the tech support process, also should provide links to alternative repair shops that Free Geek recommends; list of and links to major partners of Free Geek; In the Build Program, website should include link to motherboard schematics, and process to determine if a part is good or bad; instructional videos; technical info about PCs and Ubuntu; more colorful icons; add end dates for posts; more prominent closure notices; recycling: lists of what Free Geek will and will not accept, statistics and information about benefits to the environment; thrift store prices; more detailed instructions (in layman's terms) regarding the Hardware Grant, particularly the application, let them know that they are limited to 3 in a 90 day period; links to social media, including like and share buttons/more active social media presence; link to tech support and class<br />
list should be on front page of website; use 301 redirects; better search capabilities and more than one way to access information; website should be designed in a way that is mindful of lower resolution monitors and slower PCs; combine contribution/volunteer icons on front page; more frequent updates of pictures and content; simplified contact page; explanation of what Free Geek does; Use F pattern for more important information; don't use high bandwidth items; ability to check online for class vacancies; On<br />
grant form we should add a box so that they can let us know if they plan to keep Linux or not and let them know that support is only for hardware and Linux, let them know that we don't ship and that equipment cannot be picked up by a shipping company;<br />
<br />
== Things volunteers believe should not be included on the website == <br />
Music, Flash, excessive amount of colors.<br />
<br />
== Forms ==<br />
For the most part most volunteers found the forms on the site easy to use and to understand, however there was one volunteer that said the internship area of the current site could use some cleaning up and that the forms on the current site were clunky and needed to be redefined.<br />
<br />
== Search Function ==<br />
Not all the volunteers have used the search function on the current site. Some of the volunteers liked it a good deal and said that it worked well, while others noted that the search was poorly located and that a fixed width should not be used on the bar so it will not go outside of its container.<br />
<br />
[[Category:2012 Website Redesign Project]]</div>Alambhttp://wiki.freegeek.org/index.php?title=Website_Feedback_from_Volunteers&diff=64508Website Feedback from Volunteers2012-10-05T19:42:26Z<p>Alamb: Created page with "The website redesign team conducted interviews with ten volunteers on Wednesday Oct. 3 to find out their feelings about Free Geek, what they expect to see in our website and what…"</p>
<hr />
<div>The website redesign team conducted interviews with ten volunteers on Wednesday Oct. 3 to find out their feelings about Free Geek, what they expect to see in our website and what kind of layout/design would be suitable to their needs. Here are the notes from those conversations.<br />
<br />
== What volunteers think about Free Geek == <br />
Volunteering, Laptop exchange, helping community, helping to put computers in schools and in the homes of lower income individuals, recycling, cleaner environment, Reuse of older computers and their parts instead of recycling them, social service opportunities, working with start-ups and other non profit organizations, educational and learning opportunities, technical support, wide variety of<br />
classes, eWaste and how it affects the environment, free geek is a community technology center.<br />
<br />
== How volunteers generally use the Internet == <br />
Research, check for spelling errors, reference, learning opportunities, general browsing, access various types of Wiki pages, email and communication, keep in contact with others (social media, etc), news, blogs and forums, literature, scheduling, manage websites, update computers (searching for updates, drivers, etc), videos, Netflix, entertainment, Skype, school, gaming.<br />
<br />
== What volunteers expect/want to see on a websites home page ==<br />
Information about the site and the company in general, contact information including address or a clear contact link, phone number, and hours of operation, what the site or business offers, clear and easy to use navigation, search bar, support information or a clear support page link, social media links, little to no scrolling.<br />
<br />
== The information and features that volunteers found most useful on the current free geek site ==<br />
Address; hours; volunteer information; link to thrift store; Wiki pages<br />
<br />
==Information that volunteers found difficult to find on the current site ==<br />
Phone number<br />
<br />
== Aspects of the site that volunteers don't like ==<br />
Font/color scheme (too basic looking);navigation needs to be cleaned up and made more consistent across site clearly marked, and more easy to understand navigation; website resembles a blog; Wiki pages: are out of date, no link from Free Geek site, should be a linear structure, and should be created using Moodle; too much scrolling.<br />
<br />
== Things volunteers would like to see on the website ==<br />
Photos of staff (but omit last name for security?), different departments and building layout; Online scheduling for volunteer time- or the ability to view the schedule online, online tracking of hours, link to email/easier way to contact someone if volunteer will be late or will miss a shift; volunteers should be notified on the website that closed toed shoes are required, and that they get a 20% discount at the thrift store; within technical support information: website should say there is a fee for repair of items not purchased at Free Geek and include a description of the tech support process, also should provide links to alternative repair shops that Free Geek recommends; list of and links to major partners of Free Geek; In the Build Program, website should include link to motherboard schematics, and process to determine if a part is good or bad; instructional videos; technical info about PCs and Ubuntu; more colorful icons; add end dates for posts; more prominent closure notices; recycling: lists of what Free Geek will and will not accept, statistics and information about benefits to the environment; thrift store prices; more detailed instructions (in layman's terms) regarding the Hardware Grant, particularly the application, let them know that they are limited to 3 in a 90 day period; links to social media, including like and share buttons/more active social media presence; link to tech support and class<br />
list should be on front page of website; use 301 redirects; better search capabilities and more than one way to access information; website should be designed in a way that is mindful of lower resolution monitors and slower PCs; combine contribution/volunteer icons on front page; more frequent updates of pictures and content; simplified contact page; explanation of what Free Geek does; Use F pattern for more important information; don't use high bandwidth items; ability to check online for class vacancies; On<br />
grant form we should add a box so that they can let us know if they plan to keep Linux or not and let them know that support is only for hardware and Linux, let them know that we don't ship and that equipment cannot be picked up by a shipping company;<br />
<br />
== Things volunteers believe should not be included on the website == <br />
Music, Flash, excessive amount of colors.<br />
<br />
== Forms ==<br />
For the most part most volunteers found the forms on the site easy to use and to understand, however there was one volunteer that said the internship area of the current site could use some cleaning up and that the forms on the current site were clunky and needed to be redefined.<br />
<br />
== Search Function ==<br />
Not all the volunteers have used the search function on the current site. Some of the volunteers liked it a good deal and said that it worked well, while others noted that the search was poorly located and that a fixed width should not be used on the bar so it will not go outside of its container.</div>Alambhttp://wiki.freegeek.org/index.php?title=PR&diff=64451PR2012-10-03T01:55:11Z<p>Alamb: /* Blurb about Free Geek */</p>
<hr />
<div>; Standing [[PR]] Committee;<br />
: ''Mission:'' PR Vision Statement (adopted by committee on May xx, 2009)<br />
(Limmerick version)<br />
Figure out what The Geek has to say,<br />
And then say it in a Geeky way.<br />
Spread the word to Joe Shmoe,<br />
To the press and SludgeCo.<br />
And then listen for 'boos' and 'hoorays.'<br />
<br />
(Haiku version)<br />
Discern the message.<br />
Spread the word far, wide and well.<br />
Shut up and listen.<br />
: ''Programs:'' In charge of media outreach & relations, ads & marketing, the main Free Geek website, tabling events and networking with other organizations.<br />
: ''Email:'' pr at freegeek.org<br />
<br />
----<br />
<br />
==Priorities (as established 3/12)==<br />
#Thrift Store<br />
#$ Donations<br />
#Specific classes/events<br />
#Equipment donations<br />
#Ongoing volunteers<br />
#Institutional donors<br />
#Front desk<br />
#Nonprofit partnerships<br />
#Mission-related education<br />
#Day-to-day volunteers<br />
<br />
==Overview==<br />
<br />
PR is a standing staff committee which is responsible for media outreach & relations, ads & marketing, [http://freegeek.org the Free Geek website], and networking with other organizations.<br />
<br />
Check: [[PR Facilitator/Scribe]]<br />
<br />
* The PR Committee meets every Wednesday morning. Generally, alternating Wednesdays are devoted to "working meetings."<br />
<br />
== Running a PR meeting ==<br />
Please see [[Meeting Tips]] for essential habits of good facilitation. Also remember [http://en.wikipedia.org/wiki/SMART_criteria| to use SMART guildlines] to a basic check in on subject matter.<br />
* Preparation<br />
** Check in with members well in advance of the meeting to see if there are any dependencies that are interfering with task completion<br />
* Agenda contents - Should contain:<br />
** Previous commitments and Old business<br />
** New agenda items<br />
** Events and goals radar/timetable<br />
* Agenda management - Agendas should only contain items with specific questions to be answered or with specific work to be delegated. Other items should be discussed out of meeting or moved into a working meeting.<br />
* Assigning work for "working meetings"<br />
<br />
== Blurb about Free Geek ==<br />
<br />
This blurb is a template for press releases and other PR publications. The PR committee is available to help edit this blurb to fit the parameters and purposes of any such publication, and welcomes any suggestions for changes or improvements. Suggestions and/or requests can be submitted via the suggestion box, or by email to pr@lists.freegeek.org.<br />
<br />
FREE GEEK is a 501(c)(3) not-for-profit community technology center that recycles technology and provides access to computers, the internet, education and job skills in exchange for community service. We accept donations from the public of most electronic equipment, ranging from systems and printers to stereos and mp3 players. Free Geek does most of its work thanks to the dedicated service of our volunteers; participation averages around 550-600 active volunteers each month. Our volunteers evaluate, test and disassemble various components, which are either recycled as electronic scrap or incorporated into refurbished systems. These refurbished computers are then loaded with Free and Open Source Software. Free Geek has two flagship programs through which most of our volunteers get their start. The most popular is the Adoption program, wherein any individual may contribute 24 hours of volunteering in exchange for a free computer. In the Build program, volunteers build five computers for Free Geek and then take their sixth one home, learning to identify hardware and troubleshoot and assemble refurbished systems over the course of the program. Many Build volunteers continue to gain knowledge and contribute to the Free Geek mission by building Laptops, Macs and Servers, testing hardware, and instructing in the Build program. <br />
<br />
In addition to the Build and Adoption volunteer programs, Free Geek also offers many internships to facilitate the building of higher-level skills in positions throughout the organization. We also offer a variety of free classes, open to the public, on a range of topics from building job skills and navigating the internet, to the use of free and open source software and Command Line. Computer hardware that does not go to Free Geek's volunteers is sold online and in our Thrift Store to members of the wider community, and granted out to schools, nonprofits and other community change organizations through our Hardware Grants program. Technical Support warranties are offered with all systems disbursed or sold, provided the user maintains a Free-Geek-supported operating system. Free Geek is also committed to electronic waste recycling and works exclusively with recycling businesses who engage in environmentally responsible practices to process the obsolete technology we receive. Free Geek is proud of being a democratically-run organization, and practicing consensus to make decisions at the management level. We are governed by a board of directors whose membership includes professionals in law, environmental advocacy, and information technologies, among other fields. Our board also reserves at least one quarter of its membership seats for active volunteers, and strives for democracy and transparency in its service to the Free Geek community.<br />
<br />
==PR Budget==<br />
* Ads<br />
** May $250<br />
** $10/month for other 11 months<br />
** $600 in '''Nov''' for Willamette Week Give Guide<br />
<br />
* Tabling<br />
** $20/month EXCEPT $75 in April for Earth Day <br />
* T-shirts, stickers, and similar merchandise (includes business cards)<br />
** ''We buy t-shirts twice a year'' ~$1500<br />
<br />
* Networking/learning conferences and memberships<br />
** AOR<br />
*** membership: $135/'''yr'''<br />
*** conference in '''June''': $470 (2 people, $235 each) ''' ''(usually free, but we don't know)'' '''<br />
*** mileage to Redmond, OR in '''June''': $150 (under C7)<br />
** <s>International Computer Refurbishing Summit in Toronto</s><br />
** $75 in '''Oct''' Membership in Sustainable Business Network <br />
<br />
* Direct Mail '''Nov''' (TBD)<br />
<br />
* Grant Research<br />
** $175 in '''Dec''' for Oregon Foundation Databook & CD 2009 edition<br />
<br />
* Brochure<br />
** $250 in '''Nov''' 1000 B/W copies of brochure on 28 wt paper--trifolded<br />
<br />
* Front Desk PR <br />
** $125 in '''Oct''' for Banner at Front Desk<br />
** $150 in '''Oct''' 8X10 Prints of Community recipient/volunteer photos & frames <br />
<br />
=== Related Items ===<br />
''(This is for notes that indicate expenses that affect your committee but are actually classified under a different committee.) ''<br />
<br />
* Conferences July $100 oscon (probably goes in HR -> Training and Education)<br />
* $100 for website developer (probably goes in C7 -> Staffing Costs)<br />
* $200/YEAR for mileage to conferences (C7 mileage reimbursement expense)<br />
<br />
==Webadmin==<br />
Check out our web stats! <br />
* [http://www.tump.com/~lmoore/logs/freegeek/ Webhits over the past year]<br />
* [http://www.tump.com/~lmoore/fglog/ Webhits archive]<br />
* [http://www.tump.com/www.freegeek.org-analog/ Webserver stats] (lists which words are searched to find us, operating systems used when browsing the site, etc.)<br />
<br />
==Links==<br />
* [[PR Tasks| Who does what]]<br />
*[[Monitored by Outreach]]<br />
*[[Stats and Testimonials]] - tidbits to support various marketing, advertising, PR materials<br />
*[[Computer Collection Events]] <br />
*[[Conferences]]<br />
*[[Corporate Sponsors]] - cultivating corporate sponsorship for Free Geek programs.<br />
*[[Give Guide]]<br />
*[[Media Liaison]]<br />
*[[Mailings]] - asking for money via letters.<br />
*[[Pickups Intake]]<br />
*[[Presentations/Lectures]]<br />
*[[Tabling]]<br />
*[[T-Shirts]]<br />
*[[Stickers]]<br />
*[[Log of Ads]]<br />
*[[GeekVideo]] - documentation, proliferation, replication... consternation?<br />
*[[Webadmin]]<br />
*[[Ambassador Basics]]<br />
*[[Neighborhood Association]]<br />
*[[Free Geek Slogans]]<br />
<br />
<br />
[[Category: PR]]<br />
[[Category: Standing Committees]]</div>Alambhttp://wiki.freegeek.org/index.php?title=Build_Instructor_Schedule&diff=64449Build Instructor Schedule2012-10-02T23:20:51Z<p>Alamb: /* Build Instructors Schedule */</p>
<hr />
<div>==Build Instructors Schedule==<br />
{| border="1" fontname="Nimbus Sans" fontsize="12" cellpadding="3" cellspacing="0"<br />
|-<br />
!width="34%" align="center" style="color:white; background-color:black;"|Day<br />
!width="33%" align="center" style="color:white; background-color:black;"|AM<br />
!width="33%" align="center" style="color:white; background-color:black;"|PM<br />
|-<br />
|align="center"|'''TUESDAY'''<br />
|<br />
Kurt<br><br />
Phil<br> <br />
'''''Elizabeth'''''<br />
|<br />
Howard<br><br />
'''''Amelia'''''<br />
|-<br />
|align="center"|'''WEDNESDAY'''<br />
|<br />
Daniel<br/><br />
'''''Jake'''''<br />
|<br />
Blaine<br><br />
Nate<br><br />
'''''Amelia'''''<br />
|-<br />
|align="center"|'''THURSDAY'''<br />
|<br />
John<br><br />
'''''Liliana'''''<br />
|<br />
Blaine<br><br />
Jeffrey<br><br />
'''''Lynnae'''''<br />
|-<br />
|align="center"|'''FRIDAY'''<br />
|<br />
Tara<br> <br />
Mary<br><br />
'''''Liliana'''''<br />
| <br />
Sam<br> <br />
'''''Lynnae'''''<br />
|-<br />
|align="center"|'''SATURDAY'''<br />
|<br />
Keith<br><br />
Brett<br/> <br />
'''''Amelia'''''<br />
|<br />
Brett<br/><br />
Max<br/><br />
'''''Jake'''''<br />
|}<br />
<br />
Names in '''''Bold & Italics''''' indicate Staff Coordinators.<br />
<br />
==Spanish Build Instructors Schedule==<br />
{| border="1" fontname="Nimbus Sans" fontsize="12" cellpadding="3" cellspacing="0"<br />
|-<br />
!width="34%" align="center" style="color:white; background-color:black;"|Day<br />
!width="33%" align="center" style="color:white; background-color:black;"|AM<br />
!width="33%" align="center" style="color:white; background-color:black;"|PM<br />
|-<br />
|align="center"|'''TUESDAY'''<br />
|<br />
Carlos<br><br />
|<br />
<br />
|-<br />
|align="center"|'''SATURDAY'''<br />
|<br />
Estela<br><br />
Daisy<br><br />
Daniel<br><br />
|<br />
<br />
|}<br />
<br />
<br />
[[Category:Build]]</div>Alambhttp://wiki.freegeek.org/index.php?title=Build_Instructor_Schedule&diff=64448Build Instructor Schedule2012-10-02T23:04:47Z<p>Alamb: /* Build Instructors Schedule */</p>
<hr />
<div>==Build Instructors Schedule==<br />
{| border="1" fontname="Nimbus Sans" fontsize="12" cellpadding="3" cellspacing="0"<br />
|-<br />
!width="34%" align="center" style="color:white; background-color:black;"|Day<br />
!width="33%" align="center" style="color:white; background-color:black;"|AM<br />
!width="33%" align="center" style="color:white; background-color:black;"|PM<br />
|-<br />
|align="center"|'''TUESDAY'''<br />
|<br />
Kurt<br><br />
Phil<br> <br />
'''''Jake'''''<br />
|<br />
Howard<br><br />
'''''Amelia'''''<br />
|-<br />
|align="center"|'''WEDNESDAY'''<br />
|<br />
Daniel<br/><br />
'''''Ebeth'''''<br />
|<br />
Blaine<br><br />
Nate<br><br />
'''''Amelia'''''<br />
|-<br />
|align="center"|'''THURSDAY'''<br />
|<br />
John<br><br />
'''''Liliana'''''<br />
|<br />
Blaine<br><br />
Jeffrey<br><br />
'''''Amelia'''''<br />
|-<br />
|align="center"|'''FRIDAY'''<br />
|<br />
Tara<br> <br />
Mary<br><br />
'''''Liliana'''''<br />
| <br />
Sam<br> <br />
'''''Lynnae'''''<br />
|-<br />
|align="center"|'''SATURDAY'''<br />
|<br />
Keith<br><br />
Brett<br/> <br />
'''''Amelia'''''<br />
|<br />
Brett<br/><br />
Max<br/><br />
'''''Jake'''''<br />
|}<br />
<br />
Names in '''''Bold & Italics''''' indicate Staff Coordinators.<br />
<br />
==Spanish Build Instructors Schedule==<br />
{| border="1" fontname="Nimbus Sans" fontsize="12" cellpadding="3" cellspacing="0"<br />
|-<br />
!width="34%" align="center" style="color:white; background-color:black;"|Day<br />
!width="33%" align="center" style="color:white; background-color:black;"|AM<br />
!width="33%" align="center" style="color:white; background-color:black;"|PM<br />
|-<br />
|align="center"|'''TUESDAY'''<br />
|<br />
Carlos<br><br />
|<br />
<br />
|-<br />
|align="center"|'''SATURDAY'''<br />
|<br />
Estela<br><br />
Daisy<br><br />
Daniel<br><br />
|<br />
<br />
|}<br />
<br />
<br />
[[Category:Build]]</div>Alambhttp://wiki.freegeek.org/index.php?title=PR&diff=64441PR2012-10-02T20:32:50Z<p>Alamb: /* Blurb about Free Geek */</p>
<hr />
<div>; Standing [[PR]] Committee;<br />
: ''Mission:'' PR Vision Statement (adopted by committee on May xx, 2009)<br />
(Limmerick version)<br />
Figure out what The Geek has to say,<br />
And then say it in a Geeky way.<br />
Spread the word to Joe Shmoe,<br />
To the press and SludgeCo.<br />
And then listen for 'boos' and 'hoorays.'<br />
<br />
(Haiku version)<br />
Discern the message.<br />
Spread the word far, wide and well.<br />
Shut up and listen.<br />
: ''Programs:'' In charge of media outreach & relations, ads & marketing, the main Free Geek website, tabling events and networking with other organizations.<br />
: ''Email:'' pr at freegeek.org<br />
<br />
----<br />
<br />
==Priorities (as established 3/12)==<br />
#Thrift Store<br />
#$ Donations<br />
#Specific classes/events<br />
#Equipment donations<br />
#Ongoing volunteers<br />
#Institutional donors<br />
#Front desk<br />
#Nonprofit partnerships<br />
#Mission-related education<br />
#Day-to-day volunteers<br />
<br />
==Overview==<br />
<br />
PR is a standing staff committee which is responsible for media outreach & relations, ads & marketing, [http://freegeek.org the Free Geek website], and networking with other organizations.<br />
<br />
Check: [[PR Facilitator/Scribe]]<br />
<br />
* The PR Committee meets every Wednesday morning. Generally, alternating Wednesdays are devoted to "working meetings."<br />
<br />
== Running a PR meeting ==<br />
Please see [[Meeting Tips]] for essential habits of good facilitation. Also remember [http://en.wikipedia.org/wiki/SMART_criteria| to use SMART guildlines] to a basic check in on subject matter.<br />
* Preparation<br />
** Check in with members well in advance of the meeting to see if there are any dependencies that are interfering with task completion<br />
* Agenda contents - Should contain:<br />
** Previous commitments and Old business<br />
** New agenda items<br />
** Events and goals radar/timetable<br />
* Agenda management - Agendas should only contain items with specific questions to be answered or with specific work to be delegated. Other items should be discussed out of meeting or moved into a working meeting.<br />
* Assigning work for "working meetings"<br />
<br />
== Blurb about Free Geek ==<br />
<br />
Is this a press blurb? This should be explained if it is going to be here [[User:Luiz|Luiz]] 20:33, 17 October 2009 (UTC) -- ''this should mention hardware grants, internships, education program, thrift store, build, adoption, tech support and recycling...all in the body of the paragraph instead of the mission statement at the top.''<br />
<br />
FREE GEEK is a 501(c)(3) not-for-profit community technology center that recycles technology and provides access to computers, the internet, education and job skills in exchange for community service. We accept donations from the public of most electronic equipment, ranging from systems to printers to stereos. Free Geek does most of this work with volunteers (participation averages around 550-600 active volunteers each month). The volunteers disassemble the donated equipment and test the components, which are either recycled as electronic scrap or incorporated into refurbished systems. These refurbished computers are then loaded with Open Source Software. Free Geek has two symbiotic volunteer programs. The most popular is the Adoption program wherein any individual may contribute 24 hours of volunteering at Free Geek in exchange for a free computer. Alternately, any individual who wishes to learn how to build computers can join the Build Program. Free Geek instructors teach the Build volunteer the process of identifying hardware and assembling systems and, in exchange, the volunteer builds 5 computers for Free Geek and takes the 6th one home. Essentially, the Build volunteers assemble the systems the Adoption volunteers take home, while the Adoption volunteers help receive the incoming donations from the public and disassemble the rejected, obsolete technology. Free Geek is also committed to electronic waste recycling and selects those recycling businesses who engage in environmentally responsible practices to process the obsolete technology we receive. Free Geek is proud of being a democratically-run organization, and use consensus in our meetings.<br />
<br />
==PR Budget==<br />
* Ads<br />
** May $250<br />
** $10/month for other 11 months<br />
** $600 in '''Nov''' for Willamette Week Give Guide<br />
<br />
* Tabling<br />
** $20/month EXCEPT $75 in April for Earth Day <br />
* T-shirts, stickers, and similar merchandise (includes business cards)<br />
** ''We buy t-shirts twice a year'' ~$1500<br />
<br />
* Networking/learning conferences and memberships<br />
** AOR<br />
*** membership: $135/'''yr'''<br />
*** conference in '''June''': $470 (2 people, $235 each) ''' ''(usually free, but we don't know)'' '''<br />
*** mileage to Redmond, OR in '''June''': $150 (under C7)<br />
** <s>International Computer Refurbishing Summit in Toronto</s><br />
** $75 in '''Oct''' Membership in Sustainable Business Network <br />
<br />
* Direct Mail '''Nov''' (TBD)<br />
<br />
* Grant Research<br />
** $175 in '''Dec''' for Oregon Foundation Databook & CD 2009 edition<br />
<br />
* Brochure<br />
** $250 in '''Nov''' 1000 B/W copies of brochure on 28 wt paper--trifolded<br />
<br />
* Front Desk PR <br />
** $125 in '''Oct''' for Banner at Front Desk<br />
** $150 in '''Oct''' 8X10 Prints of Community recipient/volunteer photos & frames <br />
<br />
=== Related Items ===<br />
''(This is for notes that indicate expenses that affect your committee but are actually classified under a different committee.) ''<br />
<br />
* Conferences July $100 oscon (probably goes in HR -> Training and Education)<br />
* $100 for website developer (probably goes in C7 -> Staffing Costs)<br />
* $200/YEAR for mileage to conferences (C7 mileage reimbursement expense)<br />
<br />
==Webadmin==<br />
Check out our web stats! <br />
* [http://www.tump.com/~lmoore/logs/freegeek/ Webhits over the past year]<br />
* [http://www.tump.com/~lmoore/fglog/ Webhits archive]<br />
* [http://www.tump.com/www.freegeek.org-analog/ Webserver stats] (lists which words are searched to find us, operating systems used when browsing the site, etc.)<br />
<br />
==Links==<br />
* [[PR Tasks| Who does what]]<br />
*[[Monitored by Outreach]]<br />
*[[Stats and Testimonials]] - tidbits to support various marketing, advertising, PR materials<br />
*[[Computer Collection Events]] <br />
*[[Conferences]]<br />
*[[Corporate Sponsors]] - cultivating corporate sponsorship for Free Geek programs.<br />
*[[Give Guide]]<br />
*[[Media Liaison]]<br />
*[[Mailings]] - asking for money via letters.<br />
*[[Pickups Intake]]<br />
*[[Presentations/Lectures]]<br />
*[[Tabling]]<br />
*[[T-Shirts]]<br />
*[[Stickers]]<br />
*[[Log of Ads]]<br />
*[[GeekVideo]] - documentation, proliferation, replication... consternation?<br />
*[[Webadmin]]<br />
*[[Ambassador Basics]]<br />
*[[Neighborhood Association]]<br />
*[[Free Geek Slogans]]<br />
<br />
<br />
[[Category: PR]]<br />
[[Category: Standing Committees]]</div>Alambhttp://wiki.freegeek.org/index.php?title=File:Volunteering_for_school_credit_guidelines.odt&diff=64440File:Volunteering for school credit guidelines.odt2012-10-02T19:59:03Z<p>Alamb: uploaded a new version of "File:Volunteering for school credit guidelines.odt"</p>
<hr />
<div>Please hand out this form to people interested in volunteering for high school or college credit.</div>Alambhttp://wiki.freegeek.org/index.php?title=Stakeholder_Feedback&diff=64407Stakeholder Feedback2012-09-28T18:49:27Z<p>Alamb: </p>
<hr />
<div>This page was created to list the questions the website redesign team came up with to find out how our various stakeholders use our website, their needs and preferences for its look, feel and functionality going forward.<br />
<br />
== General Questions ==<br />
* What are your feeling towards Free Geek and what comes to mind when you think about Free Geek?<br />
* How do you generally use and rely on the internet to achieve your goals?<br />
* What items/information do you expect to see on the home page of a website?<br />
* What information on the site did you find most useful?<br />
* What types of information were difficult or were you unable to find?<br />
* What features or pages do you access the most on the current site?<br />
* What type of interactivity are you looking for on a website?<br />
* Can you list some of your likes and dislikes about the current version of the website?<br />
* Does the current site meet your needs and how likely would you be to seek out a competitor's website?<br />
* Have I missed anything or do you have anything to add?<br />
* How often do you use the search function? Where do you want the search bar located on the home page?<br />
<br />
== Stakeholder-Specific Questions ==<br />
'''Employees'''<br />
* As a Free Geek employee, what do you most often use the site for?<br />
* What features or information would you most like to see added/changed on the current site?<br />
<br />
'''Volunteers'''<br />
* Was the Volunteer Info Request form on the current site easy to use and understand?<br />
* Did you get the information that you requested?<br />
* Were the different types of volunteer opportunities adequately described and what you expected?<br />
<br />
'''Hardware Donors'''<br />
* Did the current site accurately describe the types of items that can and cannot be donated?<br />
* Was the donation process described adequately?<br />
* What information/resources would you provide that would make the donation process easier?<br />
<br />
'''Financial Donors'''<br />
* What features would you like to see on the site that would make it easier to make a financial donation to Free Geek?<br />
* Did you find the necessary information required to make the donation process easy and did you feel comfortable making your donation online?<br />
<br />
'''Students'''<br />
* Was the Class Request, Internship question, or Internship application form on the current site easy to use and understand?<br />
* Did you get the information that you requested?<br />
* Was the class schedule easy to find and did it give enough information to accurately describe the offered classes?<br />
<br />
'''Recycling Vendors'''<br />
* Does the information currently on the site give clear and concise guidelines as to what Free Geek looks for in a recycling vendor?<br />
* What information, if any, did you find lacking or missing?<br />
<br />
'''Board Members'''<br />
* Do you feel the current site accurately represents Free Geek and its goals?<br />
* What changes or additions would you like to see made to the site?<br />
* In addition to the annual report, what financial and/or company information would you like to be able to access on the site?<br />
<br />
'''Other Free Geeks'''<br />
* What tips or tricks can you suggest on different ways to maintain the website?<br />
* What features on your site work well and which ones don't work as expected?<br />
* Is there any information/features that you have added or removed from your site due to feedback from visitors of the site?<br />
<br />
'''Other Institutional Partners'''<br />
* What pertinent information about being partnered with Free Geek would you like to see on the site and what information do you currently find most useful?<br />
<br />
<br />
<br />
<br />
<br />
[[Category:2012 Website Redesign Project]]</div>Alambhttp://wiki.freegeek.org/index.php?title=Stakeholder_Feedback&diff=64403Stakeholder Feedback2012-09-28T18:36:08Z<p>Alamb: Created page with "This page was created to list the questions the website redesign team came up with to find out how our various stakeholders use our website, their needs and preferences for its l…"</p>
<hr />
<div>This page was created to list the questions the website redesign team came up with to find out how our various stakeholders use our website, their needs and preferences for its look, feel and functionality going forward.<br />
<br />
== General Questions ==<br />
* What are your feeling towards Free Geek and what comes to mind when you think about Free Geek?<br />
* How do you generally use and rely on the internet to achieve your goals?<br />
* What items/information do you expect to see on the home page of a website?<br />
* What information on the site did you find most useful?<br />
* What types of information were difficult or were you unable to find?<br />
* What features or pages do you access the most on the current site?<br />
* What type of interactivity are you looking for on a website?<br />
* Can you list some of your likes and dislikes about the current version of the website?<br />
* Does the current site meet your needs and how likely would you be to seek out a competitor's website?<br />
* Have I missed anything or do you have anything to add?<br />
* How often do you use the search function? Where do you want the search bar located on the home page?<br />
<br />
== Stakeholder-Specific Questions ==<br />
'''Volunteers'''<br />
* Was the Volunteer Info Request form on the current site easy to use and understand?<br />
* Did you get the information that you requested?<br />
* Were the different types of volunteer opportunities adequately described and what you expected?<br />
<br />
'''Hardware Donors'''<br />
* Did the current site accurately describe the types of items that can and cannot be donated?<br />
* Was the donation process described adequately?<br />
* What information/resources would you provide that would make the donation process easier?<br />
<br />
'''Financial Donors'''<br />
* What features would you like to see on the site that would make it easier to make a financial donation to Free Geek?<br />
* Did you find the necessary information required to make the donation process easy and did you feel comfortable making your donation online?<br />
<br />
'''Students'''<br />
* Was the Class Request, Internship question, or Internship application form on the current site easy to use and understand?<br />
* Did you get the information that you requested?<br />
* Was the class schedule easy to find and did it give enough information to accurately describe the offered classes?<br />
<br />
'''<br />
<br />
<br />
[[Category:2012 Website Redesign Project]]</div>Alambhttp://wiki.freegeek.org/index.php?title=2012_Website_Redesign&diff=644012012 Website Redesign2012-09-28T18:20:16Z<p>Alamb: </p>
<hr />
<div>This page was created to start collecting information for a website redesign, as proposed by the PR Committee. <br />
<br />
== New and Improved Features/Structure ==<br />
* "Free Geek in the Media" page with links to media features, flexible archival settings<br />
* Option whether or not to post new page content in that page's category page feed (e.g. option not to include Media posts in main News feed)<br />
* "Large Donors/Partners" page listing individual donations over a certain amount, institutional and in-kind donors, corporate logos?<br />
* Newsletter sign-up button<br />
* Streaming Twitter/Facebook feed<br />
* Seperate pages for institutional and individual donors<br />
* Bold donate button on front page<br />
* Address and hours on front page (and footer of every page).<br />
* Links to wiki, possibly other outward facing services<br />
* "Digital Tour": Area highlights w/ photos, more expository descriptions<br />
* Integrate Inreach programs (e.g., Star Volunteers, Events, etc)<br />
* Must be mobile-friendly!<br />
* Presence for current certifications<br />
* Incorporate Spanish pages (or...whole separate Spanish website).<br />
* Submenus<br />
* RSS feed<br />
* Photo area (Flickr account link?)<br />
* Header on every page: Logo, Hours/Location/Phone, Link to directions, Social Media Buttons <br />
* Footer on every page: Text Navigation and Search bar<br />
* No Blog looking content, except on community news page<br />
* Full articles on community news page.<br />
* Currents news on Home page with fully flexible posting options<br />
<br />
== Technical/Maintenance ==<br />
* Easy/quick for staff and volunteers to maintain<br />
* Admin: pretty easy to learn to administer, easy to add users and privileges, easy to make new pages, easy to change layout of old pages<br />
* Analytics to view click-throughs to individual posts, and internal navigation between individual pages and posts<br />
* Quick loading for dial-up users<br />
* Limit JavaScript<br />
* More cohesive method/procedure to maintain site<br />
* Ability to integrate with RT<br />
<br />
== Layout/Design ==<br />
* Press area expanded to include links to FG in the news, articles, FG YouTube page, link to reddit?<br />
* Corporate hardware donor and Financial donor thanks page<br />
* Friends/Partners links<br />
* Links to other Free Geeks and similar organizations<br />
* Harmful stuff in computers page<br />
* Photo area<br />
* Map images with links - Google, Trimet, Bicycle<br />
* More prominent hours, location, phone number on front page<br />
* Little to no scroll on front page<br />
* Keep current Logo (Remove pictures and just use the Free Geek logo), Choose colors/fonts that flow nicely from the logo.<br />
* Muted colors, New Scheme (Green ?), Fading colors/gradients<br />
* More information in other languages, primarily Spanish (Omar can help with this)<br />
<br />
== Branding ==<br />
* Reuse/Recycling<br />
* Community<br />
* Environmentalism<br />
* Casual<br />
* Empowered<br />
* Open Source<br />
* Global , diverse, accessible<br />
* Creative<br />
* Comfortable with change<br />
* Sustainable/Green<br />
* Community Resource<br />
* Fun<br />
* Cooperative Learning<br />
<br />
== Current Website Issues ==<br />
* Busy (Make new site Clean)<br />
* Dated (Make new site Modern)<br />
* Constrained (Make new site Flexible)<br />
* Intelligent and fun (writing style)<br />
* Some elements are easy to use (Build on this)<br />
<br />
[[Category:2012 Website Redesign Project]]</div>Alambhttp://wiki.freegeek.org/index.php?title=2012_Website_Redesign&diff=644002012 Website Redesign2012-09-28T18:10:42Z<p>Alamb: </p>
<hr />
<div>This page was created to start collecting information for a website redesign, as proposed by the PR Committee. <br />
<br />
== New and Improved Features ==<br />
*"Free Geek in the Media" page with links to media features, flexible archival settings<br />
*Option whether or not to post new page content in that page's category page feed (e.g. option not to include Media posts in main News feed)<br />
*"Large Donors/Partners" page listing individual donations over a certain amount, institutional and in-kind donors, corporate logos?<br />
*Newsletter sign-up button<br />
*Streaming Twitter/Facebook feed<br />
*Seperate pages for institutional and individual donors<br />
*Bold donate button on front page<br />
*Address and hours on front page (and footer of every page).<br />
*Links to wiki, possibly other outward facing services<br />
*"Digital Tour": Area highlights w/ photos, more expository descriptions<br />
*Integrate Inreach programs (e.g., Star Volunteers, Events, etc)<br />
*Must be mobile-friendly!<br />
*Presence for current certifications<br />
<br />
*Incorporate Spanish pages (or...whole separate Spanish website).<br />
<br />
'''Technical/Maintenance'''<br />
* Easy/quick for staff and volunteers to maintain<br />
* Admin: pretty easy to learn to administer, easy to add users and privileges, easy to make new pages, easy to change layout of old pages<br />
* Analytics to view click-throughs to individual posts, and internal navigation between individual pages and posts<br />
* Quick loading for dial-up users<br />
* Limit JavaScript<br />
* More cohesive method/procedure to maintain site<br />
* Ability to integrate with RT<br />
<br />
<br />
'''Structure/Features'''<br />
* Submenus<br />
* RSS feed<br />
* Photo area (Flickr account link?)<br />
* Header on every page: Logo, Hours/Location/Phone, Link to directions, Social Media Buttons <br />
* Footer on every page: Text Navigation and Search bar<br />
* No Blog looking content, except on community news page<br />
* Full articles on community news page.<br />
* Currents news on Home page with fully flexible posting options<br />
<br />
<br />
'''Layout/Design'''<br />
* Press area expanded to include links to FG in the news, articles, FG YouTube page, link to reddit?<br />
* Corporate hardware donor and Financial donor thanks page<br />
* Friends/Partners links<br />
* Links to other Free Geeks and similar organizations<br />
* Harmful stuff in computers page<br />
* Photo area<br />
* Map images with links - Google, Trimet, Bicycle<br />
* More prominent hours, location, phone number on front page<br />
* Little to no scroll on front page<br />
* More information in other languages, primarily Spanish (Omar can help with this)<br />
<br />
<br />
'''Branding'''<br />
* Reuse/Recycling<br />
* Community<br />
* Environmentalism<br />
* Casual<br />
* Empowered<br />
* Open Source<br />
* Global , diverse, accessible<br />
* Creative<br />
* Comfortable with change<br />
* Sustainable/Green<br />
* Community Resource<br />
* Fun<br />
* Cooperative Learning<br />
<br />
<br />
'''Current Website'''<br />
* Busy (Make new site Clean)<br />
* Dated (Make new site Modern)<br />
* Constrained (Make new site Flexible)<br />
* Intelligent and fun (writing style)<br />
* Some elements are easy to use (Build on this)<br />
<br />
<br />
<br />
*Wants:*<br />
<br />
· Simple Front Page (very little scrolling, if any)<br />
<br />
· Keep current Logo (Remove pictures and just use the Free Geek<br />
logo), Choose colors that flow nicely from the logo.<br />
<br />
· Muted colors<br />
<br />
· New Scheme (Green ?)<br />
<br />
· Fading colors/gradients<br />
<br />
[[Category:2012 Website Redesign Project]]</div>Alambhttp://wiki.freegeek.org/index.php?title=Category:2012_Website_Redesign_Project&diff=64399Category:2012 Website Redesign Project2012-09-28T18:09:49Z<p>Alamb: Created page with "Category:Website"</p>
<hr />
<div>[[Category:Website]]</div>Alambhttp://wiki.freegeek.org/index.php?title=2012_Website_Redesign&diff=643982012 Website Redesign2012-09-28T18:01:56Z<p>Alamb: </p>
<hr />
<div>This page was created to start collecting information for a website redesign, as proposed by the PR Committee. <br />
<br />
== New and Improved Features ==<br />
*"Free Geek in the Media" page with links to media features, flexible archival settings<br />
*Option whether or not to post new page content in that page's category page feed (e.g. option not to include Media posts in main News feed)<br />
*"Large Donors/Partners" page listing individual donations over a certain amount, institutional and in-kind donors, corporate logos?<br />
*Newsletter sign-up button<br />
*Streaming Twitter/Facebook feed<br />
*Seperate pages for institutional and individual donors<br />
*Bold donate button on front page<br />
*Address and hours on front page (and footer of every page).<br />
*Links to wiki, possibly other outward facing services<br />
*"Digital Tour": Area highlights w/ photos, more expository descriptions<br />
*Integrate Inreach programs (e.g., Star Volunteers, Events, etc)<br />
*Must be mobile-friendly!<br />
*Presence for current certifications<br />
<br />
*Incorporate Spanish pages (or...whole separate Spanish website).<br />
<br />
'''Technical/Maintenance'''<br />
* Easy/quick for staff and volunteers to maintain<br />
* Admin: pretty easy to learn to administer, easy to add users and privileges, easy to make new pages, easy to change layout of old pages<br />
* Analytics to view click-throughs to individual posts, and internal navigation between individual pages and posts<br />
* Quick loading for dial-up users<br />
* Limit JavaScript<br />
* More cohesive method/procedure to maintain site<br />
* Ability to integrate with RT<br />
<br />
<br />
'''Structure/Features'''<br />
* Submenus<br />
* RSS feed<br />
* Photo area (Flickr account link?)<br />
* Header on every page: Logo, Hours/Location/Phone, Link to directions, Social Media Buttons <br />
* Footer on every page: Text Navigation and Search bar<br />
* No Blog looking content, except on community news page<br />
* Full articles on community news page.<br />
* Currents news on Home page with fully flexible posting options<br />
<br />
<br />
'''Layout/Design'''<br />
* Press area expanded to include links to FG in the news, articles, FG YouTube page, link to reddit?<br />
* Corporate hardware donor and Financial donor thanks page<br />
* Friends/Partners links<br />
* Links to other Free Geeks and similar organizations<br />
* Harmful stuff in computers page<br />
* Photo area<br />
* Map images with links - Google, Trimet, Bicycle<br />
* More prominent hours, location, phone number on front page<br />
* Little to no scroll on front page<br />
* More information in other languages, primarily Spanish (Omar can help with this)<br />
<br />
<br />
'''Branding'''<br />
* Reuse/Recycling<br />
* Community<br />
* Environmentalism<br />
* Casual<br />
* Empowered<br />
* Open Source<br />
* Global , diverse, accessible<br />
* Creative<br />
* Comfortable with change<br />
* Sustainable/Green<br />
* Community Resource<br />
* Fun<br />
* Cooperative Learning<br />
<br />
<br />
'''Current Website'''<br />
* Busy (Make new site Clean)<br />
* Dated (Make new site Modern)<br />
* Constrained (Make new site Flexible)<br />
* Intelligent and fun (writing style)<br />
* Some elements are easy to use (Build on this)<br />
<br />
<br />
<br />
*Wants:*<br />
<br />
· Simple Front Page (very little scrolling, if any)<br />
<br />
· Keep current Logo (Remove pictures and just use the Free Geek<br />
logo), Choose colors that flow nicely from the logo.<br />
<br />
· Muted colors<br />
<br />
· New Scheme (Green ?)<br />
<br />
· Fading colors/gradients<br />
<br />
[[Category:Website]]</div>Alambhttp://wiki.freegeek.org/index.php?title=2012_Website_Redesign&diff=643972012 Website Redesign2012-09-28T18:00:13Z<p>Alamb: </p>
<hr />
<div>This page was created to start collecting information for a website redesign, as proposed by the PR Committee. <br />
<br />
== New and Improved Features ==<br />
*"Free Geek in the Media" page with links to media features, flexible archival settings<br />
*Option whether or not to post new page content in that page's category page feed (e.g. option not to include Media posts in main News feed)<br />
*"Large Donors/Partners" page listing individual donations over a certain amount, institutional and in-kind donors, corporate logos?<br />
*Newsletter sign-up button<br />
*Streaming Twitter/Facebook feed<br />
*Seperate pages for institutional and individual donors<br />
*Bold donate button on front page<br />
*Address and hours on front page (and footer of every page).<br />
*Links to wiki, possibly other outward facing services<br />
*"Digital Tour": Area highlights w/ photos, more expository descriptions<br />
*Integrate Inreach programs (e.g., Star Volunteers, Events, etc)<br />
*Must be mobile-friendly!<br />
*Presence for current certifications<br />
<br />
*Incorporate Spanish pages (or...whole separate Spanish website).<br />
<br />
'''Technical/Maintenance'''<br />
* Easy/quick for staff and volunteers to maintain<br />
* Admin: pretty easy to learn to administer, easy to add users and privileges, easy to make new pages, easy to change layout of old pages<br />
* Analytics to view click-throughs to individual posts, and internal navigation between individual pages and posts<br />
* Quick loading for dial-up users<br />
* Limit JavaScript<br />
* More cohesive method/procedure to maintain site<br />
* Ability to integrate with RT<br />
<br />
<br />
'''Structure/Features'''<br />
* Submenus<br />
* RSS feed<br />
* Photo area (Flickr account link?)<br />
* Header on every page: Logo, Hours/Location/Phone, Link to directions, Social Media Buttons <br />
* Footer on every page: Text Navigation and Search bar<br />
* No Blog looking content, except on community news page<br />
* Full articles on community news page.<br />
* Currents news on Home page with fully flexible posting options<br />
<br />
<br />
'''Layout/Design'''<br />
* Press area expanded to include links to FG in the news, articles, FG YouTube page, link to reddit?<br />
* Corporate hardware donor and Financial donor thanks page<br />
* Friends/Partners links<br />
* Links to other Free Geeks and similar organizations<br />
* Harmful stuff in computers page<br />
* Photo area<br />
* Map images with links - Google, Trimet, Bicycle<br />
* More prominent hours, location, phone number on front page<br />
* Little to no scroll on front page<br />
* More information in other languages, primarily Spanish (Omar can help with this)<br />
<br />
<br />
'''Branding'''<br />
* Reuse/Recycling<br />
* Community<br />
* Environmentalism<br />
* Casual<br />
* Empowered<br />
* Open Source<br />
* Global , diverse, accessible<br />
* Creative<br />
* Comfortable with change<br />
* Sustainable/Green<br />
* Community Resource<br />
* Fun<br />
* Cooperative Learning<br />
<br />
<br />
'''Current Website'''<br />
* Busy (Make new site Clean)<br />
* Dated (Make new site Modern)<br />
* Constrained (Make new site Flexible)<br />
* Intelligent and fun (writing style)<br />
* Some elements are easy to use (Build on this)<br />
<br />
<br />
<br />
*Wants:*<br />
<br />
· Simple Front Page (very little scrolling, if any)<br />
<br />
· Keep current Logo (Remove pictures and just use the Free Geek<br />
logo), Choose colors that flow nicely from the logo.<br />
<br />
· Muted colors<br />
<br />
· New Scheme (Green ?)<br />
<br />
· Fading colors/gradients<br />
<br />
<br />
[[Category: 2012 Website Redesign Project]]<br />
<br />
[[Category:Website]]</div>Alambhttp://wiki.freegeek.org/index.php?title=2012_Website_Redesign&diff=643822012 Website Redesign2012-09-26T20:35:21Z<p>Alamb: /* New and Improved Features */</p>
<hr />
<div>This page was created to start collecting information for a website redesign, as proposed by the PR Committee. <br />
<br />
== New and Improved Features ==<br />
*"Free Geek in the Media" page with links to media features, flexible archival settings<br />
*Option whether or not to post new page content in that page's category page feed (e.g. option not to include Media posts in main News feed)<br />
*"Large Donors/Partners" page listing individual donations over a certain amount, institutional and in-kind donors, corporate logos?<br />
*Newsletter sign-up button<br />
*Streaming Twitter/Facebook feed<br />
*Seperate pages for institutional and individual donors<br />
*Bold donate button on front page<br />
*Address and hours on front page (and footer of every page).<br />
*Links to wiki, possibly other outward facing services<br />
*"Digital Tour": Area highlights w/ photos, more expository descriptions<br />
*Integrate Inreach programs (e.g., Star Volunteers, Events, etc)<br />
*Must be mobile-friendly!<br />
*Presence for current certifications<br />
<br />
*Incorporate Spanish pages (or...whole separate Spanish website).<br />
<br />
'''Technical/Maintenance'''<br />
* Easy/quick for staff and volunteers to maintain<br />
* Admin: pretty easy to learn to administer, easy to add users and privileges, easy to make new pages, easy to change layout of old pages<br />
* Analytics to view click-throughs to individual posts, and internal navigation between individual pages and posts<br />
* Quick loading for dial-up users<br />
* Limit JavaScript<br />
* More cohesive method/procedure to maintain site<br />
* Ability to integrate with RT<br />
<br />
<br />
'''Structure/Features'''<br />
* Submenus<br />
* RSS feed<br />
* Photo area (Flickr account link?)<br />
* Header on every page: Logo, Hours/Location/Phone, Link to directions, Social Media Buttons <br />
* Footer on every page: Text Navigation and Search bar<br />
* No Blog looking content, except on community news page<br />
* Full articles on community news page.<br />
* Currents news on Home page with fully flexible posting options<br />
<br />
<br />
'''Layout/Design'''<br />
* Press area expanded to include links to FG in the news, articles, FG YouTube page, link to reddit?<br />
* Corporate hardware donor and Financial donor thanks page<br />
* Friends/Partners links<br />
* Links to other Free Geeks and similar organizations<br />
* Harmful stuff in computers page<br />
* Photo area<br />
* Map images with links - Google, Trimet, Bicycle<br />
* More prominent hours, location, phone number on front page<br />
* Little to no scroll on front page<br />
* More information in other languages, primarily Spanish (Omar can help with this)<br />
<br />
<br />
'''Branding'''<br />
* Reuse/Recycling<br />
* Community<br />
* Environmentalism<br />
* Casual<br />
* Empowered<br />
* Open Source<br />
* Global , diverse, accessible<br />
* Creative<br />
* Comfortable with change<br />
* Sustainable/Green<br />
* Community Resource<br />
* Fun<br />
* Cooperative Learning<br />
<br />
<br />
'''Current Website'''<br />
* Busy (Make new site Clean)<br />
* Dated (Make new site Modern)<br />
* Constrained (Make new site Flexible)<br />
* Intelligent and fun (writing style)<br />
* Some elements are easy to use (Build on this)<br />
<br />
<br />
<br />
*Wants:*<br />
<br />
· Simple Front Page (very little scrolling, if any)<br />
<br />
· Keep current Logo (Remove pictures and just use the Free Geek<br />
logo), Choose colors that flow nicely from the logo.<br />
<br />
· Muted colors<br />
<br />
· New Scheme (Green ?)<br />
<br />
· Fading colors/gradients<br />
<br />
<br />
<br />
[[Category:Website]]</div>Alambhttp://wiki.freegeek.org/index.php?title=General_Problems_-_Fixed!&diff=64375General Problems - Fixed!2012-09-25T23:37:04Z<p>Alamb: </p>
<hr />
<div>{| border="1" fontname="Nimbus Sans" fontsize="12" cellpadding="5" cellspacing="1"<br />
|-<br />
|style="text-align:center" width=25% |'''Bad Battery<br>"Your battery may be broken"'''<br />
|style="text-align:left"|<br />
# From the Desktop, press '''Alt+F2''' to bring up Ubuntu's ''run prompt'',<br />
# Enter ''gconf-editor'' and click '''Run''',<br />
# In the left pane, navigate to '''apps >> gnome-power-manager >> notify''' and deselect '''low_capacity'''<br />
|-<br />
!"The system will not complete a reboot. It just hangs on the Ubuntu screen. Shutdown works fine."<br />
||<br />
GRUB is the boot loader package responsible for starting up and shutting down your computer. Try editing the following GRUB configuration file and see if it makes a difference. HINT: if you hit the Esc key while your computer is booting up or shutting down during the Ubuntu splash screen, you may get more text information about what your computer is doing. If you're not comfortable working in a terminal, grab some help on this one.<br />
<br />
In a terminal, type:<br />
<br />
sudo gedit /etc/default/grub<br />
<br />
Find the line <br />
<br />
GRUB_CMDLINE_LINUX_DEFAULT="splash quiet"<br />
<br />
and edit it to read:<br />
<br />
GRUB_CMDLINE_LINUX_DEFAULT="reboot=bios splash quiet"<br />
<br />
Save and exit. In a terminal, type: <br />
<br />
sudo update-grub<br />
<br />
Shut down the computer, power on again and try rebooting. Is fixed, no?<br />
|}<br />
<br />
<br />
[[Category:Laptops]][[Category:Tech support]]</div>Alambhttp://wiki.freegeek.org/index.php?title=Build_Instructor_Trainings&diff=64320Build Instructor Trainings2012-09-20T19:59:55Z<p>Alamb: /* 2011 */</p>
<hr />
<div>This page is designed to be an easily accessible archive for past Build Instructor Trainings.<br />
=2011=<br />
[[BIT 110125|25 Jan 2011]]<br />
<br />
[[BIT 110728|28 July 2011]]<br />
<br />
[[BIT 120215|15 Feb 2012]]<br />
<br />
[[BIT 120614|14 June 2012]]<br />
<br />
[[Category: Build]]</div>Alambhttp://wiki.freegeek.org/index.php?title=BIT_120614&diff=64319BIT 1206142012-09-20T19:58:06Z<p>Alamb: </p>
<hr />
<div>Build Instructor Training 6/14/12<br />
<br />
==In attendance==<br />
<br />
Steven, Sean, Jason Owen, Max, Gerardo, Gordon, Sam, Blaine, Keith, Allan, Estela, Daisy, Kevin, Kurt, Nate, Brett <br />
<br />
Facilitating: Amelia<br />
<br />
Scribing: Liliana<br />
<br />
Place: Free Geek Meeting Room<br />
<br />
==Introductions==<br />
<br />
Instructors newly trained since February: Kevin & Sam. Welcome to the team guys!<br />
<br />
==Review of last instructor training and commits, February 2012==<br />
<br />
http://wiki.freegeek.org/index.php/BIT_120215 Build Category, see "Build Instructor Trainings"<br />
<br />
* Showed instructors where minutes are located on the wiki<br />
* Reviewed Laptop QC Sign-Off process and common cosmetic issues with systems sent to the store<br />
* Disbursement Procedures (please be conscientious about classes in session when sourcing take-home gizmos from the classroom)<br />
<br />
Amelia's Commit/Project follow-ups<br />
<br />
* Wiki page for instructional modules has been created, located here: http://wiki.freegeek.org/index.php/Category:Build_Program_Education_Modules<br />
* Tech Support Warranty flier is being completed and when it's finished, should be included w/ disbursement materials.<br />
* Documentation projects: Kurt created a module on Linux installs, Amelia will follow up with Mary on visual appendix and with Jeffrey on UI customization<br />
<br />
==Transitioning Build Instructor Positions into Internships==<br />
<br />
* Typically at Free Geek: Interns have a clearly defined start and end date and work more closely with their supervisor.<br />
* Build hasn't worked that way, but will be moving towards that. Internships will have a set time and will do applications online, and interview with Amelia (or someone else). Any current volunteer who has been working with us in this less structured format will be "grandfathered" in and won't have to worry about re-applying. Just remember to give us a heads up when you decide to leave.<br />
* Interns need to sign a confidentiality form for setting expectations re: data security as well as basic behavioral guidelines (Forms sent around the room)<br />
* Q&A session:<br />
** What about TARDIS? This will be a separate process. TARDIS is not included in this contract because not every instructor has a T-Key.<br />
** Will there be a minimum time limit? Yes. Minimum 3 months.<br />
** Will there be a chance for volunteers to shadow before starting? Perhaps. We want to make sure people are okay in the position before signing away the next 3 months and minimize their risk of committing to a position that won't be a good fit for them.<br />
<br />
==Build procedures review/orientation==<br />
<br />
'''Clearing Out Expired Builds-in-progress'''<br />
* Hold in-progress Labels are now color-coded (Thanks Jake!) and the colors-by-month are listed on the wiki at the "Hold In-Progress Color Code Guide" <br />
page on the wiki. (The Hold labels are on Dead Trees)<br />
*At the beginning of each month, please go through the stored system to remove computers labeled with the color for the month BEFORE last. (EX: <br />
on Nov. 1, pull all systems marked with Sept's color)<br />
<br />
'''Impending Checklist Updates'''<br />
* CD-RW burn instructions will include the note to, where possible, un-check "fast blank." This eliminates many of the disc mounting issues we often see.<br />
* Instruction about checking for duplicate ports needs to be clarified.<br />
* Note to disable Quick Boot will be changed to disable Silent Boot.<br />
* Basiccheck could include note in sound section to repeat test for all sound ports.<br />
<br />
'''Introduced Plans for Spec Upgrade/Distro Switchover'''<br />
* The new Linux distribution will come out in the next 3 months at the latest. The distro hasn't been picked yet. If you're curious about how the distro project is progressing, search the wiki under "Category:Distro"<br />
* Incorporating the new distro into our procedures will require many updates to our processes and documentation. Staff will likely ask Build Instructors to help with this process via proofreading and user testing.<br />
* New specs: We're re-evaluating the process for evaluating incoming systems to account for more factors, and will be raising Freekbox specs in the process. We're aiming to jump to 64-bit OS and possibly giving out dual core systems as FreekBoxen at some point in the next few months.<br />
<br />
'''Announcements'''<br />
* Ben Koenig will be teaching a class called Linux Playground, at Free Geek on Thursday June 28, 3-4:30pm.<br />
* Ubuntu Bug Squashing Party, Saturday, June 16, 10am-6pm 4th Ave Building, Room FAB86-01 (Basement)<br />
* Free Geek Volunteer Appreciation BBQ! Saturday, June 21 3pm-7pm. We're gonna have a jug band!<br />
* OSCON (Open Source Convention) is happening July 16-20, Free Geek will be tabling July 17-19 and we're looking for enthusiastic volunteers to table with us. Contact Amelia to sign up for a shift!<br />
<br />
==Commits/Projects==<br />
* Amelia will instate checklist updates<br />
* Standing offer to give instructors wiki accounts and train on wiki editing if anyone wants to share their knowledge on a Build-related educational topic. Contact Amelia to set this up.</div>Alambhttp://wiki.freegeek.org/index.php?title=BIT_120614&diff=64318BIT 1206142012-09-20T19:57:13Z<p>Alamb: </p>
<hr />
<div>Build Instructor Training 6/14/12<br />
<br />
==In attendance==<br />
<br />
Steven, Sean, Jason Owen, Max, Gerardo, Gordon, Sam, Blaine, Keith, Allan, Estela, Daisy, Kevin, Kurt, Nate, Brett <br />
<br />
Facilitating: Amelia<br />
<br />
Scribing: Liliana<br />
<br />
Place: Free Geek Meeting Room<br />
<br />
==Introductions==<br />
<br />
Instructors newly trained since February: Kevin & Sam. Welcome to the team guys!<br />
<br />
==Review of last instructor training and commits, February 2012==<br />
<br />
http://wiki.freegeek.org/index.php/BIT_120215 Build Category, see "Build Instructor Trainings"<br />
<br />
* Showed instructors where minutes are located on the wiki<br />
* Reviewed Laptop QC Sign-Off process and common cosmetic issues with systems sent to the store<br />
* Disbursement Procedures (please be conscientious about classes in session when sourcing take-home gizmos from the classroom)<br />
<br />
Amelia's Commit/Project follow-ups<br />
<br />
* Wiki page for instructional modules has been created, located here: http://wiki.freegeek.org/index.php/Category:Build_Program_Education_Modules<br />
* Tech Support Warranty flier is being completed and when it's finished, should be included w/ disbursement materials.<br />
* Documentation projects: Kurt created a module on Linux installs, Amelia will follow up with Mary on visual appendix and with Jeffrey on UI customization<br />
<br />
==Transitioning Build Instructor Positions into Internships==<br />
<br />
* Typically at Free Geek: Interns have a clearly defined start and end date and work more closely with their supervisor.<br />
* Build hasn't worked that way, but will be moving towards that. Internships will have a set time and will do applications online, and interview with Amelia (or someone else). Any current volunteer who has been working with us in this less structured format will be "grandfathered" in and won't have to worry about re-applying. Just remember to give us a heads up when you decide to leave.<br />
* Interns need to sign a confidentiality form for setting expectations re: data security as well as basic behavioral guidelines (Forms sent around the room)<br />
* Q&A session:<br />
** What about TARDIS? This will be a separate process. TARDIS is not included in this contract because not every instructor has a T-Key.<br />
** Will there be a minimum time limit? Yes. Minimum 3 months.<br />
** Will there be a chance for volunteers to shadow before starting? Perhaps. We want to make sure people are okay in the position before signing away the next 3 months and minimize their risk of committing to a position that won't be a good fit for them.<br />
<br />
==Build procedures review/orientation==<br />
<br />
'''Clearing Out Expired Builds-in-progress'''<br />
* Hold in-progress Labels are now color-coded (Thanks Jake!) and the colors-by-month are listed on the wiki at the "Hold In-Progress Color Code Guide" <br />
page on the wiki. (The Hold labels are on Dead Trees)<br />
*At the beginning of each month, please go through the stored system to remove computers labeled with the color for the month BEFORE last. (EX: <br />
on Nov. 1, pull all systems marked with Sept's color)<br />
<br />
'''Impending Checklist Updates'''<br />
* CD-RW burn instructions will include the note to, where possible, un-check "fast blank." This eliminates many of the disc mounting issues we often see.<br />
* Instruction about checking for duplicate ports needs to be clarified.<br />
* Note to disable Quick Boot will be changed to disable Silent Boot.<br />
* Basiccheck could include note in sound section to repeat test for all sound ports.<br />
<br />
'''Introduced Plans for Spec Upgrade/Distro Switchover'''<br />
* The new Linux distribution will come out in the next 3 months at the latest. The distro hasn't been picked yet. If you're curious about how the distro project is progressing, search the wiki under "Category:Distro"<br />
* Incorporating the new distro into our procedures will require many updates to our processes and documentation. Staff will likely ask Build Instructors to help with this process via proofreading and user testing.<br />
* New specs: We're re-evaluating the process for evaluating incoming systems to account for more factors, and will be raising Freekbox specs in the process. We're aiming to jump to 64-bit OS and possibly giving out dual core systems as FreekBoxen at some point in the next few months.<br />
<br />
'''Announcements'''<br />
* Ben Koenig will be teaching a class called Linux Playground, at Free Geek on Thursday June 28, 3-4:30pm.<br />
* Ubuntu Bug Squashing Party, Saturday, June 16, 10am-6pm 4th Ave Building, Room FAB86-01 (Basement)<br />
* Free Geek Volunteer Appreciation BBQ! Saturday, June 21 3pm-7pm. We're gonna have a jug band!<br />
* OSCON (Open Source Convention) is happening July 16-20, Free Geek will be tabling July 17-19 and we're looking for enthusiastic volunteers to table with us. Contact Amelia to sign up for a shift!<br />
<br />
==Commits/Projects==<br />
* Amelia will instate checklist updates<br />
* Standing offer to give instructors wiki accounts and train on wiki editing if anyone wants to share their knowledge on a Build-related educational topic. Contact Amelia to set this up.<br />
<br />
[[Category: Build]]</div>Alambhttp://wiki.freegeek.org/index.php?title=Build_Instructor_Trainings&diff=64317Build Instructor Trainings2012-09-20T19:56:00Z<p>Alamb: /* 2011 */</p>
<hr />
<div>This page is designed to be an easily accessible archive for past Build Instructor Trainings.<br />
=2011=<br />
[[BIT 110125|25 Jan 2011]]<br />
<br />
[[BIT 110728|28 July 2011]]<br />
<br />
[[BIT 120215|15 Feb 2012]]<br />
<br />
[[BIT 120614|14 June 2012<br />
<br />
[[Category: Build]]</div>Alambhttp://wiki.freegeek.org/index.php?title=Build_Instructor_Guide&diff=64305Build Instructor Guide2012-09-19T23:23:34Z<p>Alamb: /* Howto Checkout QCed Boxen */</p>
<hr />
<div>==Buildteacher duties==<br />
<br />
===Before the shift begins:===<br />
*Check the database (accessed by typing "data" in the web browser address bar of any networked computer inside Free Geek) to see who's expected and how many slots are open. There are usually walk-ins, and you should have some idea of how many slots are available.<br />
*Check the whiteboard for today's special instructions. Also check in with the staff Reuse Program Coordinator for any updates.<br />
*Make sure supplies are available:<br />
*# RAM: Replenish supplies from the Tardis.<br />
*# Hard drives: See what size hard drives will be needed for the build shift and get the appropriately sized wiped drives from the Tardis. Do imaging throughout the session as you get a chance, mark imaged drives with a red marker dot, place Freekbox and Regulars drives in the hard drive boxes for builders, and keep High-End drives either at the imaging station or in the Tardis.<br />
*# Optical Drives: Look over the optical drives and try to organize their boxes if necessary.<br />
<br />
===During the shift:===<br />
* Greet people as they arrive, get their name, introduce yourself as their instructor and identify your fellow build instructor(s) and staff. <br />
* If a person is new to build, make sure they have already gone through Hardware Identification and System Evaluation by looking at their volunteer profile in the database, or confirming with a System Eval instructor. If not, direct them to the System Eval instructor.<br />
* Persons starting their first QC should, if at all possible, start with a very ordinary box that is unlikely to have interesting problems. We don't want total puzzlement to be the student's first experience with build.<br />
* When graduating a volunteer from QC to assembly, consider whether the builder is comfortable moving on and has the skills to start assembling. Also consider what Free Geek's needs are in terms of QC vs. Assembly.<br />
* Volunteers who have finished their QC's need to be orientated to the Build assembly process (refer to the Assembly Orientation Checklist, hanging on the wall between the research stations, for a complete guide.)<br />
* During the session, keep an eye out for people, especially new ones, who look lost or troubled. Help gently. Try to make sure that people are going through the Checklists and following proper procedure.<br />
* Make sure to show builders how to problem solve instead of just fixing issues for them. <br />
* Let builders know if you are leaving the buildroom and always encourage them to turn to their neighbors for help. <br />
* Remember that computer knowledge does not equal intelligence. Treat '''everyone''' with respect and realize that builders will have different learning styles.<br />
* Image drives throughout the shift to keep up with hard drive demand.<br />
<br />
===At the end of the shift:===<br />
* Announce when the shift is close to being over and ask builders to leave time for cleanup before the next shift arrives or before we close. It is also a good idea to remind people to log their hours on the way out.<br />
* Start cleaning up what the builders have missed. This includes putting tools and supplies away, bundling keyboards and mice at each station, bringing dishes to the kitchen, and throwing stickers and other trash away. <br />
* If you are the Instructor for the afternoon shift, remember to turn off the printer, all power supplies and fans. Make sure that there are no lights left on any monitors or speakers (except for the server station).<br />
<br />
==Howto Orient New Builders==<br />
# '''Welcome''' the Builder, introduce yourself and ask their name. <br />
# Give them a quick '''tour''' of the Build room, pointing out important things like the QC shelves, spec sheets, white board, tools/hardware locations.<br />
# Explain to them '''the Build process'''. i.e., starting to QC and then moving on to assembly. <br />
#* In QC, they are using the checklist to make sure that the computer is '''within spec''', that the hardware and software are '''functional'''. <br />
# Have the Builder grab a checklist. Ask them to read through the introductory section. <br />
#* This may be a good time to make a comparison to System Eval: “When you were in System Eval you used flow charts, while here in Build you'll use checklists.<br />
#* Explain '''useful terms''' like “spec sheet” and “printme.” <br />
# Explain that they should go through the checklist as best they can and then feel free to '''use their resources''' to problem-solve.<br />
#* Point out resources, such as the volunteer next to them, Google, the wiki, help.ubuntu.com, the research stations and the Build instructors. <br />
# '''Remind them to take it slow and that they're here to learn.'''<br />
# Have fun!<br />
<br />
==Howto Checkout QCed Boxen== <br />
* Ask the builder how things went.<br />
* Make sure all of the slots and bays are covered.<br />
* Physically check that the case is secure opening up the case if necessary. This includes the following steps:<br />
** Press on the power supply, slot covers, hard drive enclosure, etc. to make sure they don't move. <br />
** Do the "shake test" to make sure there are no screws rolling around in the case.<br />
** Check for and secure any loose cables or other components that might impede functioning of the fans.<br />
* Check the box over carefully for cosmetics. ALL sticky residue and grime must be removed!<br />
* Make sure the following stickers are removed:<br />
** Identifications of previous ownership<br />
** Contact information for original tech support provider<br />
** Microsoft COAs or windows stickers<br />
** Hardware branding stickers listing any components not contained in the refurbished system<br />
* When checking specs, please pay close attention to the optical drives and make sure the Intel 82845 graphic chipset is not being used.<br />
* Make sure that everything necessary is included in the notes section of the printme:<br />
** Anything non-functional (troubleshoot and fix if possible!)<br />
** Anything unusual (e.g. no PS2 ports)<br />
** Anything untested (e.g. Card Reader, HDMI, etc.)<br />
** Any physical damage <br />
* If there are 2 sound or video ports, make sure the non-functioning one is covered with electrical tape or the official plastic covers.<br />
* If you haven't seen it boot up without user intervention, check this by rebooting the system.<br />
* Be sure there is a Free Geek sticker on front and system ID# sticker on back.<br />
* Thank the builder and, for first-timers, show them how to affix the printme and where to take the finished system.<br />
<br />
==Howto Checkout Laptop QCs==<br />
# Visually inspect the exterior of the case:<br />
#* Are there any asset tags/Microsoft stickers? Advise the Builder to remove them if so.<br />
#* Is the case fully assembled? Screws tightened?<br />
#* Is there any cosmetic damage? (Take note and confirm it has been recorded in the Printme)<br />
#* Is there an FG-PDX/Uncovered sticker? (Take note and confirm it has been recorded in the Printme)<br />
#* Are there Free Geek, GNU/Linux, and login stickers?<br />
# Confirm that wireless works:<br />
#* Disconnect or disable the ethernet controller, and try to browse to a webpage<br />
# Inspect the Printme:<br />
#* Confirm the system is Covered/Uncovered/FG-PDX.<br />
#* Confirm that the battery test has been run and is included in the Gizmo Info section (before notes).<br />
#* Check that only one storage device is installed (e.g., see if there's any mention of a Compact Flash or SD card in addition to the Hard Drive).<br />
#* Check the notes on the PrintMe:<br />
#** Internal/External Wireless?<br />
#** Wifi switch/soft key (e.g., Fn+F5)?<br />
#** Is cosmetic damage mentioned?<br />
#** BIOS key?<br />
#** Ask the builder to explain anything else.<br />
# Reboot the system<br />
#* Confirm it can boot without error/user input.<br />
# Sign-off on the system:<br />
#* Initial the physical Printme and sign off in the FGDB,<br />
#* Fold the Printme in half and keep it inside of the laptop,<br />
#* Make sure the Keeper Label has been updated (i.e., check the QC boxes),<br />
#* Make sure the Power Adapter is neatly wrapped,<br />
#* Thank the Builder and bring it back to Laptops.<br />
<br />
==Howto Disburse a Take-home Computer==<br />
#Make sure box is within FreekBox Spec,<br />
#Fill out Disbursement info on builder's Printme,<br />
#Encourage builder to QC their box, or to have someone else QC it for them (not required),<br />
#Ask builder what peripherals they want and collect them from the Warehouse and Receiving, <br />
#Encourage the builder to attend our '''New to Ubuntu class''' and give them a class flyer (if available),<br />
#Fill the builder in on our '''Tech Support policy''' and give them a copy of the policy to take with them (if available),<br />
#'''It is very important that the disbursement Printme gets to the Front Desk'''. It is preferable to walk with the builder to the front to turn in the Printme, remind them to log their hours and let the Front Desk staff know why the builder is walking out the door with computer equipment. <br />
#Don't forget to congratulate the builder for completing the program and taking home their FreekBox. Ask them to take the Build survey: [http://freegeek.limequery.com/index.php?sid=48992&lang=en] and encourage them to continue building,<br />
#If the Builder is interested in a Post-Build area, have them initiate the post-build application process.<br />
<br />
==Remember to use your resources if you get stuck!==<br />
'''There are always Reuse Program staff assigned to every shift that you can go to for help.'''<br />
<br />
==Additional Handouts for Training==<br />
; [[Media:BuildInstructorOrientation.odt|Build Instructor Orientation]]<br />
: Checklist for new Build Instructors<br />
<br />
; [[Media:Teaching_Philosophy.odt|Build Teaching Philosophy]]<br />
: Teaching philosophy of the Build program.<br />
<br />
[[Category:Build]]<br />
[[Category:Training]]</div>Alambhttp://wiki.freegeek.org/index.php?title=Build_Specs&diff=64263Build Specs2012-09-18T22:35:33Z<p>Alamb: </p>
<hr />
<div>Here are the technical specifications of the main types of computers built at Free Geek:<br />
<br />
== Freek Box ==<br />
Freek Boxes are given out to volunteers in the Build and Adoption Programs. Some are also granted out to schools and non-profits. <br />
* '''Processor:''' Pentium Dual Core/Core 2 Duo, 1.6-2.13 GHz<br />
* '''RAM:''' 1 GB<br />
* '''Video:''' Onboard or 128 Mb AGP video card (1024x768 or better). A PCI-e card may be used if it's the only video option.<br />
* '''Hard Drive:''' 120-160 GB<br />
* '''Optical Drive:''' DVD-RW combo drive <br />
* '''Sound:''' Onboard or PCI Sound Card<br />
* '''Networking:''' Onboard or PCI 10/100 Bt<br />
<br />
== FG-PDX ==<br />
FG-PDX systems are donated by the City of Portland and granted out to local schools and non-profits.<br />
* '''Processor:''' variable<br />
* '''RAM:''' 1 GB<br />
* '''Video:''' Onboard or >64 Mb AGP video card, PCI-e if necessary for video to work<br />
* '''Hard Drive:''' 80-100 GB<br />
* '''Optical Drive:''' CD-RW/DVD-ROM OR DVD-RW combo<br />
* '''Sound:''' Onboard or PCI Sound Card<br />
* '''Networking:''' Onboard or PCI 10/100 Bt<br />
<br />
== Regular ==<br />
Regular systems are sold in the store to help cover Free Geek's operating costs.<br />
* '''Processor:''' Pentium 4, Pentium D, Athlon 64 single-core, Sempron<br />
* '''RAM:''' 1 GB<br />
* '''Video:''' Onboard or 128 Mb AGP video card<br />
* '''Hard Drive:''' 80-100 GB<br />
* '''Optical Drive:''' CD-RW ''OR'' DVD-ROM<br />
* '''Sound:''' Onboard or PCI Sound Card<br />
* '''Networking:''' Onboard or PCI 10/100 Bt<br />
<br />
==HighEnd Specs==<br />
HighEnds are also sold in the store to help cover Free Geek's operating costs<br />
* '''Processor:''' Pentium Dual Core/Core 2 Duo >2.13 GHz, Core 2 Quad, Core iSeries, Celeron E/G Series, Pentium E/G Series, Xeon, AMD X2/multi-core, Phenom/II, Athlon II<br />
* '''RAM:''' 2 GB or higher<br />
* '''Video:''' Onboard or >128 Mb AGP video card or PCI-E card<br />
* '''Hard Drive:''' >160 GB<br />
* '''Optical Drive:''' DVD-RW combo drive<br />
* '''Sound:''' Onboard or PCI Sound Card<br />
* '''Networking:''' Onboard or PCI 10/100 Bt<br />
<br />
[[Category: Build]]</div>Alambhttp://wiki.freegeek.org/index.php?title=Keyholders&diff=64257Keyholders2012-09-18T21:18:43Z<p>Alamb: /* T keys */</p>
<hr />
<div>{{RightTOC}}<br />
<br />
== How to get a key ==<br />
* ''Staff amended this to cover apprentices on [http://lists.freegeek.org/pipermail/minutes/2008-March/ March 28, 2008]''<br />
<br />
Core volunteers that need an external key can ask to be granted a key by the staff collective by sending a message to staff@freegeek.org and indicating what they need the key for. The collective will discuss the matter at the next possible staff meeting. Paid interns are granted keys as needed subject to review by the staff collective. If a keyholder loses a key, they must reapply to the staff collective.<br />
<br />
For further information on who gets keys and how check out the [[After Hours Access Policy]]. If you have a key, also read the [[After Hours Access Procedure]].<br />
<br />
=== Notes ===<br />
''All members of the staff collective have keys to both the external (F) and internal (I) doors in the building. Additionally, paid apprentices, other staff, and core volunteers also have these keys as needed, typically (E) or (F) and possibly (I) keys.''<br />
<br />
Some people who used to be keyholders no longer need them. Also, we were unable to adequately review all the previous keyholders. Anyone not on the list who wants a key should send a message requesting one to staff the (see above).<br />
<br />
== Lists of keyholders ==<br />
E and F keyholders need to read and understand the [[After Hours Access Procedure]].<br />
<br />
''Italic names'' = allotted but not handed out yet.<br />
<br />
'''Note: E and F keyholders also need a PIN to arm or disarm the alarm system if they might enter or exit the building after hours. All E and F keyholders should be on the locks list.<br />
<br />
=== F keys ===<br />
'''Do not give out F keys without consulting with Richard. He's in the process of re-numbering the key & alarm code system.''' -djk 6/1/12<br />
<br><br />
''NOTE: ['''F''']ree Geek keys work on '''all''' external doors including the '''after hours access door''' (near the meeting room).''<br />
<br />
* (#1F) '''DO NOT GIVE OUT THIS KEY!! This ADMIN key is kept in the safe for making copies.'''<br />
* (#2F) Austin Crouch<br />
* (#3F) Amelia Lamb<br />
* (#4F) ''in safe''<br />
* (#5F) Liane Kocka<br />
* (#6F) Misty Falls<br />
* (#7F) Richard Seymour<br />
* (#8F) Paul Munday<br />
* (#9F) Darren Heiber<br />
* (#10F) Darryl Kan<br />
* (#11F) Brian Keefer<br />
* (#12F) McGuire Bearing/Jim Conley<br />
* (#13F) Kevin Wright<br />
* (#14F) Aradan Thompson<br />
* (#15F) Elizabeth Swager<br />
* (#16F) Stephen Getman<br />
* (#17F) Liliana Gaitan<br />
* (#18F) Robert Taylor<br />
* (#19F) ''in safe''<br />
* (#20F) Sean Ellefson<br />
* (#21F) Cynthia Prevatte<br />
* (#22F) Lynnae Griffiths<br />
* (#23F) ''in safe''<br />
* (#24F) Walter Sebaste<br />
* (#25F) Cliff Fortune<br />
* (#26F) Mark Kille<br />
* (#27F) Omar Vargas<br />
* (#28F) '''LOST!'''<br />
* (#29F) Patrick Sullivan<br />
* (#30F) ''in safe'' <br />
* (#31F) ''in safe'' <br />
* (#32F) ''in safe'' <br />
* (#33F) ''in safe'' <br />
* (#34F) ''in safe'' <br />
* (#35F) ''in safe'' <br />
* (#36F) ''in safe'' <br />
* (#37F) Eli Wisnievitz<br />
* (#38F) Ashley Sue Masoomian<br />
* (#39F) Jake Taasevigen<br />
* (#40F) John Ashcraft<br />
* (#41F) James Pella<br />
* (#42F) Michael Westwind<br />
* (#43F) Ryan Niebur<br />
* (#44F) Vagrant Cascadian<br />
* (#45F) Santiago del Carmona<br />
<br />
=== E keys ===<br />
''NOTE: "E" indicates a key for the '''E'''xternal '''after hours access door''' (near the meeting room).''<br />
<br />
* (#85E) ''in safe''<br />
* (#86E) ''in safe''<br />
* (#87E) ''in safe''<br />
* (#88E) ''in safe''<br />
* (#89E) Kelly Forest<br />
* (#90E) Michael Dexter (PLUG Advanced Topics)<br />
* (#91E) Evie Strohmeyer<br />
* (#92E) '''reserved for Ben Kerensa (groups)<br />
* (#93E) Eco Janitorial Solutions<br />
* (#94E) Eric Wilhelm (perlmongers)<br />
* (#95E) Bob Griggs<br />
* (#96E) Jason Owen<br />
* (#97E) John Jason Jordan (PLUG Clinic)<br />
* (#98E) Kenny McElroy<br />
* (#99E) '''DO NOT GIVE OUT THIS KEY!! This ADMIN key is kept in the safe for making copies.<br />
<br />
=== I keys ===<br />
''(NOTE: "I" indicates an '''I'''nternal key, used to protect money, and confidential papers.)''<br />
<br />
* (#01I) '''LOST!''' ''(Amelia will keep an eye out for it)''<br />
* (#02I) '''DO NOT GIVE OUT THIS KEY!! This ADMIN key is kept in the safe for making copies.'''<br />
* (#03I) ''in safe''<br />
* (#04I) John Ashcraft<br />
* (#05I) Liane Kocka<br />
* (#06I) Misty Falls<br />
* (#07I) Richard Seymour<br />
* (#08I) Michael Westwind<br />
* (#09I) Austin Crouch<br />
* (#10I) Darryl Kan<br />
* (#11I) Paul Munday<br />
* (#12I) Evie Strohmeyer<br />
* (#13I) Brian Keefer<br />
* (#14I) Ryan Niebur<br />
* (#15I) Vagrant Cascadian<br />
* (#16I) ''in safe''<br />
* (#17I) Patrick Sullivan<br />
* (#18I) Jason Owen<br />
* (#19I) Amelia Lamb<br />
* (#20I) Sean Ellefson<br />
* (#21I) Elizabeth Swager<br />
* (#22I) Cliff Fortune <br />
* (#23I) John McNamee<br />
* (#24I) Jake Taasevigen<br />
* (#25I) Santiago del Carmona<br />
* (#26I) Walter Sebaste<br />
* (#27I) Cynthia Prevatte<br />
* (#28I) Robert Taylor<br />
* (#29I) ''This key was recycled on 12/17/2011 because it didn't work on the Escape Hatch door.''<br />
* (#30I) Omar Vargas<br />
* (#31I) Darren Heiber<br />
* (#32I) ''in safe''<br />
* (#33I) Liliana Gaitan<br />
* (#34I) Mark Kille<br />
* (#35I) Stephen Getman<br />
* (#36I) Kevin Wright<br />
* (#37I) Lynnae Griffiths<br />
* (#38I) '''LOST!'''<br />
* (#39I) McGuire Bearing/Jim Conley<br />
* (#40I) Aradan Thompson<br />
* (#41I) James Pella<br />
* (#42I) Ashley Sue Masoomian<br />
* (#43I) Eli Wisnievitz<br />
* (#44I) ''in safe''<br />
* (#45I) ''in safe''<br />
* (#46I) ''in safe''<br />
* (#47I) ''in safe''<br />
* (#48I) ''in safe''<br />
* (#49I) ''in safe''<br />
* (#50I) ''in safe''<br />
<br />
=== T keys ===<br />
''This is the T key to the '''T'''ARDIS and other areas that contain "shiny" objects. Keys are issued at the discretion of the Production Committee and are provided to instructors in Build/Laptop/Macbuild and to point people in Advanced Testing.''<br />
<br />
* (T#1) Tom McCann<br />
* (T#2) Camille Huffman<br />
* (T#3) Robert Perry (Tex)<br />
* (T#4) Larry Lloyd<br />
* (T#5) Dennis Jones<br />
* (T#6) Blaine Deatherage-Newsom<br />
* (T#7) Eric Klotter<br />
* (T#8) Steve Van Dusen<br />
* (T#9) Nate Lee<br />
* (T#10) Kurt Krueger<br />
* (T#11) '''MISSING'''<br />
* (T#12) '''DO NOT GIVE OUT THIS KEY!! This ADMIN key is kept in the safe for making copies.'''<br />
* (T#13) Ron Escano<br />
* (T#14) Roy Marshall<br />
* (T#15) Max Schwarz<br />
* (T#16) John Franko<br />
* (T#17) Mary Meier<br />
* (T#18) Charlie MacCarthy<br />
* (T#19) Tara Nelson<br />
* (T#20) Jackson Tate<br />
* (T#21) Dale Lockhart<br />
* (T#22) Michael McCall<br />
* (T#23) Gordon Riggs<br />
* (T#24) "Lalo" Luis Eduardo Garza Crespo<br />
* (T#25) Daniel Lingle<br />
* (T#26) ''in safe''<br />
* (T#27) ''in safe''<br />
<br />
=== Tech Support (S) ===<br />
These '''S'''upport keys are regular sized.<br />
<br />
* (S#1) In Tech Support<br />
* (S#2) '''DO NOT GIVE OUT THIS KEY!! This ADMIN key is kept in the safe for making copies.'''<br />
* (S#3) ''in safe''<br />
<br />
=== Personnel File Cabinet ===<br />
* (P#1) Stephen Getman<br />
* (P#2) Richard Seymour<br />
* (P#3) ''in safe''<br />
* (P#4) ''in safe<br />
* (P#5) Mark Kille<br />
* (P#6) Liane Kocka<br />
* (P#7) '''LOST!'''<br />
* (P#8) ''in safe''<br />
<br />
=== Staff Safe (S) ===<br />
''The '''S'''afe keys are smaller than the other S keys (above).''<br />
* (#1S) Darryl Kan<br />
* (#2S) Liane Kocka<br />
* (#3S) Amelia Lamb<br />
* (#4S) Darren Heiber<br />
* (#5S) Richard Seymour<br />
* (#6S) Mark Kille<br />
* (#7S) Sean Ellefson<br />
* (#8S) Michael Westwind<br />
* (#9S) Brian Keefer<br />
* (#10S) '''LOST!'''<br />
* (#11S) Cynthia Prevatte<br />
* (#12S) ''in safe''<br />
* (#13S) ''in safe''<br />
* (#14S) '''LOST!'''<br />
* (#15S) Paul Munday<br />
* (#16S) Stephen Getman<br />
<br />
=== Truck Keys ===<br />
The GMC box Truck has "Sets of Keys". There are 3 keys in each set. One for driving and doors, one for lock, and one for the gas tank.<br />
* Master copy unnumbered: '''dont give out!'''<br />
* (1) Liane Kocka<br />
* (2) Austin Crouch<br />
* (3) Darryl Kan<br />
* (4) ''in safe<br />
<br />
=== Forklift Keys ===<br />
This includes a forklift key, and a key to the padlock on the small hanging cabinet on the wall near the forklift charger. These keys are not numbered.<br />
* Master copy unnumbered: '''dont give out!'''<br />
* Cliff Fortune<br />
* Darryl Kan<br />
* ''in safe''<br />
* John Ashcraft<br />
* Liane Kocka<br />
<br />
=== C Keys ===<br />
''(the "C" key is for the secure Supply Cabinet in the store's back room)''<br />
* (#C1) ''MISSING''<br />
* (#C2) ''was twisted, then recycled''<br />
* (#C3) ''MISSING''<br />
* (#C4) ''MISSING''<br />
* (#C5) ''in safe<br />
* (#C6) ''in safe''<br />
* (#C7) ''in safe<br />
* (#C8) ''MISSING''<br />
* (#C9) Michael Westwind<br />
* (#C10) Liane Kocka<br />
* (#C11) ''in safe''<br />
* (#C12) ''MISSING''<br />
* (#C13) ''in safe<br />
* (#C14) Lynnae Griffiths<br />
* (#C15) Brian Keefer<br />
<br />
=== Monkey House Locker ===<br />
The monkey house locker is in the monkey house. It is a lateral file cabinet. Keys are mostly silver with no numbers or identifying marks.<br />
# Master Key - Gold colored key marked "STEELCASE GRAND RAPIDS MICHIGAN" on front, "FR433" on back. ''in safe<br />
# ''in safe''<br />
# Tom Wolcott<br />
# ''missing? (was Greg K's)''<br />
# Darren Heiber<br />
# Liliana Gaitan<br />
# Misty Fall<br />
# Nate Lee<br />
<br />
=== HR keys ===<br />
* HR-A<br />
** Mark Kille<br />
** ''in safe''<br />
** ''in safe''<br />
* HR-B<br />
** Richard Seymour<br />
** ''in safe''<br />
** ''in safe''<br />
<br />
=== Classic Gaming Library or CGL ===<br />
The Classic Gaming Library is upstairs adjacent to the Wine Cellar. This door operates on the "I" key as of 12/1/2011.<br />
<br />
== Re-keying the locks ==<br />
* If you're re-keying the locks, check this page to estimate how many new keys will be needed. Remember to take into account non Free Geekers with keys (the landlord, user group reps, etc.)<br />
* It is customary for the staff collective to reevaluate who still needs keys. This will affect the number of keys needed.<br />
* Also, if there are upcoming needs for keys such as hirings, interns, etc. There also may be folks leaving who will add to the available pool of keys.<br />
* Other key requests will undoubtedly be made, so having a few extra keys made is good. (They should be kept in the safe.)<br />
* The keys should be numbered so they can be kept track of. The locksmith can do this. Our current locksmith (Atlasta Lock and Key) does this for no charge.<br />
* Before the locks are re-keyed it is very important that all keyholders be notified so that folks who need access are not locked out. This is especially important for keyholders who are not on staff, as they are most likely to be forgotten.<br />
* Be sure to review the [[List of locks]].<br />
<br />
[[Category:Locks]]</div>Alambhttp://wiki.freegeek.org/index.php?title=Keyholders&diff=64256Keyholders2012-09-18T21:13:54Z<p>Alamb: /* T keys */</p>
<hr />
<div>{{RightTOC}}<br />
<br />
== How to get a key ==<br />
* ''Staff amended this to cover apprentices on [http://lists.freegeek.org/pipermail/minutes/2008-March/ March 28, 2008]''<br />
<br />
Core volunteers that need an external key can ask to be granted a key by the staff collective by sending a message to staff@freegeek.org and indicating what they need the key for. The collective will discuss the matter at the next possible staff meeting. Paid interns are granted keys as needed subject to review by the staff collective. If a keyholder loses a key, they must reapply to the staff collective.<br />
<br />
For further information on who gets keys and how check out the [[After Hours Access Policy]]. If you have a key, also read the [[After Hours Access Procedure]].<br />
<br />
=== Notes ===<br />
''All members of the staff collective have keys to both the external (F) and internal (I) doors in the building. Additionally, paid apprentices, other staff, and core volunteers also have these keys as needed, typically (E) or (F) and possibly (I) keys.''<br />
<br />
Some people who used to be keyholders no longer need them. Also, we were unable to adequately review all the previous keyholders. Anyone not on the list who wants a key should send a message requesting one to staff the (see above).<br />
<br />
== Lists of keyholders ==<br />
E and F keyholders need to read and understand the [[After Hours Access Procedure]].<br />
<br />
''Italic names'' = allotted but not handed out yet.<br />
<br />
'''Note: E and F keyholders also need a PIN to arm or disarm the alarm system if they might enter or exit the building after hours. All E and F keyholders should be on the locks list.<br />
<br />
=== F keys ===<br />
'''Do not give out F keys without consulting with Richard. He's in the process of re-numbering the key & alarm code system.''' -djk 6/1/12<br />
<br><br />
''NOTE: ['''F''']ree Geek keys work on '''all''' external doors including the '''after hours access door''' (near the meeting room).''<br />
<br />
* (#1F) '''DO NOT GIVE OUT THIS KEY!! This ADMIN key is kept in the safe for making copies.'''<br />
* (#2F) Austin Crouch<br />
* (#3F) Amelia Lamb<br />
* (#4F) ''in safe''<br />
* (#5F) Liane Kocka<br />
* (#6F) Misty Falls<br />
* (#7F) Richard Seymour<br />
* (#8F) Paul Munday<br />
* (#9F) Darren Heiber<br />
* (#10F) Darryl Kan<br />
* (#11F) Brian Keefer<br />
* (#12F) McGuire Bearing/Jim Conley<br />
* (#13F) Kevin Wright<br />
* (#14F) Aradan Thompson<br />
* (#15F) Elizabeth Swager<br />
* (#16F) Stephen Getman<br />
* (#17F) Liliana Gaitan<br />
* (#18F) Robert Taylor<br />
* (#19F) ''in safe''<br />
* (#20F) Sean Ellefson<br />
* (#21F) Cynthia Prevatte<br />
* (#22F) Lynnae Griffiths<br />
* (#23F) ''in safe''<br />
* (#24F) Walter Sebaste<br />
* (#25F) Cliff Fortune<br />
* (#26F) Mark Kille<br />
* (#27F) Omar Vargas<br />
* (#28F) '''LOST!'''<br />
* (#29F) Patrick Sullivan<br />
* (#30F) ''in safe'' <br />
* (#31F) ''in safe'' <br />
* (#32F) ''in safe'' <br />
* (#33F) ''in safe'' <br />
* (#34F) ''in safe'' <br />
* (#35F) ''in safe'' <br />
* (#36F) ''in safe'' <br />
* (#37F) Eli Wisnievitz<br />
* (#38F) Ashley Sue Masoomian<br />
* (#39F) Jake Taasevigen<br />
* (#40F) John Ashcraft<br />
* (#41F) James Pella<br />
* (#42F) Michael Westwind<br />
* (#43F) Ryan Niebur<br />
* (#44F) Vagrant Cascadian<br />
* (#45F) Santiago del Carmona<br />
<br />
=== E keys ===<br />
''NOTE: "E" indicates a key for the '''E'''xternal '''after hours access door''' (near the meeting room).''<br />
<br />
* (#85E) ''in safe''<br />
* (#86E) ''in safe''<br />
* (#87E) ''in safe''<br />
* (#88E) ''in safe''<br />
* (#89E) Kelly Forest<br />
* (#90E) Michael Dexter (PLUG Advanced Topics)<br />
* (#91E) Evie Strohmeyer<br />
* (#92E) '''reserved for Ben Kerensa (groups)<br />
* (#93E) Eco Janitorial Solutions<br />
* (#94E) Eric Wilhelm (perlmongers)<br />
* (#95E) Bob Griggs<br />
* (#96E) Jason Owen<br />
* (#97E) John Jason Jordan (PLUG Clinic)<br />
* (#98E) Kenny McElroy<br />
* (#99E) '''DO NOT GIVE OUT THIS KEY!! This ADMIN key is kept in the safe for making copies.<br />
<br />
=== I keys ===<br />
''(NOTE: "I" indicates an '''I'''nternal key, used to protect money, and confidential papers.)''<br />
<br />
* (#01I) '''LOST!''' ''(Amelia will keep an eye out for it)''<br />
* (#02I) '''DO NOT GIVE OUT THIS KEY!! This ADMIN key is kept in the safe for making copies.'''<br />
* (#03I) ''in safe''<br />
* (#04I) John Ashcraft<br />
* (#05I) Liane Kocka<br />
* (#06I) Misty Falls<br />
* (#07I) Richard Seymour<br />
* (#08I) Michael Westwind<br />
* (#09I) Austin Crouch<br />
* (#10I) Darryl Kan<br />
* (#11I) Paul Munday<br />
* (#12I) Evie Strohmeyer<br />
* (#13I) Brian Keefer<br />
* (#14I) Ryan Niebur<br />
* (#15I) Vagrant Cascadian<br />
* (#16I) ''in safe''<br />
* (#17I) Patrick Sullivan<br />
* (#18I) Jason Owen<br />
* (#19I) Amelia Lamb<br />
* (#20I) Sean Ellefson<br />
* (#21I) Elizabeth Swager<br />
* (#22I) Cliff Fortune <br />
* (#23I) John McNamee<br />
* (#24I) Jake Taasevigen<br />
* (#25I) Santiago del Carmona<br />
* (#26I) Walter Sebaste<br />
* (#27I) Cynthia Prevatte<br />
* (#28I) Robert Taylor<br />
* (#29I) ''This key was recycled on 12/17/2011 because it didn't work on the Escape Hatch door.''<br />
* (#30I) Omar Vargas<br />
* (#31I) Darren Heiber<br />
* (#32I) ''in safe''<br />
* (#33I) Liliana Gaitan<br />
* (#34I) Mark Kille<br />
* (#35I) Stephen Getman<br />
* (#36I) Kevin Wright<br />
* (#37I) Lynnae Griffiths<br />
* (#38I) '''LOST!'''<br />
* (#39I) McGuire Bearing/Jim Conley<br />
* (#40I) Aradan Thompson<br />
* (#41I) James Pella<br />
* (#42I) Ashley Sue Masoomian<br />
* (#43I) Eli Wisnievitz<br />
* (#44I) ''in safe''<br />
* (#45I) ''in safe''<br />
* (#46I) ''in safe''<br />
* (#47I) ''in safe''<br />
* (#48I) ''in safe''<br />
* (#49I) ''in safe''<br />
* (#50I) ''in safe''<br />
<br />
=== T keys ===<br />
''This is the T key to the '''T'''ARDIS and other areas that contain "shiny" objects. Keys are issued at the discretion of the Production Committee and are provided to instructors in Build/Laptop/Macbuild and to point people in Advanced Testing.''<br />
<br />
* (T#1) Tom McCann<br />
* (T#2) Camille Huffman<br />
* (T#3) Robert Perry (Tex)<br />
* (T#4) Larry Lloyd<br />
* (T#5) Dennis Jones<br />
* (T#6) Blaine Deatherage-Newsom<br />
* (T#7) Eric Klotter<br />
* (T#8) Steve Van Dusen<br />
* (T#9) Nate Lee<br />
* (T#10) Kurt Krueger<br />
* (T#11) '''MISSING'''<br />
* (T#12) '''DO NOT GIVE OUT THIS KEY!! This ADMIN key is kept in the safe for making copies.'''<br />
* (T#13) Ron Escano<br />
* (T#14) Roy Marshall<br />
* (T#15) Max Schwarz<br />
* (T#16) John Franko<br />
* (T#17) Mary Meier<br />
* (T#18) Charlie MacCarthy<br />
* (T#19) Tara Nelson<br />
* (T#20) Jackson Tate<br />
* (T#21) Dale Lockhart<br />
* (T#22) Michael McCall<br />
* (T#23) Gordon Riggs<br />
* (T#24) "Lalo" Luis Eduardo Garza Crespo<br />
* (T#25) Daniel Lingle<br />
* (T#26) ''in safe''<br />
* (T#27) '''MISSING'''<br />
<br />
=== Tech Support (S) ===<br />
These '''S'''upport keys are regular sized.<br />
<br />
* (S#1) In Tech Support<br />
* (S#2) '''DO NOT GIVE OUT THIS KEY!! This ADMIN key is kept in the safe for making copies.'''<br />
* (S#3) ''in safe''<br />
<br />
=== Personnel File Cabinet ===<br />
* (P#1) Stephen Getman<br />
* (P#2) Richard Seymour<br />
* (P#3) ''in safe''<br />
* (P#4) ''in safe<br />
* (P#5) Mark Kille<br />
* (P#6) Liane Kocka<br />
* (P#7) '''LOST!'''<br />
* (P#8) ''in safe''<br />
<br />
=== Staff Safe (S) ===<br />
''The '''S'''afe keys are smaller than the other S keys (above).''<br />
* (#1S) Darryl Kan<br />
* (#2S) Liane Kocka<br />
* (#3S) Amelia Lamb<br />
* (#4S) Darren Heiber<br />
* (#5S) Richard Seymour<br />
* (#6S) Mark Kille<br />
* (#7S) Sean Ellefson<br />
* (#8S) Michael Westwind<br />
* (#9S) Brian Keefer<br />
* (#10S) '''LOST!'''<br />
* (#11S) Cynthia Prevatte<br />
* (#12S) ''in safe''<br />
* (#13S) ''in safe''<br />
* (#14S) '''LOST!'''<br />
* (#15S) Paul Munday<br />
* (#16S) Stephen Getman<br />
<br />
=== Truck Keys ===<br />
The GMC box Truck has "Sets of Keys". There are 3 keys in each set. One for driving and doors, one for lock, and one for the gas tank.<br />
* Master copy unnumbered: '''dont give out!'''<br />
* (1) Liane Kocka<br />
* (2) Austin Crouch<br />
* (3) Darryl Kan<br />
* (4) ''in safe<br />
<br />
=== Forklift Keys ===<br />
This includes a forklift key, and a key to the padlock on the small hanging cabinet on the wall near the forklift charger. These keys are not numbered.<br />
* Master copy unnumbered: '''dont give out!'''<br />
* Cliff Fortune<br />
* Darryl Kan<br />
* ''in safe''<br />
* John Ashcraft<br />
* Liane Kocka<br />
<br />
=== C Keys ===<br />
''(the "C" key is for the secure Supply Cabinet in the store's back room)''<br />
* (#C1) ''MISSING''<br />
* (#C2) ''was twisted, then recycled''<br />
* (#C3) ''MISSING''<br />
* (#C4) ''MISSING''<br />
* (#C5) ''in safe<br />
* (#C6) ''in safe''<br />
* (#C7) ''in safe<br />
* (#C8) ''MISSING''<br />
* (#C9) Michael Westwind<br />
* (#C10) Liane Kocka<br />
* (#C11) ''in safe''<br />
* (#C12) ''MISSING''<br />
* (#C13) ''in safe<br />
* (#C14) Lynnae Griffiths<br />
* (#C15) Brian Keefer<br />
<br />
=== Monkey House Locker ===<br />
The monkey house locker is in the monkey house. It is a lateral file cabinet. Keys are mostly silver with no numbers or identifying marks.<br />
# Master Key - Gold colored key marked "STEELCASE GRAND RAPIDS MICHIGAN" on front, "FR433" on back. ''in safe<br />
# ''in safe''<br />
# Tom Wolcott<br />
# ''missing? (was Greg K's)''<br />
# Darren Heiber<br />
# Liliana Gaitan<br />
# Misty Fall<br />
# Nate Lee<br />
<br />
=== HR keys ===<br />
* HR-A<br />
** Mark Kille<br />
** ''in safe''<br />
** ''in safe''<br />
* HR-B<br />
** Richard Seymour<br />
** ''in safe''<br />
** ''in safe''<br />
<br />
=== Classic Gaming Library or CGL ===<br />
The Classic Gaming Library is upstairs adjacent to the Wine Cellar. This door operates on the "I" key as of 12/1/2011.<br />
<br />
== Re-keying the locks ==<br />
* If you're re-keying the locks, check this page to estimate how many new keys will be needed. Remember to take into account non Free Geekers with keys (the landlord, user group reps, etc.)<br />
* It is customary for the staff collective to reevaluate who still needs keys. This will affect the number of keys needed.<br />
* Also, if there are upcoming needs for keys such as hirings, interns, etc. There also may be folks leaving who will add to the available pool of keys.<br />
* Other key requests will undoubtedly be made, so having a few extra keys made is good. (They should be kept in the safe.)<br />
* The keys should be numbered so they can be kept track of. The locksmith can do this. Our current locksmith (Atlasta Lock and Key) does this for no charge.<br />
* Before the locks are re-keyed it is very important that all keyholders be notified so that folks who need access are not locked out. This is especially important for keyholders who are not on staff, as they are most likely to be forgotten.<br />
* Be sure to review the [[List of locks]].<br />
<br />
[[Category:Locks]]</div>Alambhttp://wiki.freegeek.org/index.php?title=File:Build-specs.odt&diff=64159File:Build-specs.odt2012-09-12T00:37:31Z<p>Alamb: uploaded a new version of "File:Build-specs.odt"</p>
<hr />
<div></div>Alambhttp://wiki.freegeek.org/index.php?title=QC_checklist&diff=64146QC checklist2012-09-09T23:40:00Z<p>Alamb: /* HARDWARE AND SOFTWARE TESTING */</p>
<hr />
<div>'''Welcome to the Build Workshop!''' Quality checking a few systems that others have built will be your first step, then you'll be ready to move on to assembling and checking software on systems. <br />
<br />
'''Work through every step as well as you can, and then ask a neighbor or your Build instructor if you still have questions.''' Try and learn the reason for each of the steps: this knowledge will come in handy later when, inevitably, things aren't going as smoothly.<br />
<br />
'''Use your resources!''' There are lots available to you - your neighbor, the Build assistants and instructors and, of course, the internet. Searching the web for answers to the challenge you are facing is one of the best ways to learn. You can also access tips and troubleshooting ideas on our wiki (http://wiki.freegeek.org) under [[Build tips]] or in our Troubleshooting Guide (http://wiki.freegeek.org/index.php/Build_Troubleshooting_Guide). <br />
{| border="2" fontname="Nimbus Sans" fontsize="12"<br />
|-<br />
== BEFORE YOU POWER ON ==<br />
----<br />
'''Check what needs to be quality checked'''<br />
* Grab a system from the QC shelves in the build room, and carry it to an open Build station.<br />
----<br />
'''Do you hear a rattling noise, caused by a screw or other loose component, upon moving the system?''' <br />
* If so, find the culprit and secure/remove it. <br />
----<br />
'''Is the case properly put together and secure?''' <br />
* If not, fix it!<br />
----<br />
'''Are all slots and bays covered?''' <br />
* If not, cover 'em! Check to make sure they're screwed in tightly by pushing on each one with your finger - if a slot cover falls out it can '''short out the motherboard.'''<br />
----<br />
'''Do you see more than one video, sound, or network ports?''' <br />
* Later, when you're testing audio, headphone jacks and standard sound ports should be tested.<br />
* Orange/Black/Gray sound ports are surround sound and do not need to be tested. <br />
*Any damaged ports will need to be covered with electrical tape or port covers. If you see two identical uncovered ports, one integrated and one on a card, ask your instructor how to proceed.<br />
----<br />
'''Is there Microsoft Branding? (Certificates of Authenticity) Asset tags (identifying the last owner)? Or branded hardware tags on the faceplate (identifying original components such as RAM, HDD, Optical Drive etc)?'''<br />
* If there is, take them off. '''DO NOT remove FG-PDX, "uncovered electronic device" Processor/graphics tags or Green Light stickers.'''<br />
----<br />
'''Is the system exterior clean?''' <br />
* If not, use cleaner and rag to clean. The vacuum cleaner will help remove dust clogged in case fans. Hand sanitizer, Goo Gone and/or isopropyl (rubbing) alcohol can help loosen any stickers; ask your instructor where to find scraping tools to remove them.<br />
----<br />
'''Open up the system and check inside for:'''<br />
# Blown capacitors (If found, the system must be rejected!)<br />
# What type of DDR RAM your system has installed - write this down<br />
# The RAM speed (will be the second number on the sticker) - write this down<br />
# Any dust accumulation - please vacuum or brush it out!<br />
<br />
== BOOT AND [[Entering BIOS|ENTER BIOS]] ==<br />
----<br />
'''Get into BIOS (Setup)''' <br />
* Turn on the computer. If you see a flash screen before boot-up, it will give the keystroke to enter BIOS, and the keystroke for a Boot Menu, if applicable. Delete, Escape, F1, F2, F9, F10, F12 and Enter are typical. <br />
*Get into BIOS, and write down both the BIOS and Boot Menu keystrokes; this info will come in handy later. <br />
*If you see "'''Ubuntu'''" on your screen, you have gone too far; reboot from the power button icon on the bottom-right corner of the screen, and try again. All BIOS are different. Feel free to explore how the BIOS you're using is set up. <br />
----<br />
'''Check boot order''' <br />
* It should be: '''1st- CD-ROM'''; '''2nd-Hard Drive'''. If possible, disable other boot device options, such as floppy (sometimes called Diskette), network, or USB. Depending on the BIOS model, you may need to enable active drive ports and disable inactive ones, in addition to arranging them in the boot sequence.<br />
----<br />
'''If possible, edit the following setting:'''<br />
* Enable Quick Boot<br />
----<br />
'''Save and exit BIOS'''<br />
* The system should boot to the Ubuntu operating system.<br />
----<br />
<br />
== HARDWARE AND SOFTWARE TESTING ==<br />
----<br />
'''Login to the system'''<br />
* username will be '''Default User''' <br> password = '''freegeek''' <br />
----<br />
'''What Specification Category does the system fall under?'''<br />
* Compare the CPU speed listed on the system's Green Light sticker with the '''FREE GEEK Specification Sheet,''' or "Spec Sheet," on the wall to determine the category of specifications, or "specs," to which the system should be built. (Keep in mind that FG-PDX's are determined by their sticker, not their processor.) If you aren't sure what type of box you are working with, please check with your instructor to see how to proceed.<br />
----<br />
'''Is the system standard?''' <br />
* Check the '''Spec Sheet''' on the wall to see what else should be installed for your spec category, then compare your system's spec category to the '''Build Printme''' document saved to the Desktop. Does the box have any parts that are extra, or missing, or built to incorrect specifications? Take out and replace parts as necessary to ensure that all specs are correct, paying special attention to properly seating/securing parts to ensure that they won't come loose. Ask an instructor if you are unsure how to do this.<br />
----<br />
'''Update the software'''<br />
* Click on '''System''' >> '''Administration''' >> '''Update Manager'''. When the Update Manager pops up, click "Check" to find updates, then if any updates appear, click "Install All." It may take some time to download and install packages, so feel free to continue on with other steps while this runs in the background.<br />
----<br />
'''Drag the terminal icon to the top panel'''<br />
* Go to '''Applications''' >> '''Accessories''' >> '''Terminal'''. Use the mouse to click and hold the button down over the Terminal icon, drag, then release the mouse button when the icon hovers over the black panel along the top of the screen.<br />
----<br />
'''Stress test the system for a few minutes''' <br />
* Open a terminal and run "'''stress-test'''". Wait a few minutes while it runs, and look for error messages. If you want to know more about what it's doing, open up another terminal and run "man stress". This may take some time; feel free to continue on to the next step while you wait.<br />
----<br />
'''Run "basiccheck"''' <br />
* Click on the terminal icon to open it. Type "'''basiccheck'''", then press enter to begin the program. There are basiccheck checklists hanging on the supply shelves which will help with verifying whether each test passes or not. Feel free to ask your peers and the instructor what parts of basiccheck mean so that you understand what each test is checking. When you're finished, close the terminal.<br />
----<br />
'''Test USB'''<br />
* Plug in a USB mouse, see that the cursor moves and can interact with things. <br />
* Repeat with all USB ports, including ports on the front of the system, if any.<br />
* If any ports don't work, they may need to be enabled in BIOS; ask your instructor how to proceed.<br />
----<br />
'''Check date and time''' <br />
* Displayed in the right corner of your top panel. If incorrect:<br />
# Make sure network cable is plugged in.<br />
# Right-click on the time and then click the "Preferences" button.<br />
# Click on the "Time Settings" button.<br />
# Manually adjust date and time. Press "Set System Time" to save, then close the Clock Preferences window.<br />
----<br />
'''Play an audio CD''' <br />
* Do you hear what you expect? Is it loud enough to be heard easily? Repeat for each optical drive. Also repeat for any additional sound ports. If any sound ports (typically colored green, sometimes blue) don't play audio, cover them up with port covers or electrical tape. '''If you have functional onboard sound, and a sound card, the card will need to be removed and replaced with a slot cover.'''<br />
* If you have surround sound ports (usually orange and gray) ignore them; we do not have the means to test this function. <br />
----<br />
'''Read data CD''' <br />
* If your file browser (listed under '''Places''' in the top panel) sees files on the drive, it can read data files. Repeat for each optical drive. <br />
----<br />
'''If you have a DVD Drive, Read DVD''' <br />
* If your file browser sees the file, the DVD-ROM can read files. If you are prompted to search for a suitable plugin or codec, '''please do not do this!''' The test still passes. Repeat for each DVD-ROM drive.<br />
----<br />
'''If you have an Optical Drive with CD-RW function, Test CD Writing'''<br />
* Insert a CD-RW disc into the drive and open Brasero Disc Burning (under '''Applications''' >> '''Sound & Video'''.) Select '''Data Project''', click on the green '''+''', then select '''examples.desktop''' and click '''Add'''. Click '''Burn''' in the lower right-hand corner. A new window will pop-up with a few options. If available, select '''Use burnproof''' and '''Burn the image directly without saving it to disc''' and click '''Burn'''. When the disc is done, verify that it contains the file by re-inserting the disc and seeing what pops up on the desktop.<br />
* Blank the disc using Brasero by selecting '''Tools''' >> '''Blank'''. If available, '''uncheck the "Fast Blank" option.''' If blanking does not work, the drive may still be completely functional! Ask your instructor about software bug workarounds. <br />
----<br />
'''If you have an Optical Drive with DVD-RW function, Test DVD Writing'''<br />
* Insert a DVD-RW disc into the drive and in the Brasero file browser follow the same steps as above to burn a data project. When the disc is done, verify that it contains the file by re-inserting the disc and seeing what pops up on the desktop.<br />
* Blank the disc using Brasero by selecting '''Tools''' >> '''Blank'''. If available, uncheck "Fast Blank." Again, blanking errors may not indicate a bad drive. Ask your instructor for more information.<br />
----<br />
'''Test for booting from live CD'''<br />
* Place Live CD in drive and restart the computer. The system should boot from the live CD. <br />
* Select language: English. Scroll down on the following screen to '''Boot to first hard drive''' and press enter. This should take you to the normal Ubuntu log-in screen. <br />
---- <br />
'''Remove all CDs and DVDs from the drive(s)'''<br />
----<br />
'''Reboot the system'''<br />
* Open a terminal and type '''sudo reboot.''' Wait while it reboots, and ensure that the system powers on and offers a login screen without user intervention (e.g. requiring you to "press F1 to boot.") <br />
* If it doesn't boot smoothly, double-check your boot priority options in BIOS and try again.<br />
----<br />
'''Run "printme" from terminal'''<br />
* From a terminal, type "'''printme,'''" this will generate a questionnaire in Command Line. <br />
* Refer to your written notes for the RAM type and speed, the BIOS key and Boot Menu key, if applicable. <br />
* '''When it asks what is notable about this system, refer to the white board for what should be included, and ask your instructor for any needed clarification.''' Press enter to create a web document.<br />
----<br />
'''Copy system ID (IMPORTANT!)'''<br />
* Copy the system ID from the printme onto a blank sticker and put it on back of computer, ideally in a location that isn't covering any fans, other ventilation, or removable case parts such as slot covers.<br />
----<br />
'''Add Free Geek Sticker'''<br />
* Affix on the front of the system, in a sensible location! (Usually adjacent to or above/below the Processor tag)<br />
----<br />
'''Check in with Build Instructor''' <br />
* The Build Instructor will check the printme and edit it to sign it off. <br />
* Your instructor may ask you to replace certain components, which will require re-running the "printme" form. Some changes may also need to be made in the web browser. If your instructor gives the "thumbs-up," proceed to the next step. <br />
----<br />
'''Save Printme to the Desktop'''<br />
* After your Build Instructor has inspected the system, click "Print" in the browser that opens. Choose "Print to file." Save the file to the Desktop and name it "QC Printme", then click "Print" to save. Click on the QC Printme icon on the Desktop to open it up. <br />
----<br />
'''Enable network printers:'''<br />
* Go to '''System>>Administration>>Printing'''<br />
* Select '''Server>>Settings''' and check the box marked <i>Show Printers Shared by Other Systems</i> and click OK.<br />
* Wait for a few moments and click the refresh icon. A selection of printers should appear.<br />
----<br />
'''Print a hard copy of Printme'''<br />
* Close the "Printing - localhost" window that opens and select the "build" printer from the Print menu once it appears. Click Print and retrieve the sheet from the printer in the back (SW) corner of the room. <br />
* Have your Build Instructor sign off on the printed sheet. Then fold it in half (lengthwise) and tape it to the top of the system (the side of the page with the instructor's initials facing up.)<br />
----<br />
'''Shut down and shelve the system''' <br />
* Open a terminal and type "sudo halt" then press enter. When the system has shut down, unplug all cables, double-check that the case is secured properly, and ask a build instructor where to put the system once shutdown is complete. <br />
----<br />
'''Clean up work area if it is your last QC of the day''' <br />
* Please put all tools away, throw out any garbage or sticker remains, put screws in the appropriate bins, wrap cords around your keyboard and mouse, turn off your speakers and monitor, and generally straighten up. <br />
|}<br />
<br />
<br />
<br />
<noinclude>[[Category:Build]]</noinclude></div>Alambhttp://wiki.freegeek.org/index.php?title=QC_checklist&diff=64145QC checklist2012-09-09T23:37:47Z<p>Alamb: /* BOOT AND ENTER BIOS */</p>
<hr />
<div>'''Welcome to the Build Workshop!''' Quality checking a few systems that others have built will be your first step, then you'll be ready to move on to assembling and checking software on systems. <br />
<br />
'''Work through every step as well as you can, and then ask a neighbor or your Build instructor if you still have questions.''' Try and learn the reason for each of the steps: this knowledge will come in handy later when, inevitably, things aren't going as smoothly.<br />
<br />
'''Use your resources!''' There are lots available to you - your neighbor, the Build assistants and instructors and, of course, the internet. Searching the web for answers to the challenge you are facing is one of the best ways to learn. You can also access tips and troubleshooting ideas on our wiki (http://wiki.freegeek.org) under [[Build tips]] or in our Troubleshooting Guide (http://wiki.freegeek.org/index.php/Build_Troubleshooting_Guide). <br />
{| border="2" fontname="Nimbus Sans" fontsize="12"<br />
|-<br />
== BEFORE YOU POWER ON ==<br />
----<br />
'''Check what needs to be quality checked'''<br />
* Grab a system from the QC shelves in the build room, and carry it to an open Build station.<br />
----<br />
'''Do you hear a rattling noise, caused by a screw or other loose component, upon moving the system?''' <br />
* If so, find the culprit and secure/remove it. <br />
----<br />
'''Is the case properly put together and secure?''' <br />
* If not, fix it!<br />
----<br />
'''Are all slots and bays covered?''' <br />
* If not, cover 'em! Check to make sure they're screwed in tightly by pushing on each one with your finger - if a slot cover falls out it can '''short out the motherboard.'''<br />
----<br />
'''Do you see more than one video, sound, or network ports?''' <br />
* Later, when you're testing audio, headphone jacks and standard sound ports should be tested.<br />
* Orange/Black/Gray sound ports are surround sound and do not need to be tested. <br />
*Any damaged ports will need to be covered with electrical tape or port covers. If you see two identical uncovered ports, one integrated and one on a card, ask your instructor how to proceed.<br />
----<br />
'''Is there Microsoft Branding? (Certificates of Authenticity) Asset tags (identifying the last owner)? Or branded hardware tags on the faceplate (identifying original components such as RAM, HDD, Optical Drive etc)?'''<br />
* If there is, take them off. '''DO NOT remove FG-PDX, "uncovered electronic device" Processor/graphics tags or Green Light stickers.'''<br />
----<br />
'''Is the system exterior clean?''' <br />
* If not, use cleaner and rag to clean. The vacuum cleaner will help remove dust clogged in case fans. Hand sanitizer, Goo Gone and/or isopropyl (rubbing) alcohol can help loosen any stickers; ask your instructor where to find scraping tools to remove them.<br />
----<br />
'''Open up the system and check inside for:'''<br />
# Blown capacitors (If found, the system must be rejected!)<br />
# What type of DDR RAM your system has installed - write this down<br />
# The RAM speed (will be the second number on the sticker) - write this down<br />
# Any dust accumulation - please vacuum or brush it out!<br />
<br />
== BOOT AND [[Entering BIOS|ENTER BIOS]] ==<br />
----<br />
'''Get into BIOS (Setup)''' <br />
* Turn on the computer. If you see a flash screen before boot-up, it will give the keystroke to enter BIOS, and the keystroke for a Boot Menu, if applicable. Delete, Escape, F1, F2, F9, F10, F12 and Enter are typical. <br />
*Get into BIOS, and write down both the BIOS and Boot Menu keystrokes; this info will come in handy later. <br />
*If you see "'''Ubuntu'''" on your screen, you have gone too far; reboot from the power button icon on the bottom-right corner of the screen, and try again. All BIOS are different. Feel free to explore how the BIOS you're using is set up. <br />
----<br />
'''Check boot order''' <br />
* It should be: '''1st- CD-ROM'''; '''2nd-Hard Drive'''. If possible, disable other boot device options, such as floppy (sometimes called Diskette), network, or USB. Depending on the BIOS model, you may need to enable active drive ports and disable inactive ones, in addition to arranging them in the boot sequence.<br />
----<br />
'''If possible, edit the following setting:'''<br />
* Enable Quick Boot<br />
----<br />
'''Save and exit BIOS'''<br />
* The system should boot to the Ubuntu operating system.<br />
----<br />
<br />
== HARDWARE AND SOFTWARE TESTING ==<br />
----<br />
'''Login to the system'''<br />
* username will be '''Default User''' <br> password = '''freegeek''' <br />
----<br />
'''What Specification Category does the system fall under?'''<br />
* Compare the CPU speed listed on the system's Green Light sticker with the '''FREE GEEK Specification Sheet,''' or "Spec Sheet," on the wall to determine the category of specifications, or "specs," to which the system should be built. (Keep in mind that FG-PDX's are determined by their sticker, not their processor.) If you aren't sure what type of box you are working with, please check with your instructor to see how to proceed.<br />
----<br />
'''Is the system standard?''' <br />
* Check the '''Spec Sheet''' on the wall to see what else should be installed for your spec category, then compare your system's spec category to the '''Build Printme''' document saved to the Desktop. Does the box have any parts that are extra, or missing, or built to incorrect specifications? Take out and replace parts as necessary to ensure that all specs are correct, paying special attention to properly seating/securing parts to ensure that they won't come loose. Ask an instructor if you are unsure how to do this.<br />
----<br />
'''Update the software'''<br />
* Click on '''System''' >> '''Administration''' >> '''Update Manager'''. When the Update Manager pops up, click "Check" to find updates, then if any updates appear, click "Install All." It may take some time to download and install packages, so feel free to continue on with other steps while this runs in the background.<br />
----<br />
'''Drag the terminal icon to the top panel'''<br />
* Go to '''Applications''' >> '''Accessories''' >> '''Terminal'''. Use the mouse to click and hold the button down over the Terminal icon, drag, then release the mouse button when the icon hovers over the black panel along the top of the screen.<br />
----<br />
'''Stress test the system for a few minutes''' <br />
* Open a terminal and run "'''stress-test'''". Wait a few minutes while it runs, and look for error messages. If you want to know more about what it's doing, open up another terminal and run "man stress". This may take some time; feel free to continue on to the next step while you wait.<br />
----<br />
'''Run "basiccheck"''' <br />
* Click on the terminal icon to open it. Type "'''basiccheck'''", then press enter to begin the program. There are basiccheck checklists hanging on the supply shelves which will help with verifying whether each test passes or not. Feel free to ask your peers and the instructor what parts of basiccheck mean so that you understand what each test is checking. When you're finished, close the terminal.<br />
----<br />
'''Test USB'''<br />
* Plug in a USB mouse, see that the cursor moves and can interact with things. <br />
* Repeat with all USB ports, including ports on the front of the system, if any.<br />
* If any ports don't work, they may need to be enabled in BIOS; ask your instructor how to proceed.<br />
----<br />
'''Check date and time''' <br />
* Displayed in the right corner of your top panel. If incorrect:<br />
# Make sure network cable is plugged in.<br />
# Right-click on the time and then click the "Preferences" button.<br />
# Click on the "Time Settings" button.<br />
# Manually adjust date and time. Press "Set System Time" to save, then close the Clock Preferences window.<br />
----<br />
'''Play an audio CD''' <br />
* Do you hear what you expect? Is it loud enough to be heard easily? Repeat for each optical drive. Also repeat for any additional sound ports. If any sound ports (typically colored green, sometimes blue) don't play audio, cover them up with port covers or electrical tape. '''If you have functional onboard sound, and a sound card, the card will need to be removed and replaced with a slot cover.'''<br />
* If you have surround sound ports (usually orange and gray) ignore them; we do not have the means to test this function. <br />
----<br />
'''Read data CD''' <br />
* If your file browser (listed under '''Places''' in the top panel) sees files on the drive, it can read data files. Repeat for each optical drive. <br />
----<br />
'''If you have a DVD Drive, Read DVD''' <br />
* If your file browser sees the file, the DVD-ROM can read files. If you are prompted to search for a suitable plugin or codec, '''please do not do this!''' The test still passes. Repeat for each DVD-ROM drive.<br />
----<br />
'''If you have an Optical Drive with CD-RW function, Test CD Writing'''<br />
* Insert a CD-RW disc into the drive and open Brasero Disc Burning (under '''Applications''' >> '''Sound & Video'''.) Select '''Data Project''', click on the green '''+''', then select '''examples.desktop''' and click '''Add'''. Click '''Burn''' in the lower right-hand corner. A new window will pop-up with a few options. If available, select '''Use burnproof''' and '''Burn the image directly without saving it to disc''' and click '''Burn'''. When the disc is done, verify that it contains the examples file by re-inserting the disc and seeing what pops up on the desktop.<br />
* Blank the disc using Brasero by selecting '''Tools''' >> '''Blank'''. If available, '''uncheck the "Fast Blank" option.''' If blanking does not work, the drive may still be completely functional! Ask your instructor about software bug workarounds. <br />
----<br />
'''If you have an Optical Drive with DVD-RW function, Test DVD Writing'''<br />
* Insert a DVD-RW disc into the drive and in the Brasero file browser follow the same steps as above to burn a data project. When the disc is done, verify that it contains the examples file by re-inserting the disc and seeing what pops up on the desktop.<br />
* Blank the disc using Brasero by selecting '''Tools''' >> '''Blank'''. If available, uncheck "Fast Blank." Again, blanking errors may not indicate a bad drive. Ask your instructor for more information.<br />
----<br />
'''Test for booting from live CD'''<br />
* Place Live CD in drive and restart the computer. The system should boot from the live CD. <br />
* Select language: English. Scroll down on the following screen to '''Boot to first hard drive''' and press enter. This should take you to the normal Ubuntu log-in screen. <br />
---- <br />
'''Remove all CDs and DVDs from the drive(s)'''<br />
----<br />
'''Reboot the system'''<br />
* Open a terminal and type '''sudo reboot.''' Wait while it reboots, and ensure that the system powers on and offers a login screen without user intervention (e.g. requiring you to "press F1 to boot.") <br />
* If it doesn't boot smoothly, double-check your boot priority options in BIOS and try again.<br />
----<br />
'''Run "printme" from terminal'''<br />
* From a terminal, type "'''printme,'''" this will generate a questionnaire in Command Line. <br />
* Refer to your written notes for the RAM type and speed, the BIOS key and Boot Menu key, if applicable. <br />
* '''When it asks what is notable about this system, refer to the white board for what should be included, and ask your instructor for any needed clarification.''' Press enter to create a web document.<br />
----<br />
'''Copy system ID (IMPORTANT!)'''<br />
* Copy the system ID from the printme onto a blank sticker and put it on back of computer, ideally in a location that isn't covering any fans, other ventilation, or removable case parts such as slot covers.<br />
----<br />
'''Add Free Geek Sticker'''<br />
* Affix on the front of the system, in a sensible location! (Usually adjacent to or above/below the Processor tag)<br />
----<br />
'''Check in with Build Instructor''' <br />
* The Build Instructor will check the printme and edit it to sign it off. <br />
* Your instructor may ask you to replace certain components, which will require re-running the "printme" form. Some changes may also need to be made in the web browser. If your instructor gives the "thumbs-up," proceed to the next step. <br />
----<br />
'''Save Printme to the Desktop'''<br />
* After your Build Instructor has inspected the system, click "Print" in the browser that opens. Choose "Print to file." Save the file to the Desktop and name it "QC Printme", then click "Print" to save. Click on the QC Printme icon on the Desktop to open it up. <br />
----<br />
'''Enable network printers:'''<br />
* Go to '''System>>Administration>>Printing'''<br />
* Select '''Server>>Settings''' and check the box marked <i>Show Printers Shared by Other Systems</i> and click OK.<br />
* Wait for a few moments and click the refresh icon. A selection of printers should appear.<br />
----<br />
'''Print a hard copy of Printme'''<br />
* Close the "Printing - localhost" window that opens and select the "build" printer from the Print menu once it appears. Click Print and retrieve the sheet from the printer in the back (SW) corner of the room. <br />
* Have your Build Instructor sign off on the printed sheet. Then fold it in half (lengthwise) and tape it to the top of the system (the side of the page with the instructor's initials facing up.)<br />
----<br />
'''Shut down and shelve the system''' <br />
* Open a terminal and type "sudo halt" then press enter. When the system has shut down, unplug all cables, double-check that the case is secured properly, and ask a build instructor where to put the system once shutdown is complete. <br />
----<br />
'''Clean up work area if it is your last QC of the day''' <br />
* Please put all tools away, throw out any garbage or sticker remains, put screws in the appropriate bins, wrap cords around your keyboard and mouse, turn off your speakers and monitor, and generally straighten up. <br />
|}<br />
<br />
<br />
<br />
<noinclude>[[Category:Build]]</noinclude></div>Alambhttp://wiki.freegeek.org/index.php?title=Assembly_checklist&diff=64144Assembly checklist2012-09-09T22:32:14Z<p>Alamb: /* HARDWARE AND SOFTWARE TESTING */</p>
<hr />
<div>'''Work through every step as well as you can, and then ask a neighbor or your build instructor if you still have questions.''' Try and learn the reason for each of the steps: this knowledge will come in handy later when, inevitably, things aren't going as smoothly.<br />
<br />
'''Use your resources!''' There are lots available to you - your neighbor, the Build assistants and instructors and, of course, the internet. Searching the web for answers to the challenge you are facing is one of the best ways to learn. You can also access tips and troubleshooting ideas on our wiki (http://wiki.freegeek.org) under [[Build tips]] or in our Troubleshooting Guide (http://wiki.freegeek.org/index.php/Build_Troubleshooting_Guide). <br />
<br />
Supplies like cards, rails, hard drives, cleaning supplies, etc. can be found on the metal racks in the center of the build workshop. Here you will also find a box containing an assortment of common DDR memory.<br />
{| border="2" fontname="Nimbus Sans" fontsize="12"<br />
|-<br />
== BEFORE YOU POWER ON ==<br />
----<br />
'''Check what needs to be built on the white board''' <br />
* Head to the warehouse and scope out a system you would like to build. <br />
*'''Be sure to pay attention to the Green Light label.''' It will give you a lot of important information, like the type of video, if it did not POST, if the processor is Dual Core, etc. Make sure that the box you are about to Build is appropriate for its spec.<br />
* If everything looks good, Grab the system from the warehouse, take it back to your build station, and figure out how to pop it open. <br />
----<br />
'''Check capacitors'''<br />
* Visually inspect motherboard capacitors for bulges/leaks. If you find one, ask your instructor for a "Rejected" sticker. <br />
----<br />
'''Secure the case'''<br />
* Cover any open bays or slots. Replace any other missing case parts. (You can substitute a CD-ROM drive if no compatible bay cover is available.) Some cases require specific (proprietary) parts. If we don't have extras on hand, we unfortunately have to recycle them... <br />
* Ensure that all components are securely fastened.<br />
* Check for/remove any loose screws or unnecessary cables. If you're unsure of how to do this, ask an instructor.<br />
----<br />
'''Is there Microsoft Branding (Certificates of Authenticity)? Asset tags? (identifying the last owner)? Or branded hardware tags on the faceplate (identifying original components such as RAM, HDD, Optical Drive etc)?'''<br />
* If there are, remove them. '''DO NOT remove FG-PDX, "uncovered electronic device" Processor/graphics tags or Green Light stickers.'''<br />
----<br />
'''Clean and vacuum out box'''<br />
* There is a vacuum available on the Build supply shelf by the cleaning supplies. The most effective way to clean out a box is to use a paint brush to kick up the dust while vacuuming.<br />
----<br />
'''Test battery'''<br />
* Grab a voltmeter and set it to DCV=20. Place one wand on the battery itself and one wand on a metal part of the case. The battery passes if its voltage shows as 3.0 or greater. <br />
----<br />
'''Install RAM'''<br />
* For DDR2, try speed 533 (PC3200) first. If that doesn't work, try other numbers. Sometimes the BIOS will tell you the needed speed.<br />
* If your system's memory slots will not accept DDR2 memory, they will require another type. DDR3 is acceptable - ask your instructor for DDR3 RAM. DDR1 systems should be rejected and sent back to Prebuild as yellow-light systems.<br />
** NOTE: Usually RAM should be paired in dual channels for higher performance (i.e., 2 sticks of RAM used in specific slots, often color-coded). Make sure you try all combinations of slots if you are having trouble getting the system to recognize the RAM, and consult an Instructor if you're still having trouble.<br />
* Write down what type and speed of RAM you installed; this info will come in handy later.<br />
----<br />
'''Install video card if needed'''<br />
* You do not need to install a video card if there is functional onboard video. <br />
* Ask an instructor if you need a PCI-e card; AGP cards are available in the Build room.<br />
----<br />
'''Initial power on''' <br />
* See if expected memory value is displayed during POST or in BIOS. <br />
----<br />
'''Power down'''<br />
----<br />
'''Remove floppy drive if possible'''<br />
* Remove the floppy drive if you can find a matching face plate to cover it. If there are no covers available, you can leave the drive in, but make sure it is unplugged from the motherboard and power supply. Make sure the floppy drive (sometimes called Diskette) is disabled in BIOS and removed from the boot sequence if possible. <br />
----<br />
'''Check for onboard NIC ((Network Interface Card, or ethernet.)'''<br />
* If none can be found, install a network card.<br />
----<br />
'''Install hard drive'''<br />
* Get the appropriately sized (according to spec sheet) hard drive from the supply shelf, or from an instructor. Also check to see if you need an IDE or SATA hard drive and make sure you have the necessary cables and power connections.<br />
* Install the hard drive and attach it to the power supply and motherboard. (If the drive has IDE connections, make sure the jumper is set to the Master position. Ask an instructor for more info.)<br />
* You will need to ask an instructor for any hard drives higher than 120 GB.<br />
----<br />
'''Install sound card if needed'''<br />
* If there's onboard sound, there's no need to install a sound card.<br />
----<br />
'''Install CD/CDRW/DVD/DVD-RW Drive(s)'''<br />
* If there are already optical drives installed in your system, take a look at their face-plates to determine their capabilities. If the drives are within spec for the box you're building and have IDE connections, confirm they're properly jumpered as Master/Slave, or just Master if there's only one drive. <br />
* If the the drives are outside of spec, pull them out and sort them into the appropriate boxes on the Build shelves. Replace with appropriate drives as needed.<br />
---- <br />
'''Cover open slots and bays'''<br />
* Make sure you have coverings for all spaces that will not be filled with a card or drive. Look at similar cases for examples of what case pieces may look like. Be sure that these are screwed in tight and test them by pushing on each with your finger. If a slot cover falls out while a computer is on it can '''short out the motherboard.'''<br />
----<br />
<br />
== BOOT AND [[Entering BIOS|ENTER BIOS]] ==<br />
----<br />
'''Attach monitor, keyboard, mouse, network, sound and power cords'''<br />
----<br />
'''Enter BIOS setup'''<br />
* Turn on the computer. The keystroke to enter BIOS should be displayed on the flash screen, before bootup, as well as the Boot Menu key, if applicable. If no flash screen appears, you have to guess the BIOS keystroke. Delete, Escape, Enter, F1, F2, F9, F10, and F12 are typical. <br />
* Get into BIOS, and '''write down both the BIOS and Boot Menu keystrokes;''' this info will come in handy later.<br />
----<br />
'''Check date and time''' <br />
* Check date and time in BIOS and change to the correct time if needed.<br />
----<br />
'''Restore BIOS defaults'''<br />
* You might need to search around to find the BIOS values that need checking. While you search, enjoy the pleasure of learning about BIOS configuration! <br />
----<br />
'''Detect hard drive'''<br />
* Search BIOS to see if it is recognizing the hard drive. <br />
----<br />
'''Set boot order'''<br />
* It should be: '''1st-CD-ROM'''; '''2nd-Hard drive. If possible, disable all other boot devices such as floppy drive or network boot from the boot sequence.<br />
----<br />
'''Where possible, edit any/all of the following settings:'''<br />
* Enable USB ports<br />
* Enable Hyper-threading<br />
* Disable Quick Boot<br />
* Disable Logo Display (Sometimes called Silent or Quiet Boot)<br />
* Disable Plug & Play OS<br />
* SATA Operation: set to RAID Autodetect/AHCI<br />
----<br />
'''Save and exit BIOS'''<br />
* The system should reboot to the Ubuntu operating system. <br />
----<br />
<br />
== HARDWARE AND SOFTWARE TESTING ==<br />
----<br />
'''Login to the system'''<br />
* username will be '''Default User''' <br />
* password = '''freegeek''' <br />
----<br />
'''Check for 64-bit capability'''<br />
* From a terminal, type "'''sudo lshw -c processor | grep width'''" and press enter. Type the password: "freegeek" and press enter again. (Don't worry that the password text doesn't show on the screen; it is hidden for security reasons.)<br />
* The reading you get should be "width: 64." If your system reads "width: 32" instead, check with your instructor; this system will have to be recycled.<br />
----<br />
'''Run "basiccheck"''' <br />
* From a terminal, type "'''basiccheck'''" Read through each of the tests and verify that they pass. When the last test is finished, close the terminal.<br />
* Refer to the basiccheck checklists hanging on the supply shelves to help determine whether each test passes or not. <br />
----<br />
'''Learn to install a program through command line'''<br />
* Open up a terminal and type "sudo apt-get install gimp" and press "Enter." This will install the photo editing program called Gimp. You may have to type "freegeek" and press enter again for the installation to proceed.<br />
----<br />
'''Learn to install a program through the Graphical User Interface (GUI - the mouse)'''<br />
* The first place to look for software to add is in the Ubuntu Software Center (Applications>Ubuntu Software Center). This gives you access to the Ubuntu supported applications plus many others. Search for "k3b" and install it. K3b is a CD/DVD authoring program.<br />
----<br />
'''Test USB ports'''<br />
* Plug in a USB mouse, see that the cursor moves and can interact with things. Repeat with all USB ports, including front ports, if any.<br />
----<br />
'''Play an audio CD'''<br />
* Do you hear what you expect? Is it loud enough to be heard easily? Repeat for each CD-ROM drive. Repeat for additional sound ports. <br />
* Note if any standard sound ports do not work. These will need to be covered with electrical tape. If all onboard sound does not work, install a sound card.<br />
----<br />
'''Read data CD'''<br />
* If your file browser sees files on the drive, the CD-ROM can read files. Repeat for each CD-ROM drive. <br />
----<br />
'''If you have a DVD Drive, Read DVD'''<br />
* If your file browser sees the file, the DVD-ROM can read files. If you are prompted to search for suitable plugins or codecs, '''please do not do this!''' The test still passes. Repeat for each DVD-ROM drive.<br />
----<br />
'''If you have an Optical Drive with CD-RW function, Test CD Writing'''<br />
* Insert a CD-RW disc into the drive and open Brasero Disc Burning (under '''Applications >> Sound & Video'''.) Select '''Data Project''', click on the green +, then select '''examples.desktop''' and click '''Add'''. Click '''Burn''' in the lower right-hand corner. A new window will pop-up with a few options. If available, select '''Use burnproof''' and '''Burn the image directly without saving it to disc''' and click '''Burn'''. When the disc is done, verify that it contains the examples file by re-inserting the disc and seeing what pops up on the desktop. <br />
* Blank the disc using Brasero by selecting '''Tools >> Blank'''. If available, '''uncheck the "Fast Blank" option.''' If blanking does not work, the drive may still be completely functional! Ask your instructor about software bug workarounds. <br />
----<br />
'''If you have an Optical Drive with DVD-RW function, Test DVD Writing'''<br />
* Insert a DVD-RW disc into the drive and in the Brasero file browser follow the same steps as above to burn a data project. When the disc is done, verify that it contains the examples file by re-inserting the disc and seeing what pops up on the desktop.<br />
*Blank the disc using Brasero by selecting '''Tools >> Blank'''. If available, '''uncheck "Fast Blank."''' Again, blanking errors may not indicate a bad drive. Ask your instructor for more information. <br />
----<br />
'''Test for booting from live CD'''<br />
* Place Live CD in drive and restart the computer. The system should boot from the live CD. <br />
* Select language: English. Scroll down on the following screen to '''Boot to first hard drive''' and press enter. This should take you to the normal Ubuntu log-in screen. <br />
----<br />
'''Remove all CDs and DVDs from the drive(s)''' <br />
----<br />
'''Reboot the system'''<br />
* Open a terminal and type '''sudo reboot.''' Wait while it reboots, and ensure that the system powers on and offers a login screen without user intervention (e.g. requiring you to "press F1 to boot.") <br />
* If it doesn't boot smoothly, double-check your boot priority options in BIOS and try again.<br />
----<br />
'''Run "printme" from terminal'''<br />
* From a terminal, type "'''printme,'''" this will generate a questionnaire in Command Line. <br />
* Refer to your written notes for the RAM type and speed, the BIOS key and Boot Menu key, if applicable. <br />
* '''When it asks what is notable about this system, refer to the white board for what should be included, and ask your instructor for any needed clarification.''' Press enter to create a web document.<br />
---- <br />
'''Check in with Build Instructor''' <br />
* The Build Instructor will check the printme and edit it to sign it off. <br />
* Your instructor may ask you to replace certain components, which will require re-running the "printme" form. Some changes may also need to be made in the web browser. If your instructor gives the "thumbs-up," proceed to the next step. <br />
----<br />
'''Save Printme to the desktop'''<br />
* After your Build Instructor has inspected the system, click "Print" from the printme on the web document. "Choose "Print to File" and select "Desktop" as the folder in which to save it. Name the file "Build Printme" and click print. <br />
----<br />
'''Shut down system and place on QC shelf'''<br />
* Open a terminal and type "sudo halt" then press enter. When the system has shut down, unplug all cables, double-check that the case is secured properly, and place it on the QC shelf in the Build room.<br />
----<br />
'''Clean up work area if it is your last Assembly of the day'''<br />
* Please put all tools away, throw out any garbage or sticker remains, put screws in the appropriate bins, wrap cords around your keyboard and mouse, turn off your speakers and monitor, and generally straighten up.<br />
<br />
== Thank You For Volunteering! ==<br />
* If you are interested in further learning opportunities after finishing the Build program, ask your instructor about '''Post-Build options!'''<br />
* We want to know what you think! Go to '''http://freegeek.limequery.com/48992/lang-en''' to fill out the '''Build Program Exit Survey.'''<br />
<br />
<br />
<noinclude>[[Category:Build]]</noinclude></div>Alambhttp://wiki.freegeek.org/index.php?title=File:Build-specs.odt&diff=64143File:Build-specs.odt2012-09-09T02:14:38Z<p>Alamb: uploaded a new version of "File:Build-specs.odt"</p>
<hr />
<div></div>Alambhttp://wiki.freegeek.org/index.php?title=File:Build-specs.odt&diff=64142File:Build-specs.odt2012-09-09T02:12:21Z<p>Alamb: uploaded a new version of "File:Build-specs.odt"</p>
<hr />
<div></div>Alambhttp://wiki.freegeek.org/index.php?title=QC_checklist&diff=64141QC checklist2012-09-08T23:23:11Z<p>Alamb: </p>
<hr />
<div>'''Welcome to the Build Workshop!''' Quality checking a few systems that others have built will be your first step, then you'll be ready to move on to assembling and checking software on systems. <br />
<br />
'''Work through every step as well as you can, and then ask a neighbor or your Build instructor if you still have questions.''' Try and learn the reason for each of the steps: this knowledge will come in handy later when, inevitably, things aren't going as smoothly.<br />
<br />
'''Use your resources!''' There are lots available to you - your neighbor, the Build assistants and instructors and, of course, the internet. Searching the web for answers to the challenge you are facing is one of the best ways to learn. You can also access tips and troubleshooting ideas on our wiki (http://wiki.freegeek.org) under [[Build tips]] or in our Troubleshooting Guide (http://wiki.freegeek.org/index.php/Build_Troubleshooting_Guide). <br />
{| border="2" fontname="Nimbus Sans" fontsize="12"<br />
|-<br />
== BEFORE YOU POWER ON ==<br />
----<br />
'''Check what needs to be quality checked'''<br />
* Grab a system from the QC shelves in the build room, and carry it to an open Build station.<br />
----<br />
'''Do you hear a rattling noise, caused by a screw or other loose component, upon moving the system?''' <br />
* If so, find the culprit and secure/remove it. <br />
----<br />
'''Is the case properly put together and secure?''' <br />
* If not, fix it!<br />
----<br />
'''Are all slots and bays covered?''' <br />
* If not, cover 'em! Check to make sure they're screwed in tightly by pushing on each one with your finger - if a slot cover falls out it can '''short out the motherboard.'''<br />
----<br />
'''Do you see more than one video, sound, or network ports?''' <br />
* Later, when you're testing audio, headphone jacks and standard sound ports should be tested.<br />
* Orange/Black/Gray sound ports are surround sound and do not need to be tested. <br />
*Any damaged ports will need to be covered with electrical tape or port covers. If you see two identical uncovered ports, one integrated and one on a card, ask your instructor how to proceed.<br />
----<br />
'''Is there Microsoft Branding? (Certificates of Authenticity) Asset tags (identifying the last owner)? Or branded hardware tags on the faceplate (identifying original components such as RAM, HDD, Optical Drive etc)?'''<br />
* If there is, take them off. '''DO NOT remove FG-PDX, "uncovered electronic device" Processor/graphics tags or Green Light stickers.'''<br />
----<br />
'''Is the system exterior clean?''' <br />
* If not, use cleaner and rag to clean. The vacuum cleaner will help remove dust clogged in case fans. Hand sanitizer, Goo Gone and/or isopropyl (rubbing) alcohol can help loosen any stickers; ask your instructor where to find scraping tools to remove them.<br />
----<br />
'''Open up the system and check inside for:'''<br />
# Blown capacitors (If found, the system must be rejected!)<br />
# What type of DDR RAM your system has installed - write this down<br />
# The RAM speed (will be the second number on the sticker) - write this down<br />
# Any dust accumulation - please vacuum or brush it out!<br />
<br />
== BOOT AND [[Entering BIOS|ENTER BIOS]] ==<br />
----<br />
'''Get into BIOS (Setup)''' <br />
* Turn on the computer. If you see a flash screen before boot-up, it will give the keystroke to enter BIOS, and the keystroke for a Boot Menu, if applicable. Delete, Escape, F1, F2, F9, F10, F12 and Enter are typical. <br />
*Get into BIOS, and write down both the BIOS and Boot Menu keystrokes; this info will come in handy later. <br />
*If you see "'''Ubuntu'''" on your screen, you have gone too far; reboot from the power button icon on the bottom-right corner of the screen, and try again. All BIOS are different. Feel free to explore how the BIOS you're using is set up. <br />
----<br />
'''Check boot order''' <br />
* It should be: '''1st- CD-ROM'''; '''2nd-Hard Drive'''. If possible, disable other boot device options, such as floppy (sometimes called Diskette), network, or USB. Depending on the BIOS model, you may need to enable active drive ports and disable inactive ones, in addition to arranging them in the boot sequence.<br />
----<br />
'''Save and exit BIOS'''<br />
* The system should boot to the Ubuntu operating system.<br />
----<br />
<br />
== HARDWARE AND SOFTWARE TESTING ==<br />
----<br />
'''Login to the system'''<br />
* username will be '''Default User''' <br> password = '''freegeek''' <br />
----<br />
'''What Specification Category does the system fall under?'''<br />
* Compare the CPU speed listed on the system's Green Light sticker with the '''FREE GEEK Specification Sheet,''' or "Spec Sheet," on the wall to determine the category of specifications, or "specs," to which the system should be built. (Keep in mind that FG-PDX's are determined by their sticker, not their processor.) If you aren't sure what type of box you are working with, please check with your instructor to see how to proceed.<br />
----<br />
'''Is the system standard?''' <br />
* Check the '''Spec Sheet''' on the wall to see what else should be installed for your spec category, then compare your system's spec category to the '''Build Printme''' document saved to the Desktop. Does the box have any parts that are extra, or missing, or built to incorrect specifications? Take out and replace parts as necessary to ensure that all specs are correct, paying special attention to properly seating/securing parts to ensure that they won't come loose. Ask an instructor if you are unsure how to do this.<br />
----<br />
'''Update the software'''<br />
* Click on '''System''' >> '''Administration''' >> '''Update Manager'''. When the Update Manager pops up, click "Check" to find updates, then if any updates appear, click "Install All." It may take some time to download and install packages, so feel free to continue on with other steps while this runs in the background.<br />
----<br />
'''Drag the terminal icon to the top panel'''<br />
* Go to '''Applications''' >> '''Accessories''' >> '''Terminal'''. Use the mouse to click and hold the button down over the Terminal icon, drag, then release the mouse button when the icon hovers over the black panel along the top of the screen.<br />
----<br />
'''Stress test the system for a few minutes''' <br />
* Open a terminal and run "'''stress-test'''". Wait a few minutes while it runs, and look for error messages. If you want to know more about what it's doing, open up another terminal and run "man stress". This may take some time; feel free to continue on to the next step while you wait.<br />
----<br />
'''Run "basiccheck"''' <br />
* Click on the terminal icon to open it. Type "'''basiccheck'''", then press enter to begin the program. There are basiccheck checklists hanging on the supply shelves which will help with verifying whether each test passes or not. Feel free to ask your peers and the instructor what parts of basiccheck mean so that you understand what each test is checking. When you're finished, close the terminal.<br />
----<br />
'''Test USB'''<br />
* Plug in a USB mouse, see that the cursor moves and can interact with things. <br />
* Repeat with all USB ports, including ports on the front of the system, if any.<br />
* If any ports don't work, they may need to be enabled in BIOS; ask your instructor how to proceed.<br />
----<br />
'''Check date and time''' <br />
* Displayed in the right corner of your top panel. If incorrect:<br />
# Make sure network cable is plugged in.<br />
# Right-click on the time and then click the "Preferences" button.<br />
# Click on the "Time Settings" button.<br />
# Manually adjust date and time. Press "Set System Time" to save, then close the Clock Preferences window.<br />
----<br />
'''Play an audio CD''' <br />
* Do you hear what you expect? Is it loud enough to be heard easily? Repeat for each optical drive. Also repeat for any additional sound ports. If any sound ports (typically colored green, sometimes blue) don't play audio, cover them up with port covers or electrical tape. '''If you have functional onboard sound, and a sound card, the card will need to be removed and replaced with a slot cover.'''<br />
* If you have surround sound ports (usually orange and gray) ignore them; we do not have the means to test this function. <br />
----<br />
'''Read data CD''' <br />
* If your file browser (listed under '''Places''' in the top panel) sees files on the drive, it can read data files. Repeat for each optical drive. <br />
----<br />
'''If you have a DVD Drive, Read DVD''' <br />
* If your file browser sees the file, the DVD-ROM can read files. If you are prompted to search for a suitable plugin or codec, '''please do not do this!''' The test still passes. Repeat for each DVD-ROM drive.<br />
----<br />
'''If you have an Optical Drive with CD-RW function, Test CD Writing'''<br />
* Insert a CD-RW disc into the drive and open Brasero Disc Burning (under '''Applications''' >> '''Sound & Video'''.) Select '''Data Project''', click on the green '''+''', then select '''examples.desktop''' and click '''Add'''. Click '''Burn''' in the lower right-hand corner. A new window will pop-up with a few options. If available, select '''Use burnproof''' and '''Burn the image directly without saving it to disc''' and click '''Burn'''. When the disc is done, verify that it contains the examples file by re-inserting the disc and seeing what pops up on the desktop.<br />
* Blank the disc using Brasero by selecting '''Tools''' >> '''Blank'''. If available, '''uncheck the "Fast Blank" option.''' If blanking does not work, the drive may still be completely functional! Ask your instructor about software bug workarounds. <br />
----<br />
'''If you have an Optical Drive with DVD-RW function, Test DVD Writing'''<br />
* Insert a DVD-RW disc into the drive and in the Brasero file browser follow the same steps as above to burn a data project. When the disc is done, verify that it contains the examples file by re-inserting the disc and seeing what pops up on the desktop.<br />
* Blank the disc using Brasero by selecting '''Tools''' >> '''Blank'''. If available, uncheck "Fast Blank." Again, blanking errors may not indicate a bad drive. Ask your instructor for more information.<br />
----<br />
'''Test for booting from live CD'''<br />
* Place Live CD in drive and restart the computer. The system should boot from the live CD. <br />
* Select language: English. Scroll down on the following screen to '''Boot to first hard drive''' and press enter. This should take you to the normal Ubuntu log-in screen. <br />
---- <br />
'''Remove all CDs and DVDs from the drive(s)'''<br />
----<br />
'''Reboot the system'''<br />
* Open a terminal and type '''sudo reboot.''' Wait while it reboots, and ensure that the system powers on and offers a login screen without user intervention (e.g. requiring you to "press F1 to boot.") <br />
* If it doesn't boot smoothly, double-check your boot priority options in BIOS and try again.<br />
----<br />
'''Run "printme" from terminal'''<br />
* From a terminal, type "'''printme,'''" this will generate a questionnaire in Command Line. <br />
* Refer to your written notes for the RAM type and speed, the BIOS key and Boot Menu key, if applicable. <br />
* '''When it asks what is notable about this system, refer to the white board for what should be included, and ask your instructor for any needed clarification.''' Press enter to create a web document.<br />
----<br />
'''Copy system ID (IMPORTANT!)'''<br />
* Copy the system ID from the printme onto a blank sticker and put it on back of computer, ideally in a location that isn't covering any fans, other ventilation, or removable case parts such as slot covers.<br />
----<br />
'''Add Free Geek Sticker'''<br />
* Affix on the front of the system, in a sensible location! (Usually adjacent to or above/below the Processor tag)<br />
----<br />
'''Check in with Build Instructor''' <br />
* The Build Instructor will check the printme and edit it to sign it off. <br />
* Your instructor may ask you to replace certain components, which will require re-running the "printme" form. Some changes may also need to be made in the web browser. If your instructor gives the "thumbs-up," proceed to the next step. <br />
----<br />
'''Save Printme to the Desktop'''<br />
* After your Build Instructor has inspected the system, click "Print" in the browser that opens. Choose "Print to file." Save the file to the Desktop and name it "QC Printme", then click "Print" to save. Click on the QC Printme icon on the Desktop to open it up. <br />
----<br />
'''Enable network printers:'''<br />
* Go to '''System>>Administration>>Printing'''<br />
* Select '''Server>>Settings''' and check the box marked <i>Show Printers Shared by Other Systems</i> and click OK.<br />
* Wait for a few moments and click the refresh icon. A selection of printers should appear.<br />
----<br />
'''Print a hard copy of Printme'''<br />
* Close the "Printing - localhost" window that opens and select the "build" printer from the Print menu once it appears. Click Print and retrieve the sheet from the printer in the back (SW) corner of the room. <br />
* Have your Build Instructor sign off on the printed sheet. Then fold it in half (lengthwise) and tape it to the top of the system (the side of the page with the instructor's initials facing up.)<br />
----<br />
'''Shut down and shelve the system''' <br />
* Open a terminal and type "sudo halt" then press enter. When the system has shut down, unplug all cables, double-check that the case is secured properly, and ask a build instructor where to put the system once shutdown is complete. <br />
----<br />
'''Clean up work area if it is your last QC of the day''' <br />
* Please put all tools away, throw out any garbage or sticker remains, put screws in the appropriate bins, wrap cords around your keyboard and mouse, turn off your speakers and monitor, and generally straighten up. <br />
|}<br />
<br />
<br />
<br />
<noinclude>[[Category:Build]]</noinclude></div>Alambhttp://wiki.freegeek.org/index.php?title=Assembly_checklist&diff=64140Assembly checklist2012-09-08T23:18:57Z<p>Alamb: </p>
<hr />
<div>'''Work through every step as well as you can, and then ask a neighbor or your build instructor if you still have questions.''' Try and learn the reason for each of the steps: this knowledge will come in handy later when, inevitably, things aren't going as smoothly.<br />
<br />
'''Use your resources!''' There are lots available to you - your neighbor, the Build assistants and instructors and, of course, the internet. Searching the web for answers to the challenge you are facing is one of the best ways to learn. You can also access tips and troubleshooting ideas on our wiki (http://wiki.freegeek.org) under [[Build tips]] or in our Troubleshooting Guide (http://wiki.freegeek.org/index.php/Build_Troubleshooting_Guide). <br />
<br />
Supplies like cards, rails, hard drives, cleaning supplies, etc. can be found on the metal racks in the center of the build workshop. Here you will also find a box containing an assortment of common DDR memory.<br />
{| border="2" fontname="Nimbus Sans" fontsize="12"<br />
|-<br />
== BEFORE YOU POWER ON ==<br />
----<br />
'''Check what needs to be built on the white board''' <br />
* Head to the warehouse and scope out a system you would like to build. <br />
*'''Be sure to pay attention to the Green Light label.''' It will give you a lot of important information, like the type of video, if it did not POST, if the processor is Dual Core, etc. Make sure that the box you are about to Build is appropriate for its spec.<br />
* If everything looks good, Grab the system from the warehouse, take it back to your build station, and figure out how to pop it open. <br />
----<br />
'''Check capacitors'''<br />
* Visually inspect motherboard capacitors for bulges/leaks. If you find one, ask your instructor for a "Rejected" sticker. <br />
----<br />
'''Secure the case'''<br />
* Cover any open bays or slots. Replace any other missing case parts. (You can substitute a CD-ROM drive if no compatible bay cover is available.) Some cases require specific (proprietary) parts. If we don't have extras on hand, we unfortunately have to recycle them... <br />
* Ensure that all components are securely fastened.<br />
* Check for/remove any loose screws or unnecessary cables. If you're unsure of how to do this, ask an instructor.<br />
----<br />
'''Is there Microsoft Branding (Certificates of Authenticity)? Asset tags? (identifying the last owner)? Or branded hardware tags on the faceplate (identifying original components such as RAM, HDD, Optical Drive etc)?'''<br />
* If there are, remove them. '''DO NOT remove FG-PDX, "uncovered electronic device" Processor/graphics tags or Green Light stickers.'''<br />
----<br />
'''Clean and vacuum out box'''<br />
* There is a vacuum available on the Build supply shelf by the cleaning supplies. The most effective way to clean out a box is to use a paint brush to kick up the dust while vacuuming.<br />
----<br />
'''Test battery'''<br />
* Grab a voltmeter and set it to DCV=20. Place one wand on the battery itself and one wand on a metal part of the case. The battery passes if its voltage shows as 3.0 or greater. <br />
----<br />
'''Install RAM'''<br />
* For DDR2, try speed 533 (PC3200) first. If that doesn't work, try other numbers. Sometimes the BIOS will tell you the needed speed.<br />
* If your system's memory slots will not accept DDR2 memory, they will require another type. DDR3 is acceptable - ask your instructor for DDR3 RAM. DDR1 systems should be rejected and sent back to Prebuild as yellow-light systems.<br />
** NOTE: Usually RAM should be paired in dual channels for higher performance (i.e., 2 sticks of RAM used in specific slots, often color-coded). Make sure you try all combinations of slots if you are having trouble getting the system to recognize the RAM, and consult an Instructor if you're still having trouble.<br />
* Write down what type and speed of RAM you installed; this info will come in handy later.<br />
----<br />
'''Install video card if needed'''<br />
* You do not need to install a video card if there is functional onboard video. <br />
* Ask an instructor if you need a PCI-e card; AGP cards are available in the Build room.<br />
----<br />
'''Initial power on''' <br />
* See if expected memory value is displayed during POST or in BIOS. <br />
----<br />
'''Power down'''<br />
----<br />
'''Remove floppy drive if possible'''<br />
* Remove the floppy drive if you can find a matching face plate to cover it. If there are no covers available, you can leave the drive in, but make sure it is unplugged from the motherboard and power supply. Make sure the floppy drive (sometimes called Diskette) is disabled in BIOS and removed from the boot sequence if possible. <br />
----<br />
'''Check for onboard NIC ((Network Interface Card, or ethernet.)'''<br />
* If none can be found, install a network card.<br />
----<br />
'''Install hard drive'''<br />
* Get the appropriately sized (according to spec sheet) hard drive from the supply shelf, or from an instructor. Also check to see if you need an IDE or SATA hard drive and make sure you have the necessary cables and power connections.<br />
* Install the hard drive and attach it to the power supply and motherboard. (If the drive has IDE connections, make sure the jumper is set to the Master position. Ask an instructor for more info.)<br />
* You will need to ask an instructor for any hard drives higher than 120 GB.<br />
----<br />
'''Install sound card if needed'''<br />
* If there's onboard sound, there's no need to install a sound card.<br />
----<br />
'''Install CD/CDRW/DVD/DVD-RW Drive(s)'''<br />
* If there are already optical drives installed in your system, take a look at their face-plates to determine their capabilities. If the drives are within spec for the box you're building and have IDE connections, confirm they're properly jumpered as Master/Slave, or just Master if there's only one drive. <br />
* If the the drives are outside of spec, pull them out and sort them into the appropriate boxes on the Build shelves. Replace with appropriate drives as needed.<br />
---- <br />
'''Cover open slots and bays'''<br />
* Make sure you have coverings for all spaces that will not be filled with a card or drive. Look at similar cases for examples of what case pieces may look like. Be sure that these are screwed in tight and test them by pushing on each with your finger. If a slot cover falls out while a computer is on it can '''short out the motherboard.'''<br />
----<br />
<br />
== BOOT AND [[Entering BIOS|ENTER BIOS]] ==<br />
----<br />
'''Attach monitor, keyboard, mouse, network, sound and power cords'''<br />
----<br />
'''Enter BIOS setup'''<br />
* Turn on the computer. The keystroke to enter BIOS should be displayed on the flash screen, before bootup, as well as the Boot Menu key, if applicable. If no flash screen appears, you have to guess the BIOS keystroke. Delete, Escape, Enter, F1, F2, F9, F10, and F12 are typical. <br />
* Get into BIOS, and '''write down both the BIOS and Boot Menu keystrokes;''' this info will come in handy later.<br />
----<br />
'''Check date and time''' <br />
* Check date and time in BIOS and change to the correct time if needed.<br />
----<br />
'''Restore BIOS defaults'''<br />
* You might need to search around to find the BIOS values that need checking. While you search, enjoy the pleasure of learning about BIOS configuration! <br />
----<br />
'''Detect hard drive'''<br />
* Search BIOS to see if it is recognizing the hard drive. <br />
----<br />
'''Set boot order'''<br />
* It should be: '''1st-CD-ROM'''; '''2nd-Hard drive. If possible, disable all other boot devices such as floppy drive or network boot from the boot sequence.<br />
----<br />
'''Where possible, edit any/all of the following settings:'''<br />
* Enable USB ports<br />
* Enable Hyper-threading<br />
* Disable Quick Boot<br />
* Disable Logo Display (Sometimes called Silent or Quiet Boot)<br />
* Disable Plug & Play OS<br />
* SATA Operation: set to RAID Autodetect/AHCI<br />
----<br />
'''Save and exit BIOS'''<br />
* The system should reboot to the Ubuntu operating system. <br />
----<br />
<br />
== HARDWARE AND SOFTWARE TESTING ==<br />
----<br />
'''Login to the system'''<br />
* username will be '''Default User''' <br />
*password = '''freegeek''' <br />
----<br />
'''Run "basiccheck"''' <br />
* From a terminal, type "'''basiccheck'''" Read through each of the tests and verify that they pass. When the last test is finished, close the terminal.<br />
* Refer to the basiccheck checklists hanging on the supply shelves to help determine whether each test passes or not. <br />
----<br />
'''Learn to install a program through the Graphical User Interface (GUI - the mouse)'''<br />
* The first place to look for software to add is in the Ubuntu Software Center (Applications>Ubuntu Software Center). This gives you access to the Ubuntu supported applications plus many others. Search for "k3b" and install it. K3b is a CD/DVD authoring program.<br />
----<br />
'''Learn to install a program through command line'''<br />
* Open up a terminal and type "sudo apt-get install gimp" and press "Enter." This will install the photo editing program called Gimp. The system will ask for your password; type "freegeek" and press enter. Don't worry that the text doesn't show on the screen; it is hidden for security reasons.<br />
----<br />
'''Test USB ports'''<br />
* Plug in a USB mouse, see that the cursor moves and can interact with things. Repeat with all USB ports, including front ports, if any.<br />
----<br />
'''Play an audio CD'''<br />
* Do you hear what you expect? Is it loud enough to be heard easily? Repeat for each CD-ROM drive. Repeat for additional sound ports. <br />
* Note if any standard sound ports do not work. These will need to be covered with electrical tape. If all onboard sound does not work, install a sound card.<br />
----<br />
'''Read data CD'''<br />
* If your file browser sees files on the drive, the CD-ROM can read files. Repeat for each CD-ROM drive. <br />
----<br />
'''If you have a DVD Drive, Read DVD'''<br />
* If your file browser sees the file, the DVD-ROM can read files. If you are prompted to search for suitable plugins or codecs, '''please do not do this!''' The test still passes. Repeat for each DVD-ROM drive.<br />
----<br />
'''If you have an Optical Drive with CD-RW function, Test CD Writing'''<br />
* Insert a CD-RW disc into the drive and open Brasero Disc Burning (under '''Applications >> Sound & Video'''.) Select '''Data Project''', click on the green +, then select '''examples.desktop''' and click '''Add'''. Click '''Burn''' in the lower right-hand corner. A new window will pop-up with a few options. If available, select '''Use burnproof''' and '''Burn the image directly without saving it to disc''' and click '''Burn'''. When the disc is done, verify that it contains the examples file by re-inserting the disc and seeing what pops up on the desktop. <br />
* Blank the disc using Brasero by selecting '''Tools >> Blank'''. If available, '''uncheck the "Fast Blank" option.''' If blanking does not work, the drive may still be completely functional! Ask your instructor about software bug workarounds. <br />
----<br />
'''If you have an Optical Drive with DVD-RW function, Test DVD Writing'''<br />
* Insert a DVD-RW disc into the drive and in the Brasero file browser follow the same steps as above to burn a data project. When the disc is done, verify that it contains the examples file by re-inserting the disc and seeing what pops up on the desktop.<br />
*Blank the disc using Brasero by selecting '''Tools >> Blank'''. If available, '''uncheck "Fast Blank."''' Again, blanking errors may not indicate a bad drive. Ask your instructor for more information. <br />
----<br />
'''Test for booting from live CD'''<br />
* Place Live CD in drive and restart the computer. The system should boot from the live CD. <br />
* Select language: English. Scroll down on the following screen to '''Boot to first hard drive''' and press enter. This should take you to the normal Ubuntu log-in screen. <br />
----<br />
'''Remove all CDs and DVDs from the drive(s)''' <br />
----<br />
'''Reboot the system'''<br />
* Open a terminal and type '''sudo reboot.''' Wait while it reboots, and ensure that the system powers on and offers a login screen without user intervention (e.g. requiring you to "press F1 to boot.") <br />
* If it doesn't boot smoothly, double-check your boot priority options in BIOS and try again.<br />
----<br />
'''Run "printme" from terminal'''<br />
* From a terminal, type "'''printme,'''" this will generate a questionnaire in Command Line. <br />
* Refer to your written notes for the RAM type and speed, the BIOS key and Boot Menu key, if applicable. <br />
* '''When it asks what is notable about this system, refer to the white board for what should be included, and ask your instructor for any needed clarification.''' Press enter to create a web document.<br />
---- <br />
'''Check in with Build Instructor''' <br />
* The Build Instructor will check the printme and edit it to sign it off. <br />
* Your instructor may ask you to replace certain components, which will require re-running the "printme" form. Some changes may also need to be made in the web browser. If your instructor gives the "thumbs-up," proceed to the next step. <br />
----<br />
'''Save Printme to the desktop'''<br />
* After your Build Instructor has inspected the system, click "Print" from the printme on the web document. "Choose "Print to File" and select "Desktop" as the folder in which to save it. Name the file "Build Printme" and click print. <br />
----<br />
'''Shut down system and place on QC shelf'''<br />
* Open a terminal and type "sudo halt" then press enter. When the system has shut down, unplug all cables, double-check that the case is secured properly, and place it on the QC shelf in the Build room.<br />
----<br />
'''Clean up work area if it is your last Assembly of the day'''<br />
* Please put all tools away, throw out any garbage or sticker remains, put screws in the appropriate bins, wrap cords around your keyboard and mouse, turn off your speakers and monitor, and generally straighten up. <br />
<br />
<br />
<br />
== Thank You For Volunteering! ==<br />
* If you are interested in further learning opportunities after finishing the Build program, ask your instructor about '''Post-Build options!'''<br />
* We want to know what you think! Go to '''http://freegeek.limequery.com/48992/lang-en''' to fill out the '''Build Program Exit Survey.'''<br />
<br />
<br />
<noinclude>[[Category:Build]]</noinclude></div>Alambhttp://wiki.freegeek.org/index.php?title=Assembly_checklist&diff=64139Assembly checklist2012-09-08T23:18:09Z<p>Alamb: </p>
<hr />
<div>'''Work through every step as well as you can, and then ask a neighbor or your build instructor if you still have questions.''' Try and learn the reason for each of the steps: this knowledge will come in handy later when, inevitably, things aren't going as smoothly.<br />
<br />
'''Use your resources!''' There are lots available to you - your neighbor, the Build assistants and instructors and, of course, the internet. Searching the web for answers to the challenge you are facing is one of the best ways to learn. You can also access tips and troubleshooting ideas on our wiki (http://wiki.freegeek.org) under [[Build tips]] or in our Troubleshooting Guide (http://wiki.freegeek.org/index.php/Build_Troubleshooting_Guide). <br />
<br />
Supplies like cards, rails, hard drives, cleaning supplies, etc. can be found on the metal racks in the center of the build workshop. Here you will also find a box containing an assortment of common DDR and DDR2 memory.<br />
{| border="2" fontname="Nimbus Sans" fontsize="12"<br />
|-<br />
== BEFORE YOU POWER ON ==<br />
----<br />
'''Check what needs to be built on the white board''' <br />
* Head to the warehouse and scope out a system you would like to build. <br />
*'''Be sure to pay attention to the Green Light label.''' It will give you a lot of important information, like the type of video, if it did not POST, if the processor is Dual Core, etc. Make sure that the box you are about to Build is appropriate for its spec.<br />
* If everything looks good, Grab the system from the warehouse, take it back to your build station, and figure out how to pop it open. <br />
----<br />
'''Check capacitors'''<br />
* Visually inspect motherboard capacitors for bulges/leaks. If you find one, ask your instructor for a "Rejected" sticker. <br />
----<br />
'''Secure the case'''<br />
* Cover any open bays or slots. Replace any other missing case parts. (You can substitute a CD-ROM drive if no compatible bay cover is available.) Some cases require specific (proprietary) parts. If we don't have extras on hand, we unfortunately have to recycle them... <br />
* Ensure that all components are securely fastened.<br />
* Check for/remove any loose screws or unnecessary cables. If you're unsure of how to do this, ask an instructor.<br />
----<br />
'''Is there Microsoft Branding (Certificates of Authenticity)? Asset tags? (identifying the last owner)? Or branded hardware tags on the faceplate (identifying original components such as RAM, HDD, Optical Drive etc)?'''<br />
* If there are, remove them. '''DO NOT remove FG-PDX, "uncovered electronic device" Processor/graphics tags or Green Light stickers.'''<br />
----<br />
'''Clean and vacuum out box'''<br />
* There is a vacuum available on the Build supply shelf by the cleaning supplies. The most effective way to clean out a box is to use a paint brush to kick up the dust while vacuuming.<br />
----<br />
'''Test battery'''<br />
* Grab a voltmeter and set it to DCV=20. Place one wand on the battery itself and one wand on a metal part of the case. The battery passes if its voltage shows as 3.0 or greater. <br />
----<br />
'''Install RAM'''<br />
* For DDR2, try speed 533 (PC3200) first. If that doesn't work, try other numbers. Sometimes the BIOS will tell you the needed speed.<br />
* If your system's memory slots will not accept DDR2 memory, they will require another type. DDR3 is acceptable - ask your instructor for DDR3 RAM. DDR1 systems should be rejected and sent back to Prebuild as yellow-light systems.<br />
** NOTE: Usually RAM should be paired in dual channels for higher performance (i.e., 2 sticks of RAM used in specific slots, often color-coded). Make sure you try all combinations of slots if you are having trouble getting the system to recognize the RAM, and consult an Instructor if you're still having trouble.<br />
* Write down what type and speed of RAM you installed; this info will come in handy later.<br />
----<br />
'''Install video card if needed'''<br />
* You do not need to install a video card if there is functional onboard video. <br />
* Ask an instructor if you need a PCI-e card; AGP cards are available in the Build room.<br />
----<br />
'''Initial power on''' <br />
* See if expected memory value is displayed during POST or in BIOS. <br />
----<br />
'''Power down'''<br />
----<br />
'''Remove floppy drive if possible'''<br />
* Remove the floppy drive if you can find a matching face plate to cover it. If there are no covers available, you can leave the drive in, but make sure it is unplugged from the motherboard and power supply. Make sure the floppy drive (sometimes called Diskette) is disabled in BIOS and removed from the boot sequence if possible. <br />
----<br />
'''Check for onboard NIC ((Network Interface Card, or ethernet.)'''<br />
* If none can be found, install a network card.<br />
----<br />
'''Install hard drive'''<br />
* Get the appropriately sized (according to spec sheet) hard drive from the supply shelf, or from an instructor. Also check to see if you need an IDE or SATA hard drive and make sure you have the necessary cables and power connections.<br />
* Install the hard drive and attach it to the power supply and motherboard. (If the drive has IDE connections, make sure the jumper is set to the Master position. Ask an instructor for more info.)<br />
* You will need to ask an instructor for any hard drives higher than 120 GB.<br />
----<br />
'''Install sound card if needed'''<br />
* If there's onboard sound, there's no need to install a sound card.<br />
----<br />
'''Install CD/CDRW/DVD/DVD-RW Drive(s)'''<br />
* If there are already optical drives installed in your system, take a look at their face-plates to determine their capabilities. If the drives are within spec for the box you're building and have IDE connections, confirm they're properly jumpered as Master/Slave, or just Master if there's only one drive. <br />
* If the the drives are outside of spec, pull them out and sort them into the appropriate boxes on the Build shelves. Replace with appropriate drives as needed.<br />
---- <br />
'''Cover open slots and bays'''<br />
* Make sure you have coverings for all spaces that will not be filled with a card or drive. Look at similar cases for examples of what case pieces may look like. Be sure that these are screwed in tight and test them by pushing on each with your finger. If a slot cover falls out while a computer is on it can '''short out the motherboard.'''<br />
----<br />
<br />
== BOOT AND [[Entering BIOS|ENTER BIOS]] ==<br />
----<br />
'''Attach monitor, keyboard, mouse, network, sound and power cords'''<br />
----<br />
'''Enter BIOS setup'''<br />
* Turn on the computer. The keystroke to enter BIOS should be displayed on the flash screen, before bootup, as well as the Boot Menu key, if applicable. If no flash screen appears, you have to guess the BIOS keystroke. Delete, Escape, Enter, F1, F2, F9, F10, and F12 are typical. <br />
* Get into BIOS, and '''write down both the BIOS and Boot Menu keystrokes;''' this info will come in handy later.<br />
----<br />
'''Check date and time''' <br />
* Check date and time in BIOS and change to the correct time if needed.<br />
----<br />
'''Restore BIOS defaults'''<br />
* You might need to search around to find the BIOS values that need checking. While you search, enjoy the pleasure of learning about BIOS configuration! <br />
----<br />
'''Detect hard drive'''<br />
* Search BIOS to see if it is recognizing the hard drive. <br />
----<br />
'''Set boot order'''<br />
* It should be: '''1st-CD-ROM'''; '''2nd-Hard drive. If possible, disable all other boot devices such as floppy drive or network boot from the boot sequence.<br />
----<br />
'''Where possible, edit any/all of the following settings:'''<br />
* Enable USB ports<br />
* Enable Hyper-threading<br />
* Disable Quick Boot<br />
* Disable Logo Display (Sometimes called Silent or Quiet Boot)<br />
* Disable Plug & Play OS<br />
* SATA Operation: set to RAID Autodetect/AHCI<br />
----<br />
'''Save and exit BIOS'''<br />
* The system should reboot to the Ubuntu operating system. <br />
----<br />
<br />
== HARDWARE AND SOFTWARE TESTING ==<br />
----<br />
'''Login to the system'''<br />
* username will be '''Default User''' <br />
*password = '''freegeek''' <br />
----<br />
'''Run "basiccheck"''' <br />
* From a terminal, type "'''basiccheck'''" Read through each of the tests and verify that they pass. When the last test is finished, close the terminal.<br />
* Refer to the basiccheck checklists hanging on the supply shelves to help determine whether each test passes or not. <br />
----<br />
'''Learn to install a program through the Graphical User Interface (GUI - the mouse)'''<br />
* The first place to look for software to add is in the Ubuntu Software Center (Applications>Ubuntu Software Center). This gives you access to the Ubuntu supported applications plus many others. Search for "k3b" and install it. K3b is a CD/DVD authoring program.<br />
----<br />
'''Learn to install a program through command line'''<br />
* Open up a terminal and type "sudo apt-get install gimp" and press "Enter." This will install the photo editing program called Gimp. The system will ask for your password; type "freegeek" and press enter. Don't worry that the text doesn't show on the screen; it is hidden for security reasons.<br />
----<br />
'''Test USB ports'''<br />
* Plug in a USB mouse, see that the cursor moves and can interact with things. Repeat with all USB ports, including front ports, if any.<br />
----<br />
'''Play an audio CD'''<br />
* Do you hear what you expect? Is it loud enough to be heard easily? Repeat for each CD-ROM drive. Repeat for additional sound ports. <br />
* Note if any standard sound ports do not work. These will need to be covered with electrical tape. If all onboard sound does not work, install a sound card.<br />
----<br />
'''Read data CD'''<br />
* If your file browser sees files on the drive, the CD-ROM can read files. Repeat for each CD-ROM drive. <br />
----<br />
'''If you have a DVD Drive, Read DVD'''<br />
* If your file browser sees the file, the DVD-ROM can read files. If you are prompted to search for suitable plugins or codecs, '''please do not do this!''' The test still passes. Repeat for each DVD-ROM drive.<br />
----<br />
'''If you have an Optical Drive with CD-RW function, Test CD Writing'''<br />
* Insert a CD-RW disc into the drive and open Brasero Disc Burning (under '''Applications >> Sound & Video'''.) Select '''Data Project''', click on the green +, then select '''examples.desktop''' and click '''Add'''. Click '''Burn''' in the lower right-hand corner. A new window will pop-up with a few options. If available, select '''Use burnproof''' and '''Burn the image directly without saving it to disc''' and click '''Burn'''. When the disc is done, verify that it contains the examples file by re-inserting the disc and seeing what pops up on the desktop. <br />
* Blank the disc using Brasero by selecting '''Tools >> Blank'''. If available, '''uncheck the "Fast Blank" option.''' If blanking does not work, the drive may still be completely functional! Ask your instructor about software bug workarounds. <br />
----<br />
'''If you have an Optical Drive with DVD-RW function, Test DVD Writing'''<br />
* Insert a DVD-RW disc into the drive and in the Brasero file browser follow the same steps as above to burn a data project. When the disc is done, verify that it contains the examples file by re-inserting the disc and seeing what pops up on the desktop.<br />
*Blank the disc using Brasero by selecting '''Tools >> Blank'''. If available, '''uncheck "Fast Blank."''' Again, blanking errors may not indicate a bad drive. Ask your instructor for more information. <br />
----<br />
'''Test for booting from live CD'''<br />
* Place Live CD in drive and restart the computer. The system should boot from the live CD. <br />
* Select language: English. Scroll down on the following screen to '''Boot to first hard drive''' and press enter. This should take you to the normal Ubuntu log-in screen. <br />
----<br />
'''Remove all CDs and DVDs from the drive(s)''' <br />
----<br />
'''Reboot the system'''<br />
* Open a terminal and type '''sudo reboot.''' Wait while it reboots, and ensure that the system powers on and offers a login screen without user intervention (e.g. requiring you to "press F1 to boot.") <br />
* If it doesn't boot smoothly, double-check your boot priority options in BIOS and try again.<br />
----<br />
'''Run "printme" from terminal'''<br />
* From a terminal, type "'''printme,'''" this will generate a questionnaire in Command Line. <br />
* Refer to your written notes for the RAM type and speed, the BIOS key and Boot Menu key, if applicable. <br />
* '''When it asks what is notable about this system, refer to the white board for what should be included, and ask your instructor for any needed clarification.''' Press enter to create a web document.<br />
---- <br />
'''Check in with Build Instructor''' <br />
* The Build Instructor will check the printme and edit it to sign it off. <br />
* Your instructor may ask you to replace certain components, which will require re-running the "printme" form. Some changes may also need to be made in the web browser. If your instructor gives the "thumbs-up," proceed to the next step. <br />
----<br />
'''Save Printme to the desktop'''<br />
* After your Build Instructor has inspected the system, click "Print" from the printme on the web document. "Choose "Print to File" and select "Desktop" as the folder in which to save it. Name the file "Build Printme" and click print. <br />
----<br />
'''Shut down system and place on QC shelf'''<br />
* Open a terminal and type "sudo halt" then press enter. When the system has shut down, unplug all cables, double-check that the case is secured properly, and place it on the QC shelf in the Build room.<br />
----<br />
'''Clean up work area if it is your last Assembly of the day'''<br />
* Please put all tools away, throw out any garbage or sticker remains, put screws in the appropriate bins, wrap cords around your keyboard and mouse, turn off your speakers and monitor, and generally straighten up. <br />
<br />
<br />
<br />
== Thank You For Volunteering! ==<br />
* If you are interested in further learning opportunities after finishing the Build program, ask your instructor about '''Post-Build options!'''<br />
* We want to know what you think! Go to '''http://freegeek.limequery.com/48992/lang-en''' to fill out the '''Build Program Exit Survey.'''<br />
<br />
<br />
<noinclude>[[Category:Build]]</noinclude></div>Alambhttp://wiki.freegeek.org/index.php?title=2012_September_Newsletter&diff=641232012 September Newsletter2012-09-08T01:08:54Z<p>Alamb: /* Recycling at Free Geek: A Peek Downstream */</p>
<hr />
<div>==Empowerment Through Volunteering==<br />
Editor’s note: We are honored to present this testimonial from Greg Traylor, an active Free Geek volunteer. Thank you Greg for sharing your story with us!<br />
<br />
I’ve considered writing a self-help book for people who want to be miserable based on my own life experiences. Among chapters such as “Don’t Nurture Your Creativity,” “Stay In A Job You Loathe Because It Pays Well,” “Be Who You Think Other People Will Like,” and “Stay In Relationship Because It Is Comfortable” would be the chapter entitled “Don’t Volunteer.” Cells throughout the body are programmed to get sick and die when they are no longer relevant (among other reasons) and around 60% of your neurons in your language centers will commit ‘suicide’ when they are no longer needed. Nature tends to be recursive, mimicking itself on levels from small to large. We are all cells in the super-organism of society and are given the role of furthering that society and each other. We all must find our own ways of becoming relevant to life lest our happiness and health atrophy. I’ve found that volunteering does that for me and that Free Geek is the kind of place I want to volunteer.<br />
<br />
I learned about Free Geek a few years ago and made a mental note that I should volunteer there. It wasn’t until my life had imploded that I actually acted upon this idea. I was living on the streets of Old Town and trying to find my way out of the seemingly endless concrete maze that is homelessness. Help came but not how I would have expected. Technology and those connected to it became my saviors and that combination succeeded where organizations failed. I unexpectedly stumbled into friendships and support. The subject of Free Geek came up when talking with one of my new friends, Dan, and we soon attended the orientation together.<br />
<br />
Taking the orientation made me realize that I really wanted to be a part of this group. The combination of open source philosophy, geek culture, recycling, volunteerism and technology really appealed to me. Inspired by this visit, I applied for a Hardware Grant. This was so much simpler than I could have expected. I just filled out an online form with the appropriate information and was accepted. Free Geek has donated over 4,900 computers to schools, non-profits, religious organizations and more. Every computer comes as a complete unit with monitor, keyboard, mouse and power cables. All are thoroughly tested and loaded with Ubuntu.<br />
<br />
The idea that got me this grant (and one other) was relatively simple, provide computers, connections and training to those in transitional housing and shelters. This would be cost-free to the organizations but the ‘clients’ would pay by volunteering elsewhere, seeding other non-profits and community projects. I believe technology can help others as it helped me. I believe that in bridging the digital divide at the lowest levels we allow people to pull themselves up with information.<br />
<br />
Volunteering there has become one of the favorite parts of my week. You would pay for college classes to get the practical hands-on experience you get in your volunteering at Free Geek. The combination of volunteer and tech activities looks really good on a resume *cough* Hire me Free Geek! *cough*. There are classes you can take to further your computer-related knowledge. You are helping to remove toxic and non-biodegradable wastes from the landfill. Deserving entities will reap the benefits of your work which will allow them to help others. You receive a computer and tech support for volunteering. There is a library and public terminals. The staff and volunteers are wonderful people. They have free coffee and don’t mind if you drink enough to start shaking, in fact, it seems to amuse them.<br />
<br />
I plan on being a fixture at Free Geek for quite a while. I recently applied for a teaching internship so that I can further help where I can be of some use. I honestly believe it is a great organization. Remember that when you support Free Geek, you support the groups they support, groups that may be giving you support one day. Never underestimate the power that the marriage of good people and technology has. Give of yourself and get a better you back. Give of yourself and become relevant.<br />
<br />
==Recycling at Free Geek: A Peek Downstream==<br />
If you have ever volunteered in the Recycling department, you have probably seen our warehouse staff load pallets of materials (plastics, laptops, copper-bearing material, wires and cables, etc.) onto trucks, and watched them drive away into the distance. Have you ever found yourself wondering where those trucks were going?<br />
<br />
Free Geek works with a variety of vendors who transfer our recyclable materials to their facilities, where further processing is done to recycle or repurpose them. In the interest of sustaining the local economy, and reducing fossil fuel emissions and pollution, we strive to select vendors who do business in the Portland Metro area. We also require vendors to keep materials in the US or North America, and comply with all applicable laws, thereby ensuring the application of strict environmental standards.<br />
<br />
Additionally, in accordance with the standards of the Basel Action Network (http://www.ban.org/), our vendors avoid sending materials to solid waste landfills or incinerators, do not use prison labor in their recycling processes, do not export hazardous waste to non-EU or non-OECD (http://www.oecd.org/) countries, demonstrate an effective Environmental Health and Safety management system, and keep Free Geek informed of any changes in their processes or downstream disposal.<br />
<br />
Occasionally we are offered the opportunity to visit our vendors’ facilities and observe their operations. One such occasion occurred on a bright Thursday morning this summer. The lights did not get turned on in the Free Geek warehouse. While the recycling table and bench stood silent, our warehouse crew was off on a field trip, to Metro Metals in Vancouver, WA. This is what they had to say about their adventure:<br />
<br />
“Free Geek sends ferrous and non-ferrous material, wire, and other copper bearing material to Metro Metals. It was quite impressive to see shredders as big as a house, their incoming pile of everything from cars and refrigerators, to old strollers, and the final product of steel, copper wire, and aluminum. We also got to see their waste water management system, which filters rainwater and other water run-off before it discharges into the river. Metro Metals was one of the first companies in the Portland Metro (including Vancouver) area to include such a filtration system.<br />
<br />
Our Recycling Interns were particularly impressed to see the operations at Metro Metals. We are hoping to do more site visits like this in the future, to educate both ourselves and our volunteers about what happens to our recyclable materials once we have finished processing them.”<br />
<br />
==Hardware Grants Serve our Robot Overlords==<br />
In addition to keeping school computer labs and classrooms running with quality refurbished Ubuntu-based computers, the Free Geek Hardware Grants program provides systems to various after-school and school-related programs. Recently, we were happy to provide much-needed materials to FIRST Robotics Competition Team 1432, the original Portland-based FIRST Robotics Competition robotics team (http://team1432.org/). Team 1432, also known as Mahr's Metal Beavers, was founded by Franklin High School teacher Peter Mahr with five of his advanced metals students. While at Franklin High School for the subsequent seven years, they helped keep several at-risk students interested and involved in school, helping one student attain a full-ride scholarship for an engineering degree at Portland State University.<br />
<br />
As one might expect, running a successful robotics club can be an expensive proposition. Fortunately, Team 1432 has garnered much support from various businesses that have an invested interest in employing local highly skilled problem-solvers. Even with this support, the members of Team 1432 wisely look to the Free Geek Hardware Grants program to satisfy their needs for computer equipment to help them create, pilot, and share the successes of their competition-grade robots.<br />
<br />
According to their recently completed Hardware Grants request: "The computer parts on this list will help us finish a computer capable of running Autodesk software and we can have another one enabling three students at a time to learn Autodesk Inventor and PTC, a C.A.D. modeling program. This will aid us in building our robot and teaching students highly desirable job skills. The items on this list will also help us with our robot presentations during the year and for years to come. The projector will show a slide show about our program and what we have done at schools, and during community outreach activities. The laptop will allow us to control our robot during the events we go to throughout the year. (Events like the Marion County Fair, Multnomah County Fair, school visitations and other neighboring community events.)"<br />
<br />
Team 1432 patiently waited for two months as we worked to source and provide them with: four desktops with dual core processors, two laptops, a projector, two touchscreen monitors, two headsets and various other miscellaneous components. With our assistance, these youth are able to explore new possibilities in robotics and continue to participate in robotics competitions. Of course, it doesn't hurt when they give us wonderful feedback that reminds us why we keep on providing a valuable service to our community: "We appreciate all of the support that Free Geek has given us in the past and have always proudly displayed your logo on our robot and mentioned you on our website. Your support has made it possible for us to participate in the FIRST robotics program and that is changing our lives. We can't begin to tell you thanks enough. Many thanks for [all] that you have done, made possible and continue to do."<br />
<br />
==Volunteer Spotlight: Summer 2012 Volunteer BBQ==<br />
Free Geek shows the summer love to our awesome volunteers!<br />
<br />
If your primary contact with Free Geek has consisted of dropping off donations, or purchasing something from our Thrift Store, you may not realize that our operations are largely powered by volunteers who come here to learn workplace-readiness or computer-based skills, socialize with wonderful people and otherwise give back to their community. We could not continue to offer free computers, printers and other electronics to non-profits, schools and community change organizations without our amazing volunteers. In recognition of their tireless efforts, on Saturday, July 21st, we hosted our annual Volunteer Appreciation Barbeque, in the Free Geek parking lot.<br />
<br />
The party was a great success! Volunteers brought their friends, parents, kids, and siblings, bringing attendance to roughly 250. We played games of cornhole, chess and hackeysack, listened to hot summer jams on the stereo, and ate ourselves into a coma; hot dogs, vegetarian/beef burgers, cole slaw, potato salad, beer and lemonade were all enjoyed in abundance. One volunteer even brought home-baked brownies (although we were hoping for more participants in the brownie-baking contest, the single batch that came in was delicious enough to compensate)!<br />
<br />
As the food supply dwindled away, we raffled off some awesome prizes. Volunteers took home a snazzy desktop system with hi-def 22-inch monitor, keyboard, speakers and mouse, as well as a high end Toshiba laptop, three DVD players, and a reverb amplifier. Gift packages and certificates from a variety of local businesses were also distributed.<br />
<br />
Misty Fall, one of the organizers of the event, remarked that “usually volunteers and staff are in smaller quadrants within the building working on separate but connected tasks. The BBQ was a wonderful opportunity to see everyone outside on a sunny day eating, drinking, playing, and talking to each other. It was so satisfying to plan and experience this great opportunity to express our appreciation of all the hard work and awesome attitudes our volunteers bring to the multi-tasking, fast-paced world of Free Geek.”<br />
<br />
Big ups go to Misty and the rest of the BBQ planning team for putting on this great event without a hitch! We also could not have pulled off this wonderfully fun day without significant support from partner businesses in our community. Special thanks go to our sponsors: Cellar Door Coffee, New Seasons Market, City Bikes, Dave’s Killer Bread, Ninkasi Brewing, Pacific Pie Company, Hotlips Pizza, Widmer Brothers Brewing Company, and Jolly Roger Restaurant.<br />
<br />
==Staff Spotlight: Eli Wisnievitz==<br />
If you’ve visited the Front Desk recently, you’ve probably run into Eli, who recently joined our staff in the role of Front Desk and Receiving Support. We thought the Free Geek community might like to get to know Eli a bit, so we sat down to ask him a few questions.<br />
<br />
*How long have you been with Free Geek, and what were you doing before you joined the staff here?<br />
- I have been working at Free Geek for just over 2 months, and it has been fantastic. Before Free Geek, I worked at The Walking Company which is a comfort and arch support footwear store. Previous to that, I was an office assistant to the Food Service Director at Mount Hood Community College. I’ve also been known to teach Tennis during the summer, but it’s been a few years since I did that!<br />
<br />
*What do you enjoy most about working at the Front Desk?<br />
- The front desk is a great place to meet and interact with the volunteers and donors. These people are the most important individuals that contribute to Free Geek, either through their hard work in our volunteer areas or by donating their used technology to us. It also is a very positive place to work because many people are thrilled to be able to contribute to our mission. These donors in particular get peace of mind knowing that we ensure chain of custody over the items we recycle, and that once we receive their used technology we will do everything we can to reduce the waste it will create.<br />
<br />
*What was your first impression about Free Geek, and what has surprised you about working here?<br />
- I was awed by Free Geek when I started here. From the social perspective, it was clear that Free Geek volunteers truly loved spending their valuable time with us. From a sustainability standpoint, seeing how much effort is put into reuse was very encouraging and exciting. The warehouse is a fantastic place to be directly involved in ethically recycling electronics and keeping harmful chemicals out of the earth.<br />
<br />
- I’ve been surprised to discover how many educational opportunities we offer. In each volunteer area I have learned a great deal about various hardware and the relevant components that make them work. On the scholastic side, I am still blown away by quantity and range of classes that we offer to the public for no charge. To me life is a never ending journey of learning, and it is clear that Free Geek aims to be an educational facility for people of all ages and paths.<br />
<br />
*What do you wish the average visitor knew about what goes on in the warehouse and production areas behind the Front Desk at Free Geek?<br />
- I think that visitors would become even more amazed with Free Geek if they really understood how important and helpful the volunteer workforce is here. We are truly indebted to the volunteers who have been around for years, have spread the word and have tirelessly given back to the community at large and to Free Geek itself. The literal tons of material we are able to recycle ethically each month are broken down by volunteers. The systems we are able to donate out to individuals and nonprofits are all built by folks who have taken the time to learn from us and volunteer in our build program.<br />
<br />
*What is one thing that our readers might be surprised to learn about you?<br />
- I go by Eli (pronounced L-E), but my real name is Elishaya Wisnievitz (First day of class nightmare!) I was supposed to be named after my great grandfather, named Shaya. At the last second my 10-year-old sister insisted that they modify Shaya because it would be too strange. So it is Maya, my dear sister that I can thank for having a fairly simple nick name. I am also the first person in my direct family to be born in the United States and go to a university. While I wasn’t sure how I would fare with a degree in Philosophy and Religion, I knew that the ideas and discussions I had at Boston University would always impact how I viewed the world in a positive manner. My family is from Mexico and I enjoy practicing my Spanish with volunteers and some staff members here!<br />
<br />
[[Category:Newsletter]]</div>Alamb