Summer of Code/2016: Difference between revisions
| Line 16: | Line 16: | ||
|- | |- | ||
!valign=top | [[File:Journal-12.jpeg|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" |Journal Rethink ||valign=top width="15%" | Sam Parkinson ||align=left valign=top| | !valign=top | [[File:Journal-12.jpeg|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" |Journal Rethink ||valign=top width="15%" | Sam Parkinson ||align=left valign=top| | ||
;Brief explanation: The Sugar Journal could be rethought to add more emphasis on collaboration, or adding more organisational support for creating "projects" | ;Brief explanation: The Sugar Journal could be rethought to add more emphasis on collaboration, or adding more organisational support for creating "projects" among other things. | ||
;Expected results: Working code for the journal | ;Expected results: Working code for the journal and vague ideas (more concrete than this) defined ahead of time. | ||
;Knowledge prerequisite: Strong background in Python and knowledge of Gtk+. | |||
|- | |||
!valign=top | [[File:Journal-12.jpeg|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" |Reflection Activity||valign=top width="15%" | Sam Parkinson and Walter Bender ||align=left valign=top| | |||
;Brief explanation: The Sugar Journal is designed to be a place of reflection. We have the basic stub of a reflection activity that attempts to encourage more reflection and as a vehicle for sharing criticism. This idea needs more thought and coding. | |||
;Expected results: A solid formulation of how the activity will work in the classroom and working code for the Reflection Activity. | |||
;Knowledge prerequisite: Strong background in Python and knowledge of Gtk+. | ;Knowledge prerequisite: Strong background in Python and knowledge of Gtk+. | ||