Difference between revisions of "History of Free Geek"

From FreekiWiki
Jump to navigation Jump to search
m (→‎Further Reading: deleted section: information available via "category History")
 
(16 intermediate revisions by 6 users not shown)
Line 1: Line 1:
 +
{{migrated}}
 +
[https://docs.google.com/document/d/1sjEXoZw_ktMas8pxv4oRBjVJeQHiFLt_ME4E1XUGZtk/edit?usp=sharing Link]
 +
 
{{draft}}
 
{{draft}}
This is the history of Free Geek.
+
{{RightTOC}}
 
 
Free Geek started on the 13th on some month in 2000....
 
.... and now it's 2007 and we rock the (opensource-community-building-digital-divide-elimination) party that rocks the (recycling-for-the-environment-free-computers-for-volunteers) party.
 
 
 
==Programs: Past and Future==
 
 
 
Central to the changes of Free Geek since its formal inception has legendarily been democratic self-governance by consensus, as well as (since the first [[Big Meeting]]) its General or Community [[Founding Document of the Council|Council]]. 
 
 
 
===Open Source Software===
 
===Community Building===
 
===Bridging the Digital Divide===
 
===Recycling for Environmental Responsibility===
 
===Democratizing Technology through Reuse===
 
 
 
===Functional Self-Organization===
 
 
 
From its beginnings, a singular multiplicity of self-organization on the parts of many individuals and groups seemed to lead Free Geek to always self-identify its present collective motion as a natural means of continuing it.  And its history continues to seem embodied by its present experience, including what people remember. 
 
 
 
Its history is also implied (or imagined) in relationship with its organizational behavior, and more subtly as relationship with durable changes or transitions of behavior.  These, like its milestones (passage toward and past goals), mission emphases (decisions to articulate hence adjust goals), changes of era marking response to changes of circumstances etc., may be represented in various ways as motion within various metaphorical fields, as if "motion" and "milestone" were both presently experienced.
 
 
 
Continuing its movement today seems to depend in part upon both:
 
*remembering its past experience more or less precisely...
 
as well as 
 
*imagining forward motion precisely enough to maintain its durability.   
 
 
 
And reading here, new staff members and others may:
 
*imaginarily experience achievements and challenges of past years (possibly marveling and/or gasping),
 
*"see" presently useful similarities and differences between scenarios and situations which Free Geek has previously invoked, experienced, responded to, etc.
 
*mutually and durably reembody its formal construction of self-identity as a traditional historical entity and, yes,
 
 
* learn (and share) circumstances and events of losses and setbacks attending our owners' bosiness that may otherwise seem too sad or scary or something to even remember. 
 
 
 
And, of course:
 
 
 
* rocking.  (And knitting.)
 
 
 
====By Eras====
 
e.g., Before the Beginning, the Beginning, the Collaborative Technology thread, Board Activation, etc.
 
 
 
====By Milestones====
 
e.g., firsts: for instance, load to recyclers, adopted boxen, Council meeting, incorporation, hardware grant, paychecks for employees, Geek Prom, Geek Fair, etc.
 
  
==== By Functional Self-Organization ====
+
This is the history of [[Free Geek]].
e.g., history of committees, working groups, executive entities, etc., as well as their Council interactions, their interactions with previous and subsequent developments and circumstances, etc.
 
  
* the first working group was the [[Ass]] group. In the beginning they built the computers for the adoptersInteresting insights into this foundational process have been synthesized [[Meta_Question#So_what_are_those_stages_we.27ve_evolved_through.3F|here]] .
+
== The early days ==
 +
* Free Geek's first public event was an appearance at Earth Day 2000 at Pioneer Square in downtown Portland.
 +
* We opened our doors on September 1 later that year.
 +
* The first working group was the [[ASS]] group. Their first project was to set up the networking infrastructure for the building. They also determined that Linux would be the operating system to go out on the computers we would be giving away.
 +
* In the earliest days random technically savvy volunteers built the computers we gave away, which were first disbursed in exchange for 12 hours of volunteer work. There was no standard specification for the computers, nor any systematic quality control.
 +
* The "community service" in the mission statement was originally conceived to mean volunteer work at Free Geek and/or out in the community at large (i.e. other non-profits)While we soon discovered that we needed all the help we could get at the Free Geek facility, sometimes special arrangements are still made.  For example, if a school group has a really hard time getting to Free Geek to do their volunteer hours, we'll occasionally let them do their community service volunteer hours at their school, helping to clean up, tutor other students, etc.
 +
* The education group was formed to design a class for people who were receiving computers.
 +
* A very early issue was a larger number of volunteers than computers we were able to process and give away.
 +
* Volunteers could earn just about any type of gizmo by working hours for it, but this led to no end of bargaining. (How many hours for this hard drive?)
 +
* We planned an open house for late summer 2000 and kept putting it off, trying to figure out the best way to get local politicians to attend. In the end we settled on a day in November since it was after election day (only that year election day ended up lasting several weeks).
 +
* In January 2001 the Oregonian ran an article on its Metro section front page that advertised "Free Computers" at Free Geek. The next business day our lobby was filled with people wanting a free computer. We signed up so many volunteers (after explaining they had to volunteer for the free computer) that we needed to start a waiting list to get into the program.
  
====By Mission Emphasis====
+
=== Inception of the Build Program ===
e.g, its continuing focus, dynamic alignment with ever-changing circumstances, synchronization with past practice, etc.
+
* The ASSes took over the building of computers so there would be a standard type of computer we gave away. By that time the official number of hours needed to be volunteered had risen to 18 and then 24.
 +
* It became clear that a few system administrators couldn't build all the computers needed, so we tried to increase the size of the build volunteer pool by offering a weekend long build class. Richard and Mark concocted this idea over breakfast at the Paradox and recruited Kenny and Smyrf to help teach. George was given the title "Hardware Nazi" at this point, because he was the one whose job it was to dole out the hardware needed for building the systems.
 +
* The build class was repeated twice before it became apparent that we would need to offer it more often. Richard began offering regular build workshops on Thursday mornings before opening. There was no limit to the number of students who could attend and no prerequisites for starting the program.
  
====By Person====
+
=== Council Begins ===
e.g., personal experience and observations of major changes to organizations and operations, first-hand experience of decisional paths through and past crises and opportunities, remembrance and testimonials, etc.      
+
* There were a few working groups that existed before the council.  
 +
* Before the council we had periodic "Big Meetings" where we could talk about the big picture stuff. At one we proposed something called "The Group" (always in quotes), but that never took. Most people wanted to keep working mainly in their work groups, even if they attended more than one.
 +
* the council really got going after people had differing opinions on weather to start up a store.
  
====By External Relationships====
+
=== Struggling for Survival ===
e.g., speakers, hosted events, grants, media notice, durable relationships with other peeps and orgs, the passage of time itself (simple chronology), etc.
+
* Never knew when rent would get paid
 +
* Staff members didn't know if they could cash checks on payday
 +
* Warehouse acquisition
  
===Chronologies and Timelines===
+
== Expansion ==
 +
* Recycling Coordinator
 +
* Volunteer Coordinator
 +
* Collaborative Technologies Coordinator
 +
* added in shelving for system storage in the warehouse
 +
* Now we have the whole block (and tenants)
  
====When Lists Began====
+
== Collab Era ==
The following doesn't include lists 
+
=== Potatoes and Fromage ===
*which are defunct (e.g. those used during the Collab era)
 
*which restrict archive access (e.g., ASS, roomuse, grants, homestreet-resolution, providence, support, webadmin, volunteer)
 
*are not listed <span class="plainlinks">[http://lists.freegeek.org/listinfo/ here]</span> (e.g. staff, info)
 
*are presently empty.
 
 
 
=====2000-2003=====
 
<pre>
 
2000    2001        2002        2003                                                               
 
MJJASONDJFMAMJJASONDJFMAMJJASONDJFMAMJJASOND
 
--:--.--|--.--:--.--|--.--:--.--|--.--:--.--
 
freegeek-events; first e-mail to list:  . 
 
  : freegeek-funding; first e-mail to list 
 
  :  .  freegeek-directors; first e-mail to list
 
  :  .  freegeek-coders; first e-mail to list
 
  :  .  |  .  :  .  |  . freegeek-council; first email to list
 
  :  .  |  .  :  .  |  .  :  freegeek-social; first e-mail to list
 
  :  .  |  .  :  .  |  .  :  .  |core; first e-mail to list
 
  :  .  |  .  :  .  |  .  :  .  | core becomes freegeek-core
 
  :  .  |  .  :  .  |  .  :  .  | freegeek-gapsters; first e-mail to list
 
  :  .  |  .  :  .  |  .  :  .  |  freegeek-laptop; first e-mail to list
 
  :  .  |  .  :  .  |  .  :  .  |  .  freegeek-freekbox; first e-mail to list
 
  :  .  |  .  :  .  |  .  :  .  |  .  :freegeek-lessdisks; first e-mail to list
 
  :  .  |  .  :  .  |  .  :  .  |  .  :  . cfork; first e-mail to list
 
  :  .  |  .  :  .  |  .  :  .  |  .  :  . freegeek-startup; first e-mail to list
 
</pre>
 
  
=====2004, January/June=====
+
http://lists.freegeek.org/pipermail/collab/2003-December/000812.html
<pre>
 
2004                                                                                               
 
Jan  Feb Mar  Apr May Jun                                                                         
 
|----.---.----:---.---.----
 
freegeek-startup; first e-mail to list
 
|  fgdb-commits; first e-mail to list
 
|  lessdisks-commits; first e-mail to list
 
|    .   freegeek-inservice; first e-mail to list
 
|    .   .freegeek-pythonclass; first e-mail to list
 
|    .  .freegeek-system-eval; first e-mail to list
 
|    .  . freegeek-netaccess; first e-mail to list
 
|    .  .  freegeek-build; first e-mail to list
 
|    .  .    :fgdiag-commits; first e-mail to list
 
|    .  .    :  fg-nternships; first e-mail to list
 
|    .  .    :  fg-nternships becomes fg-internships
 
|    .  .    :  .  fg-classes; first e-mail to list
 
|    .  .    :  .  .fg-adoptionteachers; first e-mail to list
 
|    .  .    :  .  .  freegeek-fairuse; first e-mail to list
 
|    .  .    :  .  .  fg-penguinday; first e-mail to list
 
|    .  .    :  .  .  freegeek-documentors; first e-mail to list
 
</pre>
 
  
=====2004, July/Dec=====
+
=== A Real Job ===
<pre>
+
=== Overrun ===
2004                                                                                               
+
=== The Aftermath ===
Jul  Aug Sep  Oct Nov Dec                                                                         
 
+----.---.----.---.---.----
 
fg-penguinday; first e-mail to list
 
freegeek-documentors; first e-mail to list
 
+    .Kam-test; first e-mail to list
 
+    . freegeek-c7; first e-mail to list
 
+    .  freegeek-propagation; first e-mail to list
 
+    .  freegeek-technocrats; first e-mail to list
 
+    .  freegeek-modsquad; first e-mail to list
 
+    .  freegeek-reuse; first e-mail to list
 
+    .  .E-newsletter; first e-mail to list
 
+    .  .  freegeek-action; first e-mail to list
 
+    .  .  freegeek-grok; first e-mail to list
 
+    .  .    .E-newsletter becomes freegeek-e-newsletter
 
+    .  .    .  freegeek-legos; first e-mail to list
 
+    .  .    .  .  . freegeek-vroom; first e-mail to list
 
+    .  .    .  .  . lpi-study; first e-mail to list
 
+    .  .    .  .  .  freegeek-treehouse; first e-mail to list
 
</pre>
 
  
=====2005=====
+
== Reduction ==
<pre>
 
2005                                                                                               
 
Jan  Feb Mar  Apr May Jun  Jul Aug  Sep Oct Nov  Dec                                               
 
|----.---.----:---.---.----+---.----.---.---.----.---
 
freegeek-ups; first e-mail to list  .  .  .    . 
 
|    .  . freegeek-commandlineteachers; first e-mail to list
 
|    .  .  freegeek-printers; first e-mail to list
 
|    .  .    : fg-nap; first e-mail to list.    . 
 
|    .  .    :  .freegeek-distro-commits; first e-mail to list
 
|    .  .    :  .freegeek-fgdiag-bugs; first e-mail to list
 
|    .  .    :  .freegeek-website-commits; first e-mail to list
 
|    .  .    :  .  freegeek-sungeek; first e-mail to list
 
|    .  .    :  .  . freegeek-bylaws; first e-mail to list
 
|    .  .    :  .  .    +  .    freegeek-geekaid; first e-mail to list
 
|    .  .    :  .  .    +  .    .freegeek-bookworms; first e-mail to list
 
|    .  .    :  .  .    +  .    .  . freegeek-hacienda; first e-mail to list
 
|    .  .    :  .  .    +  .    .  . freegeek-ambassadors; first e-mail to list
 
|    .  .    :  .  .    +  .    .  . freegeek-crafty; first e-mail to list
 
</pre>
 
  
=====2006=====
+
== Self Sufficiency ==
<pre>
 
2006                                                                                               
 
Jan Feb Mar  Apr May  Jun Jul Aug  Sep Oct Nov  Dec                                               
 
|---.---.----:---.----.---+---.----.---.---.----.---
 
|freegeek-recycling; first e-mail to list  .    . 
 
|freegeek-geeklets; first e-mail to list  .    . 
 
|  .  .freegeek-linuxclinic; first e-mail to list
 
|  .  .freegeek-receiving; first e-mail to list 
 
|  .  .    :  .    gresham-council; first e-mail to list
 
|  .  .    :  .    .freegeek-minutes; first e-mail to list
 
|  .  .    :  .    .  +  .    .  . freegeek-priorities; first e-mail to list
 
</pre>
 
  
=====2007=====
+
== Future ==
<pre>
+
=== Post eWaste Regulation? ===
2007                                                                                               
 
Jan  Feb Mar Apr May  Jun Jul Aug  Sep Oct  Nov Dec                                               
 
|----.---.---:---.----.---+---.----.---.----.---.---
 
|  MAME; first e-mail to list.    .  .    .  . 
 
|    .  freegeek-tours; first e-mail to list  . 
 
</pre>
 
  
  
 
[[Category: History]]
 
[[Category: History]]

Latest revision as of 11:24, 8 August 2014

deletion

This page has been migrated to a document on Free Geek's Google Drive.

Information remaining behind may no longer be relevant.

MIGRATOR:

When you have tagged this page as migrated,
please add a link to the new document on Google Drive.

(Link to new page immediately below.)


Link

This is a draft of a new or in-progress document, and is likely to have a few people specifically working on it. You may wish to check in on the discussion page to see what the purpose of the document is and who's working on it; then feel free to give this article love and attention if have extra of those things.


This is the history of Free Geek.

The early days

  • Free Geek's first public event was an appearance at Earth Day 2000 at Pioneer Square in downtown Portland.
  • We opened our doors on September 1 later that year.
  • The first working group was the ASS group. Their first project was to set up the networking infrastructure for the building. They also determined that Linux would be the operating system to go out on the computers we would be giving away.
  • In the earliest days random technically savvy volunteers built the computers we gave away, which were first disbursed in exchange for 12 hours of volunteer work. There was no standard specification for the computers, nor any systematic quality control.
  • The "community service" in the mission statement was originally conceived to mean volunteer work at Free Geek and/or out in the community at large (i.e. other non-profits). While we soon discovered that we needed all the help we could get at the Free Geek facility, sometimes special arrangements are still made. For example, if a school group has a really hard time getting to Free Geek to do their volunteer hours, we'll occasionally let them do their community service volunteer hours at their school, helping to clean up, tutor other students, etc.
  • The education group was formed to design a class for people who were receiving computers.
  • A very early issue was a larger number of volunteers than computers we were able to process and give away.
  • Volunteers could earn just about any type of gizmo by working hours for it, but this led to no end of bargaining. (How many hours for this hard drive?)
  • We planned an open house for late summer 2000 and kept putting it off, trying to figure out the best way to get local politicians to attend. In the end we settled on a day in November since it was after election day (only that year election day ended up lasting several weeks).
  • In January 2001 the Oregonian ran an article on its Metro section front page that advertised "Free Computers" at Free Geek. The next business day our lobby was filled with people wanting a free computer. We signed up so many volunteers (after explaining they had to volunteer for the free computer) that we needed to start a waiting list to get into the program.

Inception of the Build Program

  • The ASSes took over the building of computers so there would be a standard type of computer we gave away. By that time the official number of hours needed to be volunteered had risen to 18 and then 24.
  • It became clear that a few system administrators couldn't build all the computers needed, so we tried to increase the size of the build volunteer pool by offering a weekend long build class. Richard and Mark concocted this idea over breakfast at the Paradox and recruited Kenny and Smyrf to help teach. George was given the title "Hardware Nazi" at this point, because he was the one whose job it was to dole out the hardware needed for building the systems.
  • The build class was repeated twice before it became apparent that we would need to offer it more often. Richard began offering regular build workshops on Thursday mornings before opening. There was no limit to the number of students who could attend and no prerequisites for starting the program.

Council Begins

  • There were a few working groups that existed before the council.
  • Before the council we had periodic "Big Meetings" where we could talk about the big picture stuff. At one we proposed something called "The Group" (always in quotes), but that never took. Most people wanted to keep working mainly in their work groups, even if they attended more than one.
  • the council really got going after people had differing opinions on weather to start up a store.

Struggling for Survival

  • Never knew when rent would get paid
  • Staff members didn't know if they could cash checks on payday
  • Warehouse acquisition

Expansion

  • Recycling Coordinator
  • Volunteer Coordinator
  • Collaborative Technologies Coordinator
  • added in shelving for system storage in the warehouse
  • Now we have the whole block (and tenants)

Collab Era

Potatoes and Fromage

http://lists.freegeek.org/pipermail/collab/2003-December/000812.html

A Real Job

Overrun

The Aftermath

Reduction

Self Sufficiency

Future

Post eWaste Regulation?