Updated: March 27, 2000

Syllabus

(http://www.scn.org/edu/tesc-ds/1999-2000/topics/syllabus.html)

Civic and Community Networking

The Evergreen State College, Lib 1612

Spring Quarter, 2000

Nine Wednesdays, 6-10 pm (March 1 through May 31, except April 26)
Saturday April 1 and Saturday June 3, 9:00 AM - 4:30 PM
Saturday and Sunday May 20 and May 21 at the University of Washington
Shaping the Network Society, ( http://www.scn.org/cpsr/diac-00/) Symposium

Program E-Mail distribution address: topics@scn.org

Schedule: http://www.scn.org/edu/tesc-ds/1999-2000/topics/schedule.html

Randy Groves
randy@scn.org
425.865.3424

Doug Schuler
dschuler@evergreen.edu
Lib 1608A
360.866.6000 ext. 6704

A community is a group of people united by the common objects of their love that incorporates three elements: shared values, unity, and intimacy.
   -- Ed Schwartz
Networks of civic engagement embody past success at collaboration which can serve as a cultural template for future collaboration.
   -- Robert Putnam
Masses make noise, citizens deliberate; masses behave, citizens act; masses collide and intersect, citizens engage, share, and contribute.
   -- Benjamin Barber

Program Themes

The development of civic society and civic problem solving capabilities are of critical concern all over the world. At the same time new communication capabilities are raising the possibilities of new collaborations, sometimes at a distance. This program will explore -- through theoretical and practical work -- how electronic communications can be used advantageously in various community settings / project areas worldwide. In the course of the program students working in "partnership project" teams will actively communicate with people at other sites throughout the world to define (and possibly develop) software and other services that assist their mission. It is expected that this program will help lay the groundwork for a number of longer-term programs / practicums within the part-time studies area that use electronic communication as a central tool. We also expect for this work to dovetail with Evergreen's planned Center for Community Partnerships.

This is a high-level intensive and innovative program for the motivated and energetic student. By combining social sciences, participatory action research, and computer systems development it is unlikely that this program exists anywhere in the world at the undergraduate level. The specifics of the program will depend to some degree on the interest levels and needs of the students and the degree of success will depend on the dedication of all participants.

Some program activities include

Suggested (upper division) equivalencies:

Program Components

Seminars

There will be several in-person seminars this quarter. Promoting a "learning community" is key at Evergreen, and seminars are essential to that goal. Everybody is expected to participate. This means that everybody needs to be prepared for each seminar: the material must be read and reflected upon. The goal of the seminar is for everybody to gain a better understanding of the ideas and the implications of the material that we read. People must be aware and supportive of each other for the seminar to work. Sometimes it is appropriate to ask a question, other times it's appropriate to connect two seemingly disparate ideas or point out a contradiction that exists in the writings. The most important thing to remember is that the seminar is a collective experience in which everybody plays a role in developing a successful session.

On-line Seminars

We will use the on-line seminars to complement (and help us prepare for) the in-person seminars. Everybody in the program will participate by contributing a question (by Monday at noon) and a one paragraph response to somebody's question (by Tuesday at noon) every week using Web Crossing. There will be one forum for Randy's seminar and one for Doug's. We will get a Web Crossing training session early in the quarter.

Readings

There will be weekly reading assignments. The readings will be found in one of three places:

The reading assignments for the individual weeks are listed in the schedule below.

Journal Entries

There will be seven one-page "journal entries" which are due every Wednesday except the first and last Wednesday. These will be in response to a simple question or statement which will be found in the schedule. These are not formal essays -- they're intended to help develop your thoughts -- but they shouldn't be "throw-away" either. They should be legible and thoughtful.

Pattern Paper

Architect Christopher Alexander and his colleagues have developed an intriguing "pattern language" for designing rooms, buildings, and towns. This "language" embodies a powerful vocabulary of over 250 architectural patterns that are life-affirming and convivial. Although we are just beginning a similar discussion, it is not too early to begin thinking about an analogous "pattern language" that knits together civic, social, political, economic, and communication patterns into a coherent and compelling vocabulary or language through which people can conceive, discuss, and build new communities.

Each student is expected to complete a pattern paper, due on May 31. The pattern you're thinking about and initial thoughts (such as how you think you'll be supporting it and what the consequences of the pattern might be) are due on May 3. This paper should be a printout of a web site and should be a minimum of five pages, including, hopefully, an appropriate graphic image. We plan to put all of these web pages on a program "pattern language" web site. We will provide an HTML template to make this easy even for those with little or no exposure to HTML.

This paper should advance one or more "patterns" that deal with some aspect of civic and community networking. Remember: It is recommended that you use quotations and ideas from books, articles, the web, etc.; this is how we participate in the ongoing human dialogues on issues that matter. On the other hand, it is not acceptable to use material without indicating and crediting the source. Some ideas for patterns include: collaborative techniques, models, community characteristics, new network tools, cross-border projects, what information do we make available and why, new social roles.

Computer Fluency

Each student will participate in one of the seven computer fluency components which are similar to group contracts. There will be time in class to work on these in class but students will be doing the bulk of the work outside of class. Each student will select an area of study, identify objectives, and develop a plan for meeting those objectives. The seven computer fluency modules are
  1. Basics (e.g. e-mail and/or browser use)
  2. JavaScript
  3. CGI / Perl scripting for the web
  4. Graphics (e.g. Photoshop)
  5. Presentation software (e.g. Microsoft Powerpoint)
  6. Building Web Pages (e.g. HTML, FrontPage, Pagemill, Flash, etc. )
  7. Networking (e.g. protocols or RFCs)

Statement from group due: April 12
The statement from the group should contain broad aims, strategy, division of labor, group evaluation technique.

Individual plan due: April 12
The individual plan should contain project component type (Basics, JavaScript, etc.), task descriptions, dates of relevant events, and how computer fluency plan will be evaluated.

Mid-term status report: May 3
The mid-term status report should contain description of your progress in meeting goals. Also discuss any problems and how you expect to overcome them.

Final product due: May 31
The final product should contain evidence that shows how well you met your goals. For web based projects, please turn in at least a hardcopy of the main page with the url of the page printed on the top.

Partnership Project

Each student will participate in a group "Partnership Project" (3 - 6 students per group) in which the Evergreen team will work -- generally electronically -- with one or more people in a possibly remote location. The idea is to begin to make recommendations as to what type or types of digital support the partnership community could use. This project will be covered more thorougly in the Partnership Project handout. These projects may be picked up again in the fall in the year-long Community Information Systems program.

The initial group project page consisting of a title, questions and concerns, first note (draft) to partnership, and list of members of the project is due by the end of the day on April 1. Each student will turn in a description of their role in the project on May 31.

Portfolios

Each student must keep a portfolio of everything that they have done (including notes) throughout the quarter. This should be tidy and well-organized using dividers. Your name should appear on the first page. The portfolio will be turned in on the last meeting day of the program and will be returned at the student evaluation conference. Please note that the portfolio consists of hard-copy -- it is not "virtual." If part of your work is on the Internet please turn in one or more printouts based on the work with the url plainly marked on each page. The portfolio should also contain a description of your role in the group project. Be sure to consult your portfolio or make photocopies of any material that you'll need for writing your self-evaluation!

Evaluations

Evaluation conferences will take place the week after the last Wednesday of class. Each student should bring in a self-evaluation and a faculty evalution on the proper forms.