Mohayon (talk | contribs)
m email redacted
 
(2 intermediate revisions by one other user not shown)
Line 126: Line 126:
|05
|05
|June 12 - June 20
|June 12 - June 20
|
|Phase I Evaluation
|
|
*Formulate a robust upgrade process to ensure that Sugarizer updates are installed successfully without losing any data to instances that have been deployed.
*Formulate a robust upgrade process to ensure that Sugarizer updates are installed successfully without losing any data to instances that have been deployed.
Line 149: Line 149:
|08
|08
|July 09 - July 13
|July 09 - July 13
|
|Phase II Evaluation
|
|
*If the Turtle/Music Blocks release is on schedule, I will add it to the Sugarizer Pi Image build.
*If the Turtle/Music Blocks release is on schedule, I will add it to the Sugarizer Pi Image build.
Line 178: Line 178:
|12
|12
|6 Aug - August 14
|6 Aug - August 14
|
|Final Evaluation
|
|
*Keep a final buffer week for added tasks.
*Keep a final buffer week for added tasks.
Line 188: Line 188:
|
|
|-
|-
|
|August 06 - August 14
|Final Evaluations
|
|}
|}


Line 219: Line 215:
=== Answers from the Community ===
=== Answers from the Community ===
:
:
*:'''Michaël Ohayon''' - mohayon75@gmail.com (Potential GSoC Mentor)
*:'''Michaël Ohayon''' (Potential GSoC Mentor)
:: 1) I think that the Pi will be able to handle the load, we won’t have that much kids connected to the same Pi and the networking process is not that heavy.
:: 1) I think that the Pi will be able to handle the load, we won’t have that much kids connected to the same Pi and the networking process is not that heavy.
::We should try to launch the server in background and display a web browser in foreground. If the load is too high we will see it quickly.
::We should try to launch the server in background and display a web browser in foreground. If the load is too high we will see it quickly.