Committees

From GCD
Jump to: navigation, search

Current Committees

Convention Circuit Committee

Established: 2013-11-21 by Board Motion

Chair: Daniel Nauschuetz

Objective: Handle all convention related activities for the GCD, including identifying conventions to participate in, recruiting volunteers, creating programs for our convention activities, developing budgets, defining success metrics, managing and advertising convention appearances.

Mailing List: gcd-conventions

Report Delivered: December 27, 2014 Conventions Committee Report

Past Chairs: Mike Nielsen - 2015-2016, Daniel Nauschuetz - 2014

Comics Bibliography Committee

Established: 2015-10-29 by the Chair, in response to Board discussions on implementing the comics bibliography module as approved by Motion of 2015-06-25, "That the GCD create a comics bibliography module within the database to fulfill one of its stated goals: "The ability to record references to all books and articles about comics stories, strips, and panels, their creators, their publishers, or profiles or histories of comics features, characters, or publications.""

Chair: not yet chosen

Members: Lionel English, Todd Enoch, Will Allred, Mike Rhode, Gene Kannenberg, Jochen Garcke

Objective: This is essentially a whole new database, though it may be related to our comics database and may even use some features and/or fields. Some of the issues to be determined include what data fields to record, how closely should it mimic a traditional book or academic paper bibliography, what types of books and papers, articles, blogs, etc. should we include, whether it should be be a database of citations or a database of publications, and anything else needing consideration. The committee will deliberate and then send a recommendation to the Board, similar to what we have done with newspaper strips, characters, creator data, features, etc.

Mailing List: GCD Bibliography Module Committee

Report Delivered: discussions in progress

Past Committees

Creator Table Specifications Committee

Established: 2014-03-22 by the Chair, in response to Board discussions on outsourcing this project.

Chair: Donald Dale Milne

Objective: Create the specifications and associated bid documents needed to put the creation of creator tables and online editing of those tables out for bids by outside contractors.

Mailing List: gcd-specifications

Report Delivered: January 19, 2015: specifications and bid documents approved by the Board February 2, 2015 - Creator Table Specifications 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

Report Delivered: April 12, 2012 - Who's Who Committee Report

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

Report Delivered: April 12, 2012 Genre Committee Report

my.comics.org

Established: May 27, 2011 by Board Motion

Chair: Jochen Garcke

Objective: Exploratory committee to outline a proposal for the proposed my.comics.org project. Said committee to consist of three to six people, and to be charged with writing a requirements doc for presentation to the board outlining a suggested features for the project.

Report Delivered: September 6, 2011 my.comics.org

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 . The report [1] lists the data points we want to capture and the functionality we desire.

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