Development Team/Meetings

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

• http://dev.laptop.org/~erikos/sugar-dev-301007.log

(all the meeting logs go here: http://www.pseudorandom.co.uk/tmp/freenode-olpc-meeting.log)

• How do we log the meeting. (see above)
• 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.

Who is where:

bertf: Germany
Cassidy: BE
daf: UK
edsiper: Chile
Erikos: Germany
hmmmbird: SA
marcopg: Italy
morgs: SA
Sjoerd: NL
smcv: UK

bertf:		E-toys, implementing tubes
Smcv:		audit/improve tubes usage
edsiper:	developer console: stripping down, composed of 3 activities: Analyze, Log, Terminal http://wiki.laptop.org/go/Developer_Environment
cassidy:	finishing stream tubes in Salut
morgs:		working on PresenceService reliability improvements, Connect
sjoerd:		finishing 
hmmmbird:	WorldWideWorkshop Joke Machine (waiting #3060)
marcopg:	had meeting with Ivan and Tomeu about backups, marcopg & Tomeu do sugar side, Ivan client/server (school server), fighting with build system
erikos:		works on control panel, functioning version
tomeu:		next to backups, screenshots
uwogBB:	Implement support for custom keybindings, develop AbiCollab debug tooling, Implement "find" support in Write (done)

ACTIONS:

bertf:		talk to smcv about tubes
marcopg:	list of activities, list of modules, assign some sugar + activity tickets to rwh, drop the created xm branch and create an update1 one

morgs:		talk to jg about getting bot up for logs
smcv:		post logs at: http://www.pseudorandom.co.uk/tmp/freenode-olpc-meeting.log
erikos: 	check for #4022 everything for 'Hint write about using txt with a view_source property' seems in place already

erikos: 	control panel, user preferences:do not move olpc-update into script, fix radio on/off, restart sugar
hmmmbird:	Correct way to get access to temporary file space during activity execution ? should use use get_activity_root() instead of /tmp 
everyone: 	read Walter's mail for clarification of the names (Update1 etc)
module_owners: module owners should create update1 branches as necessary (help: http://wiki.laptop.org/go/Git_Tips)

• The branch/build procedure discussion is moved to the journal/tubes meeting