Old Hardware Grants Howto - Revision history

Sophia at 23:38, 5 November 2009

2009-11-05T23:38:57Z

Serge at 01:06, 31 July 2008

2008-07-31T01:06:43Z

Shawn: /* Shepherd Duties */ outreach materials

2007-10-27T01:15:52Z

Shepherd Duties: outreach materials

Rfs at 20:48, 25 August 2007

2007-08-25T20:48:53Z

Rfs: /* Grant arrives: RT hygiene, application checking */

2005-12-27T20:57:15Z

Grant arrives: RT hygiene, application checking

Halfasspete: /* Quick Guide: */

2005-12-27T06:12:35Z

Quick Guide:

Halfasspete: /* Detailed Instructions */

2005-12-27T05:28:20Z

Detailed Instructions

Halfasspete at 04:46, 27 December 2005

2005-12-27T04:46:55Z

Rfs: /* Grant Statuses defined */

2005-12-08T18:05:08Z

Grant Statuses defined

Rfs at 18:03, 8 December 2005

2005-12-08T18:03:50Z

← Older revision		Revision as of 23:38, 5 November 2009
Line 1:		Line 1:
		+	{{delete}}
		+
	'''NOTE: This is deprecated. For the most recent information regarding Hardware Grants, go to [[Hardware Grants]].'''		'''NOTE: This is deprecated. For the most recent information regarding Hardware Grants, go to [[Hardware Grants]].'''

← Older revision		Revision as of 01:06, 31 July 2008
Line 1:		Line 1:
		+	'''NOTE: This is deprecated. For the most recent information regarding Hardware Grants, go to [[Hardware Grants]].'''
		+
	== Quick Guide: ==		== Quick Guide: ==

@@ Line 51: / Line 51: @@
 === Shepherd Duties ===
 * When a grantee comes and gets an approved grant, the shepherd needs to:
 ** change the GrantStatus in the ticket tracker to "Finished"
 ** change the basic ticket status to "Resolved" the ticket (this way, we can say that all requests with a GrantStatus of "Approved" are still in limbo and need to be picked up)
 ** complete the associated Quality Control (QC) Sheet (for systems), or note gizmo numbers for data entry (for other hardware)
 ** if necessary, assign a "Recipient ID" to the Grantee in the FGDB
 === InstaGrants ===

@@ Line 97: / Line 97: @@
 : The shepherd for this grant has abandoned it.
-[[Category: HardwareGrants]]
+[[Category: Hardware Grants]]
 [[Category:Howto]]

