mosaic
mosaic copied to clipboard
[to increase tree turn-around time] let participant know the schedulingPriority
could be smthg like this is tree priority number X
Liam said they are more interested in working on high-priority trees (aka trees that will complete sooner) and that's also what Ought would want ideally: have participants spend their Ought time budget on high-priority trees in order to increase the tree turn-around time
source: https://app.slack.com/client/T3L8K3NMT/CMVHF5HJ8/thread/CMVHF5HJ8-1567227911.014000
As an interim solution, would it work to simply close a workspace once I see it's high-depth (good proxy for non-priority I would think) and wait a few hours before logging back in?
I would call this low depth. But yes. If there's 5 depths remaining and no sub-questions, then it's a new tree. Otherwise, it's hard to tell. A 4 depths remaining could still be high priority, but 0-2 depths remaining is likely to be high priority.
@Mati-Roy has anyone other than Liam requested this?
not that I'm aware