10,579
edits
Changes
mLine 30:
Line 30: − +
→Tech Talk
6. Developer meetings: Weekly sugar developers meetings were restarted this past week; meetings are Thursdays at 17:00 (UTC) on irc.freenode.net, on the #sugar-meeting channel (Please see [[DevelopmentTeam/Meetings]]). You are invited to join; please add topics that you'd like to discuss (Instructions are in the wiki at [[DevelopmentTeam/Meetings#How_to_add_topics]]).
6. Developer meetings: Weekly sugar developers meetings were restarted this past week; meetings are Thursdays at 17:00 (UTC) on irc.freenode.net, on the #sugar-meeting channel (Please see [[DevelopmentTeam/Meetings]]). You are invited to join; please add topics that you'd like to discuss (Instructions are in the wiki at [[DevelopmentTeam/Meetings#How_to_add_topics]]).
7. Review process: Simon Schampijer has written up notes about the code-review process (Please see http://wiki.sugarlabs.org/go/DevelopmentTeam/CodeReview).
7. Review process: Simon Schampijer has written up notes about the code-review process (Please see[[DevelopmentTeam/CodeReview]]).
8. Auto-documentation: As mentioned above, David Faring has put together an alpha version of an automated API documentation system (Please see [http://www.sugarlabs.org/~dfarning/]). The APIs are generated using epydoc, which only documents Python files; any C code (or other languages) are not documented.
8. Auto-documentation: As mentioned above, David Faring has put together an alpha version of an automated API documentation system (Please see [http://www.sugarlabs.org/~dfarning/]). The APIs are generated using epydoc, which only documents Python files; any C code (or other languages) are not documented.