For now, we're using working groups as a way of dividing up responsibilities. Look for a working group that excites you and suits your particular interests. Follow your "wow". Once there, each group page will tell you what you can do to help.

Development:

Like getting the word out? Meeting people? Spreading new ideas? Running great events or cooking cookies for participants? Join the development working group and help us grow. Some key projects:

Internet Week Event

Outreach

Press

Social Network Strategy

Governance:

How will we work together to manage this resource? Help us navigate the intersection of public policy, commerce, and community principles. Join the governance group and make policy that makes sense. Some important discussions:

Domain Name Regulations 

Consitution

Membership Conditions

Enterprise:

Interested in business? Help us sort basic operational issues, like making the organization economically sustainable and providing services to name-holders. Join the enterprise working group and make our engine hum. Some key tasks:

Fundraising

Business Plan and Model

Finance

Domain Name Allocation Plan

Alternative Operating Models

Technology:

An open enterprise like dotCity needs evolving web tools. Help us identify our most pressing needs, and then implement existing tech solutions or build new ones. Some of our current projects:

Connectingnyc.org Website

Open Plans Wiki

About the Working Groups

This working groups governance model, and all rules specified below, have so far been entirely constructed by Matt Cooperrider. Please feel free to make the case to change them. Presently, it is the responsibility of the Governance group to improve our present model of governance on this project.

Group Responsibilities

In order to sure that someone is accountable for all of the core needs of this project, each working group will be assigned a set of responsibilities. These responsibilities are listed on each working group page. Each group's members are expected to organize themselves in whatever way is necessary to meet those responsibilities.

The responsibilities assigned, however, must be determined by the group as a whole. A working group may not relieve itself of a responsibility until one of the following occurs:

1. They demonstrate that they have met that responsibility (for a completable task), and the whole group confirms this.

2. They successfully make the case that the responsibility is no longer germane to the project, and the whole group agrees.

3. They successfully make the case that another working group ought to take on this responsibility, and another group agrees to take it on.

The working groups should feel free to add new responsibilities. Once a new responsibility has been added to a particular group and confirmed by the whole group, the rules above apply.

The master list of assigned responsibilities will be maintained on the Working Group Responsibilities page. For now, this page should only be edited by Matt Cooperrider, until a new governance model is established. (There are no permission controls on this wiki, so we're on the honor system.)

Group Projects

Groups should adopt projects only if those projects help them meet their responsibilities. Working groups should feel free to create and edit projects at will. They should be aware, however, of cases in which projects are shared by multiple groups.