<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jul 18, 2014 at 12:46 PM, Martin Abente <span dir="ltr"><<a href="mailto:martin.abente.lahaye@gmail.com" target="_blank">martin.abente.lahaye@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hello everyone,<div><br></div><div>This is a summary of the topics we discussed in our first development meeting. Logs can be found here [1].</div>
<div><br></div><div><b>Topic #1: What should we do for 0.104?</b></div>
<div><ul><li>Focus on core ideas:<br></li><ul><li>Fix or re-work collaboration? Cover web activities integration.</li><li>Make Sugar more customizable? Get rid of control panel by converting sections into applications. Make sugar itself modifiable like activities. </li>
<li>Make student assessment part of the sugar experience? Think of ways in which all these statistics gathering efforts can become part of this.</li></ul></ul></div></div></blockquote><div>For the record, I am not convinced that statistics gathering is the key to assessing the Sugar experience. This is perhaps more of a research project than a deployment topic at this point in time.</div>
<div><br></div><div>-walter </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><ul><li>Performance enhancements:<br></li><ul><li>Make Sugar more responsive? Starting by the journal.</li>
<li>Make activities launch time faster? Moving common bits to sugar-toolkit, ie., text-to-speech.</li></ul></ul></div><div><ul><li>Cover other classroom needs:<br></li><ul><li>Printing in Sugar?</li><li>Integrate screen sharing in Sugar?</li>
</ul></ul></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div><div>These are initial suggestions, we all agreed that collaboration and performance should be prioritized.</div></div></blockquote><div>
<br>
</div><div><b>Topic #2: How do we do it?</b></div><div><ul><li>Keep the current structure for phases and deadlines, ie., [2].<br></li><li>Keep the 6 months release schedules.<br></li><li>Find a way to re-sync with Gnome [3] and Fedora [4], so we can achieve the previous item.<br>
</li><li>Have regular development meetings. Each 2 weeks? Each month?<br></li><li>Have at least one code sprint for each release, ie., SF meeting in Oct/14, and UY youth summit in Sept/14.<br></li><li>Request for former Sugar developers guidance.</li>
<li>Share design team responsibilities among all of us.</li><li>Document maintainers and responsibilities.</li></ul></div><div><b>Topic #3: What are the Infrastructure needs?</b></div><div><ul><li><u>Bring Pootle back to life</u>! Call for a special meeting regarding this.<br>
</li><li>Move activities repositories to github?</li><li>Set up a discourse instance (GSoC project)?</li></ul></div><div><br></div><div>Many thanks to gonzalo, walterbender, llaske, bashintosh and satellit for joining and contributing to the meeting!</div>
<div><br></div><div>Saludos,</div><div>tch.</div><div><br></div><div><u>Refs:</u></div><div><ol><li><a href="http://meeting.sugarlabs.org/sugar-meeting/meetings/2014-07-18T13:29:08.html" target="_blank">http://meeting.sugarlabs.org/sugar-meeting/meetings/2014-07-18T13:29:08.html</a><br>
</li><li><a href="http://wiki.sugarlabs.org/go/0.100/Roadmap" target="_blank">http://wiki.sugarlabs.org/go/0.100/Roadmap</a><br></li><li><a href="https://wiki.gnome.org/ThreePointThirteen" target="_blank">https://wiki.gnome.org/ThreePointThirteen</a><br>
</li><li><a href="http://fedoraproject.org/wiki/Releases/21/Schedule" target="_blank">http://fedoraproject.org/wiki/Releases/21/Schedule</a></li></ol></div><div><br></div></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Walter Bender<br>Sugar Labs<br><a href="http://www.sugarlabs.org">http://www.sugarlabs.org</a><br>
</div></div>