Changes
Jump to navigation
Jump to search
Development Team/Meetings (view source)
Revision as of 10:40, 30 October 2007
, 10:40, 30 October 2007→Tuesday October 30
==About==
* Quick update about what we have been working on and eventually the problems we have run into.
* Discussion about the implementation details of tickets we are planning to work on. Figure out how to split up the work and who should be owning the various parts.
* Questions from activity authors about specific aspects of the platform and more in general on how to better integrate their activity in Sugar. Report about problems they run into.
* Help out new contributors to figure out where to start. Point out the tickets we need help with, discuss with them the implementation.
==When and where==
Every tuesday on irc.freenode.net, in the #olpc-meeting channel. The time is not well defined yet but this week we scheduled it at 10am EDT (3pm CET). Starting from next week we might move it to a later time to facilitate US developers to participate.
==Who==
The meeting is mainly targeted to Sugar core and activity developers, but everyone interested is welcome to join. It's primary purpose is to try to open up a bit the development, make it more transparent and allow the community to participate more easily.
==Meetings==
===Tuesday October 30===
* How do we log the meeting.
* Quick status updates.
* Reinier introduction.
* #4022 browser cannot open files generated by view source.
* #3239 Control Panel, user preferences
* Correct way to get access to temporary file space during activity execution ?
* Update1. Branching and trac.
* Module maintainers. Distribute the release duties.
* Managing the build system chaos. (idea: coordinated releases of the Sugar core. What is core?)
* How do we bring back joyride into shape.
* What API changes to expect before next milestone.
* Correct way to get access to temporary file space during activity execution ?
* Quick update about what we have been working on and eventually the problems we have run into.
* Discussion about the implementation details of tickets we are planning to work on. Figure out how to split up the work and who should be owning the various parts.
* Questions from activity authors about specific aspects of the platform and more in general on how to better integrate their activity in Sugar. Report about problems they run into.
* Help out new contributors to figure out where to start. Point out the tickets we need help with, discuss with them the implementation.
==When and where==
Every tuesday on irc.freenode.net, in the #olpc-meeting channel. The time is not well defined yet but this week we scheduled it at 10am EDT (3pm CET). Starting from next week we might move it to a later time to facilitate US developers to participate.
==Who==
The meeting is mainly targeted to Sugar core and activity developers, but everyone interested is welcome to join. It's primary purpose is to try to open up a bit the development, make it more transparent and allow the community to participate more easily.
==Meetings==
===Tuesday October 30===
* How do we log the meeting.
* Quick status updates.
* Reinier introduction.
* #4022 browser cannot open files generated by view source.
* #3239 Control Panel, user preferences
* Correct way to get access to temporary file space during activity execution ?
* Update1. Branching and trac.
* Module maintainers. Distribute the release duties.
* Managing the build system chaos. (idea: coordinated releases of the Sugar core. What is core?)
* How do we bring back joyride into shape.
* What API changes to expect before next milestone.
* Correct way to get access to temporary file space during activity execution ?