Difference between revisions of "Define Community Member Sets"
FootskyJan07 (talk | contribs) (→'''Discussion''') |
(review and brainstorming result) |
||
| Line 17: | Line 17: | ||
=='''Discussion'''== | =='''Discussion'''== | ||
Community Staff put this task back to dev, as the algorithmic work doesn't seem to mesh with our [[CommunityDefinitions]] task, which is what we are working on to build community. It could be that our works helps inform this dev task. We'd be happy to talk it over. | Community Staff put this task back to dev, as the algorithmic work doesn't seem to mesh with our [[CommunityDefinitions]] task, which is what we are working on to build community. It could be that our works helps inform this dev task. We'd be happy to talk it over. | ||
| + | |||
| + | Later Mark, Ted and Ward met to review the [[CommunityDefinitions]] work and then brainstormed additional dimensions that might be useful. Ward then condensed and reorganized this as a series of scales upon which a future user could be measured. As such this work is speculative rather than need driven. However, it should inform design of advanced user objects. | ||
| + | |||
| + | Scales that depend on the client request | ||
| + | * referrer (unknown, self, site, search) | ||
| + | * host (open proxy, irreversible, shared ip, fixed ip) | ||
| + | * session (absent, unknown, current) | ||
| + | |||
| + | Scales that depend on the user's on site behavior | ||
| + | * reading behavior (number of pages read per visit) | ||
| + | * writing behavior (number, style, location of edits) | ||
| + | * collaborative behavior (participating, leading, founding communities) | ||
| + | * supporting behavior (welcoming, patrolling, sysop, bureaucrat) | ||
| + | * temporal (new, once, occasional, frequent, past) | ||
| + | |||
| + | Scales that depend on another site's info | ||
| + | * holder (unknown, expired, whois, confirmed) | ||
| + | * cites (none, links, badge, widget) | ||
| + | * about page (absent, quoted, cites us, delegates to us) | ||
| + | * alliance (external links, domain box) | ||
| + | |||
| + | Scales that depend on login info | ||
| + | * name (ip-address, open-id, password, real name) | ||
| + | * email (unknown, known, confirmed) | ||
| + | * photo (absent, present, human, confirmed) | ||
| + | * phone (absent, present, confirmed) | ||
| + | |||
| + | Scales that depend on AboutUs as a company | ||
| + | * employment (contractor, part-time, full-time) | ||
| + | * permission (developer, sysadmin) | ||
=='''Task Lead'''== | =='''Task Lead'''== | ||
Revision as of 04:14, 18 October 2007
Description
Needed for the development tasks Internal Advertising and AdSense Improvements.
Why?
Our core business is about providing people with the tools and community they need to accomplish their work in the world. One proxy measurement of how successful we are at helping people accomplish their aims is how they choose to more deeply engage with our site. We need to be able to tell how many of our members have taken the actions or been elected by themselves or others to be part of a particular category so that we can measure how successful we are at moving folks to deeper levels of engagement.
Done When
- At least 5 interesting sets of users have been identified and clearly defined (e.g., ActiveMember, VerifiedEmail, EditedPersonalPage, etc) in a way that can be algorithmically determined.
- At least two of the sets only partially overlap.
Useful Links
>
Discussion
Community Staff put this task back to dev, as the algorithmic work doesn't seem to mesh with our CommunityDefinitions task, which is what we are working on to build community. It could be that our works helps inform this dev task. We'd be happy to talk it over.
Later Mark, Ted and Ward met to review the CommunityDefinitions work and then brainstormed additional dimensions that might be useful. Ward then condensed and reorganized this as a series of scales upon which a future user could be measured. As such this work is speculative rather than need driven. However, it should inform design of advanced user objects.
Scales that depend on the client request
- referrer (unknown, self, site, search)
- host (open proxy, irreversible, shared ip, fixed ip)
- session (absent, unknown, current)
Scales that depend on the user's on site behavior
- reading behavior (number of pages read per visit)
- writing behavior (number, style, location of edits)
- collaborative behavior (participating, leading, founding communities)
- supporting behavior (welcoming, patrolling, sysop, bureaucrat)
- temporal (new, once, occasional, frequent, past)
Scales that depend on another site's info
- holder (unknown, expired, whois, confirmed)
- cites (none, links, badge, widget)
- about page (absent, quoted, cites us, delegates to us)
- alliance (external links, domain box)
Scales that depend on login info
- name (ip-address, open-id, password, real name)
- email (unknown, known, confirmed)
- photo (absent, present, human, confirmed)
- phone (absent, present, confirmed)
Scales that depend on AboutUs as a company
- employment (contractor, part-time, full-time)
- permission (developer, sysadmin)
Task Lead
- Task Lead:
Resource Estimate
- Pair Days:
Evaluator
- Evaluator:
Task Evaluation
- How the task went:
- Sign off Person:
- Sign off Date:
