Talk:FGdb Coder and System Administrator - Revision history

Rfs at 16:42, 28 June 2012

2012-06-28T16:42:49Z

Ryan52 at 21:02, 6 May 2012

2012-05-06T21:02:36Z

Ryan52 at 19:09, 6 May 2012

2012-05-06T19:09:11Z

Ryan52: /* Detailed Responsibilities */ add more comments

2012-05-06T18:58:55Z

Detailed Responsibilities: add more comments

Mkille at 23:40, 5 May 2012

2012-05-05T23:40:15Z

Ryan52: /* Responsibilities */

2012-05-05T19:09:33Z

Responsibilities

Rfs: Created page with "'''Proposed new job title:''' The '''Applications Developer/System Administrator''' is responsible for developing Free Geek's software applications and assisting in the support …"

2012-05-05T18:57:44Z

Created page with "'''Proposed new job title:''' The '''Applications Developer/System Administrator''' is responsible for developing Free Geek's software applications and assisting in the support …"

New page

'''Proposed new job title:'''

The '''Applications Developer/System Administrator''' is responsible for developing Free Geek's software applications and assisting in the support of Free Geek technical infrastructure.

==Responsibilities==

* Go through the tickets already present in our system, helping to fix bugs and implement features where possible, given the amount of time.
** (too detailed and specific. generalize a bit.)
* Work with the Technocrats Standing Committee to prioritize FGdb tasks related to FGdb.
** (out of date. FGdb is not managed by the technocrats, who focus more on the system administration part of the job.)
* Work with the Technocrats Standing Committee to prioritize other system administration tasks.
** (this is accurate, though we may want to generalize "technocrats standing committee")
* Regular onsite work is required, though some work can be done remotely.
** (this is to encourage working here, and staying in communication with other staff, while allowing the flexibility of getting small, timely tasks completed from a distance)
* Work must be done in a way that allows other skilled volunteers to contribute to the project, though management of other coding and system administration volunteers is not required since other staff will take responsibility for volunteer coordination.
** (this is a general approach to making the position more inheritable. so far, this hasn't worked, so we should figure out how we want to approach this and consider re-wording this section)
* Learn the general overview of the code base and system infrastructure already in use.
** (this is a one-time thing for a new person on the job)

==Required Skills==
* General understanding of computer programming, Ruby on Rails, and standard programming practices.
* General understanding of Free Geek, its mission, and community.

==Desired Skills==

== See Also ==

@@ Line 4: / Line 4: @@
 '''Other information to include:''' (Mark)
-**FTE (absolute or range)
+*FTE (absolute or range)
-*** was originally 10 to 18 hours per week (Ryan)
+** was originally 10 to 18 hours per week (Ryan)
-**reports to (if applicable)
+*reports to (if applicable)
-**bargaining unit or not (job category)
+*bargaining unit or not (job category)
-**eligible for benefits?
+*eligible for benefits?
 '''should lock this page when finished with edits''' (Mark)
@@ Line 58: / Line 58: @@
 ==Desired Skills, Knowledge and Abilities==
-** (Mark: any particular credentials or certifications?)
+* (Mark: any particular credentials or certifications?)
-** (Mark: previous work or volunteer experience at Free Geek desirable?)
+* (Mark: previous work or volunteer experience at Free Geek desirable?)
 == See Also ==

@@ Line 5: / Line 5: @@
 '''Other information to include:''' (Mark)
 **FTE (absolute or range)
 **reports to (if applicable)
 **bargaining unit or not (job category)

@@ Line 25: / Line 25: @@
 ** (this is to encourage working here, and staying in communication with other staff, while allowing the flexibility of getting small, timely tasks completed from a distance)
 ** (Mark: we should specific either min on-site hours or max off-site hours under ordinary circumstances)
 * Work must be done in a way that allows other skilled volunteers to contribute to the project, though management of other coding and system administration volunteers is not required since other staff will take responsibility for volunteer coordination.
 ** (this is a general approach to making the position more inheritable. so far, this hasn't worked, so we should figure out how we want to approach this and consider re-wording this section)
 ** (Mark: is this more than a documentation question?)
 * Learn the general overview of the code base and system infrastructure already in use.
 ** (this is a one-time thing for a new person on the job)
@@ Line 34: / Line 36: @@
 ** Recommend changes to policies and procedures to improve the effectiveness and efficiency of FGdb and system administration. (Mark)
 ** Prepare monthly reports on number of bugs fixed and outstanding, and number of requested features implemented and outstanding. (Mark)
+*** (Ryan: Is this something Free Geek is now asking me to start doing? I will need to make RT tickets for many more things than I currently do to track every tiny change, which may seem excessive or at least annoy people a bit, but I don't have a problem doing it.)
 (Mark: these are some relevant boilerplate things)
 ** Communicate with other Free Geek staff and volunteers about the needs of all areas.
 ** Other duties as assigned.
 ==Required Skills, Knowledge and Abilities==

@@ Line 44: / Line 44: @@
 ==Required Skills, Knowledge and Abilities==
 * General understanding of computer programming, Ruby on Rails, and standard programming practices.
 * General understanding of Free Geek, its mission, and community.

@@ Line 3: / Line 3: @@
 The '''Applications Developer/System Administrator''' is responsible for developing Free Geek's software applications and assisting in the support of Free Geek technical infrastructure.
-==Responsibilities==
+'''Other information to include:''' (Mark)
 * Go through the tickets already present in our system, helping to fix bugs and implement features where possible, given the amount of time.
 ** (too detailed and specific. generalize a bit.)
 * Work with the Technocrats Standing Committee to prioritize FGdb tasks related to FGdb.
 ** (out of date. FGdb is not managed by the technocrats, who focus more on the system administration part of the job.)
@@ Line 12: / Line 21: @@
 * Work with the Technocrats Standing Committee to prioritize other system administration tasks.
 ** (this is accurate, though we may want to generalize "technocrats standing committee")
-* Regular onsite work is required, though some work can be done remotely.
+** (Mark: it is unclear to me whether prioritizing tasks in this duties automatically includes completing them)
 ** (this is to encourage working here, and staying in communication with other staff, while allowing the flexibility of getting small, timely tasks completed from a distance)
 * Work must be done in a way that allows other skilled volunteers to contribute to the project, though management of other coding and system administration volunteers is not required since other staff will take responsibility for volunteer coordination.
 ** (this is a general approach to making the position more inheritable. so far, this hasn't worked, so we should figure out how we want to approach this and consider re-wording this section)
 * Learn the general overview of the code base and system infrastructure already in use.
 ** (this is a one-time thing for a new person on the job)
 * Handle maintenance and upgrades for the deployed software (Ryan)
-==Required Skills==
+==Required Skills, Knowledge and Abilities==
 * General understanding of computer programming, Ruby on Rails, and standard programming practices.
 * General understanding of Free Geek, its mission, and community.
-==Desired Skills==
+(Mark: these are some relevant boilerplate things)
 == See Also ==