Sharing Productive Capital Group: Meeting 2, January 12th, 2009
Questions to ask about software (Scenerio Based Web Design):
- Who is going to be using it? Who are the stakeholders?
- People who want capital to volunteer itself
- Building user profiles that include reputation points in order to use certain high-risk equipment
- i.e. qualifications might be required to operate certain machinery; if a person has a history of abusing capital, they might need to have their rights to it suspended
- Need to have built-in capacities for people who are not computer literate to still use the capital (i.e. elderly who want their snow removed).
- How are we going to promote the capital?
- Need to constantly be generating new kinds of tags that reflect the usefulness of the capital
- We need a way to judge between uses (community evaluates and ranks the capital and its potential uses perhaps)
- User generated lists: capital is able to promote itself and advertise its ability to be used through these lists
- Can capital be substituted . . .
- When demands gets high for a particular itself (i.e. shovel for a snowblower).
- We need a system that notifies us when we need to purchase or build new capital (due to shortages, breakdown, etc.
What are the roles required to maintain and promote the system?
- Maintenance (to promote the on-site well-being of the citizens)
- Maintenance individuals are responsible for checking working order of capital before and after it gets signed out: it is also up to the person signing it out
- Repository must volunteer for itself and self-regulate its maitenance
- System must find substitute ways of doing things (i.e. either use snowshoes or build/buy a snowblower)
- Policy/justice system to regulate the system (i.e. dealing with abuse charges against a snowblower)
- Human citizens might use a token system whereby he/she has so many token and decides how urgently a particular task needs to be done.
- May be equalized for less well-off individuals
- Administrators
- Maintain technology, hardware and network
- Promoting system in non-technical ways and also making sure system promotes itself (i.e. we might hold birthday parties for the citizens in the repository)
- Volunteerism
- People need to be counted as volunteers in the system as well
- i.e. I am available for snow-removal on the following days.
- Seasonal volunteers and repeat volunteers: certain things need to be done at the same time every year (i.e. park cleanup on May 5th)
- Proxy systems for older individuals who cannot use computers
- External groups (i.e. city council)
- How might they affect and determine specific projects?
- Risk-minimizers
- Must have a body overseeing tasks (preferably, the repository itself) to determine risks to citizens during tasks in order to maximize benifit, utility and well-being