Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
policies:technology_officer [2016/01/12 13:28]
John Benedetto 		policies:technology_officer [2019/06/08 16:39] (current)
John Benedetto ↷ Links adapted because of a move operation
Line 1: Line 1:
 ====== Technology Manager ====== ====== Technology Manager ======
 +
 +<WRAP third right box>**Responsible for:**\\
 +Quelab's technology infrastructure
 +
 +**Contact Info:**\\
 +//Chris Hughes//\\
 +tech@quelab.net
 +</WRAP>
  
 FIXME FIXME
 +
 +Quelab's Technology Infrastructure is maintained by the Tech Officer and their deputies.  This position is a combination of sysadmin and moderator for the blog, wiki, and email lists.  The tech team also coordinates with the [[communications_steward]] on the moderation of the social media sites.
 +
 +Currently, the Tech office is staffed by the following volunteers, but more volunteers are always welcome!
 +
 +Chris Hughes - Email, Blog, Sysadmin\\
 +Adric Menning - Flickr, Facebook, Email\\
 +JT Benedetto - Wiki, Moodle\\
 +Geoff Nicholson - Blog, Email, Seltzer, Twitter\\
 +
 +----
  
 The term of office for the Tech Manager is one year, and is appointed by the board with the advice of the President. The term of office for the Tech Manager is one year, and is appointed by the board with the advice of the President.
  
-The responsibilities of the Tech Manager are as follows: +The responsibilities of the Tech Manager are as follows: 
 + 
 +    * Be a point of contact for website or in-house internet outages 
 +    * Maintaining communication infrastructure 
 +      * Servers 
 +      * Mailing Lists 
 +      * External facing software 
 +    * Coordinate repairs/installation of new computer/tech hardware 
 +    * Coordinate with other officers/board members to ensure tech needs are met 
 +    * Create a Disaster Recovery Plan 
 +      * To include documentation for passwords, restart procedures, backup recovery, and other points of contact in case of unavailability
  
-  * Be a point of contact for website or in-house internet outages 
-  * Maintaining communication infrastructure 
-    * Servers 
-    * Mailing Lists 
-    * External facing software 
-  * Coordinate repairs/installation of new computer/tech hardware 
-  * Coordinate with other officers/board members to ensure tech needs are met 
-  * Create a Disaster Recovery Plan 
-    * To include documentation for passwords, restart procedures, backup recovery, and other points of contact in case of unavailability