Committees: Difference between revisions
(Created page with "==Current Committees== ===Committee to Rework Genre List=== '''Established:''' November 10, 2010 by [http://docs.comics.org/wiki/GCD_Board_Votes_-_2010#November_2010 Board Mot...") |
No edit summary |
||
Line 7: | Line 7: | ||
'''Objective:''' Update the GCD genre list. | '''Objective:''' Update the GCD genre list. | ||
''' | '''Mailing List:''' [http://groups.google.com/group/gcd-genre GCD Genre Committee] | ||
<br><br> | <br><br> | ||
Line 17: | Line 17: | ||
'''Objective:''' Produce a report on integrating the Bails' Who's Who into the structure of the GCD. | '''Objective:''' Produce a report on integrating the Bails' Who's Who into the structure of the GCD. | ||
''' | '''Mailing List:''' [http://groups.google.com/group/gcd-whos-who gcd-whos who] | ||
<br><br> | <br><br> | ||
Line 28: | Line 28: | ||
'''Objective:''' Explore the possibility of a comic-strip database. The Comic Strip Committee is only responsible for identifying a logical set of data points to be collected and implementation. The structural details such as data normalization and table structures will delegated to the tech team at a later date. | '''Objective:''' Explore the possibility of a comic-strip database. The Comic Strip Committee is only responsible for identifying a logical set of data points to be collected and implementation. The structural details such as data normalization and table structures will delegated to the tech team at a later date. | ||
''' | '''Mailing List:''' [http://groups.google.com/group/gcd-strips GCD Comic Strips] | ||
'''Report Delivered:''' December 12, 2010 | '''Report Delivered:''' December 12, 2010 | ||
Line 48: | Line 48: | ||
:* decide on a reserve fund | :* decide on a reserve fund | ||
''' | '''Mailing List:''' [http://groups.google.com/group/gcd-financial-goals GCD Financial Goals] | ||
'''Results:''' None | '''Results:''' None | ||
Line 58: | Line 58: | ||
'''Objective:''' The Hardware Committee focused on the following: | '''Objective:''' The Hardware Committee focused on the following: | ||
:* define growth plans, if any, do we have for support services, like the wiki, the bugzillas and review board. | :* define growth plans, if any, do we have for support services, like the wiki, the bugzillas and review board. | ||
:* | :* identify additional features, better integration, and new support applications. | ||
:* determine the need for any new hardware requirements for areas that might maintain or even | :* determine the need for any new hardware requirements for areas that might maintain or even improve stability and performance. | ||
''' | '''Mailing List:''' [http://groups.google.com/group/gcd-hardware-committee gcd-hardware-committee] | ||
'''Results:''' None | '''Results:''' None | ||
Line 77: | Line 77: | ||
:* recruit more developers | :* recruit more developers | ||
''' | '''Mailing List:''' [http://groups.google.com/group/gcd-software-committee gcd-software-committee] | ||
'''Results:''' [[Software Planning Committee 2010]] | '''Results:''' [[Software Planning Committee 2010]] |
Revision as of 18:29, 1 January 2012
Current Committees
Committee to Rework Genre List
Established: November 10, 2010 by Board Motion
Chair: Tony Rose, Jim Van Dore
Objective: Update the GCD genre list.
Mailing List: GCD Genre Committee
Committee to Study Who's Who Integration
Established: June 18, 2011 by Board Motion
Chair: Donald Dale Milne
Objective: Produce a report on integrating the Bails' Who's Who into the structure of the GCD.
Mailing List: gcd-whos who
Past Committees
Comic Strip Committee
Established: September 3, 2010 by Board Motion
Chair: Lionel English
Objective: Explore the possibility of a comic-strip database. The Comic Strip Committee is only responsible for identifying a logical set of data points to be collected and implementation. The structural details such as data normalization and table structures will delegated to the tech team at a later date.
Mailing List: GCD Comic Strips
Report Delivered: December 12, 2010
Strategic Committees
Established: March 4, 2010
Objective:Present proposals that outline where the GCD should be on April 1, 2014 (the project's 20th anniversary) in clear, measurable goals that will help the Board achieve, retain and support the objectives. Milestones should be developed in such a way that members can reach the goals in incremental steps (short term goals to achieve the long term goals). Periodic updates will be provided.
Goals will support the mission statement, but committees are asked to consider ways in which the focus area might contribute to the overall objective of the GCD Project within the given time frame. Brainstorming sessions can be used to identify realistical and achievable goals with some leeway for labor and finances since those areas might grow. Costs of each idea (financial and other resources) and prioritize the idea must be included in the final result.
Financial Goals
Chairman: Tony Rose
Objective: The Financial Goal Committee focused on the following:
- identify income and expense areas
- identify growth areas (such as increasing Google Ad revenues, paypal donations and other revenue streams?)
- decide on a reserve fund
Mailing List: GCD Financial Goals
Results: None
Hardware Committee
Chairman: Ralf Haring
Objective: The Hardware Committee focused on the following:
- define growth plans, if any, do we have for support services, like the wiki, the bugzillas and review board.
- identify additional features, better integration, and new support applications.
- determine the need for any new hardware requirements for areas that might maintain or even improve stability and performance.
Mailing List: gcd-hardware-committee
Results: None
Software Committee
Chairman: Henry Andrews
'Objective:' The Software Committee focused on the following:
- determine if project will be able to reach the New Fun schema within the allotted time frame
- determine if the New Fun schema needs revisions.
- determine if progress can be made to the More Fun schema
- examine the possibility of expanding into other projects (*not* strips or reference work)
- examine the possibility of web service support
- recruit more developers
Mailing List: gcd-software-committee
Results: Software Planning Committee 2010