https://wiki.sugarlabs.org/api.php?action=feedcontributions&user=Icarito&feedformat=atomSugar Labs - User contributions [en]2024-03-29T09:04:19ZUser contributionsMediaWiki 1.35.2https://wiki.sugarlabs.org/index.php?title=Oversight_Board/2014-2015-candidates&diff=94595Oversight Board/2014-2015-candidates2015-03-10T16:34:05Z<p>Icarito: </p>
<hr />
<div><noinclude>[[Category:Oversight board]]<br />
[[Category:Governance]]<br />
[[Category:Team]]<br />
</noinclude><br />
<br />
==Election==<br />
Four (4) seats are open ([[Sugar Labs/Governance#Oversight_Board|due to staggered seat terms]]) for election / re-election to the [[Oversight Board|Sugar Labs Oversight Board]] for 2014-2015, those of Daniel Francis, Gonzalo Odiard, Adam Holt, and Claudia Urrea.<br />
<br />
==Candidates==<br />
Here are the candidates:<br />
* Gonzalo Odiard ([[User:Godiard/SugarOversightCandidacy2012#Sugar_Oversight_candidacy_2015.2F2016|proposals]])<br />
* Edward [[User:Mokurai | Mokurai]] Cherlin [[Open Educational Resources]]<br />
* Laura Vargas [http://pe.sugarlabs.org/ir/~kaametza Sugar Evolution]<br />
* '''Your name''' (''link to your platform'')<br />
<br />
==References==<br />
* [[Oversight_Board/2013-2014-candidates]]<br />
* [[Oversight_Board/2012-2013-candidates]]<br />
* [[Oversight_Board/2011-2012-candidates]]<br />
* [[Oversight_Board/2010-2011-candidates]]<br />
* [[Oversight_Board/2009-2010-candidates]]<br />
* [[Sugar Labs/Members]]</div>Icaritohttps://wiki.sugarlabs.org/index.php?title=Sugar_Network/1.0/Issues&diff=92502Sugar Network/1.0/Issues2014-05-07T17:47:31Z<p>Icarito: </p>
<hr />
<div>== Known issues ==<br />
<br />
=== Testing conducted on XO1.5 w/ webui 0.9 ===<br />
<br />
* Unable to edit Project<br />
* Search functionality only searches within activities, not projects<br />
* In fact "all" contexts only return activities, not projects<br />
* Uploading artifacts fails silently. Aparently empty records are created.<br />
* All projects have a "sad face" icon now.</div>Icaritohttps://wiki.sugarlabs.org/index.php?title=Sugar_Network/1.0/Todo&diff=92501Sugar Network/1.0/Todo2014-05-07T17:32:32Z<p>Icarito: /* 0.8 */</p>
<hr />
<div>== Features ==<br />
<br />
This is a list of features that need to be implemented during the [[#Intermediate_releases|intermediate releases]]. In brackets, there will be mentioned [[#Intermediate_releases|intermediate releases]] that when particular feature needs to be initially implemented (obviously, that implementation needs to be polished until final 1.0 release).<br />
<br />
=== Sugar Network ===<br />
<br />
Features related to [[Sugar Network]] implementation.<br />
<br />
===== Object domain =====<br />
<br />
The detailed information about Sugar Network object domain might be found on [[Sugar_Network/Concept|concept pages]] and in [[Platform_Team/Sugar_Network/Objects_model|objects model]]. But in short, Sugar Network objects are represented by the following list (object names might not be exposed in final GUI):<br />
<br />
* ''<u>Context</u>''<br>These are the top-level entities that represent content in the Sugar Network and might be several types:<br />
** Sugar Activities ([[#0.1|0.1]]),<br />
** {{Code|.xol}} files ([[#0.3|0.3]]);<br />
** arbitrary documents that might be opened by the Sugar, e.g., PDF or HTML files that represent, e.g., books ([[#0.3|0.3]]);<br />
** (this list might be extended before releasing 1.0, e.g., by editable Wiki articles).<br />
<br />
The rest of objects directly or indirectly associated with ''Contexts''.<br />
<br />
* ''<u>Question</u>'' ([[#0.1|0.1]])<br>General questions about ''Contexts''. The idea is populating the knowledge base for the ''Context'', similar (but much simpler) to [http://stackoverflow.com/ stackoverflow site].<br />
<br />
* ''<u>Idea</u>'' ([[#0.2|0.2]])<br>Any ideas regarding ''Contexts''.<br />
<br />
* ''<u>Problems</u>'' ([[#0.2|0.2]])<br>Report a problem with ''Contexts''. A user-friendly interface to complain about an error that the users encountered when working with the ''Context''. It is not intended to be a full functional bugs reporting system, but rather a users friendly interface to ask questions. For real bugs reporting case, there is semiautomatic ''Report'' object, or experienced people can use already existing bugs reporting systems.<br />
<br />
* ''<u>Solution</u>'' ([[#0.3|0.3]])<br>Object represent exactly a solution for particular ''Question'', ''Idea'', ''Problem''.<br />
<br />
* ''<u>Review</u>'' (?)<br>A post that reviews the ''Context''.<br />
<br />
* ''<u>Comment</u>'' (?)<br>Short comment for existing ''Question'', ''Idea'', ''Problem'', ''Review'' object. If you have a post with more than a couple of lines, consider creating new object instead of commenting existing one.<br />
<br />
* ''<u>Artifact</u>'' (?)<br>Object created within the ''Context'':<br />
** Activity objects,<br />
** (this list might be extended before releasing 1.0).<br />
<br />
* ''<u>Report</u>'' ([[#0.25|0.25]])<br>Semi automatic reports created if Sugar activity failed to start/stop.<br />
<br />
===== Workflows =====<br />
<br />
From users point of view.<br />
<br />
* <strike>Browse ''Contexts''</strike> ([[#0.1|0.1]]);<br />
* <strike>Bookmark ''Contexts''</strike> ([[#0.2|0.2]]);<br />
* <strike>Launch ''Contexts'' as Sugar activities</strike> ([[#0.1|0.1]]);<br />
* Support online and offline modes where in offline, only selected ''Contexts'' will be accessible ([[#0.3|0.3]]);<br />
* <strike>Create ''Questions'', ''Ideas'', ''Problems''</strike> ([[#0.2|0.2]]);<br />
* Browse and create ''Solutions'' for ''Questions'', ''Ideas'', ''Problems'' ([[#0.25|0.25]]);<br />
* Comment objects (?);<br />
* Semi automatic creating ''Reports'' ([[#0.25|0.25]]);<br />
* Subscriptions to events for particular ''Contexts'' (?);<br />
* Visually expose already visited content [http://groups.google.com/group/sugar-network/browse_thread/thread/6c5a7b2f4cab7583] (?)<br />
<br />
From point of view of people who can help with solving problems.<br />
<br />
* <strike>Browse and create ''Solutions'' for ''Questions'', ''Ideas'', ''Problems''</strike> ([[#0.25|0.25]]);<br />
* Subscriptions to events for ''Contexts'' people are responsible for (?);<br />
<br />
From content creators/uploaders point of view.<br />
<br />
* <strike>ASLO activities will be delivered from Sugar Network</strike> ([[#0.1|0.1]]);<br />
* Create new ''Content'' for Sugar activity (?);<br />
* Create new ''Content'' for arbitrary document (.xol, PDF, HTML, etc) (?);<br />
* Upload new versions (?).<br />
<br />
From point of view of people who are willing to take part in quality assurance (QA) process.<br />
<br />
* ..<br />
<br />
== Development releases ==<br />
<br />
More detailed TODO list for particular intermediate releases according to the [[Platform_Team/Harmonic_Distribution/1.0/Roadmap|roadmap]].<br />
<br />
=== 0.1 ===<br />
<br />
* <strike>Users friendly Sucrose+Sugar Network client distribution.</strike> Done.<br />
<br />
Distribution will be formed as 3rd party repositories to install packages, i.e., something like Sweets Distribution.<br />
<br />
Packages will include:<br />
<br />
* Sucrose with integrated SN client<br />
* Pre-configured environment to start using SN from server hosted on SL server<br />
<br />
So, after attaching this repository, installing one package and launching sugar, people will see current SN implementation and start collaborating on public SN server. Collaboration will include:<br />
<br />
* launching activities from the SN (mirrored from ASLO)<br />
* populate already implemented resources, linked to activities, e.g., Questions <br />
</strike><br />
Sugar Shell will provide the following options for providing SN content:<br />
<br />
* <strike>Original Home view (not SN), by default</strike> Empty favorites view, will be improved in 0.2;<br />
* <strike>Original Home view with activities provided from SN, limited meanwhile solution</strike> Favorites view will contain local activities downloaded from SN in 0.2;<br />
* SN client instead of <strike>Home View</strike> list view.<br />
<br />
Switch between Home View modes will happen from Control Panel.<br />
<br />
=== 0.2 ===<br />
<br />
* <strike>Investigate Jabber related issues: [http://lists.sugarlabs.org/archive/sugar-devel/2012-March/036322.html].</strike> Major work is done, minor issues might be fixed in process.<br />
* <strike>Synchronization between SN nodes.</strike> No chances to have it in 0.2, postponed to 0.3.<br />
* <strike>Server notifications about SN data changes.</strike> Implemented on server side, client will use it in 0.3.<br />
* <strike>Expose favorited contexts in favorite view in Home view.</strike> Right now, Home view shows activities from ~/Activities.<br />
* <strike>Revise Dextrose-3 patches to exclude ones that don't make sense after enabling Sugar Network.</strike> Some bugs fixing commits were merged to SD [[Platform_Team/Sweets_Distribution/Factory#Sources|repositories]].<br />
* <strike>Prepare .pot files.</strike> Moved to 0.3, translation.sugarlabs.org process should be setup before 0.3 release.<br />
* <strike>XO images for students and teachers, teachers server. This downstream work Will be done within the Hexokinase project.</strike> Moved to 0.25.<br />
<br />
=== 0.25 ===<br />
<br />
Release targeted to getting initial feedback from teachers in Comas district in Lima.<br />
<br />
* <strike>Continue working on client GUI improvements</strike>;<br />
* <strike>Initial implementation of ''Solutions'' in client GUI</strike>;<br />
* <strike>Make it possible to create new ''Reports'' in GUI after getting Sugar activity failed;</strike><br />
* <strike>Client application needs to reflect on server side changes to avoid showing stale data;</strike> Postponed for 0.3.<br />
* <strike>XO images for students and teachers (teachers server) to start testing the system right after flashing XOs.</strike><br />
<br />
=== 0.3 ===<br />
<br />
* <strike>Consider running the system in Fedora-11 (current in use in Peru).</strike> Sugar 0.94 and SN starts well.<br />
* <strike>Distribute base software updates.</strike> <span style="color: red">Moved to 0.4.</span><br />
* <strike>Start gathering [[Platform_Team/Usage_Statistics|usage statistics]].</strike> <span style="color: red">Moved to 0.4.</span><br />
* <strike>Define/Document some useful usage indicators for SN interaction.</strike> <span style="color: red">Moved to 0.4.</span><br />
* <strike>More useful client behavior in offline scenario, e.g. show content accessible locally.</strike> Initial implementation in place.<br />
* <strike>Optimize current implementation to make it more useful on XO-1 laptops.</strike> The second shell start (after calling {{Code|sugar}} command and before appearing Journal icon) for 40 installed activities is only 6 seconds longer than with Dextrose-3.<br />
* <strike>Setup -testing server instance that will keep regular SN content that should be migrated to new code base on every release.</strike>. Sugar Shell looks for http://api-testing.network.sugarlabs.org by default, there is also read-only public web server, http://network-testing.sugarlabs.org.<br />
* <strike>Setup translation.sugarlabs.org translation process.</strike> <span style="color: red">Moved to 0.4.</span><br />
* <strike>Handle server notifications about SN data changes in client application.</strike> <span style="color: red">Moved to 0.4.</span><br />
* <strike>Synchronization between SN nodes.</strike> <span style="color: red">Moved to 0.4.</span><br />
* <strike>Basic i18n support in SN content (excluding managing already entered strings).</strike><br />
* <strike>Basic routines for SN editors (including initial populating SN content):</strike> 0.3 will contain only trivial and ready use activities, the editors workflow implementation work will start from 0.4.<br />
* <strike>Since there are useful binary based activities (GC, TuxPaint), support upload such activities to SN. From developers point of view, the only they need to proceed is uploading sources bundle to SN, the rest (building sources for all supported platforms) should happen automatically.</strike> <span style="color: red">Moved to 0.4.</span><br />
* <strike>Revise most popular ASLO activities to add all needed meta information (like required dependencies) and mark the as stable and ready to run from Sugar Network.</strike> Thanks to [[User:Satellit|satellit]], testing server contains only activities that start without problems.<br />
* <strike>Worfklow to semi automatic collect fail reports using Report resource.</strike> Move to 0.25.<br />
* <strike>final XO image, for students and teachers (teachers server), that is ready for deploying.</strike> <span style="color: red">Moved to 0.4.</span><br />
<br />
=== 0.4 ===<br />
<br />
* <strike>Fix issue with creating new Journal entity on every launch from F8.</strike> <span style="color: red">Moved to 0.5.</span><br />
* <strike>Edit resources capability</strike><br />
* <strike>Delete comments capability</strike><br />
* <strike>Create context capability</strike><br />
* <strike>Distribute base software updates.</strike> <span style="color: red">Moved to 0.5.</span><br />
* <strike>Start gathering [[Platform_Team/Usage_Statistics|usage statistics]].</strike> <span style="color: red">Moved to 0.5.</span><br />
* <strike>Define/Document some useful usage indicators for SN interaction.</strike><br />
* <strike>Setup translation.sugarlabs.org translation process.</strike><br />
* <strike>Synchronization between SN nodes.</strike><br />
* <strike>Upload arbitrary documents as contexts to SN</strike> <span style="color: red">Moved to 0.5.</span> with <strike>segregation in webui</strike>.<br />
* <strike>Final XO image, for students and teachers (teachers server), that is ready for deploying to start testing in the field.</strike> Next [http://download.sugarlabs.org/hexokinase/Factory/ development] XO images and images targeting to Peru deployment [http://download.sugarlabs.org/hexokinase/].<br />
<br />
=== 0.5 ===<br />
<br />
* <strike>Journal integration:</strike> Journal is accessible as Artifact resource from {{Code|~}} mount point.<br />
** <strike>Fix an issue with creating new Journal entity on every launch from F8.</strike><span style="color: red">Moved to 0.6.</span><br />
** <strike>Upload arbitrary documents as contexts to SN.</strike><span style="color: red">Moved to 0.6.</span><br />
* <strike>Make it possible to show a top of recent comments for all currently represented resources in webui. That should help with fast observing the current discussion status.</strike><span style="color: red">Moved to 0.6.</span><br />
* <strike>Offline updates for base software updates.</strike><br />
* <strike>Start gathering [[Platform_Team/Usage_Statistics|usage statistics]].</strike><br />
* <strike>[[Wiki:Create,_read,_update_and_delete|CRUD]] workflow for SN content.</strike><span style="color: red">Moved to 0.6.</span><br />
* <strike>Basic routines for SN editors (including initial populating SN content):<br />
** let all people, not only editors, expose the fact that particular activity [doesn't]works in theirs environment (maybe just by exposing how many fail Reports exist for the Implementation, Report might have the level of failure: doesn't do basic work, doesn't do optional work but basic features work fine).</strike><span style="color: red">Moved to 0.6.</span><br />
<br />
=== 0.6 ===<br />
<br />
* <strike>Reliable way to start Sugar Activities that have additional dependencies.</strike> <span style="color: red">Moved to 0.7.</span><br />
* <strike>Fix an issue with creating new Journal entity on every launch from F8.</strike> <span style="color: red">Moved to 0.7.</span><br />
* <strike>Upload arbitrary documents as contexts to SN.</strike> <span style="color: red">Moved to 0.7.</span><br />
* <strike>Make it possible to show a top of recent comments for all currently represented resources in webui. That should help with fast observing the current discussion status.</strike> <span style="color: red">Moved to 0.7.</span><br />
* Initial implementation of Contributor Hub.<br />
* Synchronize testing server with ASLO.<br />
<br />
=== 0.7 ===<br />
<br />
Server side:<br />
<br />
* <strike>Server side stats.</strike><br />
<br />
Client side:<br />
<br />
* <strike>Support server side stats.</strike> No need.<br />
* <strike>Process package dependencies in order to provide reliable start of Sugar Activities.</strike><br />
* <strike>Resume Sugar Network non-activities content, e.g., Journal objects or .xol libraries.</strike><br />
* <strike>RO access to local Journal</strike>.<br />
<br />
WebUI:<br />
<br />
* Offline work and Syncronization functionality<br />
* Include notes regarding the licenses applicable for published content<br />
* Fix an issue with creating new Journal entity on every launch from F8.<br />
* ...<br />
<br />
Contributor Hub:<br />
<br />
* <strike>Upload content, e.g., .pdf files.</strike><br />
<br />
=== 0.8 ===<br />
<br />
Server and client side:<br />
<br />
* <strike>Offline usecase for Sugar Network nodes.</strike> Moved to 0.10+<br />
* Support ''Users' home page''.<br />
<br />
WebUI:<br />
* <strike>Subscriptions and Notifications.</strike> Moved to 0.10+<br />
* <strike>''Users' home page''.</strike> Moved to 0.10+<br />
<br />
Contributor Hub:<br />
<br />
* Visualize server stats.<br />
<br />
=== 1.0 ===<br />
<br />
No new features, only polishing.<br />
<br />
Final release should have. Difficulties are from 0 (impossible) to 5 (trivial).<br />
<br />
'''General'''<br />
<br />
* Sugar Network content related features:<br />
** Uploading non-software content. Difficulty 5.<br />
** <strike>Uploading non-binary activities. Difficulty 3.</strike> Activities will come from regular ASLO sync.<br />
** Share Journal objects.<br />
<br />
* Statistics related features:<br />
** Server side stats, e.g., ''likes'' for resources. Difficulty 2.<br />
** <strike>Personal users' stats</strike> Implemented in [[Sugar_Server_Kit/sugar-client#Collecting_usage_statistics|sugar-client]].<br />
** Visualize stats.<br />
<br />
* ''Users' home page'' to keep them up-to-date:<br />
** Live updates in resources user is subscribed after becoming online. Difficulty 4.<br />
** Getting digest of changes happened in resources where logged user is an author. Difficulty 3.<br />
<br />
* Sugar Network editors workflow:<br />
** Multiple authors per Context to let several people change Context metadata (it is all time possible to create related objects by any user). Difficulty 4.<br />
** <strike>Contributor Hub should provide a UI to let deployment supported to select what content should be accessible for particular deployment. Difficulty 3.</strike><br />
** ..<br />
<br />
'''WebUI'''<br />
<br />
* Share Journal objects.<br />
* Users' ''home page'' to keep them up-to-date.<br />
* ...<br />
<br />
'''Contributor Hub'''<br />
<br />
* Upload content.<br />
* Stats visualization.<br />
<br />
=== Post 1.0 ===<br />
<br />
* Full support of offline deployments.<br />
* Full support for server-less use-case for users.<br />
* Support binary based activities.<br />
<br />
== Statistics to gather ==<br />
<br />
Statistic types:<br />
<br />
* ''network-server''<br>Stats will be collected on Sugar Network server and stored in [[wikipedia:Round-Robin_Database|round-robin]] storage for further analyzing;<br />
* ''client-sniffer''<br>Stats will be collected by special sniffer, e.g., [[Sugar_Server_Kit/sugar-client|sugar-client]], launched on client side to collect local stats, in [[wikipedia:Round-Robin_Database|round-robin]] database, with following transmitting to the Sugar Network server;<br />
* ''unknown''<br>Ambiguous stats criterion.<br />
<br />
===Interactions===<br />
<br />
*Contexts Searches (''network-server'').<br />
*Context [Activity Type] Launches (''client-sniffer'').<br />
*Context [Activity Type] Failure Reports (''network-server'').<br />
*Context [Project Type] Views (''unknown'').<br />
*Context [Project Type] Creation (''network-server'').<br />
*Context [Project Type] Editing (''network-server'').<br />
*Resource Creation/Editing/Commenting Review Type (''network-server'').<br />
*Resource Creation/Editing/Commenting/Solving Question Type (''network-server'').<br />
*Resource Creation/Editing/Commenting Idea Type (''network-server'').<br />
*Resource Creation/Editing/Commenting/Solving Problem Type (''network-server'').<br />
<br />
===Participants===<br />
<br />
*Total Users: Total number of participants at any time (counting since network launching) (''network-server'').<br />
*Period New Users: Simple summation of the number of new participants over the course of a specified time period (''network-server'').<br />
*Period Active Users: Simple summation of the number of participants that registered at least one effective interaction on the network over the course of a specified time period (''network-server'').<br />
*Period Unique Visitors: The number of unduplicated (counted only once) visitors to the network over the course of a specified time period (visitors may or may not make effective interactions) (''network-server'').<br />
*Top/Ranking Users: [how to rank participation?] [total / by period?] [also, sort by Location or Conexion type?] (''unknown'')<br />
<br />
===Usage===<br />
<br />
*Total Visits: Total number of visits to the network at any time (counting since network launching). (''network-server'')<br />
*Period Visits: Total number of visits to the network over the course of a specified time period. (''network-server'')<br />
*Period Effective Visits: Simple summation of the number of visits that registered at least one effective interaction on the network over the course of a specified time period. (''network-server'')<br />
*Period Interactions Per Visit: Average number of effective interactions per visit on the network over the course of a specified time period. (''network-server'')<br />
<br />
===Content===<br />
<br />
*Total Contexts [Activity type]: simple summation of contexts of Activity type at any time (counting since network launching). (''network-server'')<br />
*Period New Contexts [Activity type]: simple summation of the total number of created contexts of Activity type over the course of a specified time period. (''network-server'')<br />
*Period Active Contexts [Activity type]: simple summation of the total number of contexts of Activity type that registered at least one effective interaction over the course of a specified time period. (''network-server'')<br />
*Total Contexts [Project type]: simple summation of contexts of Proejct type at any time (counting since network launching). (''network-server'')<br />
*Period New Contexts [Project type]: simple summation of the total number of created contexts of Project type over the course of a specified time period. (''network-server'')<br />
*Period Active Contexts [Project type]: simple summation of the total number of contexts of Project type that registered at least one effective interaction over the course of a specified time period. (''network-server'')<br />
*Period Context Ranking [100?] of Contexts by type: most interacted Contexts over the course of a specified time period. (''unknown'')<br />
<br />
== Inventory of technical issues outside Client and Server ==<br />
<br />
* How will students register with a teacher<br />
* How will teachers turn their laptop into servers<br />
* What are the constraints of the syncronization mechanism<br />
* Patch to Journal for sharing in SN<br />
<br />
== Questions for educators/experts ==<br />
<br />
* What kind of users' statistics will be useful for educators/researchers?<br>See the current [[Platform_Team/Usage_Statistics|implementation]] of Australian [https://dev.laptop.org.au/issues/59 request]. The collected data are being stored in [[Wikipedia:Round-Robin_Database|RRD]] format and might be represented in [http://oss.oetiker.ch/rrdtool/gallery/index.en.html graphics].<br />
* Should students, teachers be clearly separated in the GUI?<br />
* Should teachers track what their students do within the Network?<br />
* Should the students track what they do within the Network?<br />
* Should teachers moderate what their students do within the Network?<br />
<br />
* What kind of users' statistics will be useful for teachers and learners?</div>Icaritohttps://wiki.sugarlabs.org/index.php?title=Sugar_Network/1.0/Todo&diff=92500Sugar Network/1.0/Todo2014-05-07T17:31:30Z<p>Icarito: /* 0.8 */</p>
<hr />
<div>== Features ==<br />
<br />
This is a list of features that need to be implemented during the [[#Intermediate_releases|intermediate releases]]. In brackets, there will be mentioned [[#Intermediate_releases|intermediate releases]] that when particular feature needs to be initially implemented (obviously, that implementation needs to be polished until final 1.0 release).<br />
<br />
=== Sugar Network ===<br />
<br />
Features related to [[Sugar Network]] implementation.<br />
<br />
===== Object domain =====<br />
<br />
The detailed information about Sugar Network object domain might be found on [[Sugar_Network/Concept|concept pages]] and in [[Platform_Team/Sugar_Network/Objects_model|objects model]]. But in short, Sugar Network objects are represented by the following list (object names might not be exposed in final GUI):<br />
<br />
* ''<u>Context</u>''<br>These are the top-level entities that represent content in the Sugar Network and might be several types:<br />
** Sugar Activities ([[#0.1|0.1]]),<br />
** {{Code|.xol}} files ([[#0.3|0.3]]);<br />
** arbitrary documents that might be opened by the Sugar, e.g., PDF or HTML files that represent, e.g., books ([[#0.3|0.3]]);<br />
** (this list might be extended before releasing 1.0, e.g., by editable Wiki articles).<br />
<br />
The rest of objects directly or indirectly associated with ''Contexts''.<br />
<br />
* ''<u>Question</u>'' ([[#0.1|0.1]])<br>General questions about ''Contexts''. The idea is populating the knowledge base for the ''Context'', similar (but much simpler) to [http://stackoverflow.com/ stackoverflow site].<br />
<br />
* ''<u>Idea</u>'' ([[#0.2|0.2]])<br>Any ideas regarding ''Contexts''.<br />
<br />
* ''<u>Problems</u>'' ([[#0.2|0.2]])<br>Report a problem with ''Contexts''. A user-friendly interface to complain about an error that the users encountered when working with the ''Context''. It is not intended to be a full functional bugs reporting system, but rather a users friendly interface to ask questions. For real bugs reporting case, there is semiautomatic ''Report'' object, or experienced people can use already existing bugs reporting systems.<br />
<br />
* ''<u>Solution</u>'' ([[#0.3|0.3]])<br>Object represent exactly a solution for particular ''Question'', ''Idea'', ''Problem''.<br />
<br />
* ''<u>Review</u>'' (?)<br>A post that reviews the ''Context''.<br />
<br />
* ''<u>Comment</u>'' (?)<br>Short comment for existing ''Question'', ''Idea'', ''Problem'', ''Review'' object. If you have a post with more than a couple of lines, consider creating new object instead of commenting existing one.<br />
<br />
* ''<u>Artifact</u>'' (?)<br>Object created within the ''Context'':<br />
** Activity objects,<br />
** (this list might be extended before releasing 1.0).<br />
<br />
* ''<u>Report</u>'' ([[#0.25|0.25]])<br>Semi automatic reports created if Sugar activity failed to start/stop.<br />
<br />
===== Workflows =====<br />
<br />
From users point of view.<br />
<br />
* <strike>Browse ''Contexts''</strike> ([[#0.1|0.1]]);<br />
* <strike>Bookmark ''Contexts''</strike> ([[#0.2|0.2]]);<br />
* <strike>Launch ''Contexts'' as Sugar activities</strike> ([[#0.1|0.1]]);<br />
* Support online and offline modes where in offline, only selected ''Contexts'' will be accessible ([[#0.3|0.3]]);<br />
* <strike>Create ''Questions'', ''Ideas'', ''Problems''</strike> ([[#0.2|0.2]]);<br />
* Browse and create ''Solutions'' for ''Questions'', ''Ideas'', ''Problems'' ([[#0.25|0.25]]);<br />
* Comment objects (?);<br />
* Semi automatic creating ''Reports'' ([[#0.25|0.25]]);<br />
* Subscriptions to events for particular ''Contexts'' (?);<br />
* Visually expose already visited content [http://groups.google.com/group/sugar-network/browse_thread/thread/6c5a7b2f4cab7583] (?)<br />
<br />
From point of view of people who can help with solving problems.<br />
<br />
* <strike>Browse and create ''Solutions'' for ''Questions'', ''Ideas'', ''Problems''</strike> ([[#0.25|0.25]]);<br />
* Subscriptions to events for ''Contexts'' people are responsible for (?);<br />
<br />
From content creators/uploaders point of view.<br />
<br />
* <strike>ASLO activities will be delivered from Sugar Network</strike> ([[#0.1|0.1]]);<br />
* Create new ''Content'' for Sugar activity (?);<br />
* Create new ''Content'' for arbitrary document (.xol, PDF, HTML, etc) (?);<br />
* Upload new versions (?).<br />
<br />
From point of view of people who are willing to take part in quality assurance (QA) process.<br />
<br />
* ..<br />
<br />
== Development releases ==<br />
<br />
More detailed TODO list for particular intermediate releases according to the [[Platform_Team/Harmonic_Distribution/1.0/Roadmap|roadmap]].<br />
<br />
=== 0.1 ===<br />
<br />
* <strike>Users friendly Sucrose+Sugar Network client distribution.</strike> Done.<br />
<br />
Distribution will be formed as 3rd party repositories to install packages, i.e., something like Sweets Distribution.<br />
<br />
Packages will include:<br />
<br />
* Sucrose with integrated SN client<br />
* Pre-configured environment to start using SN from server hosted on SL server<br />
<br />
So, after attaching this repository, installing one package and launching sugar, people will see current SN implementation and start collaborating on public SN server. Collaboration will include:<br />
<br />
* launching activities from the SN (mirrored from ASLO)<br />
* populate already implemented resources, linked to activities, e.g., Questions <br />
</strike><br />
Sugar Shell will provide the following options for providing SN content:<br />
<br />
* <strike>Original Home view (not SN), by default</strike> Empty favorites view, will be improved in 0.2;<br />
* <strike>Original Home view with activities provided from SN, limited meanwhile solution</strike> Favorites view will contain local activities downloaded from SN in 0.2;<br />
* SN client instead of <strike>Home View</strike> list view.<br />
<br />
Switch between Home View modes will happen from Control Panel.<br />
<br />
=== 0.2 ===<br />
<br />
* <strike>Investigate Jabber related issues: [http://lists.sugarlabs.org/archive/sugar-devel/2012-March/036322.html].</strike> Major work is done, minor issues might be fixed in process.<br />
* <strike>Synchronization between SN nodes.</strike> No chances to have it in 0.2, postponed to 0.3.<br />
* <strike>Server notifications about SN data changes.</strike> Implemented on server side, client will use it in 0.3.<br />
* <strike>Expose favorited contexts in favorite view in Home view.</strike> Right now, Home view shows activities from ~/Activities.<br />
* <strike>Revise Dextrose-3 patches to exclude ones that don't make sense after enabling Sugar Network.</strike> Some bugs fixing commits were merged to SD [[Platform_Team/Sweets_Distribution/Factory#Sources|repositories]].<br />
* <strike>Prepare .pot files.</strike> Moved to 0.3, translation.sugarlabs.org process should be setup before 0.3 release.<br />
* <strike>XO images for students and teachers, teachers server. This downstream work Will be done within the Hexokinase project.</strike> Moved to 0.25.<br />
<br />
=== 0.25 ===<br />
<br />
Release targeted to getting initial feedback from teachers in Comas district in Lima.<br />
<br />
* <strike>Continue working on client GUI improvements</strike>;<br />
* <strike>Initial implementation of ''Solutions'' in client GUI</strike>;<br />
* <strike>Make it possible to create new ''Reports'' in GUI after getting Sugar activity failed;</strike><br />
* <strike>Client application needs to reflect on server side changes to avoid showing stale data;</strike> Postponed for 0.3.<br />
* <strike>XO images for students and teachers (teachers server) to start testing the system right after flashing XOs.</strike><br />
<br />
=== 0.3 ===<br />
<br />
* <strike>Consider running the system in Fedora-11 (current in use in Peru).</strike> Sugar 0.94 and SN starts well.<br />
* <strike>Distribute base software updates.</strike> <span style="color: red">Moved to 0.4.</span><br />
* <strike>Start gathering [[Platform_Team/Usage_Statistics|usage statistics]].</strike> <span style="color: red">Moved to 0.4.</span><br />
* <strike>Define/Document some useful usage indicators for SN interaction.</strike> <span style="color: red">Moved to 0.4.</span><br />
* <strike>More useful client behavior in offline scenario, e.g. show content accessible locally.</strike> Initial implementation in place.<br />
* <strike>Optimize current implementation to make it more useful on XO-1 laptops.</strike> The second shell start (after calling {{Code|sugar}} command and before appearing Journal icon) for 40 installed activities is only 6 seconds longer than with Dextrose-3.<br />
* <strike>Setup -testing server instance that will keep regular SN content that should be migrated to new code base on every release.</strike>. Sugar Shell looks for http://api-testing.network.sugarlabs.org by default, there is also read-only public web server, http://network-testing.sugarlabs.org.<br />
* <strike>Setup translation.sugarlabs.org translation process.</strike> <span style="color: red">Moved to 0.4.</span><br />
* <strike>Handle server notifications about SN data changes in client application.</strike> <span style="color: red">Moved to 0.4.</span><br />
* <strike>Synchronization between SN nodes.</strike> <span style="color: red">Moved to 0.4.</span><br />
* <strike>Basic i18n support in SN content (excluding managing already entered strings).</strike><br />
* <strike>Basic routines for SN editors (including initial populating SN content):</strike> 0.3 will contain only trivial and ready use activities, the editors workflow implementation work will start from 0.4.<br />
* <strike>Since there are useful binary based activities (GC, TuxPaint), support upload such activities to SN. From developers point of view, the only they need to proceed is uploading sources bundle to SN, the rest (building sources for all supported platforms) should happen automatically.</strike> <span style="color: red">Moved to 0.4.</span><br />
* <strike>Revise most popular ASLO activities to add all needed meta information (like required dependencies) and mark the as stable and ready to run from Sugar Network.</strike> Thanks to [[User:Satellit|satellit]], testing server contains only activities that start without problems.<br />
* <strike>Worfklow to semi automatic collect fail reports using Report resource.</strike> Move to 0.25.<br />
* <strike>final XO image, for students and teachers (teachers server), that is ready for deploying.</strike> <span style="color: red">Moved to 0.4.</span><br />
<br />
=== 0.4 ===<br />
<br />
* <strike>Fix issue with creating new Journal entity on every launch from F8.</strike> <span style="color: red">Moved to 0.5.</span><br />
* <strike>Edit resources capability</strike><br />
* <strike>Delete comments capability</strike><br />
* <strike>Create context capability</strike><br />
* <strike>Distribute base software updates.</strike> <span style="color: red">Moved to 0.5.</span><br />
* <strike>Start gathering [[Platform_Team/Usage_Statistics|usage statistics]].</strike> <span style="color: red">Moved to 0.5.</span><br />
* <strike>Define/Document some useful usage indicators for SN interaction.</strike><br />
* <strike>Setup translation.sugarlabs.org translation process.</strike><br />
* <strike>Synchronization between SN nodes.</strike><br />
* <strike>Upload arbitrary documents as contexts to SN</strike> <span style="color: red">Moved to 0.5.</span> with <strike>segregation in webui</strike>.<br />
* <strike>Final XO image, for students and teachers (teachers server), that is ready for deploying to start testing in the field.</strike> Next [http://download.sugarlabs.org/hexokinase/Factory/ development] XO images and images targeting to Peru deployment [http://download.sugarlabs.org/hexokinase/].<br />
<br />
=== 0.5 ===<br />
<br />
* <strike>Journal integration:</strike> Journal is accessible as Artifact resource from {{Code|~}} mount point.<br />
** <strike>Fix an issue with creating new Journal entity on every launch from F8.</strike><span style="color: red">Moved to 0.6.</span><br />
** <strike>Upload arbitrary documents as contexts to SN.</strike><span style="color: red">Moved to 0.6.</span><br />
* <strike>Make it possible to show a top of recent comments for all currently represented resources in webui. That should help with fast observing the current discussion status.</strike><span style="color: red">Moved to 0.6.</span><br />
* <strike>Offline updates for base software updates.</strike><br />
* <strike>Start gathering [[Platform_Team/Usage_Statistics|usage statistics]].</strike><br />
* <strike>[[Wiki:Create,_read,_update_and_delete|CRUD]] workflow for SN content.</strike><span style="color: red">Moved to 0.6.</span><br />
* <strike>Basic routines for SN editors (including initial populating SN content):<br />
** let all people, not only editors, expose the fact that particular activity [doesn't]works in theirs environment (maybe just by exposing how many fail Reports exist for the Implementation, Report might have the level of failure: doesn't do basic work, doesn't do optional work but basic features work fine).</strike><span style="color: red">Moved to 0.6.</span><br />
<br />
=== 0.6 ===<br />
<br />
* <strike>Reliable way to start Sugar Activities that have additional dependencies.</strike> <span style="color: red">Moved to 0.7.</span><br />
* <strike>Fix an issue with creating new Journal entity on every launch from F8.</strike> <span style="color: red">Moved to 0.7.</span><br />
* <strike>Upload arbitrary documents as contexts to SN.</strike> <span style="color: red">Moved to 0.7.</span><br />
* <strike>Make it possible to show a top of recent comments for all currently represented resources in webui. That should help with fast observing the current discussion status.</strike> <span style="color: red">Moved to 0.7.</span><br />
* Initial implementation of Contributor Hub.<br />
* Synchronize testing server with ASLO.<br />
<br />
=== 0.7 ===<br />
<br />
Server side:<br />
<br />
* <strike>Server side stats.</strike><br />
<br />
Client side:<br />
<br />
* <strike>Support server side stats.</strike> No need.<br />
* <strike>Process package dependencies in order to provide reliable start of Sugar Activities.</strike><br />
* <strike>Resume Sugar Network non-activities content, e.g., Journal objects or .xol libraries.</strike><br />
* <strike>RO access to local Journal</strike>.<br />
<br />
WebUI:<br />
<br />
* Offline work and Syncronization functionality<br />
* Include notes regarding the licenses applicable for published content<br />
* Fix an issue with creating new Journal entity on every launch from F8.<br />
* ...<br />
<br />
Contributor Hub:<br />
<br />
* <strike>Upload content, e.g., .pdf files.</strike><br />
<br />
=== 0.8 ===<br />
<br />
Server and client side:<br />
<br />
<strike>* Offline usecase for Sugar Network nodes.</strike> Moved to 0.10+<br />
* Support ''Users' home page''.<br />
<br />
WebUI:<br />
<strike>* Subscriptions and Notifications.</strike> Moved to 0.10+<br />
<strike>* ''Users' home page''.</strike> Moved to 0.10+<br />
<br />
Contributor Hub:<br />
<br />
* Visualize server stats.<br />
<br />
=== 1.0 ===<br />
<br />
No new features, only polishing.<br />
<br />
Final release should have. Difficulties are from 0 (impossible) to 5 (trivial).<br />
<br />
'''General'''<br />
<br />
* Sugar Network content related features:<br />
** Uploading non-software content. Difficulty 5.<br />
** <strike>Uploading non-binary activities. Difficulty 3.</strike> Activities will come from regular ASLO sync.<br />
** Share Journal objects.<br />
<br />
* Statistics related features:<br />
** Server side stats, e.g., ''likes'' for resources. Difficulty 2.<br />
** <strike>Personal users' stats</strike> Implemented in [[Sugar_Server_Kit/sugar-client#Collecting_usage_statistics|sugar-client]].<br />
** Visualize stats.<br />
<br />
* ''Users' home page'' to keep them up-to-date:<br />
** Live updates in resources user is subscribed after becoming online. Difficulty 4.<br />
** Getting digest of changes happened in resources where logged user is an author. Difficulty 3.<br />
<br />
* Sugar Network editors workflow:<br />
** Multiple authors per Context to let several people change Context metadata (it is all time possible to create related objects by any user). Difficulty 4.<br />
** <strike>Contributor Hub should provide a UI to let deployment supported to select what content should be accessible for particular deployment. Difficulty 3.</strike><br />
** ..<br />
<br />
'''WebUI'''<br />
<br />
* Share Journal objects.<br />
* Users' ''home page'' to keep them up-to-date.<br />
* ...<br />
<br />
'''Contributor Hub'''<br />
<br />
* Upload content.<br />
* Stats visualization.<br />
<br />
=== Post 1.0 ===<br />
<br />
* Full support of offline deployments.<br />
* Full support for server-less use-case for users.<br />
* Support binary based activities.<br />
<br />
== Statistics to gather ==<br />
<br />
Statistic types:<br />
<br />
* ''network-server''<br>Stats will be collected on Sugar Network server and stored in [[wikipedia:Round-Robin_Database|round-robin]] storage for further analyzing;<br />
* ''client-sniffer''<br>Stats will be collected by special sniffer, e.g., [[Sugar_Server_Kit/sugar-client|sugar-client]], launched on client side to collect local stats, in [[wikipedia:Round-Robin_Database|round-robin]] database, with following transmitting to the Sugar Network server;<br />
* ''unknown''<br>Ambiguous stats criterion.<br />
<br />
===Interactions===<br />
<br />
*Contexts Searches (''network-server'').<br />
*Context [Activity Type] Launches (''client-sniffer'').<br />
*Context [Activity Type] Failure Reports (''network-server'').<br />
*Context [Project Type] Views (''unknown'').<br />
*Context [Project Type] Creation (''network-server'').<br />
*Context [Project Type] Editing (''network-server'').<br />
*Resource Creation/Editing/Commenting Review Type (''network-server'').<br />
*Resource Creation/Editing/Commenting/Solving Question Type (''network-server'').<br />
*Resource Creation/Editing/Commenting Idea Type (''network-server'').<br />
*Resource Creation/Editing/Commenting/Solving Problem Type (''network-server'').<br />
<br />
===Participants===<br />
<br />
*Total Users: Total number of participants at any time (counting since network launching) (''network-server'').<br />
*Period New Users: Simple summation of the number of new participants over the course of a specified time period (''network-server'').<br />
*Period Active Users: Simple summation of the number of participants that registered at least one effective interaction on the network over the course of a specified time period (''network-server'').<br />
*Period Unique Visitors: The number of unduplicated (counted only once) visitors to the network over the course of a specified time period (visitors may or may not make effective interactions) (''network-server'').<br />
*Top/Ranking Users: [how to rank participation?] [total / by period?] [also, sort by Location or Conexion type?] (''unknown'')<br />
<br />
===Usage===<br />
<br />
*Total Visits: Total number of visits to the network at any time (counting since network launching). (''network-server'')<br />
*Period Visits: Total number of visits to the network over the course of a specified time period. (''network-server'')<br />
*Period Effective Visits: Simple summation of the number of visits that registered at least one effective interaction on the network over the course of a specified time period. (''network-server'')<br />
*Period Interactions Per Visit: Average number of effective interactions per visit on the network over the course of a specified time period. (''network-server'')<br />
<br />
===Content===<br />
<br />
*Total Contexts [Activity type]: simple summation of contexts of Activity type at any time (counting since network launching). (''network-server'')<br />
*Period New Contexts [Activity type]: simple summation of the total number of created contexts of Activity type over the course of a specified time period. (''network-server'')<br />
*Period Active Contexts [Activity type]: simple summation of the total number of contexts of Activity type that registered at least one effective interaction over the course of a specified time period. (''network-server'')<br />
*Total Contexts [Project type]: simple summation of contexts of Proejct type at any time (counting since network launching). (''network-server'')<br />
*Period New Contexts [Project type]: simple summation of the total number of created contexts of Project type over the course of a specified time period. (''network-server'')<br />
*Period Active Contexts [Project type]: simple summation of the total number of contexts of Project type that registered at least one effective interaction over the course of a specified time period. (''network-server'')<br />
*Period Context Ranking [100?] of Contexts by type: most interacted Contexts over the course of a specified time period. (''unknown'')<br />
<br />
== Inventory of technical issues outside Client and Server ==<br />
<br />
* How will students register with a teacher<br />
* How will teachers turn their laptop into servers<br />
* What are the constraints of the syncronization mechanism<br />
* Patch to Journal for sharing in SN<br />
<br />
== Questions for educators/experts ==<br />
<br />
* What kind of users' statistics will be useful for educators/researchers?<br>See the current [[Platform_Team/Usage_Statistics|implementation]] of Australian [https://dev.laptop.org.au/issues/59 request]. The collected data are being stored in [[Wikipedia:Round-Robin_Database|RRD]] format and might be represented in [http://oss.oetiker.ch/rrdtool/gallery/index.en.html graphics].<br />
* Should students, teachers be clearly separated in the GUI?<br />
* Should teachers track what their students do within the Network?<br />
* Should the students track what they do within the Network?<br />
* Should teachers moderate what their students do within the Network?<br />
<br />
* What kind of users' statistics will be useful for teachers and learners?</div>Icaritohttps://wiki.sugarlabs.org/index.php?title=Summer_of_Code/2014/AnaBalica/Social_Help&diff=92210Summer of Code/2014/AnaBalica/Social Help2014-03-24T03:42:39Z<p>Icarito: /* You and the community */</p>
<hr />
<div>===About me===<br />
<br />
*''What is your name?''<br />
:Ana Balica<br />
*''What is your email address?''<br />
:ana.balica@gmail.com<br />
*''What is your Sugar Labs wiki username?''<br />
:AnaBalica<br />
*''What is your IRC nickname on irc.freenode.net?''<br />
:ananasova<br />
*''What is your first language? (We have mentors who speak multiple languages and can match you with one of them if you'd prefer.)''<br />
:I know 3 languages: Romanian, Russian and English.<br />
*''Where are you located, and what hours (UTC) do you tend to work? (We also try to match mentors by general time zone if possible.)''<br />
:Originally I am from Republic of Moldova. My current location (also during the summer) is Prague, Czech Republic (UTC +1). Normal working day starts at 8AM UTC and ends at 7PM UTC. <br />
* Have you participated in an open-source project before? If so, please send us URLs to your profile pages for those projects, or some other demonstration of the work that you have done in open-source. If not, why do you want to work on an open-source project this summer?<br />
:Open-source contributions:<br />
:* moin2.0 - [https://bitbucket.org/ana-balica/moin-2.0/commits/all?search=author(ana) change subscription mechanism and other enhancements]<br />
:* sugar bugfix - [https://github.com/sugarlabs/sugar/commit/88da6648c3db750691897535f36104789f8b879c Fix #4733 - remove warning on username change] and [https://github.com/sugarlabs/sugar/commit/89664a09ce64f005112d1e54662b32ffeb4d64b8 Manage restart message on reverting to initial username]<br />
<br />
===About the project===<br />
<br />
*''What is the name of your project?''<br />
:Social Help<br />
*''Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?''<br />
====Abstract====<br />
:Social Help is a system wide mechanism to access a range of social channels like IRC, forums or social networks (i.e. Sugar Network) within a specific context. Basic implementation is available on [https://github.com/ana-balica/sugar/tree/prototype-social-help github branch prototype-social-help] and the interaction workflow is screencasted and posted on [https://www.youtube.com/watch?v=x316a6JX84Q youtube]. The prototype includes a system-wide handling of a keypress combination - <Shift><Alt><c>, which pops up a window that has 2 options: to join IRC or to open the Browse activity. At the moment the following window looks like that:<br />
<br />
<gallery mode=packed heights=200px><br />
File:screenshot_sugar1.png|Social Help window within Read Activity<br />
File:screenshot_sugar2.png|Social Sugar window within TurtleArt activity<br />
</gallery><br />
<br />
<br />
:Here is a simple UI design of the window (made in Inkscape). The Discourse button is merely an example (in case the community decides on using a different forum platform).<br />
<br />
<gallery mode=packed heights=200px><br />
File:Social_help_window.png|Social Help window design<br />
</gallery><br />
<br />
:'''Update:''' This is just a prototype and there is a better idea how to handle Social Help window (from Sam Parkinson). We can add one extra icon to the static Help dialog, which will display the Social Help interface. In that way we are not overloading the user operation with extra shortcuts and we make it more discoverable, due to the fact that users are already used to static Help window.<br />
<br />
====Functional requirements====<br />
{| class="wikitable"<br />
|-<br />
! Nr !! Description !! Priority !! Time to implement !! Comments<br />
|-<br />
| 1 || On a specific keypress bring up a window with a list of available social channels for the specific context || Major || 4 days || <br />
|-<br />
| 2 || Create a toolbar button in the sugar toolkit with a palette that contains all available social channels for the following activity || Major || 4 days || The priority is set to major, since a visual component to access Social Help is more intuitive and simple to find.<br />
|-<br />
| 3 || Include Social Help toolbar button to the main activities included in the standard distribution || Major || 1 day || If the button won't be made available from the UI, the whole reason to have it disappears.<br />
|-<br />
| 4 || On clicking the IRC button, IRC activity should be opened with the name of the user set from system settings and the respective channel joined. || Major || 3 days || In my opinion an IRC channel option should be present along with the forum possibility, because it is the fastest and most straight-forward way to get a quick answer to a short, well-formed question (nevertheless it contains its drawbacks, which are surely covered by forum style help). I am also wondering if there is going to exist a single or multiple help channels.<br />
|-<br />
| 5 || Display an error message in case the user has chosen to ask for help via IRC activity and the following activity is not installed. Propose to open the browser to the download page of the IRC activity. || Medium || 2 days ||<br />
|-<br />
| 6 || On clicking the forum button, resume the Browse activity and open an extra tab that links to the forum address. || Major || 3 days ||<br />
|-<br />
| 7 || Create an automatic way of registration/authentication to afford users to post questions on the forum/network as quick as possible. The registration and authentication progress is dependent on the platform to be chosen. || Medium || 2 weeks || It is quite important to create a flawless workflow to the user, it is especially important in case it is going to be a one time access. If a user will visit the forum/network more than once, than the browser clearly keeps the session data and allow instant access to posting.<br />
|-<br />
| 8 || Localize all the components of Social Help || Major || 2 days ||<br />
|-<br />
| 9 || Create the Code of Conduct for Social Help channels || Minor || 3 days ||<br />
|}<br />
<br />
====Comparison between Discourse and Sugar Network====<br />
{| class="wikitable"<br />
|-<br />
! Criteria !! Discourse !! Sugar Network<br />
|-<br />
| Showcase/Example || http://try.discourse.org/ || http://network.sugarlabs.org/<br />
|-<br />
| UI and UX || Has a clean, modern UI, contains categories, information about posts, likes, latest activity, suggested topics. It is mobile-friendly. Since it is a general purpose discussion software, it has a decent universal-like design. Discourse is skinnable and themable, therefore can be easily adapted to Sugar needs. || Follows the Sugar style guidelines, is [[Platform_Team/Sugar_Network#Clients|oriented towards low aged students]]. Hence represents a well-known and intuitive tool for users. Contains a grid of activities with sections divided into questions, ideas, problems, reviews, all resources and artifact gallery. Moreover has lists of resources and artifacts.<br />
|-<br />
| Current status || [http://www.discourse.org/faq/#switch Late beta], approaching version 1.0 || [[Sugar_Network/1.0/Roadmap|Version 1.0]]<br />
|-<br />
| Registration and authentication || Provides access to stand alone registration or using available services (Google, Github, Facebook and others). Respectively authentication is done using forum credentials or external credentials. || Sugar Network has an RESTful [[Platform_Team/Sugar_Network/API|API]] and a client side application on top of it, which allows [[Platform_Team/Sugar_Network/API#Authentication|authentication and authorization]]. ''At the moment I can find any relevant information regarding the registration process. Is it already integrated with Sugar Environment via users GUID?''<br />
|-<br />
| Usability || It is a discussion software, intuitive and easy to use (sounds like a subjective option, nevertheless it is also based on the community voice and the project scope as a whole). Provides a user profile with some data about the user and his activity on the forum. || Sugar Network is a content sharing and social activity system for Sugar Learning Environment, which represents a central point for collaboration between [[Sugar_Network/Concept#Targeted_audience|students, educators, software developers]]. It offers a social network to [[Sugar_Network/Declaration_of_purpose|ask questions, propose ideas, complain about problems and express ideas]]. It provides access not only to Internet users, but also to primary and secondary educational institutions including those without Internet connection.<br />
|}<br />
<br />
====Conclusion====<br />
:Social Help is oriented towards users of Sugar (kids) that for various reasons are in need of social interaction:<br />
:* ask a question on how to achieve something within Sugar or an activity<br />
:* share knowledge and experience<br />
:* propose enhancements<br />
:* debug possible problems<br />
<br />
:To think about it, today's society is overwhelmed with social networks, forums and chats. Social Help is an easy way to access social channels and get children involved into helping each other. The interaction can give them a headstart in understanding how to use the tools they are offered and even contribute to the project. <br />
*''What is the timeline for development of your project? The Summer of Code work period is from May 19 - August 22; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (27 June); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.''<br />
:Timeline:<br />
:* 19-25 May - Decide on and code the final UI design of the Social Help window<br />
:* 26-1 June - Bring on a context-dependent window on a specific keypress to show all available communication channels for the following context and attach callbacks to UI widgets<br />
:* 2-8 June - Create a toolbar button for social help with a palette listing all available channels for the current context, integrate the toolbar button to main activities<br />
:* 9-15 June - On IRC channel button press event open IRC activity, set the nickname based on system user and join the help channel<br />
:* 16-29 June - Set up a forum platform or familiarize with the existing one, create a seamless registration and authentication process for Sugar users<br />
:* 30-6 July - On Forum(s) button press event open the respective activity or the Browse activity and point to the context-dependent category to post the question<br />
:* 7-13 July - Create error message popup windows and offer to download missing components (i.e. IRC activity)<br />
:* 14-20 July - Write unit and integration tests for the available functionality<br />
:* 21-27 July - Extensive manual testing, bugfixing, localization<br />
:* 28-3 August - Write documentation (docstrings, a wiki page with description, help page to Help activity maybe)<br />
:* 4-10 August - Extra polishing (small enhancements)<br />
:* 11-17 August - Merging to main repos, submitting code to melange<br />
*''Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.''<br />
:My exposure to computer science and information technologies began 4 years ago. In that period I have achieved a reasonably solid expertise in clean coding, usage of procedural and OOP paradigms (just the basics of functional), scratched the surface of software design and design patters. My main passion is Python (actively developing using Python for the last 3 years), though I have tried also other tools (JavaScript, PHP, Matlab/Octave, git, a variety of web frameworks, technologies, libraries). <br />
<br />
:Some of my pet projects are:<br />
:* FAF website (Django), [https://github.com/TUM-FAF/FAFSite github repo], currently hosted here http://faf.utm.md/ (the university website might be down) and migrating to http://faf.code.md/<br />
:* My blog written in Flask, [https://github.com/ana-balica/codee_blog Code Speculations], available here http://www.code-speculations.me/<br />
<br />
:My github contains a variety of small university projects: a poll website written in Symfony2, Scrapy spiders, Qt4 apps, semantic web and linked data showcase app, SVG based editing tool.<br />
<br />
:Additionally I was employed as software developer for 8 months at [http://www.red-sky.com/ Red Sky] (had to quit due to change of geolocation). I have worked on [http://www.carocean.co.uk/ CarOcean] project, which is based on Scrapy framework. My responsibility was to handle about 100 different spiders (the project is available in 9 countries). Consequently I got a lot of experience in crawling the web, using xpath, regular expressions, agile methodology. As well I have worked on small PHP (Zend framework) projects.<br />
<br />
===You and the community===<br />
*''If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.''<br />
:'''My thoughts'''<br />
:Social Help doesn't have a striking, absolutely vital impact on Sugar Labs community. Nevertheless this small feature will open the borders of communication for so many users on some many topics. Social Help shows a straight-forward way where to ask a question or to share your knowledge. By completing this project, Sugar Labs community will get even closer to its users through IRC and forums, which subsequently leads to a better understanding of what it's users are expecting. <br />
:Moreover Sugar Help will become a channel to find pals all over the world with same interests via reciprocal help. <br />
<br />
In the mid-1970s Alan Kay predicted that, among other things, computers would enhance interpersonal communication. While there remain a few skeptics, it is pretty obvious he was spot on in his prediction. People are inherently social beings and the computer gives us opportunity to exercise that aspect of our nature. Amplifying the social aspects of Sugar for our users is a great way to share best practice, provide support, and mostly have fun while learning. Social Sugar is critical to our future as a community and as a project. --[[User:Walter|Walter]] ([[User talk:Walter|talk]]) 18:23, 19 March 2014 (EDT)<br />
<br />
Users require a way to provide feedback to the developers so that the platform has a chance to improve. Social Help will enable users to share their issues and help build a good knowledge base for the Sugar doers community. --[[User:Icarito|icarito]] ([[User talk:Icarito|talk]]) 23:42, 23 March 2014 (EDT)<br />
<br />
*''What will you do if you get stuck on your project and your mentor isn't around?''<br />
:Research or refocus. Those are the 2 strategies that always work for me. If it is a bug, then there must be a way to solve it. Get a step back and read some documentation - maybe I have missed something important. If the issue involves a collaborative decision and the presence of the mentor is absolutely critical, then I can refocus, checkout to a new topic branch and start doing other tasks. <br />
*''How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?''<br />
:Talking from my past experience, weekly meeting are really helpful to keep everybody up-to-date (might be held only with the mentors and co-mentors). Usually I prepare lists of DONE, TODO next week and BLOCKERS. Also I am always online on IRC (using irssi via ssh) and I check it several times a day.<br />
<br />
===Miscellaneous===<br />
*''We want to make sure that you can set up a [http://developer.sugarlabs.org development environment] before the summer starts. Please do ''one'' of the following:''<br />
**''Send us a link to a screenshot of your Sugar development environment with the following modification: when you hover over the XO-person icon in the middle of Home view, the drop-down text should have your email in place of "logout".''<br />
**''Send us a link to a pull request or merge request you have made on a Sugar or Sugar activity bug.''<br />
:Sugar commits:<br />
:* [https://github.com/sugarlabs/sugar/commit/88da6648c3db750691897535f36104789f8b879c Fix #4733 - remove warning on username change ]<br />
:*[https://github.com/sugarlabs/sugar/commit/89664a09ce64f005112d1e54662b32ffeb4d64b8 Manage restart message on reverting to initial username]<br />
* Describe a great learning experience you had as a child.<br />
:In childhood I used to do all sorts of trivial experiments related to physics and biology. I was blocking the sunlight from for some plants, managing their watering cycle, filling up washbowls with different temperature water to test how same water temperature is relative to previous heat exposure of some parts of the body, trying to understand how animal communities work and how they communicate.<br />
[[Category:2014 GSoC applications]]</div>Icaritohttps://wiki.sugarlabs.org/index.php?title=Deployment_Team/Contacts&diff=69450Deployment Team/Contacts2011-09-23T02:17:18Z<p>Icarito: </p>
<hr />
<div><noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}{{TeamHeader|Deployment Team}} </noinclude><br />
{{TOCright}}<br />
== Coordinator ==<br />
{{:Deployment Team/Coordinator}}<br />
<br />
=== Mail list ===<br />
<br />
We use the "It's an education project" list <iaep AT sugarlabs.org>.<br />
<br />
=== IRC channel===<br />
<br />
We hold biweekly meetings on Wednesdays at 14:00 UTC on irc.freenode.net #sugar-meeting<br />
<br />
===The team===<br />
Please feel free to add yourself to the list.<br />
* [[User:RafaelOrtiz | Rafael Ortiz]]<br />
* [[User:Befana | Pilar Saenz]]<br />
* [[User:Monyu | Gloria Meneses]]<br />
* [[User:Walter | Walter Bender]]<br />
* [[User:Dfarning | David Farning]]<br />
* [[User:Sebastian| Sebastian Silva]]<br />
* [[User:drneals | Neal Scogin]]<br />
* [[User:CarolineM | Caroline Meeks]] - Focusing on Sugar on a Stick (LiveUSB) based deployments<br />
* [[User:alsroot | Aleksey Lim]]<br />
* [http://somosazucar.org/ Laura Vargas]<br />
* &nbsp;<br />
<br />
<br />
[[Category:Deployment]]<br />
[[Category:Contact]]</div>Icaritohttps://wiki.sugarlabs.org/index.php?title=Activity_Team/TODO&diff=63471Activity Team/TODO2011-03-10T18:00:43Z<p>Icarito: /* Activity Feature Requests */</p>
<hr />
<div><noinclude>{{GoogleTrans-en}}{{TeamHeader|Activity Team}}<br />
[[Category:Activity Team]]<br />
[[Category:TODO]]<br />
</noinclude><br />
{{TOCright}}<br />
When you plan to take a task from the list, please sign and date it using four tildes.<br />
<pre>* task name &tilde;&tilde;&tilde;&tilde;</pre><br />
<br />
When a task is complete, strike it out.<br />
<pre>&lt;strike&gt;task name&lt;/strike&gt;</pre><br />
<br />
==Community Tasks==<br />
* <strike>Announce availability of ATeam contacts page to mailing lists. [[User:Wade|Wade]] 17:26, 12 January 2009 (UTC)</strike><br />
* Query ATeam members about skills, interest, time commitment. [[User:Wade|Wade]] 17:26, 12 January 2009 (UTC)<br />
* <strike>Look for at least one additional coordinator.</strike> [[User:garycmartin|garycmartin]] now a co-co-ordinator.<br />
* Contact former + current activity developers. [[User:Wade|Wade]] 17:26, 12 January 2009 (UTC) <br />
** Ask about moving activities to git.sugarlabs.org (or mirroring). [[User:Garycmartin|Garycmartin]] 22:00, 25 May 2009 (UTC) still in progress<br />
** Ask about joining the Activity Team or coming to meetings.<br />
* Write guides for Activity Authors. Pages should be located at Activity Team/Guides/Name. Don't forget to add links to [[Activity Team/Resources]].<br />
** Gitorious tutorial. Overview of SSH key setup. How to create projects, make clones, request and accept merges. Solutions to common problems.<br />
** Localization tutorial. Intro to Python features, how to set up Pootle, deal with things like localizing images.<br />
** Posting tutorial. Take the migrating from OLPC document and produce a guide to posting newly developed activities.<br />
** Documentation tutorial. Guidelines for activity documentation, and perhaps instructions on how to create a FLOSS manual about your activity.<br />
** Integrate IMAGE from [[User:Cjl/Sandbox]] and add C (collaboration) and V (view source) and maybe a J (journal) or R (reflection) (CoVeR IMAGE)?<br />
** a.sl.o needs a "reading" or "literacy" or "words" category.<br />
*** actually a.sl.o needs its categories reworked, could well turn into formal activity tags within the Sugar UI if we get it right [[User:Garycmartin|Garycmartin]] 22:00, 25 May 2009 (UTC)<br />
<br />
==High Impact Tasks==<br />
These are tasks which will have a big impact on Sugar deployments. This is your chance to affect thousands of children in the developing world! This section will be updated frequently to feature the most urgent work the Activity Team has to do.<br />
<br />
====SWF activity launcher====<br />
<strike>The Nepal deployment have created a suite of Flash based learning activities but are currently having to jump through many hoops to package them correctly. We would like to have a launcher which creates an activity window and launches Gnash in it, with a .SWF file. This launcher would then be used to easily make activity bundles out of SWF files. '''Nepal is freezing their deployment image in mid-Feburary and extensively uses Flash based activities. We could really use some movement on this task.'''</strike><br />
<br />
:Not directly related to Nepal deployment (I think), but Tomeu has been working on a gnash gtk widget called [http://git.sugarlabs.org/projects/swf-edit SWFEdit], there is some more information on his [http://blog.tomeuvizoso.net/2009/04/embed-flash-movies-with-gnash-in-your.html blog]. I'll try to put up some demo activities and drum up some interest once I've had time to play! [[User:Garycmartin|Garycmartin]] 03:20, 26 May 2009 (UTC)<br />
<br />
====Web activity launcher & framework====<br />
<strike>Other deployments are using HTML+CSS+Javascript to make learning activities, but they currently have to be installed using the Library Collection feature of Sugar which is not well developed. We would like to build a 'web-activity' launcher script which allows Web based activities to be first class activities with icons on the home screens. This would involve making a new framework out of the source code to the Browse activity and submitting it upstream to the Development Team, in addition to writing the launcher script.</strike><br />
:In progress. See [[Karma]].<br />
<br />
====Maze collaboration====<br />
Maze is currently the most addictive multiplayer game on the XO, and it needs a further dusting of crack, including better statistics, handicaps, etc.<br />
<br />
====Quiz software====<br />
One of the top activity requests from deployments is a general purpose, collaborative [[Activities/Quiz|Quiz activity]]. It should support creation of quizzes by teachers. It should support image, sound and text content, in the form of multiple choice, fill in the blank, true/false, etc. It should allow multiple students to take a quiz simultaneously by joining the activity. '''This project has been taken up by Tony Anderson. He hopes to have an initial version done by Feb 22'''.<br />
:I am still working on this - May 10 is current target date. Tony<br />
<br />
====Speak collaboration====<br />
<strike>This has the potential to be an awesome communication method; not only a chat option for the blind but a way of teaching specific words, and a fun way to engage small clusters of people around an XO: sound carries well to people who aren't currently reading the screen.</strike> [[User:Alsroot|alsroot]] 13:19, 1 February 2009 (UTC)<br />
<br />
====Document Process to Add instruments to TamTam====<br />
<strike>Most deployments would love to add their native instruments to TamTam but have no idea how to get started. Documentation on how to do this is lacking in the TamTam wiki. If it is very technically challenging to add new instruments to TamTam, it would be great if someone from the Activity Team would volunteer to assist deployments in adding new instruments.</strike> see [[Activity_Team/Modifing_an_Activity#Modifying_TamTam|Modifying TamTam]]<br />
<br />
====Sugarize Scratch====<br />
Scratch has a huge following. If Sugar was the best or easiest way to use Scratch it would help our adoption. First step is getting it working on the latest version an put it up on the activity portal. Next is saving to the Journal and collaboration.<br />
<br />
==Infrastructure Tasks==<br />
* <strike>Make activities.sugarlabs.org (or activities.sugarlabs.org) work.</strike> See [[Activity Team/Remora_port]].<br />
* Move projects owned by ATeam members over to git.sugarlabs.org and downloads.sugarlabs.org<br />
*: See [[Activity Team/How_to_migrate_from_OLPC]] for activity migration instructions.<br />
*: See [[Activity Team/Activity Status]] for a list of projects that need to be moved.<br />
* <strike>Bug IT to get us admin accounts for SL services.</strike> <br />
** <strike>Downloads.</strike> [[User:Wade|Wade]] 21:10, 10 February 2009 (UTC) activities.sugarlabs.org will fill this need, for now we have to request individual accounts.<br />
** <strike>Trac (component creation)</strike> 21:10, 10 February 2009 (UTC) can create new components now.<br />
* <strike>Ask IT about activity repository mirroring. A read-only Git repository on SL which automatically pulls from a remote repository.</strike> We'll just ask authors to push a copy to Gitorious.<br />
* <strike>Flesh out structure for Activity Team wiki.[[User:Wade|Wade]] 01:34, 14 January 2009 (UTC)</strike><br />
* <strike>Create Activity Team wiki structure page indicating where content is supposed to go.</strike> Wiki is doing pretty well now.<br />
* <strike>Bug IT to add helpful "git-clone" hints like on: http://dev.laptop.org/git?p=activities/help;a=summary and/or instructions for developing within sugar like: (snipped) I moved this snippet to the Get Involved page, and Gitorious does offer push / clone urls. [[User:Wade|Wade]] 01:34, 14 January 2009 (UTC)</strike><br />
<br />
==Development Tasks==<br />
* Help SoaS and other distro packagers to get as many activities as possible working on plain Sugar (outside the XO software environment).<br />
*: See [[Activity Team/Activity Status]] for a list of projects that need to ported and/or tested.<br />
* Clean up activities. Bring .POT files up to date, check MANIFEST is correct, publish latest version to downloads.sugarlabs.org.<br />
*: See [[Activity Team/Activity Status]] for a list of projects that need to cleaned up.<br />
* Build a list of "Rescue" activities: Ones which have not been worked on in a while but are close to being usable.<br />
* Build a list of "Help Wanted" activities: Great ideas or existing projects which need to be sugarized.<br />
* Generate spec for Web, SWF activities and deliver to Development Team.<br />
<br />
==Activity Feature Requests==<br />
This section is for feature requests for specific activities. As requests, there can be no guarantee as to the order in which we will process them, but we will do our best. <br />
<br />
If you are a new activity developer, there are many small tasks here which would be a great way to get introduced to the project.<br />
<br />
==Adding new Toolbars==<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
! Activity !! Git repo with patches !! Comment<br />
|-<br />
| Typing Turtle || git://git.sugarlabs.org/~icarito/typing-turtle/typing-turtle-icarito.git || DONE. Waiting for merge request.<br />
|-<br />
| StopWatch || git://git.sugarlabs.org/stopwatch/stopwatch.git || DONE. Moved Share and Keep buttons to main toolbar.<br />
|-<br />
| Help || git://git.sugarlabs.org/~icarito/help/help-newui.git || DONE. Put navigation in main bar (like in Browse).<br />
|-<br />
| Distance || git://git.sugarlabs.org/distance/distance.git || DONE by dirakx. <br />
|-<br />
| Maze || git://git.sugarlabs.org/~icarito/maze/icaritos-mainline.git || DONE. Moved Share to main bar.<br />
|-<br />
| Get Books || git://git.sugarlabs.org/~icarito/get-books/icaritos-mainline.git || DONE. Moved book actions to main toolbar.<br />
|-<br />
| Words || - || Working on it [[User:Icarito|icarito]] 13:00, 10 March 2011 (EST). The UI can be improved.<br />
|-<br />
| Jukebox || - || Working on it [[User:Icarito|icarito]] 13:00, 10 March 2011 (EST). <br />
|}<br />
<br />
<br />
===[[Activities/Turtle Art#Portfolios|Turtle Art]]===<br />
* <strike>Move the show/hide blocks, erase, and stop buttons to the toolbar</strike><br />
* <strike>Add run and step buttons to the same toolbar</strike><br />
* <strike>Reconfigure audio initialization so that it only happens when TA starts up or gets sent to the background</strike><br />
* Don't let bricks get lost off the screen<br />
* <strike>Add a special stack "hat" for "main" (tied to the run button above)</strike><br />
* <strike>Merge with TA with sensors.</strike><br />
See the addition to-do items [[Activities/Turtle Art#Know_bugs_and_areas_in_need_of_improvement|here]]</div>Icaritohttps://wiki.sugarlabs.org/index.php?title=Activity_Team/Contacts&diff=63358Activity Team/Contacts2011-03-09T04:20:39Z<p>Icarito: /* Contributors */</p>
<hr />
<div><noinclude>{{GoogleTrans-en}}{{TeamHeader|Activity Team}}{{TOCright}}</noinclude><br />
<br />
==Coordinators==<br />
{{:Activity Team/Coordinator}}<br />
<br />
==Contributors==<br />
* [[User:alsroot|Aleksey Lim]]<br />
* [[User:nrp|Nirav Patel]]<br />
* [[User:bjordan|Brian Jordan]]<br />
* [[User:ysun|Yifan Sun]]<br />
* [[User:Prakhar|Prakhar Agarwal]]<br />
* [[User:Arjs|Arjun Sarwal]]<br />
* [[User:Tziegmann|Tom Ziegmann]]<br />
* [[User:Assim|Assim Deodia]]<br />
* [[User:Elzapp|Bård Aase]]<br />
* [[User:Marten|Marten Vijn]]<br />
* [[User:Babarehner|Mike Rehner]]<br />
* [[User:Icarito|Sebastian Silva]]<br />
<br />
When adding yourself to the list, please take a minute and decide how you will contribute to the effort. Then, head over to [[Activity Team/TODO]] put your name down next to something, or add a new item if you like. '''Welcome to the team!'''<br />
<br />
==Sugar Mail List==<br />
The Sugar developer [http://lists.sugarlabs.org/listinfo/sugar-devel mail list] has a friendly and active community of Activity and Sugar developers.<br />
<br />
==IRC Channel==<br />
Activity developers hang out on irc.freenode.net, in the #sugar channel. If you have Sugar installed, you can use the [http://activities.sugarlabs.org/en-US/sugar/addon/4029 IRC] Activity, just type /join #sugar<br />
<br />
To ask newbie questions about activity, or sugar core, development process, join [http://en.wikipedia.org/wiki/IRC IRC] channel [irc://chat.freenode.org/sugar-newbies #sugar-newbies] (e.g. via [http://webchat.freenode.net/?randomnick=1&prompt=1&channels=sugar-newbies web client]). Also browse chat [http://meeting.sugarlabs.org/sugar-newbies logs].<br />
<br />
[[Category:Activity Team]]<br />
[[Category:Contact]]</div>Icaritohttps://wiki.sugarlabs.org/index.php?title=User:Icarito&diff=63264User:Icarito2011-03-08T18:27:45Z<p>Icarito: </p>
<hr />
<div>See http://wiki.sugarlabs.org/go/User:Sebastian<br />
<br />
'''Public SSH Key'''<br />
<br />
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAw1mkkuu5q1EdYijHjTo23XGltCDtGLeB3Y1j5TezTYc3e9J5Ks31a9ZZvHdVY2RqR0MJT6Zi1RK5qEkx3VH6fS3u8a3CT08Ch+zafyA51E3f3XMBmq3AHm+RDQDJ+r6YVG28wGVGROz5+j/DSK4OyE8HJsePC6McBUqVhz8yufHY4yBUUDJ+9CypePN1tmq5ZOEiWtWgK/EJmj5EK8/6XF0VuWDh+nLBDfyMo3IB40M6lOG73kRfz5gT09sPVLgG/2sHE9d6xJCktDq0nRwdr7HfiaatJYSclbpka9kc1YP66tfnMZvWMV5s1f6Ga8IYBrAnWVu6vWMVzrUVfIEpUw== sebastian@sugarlabs.org</div>Icaritohttps://wiki.sugarlabs.org/index.php?title=User:Icarito&diff=62630User:Icarito2011-03-01T05:20:11Z<p>Icarito: Created page with "See http://wiki.sugarlabs.org/go/User:Sebastian"</p>
<hr />
<div>See http://wiki.sugarlabs.org/go/User:Sebastian</div>Icarito