Search results

<noinclude>{{TeamHeader|Packaging Team}}{{Stub}}</noinclude> {{Merge|Development Team/Packaging}}

...ubtedly get feedback about bugs—we are still too thin on the testing (Bug) team, but nonetheless, we are on a trajectory towards a much improved product th The Localization team has been busy. We have almost complete support for more than 25 languages a

...with those packaging the GNU/Linux distributions and downstream with those packaging Sugar for deployment on specific hardware or doing a Sugar deployment. Our === Community jams, meet-ups, and meetings ===

<noinclude><div class="noprint">{{TeamHeader|Activity Team}}</div></noinclude> {{:Activity Team/Mission}}

...learning opportunities for children. (Kudos to Sean Daly and the Marketing Team for their efforts in getting the word out.) ...tent and process. There has been a productive dialog between the packaging team, the developers, testers, and the user community; as a result, we are conve

...he Fedora packaging team as well as Sean Daly and the Sugar Labs marketing team (we got unprecedented international coverage). Simon Schampijer organized a The bookends were the FOSSed and NECC meetings. Caroline Meeks and I ran a workshop for teachers at [http://www.fossed.com

1. Now that the Sugar community and the Release Team have wrapped up 0.84, it is time to talk about our “Big Overarching Visio ...r. We have laid the ground-work over the past six months, working with the packaging teams of a number of GNU/Linux distributions; now is the time to leverage t

[[Category:Team]] == [[:Category:Team|Teams]] ==

:'''<tomeu>''' dfarning: what about packaging the XS stuff inside the ltsp server itself? :'''<tomeu>''' we could discuss this stuff in the developer meetings?

...'' I expect that we're going to have to do some of that in the engineering meetings. :'''<gregdek>''' Engineering meetings at release time should be: "which bugs are hot, and what's our status on th

<noinclude>{{TeamHeader|Development Team|roadmap_link={{Upcoming Stable Release}}/Roadmap}}__NOTOC__ [[Category:Development Team]]

:'''<walter>''' The budget break down is essentially support for meetings ($ for Greg's Event committee) and engineering support :'''<walter>''' I think this is something the deployment team should be handling: getting requirements and communicating them clearly

...adiness to help out - either joining [[BugSquad|bug squad]] and [[BugSquad/Meetings|helping]] to [[BugSquad/Triage Guide|triage]], or actually helping fix some ..._.28not_fulfilled_yet.29|Version support]] for [[Journal]] / [[Development Team/Almanac/sugar.datastore.datastore|DataStore]]: Start with (old) [http://wik

(06:58:52 PM) tomeu: bemasc: do you know if OLPC has now a testing team? (06:59:53 PM) dirakx: afaik OLPC doesn't have such a team.

* Not specific: Improve communication between Team X and Team Y. ...fic: Write a working module for Web App Q that creates a service queue for Team X to do Task Z more efficiently.