Changes

m
fix camelcase links
Line 40: Line 40:  
8. Developers meeting: The next Sugar developers meeting is scheduled for Thursday, 25 September at 14.00 (UTC). At this meeting, we want to form the Sugar Labs Bugsquad, a quality assurance (QA) team for Sugar. The squad will keep track of current bugs and try to make sure that major bugs do not go unnoticed by developers. You do not need any programming knowledge to be in the Bugsquad; in fact it is a great way to return something to the Sugar community if you cannot program. The Sugar Labs bugsquad is modeled on the [http://developer.gnome.org/projects/bugsquad GNOME bugsquad].
 
8. Developers meeting: The next Sugar developers meeting is scheduled for Thursday, 25 September at 14.00 (UTC). At this meeting, we want to form the Sugar Labs Bugsquad, a quality assurance (QA) team for Sugar. The squad will keep track of current bugs and try to make sure that major bugs do not go unnoticed by developers. You do not need any programming knowledge to be in the Bugsquad; in fact it is a great way to return something to the Sugar community if you cannot program. The Sugar Labs bugsquad is modeled on the [http://developer.gnome.org/projects/bugsquad GNOME bugsquad].
   −
9. Design meeting: Eben Eliason reports that the first design meeting was a bit more technical than anticipated, but we did make some progress on a visual clipboard API and icon reviews [[DesignTeam/Meetings#Thursday_September_18.2C_2008_-_15.30_.28UTC.29|Minutes can be found in the wiki]].
+
9. Design meeting: Eben Eliason reports that the first design meeting was a bit more technical than anticipated, but we did make some progress on a visual clipboard API and icon reviews [[Design Team/Meetings#Thursday_September_18.2C_2008_-_15.30_.28UTC.29|Minutes can be found in the wiki]].
    
10. API documentation: David Farning has been leading an effort to document the Sugar API. With help from Pauli Virtanen, Janet Swisher, and Marco Pesenti Gritti, we now have a wiki-based tool (See [http://sugarlabs1.xen.prgmr.com]). Follow the instructions at [http://sugarlabs1.xen.prgmr.com/pydocweb/wiki/getting_started/ getting started]. Don't worry about being perfect, someone will come along and clean up the docstrings before they are committed back to the git tree. (The patches are flowing into the git tree correctly, but if you find bugs, please let us know: this is the first time pydocweb has been used "in the wild.")
 
10. API documentation: David Farning has been leading an effort to document the Sugar API. With help from Pauli Virtanen, Janet Swisher, and Marco Pesenti Gritti, we now have a wiki-based tool (See [http://sugarlabs1.xen.prgmr.com]). Follow the instructions at [http://sugarlabs1.xen.prgmr.com/pydocweb/wiki/getting_started/ getting started]. Don't worry about being perfect, someone will come along and clean up the docstrings before they are committed back to the git tree. (The patches are flowing into the git tree correctly, but if you find bugs, please let us know: this is the first time pydocweb has been used "in the wild.")
2,751

edits