@@ Line 17: / Line 17: @@
 An organization (the "Requestor") can only request a grant via the [http://freegeek.org/grants.php web form]. This both creates a ticket in the [http://todo.freegeek.org/ Request Tracker] (RT) and sends an email to the [http://lists.freegeek.org/listinfo/grants grants list]. Requestors get no confirmation of receipt.
-=== Grant arrives: RT hygiene, application checking ===
+=== When the grant arrives ===
 Everyone working on the grant committee should be on the list and have a HardwareGrants RT account as well. Anyone on the grants group may perform the following grant-application processing.
-When a grant arrives, it needs some massaging.
+==== RT hygiene ====
-* The Subject should be changed to the organization name.
+When a grant arrives, it needs some massaging. Someone needs to go to the ticket tracker, and:
-* The Requestor should be changed to the requestor's email address (and the existing one removed).
+# The Subject should be changed to the organization name.
-* The application should be checked to see if all important questions are answered and if it's a valid
+#* Add a suffix to the name "-- local" for local grants or "--" plus the name of the location for non-local grants.
 * If it's not a valid request (It's for an individual, a for-profit business, it's a request for money or a copy of Win2k):
 *# Take the ticket
 *# Change ticket GrantStatus to Denied
-*# Email the requestor with the reason
+*# Post a reply stating the reason for denial to the ticket in RT. (This will email the requestor and the list).
 *# Change ticket Status to Resolved.
 === Grants and their Shepherds ===

← Older revision		Revision as of 06:12, 27 December 2005
Line 1:		Line 1:
	== Quick Guide: ==		== Quick Guide: ==
		+
		+	:'' I would think this Quick Guide could be removed, since the Wiki's auto-generated Table of Contents does the same thing, only better. But, the original document's "Quick Guide" did not quite match the structure of the "Detailed Instructions." So I'm leaving this task to someone more knowledgeable. --[[User:Halfasspete\|Pete]] 22:12, 26 Dec 2005 (PST)''

	Most grants are for computers. This is a rough overview of the process. The process is still in development and we will try to streamline it, but as people learn it, we will be able to get a current status of all our outstanding requests easily.		Most grants are for computers. This is a rough overview of the process. The process is still in development and we will try to streamline it, but as people learn it, we will be able to get a current status of all our outstanding requests easily.

@@ Line 12: / Line 12: @@
 ==Detailed Instructions==
-* The application process: An organization (the "Requestor") can only request a grant via the form on the grants web page http://freegeek.org/grants.php. This both creates a ticket in the Request Tracker (RT) and sends an email to the grants list. Requestors get no confirmation of receipt. (The grants list is found at http://lists.freegeek.org/listinfo/grants, and the ticket tracker is at http://todo.freegeek.org/.
+=== Application Process ===
-* Everyone working on the grant committee should be on the list and have a HardwareGrants RT account as well. Anyone on the grants group may perform the following grant-application processing.
+An organization (the "Requestor") can only request a grant via the [http://freegeek.org/grants.php web form]. This both creates a ticket in the [http://todo.freegeek.org/ Request Tracker] (RT) and sends an email to the [http://lists.freegeek.org/listinfo/grants grants list]. Requestors get no confirmation of receipt.
-** When a grant comes in, someone needs to go to the ticket tracker, and:
+=== Grant arrives: RT hygiene, application checking ===
-**# change its initial GrantStatus to "Requested"
+Everyone working on the grant committee should be on the list and have a HardwareGrants RT account as well. Anyone on the grants group may perform the following grant-application processing.
-**# Edit the subject (title of the request) and make it distinguishable from all the other requests, probably by including the organizational name
 When this is done, reply to the grant on the list, make the title of your post match the new title of the request, and include a link to the ticket in the post.
 * A request needs a "shepherd" to go anywhere. If you want to shepherd a grant thorugh the process, you should go to the ticket tracker and "Take" the ticket. This makes you the shepherd. Once you are a shepherd, you are committing to getting the grant through to approval and disbursion (or denial).
 * The shepherd (or someone else if there is no shepherd yet) needs to read the grant and determine if we have all the information we need to proceed.
@@ Line 36: / Line 43: @@
 ** Set its GrantStatus to "Approved", if the request has been "Approved." (Do not "Resolve" the ticket at this point.)
 ** Contact the requestor and inform them of the decision.
 * When a grantee comes and gets an approved grant, the shepherd needs to:
 ** change the GrantStatus in the ticket tracker to "Finished"
@@ Line 41: / Line 50: @@
 ** complete the associated Quality Control (QC) Sheet (for systems), or note gizmo numbers for data entry (for other hardware)
 ** if necessary, assign a "Recipient ID" to the Grantee in the FGDB
-* InstaGrants happen between meetings. If an instagrant happens, it should be entered into the ticket tracker with a GrantStatus of "InstaGranted". When the equipment is disbursed change the GrantStatus to "Finished," "Resolve" the ticket, assign a "Recipient ID" if necessary, and provide for updating the status of the granted equipment in the FGDB, as above.
-** If a shepherd moves on to other pastures and leaves his requests behind, someone needs to go through his tickets and change all their GrantStatuses to "Orphaned".
 Non-computer grants can be treated just like computer grants. If, for some reason, the web form doesn't serve the purpose, a new ticket can be made in one of two other ways:
 * Send an email to hardware-grants@freegeek.org . The subject of your email will become the title of the request.
-** Go to the ticket tracker and enter it using the web interface.
+* Go to the ticket tracker and enter it using the web interface.
-During the course of a requests lifespan, it is often good to comment on the request, adding a note that contains information about how the request needs to be implemented for instance. This can be done in one of two ways:
+During the course of a request's lifespan, it is often good to comment on the request, adding a note that contains information about how the request needs to be implemented for instance. This can be done in one of two ways:
 * Through the web interface
 * By sending an email to hardware-grants@freegeek.org with a subject that contains a string like "[freegeek.org #123]" (where 123 is the ticket number).

← Older revision		Revision as of 04:46, 27 December 2005
Line 74:		Line 74:

	[[Category: HardwareGrants]]		[[Category: HardwareGrants]]
		+	[[Category:Howto]]

@@ Line 67: / Line 67: @@
 : We have approved the grant request, but there is no shepherd yet.
 ; InstaGranted
-: We have decided to give the hardware out before the next meeting.
+: We have given the hardware out before the next meeting (after consulting another member of the Hardware Grants group).
 ; Finished
 : The equipment has been disbursed.