Subject: CapAccess Committees (FYI)

From: Douglas Schuler <[email-masked]>
Date: Wed, 5 Aug 1992 08:44:52 -0700

In case any of you are interested, here is a list of committees that
the CapAccess group in Washington DC have put together.  CapAccess is
an amibitious effort similar to ours that is being developed slightly
differently.  

Richard Civille, CPSR staff, and Paul Hyland of the CPSR board are
both working on this project.  CapAccess is currently becoming a
501.c.3 (non-profit) entity.

-- Doug

>From [email-masked] Mon Aug  3 15:31:19 1992
From: Richard Civille <[email-masked]>
To: Doug Schuler <[email-masked]>
Date: Mon, 3 Aug 1992 17:28:14 EDT
Subject: CapAccess Committees 

  CapAccess Committees

Doug:

CapAccess committees are:

Information services:  Develop the menu structure for the system, provide a
forum for potential information service providers to come into the project. 
Get to figure out the the freenet/feenet balance and how to cross-subsidize
fee-based services to support free public access.

User services:  Develop the "help-desk", both online and voice mail. 
Develop base of volunteer "mentors" to help others use the system.  Develop
two test user groups, one to hack the system and the other group to bring in
representative "constituencies" such as homeless shelters, K-12, reference
librarians, etc.  Serve as a "advocate" for users and  promote ease and
convenience of use.

Ways and Means:  Coordinates fund-raising.  Collects budgets and task
timelines from each of the committees to develop a master budget and project
timeline for the whole effort.  Works with committees in helping to seek
particular funding for committee assignments.

Policies and Procedures:  Evaluates administrative policy and develops
procedures.  Reviews sysop and online system administrative policy from
other systems, identifies issues, organizes meetings to review policy issues
and formulate recommendations.

Governance:  Composes and recommends articles of incorporation, bylaws,
responsible for creating governance structure and proposing membership
"lines of interest" which will be used to determine categories of
representation on the Membership Council, the primary governing body below
the Board of Directors, half of whom are drawn from the Council.

Public Relations:  logo, letterhead, puts out a little newsletter 10 days
after each membership meeting, plans system "innauguration" when it goes
public, coordinates closely with Ways and Means.

Technical Advisory Committee:  Oversees system operation, acts as liason
between George Wash. Univ. computer center and CapAccess.  Develops
functional requirements specifications.  Evaluates the software, looks at
development needs and options.

Steering Committee:  The provisional board of directors.  Comprised of two
representatives from each standing committee.  Oversees general direction of
the CapAccess project.

Richard Civille