Difference between revisions of "Design Team/Meetings"
(New page: <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...) |
|||
Line 28: | Line 28: | ||
=== Thursday September 18, 2008 - 15.30 (UTC) === | === Thursday September 18, 2008 - 15.30 (UTC) === | ||
==== Topics ==== | ==== Topics ==== | ||
− | + | ===== Visual Clipboard API ===== | |
+ | For reference, please see the [http://wiki.laptop.org/go/Specifications/Clipboard clipboard specification]. | ||
+ | ===== 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. | ||
[[Category:DevelopmentTeam]] | [[Category:DevelopmentTeam]] |
Revision as of 11:54, 15 September 2008
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
When and where
- Biweekly, 1st and 3rd Thursdays
- 15.30 (UTC)
- irc.freenode.net, #sugar-meeting
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'
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.
Meetings
Thursday September 18, 2008 - 15.30 (UTC)
Topics
Visual Clipboard API
For reference, please see the clipboard specification.
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.