Open shereefb opened 8 years ago
A few thoughts on principles for designing the conditions.
Deriving from these, here are some proposed stay-alive conditions, expressed as the terms of the learner-investor contract and the stats and processes that back them up:
The terms of the contract will be assessed as such:
Learners log their daily activities, including the type of activity and duration (increments of 15 min).
TBD
TBD
TBD
TBD
* “pair left” and “pair right” use the driver/navigator analogy with a driver assumed to be sitting in the left seat. Therefore, to “pair left” is to drive a pair with a less experienced navigator/observer, and to “pair right” is to navigate/observe a pair with a more experienced driver.
Proposed solution in #273.
In brief:
I really like this as a start.
Only red flag is that now stats don't have teeth. But maybe that's ok. Feels safe enough to try.
On Thu, Apr 14, 2016 at 8:59 AM Tanner Welsh notifications@github.com wrote:
Proposed solution in #273 https://github.com/LearnersGuild/learning-os/pull/273.
In brief:
- There are no game stats that determine how a player "stays alive"; stats are always for player's benefit to help them learn, but do not put them at risk of "failing"
- Learners can only get kicked out for breaching a Code of Conduct (set of behaviors/agreements)
— You are receiving this because you were assigned. Reply to this email directly or view it on GitHub https://github.com/LearnersGuild/learning-os/issues/195#issuecomment-210018084
"When they tell you to grow up, they mean stop growing.” ~Tom Robbins
Context
What mechanics / stats keep a player in the game
Criteria
Principles razor