Search results

Jump to navigation Jump to search
Results 1 – 22 of 134
Advanced search

Search in namespaces:

  
  
  
  
  
  
  
  
  
  

Page title matches

  • {{Obsolete | Please refer to [[Development Team/Meetings]] instead}} * meetings should be announced in advance on the sugar and iaep mailing lists
    981 bytes (148 words) - 21:44, 19 December 2016

Page text matches

  • ==Sugar Digest== ...ar. Check out http://proyectofedora.org/argentina/?p=320 for an example of how Turtle Art has been modified by some of our end users!! Free Software rock
    2 KB (366 words) - 11:07, 13 May 2011
  • == Sugar Digest == It has been a very exciting week. (You may have noticed, I don't often use adverbs, but '
    2 KB (389 words) - 17:18, 17 December 2012
  • == Sugar Digest == .... Please try [[Activities/Portfolio|Portfolio]] and give me feedback as to how I can improve it.
    3 KB (552 words) - 11:26, 1 December 2011
  • == Sugar Digest == ...er Corporation], which is distributing Sugar and GNOME on Fedora 16 across a variety of platforms. In their GNOME shell, they include Etoys and Scratch,
    5 KB (780 words) - 18:56, 10 June 2012
  • == Sugar Digest == ...wn to a short list. Many thanks to everyone who has lent a hand so far and to Google for giving us this opportunity.
    4 KB (678 words) - 20:36, 15 July 2013
  • ===Sugar Digest === ...ing lists and in the chat rooms, it is readily apparent that Sugar and the Sugar community are growing in both size and stability. Thank you.
    4 KB (559 words) - 22:57, 28 July 2010
  • * Receive report from Google Code-in project team, ...made by Membership and Elections Committee and the Google Code-in project team.
    4 KB (586 words) - 18:55, 1 February 2019
  • == Sugar Digest == ...l permission). Watching their growth from Sugar user to Sugar developer to Sugar mentor is especially rewarding.
    5 KB (918 words) - 15:04, 5 December 2015
  • === Sugar Digest === ...e more deployment guides and lesson plans are being written, we still lack a compelling narrative.
    5 KB (865 words) - 09:31, 19 December 2016
  • <noinclude>{{TeamHeader|Infrastructure Team}}{{TOCright}} ...opposed to all clients accessing the same central server, thereby causing a bottleneck near that server.
    5 KB (818 words) - 21:10, 9 August 2014
  • === Sugar Digest === ...ugar Labs, we have a lot to reflect upon in 2009 and a lot to look forward to in 2010.
    5 KB (906 words) - 19:37, 27 July 2010
  • ===Sugar Digest=== ...fer to load Sugar onto recycled USB flash drives and sending them to Sugar Labs for global deployment.
    8 KB (1,360 words) - 19:37, 27 July 2010
  • <noinclude>{{TeamHeader|Sugar Labs|home=Community Home|meeting_link=Events|meeting_label=Events Calendar}} [[Category:Team]]
    10 KB (1,397 words) - 13:37, 8 October 2024
  • | [[Documentation Team|english]] &#124; [[Documentation Team/lang-es|español]] }} <noinclude>{{TeamHeader|Documentation Team|home=Documentation}}</noinclude>
    5 KB (808 words) - 17:13, 29 April 2020
  • <noinclude>{{TeamHeader|Sugar on a Stick|home=Project Home|xbgColor=ffe792|join_label=Get Involved}} <big>'''Frequently Asked Questions about Sugar on a Stick'''</big>
    7 KB (1,132 words) - 21:34, 5 February 2014
  • === Sugar Digest === ...it is helpful to discuss the Journal as a tool for reflection, not just as a replacement for the file system.
    7 KB (1,046 words) - 09:33, 19 December 2016
  • ==Sugar Digest== ...schools to make any major changes to their current Sugar processes. Kudos to the Design, Developer, and Testing teams for all their contributions.
    4 KB (708 words) - 11:04, 17 October 2010
  • === Sugar Digest === ...sic, browsing, reading, writing, programming, graphics, etc.—they are able to engage in debugging both their personal expression and the very tools that
    7 KB (1,117 words) - 08:31, 19 December 2016
  • === Sugar Digest === ...le.php?story=20090918110925298 Groklaw] (with lots of help from Sean); and a presentation at Software Freedom Day.
    5 KB (844 words) - 19:37, 27 July 2010
  • ...ivity API]]. This page documents how it is possible to use Mono to write a Sugar activity. With Mono, you can use any underlying language like C# or Boo. To write an OLPC Mono activity, you need to prepare a .xo [[Bundle]] including all required libraries. This is necessary because
    7 KB (1,072 words) - 17:39, 30 August 2009

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