Difference between revisions of "User:Matteo/scratch.03"

From FreekiWiki
Jump to navigation Jump to search
(more play)
(+ section)
 
(22 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
__NOTOC__ __NOEDITSECTION__
+
==Documentor Sources==
−
Building computers for people is a fun way to learn stuff. The build program is a structured way for volunteers to contribute to the cause and learn about hardware and basic troubleshooting and Linux skills. Builders can also earn a computer, but the time commitment is significant and the computer is the same as that earned in the [[Adoption Program]].
+
''Free Geek looks good on a resume and even better if its a special project''
−
{|cellspacing="1px" style="background-color:#f8fcff"
+
* School types to find interns
 +
** Tech. Wrighters
 +
** Mathamatitions
 +
** law
 +
** P.S. (Political Science)
 +
** Social Worker/Comunety orginizer
  
−
| width="70%" style="border: 1px solid #6688AA; background-color:#FFFFFF; padding:1em;" valign="top"|
+
==Documenting Policy Project==
 +
''these thoughts will be blended with the process found in the [[Policy Development]] page''
 +
* Is this a policy or a guideline (if no change the current policy and document the change)
 +
* Is this a new or a change to a current policy or guideline
 +
* Who created the Policy and how does it relate to others / what is the scope of the policy
  
−
==[[Prebuild]] steps==
+
==Creating New Policies==
−
We don't require any prior knowledge for people to join the build program. The steps that precede the build workshops are called, collectively, the "prebuild steps," and teach very basic material that will be needed for people to make their way in the build workshops. Several of these steps can be bypassed by people who know the material already; see [[Testing Out]].
 
  
−
==Build workshops==
+
* Research current Apliciable policies
−
The build workshops are the heart of the build program. They run almost every day we're open, and though there are teachers (and often assistants) for each one, are largely peer-taught. There will be a range of extreme beginners to experienced builders in each workshop.
+
* Find a couple of people to bounce your idea off of
 +
* Email your Perposal to the correct list
 +
* Please clearley seperate your email into sections:
 +
** the Policy you propose
 +
** Reason this policy is needed (would this be a change to a current Policy)
 +
** Any thing you came up with during your research (like Policies)
  
−
;QC
+
==Policy Page Ideas==
−
The first thing builders do in a build workshop is to quality contol computers built by other builders. They use several free geek specific scripts and follow a checklist.
+
Three sections in the page perhaps
−
* ''Educational goals:'' Learning to use scripts and other utilities, basic troubleshooting, seeing the pitfalls others fall into.
+
<pre>
−
* ''Material goals:'' Make sure the [[FreekBox]]en, [[Grantbox]]en, and [[Storebox]]en are ready to go out the door!
+
{{Policy Header}}
−
 
+
* Policy name
−
;Assembly and software
+
* Note on what the policy is about/Scope of policy
−
More troubleshooting! This is where participants are actually building (putting together) computers and installing the software.
+
==Policy==
−
* ''Educational goals:'' More in-depth hardware knowledge, use of configuration tools.
+
* Body that set the policy(s) / Date Adopted / with Link to lists.freegeek meeting Minuits.
−
* ''Material goals:'' Um, we need computers! Reuse is our mission.
+
* Wording of the most recent agreed apon policy - as agreed upon
−
 
+
==Notes==
−
=="Graduating" from build==
+
* Interpretation/Implementation
−
A builder who has completed six computers may bring one home (one per person per year, kids). There's also a certificate we want to give out to these 'graduates' but we aren't super-good at tracking it!
+
* Examples/Background/History
−
 
+
* Exceptions/Ramifications
−
==Build assistants and instructors==
+
* Related policies
−
Builders who seem to really 'get it,' enjoy participating, and answer more questions than they ask may be invited by the build instructor to become a build assistant. Build assistants are expected to try extra hard to help their neighbors and pick up abandoned machines. They can also sign up for build workshops in assistant slots when the workshop is otherwise fully booked.
+
* Etc...
−
 
+
</pre>
−
Those who really enjoy teaching and want to help out a lot may go on to be build instructors, at which point they have earned the undying love of their peers and may start to develop a halolike glow and a fan club.
 
−
 
 
−
|width="30%"|
 
−
{|
 
−
| align="left" style="border: 1px solid #6688AA; background-color:#efefef;padding:1em;" valign="top" |
 
−
== Links ==
 
−
*[[Aaron's PCI Modem comments]]
 
−
*[http://freegeek.org/staffsched Staff schedule]: who's teaching pre-build? who's the build instructor?
 
−
*[[Build tips]] - lessons learned the hard way
 
−
*[[Build sheet]] - step by step building a FreekBox
 
−
|-
 
−
| align="left" style="border: 1px solid #6688AA; background-color:#efefef; padding:1em;" valign="top" |
 
−
==Server Build==
 
−
The [[Server Build]] program Workes on server class systems.                                                                                                                                                                                                                                                                                                                                                                                                  
 
−
==Laptop program==
 
−
Because of the limited nature of the [[laptop]] program, the laptop repair classes are open only to build instructors.
 
−
=="Advanced Linux" classes==
 
−
One of the benefits of being a builder is eligability to attend the (sporadically-held) "[[From User to Root|advanced linux]]" classes that go into some of the more technical aspects of using the operating system.
 
−
==Advanced testing==
 
−
Builders who want to play with hardware more than they want to work with people may elect to do advanced testing in place of some of their six builds. This would involve motherboard testing, modem testing, and other similar testing, which is often not all that well documented.
 
−
|}
 
−
|-
 
−
|}
 

Latest revision as of 02:21, 3 October 2006

Documentor Sources

Free Geek looks good on a resume and even better if its a special project

  • School types to find interns
    • Tech. Wrighters
    • Mathamatitions
    • law
    • P.S. (Political Science)
    • Social Worker/Comunety orginizer

Documenting Policy Project

these thoughts will be blended with the process found in the Policy Development page

  • Is this a policy or a guideline (if no change the current policy and document the change)
  • Is this a new or a change to a current policy or guideline
  • Who created the Policy and how does it relate to others / what is the scope of the policy

Creating New Policies

  • Research current Apliciable policies
  • Find a couple of people to bounce your idea off of
  • Email your Perposal to the correct list
  • Please clearley seperate your email into sections:
    • the Policy you propose
    • Reason this policy is needed (would this be a change to a current Policy)
    • Any thing you came up with during your research (like Policies)

Policy Page Ideas

Three sections in the page perhaps 

{{Policy Header}}
* Policy name
* Note on what the policy is about/Scope of policy
==Policy==
* Body that set the policy(s) / Date Adopted / with Link to lists.freegeek meeting Minuits.
* Wording of the most recent agreed apon policy - as agreed upon
==Notes==
* Interpretation/Implementation
* Examples/Background/History
* Exceptions/Ramifications
* Related policies
* Etc...
Retrieved from "http://wiki.freegeek.org/index.php?title=User:Matteo/scratch.03&oldid=20567"