Search results

Jump to navigation Jump to search
  • noinclude>{{GoogleTrans-en}}{{TeamHeader|Development Team|roadmap_link={{Upcoming Stable Release}}/Roadmap}}</noinclude> ==Sucrose Development==
    3 KB (370 words) - 18:56, 5 July 2009
  • * Fetch dependencies from [[Development Team/Jhbuild|sugar-jhbuild]] (native sugar building system) * '''sugar-platform''' provides [[0.84/Platform Components|Sugar Platform]]
    1 KB (173 words) - 14:28, 3 July 2012
  • ...s about how our computers could help to advance our children’s educational development. The new essay begins with a quote from George Pólya. ...dation grants (all four are linked to from the [[Deployment Team#Proposals|Deployment page]]).
    6 KB (850 words) - 09:31, 19 December 2016
  • ...ke OLPC are more centralized by their nature and have absolutely different deployment schemes. And, of course, both schemes are important and useful. ...Sugar release. For example, the latest OLPC Sugar is <s>0.82, next will be 0.84, but the latest stable version is 0.88</s>.
    5 KB (756 words) - 10:13, 3 July 2011
  • To install [[0.84/Platform Components|Sugar Platform]]<br>'''NOTE''' In most cases you don't * '''Development release'''<br>To install last release in development cycle use ACCEPT_KEYWORDS ''~x86'' or ''~amd64''
    2 KB (362 words) - 21:42, 1 July 2012
  • ...p of the Sugar platform. Marco has been doing good work on a [[Development Team/Release/Roadmap|release roadmap]] and establishing a release cycle. ...needed to reduce the barrier to entry to test and use Sugar. Greg and his team have been getting Sugar prepared on [[Fedora]]. Jonas has been shouldering
    3 KB (477 words) - 14:19, 3 July 2012
  • <noinclude>{{TeamHeader|Activity Team}}{{TOCright}} : '''[[Talk:Activity Team/FAQ | Post questions here]]''' for the [[Activity Team]].
    7 KB (1,161 words) - 22:11, 16 January 2018
  • ...those packaging Sugar for deployment on specific hardware or doing a Sugar deployment. Our product is the support of those efforts. ...g the development of Sugar were necessary in the creation of Sugar and the development of Sugar ”products” will require dedicated in-kind contributions from i
    7 KB (1,128 words) - 19:37, 27 July 2010
  • ...o process. We should consider different structures for different levels of development within the early, elementary, and middle-school years. A "Madlibs"-like for ...t are important for the future growth of Sugar Labs: vision, distribution, deployment, quality assurance, and infrastructure. Please help us fill in the schedule
    7 KB (1,046 words) - 09:33, 19 December 2016
  • {{TeamHeader|Translation Team}} ...e an up to date list of common questions that we get about the Translation Team. This page contains many frequently-asked questions along with some answers
    14 KB (2,320 words) - 21:35, 5 February 2014
  • 1. Now that the Sugar community and the Release Team have wrapped up 0.84, it is time to talk about our “Big Overarching Vision Goals for 2009” I ...-thinking skills, and to further the development of diverse communities of development and support around the needs of teachers and learnings. Children are not of
    10 KB (1,562 words) - 19:37, 27 July 2010
  • ...t half of the meeting due to a scheduling conflict, but by all [[Marketing Team/Events/Sugarcamp Boston 2008/Minutes|reports]] it was a productive three da * Brendan Powers talked about the various LTSP deployment approaches taken by Resara when they work with schools and how Sugar could
    7 KB (1,144 words) - 09:31, 19 December 2016
  • ...ity to communicate lively by serial port with an Arduino (an open hardware development board). This feature most be ported to the 0.88 version, and also add the p * '''What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - A
    6 KB (900 words) - 19:03, 6 April 2010
  • ...oyment team pages; and the unveiling of a new Sugar Labs logo ([[Marketing Team/Logo]]). [[Oversight Board/Meeting_Minutes-2008-09-19|Minutes can be found ...scussion of our 0.84 goals in the wiki ([[Development Team/Release/Roadmap/0.84#Goals|here]]). They have assigned owners and peers to all groups and starte
    8 KB (1,252 words) - 09:34, 19 December 2016
  • <noinclude>{{TeamHeader|Activity Team}}</noinclude> ...#daffd5; padding: 10px; border: 1px solid #cde7a8" align=left>The Activity team will be holding regular bi-weekly meetings on Monday at 15:00 UTC on irc.fr
    8 KB (1,246 words) - 07:38, 24 October 2011
  • ...organize/liaison with the Test committee; I will organize/liaison with the Deployment committee. Please contact us if you have interested in participating on one ...ng a comprehensive analysis of reliable research undertaken to date on the deployment of low-cost ICT to support education goals around the world with an emphasi
    7 KB (1,036 words) - 08:28, 19 December 2016
  • ...sure to note here as well if this feature has been requested by a specific deployment, or if it has emerged from a bug report.'' ''If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "None necessar
    5 KB (772 words) - 08:51, 25 July 2014
  • ** Help expand the community to include development of pedagogy; models of use; etc. ...e discussion begs the question of how Sugar Labs can rise above day-to-day deployment headaches in order to ensure that there is a solid foundation being built.
    8 KB (1,242 words) - 08:27, 19 December 2016
  • ...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
    6 KB (1,057 words) - 19:37, 27 July 2010
  • * [[Archive/Current Events/2011-09-20|2011-08-22]] ...the OLPC engineering team threw in a few additional sensors. * [[Archive/Current Events/2011-07-09|2011-06-28]] the translation team has been reaching out...
    22 KB (3,188 words) - 20:10, 6 November 2017

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)