John's Notes on Assessment Plan

Habitus: http://en.wikipedia.org/wiki/Habitus_(sociology)

We are PEER to PEER ( sometimes we forget that )
ie "Don't make this depend on us"

Four planes
* helping assessing others
* working through (iterations)
* habits
* group work (roles)

Values: openness, community and peer learning doesnt make sense to someone thats outside P2PU
Habits: if you're helpful for one month vs. helpful for one year (more recognition based on how long they've been doing it)
Number of habits that we have should be quite small
Note to VMG: traits and habits appear very similar

tagging:
* schools get to introduce new tags "values"
* new tags shouldn't be totally free (need reputation to create them) stackexchange
[more established users establish the tags]

TRULY P2P
Why should we dictate these things
Tags--can enable tags to change
Most popular habits can change over time
Let the community decide by practice
(maybe a more elastic design)

John likes this:
submit work for feedback, not badges... byproduct, not end goal

Feedback as currency

• idea: feedback is a sort of currency, the more you give the more you get
• [bitcoin]
• think about the reputation you can pass around from user to user
• suggest making this happen in phases. ex: forget about metabadges in v1 and move that way later.

Person who receives feedback: s/b obligated to vote up or down or a plus
Get the most "credit" or reputation by feedback, then project, then votes up or down 

Posting a version -> good, should be rewarded
Posting feedback -> Better, should be rewarded more
reviewing feedback -> important, but shouldn't be rewarded very much, just a little to make sure we can validate feedback

Group work structure:

like the tag idea, how does it apply to non tech stuff?

idea: progress through many roles in a group until you've done them all
--

encourage diversity / restrictions on groups/ working with people that you haven't worked with before