https://wiki.sugarlabs.org/api.php?action=feedcontributions&feedformat=atom&user=EbenSugar Labs - User contributions [en]2026-06-13T09:12:30ZUser contributionsMediaWiki 1.43.0https://wiki.sugarlabs.org/index.php?title=Design_Team/Proposals/Groups&diff=34207Design Team/Proposals/Groups2009-07-27T00:55:11Z<p>Eben: </p>
<hr />
<div><noinclude>{{TOCright}}<!-- START OF BLOCK -- 1. COPY & PASTE this BLOCK to below the END OF BLOCK line.<br />
2. PASTE it before any pre-existing proposal,<br />
3. then OVERWRITE the place holders with your information,<br />
4. and DELETE the START & END OF BLOCK instruction lines.<br />
5. Click [Show preview] to check formatting, and adjust as necessary.<br />
6. Click [Save page] to complete the edit.<br />
<br />
</noinclude><br />
<!-- Pre-existing Proposal Block --><br />
<br />
=== Group mock-ups ===<br />
<br />
TODO:<br />
* Get agreement on any of this :-)<br />
<br />
==== Add buddy to existing Group from Neighbourhood ====<br />
<br />
[[Image:group_mockup_gary_neighbourhood_buddy_paletter.png|thumb|centre|640px|Buddy palettes would show self tags (tags the buddy added to their own profile) and a new "Add to Group -->" menu showing any groups the user had already created (managing these groups is performed in the Group view). Friends can be considered as a default group provided by the system that you can't delete.]]<br />
<br />
==== Group view with additional management ====<br />
<br />
[[Image:group_mockup_gary_group_buddy_palette.png|thumb|centre|640px|Note combination box for creating new and selecting existing Groups is currently set to "Colleagues". All buddy icons shown are for buddies already added to the "Colleagues" group. Hovering over a buddy reveals a palette that allows you to remove a buddy from this group.]]<br />
<br />
==== Group view with additional management ====<br />
<br />
[[Image:group_mockup_gary_group_combo_box.png|thumb|centre|640px|Clicking the combination box reveals the other Groups already defined, including the default "Friends" group provided by the system. Selecting an entry updates the buddy icons shown on the main canvas for that Group. Clicking the erase (-) toolbar button would raise an alert "Confirm erase: Are you sure you want to permanently erase the '<group_name>' group? (Keep/Erase)". Typing a new string into the combination box would activate the add group (+) toolbar button and disable the (-) button. Typing a new name then clicking (+) would create the group and clear the canvas of previously shown buddies (you'll see none here until you add them from neighborhood).]]<br />
<br />
==== Journal view showing "Send to --> Group" ====<br />
<br />
[[Image:group_mockup_gary_journal_send_to_group.png|thumb|centre|640px|Once we have named Groups, the Journal "Send to -->" feature can be extended at some future release cycle to support sending an entry to a whole group. Named Groups could also appear in the Activity "Share with:" menu for quick private collaboration with a number of buddies (each buddy in the Group would receive an Activity invite request).]]<br />
<br />
=== Former Design Sketches ===<br />
These images represent some earlier explorations of Groups, of both "open" and "closed" nature. For additional background on groups and their behaviors, please see [[Design Team/Specifications/Groups]]. If the above "local group" concept is implemented as a stepping stone to this model, we should be very clear in determining how that transition will happen. It's unclear to me how to illustrate the difference between the two, or how to convert local named groups to mutual open groups down the road. I do, however, see the open and closed groups specified here as more useful than local group names, since the benefits of group creation are enjoyed by all members.<br />
<br />
[[Image:Groups_1.jpg|thumb|centre|640px|The toolbar of the Groups zoom level has a group filter, in addition to the usual search field, as well as controls for creating or leaving groups. (I think Gary's use of (+) and (-) may be clearer than this design.)]]<br />
<br />
[[Image:Groups_2.jpg|thumb|centre|640px|The "Create group" button has a secondary option for creating a "closed" group. This feature is more likely to be used by teachers in an organized context, such as to define a class, so it is not as prominent in the UI.]]<br />
<br />
[[Image:Groups_3.jpg|thumb|centre|640px|The group creation process consists of providing a name, and selecting a number of individuals to invite to the group as it's created. Alternatively, we could simplify this process some if we only required a name, and then individually invite members using the process shown below.]]<br />
<br />
[[Image:Groups_4.jpg|thumb|centre|640px|Creating a closed group is nearly identical, however a set of instructors (who can manage the groups members and name) is also chosen.]]<br />
<br />
[[Image:Groups_5.jpg|thumb|centre|640px|Group invitations appear in the upper left corner of the screen. They appear in the colors of the inviter, and show the inviters name and the name of the group.]]<br />
<br />
[[Image:Groups_6.jpg|thumb|centre|640px|The groups one belongs to appear in the "Start with" and "Send to" menus, making sharing and collaborating with sets of friends easy and efficient. I like Gary's use of the group icon in the menus. In fact, we might assign "arbitrary" colors to groups based on their creator. The group icon we'd use in the UI (in the Journal list, menus, etc.) would be the three dots, with stroke and fill, rather than the circled white zoom level icon.]]<br />
<br />
<noinclude><br />
<br />
==Subpages==<br />
{{Special:PrefixIndex/{{PAGENAMEE}}/}}<br />
</noinclude></div>Ebenhttps://wiki.sugarlabs.org/index.php?title=File:Groups_6.jpg&diff=34206File:Groups 6.jpg2009-07-27T00:37:55Z<p>Eben: </p>
<hr />
<div></div>Ebenhttps://wiki.sugarlabs.org/index.php?title=File:Groups_5.jpg&diff=34205File:Groups 5.jpg2009-07-27T00:37:27Z<p>Eben: </p>
<hr />
<div></div>Ebenhttps://wiki.sugarlabs.org/index.php?title=File:Groups_4.jpg&diff=34204File:Groups 4.jpg2009-07-27T00:36:51Z<p>Eben: </p>
<hr />
<div></div>Ebenhttps://wiki.sugarlabs.org/index.php?title=File:Groups_3.jpg&diff=34203File:Groups 3.jpg2009-07-27T00:36:30Z<p>Eben: </p>
<hr />
<div></div>Ebenhttps://wiki.sugarlabs.org/index.php?title=File:Groups_3.5.jpg&diff=34202File:Groups 3.5.jpg2009-07-27T00:34:14Z<p>Eben: </p>
<hr />
<div></div>Ebenhttps://wiki.sugarlabs.org/index.php?title=File:Groups_2.5.jpg&diff=34201File:Groups 2.5.jpg2009-07-27T00:33:40Z<p>Eben: </p>
<hr />
<div></div>Ebenhttps://wiki.sugarlabs.org/index.php?title=File:Groups_2.jpg&diff=34200File:Groups 2.jpg2009-07-27T00:33:09Z<p>Eben: </p>
<hr />
<div></div>Ebenhttps://wiki.sugarlabs.org/index.php?title=File:Groups_1.jpg&diff=34199File:Groups 1.jpg2009-07-27T00:32:33Z<p>Eben: </p>
<hr />
<div></div>Ebenhttps://wiki.sugarlabs.org/index.php?title=Talk:Features/Terminal_Sharing&diff=34092Talk:Features/Terminal Sharing2009-07-25T02:04:59Z<p>Eben: Created page with 'This sounds quite fun and useful. Is there a reason this couldn't be integrated with the Terminal activity itself, with these features enabled when the activity is shared? -~~~~'</p>
<hr />
<div>This sounds quite fun and useful. Is there a reason this couldn't be integrated with the Terminal activity itself, with these features enabled when the activity is shared? -[[User:Eben|Eben]] 02:04, 25 July 2009 (UTC)</div>Ebenhttps://wiki.sugarlabs.org/index.php?title=Marketing_Team/Boot_Logo&diff=29944Marketing Team/Boot Logo2009-05-30T14:36:08Z<p>Eben: </p>
<hr />
<div>== Basic Sugar Logo Boot Animation ==<br />
<br />
Below is a basic animation that could be considered a safe starting point for experimentation, no surprises, no messing with user interface metaphors. Comprises of a white background, the Sugar logo in default colour at the centre, and 24 grey dots appearing in a circle around it (assumes a grey Fedora Spin logo off in one corner).<br />
<br />
[[Image:basic-sugar-boot.gif|centre]]<br />
<br />
<br />
== Basic Logo Variant with Changing Logo Colour ==<br />
<br />
[[Image:multi-colour-sugar-boot.gif|centre]]<br />
<br />
== Retaining the XO ==<br />
<br />
The use of the outlined XO has always been an important part of the design for us, since it's meant to convey the transition of the laptop/avatar to its "on" state, and the transition of the child into a collaborative/learning space. Here's a very basic option which shows the logo for a bit, but retains the XO for the latter portion of the boot sequence before the transition to Home view, when it becomes colored. (My apologies: I just have two stills to show for now.)<br />
<br />
[[Image:boot-with-xo-1.png|centre]]<br />
<br />
[[Image:boot-with-xo-2.png|centre]]</div>Ebenhttps://wiki.sugarlabs.org/index.php?title=File:Boot-with-xo-2.png&diff=29943File:Boot-with-xo-2.png2009-05-30T14:35:30Z<p>Eben: </p>
<hr />
<div></div>Ebenhttps://wiki.sugarlabs.org/index.php?title=File:Boot-with-xo-1.png&diff=29942File:Boot-with-xo-1.png2009-05-30T14:35:16Z<p>Eben: </p>
<hr />
<div></div>Ebenhttps://wiki.sugarlabs.org/index.php?title=Downloads&diff=20888Downloads2009-03-08T21:17:03Z<p>Eben: </p>
<hr />
<div><noinclude><br />
{{ Translations | [[Downloads|english]] &#124; [[Downloads/lang-es|español]] &#124; [[Downloads/lang-fr|français]] }}<br />
{{ 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 }}<br />
</noinclude><br />
<br />
__NOTOC__<br />
<br />
==Are you a Windows or Macintosh user?==<br />
Windows users should try [[Sugar_on_a_Stick/Installation/Windows|'''Sugar on a Stick''']], and Mac (OSX) users should try [[Supported_systems/Mac|'''VirtualBox''']]. Select your operating system below to give Sugar a try!<br />
<br />
<span class="plainlinks"><br />
[http://sugarlabs.org/go/Sugar_on_a_Stick/Installation/Windows http://sugarlabs.org/wiki/images/f/f9/Windows.gif]<br />
[http://sugarlabs.org/go/Supported_systems/Mac http://sugarlabs.org/wiki/images/7/76/Apple.gif]<br />
</span><br />
<br />
<br />
==Are you already using GNU/Linux?==<br />
Select your favorite distribution below for instructions on installing Sugar.<br />
<br />
<span class="plainlinks"><br />
[http://wiki.sugarlabs.org/go/Community/Distributions/Fedora http://sugarlabs.org/wiki/images/1/17/Fedora-small.jpg]<br />
[http://wiki.sugarlabs.org/go/Community/Distributions/Debian http://sugarlabs.org/wiki/images/b/bf/Debian-small.jpg]<br />
[http://wiki.sugarlabs.org/go/Community/Distributions/Ubuntu http://sugarlabs.org/wiki/images/7/74/Ubuntu-small.jpg]<br />
[http://wiki.sugarlabs.org/go/Community/Distributions/Gentoo http://sugarlabs.org/wiki/images/7/7e/Gentoo-small.png]<br />
[http://wiki.sugarlabs.org/go/Community/Distributions/ALTLinux http://sugarlabs.org/wiki/images/1/12/Altlinux-small.png]<br />
[http://wiki.sugarlabs.org/go/Community/Distributions/Mandriva http://sugarlabs.org/wiki/images/6/67/Mandriva-small.png]<br />
[http://sugarlabs.org/go/Community/Distributions/Magalh%C3%A3es http://sugarlabs.org/wiki/images/5/5b/Caixa_M%C3%A1gica-small.jpg]<br />
[http://en.opensuse.org/Sugar http://sugarlabs.org/wiki/images/e/ec/Suse-small.jpg]<br />
</span><br />
<br />
<br />
==Do you have an OLPC XO-1?==<br />
[[Sugar_on_a_Stick/Installation/OLPC|Update your XO]] to the latest Sugar release.<br />
<br />
<span class="plainlinks"><br />
[http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Installation/OLPC http://sugarlabs.org/wiki/images/8/80/OLPCXO.png]<br />
</span><br />
<br />
<br />
==Are you looking for Sugar Activities?==<br />
<span class="plainlinks">Please visit our dedicated [http://activities.sugarlabs.org Activities download site].</span><br />
<br />
<span class="plainlinks"><br />
[http://activities.sugarlabs.org http://sugarlabs.org/wiki/images/2/2b/Sugarlabs_mainpage_02.png]<br />
</span><br />
<br />
<br />
==Are you a developer?==<br />
<br />
Learn how to get setup on the [[Supported systems]] page. <br />
<br />
<span class="plainlinks"><br />
[http://wiki.sugarlabs.org/go/Supported_systems http://sugarlabs.org/wiki/images/0/06/Gear.png]<br />
</span><br />
<br />
Here are some additional references you may find useful:<br />
* [[DevelopmentTeam/Jhbuild | jhbuild]]<br />
* <span class="plainlinks">[http://git.sugarlabs.org Gitorious source code repository]</span><br />
* VM<br />
* Linux Terminal Server<br />
* Adding Sugar to your favorite distro...</div>Ebenhttps://wiki.sugarlabs.org/index.php?title=File:Windows.gif&diff=20887File:Windows.gif2009-03-08T21:04:04Z<p>Eben: </p>
<hr />
<div></div>Ebenhttps://wiki.sugarlabs.org/index.php?title=Design_Team/Designs&diff=20252Design Team/Designs2009-03-03T00:39:43Z<p>Eben: </p>
<hr />
<div>{{Translations}}<br />
<br />
This page serves as a showcase for design ideas and discussion around the Sugar UI. Each topic below contains a "slideshow" illustrating our latest ideas and outlining some of the decisions and tradeoffs that were made in coming to them. Please feel free to add to the discussion sections to provide useful feedback as we iterate on the designs and move them toward implementation.<br />
<br />
For more detailed (and more technical) descriptions of some of the topics presented below, please visit the [[DesignTeam/Specifications | specification]] pages, which will drive the implementation of specific features.<br />
<br />
<br />
<br />
=== [[DesignTeam/Designs/Activity Management | Activity Management]] ===<br />
<br />
This slideshow focuses on our new approaches to activity launching, switching, and management. Most importantly, it includes updated design ideas for the Home screen and a brand new Frame organization which enhances activity management, though has additional merits on its own as well.<br />
<br />
===[[DesignTeam/Designs/Frame | Frame]]===<br />
<br />
This slideshow provides a deeper understanding of the reorganized Frame, describing its sections for people, places (and activities), clipboard, and devices. It also introduces the foundation of the notification system and explains its relationship to the Frame's layout and purpose as a persistent UI element.<br />
<br />
===[[DesignTeam/Designs/Journal | Journal]]===<br />
<br />
This slideshow presents a brand new vision for the Journal, which is focused around two views: object and action. The object view will be reminiscent of the current Journal UI, presenting a list of objects stored on the system and providing access to detailed information and (now) their version histories. The action view, on the other hand, will serve as a friendly "journal-like" log of the child's interactions with the machine, referencing one or more objects but reading much like a scrapbook, and providing a friendly browsable interface into the content they have created.<br />
<br />
===[[DesignTeam/Designs/Toolbars | Toolbars]]===<br />
<br />
This slideshow illustrates the latest thinking regarding toolbars and the nature of tabs within the interface.</div>Ebenhttps://wiki.sugarlabs.org/index.php?title=Design_Team/Specifications&diff=20251Design Team/Specifications2009-03-03T00:37:09Z<p>Eben: New page: The following list of specifications is a work in progress, and will be fleshed out over the coming weeks/months. * Clipboard * [[DesignTeam/Spec...</p>
<hr />
<div>The following list of specifications is a work in progress, and will be fleshed out over the coming weeks/months.<br />
<br />
* [[DesignTeam/Specifications/Clipboard | Clipboard]]<br />
* [[DesignTeam/Specifications/Groups | Groups]]<br />
* [[DesignTeam/Specifications/Toolbars | Toolbars]]<br />
* [[DesignTeam/Specifications/Palettes | Palettes]]<br />
* [[DesignTeam/Specifications/Trays | Trays]]<br />
* [[DesignTeam/Specifications/Color Chooser | Color Chooser]]<br />
* [[DesignTeam/Specifications/Object Chooser | Object Chooser]]<br />
* [[DesignTeam/Specifications/Object Transfers | Object Transfers]]<br />
* [[DesignTeam/Specifications/Modal Dialogs | Modal Dialogs]]<br />
* [[DesignTeam/Specifications/Non-Modal Dialogs | Non-Modal Dialogs]]<br />
* [[DesignTeam/Specifications/Specific Dialogs | Specific Dialogs]]<br />
* [[DesignTeam/Specifications/Notifications | Notifications]]<br />
* [[DesignTeam/Specifications/Activity Launch | Activity Launch]]<br />
* [[DesignTeam/Specifications/Screenshots | Screenshots]]<br />
* [[DesignTeam/Specifications/Icons | Icons]]<br />
* [[DesignTeam/Specifications/Overlay Chat | Overlay Chat]]<br />
* [[DesignTeam/Specifications/Bulletin Board | Bulletin Board]]</div>Ebenhttps://wiki.sugarlabs.org/index.php?title=Design_Team/Specifications/Clipboard&diff=20250Design Team/Specifications/Clipboard2009-03-03T00:25:58Z<p>Eben: </p>
<hr />
<div>== Visual Spec ==<br />
<br />
The clipboard lives within the left edge of the frame, and as such has all the associated visual characteristics of the tray control. The visual spec below indicates the appearance of clipping icons and their palettes.<br />
<br />
===Clippings===<br />
<br />
The clipboard may contain both Clippings and Objects, the distinction between which should be understood as provided blow. I'll use lowercase "clippings" to refer to both types in general.<br />
<br />
'''Clippings:''' are temporary objects that result from copying image, text, or any other data from within another larger context such as a paint or write activity. These temporary clippings have no associated activity ID, no name/title, and no permanence on the system beyond the clipboard. As such, they will receive one of the standard clipping icons (and titles) provided by the system, according to their mime type.<br />
<br />
'''Objects:''' have some amount permanence, in varying levels, and more specifically represent a notion of ''wholeness.'' Examples of several forms of Objects are an image copied from Browse (it is a whole image), an instrument copied from within TamTam (the entire instrument sound, not just an audio clipping from it), or an instance of an activity object (copied from the Journal). Objects will ''always'' have a title, and may additionally have an associated icon. In some cases the icon will be directly associated with the Object, such as when it comes from the Journal; in other cases, an activity may have to provide an icon when the copy is performed. The important distinction of objects is that they have a name/title.<br />
<br />
====Kinds====<br />
<br />
The following list indicates the 6 "primitive types" of data in Sugar, with data of course being the most generic.<br />
<br />
* Text<br />
* Image<br />
* Video<br />
* Audio<br />
* URL<br />
* Data<br />
<br />
====Titles====<br />
<br />
Clippings, which don't have an associated title, will be titled with the name of the clipping type itself eg. "Text clipping", "Image clipping" etc. Objects, of course, have their own associated titles eg. "A drawing of my house", "Family Photo", etc. The API for the clipboard should allow an activity to provide a title for a clipping when appropriate. The title of a clipping appears as the primary text of it's palette.<br />
<br />
====Icons====<br />
<br />
Clippings have generic icons as provided by the system. Clipping icons, which are of course created by the child on his/her own laptop, should always be rendered in the child's chosen XO colors.<br />
<br />
Objects may have a specific icon associated with them, and the clipboard API should allow activities to specify one when appropriate. This icon should always be colored, but may not be colored in the child's own XO colors. If the Object comes from the Journal, from a BBoard, or even from within an activity having an identity associated with another XO, the colors of the original creator should be reflected in the clipboard. On the other hand, any Object which has no associated owner should take on the child's own XO colors. The visual style of these icons will match that of all Object icons.<br />
<br />
Note that some Objects may not actually have a specific icon. For instance, an image copied from Browse has a title but no particular icon. When no icon is specified, the standard clipping icon will be used, regardless of the association of a title with the Object.<br />
<br />
====Previews====<br />
<br />
Since the Sugar clipboard can contain multiple clippings, previews should be used whenever possible to make locating the desired clipping easy. The appropriate preview will depend upon the type of the clipping. For each type we will define a default preview, and in all cases it will be possible for the activity to provide an image and/or a string to override the default. <br />
<br />
The default previews follow:<br />
<br />
'''Text:''' The head of the string up to the nearest word boundary beneath ''n'' characters. When the preview does not represent the entire copied string it should end with an ellipsis, and the string should be quoted to indicate that it was taken from the clipping. Text previews should appear as the secondary text of the palette, for quickest access.<br />
<br />
'''Image:''' A thumbnail of the image will appear in the secondary palette, with maximin dimensions of ''w'' x ''h''.<br />
<br />
'''Video:''' In the short term, we'll use a thumbnail still from the video at some time ''t'' from the beginning of the clip. Ideally, we'll provide live video previews via a small embedded player. This should appear just as the image thumbnail.<br />
<br />
'''Audio:''' A visual of the waveform for the audio clip, and/or a live audio preview, to be shown within the secondary palette.<br />
<br />
'''URL:''' The URL string, shortened in the ''middle'' with an ellipsis when too long, should appear as the secondary title of the palette.<br />
<br />
'''Data:''' For data which we cannot otherwise display, we'll simply provide the icon and name of the activity the clipping was created from to give it context eg. "Copied from TamTam". The "copied from..." string should appear as the secondary text of the palette, while the icon appears within the secondary palette.<br />
<br />
==== Selection ====<br />
<br />
Exactly one clipping may be selected at any given time. The clippings should thus be implemented as a radio button set, the selected item of which will appear with the standard gray rounded-rectangle.<br />
<br />
== Interaction Spec ==<br />
<br />
The clipboard is specified in such a way that it will behave identically to those on current operating systems, while at the same time providing additional support for advanced users including drag and drop support and history.<br />
<br />
===Copying===<br />
<br />
A child may place an object on the clipboard in a couple convenient ways. First, the traditional CTRL-C shortcut will copy the current selection to the clipboard; both the ctrl-X and ALT-C shortcuts will provide "copy and erase" functionality, placing the selection on the clipboard in the same manner, and removing it from the context from which it was "cut". Additionally, since objects support direct manipulation, the child may simply drag a photo, file, or selection onto the clipboard edge of the frame in order to copy it. Any activity which supports copy and paste operations should also provide an "Edit" toolbar containing buttons for this functionality.<br />
<br />
As items are placed on the clipboard, they are arranged temporally in a "push-through" stack, with the most recent clipping appearing at the top of the stack (the upper end of the clipboard) and becoming the current selection. Once the clipboard reaches a predefined limit (as many as will fit in the left edge of the frame), the elements at the bottom of the stack will begin to drop off, making room for the new ones and preventing the clipboard from growing indefinitely in size and memory consumption.<br />
<br />
===Selecting a source===<br />
<br />
With the presence of a clipboard which contains multiple clippings, it becomes necessary to add a means for selecting an active clipping as the source for any paste command. Any invocation of a copy or copy-and-erase shortcut will automatically place the resulting clipping at the top of the stack, selecting it as the source, so that a subsequent paste command behaves as expected. Likewise, any item dragged to the clipboard will become the newly selected source. This maintains consistency with current single-item clipboards.<br />
<br />
An alternate source may be manually selected as desired, via a single click on the clipping.<br />
<br />
===Pasting===<br />
<br />
Paste will be supported with CTRL-V in the usual manner. The paste operation will not change the selected source, such that subsequent pastes will repeatedly paste the same clipping, again retaining the behavior of common single-item clipboards by default. Drag'n'drop support will allow the child to drag any clipping out of the clipboard to paste it in another location which supports its type, such as within another activity, on a friend, or to a Bulletin Board. The clipping that is chosen as the source for a drag need not be first selected as the source, nor should the dragged item become the source as a result of the drag operation.<br />
<br />
The clipboard will also support an alternate paste-and-remove operation, attached to the ALT-V shortcut. This will paste the currently selected source and remove the source clipping from the clipboard in one step. When the clipping is removed, the previous clipping (the one that was below it in the stack) will become the new source, essentially popping the clipping of the stack (if the selected source is at the top). In this manner, one could copy three items in one activity and subsequently paste all three in a row into another.<br />
<br />
Elements may also be removed explicitly by the user via their secondary rollover palette.<br />
<br />
===Actions===<br />
<br />
The following actions should be available on all clippings.<br />
<br />
'''Paste:'''<br />
<br />
'''Paste & remove:'''<br />
<br />
'''Open with >:'''<br />
<br />
'''Keep in Journal:'''<br />
<br />
'''Remove:'''<br />
<br />
'''Send to >:'''</div>Ebenhttps://wiki.sugarlabs.org/index.php?title=Design_Team/Specifications/Clipboard&diff=20249Design Team/Specifications/Clipboard2009-03-03T00:25:26Z<p>Eben: New page: == Visual Spec == The clipboard lives within the left edge of the frame, and as such has all the associated visual characteristics of the tray control. The visual spec below indicates th...</p>
<hr />
<div>== Visual Spec ==<br />
<br />
The clipboard lives within the left edge of the frame, and as such has all the associated visual characteristics of the tray control. The visual spec below indicates the appearance of clipping icons and their palettes.<br />
<br />
===Clippings===<br />
<br />
The clipboard may contain both Clippings and Objects, the distinction between which should be understood as provided blow. I'll use lowercase "clippings" to refer to both types in general.<br />
<br />
'''Clippings:''' are temporary objects that result from copying image, text, or any other data from within another larger context such as a paint or write activity. These temporary clippings have no associated activity ID, no name/title, and no permanence on the system beyond the clipboard. As such, they will receive one of the standard clipping icons (and titles) provided by the system, according to their mime type.<br />
<br />
'''Objects:''' have some amount permanence, in varying levels, and more specifically represent a notion of ''wholeness.'' Examples of several forms of Objects are an image copied from Browse (it is a whole image), an instrument copied from within TamTam (the entire instrument sound, not just an audio clipping from it), or an instance of an activity object (copied from the Journal). Objects will ''always'' have a title, and may additionally have an associated icon. In some cases the icon will be directly associated with the Object, such as when it comes from the Journal; in other cases, an activity may have to provide an icon when the copy is performed. The important distinction of objects is that they have a name/title.<br />
<br />
====Kinds====<br />
<br />
The following list indicates the 6 "primitive types" of data in Sugar, with data of course being the most generic.<br />
<br />
* Text<br />
* Image<br />
* Video<br />
* Audio<br />
* URL<br />
* Data<br />
<br />
====Titles====<br />
<br />
Clippings, which don't have an associated title, will be titled with the name of the clipping type itself eg. "Text clipping", "Image clipping" etc. Objects, of course, have their own associated titles eg. "A drawing of my house", "Family Photo", etc. The API for the clipboard should allow an activity to provide a title for a clipping when appropriate. The title of a clipping appears as the primary text of it's palette.<br />
<br />
====Icons====<br />
<br />
Clippings have generic icons as provided by the system. Clipping icons, which are of course created by the child on his/her own laptop, should always be rendered in the child's chosen XO colors.<br />
<br />
Objects may have a specific icon associated with them, and the clipboard API should allow activities to specify one when appropriate. This icon should always be colored, but may not be colored in the child's own XO colors. If the Object comes from the Journal, from a BBoard, or even from within an activity having an identity associated with another XO, the colors of the original creator should be reflected in the clipboard. On the other hand, any Object which has no associated owner should take on the child's own XO colors. The visual style of these icons will match that of all Object icons.<br />
<br />
Note that some Objects may not actually have a specific icon. For instance, an image copied from Browse has a title but no particular icon. When no icon is specified, the standard clipping icon will be used, regardless of the association of a title with the Object.<br />
<br />
====Previews====<br />
<br />
Since the Sugar clipboard can contain multiple clippings, previews should be used whenever possible to make locating the desired clipping easy. The appropriate preview will depend upon the type of the clipping. For each type we will define a default preview, and in all cases it will be possible for the activity to provide an image and/or a string to override the default. <br />
<br />
The default previews follow:<br />
<br />
'''Text:''' The head of the string up to the nearest word boundary beneath ''n'' characters. When the preview does not represent the entire copied string it should end with an ellipsis, and the string should be quoted to indicate that it was taken from the clipping. Text previews should appear as the secondary text of the palette, for quickest access.<br />
<br />
'''Image:''' A thumbnail of the image will appear in the secondary palette, with maximin dimensions of ''w'' x ''h''.<br />
<br />
'''Video:''' In the short term, we'll use a thumbnail still from the video at some time ''t'' from the beginning of the clip. Ideally, we'll provide live video previews via a small embedded player. This should appear just as the image thumbnail.<br />
<br />
'''Audio:''' A visual of the waveform for the audio clip, and/or a live audio preview, to be shown within the secondary palette.<br />
<br />
'''URL:''' The URL string, shortened in the ''middle'' with an ellipsis when too long, should appear as the secondary title of the palette.<br />
<br />
'''Data:''' For data which we cannot otherwise display, we'll simply provide the icon and name of the activity the clipping was created from to give it context eg. "Copied from TamTam". The "copied from..." string should appear as the secondary text of the palette, while the icon appears within the secondary palette.<br />
<br />
== Selection ==<br />
<br />
Exactly one clipping may be selected at any given time. The clippings should thus be implemented as a radio button set, the selected item of which will appear with the standard gray rounded-rectangle.<br />
<br />
== Interaction Spec ==<br />
<br />
The clipboard is specified in such a way that it will behave identically to those on current operating systems, while at the same time providing additional support for advanced users including drag and drop support and history.<br />
<br />
===Copying===<br />
<br />
A child may place an object on the clipboard in a couple convenient ways. First, the traditional CTRL-C shortcut will copy the current selection to the clipboard; both the ctrl-X and ALT-C shortcuts will provide "copy and erase" functionality, placing the selection on the clipboard in the same manner, and removing it from the context from which it was "cut". Additionally, since objects support direct manipulation, the child may simply drag a photo, file, or selection onto the clipboard edge of the frame in order to copy it. Any activity which supports copy and paste operations should also provide an "Edit" toolbar containing buttons for this functionality.<br />
<br />
As items are placed on the clipboard, they are arranged temporally in a "push-through" stack, with the most recent clipping appearing at the top of the stack (the upper end of the clipboard) and becoming the current selection. Once the clipboard reaches a predefined limit (as many as will fit in the left edge of the frame), the elements at the bottom of the stack will begin to drop off, making room for the new ones and preventing the clipboard from growing indefinitely in size and memory consumption.<br />
<br />
===Selecting a source===<br />
<br />
With the presence of a clipboard which contains multiple clippings, it becomes necessary to add a means for selecting an active clipping as the source for any paste command. Any invocation of a copy or copy-and-erase shortcut will automatically place the resulting clipping at the top of the stack, selecting it as the source, so that a subsequent paste command behaves as expected. Likewise, any item dragged to the clipboard will become the newly selected source. This maintains consistency with current single-item clipboards.<br />
<br />
An alternate source may be manually selected as desired, via a single click on the clipping.<br />
<br />
===Pasting===<br />
<br />
Paste will be supported with CTRL-V in the usual manner. The paste operation will not change the selected source, such that subsequent pastes will repeatedly paste the same clipping, again retaining the behavior of common single-item clipboards by default. Drag'n'drop support will allow the child to drag any clipping out of the clipboard to paste it in another location which supports its type, such as within another activity, on a friend, or to a Bulletin Board. The clipping that is chosen as the source for a drag need not be first selected as the source, nor should the dragged item become the source as a result of the drag operation.<br />
<br />
The clipboard will also support an alternate paste-and-remove operation, attached to the ALT-V shortcut. This will paste the currently selected source and remove the source clipping from the clipboard in one step. When the clipping is removed, the previous clipping (the one that was below it in the stack) will become the new source, essentially popping the clipping of the stack (if the selected source is at the top). In this manner, one could copy three items in one activity and subsequently paste all three in a row into another.<br />
<br />
Elements may also be removed explicitly by the user via their secondary rollover palette.<br />
<br />
===Actions===<br />
<br />
The following actions should be available on all clippings.<br />
<br />
'''Paste:'''<br />
<br />
'''Paste & remove:'''<br />
<br />
'''Open with >:'''<br />
<br />
'''Keep in Journal:'''<br />
<br />
'''Remove:'''<br />
<br />
'''Send to >:'''</div>Ebenhttps://wiki.sugarlabs.org/index.php?title=Design_Team/Specifications/Groups&diff=20248Design Team/Specifications/Groups2009-03-02T23:58:09Z<p>Eben: New page: == What is a group? == A group is composed of a set of people who have elected to have membership in that group, and who all agree upon the membership of that group. In other words, unli...</p>
<hr />
<div>== What is a group? ==<br />
<br />
A group is composed of a set of people who have elected to have membership in that group, and who all agree upon the membership of that group. In other words, unlike "buddy lists" in common instant messaging clients which offer ''local'' (per user) definition of groups mostly for organizational purposes, groups instead offer a facility for defining sets of people who all desire to collaborate together.<br />
<br />
This could be a school, a class, or a study group. It could be a chess club, a poetry group, or a set of close friends. Groups can be defined for the duration of the schoolyear, the duration of a specific project assignment, or simply for the day. Groups are a flexible and open framework for making collaboration with others simple and efficient.<br />
<br />
== Types of Groups ==<br />
<br />
We envision two types of groups: open and closed. The distinction between these is the management infrastructure (which we minimize as much as possible in both cases).<br />
<br />
=== Open groups ===<br />
<br />
Open groups have no manager(s). This means that the set of operations that can be performed on the group are the same for every member of the group. First, consider the set of properties that defines an open group.<br />
<br />
Properties:<br />
<br />
# Name<br />
# Colors/Icon<br />
# Set of members<br />
<br />
Then, consider the set of operations that can (or cannot) be performed on these properties. The name is chosen at time of creation of the group, and cannot be changed thereafter. The colors and icon are also chosen at creation time, and cannot be changed. Any member within the group may invite additional members, and any member may leave the group freely. Open groups naturally disappear when their membership sets become empty.<br />
<br />
=== Closed groups ===<br />
<br />
Properties:<br />
<br />
# Name<br />
# Colors/Icon<br />
# Set of members<br />
# Set of instructors<br />
<br />
Closed groups provide additional facilities for management, which can be useful in structured settings, such as a classroom. To enable this, closed groups also have a set of instructors, in addition to the members set, who have the ability to perform group management. Instructors may rename the group, change it's icon/colors, edit group membership, and add instructors.<br />
<br />
Unlike open groups, membership is defined solely by the instructors. Members (who are not also instructors) cannot invite new members to a closed group, nor may they leave the group freely. Instructors may promote members to instructors, or add new instructors, but can only remove themselves from the instructors list. At least one instructor must be defined for any closed group; the last remaining instructor cannot remove herself, but can opt to delete the group.<br />
<br />
In addition to managing the sets of people which define the groups, instructors may delete a closed group, or choose to convert a closed group to an open one. When a closed group is opened, all instructors become simple members of the group. It is not possible to convert an open group to a closed one (though it is trivial to define a ''new'' closed group based on an existing open one).<br />
<br />
The management facilities in closed groups make it possible to define classes, manage the student roster, transfer classes to new teachers, rename groups (say, from "grade 3" to "grade 4"), etc. The class example is the primary use case for closed groups, though others surely exist.<br />
<br />
== Creating groups ==<br />
<br />
Groups are exposed, primarily, in the Groups view of the Sugar UI---one of the four zoom levels defined in the interface. Anyone may create a group. The interface for group creation allows the creator to set the basic group parameters such as name, color, and icon, to define a set of initial members to invite to the group, and the option to make the group open or closed.<br />
<br />
Once the group has been defined, invitations are sent to the set of initial members (and instructors, if applicable). The invitee receiving the invitation then has the option to accept or reject the invitation. Upon accepting, the new group gets added to their list of available groups.<br />
<br />
== Leveraging groups for collaboration ==<br />
<br />
So, what good are groups anyway? The group framework exists primarily to enable simple and seamless collaboration in Sugar. This includes easily finding group members and joining their activities, sharing activities with specific groups of people, and finding objects and activities created by or with a given group of people within the Journal.<br />
<br />
=== Visualizing groups ===<br />
<br />
Groups are a core construct of the "zooming" interface of the Sugar UI. With a zoom level dedicated just to them, it is possible to visualize individual groups, filtering the densely populated neighborhood to a specific set of individuals and their activities.<br />
<br />
This filtering is an important aspect of the scalability of the collaborative interface Sugar provides, since it makes it simple to view relevant slices of the available information, perhaps by class, or by subject, or by groups of friends and family<br />
<br />
=== Sharing with a group ===<br />
<br />
Groups also make sharing one-step simple. Rather than having to invite a number of individuals to an activity, a child can simply share an activity with a group (or groups) of choice.<br />
<br />
This also offers an addition level of granularity with respect to sharing. Whereas currently activities may only be shared with privately invited individuals or openly public, groups provide an intermediate scope for sharing with a specific set of individuals. Effectively, the set of individuals who can see and join a given activity is defined as the union of all groups it has been shared with and all individuals invited to it.<br />
<br />
=== Groups and the Journal ===<br />
<br />
In addition to providing a shortcut of sorts for sharing activities, groups also have a purpose within the Journal. Metadata regarding the groups any activity has been shared with are kept with their Journal entries, making it possible to locate all activities worked on with a given group.</div>Ebenhttps://wiki.sugarlabs.org/index.php?title=Design_Team&diff=20237Design Team2009-03-02T21:43:25Z<p>Eben: </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 }}<br />
{{TeamHeader|DesignTeam}}</noinclude><br />
<br />
== Mission ==<br />
{{:DesignTeam/Mission}}<br />
<br />
==Human Interface Guidelines==<br />
The [http://sugarlabs.org/go/DesignTeam/Human_Interface_Guidelines Sugar Sugar Human Interface Guidelines] provide insight into the design of the Sugar experience, as well as guidelines for designing custom icons, controls, and activity interfaces.<br />
<br />
== Designs ==<br />
The Design Team manages a series of [[DesignTeam/Designs | Design "slideshows"]] which illustrate various parts of the interface and how they function in a typical workflow.<br />
<br />
== Specifications ==<br />
The Design Team also maintains a list of [[DesignTeam/Specifications | specifications]] which provide additional details regarding the appearance and behavior of various software features. The specifications page is empty at present, but will be populated soon with preliminary specs for a number of features either currently implemented or planned for upcoming releases.<br />
<br />
=== business cards ===<br />
<br />
There are four images ([[:Image:Logo_orange_800x800.png|orange]], [[:Image:Logo_blue_800x800.png|blue]], [[:Image:Logo_magenta_800x800.png|magenta]], and [[:Image:Logo_green_800x800.png|green]]) that can be used to make [http://moo.com Moo] Sugar Labs business cards.<br />
<br />
[[Category:DesignTeam]]</div>Ebenhttps://wiki.sugarlabs.org/index.php?title=Design_Team/Meetings&diff=20184Design Team/Meetings2009-03-01T16:43:23Z<p>Eben: /* Sunday March 1, 2009 - 15.00 (UTC) */</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|DesignTeam}} </noinclude><br />
__NOTOC__<br />
<div style="font-size: 1.3em; background: #edfdd7; padding: 10px; border: 1px solid #cde7a8">The Design team will be holding a meeting on Sunday 01 March 2009 at 13:00 UTC (10:00 EST) on irc.freenode.net (channel: #sugar-meeting ie go to http://en.forum.laptop.org/chat/irc.cgi and select "status" at the top of screen, type /join #sugar-meeting into bottom pane.). Please add to the agenda below and please join in with your ideas.<br />
<br />
Hint: You can use an [http://www.timeanddate.com/worldclock/converter.html online time calculator] to convert from UTC to your local time zone or back.<br />
</div><br />
== Who and what==<br />
The meeting is targeted to Sugar core and activity developers, but remains open to anyone interested. It's primary purpose is to open the design approach, making it more transparent and allowing the community to provide feedback on both current and upcoming features.<br />
<br />
In general, discussion focuses on:<br />
* high level design goals and ideas<br />
* feedback and discussion of problems in the current design<br />
* reviews of design proposals<br />
<br />
To convert UTC to your local time, use [http://www.timeanddate.com/worldclock/converter.html?hour=11&min=30&sec=0&p1=0&p2=43 this converter] or run: <br />
date -d '[current date] [time] UTC' <br />
date -d '2008-06-03 14:00 UTC'<br />
<br />
== Adding topics ==<br />
You can add topics for discussion to the topics section for the meeting throughout the week. Posted topics will be collected and sent out in the announcement on the morning of the meeting.<br />
<br />
== Meetings ==<br />
=== Sun March 1, 2009 - 13.00 (UTC) / 10.00 EST ===<br />
<br />
==== Topics ====<br />
<br />
We'll continue discussion of revised, and thorough, mockups for overlay chat in activities. This includes ways in which this chat system can extend into the other zoom levels, and short term and long term goals.<br />
<br />
Other topics: Discuss development roadmap and prioritize design activities for next build<br />
<br />
<br />
=== Friday December 19, 2008 - 15.30 (UTC) ===<br />
<br />
==== Topics ====<br />
<br />
We'll continue discussion of revised, and thorough, mockups for overlay chat in activities. This includes ways in which this chat system can extend into the other zoom levels, and short term and long term goals.<br />
<br />
<br />
=== Thursday December 4, 2008 - 15.30 (UTC) ===<br />
<br />
==== Topics ====<br />
<br />
We'll focus on possibilities for overlay chat in activites, presenting both short term and long term ideas, and discuss how this could later be extended to the neighborhood.<br />
<br />
==== Media ====<br />
<br />
* [[Media:Overlay_chat_sketch.pdf | Overlay chat sketch (PDF)]]<br />
<br />
==== Logs ====<br />
<br />
* http://meeting.laptop.org/sugar-meeting.20081204_1042.html<br />
<br />
=== Wednesday November 26, 2008 - 15.00 (UTC) ===<br />
<br />
We'd like to hold a meeting this week while the topics discussed at the recent SugarCamp are fresh in our minds. Though this is not part of the usual meeting cycle, I think it's important enough to merit an extra meeting. Due to Thanksgiving on Thursday, we'll hold it on Wednesday instead.<br />
<br />
==== Topics ====<br />
===== Short Term Roadmap Definition =====<br />
<br />
To capitalize on the extremely valuable discussions at the recent SugarCamp in Cambridge, we'd like to take some time to define a rough feature roadmap for the Sugar OS within the OLPC 9.1 timeframe. As a starting point for this discussion, we should likely review the various design proposals presented on the last day of the conference.<br />
<br />
=====Groups=====<br />
=====Resuming activities from Home=====<br />
=====Enhancing the Journal=====<br />
=====Improving Toolbars=====<br />
=====Encouraging Naming/Tagging=====<br />
<br />
==== Logs ====<br />
* http://meeting.laptop.org/sugar-meeting.20081126_1018.html<br />
<br />
<br />
=== Thursday September 18, 2008 - 15.30 (UTC) ===<br />
==== Topics ====<br />
===== Visual Clipboard API =====<br />
For reference, please see the [http://wiki.laptop.org/go/Specifications/Clipboard clipboard specification]. For a more targeted list of features and goals, please see the [[DevelopmentTeam/0.84/Clipboard|clipboard planning page]].<br />
<br />
We had a fairly long discussion about this, which didn't seem to get too far. Fortunately, a follow-up between Marco and I clarified some points, and we agreed that it should be possible to implement the majority of the goals across the system using the "formats" allowed in the GTK protocols, and falling back to sane defaults when extra info isn't provided.<br />
<br />
Some references:<br />
* http://www.pygtk.org/pygtk2tutorial/ch-NewInPyGTK2.2.html#sec-Clipboards<br />
* http://www.pygtk.org/pygtk2tutorial/ch-DragAndDrop.html<br />
* http://www.pygtk.org/pygtk2tutorial/ch-ManagingSelections.html<br />
<br />
===== Advancing the Journal =====<br />
I'd like to have a conversation regarding the current iteration of the Journal, future plans, and the steps we hope to take toward them in the next major release so we can scope our goals. The latest mockups (though slightly out of date) can be seen [http://wiki.laptop.org/go/Designs/Journal here].<br />
<br />
Due to the lengthy clipboard discussion, we didn't hit this topic today. We'll pick it up first thing next week.<br />
<br />
===== Icon reviews =====<br />
We discussed three icons today.<br />
<br />
'''Settings (control panel)''': By popular demand, a wrench was chosen as the base for this icon, though it was also proposed that a wrench and screwdriver could be clearer. It was agreed that the wrench is a simpler icon, and a more generic metaphor which could be used to represent "settings" throughout the system. A few visual tweaks {{Trac|8198|}} made many happier with the wrench, but since this isn't a major change they can come post 8.2.<br />
<br />
'''View Details (Journal)''': The old designs for this button closely resembled a play button (but with an open triangle, akin to a greater than (>) symbol), which some found confusing. The new proposal is an ellipsis [...] icon, to indicate the idea that more info is available, but omitted in the abbreviated list view. This works nicely within the [wiki.laptop.org/go/Designs/Journal new Journal designs], since the icons will occasionally appear within a string of icon-annotated text. All present agreed the latter was a better direction. This change could make 8.2.<br />
<br />
'''Access Point''': Recent experience reports have indicated that the removal of an identifier of the connected AP is frustrating. The proposal discussed is shown [http://interdimensionmedia.com/scratch/devices.png], which wraps the former AP icon (the circle) in "parenthesis" (meant to indicate radio signal). This retains the primitive circular shape of the current access points, but illustrates which is connected in a way which alludes to the wireless activity LED. The point was discussed that the other LED is actually more semantically correct, but not as suitable as an icon.<br />
<br />
Additionally, these [http://wiki.laptop.org/go/Image:School_server_and_ap.png alternate designs] were proposed, using antennae to make the purpose of the icons clearer. We may wish to elicit feedback about these alternatives from teachers and kids to see which convey the notion of wireless connectivity the best. The triangle proposed here was used once, and subsequently removed due to some distaste for the shape in this context, but it may still convey the idea better with the antenna. This change is strongly desired for 8.2.<br />
<br />
<br />
=== Sunday March 1, 2009 - 15.00 (UTC) ===<br />
<br />
Logs: [[DesignTeam/Meetings/09.03.01]]<br />
<br />
[[Category:DevelopmentTeam]]<br />
[[Category:Meetings]]</div>Ebenhttps://wiki.sugarlabs.org/index.php?title=Design_Team/Meetings&diff=20183Design Team/Meetings2009-03-01T16:41:40Z<p>Eben: </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|DesignTeam}} </noinclude><br />
__NOTOC__<br />
<div style="font-size: 1.3em; background: #edfdd7; padding: 10px; border: 1px solid #cde7a8">The Design team will be holding a meeting on Sunday 01 March 2009 at 13:00 UTC (10:00 EST) on irc.freenode.net (channel: #sugar-meeting ie go to http://en.forum.laptop.org/chat/irc.cgi and select "status" at the top of screen, type /join #sugar-meeting into bottom pane.). Please add to the agenda below and please join in with your ideas.<br />
<br />
Hint: You can use an [http://www.timeanddate.com/worldclock/converter.html online time calculator] to convert from UTC to your local time zone or back.<br />
</div><br />
== Who and what==<br />
The meeting is targeted to Sugar core and activity developers, but remains open to anyone interested. It's primary purpose is to open the design approach, making it more transparent and allowing the community to provide feedback on both current and upcoming features.<br />
<br />
In general, discussion focuses on:<br />
* high level design goals and ideas<br />
* feedback and discussion of problems in the current design<br />
* reviews of design proposals<br />
<br />
To convert UTC to your local time, use [http://www.timeanddate.com/worldclock/converter.html?hour=11&min=30&sec=0&p1=0&p2=43 this converter] or run: <br />
date -d '[current date] [time] UTC' <br />
date -d '2008-06-03 14:00 UTC'<br />
<br />
== Adding topics ==<br />
You can add topics for discussion to the topics section for the meeting throughout the week. Posted topics will be collected and sent out in the announcement on the morning of the meeting.<br />
<br />
== Meetings ==<br />
=== Sun March 1, 2009 - 13.00 (UTC) / 10.00 EST ===<br />
<br />
==== Topics ====<br />
<br />
We'll continue discussion of revised, and thorough, mockups for overlay chat in activities. This includes ways in which this chat system can extend into the other zoom levels, and short term and long term goals.<br />
<br />
Other topics: Discuss development roadmap and prioritize design activities for next build<br />
<br />
<br />
=== Friday December 19, 2008 - 15.30 (UTC) ===<br />
<br />
==== Topics ====<br />
<br />
We'll continue discussion of revised, and thorough, mockups for overlay chat in activities. This includes ways in which this chat system can extend into the other zoom levels, and short term and long term goals.<br />
<br />
<br />
=== Thursday December 4, 2008 - 15.30 (UTC) ===<br />
<br />
==== Topics ====<br />
<br />
We'll focus on possibilities for overlay chat in activites, presenting both short term and long term ideas, and discuss how this could later be extended to the neighborhood.<br />
<br />
==== Media ====<br />
<br />
* [[Media:Overlay_chat_sketch.pdf | Overlay chat sketch (PDF)]]<br />
<br />
==== Logs ====<br />
<br />
* http://meeting.laptop.org/sugar-meeting.20081204_1042.html<br />
<br />
=== Wednesday November 26, 2008 - 15.00 (UTC) ===<br />
<br />
We'd like to hold a meeting this week while the topics discussed at the recent SugarCamp are fresh in our minds. Though this is not part of the usual meeting cycle, I think it's important enough to merit an extra meeting. Due to Thanksgiving on Thursday, we'll hold it on Wednesday instead.<br />
<br />
==== Topics ====<br />
===== Short Term Roadmap Definition =====<br />
<br />
To capitalize on the extremely valuable discussions at the recent SugarCamp in Cambridge, we'd like to take some time to define a rough feature roadmap for the Sugar OS within the OLPC 9.1 timeframe. As a starting point for this discussion, we should likely review the various design proposals presented on the last day of the conference.<br />
<br />
=====Groups=====<br />
=====Resuming activities from Home=====<br />
=====Enhancing the Journal=====<br />
=====Improving Toolbars=====<br />
=====Encouraging Naming/Tagging=====<br />
<br />
==== Logs ====<br />
* http://meeting.laptop.org/sugar-meeting.20081126_1018.html<br />
<br />
<br />
=== Thursday September 18, 2008 - 15.30 (UTC) ===<br />
==== Topics ====<br />
===== Visual Clipboard API =====<br />
For reference, please see the [http://wiki.laptop.org/go/Specifications/Clipboard clipboard specification]. For a more targeted list of features and goals, please see the [[DevelopmentTeam/0.84/Clipboard|clipboard planning page]].<br />
<br />
We had a fairly long discussion about this, which didn't seem to get too far. Fortunately, a follow-up between Marco and I clarified some points, and we agreed that it should be possible to implement the majority of the goals across the system using the "formats" allowed in the GTK protocols, and falling back to sane defaults when extra info isn't provided.<br />
<br />
Some references:<br />
* http://www.pygtk.org/pygtk2tutorial/ch-NewInPyGTK2.2.html#sec-Clipboards<br />
* http://www.pygtk.org/pygtk2tutorial/ch-DragAndDrop.html<br />
* http://www.pygtk.org/pygtk2tutorial/ch-ManagingSelections.html<br />
<br />
===== Advancing the Journal =====<br />
I'd like to have a conversation regarding the current iteration of the Journal, future plans, and the steps we hope to take toward them in the next major release so we can scope our goals. The latest mockups (though slightly out of date) can be seen [http://wiki.laptop.org/go/Designs/Journal here].<br />
<br />
Due to the lengthy clipboard discussion, we didn't hit this topic today. We'll pick it up first thing next week.<br />
<br />
===== Icon reviews =====<br />
We discussed three icons today.<br />
<br />
'''Settings (control panel)''': By popular demand, a wrench was chosen as the base for this icon, though it was also proposed that a wrench and screwdriver could be clearer. It was agreed that the wrench is a simpler icon, and a more generic metaphor which could be used to represent "settings" throughout the system. A few visual tweaks {{Trac|8198|}} made many happier with the wrench, but since this isn't a major change they can come post 8.2.<br />
<br />
'''View Details (Journal)''': The old designs for this button closely resembled a play button (but with an open triangle, akin to a greater than (>) symbol), which some found confusing. The new proposal is an ellipsis [...] icon, to indicate the idea that more info is available, but omitted in the abbreviated list view. This works nicely within the [wiki.laptop.org/go/Designs/Journal new Journal designs], since the icons will occasionally appear within a string of icon-annotated text. All present agreed the latter was a better direction. This change could make 8.2.<br />
<br />
'''Access Point''': Recent experience reports have indicated that the removal of an identifier of the connected AP is frustrating. The proposal discussed is shown [http://interdimensionmedia.com/scratch/devices.png], which wraps the former AP icon (the circle) in "parenthesis" (meant to indicate radio signal). This retains the primitive circular shape of the current access points, but illustrates which is connected in a way which alludes to the wireless activity LED. The point was discussed that the other LED is actually more semantically correct, but not as suitable as an icon.<br />
<br />
Additionally, these [http://wiki.laptop.org/go/Image:School_server_and_ap.png alternate designs] were proposed, using antennae to make the purpose of the icons clearer. We may wish to elicit feedback about these alternatives from teachers and kids to see which convey the notion of wireless connectivity the best. The triangle proposed here was used once, and subsequently removed due to some distaste for the shape in this context, but it may still convey the idea better with the antenna. This change is strongly desired for 8.2.<br />
<br />
<br />
=== Sunday March 1, 2009 - 15.00 (UTC) ===<br />
<br />
Logs: [DesignTeam/Meetings/09.03.01]<br />
<br />
[[Category:DevelopmentTeam]]<br />
[[Category:Meetings]]</div>Ebenhttps://wiki.sugarlabs.org/index.php?title=Design_Team/Meetings/2009-03-01&diff=20182Design Team/Meetings/2009-03-012009-03-01T16:39:40Z<p>Eben: New page: [10:02am] eben: Hello everyone. [10:02am] garycmartin: eben: Hi [10:03am] walterbender: garycmartin: I mean that by default, TA starts on the Project toolbar, where mostly you stay... [10:...</p>
<hr />
<div>[10:02am] eben: Hello everyone.<br />
[10:02am] garycmartin: eben: Hi<br />
[10:03am] walterbender: garycmartin: I mean that by default, TA starts on the Project toolbar, where mostly you stay...<br />
[10:04am] walterbender: garycmartin: Browse starts on the Browse toolbar...<br />
[10:04am] tomeu: eben: hi!<br />
[10:04am] tomeu: and hi, FGrose<br />
[10:04am] walterbender: eben: good morning<br />
[10:04am] FGrose: Hi<br />
[10:04am] garycmartin: walterbender: understood.<br />
[10:04am] • walterbender leaving in 10 minutes to pick my daughter up at the airport <br />
[10:04am] eben: So, I'm a little confused. EST is UTC-5, right?<br />
[10:05am] walterbender: eben: yes... we thought the meeting started at 8am EST<br />
[10:05am] eben: But Christian sent mail saying that the design meeting was at 8am then....<br />
[10:05am] tomeu: garycmartin: what do you think about the new toolbar proposal from eben?<br />
[10:05am] walterbender: eben: we've been hanging out, talking.<br />
[10:05am] eben: I think he meant it to be 10, as that was the time he last discussed with me.<br />
[10:05am] tomeu: eben: we have solved all the design issues in your absence <br />
[10:05am] eben: And he also informed me a little bit ago that he'd be about 10 minutes late.<br />
[10:05am] walterbender: eben: yes. I confirmed that with him this morning.<br />
[10:05am] eben: tomeu: fantastic!<br />
[10:06am] tomeu: that means killing X and using ncurses<br />
[10:06am] eben: I'll just go make brunch then. <br />
[10:06am] walterbender: eben: we had mostly been talking about the website... saving the 0.86 discussion for the group.<br />
[10:06am] eben: walterbender: OK.<br />
[10:06am] garycmartin: tomeu: I like it, lot's of atrwork challenges, but it's better that utility than we have now. ... But needs the Stop button all the time at top <br />
[10:07am] tomeu: garycmartin: one way to subvert eben's decisions is to make a mistake and let a "bug" slip into the implementation<br />
[10:07am] garycmartin: tomeu: ncurses, cool a decent UI at last ;-b<br />
[10:08am] eben: tomeu: <br />
[10:08am] tomeu: garycmartin: if he really cares, he'll fix it himself, but that doesn't happen 100% of the cases <br />
[10:09am] garycmartin: tomeu: I like the way you think <br />
[10:09am] tomeu: sneaky, yeah<br />
[10:11am] eben: So, hopefully Christian will be here shortly and we can discuss some designs. We both wanted to get re-aquainted with the state of things, and work out a preliminary roadmap for the next release.<br />
[10:12am] tomeu: ok<br />
[10:13am] walterbender: eben: I think the 0.84 changes are great!!! a huge boost to usability<br />
[10:13am] walterbender: especially the resume functionality !!<br />
[10:13am] eben: walterbender: Excellent. I only have cursory knowledge of them. <br />
[10:14am] eben: walterbender: I'm glad people are finding that a good change. I'm still a little worried that people won't find how to start new activities, though. How do you find it to be?<br />
[10:14am] walterbender: eben: they eliminate about 5 steps and eliminate most of the Journal spam...<br />
[10:14am] walterbender: the Journal is much more useful now.<br />
[10:15am] eben: walterbender: awesome<br />
[10:15am] garycmartin: walterbender: I just have cjb's latest F11 build on my XO, so I've just caught up with the Sugar changes over the last ~3 weeks. Looking great.<br />
[10:16am] cms: good morning--sorry i'm late<br />
[10:16am] garycmartin: I love that the palettes now show the 'Start' (New in next cycle) item as a white outline activity icon.<br />
[10:16am] tomeu: walterbender: we didn't got to label the palette item "Start new" instead of "Start" because of the string freeze, but if you think it's very important, we can ask unmadindu if he thinks we can get a string freeze<br />
[10:16am] tomeu: ooops, that was for eben<br />
[10:17am] tomeu: hi cms!<br />
[10:17am] cms: hi tomeu<br />
[10:17am] cms: what are we discussing?<br />
[10:17am] eben: tomeu: Oh, do we have menu sections!?<br />
[10:18am] eben: (labels for them, that is)<br />
[10:18am] garycmartin: cms: hi<br />
[10:18am] tomeu: eben: do we?<br />
[10:18am] cms: hi gary<br />
[10:18am] tomeu: cms: starting new activity instances from the palette in the home view<br />
[10:19am] eben: tomeu: I don't know. I'm asking, since that's where the "resume recent" and "start new" were supposed to be.<br />
[10:19am] cms: tomeu: ah, i saw most of that was already implemented, correct?<br />
[10:19am] tomeu: eben, cms: we don't have labelled sections in palettes yet <br />
[10:20am] tomeu: so it's not 100% as the design says<br />
[10:20am] eben: cms: UTC 15:00 = EST 10:00 <br />
[10:20am] eben: tomeu: Oh, so where's the labels? We don't have any?<br />
[10:20am] cms: heh<br />
[10:20am] cms: can we actually back up for a second and talk about the development schedule?<br />
[10:21am] cms: is there a date set for the new release?<br />
[10:21am] tomeu: eben: no section labels, no<br />
[10:21am] tomeu: eben: but we do have separators, at leasr<br />
[10:21am] tomeu: t5<br />
[10:21am] tomeu: argh<br />
[10:22am] tomeu: cms: http://sugarlabs.org/go/DevelopmentTeam/Release/Roadmap<br />
[10:22am] eben: tomeu: sure, but that doesn't make the reason for the separation clear. But OK. We need to make those then.<br />
[10:22am] tomeu: eben: sure, I agree those labels are important<br />
[10:22am] cms: tomeu: thanks!<br />
[10:23am] eben: tomeu: I think we're more interested in the 0.86 roadmap.<br />
[10:23am] cms: eben: yes, that would be helpfu<br />
[10:23am] tomeu: oooh<br />
[10:23am] tomeu: no roadmap yet<br />
[10:23am] eben: To get an idea of the timeline we want to plan on coming up.<br />
[10:23am] cms: since we are days away from 0.84<br />
[10:24am] tomeu: but we would like to release again in 6 months, aprox<br />
[10:24am] eben: OK, well, what's the approx. number of months between releases, usually?<br />
[10:24am] cms: that's good to know<br />
[10:24am] eben: 6, OK, great.<br />
[10:24am] cms: eben, should we recap all of the main features we want to address in that timeframe?<br />
[10:25am] tomeu: nice<br />
[10:25am] cms: some of these may already have been implemented<br />
[10:25am] eben: cms: I think we should, yeah. We should also refine those added in 0.84.<br />
[10:25am] tomeu: what I have started to do regarding 0.86 is try to get contacts that can proxy feedback from places where sugar is being used<br />
[10:25am] eben: tomeu: excellent/<br />
[10:25am] tomeu: I haven't had much success yet, but want to scale up this efforts in th enext days<br />
[10:25am] cms: tomeu: that's great, that feedback will be invaluable<br />
[10:26am] cms: when are kids given the opportunity to give feedback?<br />
[10:26am] tomeu: cms: they can always enter a ticket or send email <br />
[10:26am] cms: great<br />
[10:27am] eben: OK, so should we just list the items we think are important (without any discussion, just so we get a full list) and then go from there?<br />
[10:27am] tomeu: cms: I guess we need to set up some kind of process so direct contributions get translated, summarized and categorized<br />
[10:27am] cms: eben: yes, let's do that<br />
[10:27am] eben: tomeu: yeah, that would be great.<br />
[10:27am] cms: so, one of the most important features was mesh chat<br />
[10:27am] tomeu: so teachers and parents would ask kids, and someone would summarize that<br />
[10:27am] tomeu: something like that<br />
[10:27am] cms: tomeu: yes it makes sense that it be facilitated<br />
[10:28am] eben: • Make Groups view work properly (more like the neighborhood)<br />
[10:28am] eben: • Add list (or list-like) views to all zoom levels, for scalability & keyboard navigability<br />
[10:29am] eben: • Sweet new toolbars<br />
[10:30am] eben: • something controversial: remove ring view/favorites; use grid and/or freeform view<br />
[10:30am] tomeu: * labelled palette sections<br />
[10:31am] cms: let's figure out which of these features we can address, and if we can't do all of them, we probably need to prioritize...<br />
[10:32am] eben: I'm sure there are many smaller ones, but I think these are the biggest on my mind.<br />
[10:32am] cms: most important in my opinion are mesh chat, groups view, home view<br />
[10:32am] eben: cms: You think we have a pretty comprehensive list of the big ones here?<br />
[10:32am] garycmartin: - Jouranal grid view?<br />
[10:32am] cms: eben: yes, that sums it up i believe<br />
[10:32am] eben: garycmartin: Right....the "new Journal" is another really big change.<br />
[10:32am] cms: garycmartin: good call<br />
[10:33am] tomeu: what about the action/object separation in the journal?<br />
[10:33am] eben: I might actually recommend pushing that off one more release so we can get the rest of the UI (zoom levels) working perfectly first.<br />
[10:33am] eben: (Not that I don't *really* want to make that change...)<br />
[10:33am] cms: tomeu: the new journal is an important area to focus on, but i agree with eben that we should try to resolve the other areas first<br />
[10:34am] eben: We might talk about some pieces of the Journal that could be improved though...<br />
[10:34am] tomeu: what means "remove ring view/favorites; use grid and/or freeform view"?<br />
[10:34am] cms: the journal works well enough in its current state for another release, but the other areas are more pressing<br />
[10:34am] eben: We could still use the sort-bar, and mutliple selection, etc.<br />
[10:34am] eben: These can happen without a transplant.<br />
[10:34am] tomeu: I'm ready to work on the weekends on the action/object separation <br />
[10:34am] eben: OK, well, cms, maybe we should start with Home?<br />
[10:34am] cms: tomeu: the action/object separation is ultimately an important change...<br />
[10:35am] cms: eben: ok<br />
[10:35am] eben: cms: I think that might be the hardest to get consensus around.<br />
[10:35am] eben: So, Christian and I have been doing a lot of thinking...<br />
[10:35am] tomeu: cms: apart from other obvious benefits, if we have an object view in the journal, probably with hierarchy, means we can interface with the filesystem as some people want<br />
[10:35am] cms: now that we have had some time to experience the new home view, there are some modifications we think would make it more usable<br />
[10:36am] eben: And we've both independently come to the conclusion that the ring doesn't really serve the purpose we had intended<br />
[10:36am] cms: the first observation is that people don't use the favorites<br />
[10:36am] eben: Mostly because people either don't know about, or don't make use of favorites to an advantage.<br />
[10:36am] cms: this comes as a bit of a surprise, but it was an interesting finding<br />
[10:37am] tomeu: that means that people don't use the ring, or don't use the starring thing?<br />
[10:37am] eben: And we think that this distinction is likely more confusing in the end than a view which plainly and simply shows all installed activities.<br />
[10:37am] cms: because people aren't using favorites, they tend to show *everything* in the main, ring view<br />
[10:37am] eben: tomeu: It means that the ring doesn't really "work", since it's really only designed to hold 10-20 activities.<br />
[10:37am] tomeu: ok<br />
[10:37am] cms: in other words, they aren't *de-starring* items to free up the ring<br />
[10:37am] eben: The ring isn't serving their use cases well.<br />
[10:37am] tomeu: I see<br />
[10:38am] cms: has anyone else observed this?<br />
[10:38am] eben: So, I think cms and I have slightly different interpretations of what this means, but it involves some combination of freeform, grid, and list views.<br />
[10:38am] garycmartin: cms: not here. Ring view is certainly my fav layout.<br />
[10:38am] tomeu: I have seen how some sugar on a stick images shipped with lots of activities as favorite, and that made the ring hard to use<br />
[10:39am] tomeu: but if there aren't many activities, the ring works quite well<br />
[10:39am] eben: With the ultimate goal to be to have 2 views (just like all zoom levels will have!), where both views show *all*activities, and one of those views includes text up front.<br />
[10:39am] tomeu: text up front?<br />
[10:39am] cms: garycmartin: yes, to tomeu's point--the ring looks great when there are a ltd number of activities represented<br />
[10:40am] eben: tomeu: Sure, but a) we don't think that's common, and b) we think that favorites are more trouble than they're worth to people. Added complexity.<br />
[10:40am] cms: but when you exceed a certain number, it tends to become unmanageable<br />
[10:40am] tomeu: looks great, and is also easy to click on the wanted activity<br />
[10:40am] eben: text up front: show text without need for a palette<br />
[10:40am] tomeu: eben: may be, yeah<br />
[10:41am] garycmartin: eben: so how will a teacher/parent customise the view - just start deleting stuff??<br />
[10:41am] cms: the proposal is to essentially remove the favorites altogether--<br />
[10:41am] tomeu: eben, cms: btw, which observations have you made?<br />
[10:41am] cms: --and have a single view for all activities<br />
[10:41am] eben: garycmartin: or organizing stuff. <br />
[10:41am] cms: garycmartin: the model could be much simpler than it currently is<br />
[10:41am] cms: meaning a single view for all activities<br />
[10:42am] cms: now, maybe we need to think more about what that single view could look like,<br />
[10:42am] garycmartin: eben: Do what Apple did with their stacks. Nice ring view if under N items, then auto switch to a grid (please not raandom) once exceeded.<br />
[10:42am] cms: but we think that the freeform view satisfies the need for organizing activities in a single space<br />
[10:43am] eben: garycmartin: That type of solution honestly doesn't seem valid to me. (even in Apple's case)<br />
[10:43am] tomeu: my personal, user experience is that freeform views don't work well<br />
[10:43am] cms: tomeu: i'm not sure--<br />
[10:43am] tomeu: maybe I should post a screenshot of my desktop for you to see<br />
[10:43am] eben: I feel like the stack was just eye-candy, and it didn't scale, so they resorted to a grid view for large quantities.<br />
[10:43am] cms: i was reading an article recently on interaction design<br />
[10:44am] cms: (eben, i think you had bookmarked it)<br />
[10:44am] cms: on essentially "unnecessary" affordances<br />
[10:44am] tomeu: maybe we are facing two very different user groups? maybe we need to support two very different interaction models?<br />
[10:45am] cms: the freeform view gives you the ability to organize activities spatially, which may not have a clear and immediate purpose (other than making small clusters/groupings),<br />
[10:45am] cms: but the sheer ability to move objects around the space and personalize it in that way is satisfying on its own<br />
[10:45am] eben: cms: Also, we want search in Home to work well....right now its disabled.<br />
[10:45am] tomeu: I don't know why, but I feel very annoying having to move the icons around in my dekstop<br />
[10:45am] tomeu: so much that I don't do it<br />
[10:45am] eben: A funny thing about it before was that not all of the activities were in the view...<br />
[10:46am] eben: so, do you pull them into the view? or not search on them?<br />
[10:46am] cms: mean to say, there are interactions that functionally may not be necessary, but are satisfying to people<br />
[10:46am] garycmartin: cms: so can we at least keep a 'snap to ring' 'snap to spiral' if we want?<br />
[10:46am] cms: tomeu: *some* people <br />
[10:46am] eben: Now, everything will be available.<br />
[10:46am] tomeu: perhaps if we had a good search facility in home, we would be already supporting an interaction mode closer to me<br />
[10:46am] eben: garycmartin: I think "snap to grid" should be a default, personally. cms disagrees. <br />
[10:46am] tomeu: cms: yeah, I guess that's true<br />
[10:47am] eben: garycmartin: But I don't see a reason that snap-to-snything couldn't continue to be a hack, as it has been...<br />
[10:47am] cms: garycmartin: we should think about how to best implement this--there may be a setting in the preferences that controls snap to grid<br />
[10:47am] cms: eben: i don't disagree<br />
[10:47am] cms: eben: actually, you're right i don't think it should be the default, but i *do* think there should be the option<br />
[10:47am] eben: I just think Sugar, up front, should be presenting an extremely simple and consistent model for Home. (and all zoom levels)<br />
[10:48am] cms: eben: i agree.<br />
[10:48am] cms: simplicity is really key, here<br />
[10:48am] eben: And, let me just put two flavors of this out there, briefly.<br />
[10:48am] cms: and the notion of a personal space that you can customize<br />
[10:49am] eben: As I mentioned, there are kind of three layout options: freeform, grid, and list.<br />
[10:49am] tomeu: I agree as well with that goal<br />
[10:49am] eben: There are a few ways to combine these.<br />
[10:49am] garycmartin: eben: the ring view is like neighbourhood group sharing, grid or random looses that.<br />
[10:49am] eben: 1) freeform (with snap-to-grid option) and list<br />
[10:49am] eben: 2) freeform and grid (*instead* of list)<br />
[10:50am] garycmartin: eben: neighbourhood (graphic) view will have to be limited (gadget/screen space) list view would show all. So that's like home fav's just now...<br />
[10:50am] cms: garycmartin: that was the initial thought, yes. but freeform also has a close resemblence to neighborhood<br />
[10:50am] eben: 3) freeform or grid, and list<br />
[10:50am] eben: garycmartin: Kind of, that's true.<br />
[10:51am] eben: Although in Home, there's no implication that the things are just "out of sight"...they're literally sectioned off in a different space.<br />
[10:51am] cms: garycmartin: but ultimately this is to address function not form<br />
[10:51am] caroline: hi<br />
[10:51am] cms: hi caroline<br />
[10:51am] eben: I think this model works well in the other views, since we're still talking about a single plane and items within it, either in view or not.<br />
[10:52am] eben: But yes, I agree with cms....this is primarily a functional decision (everyone knows that both of us strongly preferred the ring, to begin with)<br />
[10:52am] eben: But over time, we've come to see that it's not really the best solution in terms of model and interaction.<br />
[10:53am] eben: It was a miracle, really, that we sat down over lunch not too long ago and both brought up this same point, independently.<br />
[10:53am] tomeu: wonder who has actually used sugar 0.82 with kids and could give feedback about it<br />
[10:53am] cms: eben: of the three options, i find myself leaning towards (1), for simplicity mostly<br />
[10:54am] cms: tomeu: that is a good point, actually--some feedback here would help us all make a decision<br />
[10:54am] eben: Right, I think I put them in order of probability, actually.<br />
[10:54am] tomeu: caroline: how close are you from giving this kind of feedback?<br />
[10:54am] cms: tomeu: the thing that cause me to begin questioning the ring was looking at people's screenshots of their home views<br />
[10:54am] caroline: Sorry, I'm still lost we are talking about how to display activities in the home view?<br />
[10:55am] cms: the home views i saw were always fully populated with activities, and the ring no longer seemed to work as intended<br />
[10:55am] tomeu: caroline: yup, and secondarily, the other zoom views<br />
[10:55am] caroline: I think we are about a month from being able to have a group of kids use Sugar and us look over thier sholder and ask questions.<br />
[10:55am] eben: I think one of the reasons that the "small number of favorites" failed is explicitly because the model of "activities" is working so well! So it's a win, there. <br />
[10:55am] cms: eben: yes a nice way to view it... <br />
[10:55am] caroline: *my* imagnation of how I would like it to work is day 1 kid gets ring with a few things picked out by the teacher.<br />
[10:55am] eben: They are small and self-contained, and there are lots of them, each good at its own little thing.<br />
[10:56am] caroline: the teacher can via the web add things to all the kids favorites<br />
[10:56am] cms: eben: essentially, that is what is going on. people don't want to have to choose between their favorite activities, they want them all to be displayed<br />
[10:56am] caroline: kids talk to each other and learn how to access and add favorites and add addons.<br />
[10:56am] eben: I even find myself with an overstuffed ring, even though I only have a dozen apps in my OSX Dock<br />
[10:56am] cms: caroline: you raise an interesting point<br />
[10:56am] cms: caroline: but i wonder if that isn't something else altogether<br />
[10:57am] cms: i.e., perhaps there is a different home view that teachers can create for their students, a kind of shared collaboration space<br />
[10:57am] caroline: I think there is a big difference in use case between evaluating Sugar and introdcuting ti to a class. And using it a year into your schooling.<br />
[10:57am] caroline: cms, we should be doing some of that in Moodle.<br />
[10:57am] tomeu: yeah, long term feedback would be better, but if we change the UI every release, we won't get it ever <br />
[10:58am] cms: tomeu: agreed...<br />
[10:58am] eben: I recently shown Sugar to some new individuals myself (not kids, unfortunately; but actually some folks with a little interaction design background) and they found the favorites idea to be a little awkward..didn't understand it without explanation.<br />
[10:58am] caroline: because remember the idea of "class" is not that stable. There is my reading group, my math group, my afterschool class.<br />
[10:58am] garycmartin: cms: eben: I'm really not feeling the love here. Give'em a grid, it's easier; and if they don't like it, make it random and leave them to spend 20min trying to drag-n-drop, dodging pop-up menus and accidental launches... Yeuch<br />
[10:58am] caroline: With "no ceiling" everything will not be discoverable by everyone without explaination. But our tartget is schools, with kids helpign each other.<br />
[10:59am] caroline: My goal is to reinforce the notion that exploring will get you somehting interesting.<br />
[10:59am] eben: garycmartin: they shouldn't pop up when dragging. <br />
[10:59am] cms: caroline: a while ago, eben and i discussed a bulletin board concept that essentially gave you the flexibility to create these shared spaces, in conjunction with groups<br />
[10:59am] caroline: and that watching other kids will get you something interesting.<br />
[10:59am] caroline: cms, just saw that email haven't followed the link yet.<br />
[10:59am] eben: caroline: Sure, but I don't think it's good to let that be an excuse for having a confusing interface. <br />
[10:59am] caroline: eben agreed<br />
[11:00am] eben: caroline: I agree, though, but I think there are other, better things we can let them explore and learn.<br />
[11:00am] garycmartin: Currentyl in Sugar it's so nice not to have to constantly clean up the desktop like I have to else where.<br />
[11:00am] eben: One of them, hopefully, will be the addition of proper "groups"<br />
[11:00am] caroline: we have a tension between initial very simple views controled by the teacher, and complex rich student controled views of experienced older kids.<br />
[11:01am] cms: garycmartin: well, i think it's still a different model from your typical desktop, due to activities always remaining in view. there's no need to clean up, but it's nice to be able to reposition if you like<br />
[11:01am] caroline: I'm thinking of the 3 year olds I saw not even struggle with windows they just gave up till an adult came over.<br />
[11:01am] caroline: that is exactly what I don't want.<br />
[11:01am] cms: garycmartin: it's more like taking the ring, and spreading it out over the entire screen<br />
[11:01am] caroline: what is the topic on the email with the link to the bulletin boards?<br />
[11:02am] cms: caroline: actually, this was discussed many months ago<br />
[11:02am] caroline: you guys need to change subjects more in these long threads!<br />
[11:02am] cms: i can try to find it--eben, do you know when it was discussed?<br />
[11:02am] eben: I'm not sure bulletin-boards relate to the current discussion, though.<br />
[11:02am] cms: they do<br />
[11:02am] eben: how?<br />
[11:02am] tomeu: long threads are really evil, yeah<br />
[11:03am] cms: in terms of what caroline was mentioning--teacher-created collaboration spaces<br />
[11:03am] eben: Oh oh....sure. Well, definitely, that's exactly what they are. <br />
[11:03am] tomeu: bulletin boards are the solution to all the problems we avoid <br />
[11:03am] cms: it would be good to have the long-term vision in the back of our minds as we set out to redesign home<br />
[11:03am] eben: But they're just not a part of Home But we should find that for her.<br />
[11:03am] cms: yes, i'll see if i can dig it up again<br />
[11:04am] caroline: http://sugarlabs.org/go/DesignTeam/Human_Interface_Guidelines/The_Laptop_Experience/Bulletin_Boards this?<br />
[11:04am] cms: caroline: i think that will address what you were referring to<br />
[11:04am] eben: caroline: Kind of...that's a really old mockup/form<br />
[11:04am] caroline: anyway, we are gettig off topic I think, eben can you restate what you are looking for?<br />
[11:05am] eben: caroline: A way to think about the current bulletin board idea is that it's an activity (which can be shared), which serves like a shared desktop for activities, objects, notes, etc.<br />
[11:05am] cms: eben: thanks, that sums it up nicely<br />
[11:05am] eben: caroline: They can be created around specific topics and serve as a literal "bulletin-board", or more like a project starter kit for a given asignment, etc.<br />
[11:06am] caroline: cool<br />
[11:06am] eben: caroline: We should talk more about that sometime, and get your feedback. I think you'll like the thoughts, so far.<br />
[11:07am] caroline: ok I don;t want to get you off topic<br />
[11:07am] eben: So, how can we sum up Home, for now?<br />
[11:07am] eben: Should we give this a week to settle and discuss again next week?<br />
[11:07am] cms: yes, let's have the thought settle for a while, then pick it up again and see how it resonates<br />
[11:08am] eben: Sounds good.<br />
[11:08am] tomeu: eben: I think we should work hard in involving more people in this discussions<br />
[11:08am] cms: tomeu: what is the best way to do that?<br />
[11:08am] garycmartin: tomeu: yes, I noticed no one started the meeting bot to capture all this...<br />
[11:08am] eben: garycmartin: Oh, that's my fault.<br />
[11:08am] • eben is sorry.<br />
[11:08am] tomeu: cms: that's what I'm trying to discover by appointing contact points in each geog. area where sugar is used<br />
[11:09am] tomeu: cms: will keep working on that, then we'll have some people to ask for feedback<br />
[11:09am] eben: tomeu: Yeah, good point. Having a few people here with outside insight would be useful; they don't have to be directly interested in the design itself.<br />
[11:09am] tomeu: 0.82 is not widely used, though<br />
[11:09am] eben: tomeu: also a good point. <br />
[11:10am] caroline: eben you are local to me right? I hope to shortly have a computer lab somewhere and a supply of kids, think about what you'd like to observe.<br />
[11:10am] cms: should we move on to mesh chat? i think that is one of the most compelling new features<br />
[11:10am] eben: OK. Well, it's been an hour. Do folks want to wrap up now, then; or take on a few other zoom-level issues?<br />
[11:10am] eben: caroline: Yeah...I'm in Providence these days.<br />
[11:10am] tomeu: eben: as we don't have nobody paying developers, maybe we need to find a way so that developers that contribute their own time feel that the stuff they do is in connection with the needs of actual users<br />
[11:11am] tomeu: I'm happy to move to other issues<br />
[11:12am] cms: tomeu: yes, before we make any major changes we should make sure that we have some validation<br />
[11:12am] eben: The remaining issues in the zoom levels are 1) groups is "broken" 2) list views at all levels 3) neighborhood search with gadget 4) chat<br />
[11:12am] tomeu: btw, not sure I have pasted this link before: http://sugarlabs.org/go/DeploymentTeam/Places<br />
[11:12am] garycmartin: Happy to move on (still reeling from home change suggestion)<br />
[11:12am] tomeu: I think caroline had some ideas about the groups view<br />
[11:12am] eben: Then there are also 5) activity search in Home (related to previous discussion) and 6) addition of groups (finally!)<br />
[11:13am] tomeu: activity groups or contact groups?<br />
[11:13am] • erikos sad to have missed the meeting<br />
[11:14am] caroline: yeah groups is broken<br />
[11:14am] eben: tomeu: groups, as in collections of people (for the purpose of sharing, etc.)<br />
[11:14am] tomeu: erikos: we're just starting <br />
[11:14am] tomeu: ok<br />
[11:14am] caroline: what is groups supposed to do? Show friends? Show classmates?<br />
[11:14am] erikos: tomeu: ohh<br />
[11:14am] eben: But, we can "fix" the groups view without adding proper groups support.<br />
[11:14am] eben: Sure, let me try to clarify the goal.<br />
[11:14am] tomeu: erikos: we have been talking one hour, but there's lot of ground to cover<br />
[11:15am] eben: Right now, we have the notion of friends.<br />
[11:15am] erikos: tomeu: absolutely - there is a lot to do for 0.86<br />
[11:15am] eben: We want to add to this the notion of groups....sets of individuals who all agree to join a group...which can then serve as sharing scope.<br />
[11:15am] eben: (eg. "share this with my [third grade class] group, or my [chess club] group")<br />
[11:16am] tomeu: caroline: were you in the presentation that cms and eben did in the sugarcamp?<br />
[11:16am] eben: The Groups view is supposed to be the space between Home and Neighborhood, where you interact with these people you're closer to....friends...and other group members.<br />
[11:17am] caroline: ok, so once we have integration between Moodle and eJabber we could start to do some more interesting things.<br />
[11:17am] eben: The view itself should work almost identically to the neighborhood view...in fact...it's basically the same, except we "zoom in" a little bit to show people we know, instead of everyone.<br />
[11:17am] eben: The same rules for showing people clustered around activities, etc. all apply there (should, anyway).<br />
[11:17am] caroline: So once we are connected to Moodle we now know who is online and shares a group with you.<br />
[11:18am] eben: caroline: Yes, there has been some discussion around the idea of linking Sugar groups with Moodle.<br />
[11:18am] caroline: My Moodle classes could include, My class, my grade, my afterschool program, plus I have maybe Sugar frineds who might be in other grades including older and younger sybling.<br />
[11:18am] eben: I'd like them to be possible without Moodle, but maybe that's too hard a challenge. Not sure yet.<br />
[11:18am] eben: caroline: Because I'd really like them to be created ad-hoc. "You four, form a group for the rest of class and work on X"<br />
[11:19am] caroline: I optomistically see that info being available to Sugar in the next few months. Seems quite possible to trasmit.<br />
[11:19am] caroline: yeah, that is a harder problem.<br />
[11:19am] eben: Anyway, at least the notion of what groups should *do* is pretty clear.<br />
[11:19am] caroline: but if we solve the general problem of group view conveys info about groups from Moodle it becomes Moodles problem.<br />
[11:19am] tomeu: the biggest problem with groups is how to make sure that in all laptops in a class, the class group contain the same people<br />
[11:19am] eben: The two big advantages are 1) there will be a filter on the Groups view, so you can look at a particular group at any given moment.<br />
[11:20am] eben: and 2) You can also share with a group, instead of just the neighborhood<br />
[11:21am] eben: tomeu: Well, the trick is really in namespace collisions....<br />
[11:21am] eben: I think group membership isn't very hard....though like anything, it could take time to propagate the membership changes.<br />
[11:21am] eben: I don't think that's a problem though.<br />
[11:22am] tomeu: well, if a group composition changes without intervention from the user, maybe that user will make an operation on a set of people that aren't what he thinks?<br />
[11:22am] garycmartin: eben: isn't 'group' better as local thing? I make a 'group' object and add 5 of my friends to it. I can now share to that group.<br />
[11:23am] eben: The only other point to make about Groups view, in how it differs from Neighborhood, is non-friends/non-group members who are shown there because they're in an activity which does contain a friend/group member are rendered as outlines.<br />
[11:23am] garycmartin: eben: the group isn't 'publised' for others to auto join (unless I share the 'group' object)<br />
[11:23am] eben: garycmartin: No, we explicitly want this to be a shared notion. A collaboration.<br />
[11:24am] garycmartin: eben: it is, you create a group, and then if you want share it.<br />
[11:25am] eben: garycmartin: Well, you share activities *with* a group<br />
[11:25am] cms: hi everyone--i'm going to have to leave, but looking forward to continuing this next week<br />
[11:25am] garycmartin: eben: the 'group' object could come from moodle, someone sharing, or yourself.<br />
[11:25am] eben: But what does that mean to share it?<br />
[11:25am] tomeu: cms: ok, we can move some of this discussion to the mailing list<br />
[11:25am] caroline: I agree at least some of the time the group can be a Moodle Group<br />
[11:25am] garycmartin: cms: thanks for you time.<br />
[11:25am] eben: A group is shared, implicitly, with its members.<br />
[11:25am] caroline: I think you share with a Group, you don't share a Group.<br />
[11:26am] eben: caroline: right, that's the idea.<br />
[11:26am] cms: thanks--see you later<br />
[11:26am] eben: A group isn't an "object"....it's a collection of individuals who agree to share things amongst themselves.<br />
[11:26am] garycmartin: eben: if a group is shared implicitley, then there's a whole bunch of network chatter and sync going on, invites appearing and other such distractions.<br />
[11:27am] eben: garycmartin: nah, not really.<br />
[11:27am] eben: I mean, it would work something like this...<br />
[11:27am] caroline: so the conclusion I am coming to is Group view is broken cause the connection to Moodle is fundmentally still broken.<br />
[11:27am] eben: I cdecide to make a group, and pick the people I want to join. Yes, there is some chatter, as each would get an invite to join the group, and either accept or decline.<br />
[11:27am] tomeu: caroline: but don't we want groups to work even without moodle?<br />
[11:27am] eben: But that chatter is limited to the members, and once and done.<br />
[11:28am] caroline: tomeu, for me. No not really.<br />
[11:28am] eben: Then, anytime someone in the group shares an activity with the group, each group member gets an invitation to join.<br />
[11:28am] caroline: but I know that I am more into the server then average person.<br />
[11:28am] eben: But again, only group members get that, so it's not lots of broadcast.<br />
[11:28am] tomeu: oh, ok<br />
[11:29am] eben: tomeu: yes, it's a goal of mine to have this work without a server....but that's a technical discussion to be had. Maybe we should start with server, and then later grow the offline support?<br />
[11:30am] caroline: I need to go eat sme breakfast back in a bit.<br />
[11:30am] eben: I need to go, myself, actually.<br />
[11:30am] tomeu: eben: yeah, that's a possibility<br />
[11:31am] tomeu: eben: ok, how we move forward with 0.86? perhaps you can email a link to the log with some minutes to the ml?<br />
[11:31am] eben: Perhaps we should come back to this anyway, since adding "groups" is not for next release....but making "Groups view" work naturally, so it's ready for future "groups" support is.<br />
[11:31am] tomeu: that may get more people interested<br />
[11:31am] eben: tomeu: You mean copy/paste the log somewhere?<br />
[11:32am] eben: Next time I'll remember to use the bot...<br />
[11:33am] garycmartin: eben: Currently Sugar can share with 1 buddy, or share with all buddy, the bit it's really missing is, share with bob & sue (or N other named buddies). Share with N users seems the feture to fill (if you give N a name it's a nice group).<br />
[11:33am] tomeu: eben: to the wiki, yeah, like we do in the dev team meeting: http://sugarlabs.org/go/DevelopmentTeam/Meetings#Meetings<br />
[11:33am] eben: garycmartin: right! But the idea here is that all groups are named, and that Bob and Sue would need to agree to be members of that group.<br />
[11:34am] eben: tomeu: But you usually link to the logs which are kept by the bot.<br />
[11:34am] eben: I guess copy/paste directly into the wiki could also work...<br />
[11:34am] eben: A little ugly, probably.<br />
[11:34am] tomeu: eben: before we had the bot, we pasted to the wiki or linked to a file somewhere else<br />
[11:34am] eben: ok<br />
[11:34am] tomeu: a bit ugly, but well</div>Ebenhttps://wiki.sugarlabs.org/index.php?title=Template:Definition_table&diff=13470Template:Definition table2008-12-17T15:42:42Z<p>Eben: New page: <includeonly>{| {{#if:{{{1|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{1}}} {{!}}{{!}} {{!}} style="vertical-align:top;" {{!}} {{{2}}} {{!}}-}} {{#i...</p>
<hr />
<div><includeonly>{|<br />
{{#if:{{{1|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{1}}} {{!}}{{!}}<br />
{{!}} style="vertical-align:top;" {{!}} {{{2}}}<br />
{{!}}-}}<br />
{{#if:{{{3|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{3}}} {{!}}{{!}}<br />
{{!}} style="vertical-align:top;" {{!}} {{{4}}}<br />
{{!}}-}}<br />
{{#if:{{{5|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{5}}} {{!}}{{!}}<br />
{{!}} style="vertical-align:top;" {{!}} {{{6}}}<br />
{{!}}-}}<br />
{{#if:{{{7|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{7}}} {{!}}{{!}} <br />
{{!}} style="vertical-align:top;" {{!}} {{{8}}} <br />
{{!}}-}}<br />
{{#if:{{{9|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{9}}} {{!}}{{!}} <br />
{{!}} style="vertical-align:top;" {{!}} {{{10}}} <br />
{{!}}-}}<br />
{{#if:{{{11|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{11}}} {{!}}{{!}} <br />
{{!}} style="vertical-align:top;" {{!}} {{{12}}} <br />
{{!}}-}}<br />
{{#if:{{{13|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{13}}} {{!}}{{!}} <br />
{{!}} style="vertical-align:top;" {{!}} {{{14}}} <br />
{{!}}-}}<br />
{{#if:{{{15|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{15}}} {{!}}{{!}} <br />
{{!}} style="vertical-align:top;" {{!}} {{{16}}} <br />
{{!}}-}}<br />
{{#if:{{{17|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{17}}} {{!}}{{!}} <br />
{{!}} style="vertical-align:top;" {{!}} {{{18}}} <br />
{{!}}-}}<br />
{{#if:{{{19|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{19}}} {{!}}{{!}} <br />
{{!}} style="vertical-align:top;" {{!}} {{{20}}} <br />
{{!}}-}}<br />
{{#if:{{{21|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{21}}} {{!}}{{!}}<br />
{{!}} style="vertical-align:top;" {{!}} {{{22}}}<br />
{{!}}-}}<br />
{{#if:{{{23|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{23}}} {{!}}{{!}}<br />
{{!}} style="vertical-align:top;" {{!}} {{{24}}}<br />
{{!}}-}}<br />
{{#if:{{{25|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{25}}} {{!}}{{!}}<br />
{{!}} style="vertical-align:top;" {{!}} {{{26}}}<br />
{{!}}-}}<br />
{{#if:{{{27|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{27}}} {{!}}{{!}} <br />
{{!}} style="vertical-align:top;" {{!}} {{{28}}} <br />
{{!}}-}}<br />
{{#if:{{{29|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{29}}} {{!}}{{!}} <br />
{{!}} style="vertical-align:top;" {{!}} {{{30}}} <br />
{{!}}-}}<br />
{{#if:{{{31|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{31}}} {{!}}{{!}}<br />
{{!}} style="vertical-align:top;" {{!}} {{{32}}}<br />
{{!}}-}}<br />
{{#if:{{{33|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{33}}} {{!}}{{!}}<br />
{{!}} style="vertical-align:top;" {{!}} {{{34}}}<br />
{{!}}-}}<br />
{{#if:{{{35|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{35}}} {{!}}{{!}}<br />
{{!}} style="vertical-align:top;" {{!}} {{{36}}}<br />
{{!}}-}}<br />
{{#if:{{{37|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{37}}} {{!}}{{!}} <br />
{{!}} style="vertical-align:top;" {{!}} {{{38}}} <br />
{{!}}-}}<br />
{{#if:{{{39|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{39}}} {{!}}{{!}} <br />
{{!}} style="vertical-align:top;" {{!}} {{{40}}} <br />
{{!}}-}}<br />
{{#if:{{{41|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{41}}} {{!}}{{!}}<br />
{{!}} style="vertical-align:top;" {{!}} {{{42}}}<br />
{{!}}-}}<br />
{{#if:{{{43|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{43}}} {{!}}{{!}}<br />
{{!}} style="vertical-align:top;" {{!}} {{{44}}}<br />
{{!}}-}}<br />
{{#if:{{{45|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{45}}} {{!}}{{!}}<br />
{{!}} style="vertical-align:top;" {{!}} {{{46}}}<br />
{{!}}-}}<br />
{{#if:{{{47|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{47}}} {{!}}{{!}} <br />
{{!}} style="vertical-align:top;" {{!}} {{{48}}} <br />
{{!}}-}}<br />
{{#if:{{{49|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{49}}} {{!}}{{!}} <br />
{{!}} style="vertical-align:top;" {{!}} {{{50}}} <br />
{{!}}-}}<br />
{{#if:{{{51|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{51}}} {{!}}{{!}}<br />
{{!}} style="vertical-align:top;" {{!}} {{{52}}}<br />
{{!}}-}}<br />
{{#if:{{{53|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{53}}} {{!}}{{!}}<br />
{{!}} style="vertical-align:top;" {{!}} {{{54}}}<br />
{{!}}-}}<br />
{{#if:{{{55|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{55}}} {{!}}{{!}}<br />
{{!}} style="vertical-align:top;" {{!}} {{{56}}}<br />
{{!}}-}}<br />
{{#if:{{{57|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{57}}} {{!}}{{!}} <br />
{{!}} style="vertical-align:top;" {{!}} {{{58}}} <br />
{{!}}-}}<br />
{{#if:{{{59|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{59}}} {{!}}{{!}} <br />
{{!}} style="vertical-align:top;" {{!}} {{{60}}} <br />
{{!}}-}}<br />
{{#if:{{{61|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{61}}} {{!}}{{!}}<br />
{{!}} style="vertical-align:top;" {{!}} {{{62}}}<br />
{{!}}-}}<br />
{{#if:{{{63|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{63}}} {{!}}{{!}}<br />
{{!}} style="vertical-align:top;" {{!}} {{{64}}}<br />
{{!}}-}}<br />
{{#if:{{{65|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{65}}} {{!}}{{!}}<br />
{{!}} style="vertical-align:top;" {{!}} {{{66}}}<br />
{{!}}-}}<br />
{{#if:{{{67|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{67}}} {{!}}{{!}} <br />
{{!}} style="vertical-align:top;" {{!}} {{{68}}} <br />
{{!}}-}}<br />
{{#if:{{{69|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{69}}} {{!}}{{!}} <br />
{{!}} style="vertical-align:top;" {{!}} {{{70}}} <br />
{{!}}-}}<br />
{{#if:{{{71|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{71}}} {{!}}{{!}}<br />
{{!}} style="vertical-align:top;" {{!}} {{{72}}}<br />
{{!}}-}}<br />
{{#if:{{{73|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{73}}} {{!}}{{!}}<br />
{{!}} style="vertical-align:top;" {{!}} {{{74}}}<br />
{{!}}-}}<br />
{{#if:{{{75|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{75}}} {{!}}{{!}}<br />
{{!}} style="vertical-align:top;" {{!}} {{{76}}}<br />
{{!}}-}}<br />
{{#if:{{{77|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{77}}} {{!}}{{!}} <br />
{{!}} style="vertical-align:top;" {{!}} {{{78}}} <br />
{{!}}-}}<br />
{{#if:{{{79|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{79}}} {{!}}{{!}} <br />
{{!}} style="vertical-align:top;" {{!}} {{{80}}} <br />
{{!}}-}}<br />
{{#if:{{{81|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{81}}} {{!}}{{!}}<br />
{{!}} style="vertical-align:top;" {{!}} {{{82}}}<br />
{{!}}-}}<br />
{{#if:{{{83|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{83}}} {{!}}{{!}}<br />
{{!}} style="vertical-align:top;" {{!}} {{{84}}}<br />
{{!}}-}}<br />
{{#if:{{{85|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{85}}} {{!}}{{!}}<br />
{{!}} style="vertical-align:top;" {{!}} {{{86}}}<br />
{{!}}-}}<br />
{{#if:{{{87|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{87}}} {{!}}{{!}} <br />
{{!}} style="vertical-align:top;" {{!}} {{{88}}} <br />
{{!}}-}}<br />
{{#if:{{{89|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{89}}} {{!}}{{!}} <br />
{{!}} style="vertical-align:top;" {{!}} {{{90}}} <br />
{{!}}-}}<br />
{{#if:{{{91|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{91}}} {{!}}{{!}}<br />
{{!}} style="vertical-align:top;" {{!}} {{{92}}}<br />
{{!}}-}}<br />
{{#if:{{{93|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{93}}} {{!}}{{!}}<br />
{{!}} style="vertical-align:top;" {{!}} {{{94}}}<br />
{{!}}-}}<br />
{{#if:{{{95|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{95}}} {{!}}{{!}}<br />
{{!}} style="vertical-align:top;" {{!}} {{{96}}}<br />
{{!}}-}}<br />
{{#if:{{{97|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{97}}} {{!}}{{!}} <br />
{{!}} style="vertical-align:top;" {{!}} {{{98}}} <br />
{{!}}-}}<br />
{{#if:{{{99|}}}| {{!}} style="font-weight:bold; text-align:right; vertical-align:top;" {{!}} {{{99}}} {{!}}{{!}} <br />
{{!}} style="vertical-align:top;" {{!}} {{{100}}} <br />
{{!}}-}}<br />
|}{{#if:{{{101|}}}|''Definition tables only support 50 rows; additional definitions have been omitted''}}</includeonly><noinclude><br />
==Usage==<br />
<pre><br />
{{Definition_table<br />
|Word_1 | Definition one<br />
|Word_2 | Definition two<br />
...<br />
|Word_n | Definition n<br />
}}<br />
</pre><br />
<br />
==Sample==<br />
{{Definition_table<br />
|Definition&nbsp;list | A [[Help:Editing#Sections.2C_paragraphs.2C_lists_and_lines| definition list]] is used for creating lists of definitions. The term is rendered in bold, left-aligned, on its own line, and the definition appears, indented, on the following line(s). Definitions in definition lists are limited to single line formatting, though newlines can be inserted with <nowiki><br></nowiki> tags.<br />
|Definition&nbsp;table | A definition table is used anywhere one wishes to organize blocks of content according to specific key terms, without creating separate section headers for each. The term is rendered in bold, right-aligned, in the first column of the table, and the second column contains the definition or other content. The content may contain any wiki formatting desired, excluding tables, and may contain multi-line formatting such as lists.<br />
}}<br />
==Limitations==<br />
* Definition tables support a maximum of 50 rows. If more rows are supplied, a warning will appear on the page, indicating that additional rows have been omitted.<br />
* Since definition tables use wiki table formatting, tables in the content blocks must begin on a new line.<br />
* When using a list (beginning with * or #) on the first line of a content block, one must insert a newline between the pipe (|) following the term and the list character, or the first list item won't be properly formatted.<br />
* Content blocks within a definition table cannot be individually edited (though this is by design).<br />
<br />
</noinclude></div>Ebenhttps://wiki.sugarlabs.org/index.php?title=Design_Team/Meetings&diff=13332Design Team/Meetings2008-12-16T21:50:55Z<p>Eben: /* Thursday December 11, 2008 - 15.30 (UTC) */</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 }}</noinclude><br />
== Who and what==<br />
<br />
The meeting is targeted to Sugar core and activity developers, but remains open to anyone interested. It's primary purpose is to open the design approach, making it more transparent and allowing the community to provide feedback on both current and upcoming features.<br />
<br />
In general, discussion focuses on:<br />
* high level design goals and ideas<br />
* feedback and discussion of problems in the current design<br />
* reviews of design proposals<br />
<br />
== When and where ==<br />
* Biweekly, 1st and 3rd Thursdays<br />
* 15.30 (UTC)<br />
* irc.freenode.net, [irc://irc.freenode.net/sugar-meeting #sugar-meeting]<br />
<br />
<br />
To convert UTC to your local time, use [http://www.timeanddate.com/worldclock/converter.html?hour=11&min=30&sec=0&p1=0&p2=43 this converter] or run: <br />
date -d '[current date] [time] UTC' <br />
date -d '2008-06-03 14:00 UTC'<br />
<br />
<br />
<br />
== Adding topics ==<br />
You can add topics for discussion to the topics section for the meeting throughout the week. Posted topics will be collected and sent out in the announcement on the morning of the meeting.<br />
<br />
== Meetings ==<br />
<br />
=== Thursday September 18, 2008 - 15.30 (UTC) ===<br />
==== Topics ====<br />
===== Visual Clipboard API =====<br />
For reference, please see the [http://wiki.laptop.org/go/Specifications/Clipboard clipboard specification]. For a more targeted list of features and goals, please see the [[DevelopmentTeam/0.84/Clipboard|clipboard planning page]].<br />
<br />
We had a fairly long discussion about this, which didn't seem to get too far. Fortunately, a follow-up between Marco and I clarified some points, and we agreed that it should be possible to implement the majority of the goals across the system using the "formats" allowed in the GTK protocols, and falling back to sane defaults when extra info isn't provided.<br />
<br />
Some references:<br />
* http://www.pygtk.org/pygtk2tutorial/ch-NewInPyGTK2.2.html#sec-Clipboards<br />
* http://www.pygtk.org/pygtk2tutorial/ch-DragAndDrop.html<br />
* http://www.pygtk.org/pygtk2tutorial/ch-ManagingSelections.html<br />
<br />
===== Advancing the Journal =====<br />
I'd like to have a conversation regarding the current iteration of the Journal, future plans, and the steps we hope to take toward them in the next major release so we can scope our goals. The latest mockups (though slightly out of date) can be seen [http://wiki.laptop.org/go/Designs/Journal here].<br />
<br />
Due to the lengthy clipboard discussion, we didn't hit this topic today. We'll pick it up first thing next week.<br />
<br />
===== Icon reviews =====<br />
We discussed three icons today.<br />
<br />
'''Settings (control panel)''': By popular demand, a wrench was chosen as the base for this icon, though it was also proposed that a wrench and screwdriver could be clearer. It was agreed that the wrench is a simpler icon, and a more generic metaphor which could be used to represent "settings" throughout the system. A few visual tweaks {{Trac|8198|}} made many happier with the wrench, but since this isn't a major change they can come post 8.2.<br />
<br />
'''View Details (Journal)''': The old designs for this button closely resembled a play button (but with an open triangle, akin to a greater than (>) symbol), which some found confusing. The new proposal is an ellipsis [...] icon, to indicate the idea that more info is available, but omitted in the abbreviated list view. This works nicely within the [wiki.laptop.org/go/Designs/Journal new Journal designs], since the icons will occasionally appear within a string of icon-annotated text. All present agreed the latter was a better direction. This change could make 8.2.<br />
<br />
'''Access Point''': Recent experience reports have indicated that the removal of an identifier of the connected AP is frustrating. The proposal discussed is shown [http://interdimensionmedia.com/scratch/devices.png], which wraps the former AP icon (the circle) in "parenthesis" (meant to indicate radio signal). This retains the primitive circular shape of the current access points, but illustrates which is connected in a way which alludes to the wireless activity LED. The point was discussed that the other LED is actually more semantically correct, but not as suitable as an icon.<br />
<br />
Additionally, these [http://wiki.laptop.org/go/Image:School_server_and_ap.png alternate designs] were proposed, using antennae to make the purpose of the icons clearer. We may wish to elicit feedback about these alternatives from teachers and kids to see which convey the notion of wireless connectivity the best. The triangle proposed here was used once, and subsequently removed due to some distaste for the shape in this context, but it may still convey the idea better with the antenna. This change is strongly desired for 8.2.<br />
<br />
=== Wednesday November 26, 2008 - 15.00 (UTC) ===<br />
<br />
We'd like to hold a meeting this week while the topics discussed at the recent SugarCamp are fresh in our minds. Though this is not part of the usual meeting cycle, I think it's important enough to merit an extra meeting. Due to Thanksgiving on Thursday, we'll hold it on Wednesday instead.<br />
<br />
==== Topics ====<br />
===== Short Term Roadmap Definition =====<br />
<br />
To capitalize on the extremely valuable discussions at the recent SugarCamp in Cambridge, we'd like to take some time to define a rough feature roadmap for the Sugar OS within the OLPC 9.1 timeframe. As a starting point for this discussion, we should likely review the various design proposals presented on the last day of the conference.<br />
<br />
=====Groups=====<br />
=====Resuming activities from Home=====<br />
=====Enhancing the Journal=====<br />
=====Improving Toolbars=====<br />
=====Encouraging Naming/Tagging=====<br />
<br />
==== Logs ====<br />
* http://meeting.laptop.org/sugar-meeting.20081126_1018.html<br />
<br />
[[Category:DevelopmentTeam]]<br />
[[Category:Meeting minutes]]<br />
<br />
=== Thursday December 4, 2008 - 15.30 (UTC) ===<br />
<br />
==== Topics ====<br />
<br />
We'll focus on possibilities for overlay chat in activites, presenting both short term and long term ideas, and discuss how this could later be extended to the neighborhood.<br />
<br />
==== Media ====<br />
<br />
* [[Media:Overlay_chat_sketch.pdf | Overlay chat sketch (PDF)]]<br />
<br />
==== Logs ====<br />
<br />
* http://meeting.laptop.org/sugar-meeting.20081204_1042.html<br />
<br />
<br />
=== Friday December 19, 2008 - 15.30 (UTC) ===<br />
<br />
''NOTICE: Christian is unable to attend the regularly scheduled meeting on Thursday, so are postponing the meeting until Friday at the same time.''<br />
<br />
==== Topics ====<br />
<br />
We'll continue discussion of revised, and thorough, mockups for overlay chat in activities. This includes ways in which this chat system can extend into the other zoom levels, and short term and long term goals.<br />
<br />
==== Media ====<br />
<br />
<br />
==== Logs ====</div>Ebenhttps://wiki.sugarlabs.org/index.php?title=Design_Team/Meetings&diff=13013Design Team/Meetings2008-12-11T15:34:53Z<p>Eben: /* Thursday December 11, 2008 - 15.30 (UTC) */</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 }}</noinclude><br />
== Who and what==<br />
<br />
The meeting is targeted to Sugar core and activity developers, but remains open to anyone interested. It's primary purpose is to open the design approach, making it more transparent and allowing the community to provide feedback on both current and upcoming features.<br />
<br />
In general, discussion focuses on:<br />
* high level design goals and ideas<br />
* feedback and discussion of problems in the current design<br />
* reviews of design proposals<br />
<br />
== When and where ==<br />
* Biweekly, 1st and 3rd Thursdays<br />
* 15.30 (UTC)<br />
* irc.freenode.net, [irc://irc.freenode.net/sugar-meeting #sugar-meeting]<br />
<br />
<br />
To convert UTC to your local time, use [http://www.timeanddate.com/worldclock/converter.html?hour=11&min=30&sec=0&p1=0&p2=43 this converter] or run: <br />
date -d '[current date] [time] UTC' <br />
date -d '2008-06-03 14:00 UTC'<br />
<br />
<br />
<br />
== Adding topics ==<br />
You can add topics for discussion to the topics section for the meeting throughout the week. Posted topics will be collected and sent out in the announcement on the morning of the meeting.<br />
<br />
== Meetings ==<br />
<br />
=== Thursday September 18, 2008 - 15.30 (UTC) ===<br />
==== Topics ====<br />
===== Visual Clipboard API =====<br />
For reference, please see the [http://wiki.laptop.org/go/Specifications/Clipboard clipboard specification]. For a more targeted list of features and goals, please see the [[DevelopmentTeam/0.84/Clipboard|clipboard planning page]].<br />
<br />
We had a fairly long discussion about this, which didn't seem to get too far. Fortunately, a follow-up between Marco and I clarified some points, and we agreed that it should be possible to implement the majority of the goals across the system using the "formats" allowed in the GTK protocols, and falling back to sane defaults when extra info isn't provided.<br />
<br />
Some references:<br />
* http://www.pygtk.org/pygtk2tutorial/ch-NewInPyGTK2.2.html#sec-Clipboards<br />
* http://www.pygtk.org/pygtk2tutorial/ch-DragAndDrop.html<br />
* http://www.pygtk.org/pygtk2tutorial/ch-ManagingSelections.html<br />
<br />
===== Advancing the Journal =====<br />
I'd like to have a conversation regarding the current iteration of the Journal, future plans, and the steps we hope to take toward them in the next major release so we can scope our goals. The latest mockups (though slightly out of date) can be seen [http://wiki.laptop.org/go/Designs/Journal here].<br />
<br />
Due to the lengthy clipboard discussion, we didn't hit this topic today. We'll pick it up first thing next week.<br />
<br />
===== Icon reviews =====<br />
We discussed three icons today.<br />
<br />
'''Settings (control panel)''': By popular demand, a wrench was chosen as the base for this icon, though it was also proposed that a wrench and screwdriver could be clearer. It was agreed that the wrench is a simpler icon, and a more generic metaphor which could be used to represent "settings" throughout the system. A few visual tweaks {{Trac|8198|}} made many happier with the wrench, but since this isn't a major change they can come post 8.2.<br />
<br />
'''View Details (Journal)''': The old designs for this button closely resembled a play button (but with an open triangle, akin to a greater than (>) symbol), which some found confusing. The new proposal is an ellipsis [...] icon, to indicate the idea that more info is available, but omitted in the abbreviated list view. This works nicely within the [wiki.laptop.org/go/Designs/Journal new Journal designs], since the icons will occasionally appear within a string of icon-annotated text. All present agreed the latter was a better direction. This change could make 8.2.<br />
<br />
'''Access Point''': Recent experience reports have indicated that the removal of an identifier of the connected AP is frustrating. The proposal discussed is shown [http://interdimensionmedia.com/scratch/devices.png], which wraps the former AP icon (the circle) in "parenthesis" (meant to indicate radio signal). This retains the primitive circular shape of the current access points, but illustrates which is connected in a way which alludes to the wireless activity LED. The point was discussed that the other LED is actually more semantically correct, but not as suitable as an icon.<br />
<br />
Additionally, these [http://wiki.laptop.org/go/Image:School_server_and_ap.png alternate designs] were proposed, using antennae to make the purpose of the icons clearer. We may wish to elicit feedback about these alternatives from teachers and kids to see which convey the notion of wireless connectivity the best. The triangle proposed here was used once, and subsequently removed due to some distaste for the shape in this context, but it may still convey the idea better with the antenna. This change is strongly desired for 8.2.<br />
<br />
=== Wednesday November 26, 2008 - 15.00 (UTC) ===<br />
<br />
We'd like to hold a meeting this week while the topics discussed at the recent SugarCamp are fresh in our minds. Though this is not part of the usual meeting cycle, I think it's important enough to merit an extra meeting. Due to Thanksgiving on Thursday, we'll hold it on Wednesday instead.<br />
<br />
==== Topics ====<br />
===== Short Term Roadmap Definition =====<br />
<br />
To capitalize on the extremely valuable discussions at the recent SugarCamp in Cambridge, we'd like to take some time to define a rough feature roadmap for the Sugar OS within the OLPC 9.1 timeframe. As a starting point for this discussion, we should likely review the various design proposals presented on the last day of the conference.<br />
<br />
=====Groups=====<br />
=====Resuming activities from Home=====<br />
=====Enhancing the Journal=====<br />
=====Improving Toolbars=====<br />
=====Encouraging Naming/Tagging=====<br />
<br />
==== Logs ====<br />
* http://meeting.laptop.org/sugar-meeting.20081126_1018.html<br />
<br />
[[Category:DevelopmentTeam]]<br />
[[Category:Meeting minutes]]<br />
<br />
=== Thursday December 4, 2008 - 15.30 (UTC) ===<br />
<br />
==== Topics ====<br />
<br />
We'll focus on possibilities for overlay chat in activites, presenting both short term and long term ideas, and discuss how this could later be extended to the neighborhood.<br />
<br />
==== Media ====<br />
<br />
* [[Media:Overlay_chat_sketch.pdf | Overlay chat sketch (PDF)]]<br />
<br />
==== Logs ====<br />
<br />
* http://meeting.laptop.org/sugar-meeting.20081204_1042.html<br />
<br />
<br />
=== Thursday December 11, 2008 - 15.30 (UTC) ===<br />
<br />
''NOTICE: Due to unforseen commitments this week, we did not have adequate chance to finalize our sketches for overlay chat. Therefore, we will postpone until our regularly scheduled meeting next week when we will discuss the new designs. In the meantime, please feel free to add additional topics for next weeks discussion! Thanks.''<br />
<br />
==== Topics ====<br />
<br />
We'll continue discussion of revised, and thorough, mockups for overlay chat in activities. This includes ways in which this chat system can extend into the other zoom levels, and short term and long term goals.<br />
<br />
==== Media ====<br />
<br />
<br />
==== Logs ====</div>Ebenhttps://wiki.sugarlabs.org/index.php?title=Sugar_System_Stack&diff=13012Sugar System Stack2008-12-11T15:29:18Z<p>Eben: /* Sugar Application Stack (Graphical) */</p>
<hr />
<div><noinclude><br />
<noinclude><br />
<br />
Sugar is designed to encourage exploration and learning by children that have not been exposed to<br />
or indoctrinated into any existing computing environment. <br />
<br />
</noinclude><br />
<br />
===The Sugar stack===<br />
<br />
Sugar is implemented on top of existing or modified operating systems and hardware. Sugar Activities ("Sugar-enhanced applications") are accessed by the user from the Sugar platform. Many Activities, such as Browse, take advantage of library collections. Some collections are included with Sugar; others may be installed from the Web or created locally. <br />
<br />
The layers in a Sugar system are:<br />
<br />
* Library Collections (e.g., for the Browse Activity)<br />
* Sugar Activities<br />
* Sugar<br />
* Operating System<br />
* Computer Hardware<br />
<br />
===Sugar Application Stack (Graphical)===<br />
<br />
{| border="1" cellpadding="3" style="border-collapse: collapse; border: solid 1px gray;"<br />
<br />
|- align="center" style="background:#ffffd0;"<br />
|style="background:#ffc0c0;"|'''Library<br>Collections'''<br />
|style="background:#ffc0c0;"|[http://wiki.laptop.org/go/Library pre-installed], [http://wiki.laptop.org/go/Library_grid online],<br>[http://wiki.laptop.org/go/Library_bundles locally created]<br />
|rowspan="2"|[http://wiki.laptop.org/go/Read Read]<br />
|rowspan="2"|[http://wiki.laptop.org/go/Write Write]<br />
|rowspan="2"|[http://wiki.laptop.org/go/Record Record]<br />
|rowspan="2"|[http://wiki.laptop.org/go/Etoys EToys]<br />
|rowspan="2"|[http://wiki.laptop.org/go/TurtleArt TurtleArt]<br />
|rowspan="2" colspan="2"|[[Activities | ...]]<br />
<br />
|- align="center" style="background:#ffffd0;"<br />
||'''Sugar<br>Activities'''<br />
||[http://wiki.laptop.org/go/Browse Browse]<br />
<br />
|- align="center" style="background:#e0ffe0;"<br />
||'''Application<br>Framework'''<br />
|colspan="8"|[[Sugar]]<br />
<br />
|- align=center style="background:#e0e0ff;"<br />
||'''Operating<br>System'''<br />
||[[Community/Distributions/Fedora|Fedora]]<br />
||[[Community/Distributions/Debian|Debian]]<br />
||[[Community/Distributions/Ubuntu|Ubuntu]]<br />
||Linux, other<br />
||[http://en.wikipedia.org/wiki/Linux_Terminal_Server_Project LTSP]<br />
||[http://wiki.laptop.org/go/Sugar_on_MacOS_X Mac OSX]]<br />
||[[Supported systems/Windows|MS Windows<br>(QEMU)]]<br />
||...<br />
<br />
|- align=center style="background:#ffffff;"<br />
||'''Hardware<br>Platform'''<br />
||[http://en.wikipedia.org/wiki/Olpc OLPC]<br>[http://wiki.laptop.org/go/XO XO-1]<br />
||[http://en.wikipedia.org/wiki/Asus ASUS]<br>[http://en.wikipedia.org/wiki/Eee_PC EEE PC]<br />
||[http://en.wikipedia.org/wiki/Intel Intel]<br>[http://en.wikipedia.org/wiki/Classmate_PC Classmate]<br />
||[http://en.wikipedia.org/wiki/Olpc OLPC]<br>[http://wiki.laptop.org/go/XO-2 XO-2]<br />
|colspan="4"|...<br />
<br />
|}<br />
<br />
[[Sugar Application Stack (ASCII Text)]]<br />
<br />
[[Category:Supported systems]]</div>Ebenhttps://wiki.sugarlabs.org/index.php?title=Sugar_System_Stack&diff=13011Sugar System Stack2008-12-11T15:26:53Z<p>Eben: /* Sugar Application Stack (Graphical) */</p>
<hr />
<div><noinclude><br />
<noinclude><br />
<br />
Sugar is designed to encourage exploration and learning by children that have not been exposed to<br />
or indoctrinated into any existing computing environment. <br />
<br />
</noinclude><br />
<br />
===The Sugar stack===<br />
<br />
Sugar is implemented on top of existing or modified operating systems and hardware. Sugar Activities ("Sugar-enhanced applications") are accessed by the user from the Sugar platform. Many Activities, such as Browse, take advantage of library collections. Some collections are included with Sugar; others may be installed from the Web or created locally. <br />
<br />
The layers in a Sugar system are:<br />
<br />
* Library Collections (e.g., for the Browse Activity)<br />
* Sugar Activities<br />
* Sugar<br />
* Operating System<br />
* Computer Hardware<br />
<br />
===Sugar Application Stack (Graphical)===<br />
<br />
{| border="1" cellpadding="3" style="border-collapse: collapse; border: solid 1px gray;"<br />
<br />
|- align="center" style="background:#ffffd0;"<br />
|style="background:#ffc0c0;"|'''Library<br>Collections'''<br />
|style="background:#ffc0c0;"|[http://wiki.laptop.org/go/Library pre-installed],<br>[http://wiki.laptop.org/go/Library_grid from the web],<br>[http://wiki.laptop.org/go/Library_bundles locally created]<br />
|rowspan="2"|[http://wiki.laptop.org/go/Read Read]<br />
|rowspan="2"|[http://wiki.laptop.org/go/Write Write]<br />
|rowspan="2"|[http://wiki.laptop.org/go/Record Record]<br />
|rowspan="2"|[http://wiki.laptop.org/go/Etoys EToys]<br />
|rowspan="2"|[http://wiki.laptop.org/go/TurtleArt TurtleArt]<br />
|rowspan="2" colspan="2"|[[Activities | ...]]<br />
<br />
|- align="center" style="background:#ffffd0;"<br />
||'''Sugar<br>Activities'''<br />
||[http://wiki.laptop.org/go/Browse Browse]<br />
<br />
|- align="center" style="background:#e0ffe0;"<br />
||'''Application<br>Framework'''<br />
|colspan="8"|[[Sugar]]<br />
<br />
|- align=center style="background:#e0e0ff;"<br />
||'''Operating<br>System'''<br />
||[[Community/Distributions/Fedora|Fedora]]<br />
||[[Community/Distributions/Debian|Debian]]<br />
||[[Community/Distributions/Ubuntu|Ubuntu]]<br />
||Linux, other<br />
||[http://en.wikipedia.org/wiki/Linux_Terminal_Server_Project LTSP]<br />
||[http://wiki.laptop.org/go/Sugar_on_MacOS_X Mac OSX]]<br />
||[[Supported systems/Windows|MS Windows<br>(QEMU)]]<br />
||...<br />
<br />
|- align=center style="background:#ffffff;"<br />
||'''Hardware<br>Platform'''<br />
||[http://en.wikipedia.org/wiki/Olpc OLPC]<br>[http://wiki.laptop.org/go/XO XO-1]<br />
||[http://en.wikipedia.org/wiki/Asus ASUS]<br>[http://en.wikipedia.org/wiki/Eee_PC EEE PC]<br />
||[http://en.wikipedia.org/wiki/Intel Intel]<br>[http://en.wikipedia.org/wiki/Classmate_PC Classmate]<br />
||[http://en.wikipedia.org/wiki/Olpc OLPC]<br>[http://wiki.laptop.org/go/XO-2 XO-2]<br />
|colspan="4"|...<br />
<br />
|}<br />
<br />
[[Sugar Application Stack (ASCII Text)]]<br />
<br />
[[Category:Supported systems]]</div>Ebenhttps://wiki.sugarlabs.org/index.php?title=Sugar_System_Stack&diff=13008Sugar System Stack2008-12-11T15:20:19Z<p>Eben: /* Sugar Application Stack (Graphical) */</p>
<hr />
<div><noinclude><br />
<noinclude><br />
<br />
Sugar is designed to encourage exploration and learning by children that have not been exposed to<br />
or indoctrinated into any existing computing environment. <br />
<br />
</noinclude><br />
<br />
===The Sugar stack===<br />
<br />
Sugar is implemented on top of existing or modified operating systems and hardware. Sugar Activities ("Sugar-enhanced applications") are accessed by the user from the Sugar platform. Many Activities, such as Browse, take advantage of library collections. Some collections are included with Sugar; others may be installed from the Web or created locally. <br />
<br />
The layers in a Sugar system are:<br />
<br />
* Library Collections (e.g., for the Browse Activity)<br />
* Sugar Activities<br />
* Sugar<br />
* Operating System<br />
* Computer Hardware<br />
<br />
===Sugar Application Stack (Graphical)===<br />
<br />
{| border="1" cellpadding="3" style="border-collapse: collapse; border: solid 1px gray;"<br />
<br />
|- align="center" style="background:#ffffd0;"<br />
|style="background:#ffc0c0;"|'''Library<br>Collections'''<br />
|style="background:#ffc0c0;"|[http://wiki.laptop.org/go/Library pre-installed],<br>[http://wiki.laptop.org/go/Library_grid from the Web],<br>[http://wiki.laptop.org/go/Library_bundles locally created]<br />
|rowspan="2"|[http://wiki.laptop.org/go/Read Read]<br />
|rowspan="2"|[http://wiki.laptop.org/go/Write Write]<br />
|rowspan="2"|[http://wiki.laptop.org/go/Record Record]<br />
|rowspan="2"|[http://wiki.laptop.org/go/Etoys EToys]<br />
|rowspan="2"|[http://wiki.laptop.org/go/TurtleArt TurtleArt]<br />
|rowspan="2" colspan="2"|[[Activities | ...]]<br />
<br />
|- align="center" style="background:#ffffd0;"<br />
||'''Sugar<br>Activities'''<br />
||[http://wiki.laptop.org/go/Browse Browse]<br />
<br />
|- align="center" style="background:#e0ffe0;"<br />
||'''Application<br>Framework'''<br />
|colspan="8"|[[Sugar]]<br />
<br />
|- align=center style="background:#e0e0ff;"<br />
||'''Operating<br>System'''<br />
||[[Community/Distributions/Fedora|Fedora]]<br />
||[[Community/Distributions/Debian|Debian]]<br />
||[[Community/Distributions/Ubuntu|Ubuntu]]<br />
||Linux, other<br />
||[http://en.wikipedia.org/wiki/Linux_Terminal_Server_Project LTSP]<br />
||[http://wiki.laptop.org/go/Sugar_on_MacOS_X Mac OSX]]<br />
||[[Supported systems/Windows|MS Windows<br>(QEMU)]]<br />
||...<br />
<br />
|- align=center style="background:#ffffff;"<br />
||'''Hardware<br>Platform'''<br />
||[http://en.wikipedia.org/wiki/Olpc OLPC]<br>[http://wiki.laptop.org/go/XO XO-1]<br />
||[http://en.wikipedia.org/wiki/Asus ASUS]<br>[http://en.wikipedia.org/wiki/Eee_PC EEE PC]<br />
||[http://en.wikipedia.org/wiki/Intel Intel]<br>[http://en.wikipedia.org/wiki/Classmate_PC Classmate]<br />
||[http://en.wikipedia.org/wiki/Olpc OLPC]<br>[http://wiki.laptop.org/go/XO-2 XO-2]<br />
|colspan="4"|...<br />
<br />
|}<br />
<br />
[[Sugar Application Stack (ASCII Text)]]<br />
<br />
[[Category:Supported systems]]</div>Ebenhttps://wiki.sugarlabs.org/index.php?title=Activities&diff=13004Activities2008-12-11T15:18:01Z<p>Eben: /* And more */</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 }}</noinclude>{{Translations}}<br />
<br />
== Activities ==<br />
Sugar applications are called [http://wiki.laptop.org/go/Activities Activities]. This is a list of some Activities that are installed by default. There is a proposal for an [[Activity portal]].<br />
<br />
<div style="float:left"><br />
__TOC__<br />
</div><br />
<br />
<table border="0"><br />
<tr><br />
<td width="33%" style="text-align: center;"><br />
[[Image:activity-journal.png|40px]]<br />
<br />
=== Journal === <br />
Object and activity browser<br />
<br />
</td><br />
<br />
<td width="33%" style="text-align: center;"><br />
[[Image:activity-pippy.png|40px]]<br />
=== Pippy=== <br />
Python Programming language/environment<br />
</td><br />
<br />
<td width="33%" style="text-align: center;"><br />
[[Image:activity-web.png|40px]]<br />
=== [http://wiki.laptop.org/go/Browse Browse] === <br />
Web browser based on Mozilla Firefox<br />
</td></tr><br />
<tr><br />
<td width="33%" style="text-align: center;"><br />
[[Image:activity-etoys.png|40px]]<br />
=== Etoys=== <br />
Learning / programming / authoring environment<br />
</td><br />
<td width="33%" style="text-align: center;"><br />
[[Image:activity-read.png|40px]]<br />
=== Read=== <br />
Book/PDF reader<br />
</td><br />
<td width="33%" style="text-align: center;"><br />
[[Image:activity-turtleart.png|40px]]<br />
=== Turtle Art=== <br />
Pseudo-Logo graphical programming language<br />
</td></tr><br />
<tr><br />
<td width="33%" style="text-align: center;"><br />
[[Image:activity-write.png|40px]]<br />
=== Write=== <br />
Word processor</td><br />
<td width="33%" style="text-align: center;"><br />
[[Image:activity-calculate.png|40px]]<br />
=== Calculate=== <br />
Basic calculator<br />
</td><br />
<td width="33%" style="text-align: center;"><br />
[[Image:activity-news.png|40px]]<br />
=== News Reader=== <br />
News reader<br />
</td></tr><br />
<tr><br />
<td width="33%" style="text-align: center;"><br />
[[Image:activity-measure.png|40px]]<br />
=== Measure=== <br />
Oscilloscope and Data Logging<br />
</td><br />
<td width="33%" style="text-align: center;"><br />
[[Image:activity-draw.png|40px]]<br />
=== Paint=== <br />
Simple paint activity<br />
</td><br />
<td width="33%" style="text-align: center;"><br />
[[Image:activity-acousticmeasure.png|40px]]<br />
=== Distance=== <br />
Measure distance between two laptops<br />
</td></tr><br />
<tr><br />
<td width="33%" style="text-align: center;"><br />
[[Image:activity-record.png|40px]]<br />
=== Record=== <br />
Still, video, and audio capture<br />
</td><br />
<td width="33%" style="text-align: center;"><br />
[[Image:activity-analyze.png|40px]]<br />
=== Analyze=== <br />
An activity version of the Sugar analyze tool<br />
</td><br />
<td width="33%" style="text-align: center;"><br />
[[Image:activity-log.png|40px]]<br />
=== Log=== <br />
An activity version of the Sugar logging tool<br />
</td><br />
<tr><br />
<td width="33%" style="text-align: center;"><br />
[[Image:activity-terminal.png|40px]] <br />
=== Terminal=== <br />
An activity version of the Sugar terminal <br />
</td><br />
<td width="33%" style="text-align: center;"><br />
[[Image:activity-tamtamjam.png|40px]]<br />
=== TamTam=== <br />
Music composition and synthesis.<br />
</td><br />
<td width="33%" style="text-align: center;"><br />
=== And more ===<br />
[http://wiki.laptop.org/go/Activities/All Dozens more are available].<br />
</td><br />
</tr><br />
</table><br />
<br />
=Running Linux Applications Under Sugar=<br />
<br />
There are two ways to run Linux applications as Activities under Sugar (meaning you don't need to use Terminal to load them):<br />
*'''Sugar Coating''' - Making Linux apps run under Sugar, but not modifying them to take advantage of Sugar's collaborative capabilities<br />
*'''Sugarizing''' - A fully integrated Linux application, re-engineered to take advantage of Sugar's advanced collaboration abilities<br />
<br />
===Sugar Coating Activities===<br />
<br />
To run Linux apps under Sugar (i.e. making them to run in the Sugar interface, without the collaboration and other Sugar integration programmed into them), read these instructions on [[Running Linux Applications Under Sugar]]. <br />
<br />
===Sugarizing Activities===<br />
<br />
To be written.<br />
<br />
=Useful Linux Applications=<br />
<br />
===VLC Media Player===<br />
The VLC media player is a highly portable multimedia player for various audio and video formats (MPEG-1, MPEG-2, MPEG-4, DivX, mp3, flv, avi, ogg, ...) as well as DVDs, VCDs, and various streaming protocols. It can also be used as a server to stream in unicast or multicast in IPv4 or IPv6 on a high-bandwidth network.; the VLC Player is considered to be better by some users then MPlayer because it offer more settings, options and features. There is also no need to run it from Terminal. Read [[Activity_VLC]] to learn how to install it.<br />
<br />
===Seamonkey===<br />
SeaMonkey has inherited the successful all-in-one concept of the original Netscape Communicator and continues that product line based on the modern, cross-platform architecture provided by the Mozilla project.<br />
<br />
* The Internet browser at the core of the SeaMonkey suite uses the same rendering engine as its sibling Mozilla Firefox, with popular features like tabbed browsing, popup blocking, find as you type and a lot of other functionality for a smooth web experience.<br />
* SeaMonkey's Mail and Newsgroups client shares lots of code with Mozilla Thunderbird and features adaptive Junk mail filtering, labels and mail views, multiple accounts, S/MIME, address books with LDAP support and is ready for both private and corporate use.<br />
* Additonal components include an easy-to-use HTML Editor, the ChatZilla IRC chat application and web development tools like a DOM Inspector and a JavaScript debugger.<br />
* If that's still not enough, SeaMonkey can be extended with numerous Add-Ons that provide additional functionality and customization for a complete Internet experience.<br />
<br />
Seamonkey can be Sugar-coated.<br />
<br />
===Midnight Commander===<br />
Midnight Commander is a text-mode file manager. It is easily Sugar-coated for access from the Activities panel.[http://www.ibiblio.org/mc/images/mc-panels.png Screenshot]<br />
<br />
===Totem Media Player===<br />
The Totem media player is already installed in the OLPC XO-1. It is the engine that supports media on the system. Out of the box it does not support MP3 music or MPEG-4 video. A free driver can be downloaded to add MP3 compatability. A Sugar-coating can be applied to easily access the program from the Activities panel. <br />
<br />
===[http://tux4kids.alioth.debian.org/ Tux4Kids]===<br />
;TuxType2: [http://tuxtype.sourceforge.net/ TuxType] is a touch typing tutorial/game than can be installed on the OLPC XO-1 using the yum command. A Sugar-coating can be applied to easily access the program from the Activities panel.<br />
;TuxMath: [http://tux4kids.alioth.debian.org/tuxmath.php TuxMath] is an arcade game that helps kids practice their math facts. A Sugar-coating can be applied to easily access the program from the Activities panel.<br />
;TuxPaint: [http://www.tuxpaint.org/ Tux Paint] is a drawing program for children ages 3 to 12. It combines an easy-to-use interface, fun sound effects, and an encouraging cartoon mascot who guides children as they use the program. A Sugar-coating can be applied to easily access the program from the Activities panel. <br />
<br />
-----<br />
<br />
(Let's try to organize this page based on some criteria of completion as per the discussion in [[Talk:{{PAGENAME}}]].)</div>Ebenhttps://wiki.sugarlabs.org/index.php?title=Wiki_Team/TODO&diff=12998Wiki Team/TODO2008-12-11T15:07:01Z<p>Eben: </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 }}<br />
{{TeamHeader|WikiTeam}}</noinclude><br />
<br />
=== Active Tasks ===<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
! Task<br />
! Owner<br />
! Priority<br />
! Next Milestone<br />
! Notes<br />
|-<br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
|}<br />
<br />
=== Requested Tasks ===<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
! Task<br />
! Owner<br />
! Priority<br />
! Next Milestone<br />
! Notes<br />
|-<br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
|}<br />
<br />
<noinclude>=== Completed Tasks ===<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
! Task<br />
! Owner <br />
! Priority<br />
! Completion Date<br />
! Notes<br />
|-<br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
|}<br />
<br />
=== Ongoing Tasks ===<br />
People are needed mostly for writing and editing, but there are many other ways of making a useful contribution. For example, simply pointing out errors (such as typos, grammar and spelling, and technical errors) is an extremely useful way to help.<br />
<br />
*Fix spelling and formatting errors<br />
*Simplify the structure of long pages<br />
*Organize untidy pages so that they are easy to read<br />
*Fix broken links<br />
*Add new documentation to the wiki<br />
*Add category tags where appropriate<br />
<br />
Before you start contributing to the wiki, you should read the [[WikiTeam/Resources|Wiki Guide]] for information on how to edit pages correctly. See the **Wiki Cleanup** page for tips on cleaning-up wiki pages.<br />
<br />
====Cleanup====<br />
The pages listed on [[:Category:Cleanup]] are in need of a thorough cleanup.<br />
<br />
These pages either:<br />
* Do not follow the standards of documentation,<br />
* Contain incorrect or out-of-date information, or<br />
* Are formatted incorrectly. <br />
<br />
Feel free to dive in. Tidy up a page and remove the Cleanup **tag**!<br />
<br />
If you find a page that needs to be cleaned up, DO NOT add it here. Follow the instructions as laid out on the Tag page.<br />
<br />
====Organize====<br />
Much of our work is getting the wiki organized. We look through [[Special:Allpages]] to ensure that content is in the correct place<br />
<br />
====Coordinate====<br />
Coordination between wiki.laptop.org and wiki.sugarlabs.org.<br />
<br />
Move content between w.s.o and w.l.o so that it lands in the most appropriate place. <br />
<br />
====Expand====<br />
Want to contribute your knowledge?<br />
<br />
As an open source Wiki, we have a wide range of individuals working to help expand our resource, and we want your help.<br />
<br />
Check out the list of articles with the Needs Expansion tag for articles that are formatted correctly, but simply need to be expanded to cover the full topic. <br />
<br />
See the Community [[Sugar Labs/TODO|TODO]] list for more thing that need doing.<br />
[[Category:Wiki]]<br />
</noinclude></div>Ebenhttps://wiki.sugarlabs.org/index.php?title=BugSquad/TODO&diff=12997BugSquad/TODO2008-12-11T15:05:50Z<p>Eben: </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 }}<br />
{{TeamHeader|TestingTeam}}<br />
</noinclude><br />
<br />
=== Active Tasks ===<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
! Task<br />
! Owner<br />
! Priority<br />
! Next Milestone<br />
! Notes<br />
|-<br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
|}<br />
<br />
=== Requested Tasks ===<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
! Task<br />
! Owner<br />
! Priority<br />
! Next Milestone<br />
! Notes<br />
|-<br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
|}<br />
<br />
<noinclude>=== Completed Tasks ===<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
! Task<br />
! Owner <br />
! Priority<br />
! Completion Date<br />
! Notes<br />
|-<br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
|}<br />
<br />
Form the TestingTeam at the sugar dev meeting [[DevelopmentTeam/Meetings]].<br />
<br />
[[Category:TestingTeam]]<br />
</noinclude></div>Ebenhttps://wiki.sugarlabs.org/index.php?title=Marketing_Team/TODO&diff=12996Marketing Team/TODO2008-12-11T15:04:58Z<p>Eben: </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 }}<br />
{{TeamHeader|MarketingTeam}}</noinclude><br />
<br />
=== Active Tasks ===<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
! Task<br />
! Owner<br />
! Priority<br />
! Next Milestone<br />
! Notes<br />
|-<br />
| Make the "Get Involved" page amazing<br />
| gregdek<br />
| 1<br />
| 12/16/2008<br />
| Content on page is better. Still need strong TODO pages for individual teams; gregdek will drive that. We also need to move "get involved" to above the fold.<br />
|-<br />
| Create a sponsorship program<br />
| walter<br />
| 1<br />
| 12/16/2008<br />
| In order to get corporate sponsors, we need to tell them what they get for their money.<br />
|-<br />
| Finish creation of the elevator pitch<br />
| gregdek<br />
| 1<br />
| 12/16/2008<br />
| We have a bunch of pitches at [[MarketingTeam/ElevatorPitch]]. gregdek will talk to Dennis and Scott about <br />
|-<br />
| Get everyone's blog aggregated at planet.sugarlabs.org<br />
| gregdek<br />
| 1<br />
| weekly update <br />
| We need the voices of Sugar Labs to be loud and clear. (12/2: 23 feeds.) (12/9: 23 feeds.)<br />
|-<br />
| Business card design<br />
| walter<br />
| 1<br />
| 12/16/2008<br />
| Sugar Labs representatives need easy access to business cards. Walter will work with Christian to get simple, easy-to-use designs.<br />
|}<br />
<br />
=== Requested Tasks ===<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
! Task<br />
! Owner<br />
! Priority<br />
! Next Milestone<br />
! Notes<br />
|-<br />
| Slide deck design<br />
| christian<br />
| <br />
| <br />
| Requested by [[User:Mchua|Mchua]]. Can we have a .odp template downloadeable from [[Presentations]], for making cool-looking, SL-branded slide decks?<br />
|}<br />
<br />
<noinclude>=== Completed Tasks ===<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
! Task<br />
! Owner <br />
! Priority<br />
! Completion Date<br />
! Notes<br />
|-<br />
| Get the weekly meeting scheduled<br />
| gregdek<br />
| 1<br />
| 12/2/2008<br />
| Meetings are now every Tuesday at 1600 UTC.<br />
|-<br />
| Create mailing list<br />
| gregdek<br />
| 1<br />
| 11/20/2008<br />
| We have a mailing list now: http://lists.sugarlabs.org/listinfo/marketing<br />
|-<br />
| Write a blurb for the top of planet.sugarlabs.org<br />
| mchua<br />
| 1<br />
| 12/9/2008<br />
| Important to describe what pl.sl.o actually is. Update: The blurb is written, and has been pushed to [[InfrastructureTeam]] as [http://dev.sugarlabs.org/ticket/77 ticket #77]. Closed.<br />
|-<br />
| Start stuff for [[Summer of Code]] '09 for Sugar Labs<br />
| mchua<br />
| 1<br />
| <br />
| Done. See wiki page.<br />
<br />
|}<br />
<br />
[[Category:MarketingTeam]]<br />
</noinclude></div>Ebenhttps://wiki.sugarlabs.org/index.php?title=Infrastructure_Team/TODO&diff=12995Infrastructure Team/TODO2008-12-11T15:02:52Z<p>Eben: </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|InfrastructureTeam}}</noinclude><br />
<br />
=== Active Tasks ===<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
! Task<br />
! Owner<br />
! Priority<br />
! Next Milestone<br />
! Notes<br />
|-<br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
|}<br />
<br />
=== Requested Tasks ===<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
! Task<br />
! Owner<br />
! Priority<br />
! Next Milestone<br />
! Notes<br />
|-<br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
|}<br />
<br />
<noinclude>=== Completed Tasks ===<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
! Task<br />
! Owner <br />
! Priority<br />
! Completion Date<br />
! Notes<br />
|-<br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
|}<br />
<br />
=== Backups ===<br />
<br />
We are considering a couple of possibilities:<br />
<br />
* MIT provides a backup service for a few bucks per machine per month via Tivoli<br />
* Harvard Computer Society filer<br />
<br />
=== Shell accounts ===<br />
<br />
Setup workload will be distributed between the sysadmins and a few members of the core team.<br />
<br />
===General===<br />
* CMS to host a few, nice looking, official pages.<br />
* git for both core and activities. personal repos. (ssh access for devs)<br />
* Trac for core and activities<br />
* buildbot, master + a few slaves (ssh access for devs)<br />
* RT system<br />
** Is this really needed? We can just use other infrastructure for help requests... [[User:Firefoxman|Firefoxman]] 19:27, 18 May 2008 (UTC)<br />
* Pootle<br />
* LDAP or OpenID authentication across various Sugarlabs tools<br />
</noinclude></div>Ebenhttps://wiki.sugarlabs.org/index.php?title=Education_Team/TODO&diff=12994Education Team/TODO2008-12-11T15:01:35Z<p>Eben: </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 }}<br />
{{TeamHeader|EducationTeam}}</noinclude><br />
=== Active Tasks ===<br />
{| border=1 cellpadding=2 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
! Task<br />
! Owner<br />
! Priority<br />
! Next Milestone<br />
! Notes<br />
|-<br />
| outreach to Lesley University<br />
| Walter<br />
| high<br />
| meeting with senior admin.<br />
| Lesley has a great alumni network and tremendous outreach into classrooms throughout the US<br />
|-<br />
|}<br />
<br />
=== Requested Tasks ===<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
! Task<br />
! Owner<br />
! Priority<br />
! Next Milestone<br />
! Notes<br />
|-<br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
|}<br />
<br />
<noinclude>=== Completed Tasks ===<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
! Task<br />
! Owner <br />
! Priority<br />
! Completion Date<br />
! Notes<br />
|-<br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
|}<br />
<br />
See the Community [[Sugar Labs/TODO|TODO]] list for more thing that need doing.<br />
[[Category:EducationTeam]]<br />
</noinclude></div>Ebenhttps://wiki.sugarlabs.org/index.php?title=Documentation_Team/TODO&diff=12990Documentation Team/TODO2008-12-11T14:51:30Z<p>Eben: </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 }}<br />
{{TeamHeader|DocumentationTeam}}</noinclude><br />
<br />
=== Active Tasks ===<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
! Task<br />
! Owner<br />
! Priority<br />
! Next Milestone<br />
! Notes<br />
|-<br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
|}<br />
<br />
=== Requested Tasks ===<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
! Task<br />
! Owner<br />
! Priority<br />
! Next Milestone<br />
! Notes<br />
|-<br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
|}<br />
<br />
<noinclude>=== Completed Tasks ===<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
! Task<br />
! Owner <br />
! Priority<br />
! Completion Date<br />
! Notes<br />
|-<br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
|}<br />
<br />
=== User Documentation ===<br />
We will need to create documentation for our own work, and we should contribute to OLPC documentation.<br />
<br />
We need to decide on document formats and tools. At some point we will create new formats, based on our research into new textbook capabilities given Sugar software.<br />
<br />
See the Community [[Sugar Labs/TODO|TODO]] list for more thing that need doing.<br />
[[Category:DocumentationTeam]]<br />
</noinclude></div>Ebenhttps://wiki.sugarlabs.org/index.php?title=Development_Team/TODO&diff=12989Development Team/TODO2008-12-11T14:50:58Z<p>Eben: </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 }}<br />
{{TeamHeader|DevelopmentTeam}}</noinclude><br />
=== Active Tasks ===<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
! Task<br />
! Owner<br />
! Priority<br />
! Next Milestone<br />
! Notes<br />
|-<br />
| Get to the point where we can effectively dogfood collaboration<br />
| marcopg<br />
| <br />
| <br />
| <br />
|-<br />
| Restructure the DevelopmentTeam wiki<br />
| marcopg<br />
| <br />
| <br />
| (later I want to start adding documentation)<br />
|-<br />
| Implement journal entry transfer<br />
| tomeu<br />
| <br />
| <br />
| <br />
|-<br />
| Finish support for removable devices in the journal<br />
| tomeu<br />
| <br />
| <br />
| <br />
|-<br />
| Making PS a bit more controllable from the control panel<br />
| morgs<br />
| <br />
| <br />
| (restart gabble without needing to restart Sugar, switch between jabber servers)<br />
|-<br />
|}<br />
<br />
=== Requested Tasks ===<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
! Task<br />
! Owner<br />
! Priority<br />
! Next Milestone<br />
! Notes<br />
|-<br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
|}<br />
<br />
<noinclude>=== Completed Tasks ===<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
! Task<br />
! Owner <br />
! Priority<br />
! Completion Date<br />
! Notes<br />
|-<br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
|}<br />
<br />
See the Community [[Sugar Labs/TODO|TODO]] list for more thing that need doing.<br />
[[Category:DevelopmentTeam]]<br />
</noinclude></div>Ebenhttps://wiki.sugarlabs.org/index.php?title=Deployment_Team/TODO&diff=12988Deployment Team/TODO2008-12-11T14:50:08Z<p>Eben: </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|DeploymentTeam}} </noinclude><br />
<br />
=== Active Tasks ===<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
! Task<br />
! Owner<br />
! Priority<br />
! Next Milestone<br />
! Notes<br />
|-<br />
|-<br />
! Meeting with the Gardner School<br />
! Caroline<br />
! High<br />
! Should be scheduled next week<br />
! <br />
|-<br />
| <br />
| <br />
| <br />
| <br />
|-<br />
|}<br />
<br />
=== Requested Tasks ===<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
! Task<br />
! Owner<br />
! Priority<br />
! Next Milestone<br />
! Notes<br />
|-<br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
|}<br />
<br />
<noinclude>=== Completed Tasks ===<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
! Task<br />
! Owner <br />
! Priority<br />
! Completion Date<br />
! Notes<br />
|-<br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
|}<br />
<br />
=== To Do ===<br />
* <strike>Schedule byweekly meetings and announce then on IAEP/Sugar.</strike><br />
:: biweekly meetings are in the shared calendar <br />
* Determine Regional Sugar labs governance.<br />
** Create a set of principles<br />
** Create a strawman business model<br />
* Facilitate communication between learners and developers.(implement ways to do so)<br />
* Document and complement deployment guides.<br />
<br />
'''See''' the [[Sugar Labs/TODO|Community To Do list]] for more items that need doing.<br />
[[Category:Deployment]]<br />
</noinclude></div>Ebenhttps://wiki.sugarlabs.org/index.php?title=Design_Team/Getting_Involved&diff=12985Design Team/Getting Involved2008-12-11T14:44:37Z<p>Eben: </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 }}<br />
{{TeamHeader|DesignTeam}}</noinclude><br />
<br />
There are many ways to get involved with the design team. No matter which you choose, we invite you to introduce yourself and your area of interest at our biweekly IRC meetings, on 1st and 3rd Thursdays at 15.30 UTC on irc.freenode.net, [irc://irc.freenode.net/sugar-meeting #sugar-meeting]. Please see [[DesignTeam/Meetings]] for more information about times and topics.<br />
<br />
[[Category:DesignTeam]]</div>Ebenhttps://wiki.sugarlabs.org/index.php?title=Design_Team/Contacts&diff=12950Design Team/Contacts2008-12-10T17:21:21Z<p>Eben: </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 }}<br />
{{TeamHeader|DesignTeam}}</noinclude><br />
== Coordinators ==<br />
{{:DesignTeam/Coordinator}}<br />
<br />
== IRC channel ==<br />
Sugar designers (and developers) hang out in the [irc://irc.freenode.net/sugar #sugar] channel on irc.freenode.net.<br />
<br />
== Team Members ==<br />
Please add yourself to the list if you're interested in participating!<br />
<br />
*[[User:Eben | Eben Eliason]]<br />
*[[User:christianmarcschmidt | Christian Marc Schmidt]]<br />
<br />
<br />
<br />
[[Category:DesignTeam]]</div>Ebenhttps://wiki.sugarlabs.org/index.php?title=Design_Team/Contacts&diff=12948Design Team/Contacts2008-12-10T17:18:54Z<p>Eben: /* People */</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 }}<br />
{{TeamHeader|DesignTeam}}</noinclude><br />
== Coordinators ==<br />
{{:DesignTeam/Coordinator}}<br />
<br />
== IRC channel ==<br />
Sugar designers (and developers) hang out in the [irc://irc.freenode.net/sugar #sugar] channel on irc.freenode.net.<br />
<br />
== People ==<br />
Please add yourself to the list if you're interested in participating!<br />
<br />
*[[User:Eben | Eben Eliason]]<br />
*[[User:christianmarcschmidt | Christian Marc Schmidt]]<br />
<br />
<br />
<br />
[[Category:DesignTeam]]</div>Ebenhttps://wiki.sugarlabs.org/index.php?title=Design_Team/Contacts&diff=12947Design Team/Contacts2008-12-10T17:17:36Z<p>Eben: /* Coordinator */</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 }}<br />
{{TeamHeader|DesignTeam}}</noinclude><br />
== Coordinators ==<br />
{{:DesignTeam/Coordinator}}<br />
<br />
== IRC channel ==<br />
Sugar designers (and developers) hang out in the [irc://irc.freenode.net/sugar #sugar] channel on irc.freenode.net.<br />
<br />
== People ==<br />
* Christian Marc Schmidt<br />
<br />
[[Category:DesignTeam]]</div>Ebenhttps://wiki.sugarlabs.org/index.php?title=Design_Team/TODO&diff=12946Design Team/TODO2008-12-10T17:15:22Z<p>Eben: </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 }}<br />
{{TeamHeader|DesignTeam}}</noinclude><br />
<br />
=== Active Tasks ===<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
! Task<br />
! Owner<br />
! Priority<br />
! Next Milestone<br />
! Notes<br />
|-<br />
| Create a proper todo list<br />
| Eben<br />
| High<br />
| <br />
| Help is welcomed!<br />
|-<br />
| Update the [[DesignTeam/Hig/Sugar|Human Interface Guidelines]]<br />
| Eben<br />
| Normal<br />
| <br />
| <br />
|-<br />
| Transfer designs from w.l.o<br />
| Eben<br />
| Normal<br />
| <br />
| It makes sense for current and future design work to live on w.s.o instead.<br />
|-<br />
|}<br />
<br />
<br />
=== Requested Tasks ===<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
! Task<br />
! Owner<br />
! Priority<br />
! Next Milestone<br />
! Notes<br />
|-<br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
|}<br />
<br />
<br />
<noinclude>=== Completed Tasks ===<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
! Task<br />
! Owner <br />
! Priority<br />
! Completion Date<br />
! Notes<br />
|-<br />
| Style these todo tables reasonably<br />
| Eben<br />
| Normal<br />
| <br />
| Perhaps we can get help from the wiki team to propagate the styles, or add a class for them.<br />
|-<br />
|}<br />
<br />
<br />
See the Community [[Sugar Labs/TODO|TODO]] list for more things that need doing.<br />
[[Category:TestingTeam]]<br />
</noinclude></div>Ebenhttps://wiki.sugarlabs.org/index.php?title=Design_Team/TODO&diff=12945Design Team/TODO2008-12-10T17:13:19Z<p>Eben: /* Active Tasks */</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 }}<br />
{{TeamHeader|DesignTeam}}</noinclude><br />
<br />
=== Active Tasks ===<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
! Task<br />
! Owner<br />
! Priority<br />
! Next Milestone<br />
! Notes<br />
|-<br />
| Create a proper todo list<br />
| Eben<br />
| High<br />
| <br />
| Help is welcomed!<br />
|-<br />
| Update the [[DesignTeam/Hig/Sugar|Human Interface Guidelines]]<br />
| Eben<br />
| Normal<br />
| <br />
| <br />
|-<br />
| Transfer designs from w.l.o<br />
| Eben<br />
| Normal<br />
| <br />
| It makes sense for current and future design work to live on w.s.o instead.<br />
|-<br />
|}<br />
<br />
=== Requested Tasks ===<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
! Task<br />
! Owner<br />
! Priority<br />
! Next Milestone<br />
! Notes<br />
|-<br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
|}<br />
<br />
<noinclude>=== Completed Tasks ===<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
! Task<br />
! Owner <br />
! Priority<br />
! Completion Date<br />
! Notes<br />
|-<br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
|}<br />
<br />
<br />
See the Community [[Sugar Labs/TODO|TODO]] list for more thing that need doing.<br />
[[Category:TestingTeam]]<br />
</noinclude></div>Ebenhttps://wiki.sugarlabs.org/index.php?title=Design_Team/TODO&diff=12942Design Team/TODO2008-12-10T17:03:54Z<p>Eben: /* Active Tasks */</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 }}<br />
{{TeamHeader|DesignTeam}}</noinclude><br />
<br />
=== Active Tasks ===<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
! Task<br />
! Owner<br />
! Priority<br />
! Next Milestone<br />
! Notes<br />
|-<br />
| Create a proper todo list<br />
| Eben<br />
| High<br />
| <br />
| Help is welcomed!<br />
|-<br />
| Style these todo tables reasonably<br />
| Eben<br />
| Normal<br />
| <br />
| <br />
|-<br />
| Update the [[DesignTeam/Hig/Sugar|Human Interface Guidelines]]<br />
| Eben<br />
| Normal<br />
| <br />
| <br />
|-<br />
|}<br />
<br />
=== Requested Tasks ===<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
! Task<br />
! Owner<br />
! Priority<br />
! Next Milestone<br />
! Notes<br />
|-<br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
|}<br />
<br />
<noinclude>=== Completed Tasks ===<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
! Task<br />
! Owner <br />
! Priority<br />
! Completion Date<br />
! Notes<br />
|-<br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
|}<br />
<br />
<br />
See the Community [[Sugar Labs/TODO|TODO]] list for more thing that need doing.<br />
[[Category:TestingTeam]]<br />
</noinclude></div>Ebenhttps://wiki.sugarlabs.org/index.php?title=Design_Team/TODO&diff=12939Design Team/TODO2008-12-10T17:02:11Z<p>Eben: /* Human Interface Guidelines */</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 }}<br />
{{TeamHeader|DesignTeam}}</noinclude><br />
<br />
=== Active Tasks ===<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
! Task<br />
! Owner<br />
! Priority<br />
! Next Milestone<br />
! Notes<br />
|-<br />
| Create a proper todo list!<br />
| Eben<br />
| High<br />
| <br />
| Help is welcomed.<br />
|-<br />
| Style these todo tables reasonably<br />
| Eben<br />
| Normal<br />
| <br />
| <br />
|-<br />
|}<br />
<br />
=== Requested Tasks ===<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
! Task<br />
! Owner<br />
! Priority<br />
! Next Milestone<br />
! Notes<br />
|-<br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
|}<br />
<br />
<noinclude>=== Completed Tasks ===<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
! Task<br />
! Owner <br />
! Priority<br />
! Completion Date<br />
! Notes<br />
|-<br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
|}<br />
<br />
<br />
See the Community [[Sugar Labs/TODO|TODO]] list for more thing that need doing.<br />
[[Category:TestingTeam]]<br />
</noinclude></div>Ebenhttps://wiki.sugarlabs.org/index.php?title=Design_Team/TODO&diff=12938Design Team/TODO2008-12-10T16:59:29Z<p>Eben: /* Requested Tasks */</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 }}<br />
{{TeamHeader|DesignTeam}}</noinclude><br />
<br />
=== Active Tasks ===<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
! Task<br />
! Owner<br />
! Priority<br />
! Next Milestone<br />
! Notes<br />
|-<br />
| Create a proper todo list!<br />
| Eben<br />
| High<br />
| <br />
| Help is welcomed.<br />
|-<br />
| Style these todo tables reasonably<br />
| Eben<br />
| Normal<br />
| <br />
| <br />
|-<br />
|}<br />
<br />
=== Requested Tasks ===<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
! Task<br />
! Owner<br />
! Priority<br />
! Next Milestone<br />
! Notes<br />
|-<br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
|}<br />
<br />
<noinclude>=== Completed Tasks ===<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
! Task<br />
! Owner <br />
! Priority<br />
! Completion Date<br />
! Notes<br />
|-<br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
|}<br />
<br />
===Human Interface Guidelines===<br />
* [[DesignTeam/Hig/Sugar|Cleanup and finish]]<br />
<br />
See the Community [[Sugar Labs/TODO|TODO]] list for more thing that need doing.<br />
[[Category:TestingTeam]]<br />
</noinclude></div>Ebenhttps://wiki.sugarlabs.org/index.php?title=Design_Team/TODO&diff=12937Design Team/TODO2008-12-10T16:58:49Z<p>Eben: /* Active Tasks */</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 }}<br />
{{TeamHeader|DesignTeam}}</noinclude><br />
<br />
=== Active Tasks ===<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
! Task<br />
! Owner<br />
! Priority<br />
! Next Milestone<br />
! Notes<br />
|-<br />
| Create a proper todo list!<br />
| Eben<br />
| High<br />
| <br />
| Help is welcomed.<br />
|-<br />
| Style these todo tables reasonably<br />
| Eben<br />
| Normal<br />
| <br />
| <br />
|-<br />
|}<br />
<br />
=== Requested Tasks ===<br />
{| border="1"<br />
|-<br />
! Task<br />
! Owner<br />
! Priority<br />
! Next Milestone<br />
! Notes<br />
|-<br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
|}<br />
<br />
<noinclude>=== Completed Tasks ===<br />
{| border="1"<br />
|-<br />
! Task<br />
! Owner <br />
! Priority<br />
! Completion Date<br />
! Notes<br />
|-<br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
|}<br />
<br />
===Human Interface Guidelines===<br />
* [[DesignTeam/Hig/Sugar|Cleanup and finish]]<br />
<br />
See the Community [[Sugar Labs/TODO|TODO]] list for more thing that need doing.<br />
[[Category:TestingTeam]]<br />
</noinclude></div>Ebenhttps://wiki.sugarlabs.org/index.php?title=Design_Team/TODO&diff=12931Design Team/TODO2008-12-10T15:25:44Z<p>Eben: /* Active Tasks */</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 }}<br />
{{TeamHeader|DesignTeam}}</noinclude><br />
<br />
=== Active Tasks ===<br />
{| border="1"<br />
|-<br />
! Task<br />
! Owner<br />
! Priority<br />
! Next Milestone<br />
! Notes<br />
|-<br />
| Create a proper todo list!<br />
| Eben<br />
| High<br />
| <br />
| Help is welcomed.<br />
|-<br />
| Style these todo tables reasonably<br />
| Eben<br />
| Normal<br />
| <br />
| <br />
|-<br />
|}<br />
<br />
=== Requested Tasks ===<br />
{| border="1"<br />
|-<br />
! Task<br />
! Owner<br />
! Priority<br />
! Next Milestone<br />
! Notes<br />
|-<br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
|}<br />
<br />
<noinclude>=== Completed Tasks ===<br />
{| border="1"<br />
|-<br />
! Task<br />
! Owner <br />
! Priority<br />
! Completion Date<br />
! Notes<br />
|-<br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
|}<br />
<br />
===Human Interface Guidelines===<br />
* [[DesignTeam/Hig/Sugar|Cleanup and finish]]<br />
<br />
See the Community [[Sugar Labs/TODO|TODO]] list for more thing that need doing.<br />
[[Category:TestingTeam]]<br />
</noinclude></div>Eben