Design Team/Meetings

From Sugar Labs
< Design Team
Revision as of 05:36, 11 December 2010 by Sascha silbe (talk | contribs) (→‎Logs: fix link to logs)
Jump to navigation Jump to search

Team Home   ·   Join   ·   Contacts   ·   Resources   ·   FAQ   ·   Vision   ·   To Do   ·   Meetings

The Sugar Labs Meetings calendar is available in a variety of formats at these links: XML.gif ICal.gif HTML.gif.

To convert UTC to your local time, use this converter or run:

date -d '[current date] [time] UTC'
date -d '2008-06-03 14:00 UTC'

Upcoming IRC meeting: Unscheduled

Please discuss the following on

  • Start new/Resume functionality in Home view
  • Journal backup UI (Patch from Martin Abente, Patch from Sascha Silbe)
  • Alerts (Patch from Anish Mangal) and notifications
  • Uncaught exception handler (#2063)
  • How to handle start-up delay due to data store migration (#1546)?
  • "Your Journal is empty" shown for unreadable storage media (#1810)
  • invalid/unknown colors are shown as owner colors (#1750)
  • Erasure of downloaded Activity entries in Journal permanently removes the code bundle (#1512)
  • Drop down menus give no indication of their existence, also are too slow to load (#1169, Patch from Michael Stone)

We should also go through open tickets filed against component design some time.

Who and what

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.

In general, discussion focuses on:

  • high level design goals and ideas
  • feedback and discussion of problems in the current design
  • reviews of design proposals

Adding topics

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.

Past meetings

Saturday 10 July 2010 14:30 UTC

Sunday 16 August 2009 09:40 UTC

Summary & log - Sugar 0.86 Design

Saturday 09 May 2009 10:00 EDT

Summary & log.


Sunday 19 April 2009 13:00 UTC / 9:00 EDT



We discussed design goals for the next release 0.86. Design mockups will be created in response to the high-level features listed below (potentially in advance of SugarCamp 2009 on May 16th), to further illustrate the design intent and allow for integration with the development schedule.

High-level feature recap:

  • polish activity list in Home
  • support filtering/searching via tags in Home
  • add list views to groups/neighorhood
  • make groups dynamic (like neighborhood)
  • extend activity chat
  • add overlay chat to groups/neighborhood
  • design a bulletin-board _activity_
  • remove management from activity list, ensure _all_ installed activities are in Journal
  • new toolbar design

Concrete design/development tasks:

  1. design mockups to make the frame more discoverable
  2. design mockups to polish the new toolbars
  3. Home list view: remove the date column and enable alphabetical sort. Label versions "Version x"
  4. Design mockups for tagging/filtering/search within Home view
  5. Draft changes to file to support tagging
  6. Design mockups for overlay chat in groups/neighborhood (should also include revising the activity chat..which exists but not as earlier designs proposed)
  7. Design mockups of bulletin board activity
  8. Design mockups for list views in groups and neighborhood

Saturday 21 March 2009 14:00 UTC / 10:00 EDT



Discussion of the Home view and whether to abandon the notion of favorites for a single consolidated view

See Design Team/Proposals.

Unify look of web services

(Marketing Team) Tuesday 10 March 2009 13:00 UTC / 09:00 EDT


Sun March 1, 2009 - 13.00 (UTC) / 10.00 EST

Logs: Design Team/Meetings/09.03.01


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.

Other topics: Discuss development roadmap and prioritize design activities for next build

Friday December 19, 2008 - 15.30 (UTC)


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.

Thursday December 4, 2008 - 15.30 (UTC)


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.



Wednesday November 26, 2008 - 15.00 (UTC)

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.


Short Term Roadmap Definition

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.

Resuming activities from Home
Enhancing the Journal
Improving Toolbars
Encouraging Naming/Tagging


Thursday September 18, 2008 - 15.30 (UTC)


Visual Clipboard API

For reference, please see the clipboard specification. For a more targeted list of features and goals, please see the clipboard planning page.

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.

Some references:

Advancing the Journal

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 here.

Due to the lengthy clipboard discussion, we didn't hit this topic today. We'll pick it up first thing next week.

Icon reviews

We discussed three icons today.

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.

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 [ 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.

Access Point: Recent experience reports have indicated that the removal of an identifier of the connected AP is frustrating. The proposal discussed is shown [1], 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.

Additionally, these 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.