RT - Revision history

Bkoenig at 18:15, 29 May 2014

2014-05-29T18:15:48Z

Scrump at 20:49, 12 June 2012

2012-06-12T20:49:21Z

Sophia at 21:30, 15 September 2009

2009-09-15T21:30:37Z

Rfs: /* Administrator Notes */

2009-04-07T17:38:11Z

Administrator Notes

Rfs: /* Administrator Notes */

2009-03-21T21:12:10Z

Administrator Notes

MichaelWestwind: /* How does FREE GEEK use RT? */

2008-11-28T16:14:26Z

How does FREE GEEK use RT?

Rfs: /* How does FREE GEEK use RT? */

2008-06-17T19:30:18Z

How does FREE GEEK use RT?

Rfs: /* How does FREE GEEK use RT? */

2008-06-17T19:29:47Z

How does FREE GEEK use RT?

Rfs: /* How does FREE GEEK use RT? */

2008-06-17T19:29:13Z

How does FREE GEEK use RT?

Rfs: /* How does FREE GEEK use RT? */

2008-06-17T19:28:56Z

How does FREE GEEK use RT?

← Older revision		Revision as of 18:15, 29 May 2014
Line 1:		Line 1:
		+	{{Migrated}}
		+	[https://docs.google.com/document/d/1AdS3ERwY-VahtmTgMxtq5OAlMKH29KG-6jlNfdqEcKA/edit?usp=sharing Link]
		+
	This is a brief overview of what RT is and how it's used at Free Geek. To learn more of the details about navigating and using RT, see [[Learning RT]].		This is a brief overview of what RT is and how it's used at Free Geek. To learn more of the details about navigating and using RT, see [[Learning RT]].

← Older revision		Revision as of 20:49, 12 June 2012
Line 1:		Line 1:
		+	This is a brief overview of what RT is and how it's used at Free Geek. To learn more of the details about navigating and using RT, see [[Learning RT]].
		+
	==What is RT?==		==What is RT?==
	RT is short for ''Request Tracker'' - a system used for keeping track of tasks and who's doing them. Individual tasks (called ''tickets''), ranging from bugs to support calls to grants, are organized in ''queues'', depending on their category, and gain ''owners'' - that is, the person responsible for seeing them to completion. Each ticket gathers a history in the form of comments and replies. Users of RT see all the tickets that they own as a (somewhat collaborative) todo list - thus the URL we use, http://todo.freegeek.org/		RT is short for ''Request Tracker'' - a system used for keeping track of tasks and who's doing them. Individual tasks (called ''tickets''), ranging from bugs to support calls to grants, are organized in ''queues'', depending on their category, and gain ''owners'' - that is, the person responsible for seeing them to completion. Each ticket gathers a history in the form of comments and replies. Users of RT see all the tickets that they own as a (somewhat collaborative) todo list - thus the URL we use, http://todo.freegeek.org/

@@ Line 9: / Line 9: @@
 ; Software Developers : use RT as a bug- and feature request-tracker. Problems with the Free Geek database go into the fgdb queue and will be looked at by [[Coders]] when they get a chance.
-; Hardware Grants : grant requests from [http://freegeek.org/grants.php our website] create a ticket in the HardwareGrants queue. The [[Hardware Grants Group|grants group]] reviews these requests at their monthly meeting in accordance with our granting criteria, and a grant shepherd then owns the ticket and sees the grant through to delivery.
+; Hardware Grants : grant requests from [http://freegeek.org/grants.php our website] create a ticket in the HardwareGrants queue. The [[Hardware Grants Group|grants group]] reviews these requests in accordance with our granting criteria, and a grant shepherd then owns the ticket and sees the grant through to delivery.
 ; [[Tech Support]] : the TechSupport queue is used to keep track of support history and build a knowledgebase of common issues. Support requests that come in outside of support hours can be put into the TechSupport queue with an email sent to support@freegeek.org, and tech support volunteers can check that queue to find out what needs followup.
 ; [[Knowledge Bees|Documentation]] : is an example of a working group that does not meet, and whose work is somewhat sporadic and influenced by the work of other groups. When changes are made in the interface of a testing script or the procedures for a common task, a ticket in the Documentation queue alerts the group that the documentation need to be updated.
@@ Line 25: / Line 25: @@
 The following people are currently RT administrators:
 *Michael Westwind
 *Richard Seymour

@@ Line 22: / Line 22: @@
 * [[RT Permissions]]
-* [[Setting up an RT queue and an Mailman list to work together]]
+* [[Setting up an RT queue and a Mailman list to work together]]
 The following people are currently RT administrators:

@@ Line 28: / Line 28: @@
 *Michael Westwind
 *Richard Seymour
-*Shawn Furst
+*Vagrant Cascadian
 [[Category:Howto]]

@@ Line 11: / Line 11: @@
 ; Hardware Grants : grant requests from [http://freegeek.org/grants.php our website] create a ticket in the HardwareGrants queue. The [[Hardware Grants Group|grants group]] reviews these requests at their monthly meeting in accordance with our [[granting criteria]], and a grant shepherd then owns the ticket and sees the grant through to delivery.
 ; [[Tech Support]] : the TechSupport queue is used to keep track of support history and build a knowledgebase of common issues. Support requests that come in outside of support hours can be put into the TechSupport queue with an email sent to support@freegeek.org, and tech support volunteers can check that queue to find out what needs followup.
-; [[Documentation]] : is an example of a working group that does not meet, and whose work is somewhat sporadic and influenced by the work of other groups. When changes are made in the interface of a testing script or the procedures for a common task, a ticket in the Documentation queue alerts the group that the [http://web.freegeek.org/howto howtos] need to be updated. '''NOTE''': this example is out of date.
+; [[Knowledge Bees|Documentation]] : is an example of a working group that does not meet, and whose work is somewhat sporadic and influenced by the work of other groups. When changes are made in the interface of a testing script or the procedures for a common task, a ticket in the Documentation queue alerts the group that the [http://web.freegeek.org/howto howtos] need to be updated. '''NOTE''': this example is out of date.
 ; Working Groups and [[Free Geek Structure#Standing Staff Committees|Standing Staff Committees]] : are groups that meet regularly and deal with a large number of small and large ongoing tasks. Keeping these tasks in RT helps with figuring out what needs to be on a meeting agenda, what commitments are taken care of, and what need more work.

@@ Line 12: / Line 12: @@
 ; [[Tech Support]] : the TechSupport queue is used to keep track of support history and build a knowledgebase of common issues. Support requests that come in outside of support hours can be put into the TechSupport queue with an email sent to support@freegeek.org, and tech support volunteers can check that queue to find out what needs followup.
 ; [[Documentation]] : is an example of a working group that does not meet, and whose work is somewhat sporadic and influenced by the work of other groups. When changes are made in the interface of a testing script or the procedures for a common task, a ticket in the Documentation queue alerts the group that the [http://web.freegeek.org/howto howtos] need to be updated. '''NOTE''': this example is out of date.
-; Working Groups and [[Free Geek Structure#Standing Staff Committees|standing subcommittees]] : are groups that meet regularly and deal with a large number of small and large ongoing tasks. Keeping these tasks in RT helps with figuring out what needs to be on a meeting agenda, what commitments are taken care of, and what need more work.
+; Working Groups and [[Free Geek Structure#Standing Staff Committees|Staff Standing Committees]] : are groups that meet regularly and deal with a large number of small and large ongoing tasks. Keeping these tasks in RT helps with figuring out what needs to be on a meeting agenda, what commitments are taken care of, and what need more work.
 ==How can you get an RT account?==