Changes

1,060 bytes added ,  04:12, 8 July 2010
→‎Upcoming meeting: 10 July 2010 14:30 UTC: added topics from mailing list and bug tracker
Line 11: Line 11:  
* http://lists.laptop.org/pipermail/devel/2010-July/029187.html
 
* http://lists.laptop.org/pipermail/devel/2010-July/029187.html
 
*: We'll be reviewing designs for the proposed Start new/Resume functionality in Home view. Please join!<br>Thanks,  Christian
 
*: We'll be reviewing designs for the proposed Start new/Resume functionality in Home view. Please join!<br>Thanks,  Christian
 +
*: Journal backup UI ([http://patchwork.sugarlabs.org/patch/174/ Patch] from Martin Abente, [http://patchwork.sugarlabs.org/patch/171/ Patch] from Sascha Silbe)
 +
*: Alerts ([http://patchwork.sugarlabs.org/patch/161/ Patch] from Anish Mangal) and notifications
 +
*: Uncaught exception handler ({{Bug|2063}})
 +
*: How to handle start-up delay due to data store migration ({{Bug|1546}})?
 +
*: "Your Journal is empty" shown for unreadable storage media ({{Bug|1810}})
 +
*: invalid/unknown colors are shown as owner colors ({{Bug|1750}})
 +
*: Erasure of downloaded Activity entries in Journal permanently removes the code bundle ({{Bug|1512}})
 +
*: Drop down menus give no indication of their existence, also are too slow to load ({{Bug|1169}}, [http://people.sugarlabs.org/bernie/sugar/sugar-0.88-patches/sugar-toolkit/kill-the-delayed-menus-for-good.patch Patch] from Michael Stone)
 +
 +
We should also go through [http://bugs.sugarlabs.org/query?component=design&status=accepted&status=assigned&status=new&status=reopened open tickets filed against component design] some time.
 +
 
== Who and what==
 
== 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.
 
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.
344

edits