You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 15, 2018. It is now read-only.
Some locations forget to update their status in Coderetreat Live. Some ignore Coderetreat Live altogether, while others forget to end their coderetreats. There is a lot going on during a coderetreat, and these mistakes are entirely understandable.
To make the app better show the status of the coderetreats, we could update Coderetreat Live to automatically start Coderetreates based on their scheduled start time (maybe an hour after the start time to give the real hosts a chance to start it). Likewise, the app could automatically end coderetreats that have been running for 10 hours (most coderetreats finish in less than 8 hours, so waiting 2 hours more gives some buffer for humans to more accurately stop the coderetreat).
I actually did this manually during GDCR 2015, with the help of a Google Spreasheet. In hindsight, there should be no reason to that manually (it is a lot of work).
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Some locations forget to update their status in Coderetreat Live. Some ignore Coderetreat Live altogether, while others forget to end their coderetreats. There is a lot going on during a coderetreat, and these mistakes are entirely understandable.
To make the app better show the status of the coderetreats, we could update Coderetreat Live to automatically start Coderetreates based on their scheduled start time (maybe an hour after the start time to give the real hosts a chance to start it). Likewise, the app could automatically end coderetreats that have been running for 10 hours (most coderetreats finish in less than 8 hours, so waiting 2 hours more gives some buffer for humans to more accurately stop the coderetreat).
I actually did this manually during GDCR 2015, with the help of a Google Spreasheet. In hindsight, there should be no reason to that manually (it is a lot of work).
The text was updated successfully, but these errors were encountered: