102
edits
Changes
Jump to navigation
Jump to search
Line 4:
Line 4: − + − + − + − + − + − + − + Line 26:
Line 26: − + Line 120:
Line 120: − + + + Line 191:
Line 193: − + Line 204:
Line 206: − + Line 224:
Line 226: − + Line 237:
Line 239: − + Line 272:
Line 274: − +
no edit summary
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
|-style="background:#787878; color: white;"
! Project !! Student !! Mentor !! Blog
! Project !! Student !! Mentors !! Proposal !! Blog !! IRC nick
|-
|-
|Font Editor Activity||aku||Dave Crossland, Eli Heuer ||
|Font Editor Activity||Yash Agarwal||Dave Crossland, Eli Heuer || [https://sugarlabs.github.io/edit-fonts-activity/refined-proposal] || [http://sugarlabs.github.io/font-editor-activity/] || yagarwal
|-
|-
|Git Backend||Vikram Ahuja||Walter Bender, Tymon Radzik||
|Git Backend||Vikram Ahuja||Walter Bender, Tymon Radzik || Pending || [http://vikramahujagsoc.blogspot.com/] || vikram
|-
|-
|Journal Rethink||Abhijit Patel||Walter Bender, Sam Parkinson||
|Journal Rethink||Abhijit Patel||Walter Bender, Sam Parkinson||[https://www.docdroid.net/hbalTLC/1458885012-journal-rethink-proposal.pdf.html] || [http://abrahmab.github.io/] || AbrahmAB
|-
|-
|Music Widgets||Hemant Kasat||Walter Bender, Devin Ulibarri||
|Music Widgets||Hemant Kasat||Walter Bender, Devin Ulibarri || Pending || [http://musicblocks.net/2016/06/13/multiple-rhythm-rulers/] || hemant_kasat
|-
|-
|Sugarizer OS||Jeremie Amsellem||Lionel Laské, Michaël Ohayon||
|Sugarizer OS||Jeremie Amsellem||Lionel Laské, Michaël Ohayon || Pending || [http://lp1-eu.blogspot.fr/] || lp1
|-
|-
|Sugar on the Ground||Utkarsh Tiwari||Tony Anderson, Sebastian Silva||
|Sugar on the Ground||Utkarsh Tiwari||Tony Anderson, Sebastian Silva || [http://docdro.id/zx9U1Vd] || [https://iamutkarshtiwari.wordpress.com/about/google-summer-of-code16-with-sugar-labs-2/] || iamutkarshtiwari
|}
|}
;Note 1: Potential mentors, please feel free to add ideas to this list. Also, feel free to add your name to a project you'd be willing to co-mentor.
;Note 1: Potential mentors, please feel free to add ideas to this list. Also, feel free to add your name to a project you'd be willing to co-mentor.
;Note 2: Potential students, more project ideas can be found on our [[Features]] page.
;Note 2: Potential students, more project ideas can be found on our [[Features]] page.
;Note: Accepted projects are in <font color="#00bb00">Green</font>
;Note 3: Accepted projects are in <font color="#00bb00">Green</font>
== Sugar Core ==
== Sugar Core ==
|-
|-
!valign=top | || valign=top width = "15%" style="background:#00bb00;" | Font Editor Activity||valign=top width="15%" | with Dave Crossland || align=left valign=top|
!valign=top | || valign=top width = "15%" style="background:#00bb00;" | [[Font Editor|Font Editor Activity]]||valign=top width="15%" | with Dave Crossland || align=left valign=top|
;Brief explanation: Typeface design is a cornerstone of literate cultures, with subliminal power: Typefaces carry the emotions of texts, from formal designs that speak with authority to fun designs that are silly or military or ornate. They are both artistic and functional works, and our ability to share and modify them is important for the same reasons as for software programs. A Sugar font editor activity will empower users to create and modify fonts for their own tastes and needs. Fonts are fun to make, but we need an editor to do it.
;Brief explanation: Typeface design is a cornerstone of literate cultures, with subliminal power: Typefaces carry the emotions of texts, from formal designs that speak with authority to fun designs that are silly or military or ornate. They are both artistic and functional works, and our ability to share and modify them is important for the same reasons as for software programs. A Sugar font editor activity will empower users to create and modify fonts for their own tastes and needs. Fonts are fun to make, but we need an editor to do it.
;Expected results: Lots of free software Python and JavaScript libraries already exist so this project offers the possibility to make real progress for users this summer.
;Expected results: Lots of free software Python and JavaScript libraries already exist so this project offers the possibility to make real progress for users this summer.
;Knowledge prerequisite: Strong background in JavaScript or Python
;Knowledge prerequisite: Strong background in JavaScript or Python
:
:
|}
|}
|-
|-
!valign=top | [[File:Journal.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" | Sugar Journal save option ||valign=top width="15%" | Tony Anderson ||align=left valign=top|
!valign=top | [[File:Journal.png|90px|thumb|center]] ||valign=top width="15%" style="background:#00bb00;" | Sugar Journal save option ||valign=top width="15%" | Tony Anderson ||align=left valign=top|
The Sugar Journal should provide a 'save/save as' interface which should enable a user to choose whether to save the current document when an activity is closed. The interface should require a name change from 'current.activity' to a user supplied name. If the document is derived from one currently saved in the Journal, the user should be allowed to save (overwrite) or save as (create new document) by giving a new name to the document. This could be accomplished by showing a modal dialog at close time requesting the user to supply a name or not save the document. If the document has a user supplied name, the dialog could request the user to save or to provide a new name to create a new document.
The Sugar Journal should provide a 'save/save as' interface which should enable a user to choose whether to save the current document when an activity is closed. The interface should require a name change from 'current.activity' to a user supplied name. If the document is derived from one currently saved in the Journal, the user should be allowed to save (overwrite) or save as (create new document) by giving a new name to the document. This could be accomplished by showing a modal dialog at close time requesting the user to supply a name or not save the document. If the document has a user supplied name, the dialog could request the user to save or to provide a new name to create a new document.
|-
|-
!valign=top | [[File:Journal.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" | Sugar Journal backup and restore ||valign=top width="15%" | Tony Anderson ||align=left valign=top|
!valign=top | [[File:Journal.png|90px|thumb|center]] ||valign=top width="15%" style="background:#00bb00;" | Sugar Journal backup and restore ||valign=top width="15%" | Tony Anderson ||align=left valign=top|
Sugar provides a method to backup and restore the Journal (one method to a USB key and one method to the school server). The Journal also provides a select box to enable an action to be taken for all selected objects. This mechanism should be sufficient for the USB key case. However, the school server backup currently is based on taking a snapshot of the current Journal state. This means the size of the objects in a user's Journal cannot exceed the available local store on an XO (300MB for an XO-1, 1.9GB for other models). A mechanism is needed to save on the school server all documents created by the user and to restore a selected object to the Journal from the school server. Since many documents may represent library objects (e-books, audio, image or video media), the mechanism should recognize these and not save them as user documents. However, the metadata saved should enable the system to download the library items again as needed (and, as available).
Sugar provides a method to backup and restore the Journal (one method to a USB key and one method to the school server). The Journal also provides a select box to enable an action to be taken for all selected objects. This mechanism should be sufficient for the USB key case. However, the school server backup currently is based on taking a snapshot of the current Journal state. This means the size of the objects in a user's Journal cannot exceed the available local store on an XO (300MB for an XO-1, 1.9GB for other models). A mechanism is needed to save on the school server all documents created by the user and to restore a selected object to the Journal from the school server. Since many documents may represent library objects (e-books, audio, image or video media), the mechanism should recognize these and not save them as user documents. However, the metadata saved should enable the system to download the library items again as needed (and, as available).
;For example: the mechanism may be to upload Journal documents to an OwnCloud repository. The user could then select an item in the OwnCloud repository to be downloaded to the Journal. The user could also share any item in OwnCloud with other user groups or individuals
;For example: the mechanism may be to upload Journal documents to an OwnCloud repository. The user could then select an item in the OwnCloud repository to be downloaded to the Journal. The user could also share any item in OwnCloud with other user groups or individuals
|-
|-
!valign=top | [[File:Journal.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" | Sugar Journal activity resume feature ||valign=top width="15%" | Tony Anderson ||align=left valign=top|
!valign=top | [[File:Journal.png|90px|thumb|center]] ||valign=top width="15%" style="background:#00bb00;" | Sugar Journal activity resume feature ||valign=top width="15%" | Tony Anderson ||align=left valign=top|
In Sugar's Home View, a click on an activity icon by default resumes the most recent instance of the activity. This capability is designed into the Journal and is redundant in the Home View. A Sugar activity is a tool to enable the user to accomplish some task. If that task is not completed, the user can resume it via the Journal. If the tool is to be used on a new task, the user can launch it from the Home View. The current Home View assumes that the intent of the user is to continue the most recent task with that tool.
In Sugar's Home View, a click on an activity icon by default resumes the most recent instance of the activity. This capability is designed into the Journal and is redundant in the Home View. A Sugar activity is a tool to enable the user to accomplish some task. If that task is not completed, the user can resume it via the Journal. If the tool is to be used on a new task, the user can launch it from the Home View. The current Home View assumes that the intent of the user is to continue the most recent task with that tool.
|-
|-
!valign=top | [[File:Journal.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" | Sugar offline ||valign=top width="15%" | Tony Anderson ||align=left valign=top|
!valign=top | [[File:Journal.png|90px|thumb|center]] ||valign=top width="15%" style="background:#00bb00;" | Sugar offline ||valign=top width="15%" | Tony Anderson ||align=left valign=top|
There are a number of Sugar activities which currently require access to the internet (InfoSlicer, GetBooks). These activities should have an option to function with the school server. For example, GetBooks could access books on the school server and InfoSlicer could create slices from Wikipedia on the school server as Journal objects.
There are a number of Sugar activities which currently require access to the internet (InfoSlicer, GetBooks). These activities should have an option to function with the school server. For example, GetBooks could access books on the school server and InfoSlicer could create slices from Wikipedia on the school server as Journal objects.
|-
|-
!valign=top | [[File:Sugarizer os android.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" | Sugarizer OS ||valign=top width="15%" | Lionel Laské and Michaël Ohayon||align=left valign=top|
!valign=top | [[File:Sugarizer os android.png|90px|thumb|center]] ||valign=top width="15%" style="background:#00bb00;" | Sugarizer OS ||valign=top width="15%" | Lionel Laské and Michaël Ohayon||align=left valign=top|
The goal of this project is to create "Sugarizer OS".
The goal of this project is to create "Sugarizer OS".
Sugarizer OS is a way to boot directly a device on Sugarizer and allow the user to use both Sugarizer activities and system native applications. Sugarizer OS is not an OS but a way to propose a full Sugar experience on a non-Sugar device.
Sugarizer OS is a way to boot directly a device on Sugarizer and allow the user to use both Sugarizer activities and system native applications. Sugarizer OS is not an OS but a way to propose a full Sugar experience on a non-Sugar device.