Search results

Jump to navigation Jump to search

Page title matches

Page text matches

  • {{TeamHeader|Documentation Team}} ...o date list of common questions that we get about the [[Documentation Team|Documentation Team]]. This page contains many frequently-asked questions along with some
    2 KB (315 words) - 20:15, 24 February 2010
  • {{Developers}} *[[Documentation Team | Documenters]]
    2 KB (343 words) - 21:33, 23 February 2010
  • == Resources for developers == * [[Dextrose/Building|Dextrose Build System Documentation]]
    1,018 bytes (122 words) - 00:33, 17 May 2016
  • Let activity and service developers rely on present of particular glucose release. This service is a [[Documentation Team/Services/Native packages usage|wrapper]] for native package thus its v
    2 KB (270 words) - 07:11, 18 May 2010
  • ...or 0install packages depend on this service? Are there changes outside the developers' control on which completion of this service depends? In other words, does == Documentation ==
    2 KB (293 words) - 17:46, 25 November 2010
  • ...or 0install packages depend on this service? Are there changes outside the developers' control on which completion of this service depends? In other words, does == Documentation ==
    2 KB (290 words) - 17:44, 25 November 2010
  • GObject based library to provide high level client API for what activity developers might need to code collab activities. This service is a [[Documentation Team/Services/Native packages usage|wrapper]] for native package thus its v
    3 KB (395 words) - 17:41, 25 November 2010
  • <noinclude>{{TeamHeader|Documentation Team}}[[Category:Contact]]</noinclude> {{:Documentation Team/Coordinator}}
    689 bytes (84 words) - 15:27, 2 November 2011
  • .../important|Please note|See this [http://developer.sugarlabs.org/ developer documentation website] for the '''sugar-build''' development environment.}} '''Are you looking for [[Activity_Team/Resources|documentation on how to create Sugar Activities]]?'''
    4 KB (560 words) - 17:33, 22 July 2014
  • This service is a [[Documentation Team/Services/Native packages usage|wrapper]] for native package thus its v ...or 0install packages depend on this service? Are there changes outside the developers' control on which completion of this service depends? In other words, does
    3 KB (383 words) - 17:45, 25 November 2010
  • === For developers === === For non-developers ===
    3 KB (531 words) - 20:08, 24 February 2010
  • This service is a [[Documentation Team/Services/Native packages usage|wrapper]] for native package thus its v ...or 0install packages depend on this service? Are there changes outside the developers' control on which completion of this service depends? In other words, does
    3 KB (383 words) - 17:41, 25 November 2010
  • Everything that developers need to start developing native sugar activities. Library depends on all ot This service is a [[Documentation Team/Services/Native packages usage|wrapper]] for native package, thus its
    3 KB (461 words) - 17:47, 25 November 2010
  • Allow developers to create activities using Flash tools. Flash developers will be able to create content for activities with the same tools and skill
    2 KB (229 words) - 15:28, 5 November 2013
  • * Have overall project documentation * Have more detailed documentation of certain areas
    3 KB (457 words) - 22:19, 5 September 2010
  • {{Note/note|Note|This page was imported from the OLPC wiki. See [[OLPC:Developers manual]].}} * [[Developers/Stack]]
    3 KB (431 words) - 14:11, 3 July 2012
  • * Translating the Sugar Documentation (e.g. FLOSSManuals) ...ip with FLOSS Manual at http://en.flossmanuals.net/ . Translation of that documentation uses FLOSS Manual tools.
    3 KB (409 words) - 11:03, 14 May 2016
  • Since this module makes it simpler to create an activity framework, developers new to Sugar can more readily make Sugar activities; in this way we may get This extension to the toolkit doesn't impact any existing work: developers can choose to use SimpleActivity/SharedActivtiy or continue doing everythin
    2 KB (302 words) - 22:28, 21 November 2013
  • ...or 0install packages depend on this service? Are there changes outside the developers' control on which completion of this service depends? In other words, does == Documentation ==
    2 KB (343 words) - 17:45, 25 November 2010
  • ...or 0install packages depend on this service? Are there changes outside the developers' control on which completion of this service depends? In other words, does == Documentation ==
    2 KB (348 words) - 17:47, 25 November 2010
  • ...or 0install packages depend on this service? Are there changes outside the developers' control on which completion of this service depends? In other words, does == Documentation ==
    2 KB (330 words) - 17:43, 25 November 2010
  • ...or 0install packages depend on this service? Are there changes outside the developers' control on which completion of this service depends? In other words, does == Documentation ==
    2 KB (345 words) - 07:12, 18 May 2010
  • == Documentation == ...g list or during a meeting? Link to that material here so other interested developers can get involved.''
    2 KB (214 words) - 04:33, 27 April 2012
  • {{Developers}} * [[Developers/Setup|개발자/구축]]
    3 KB (76 words) - 21:33, 23 February 2010
  • ''What work do the developers have to accomplish to complete the feature in time for release? Is it a la ...her packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, does
    4 KB (647 words) - 13:27, 31 January 2014
  • ...major release and a minor (bugfix) release is more clearly visible. Since developers can still use just integer numbers the simplicity of the old scheme is kept This scheme also enables developers who maintain older versions of Sugar, building activities with intermediate
    3 KB (484 words) - 14:59, 5 November 2013
  • Developers interested in working on the Sugar interface or writing activities can have == Documentation ==
    1 KB (208 words) - 17:44, 16 August 2014
  • [[Category:Services/Documentation]] ...this Guide is to describe how to simplify the usage by activity or service developers of packages that are not included in the [[0.86/Platform_Components|Sugar P
    5 KB (663 words) - 15:13, 3 July 2012
  • ...ted by educators, refined by developers, and distributed, free, along with documentation, in multiple languages.
    879 bytes (129 words) - 10:50, 8 July 2018
  • ...her packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, comp == Documentation ==
    3 KB (519 words) - 01:28, 18 October 2009
  • == Developers & Testers == {{warning | Please add new activity documentation at GitHub. Read [https://help.sugarlabs.org/en/how_to_help.html How to edit
    2 KB (291 words) - 10:20, 14 August 2018
  • ''What work do the developers have to accomplish to complete the feature in time for release? Is it a la ...her packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, comp
    4 KB (669 words) - 15:17, 5 November 2013
  • ...LO is a ground up rewrite of the aslo to make it work better for users and developers. [http://www.aslo.cf Check it out] ...ng an activity is a lot harder than it needs to be; making it easier gives developers more time to develop activities. The new ASLO '''automatically builds the
    4 KB (687 words) - 14:55, 29 December 2015
  • ''What work do the developers have to accomplish to complete the feature in time for release? Is it a la ...her packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, does
    5 KB (772 words) - 08:51, 25 July 2014
  • Developers should have in account check if the env variable exists or not, because act == Documentation ==
    1 KB (224 words) - 22:10, 12 October 2015
  • ''What work do the developers have to accomplish to complete the feature in time for release? Is it a la ...her packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, comp
    5 KB (767 words) - 02:12, 18 October 2009
  • == Documentation == ...g list or during a meeting? Link to that material here so other interested developers can get involved.''
    3 KB (383 words) - 13:15, 31 January 2014
  • == Documentation == ...g list or during a meeting? Link to that material here so other interested developers can get involved.''
    2 KB (377 words) - 21:24, 17 July 2017
  • ''What work do the developers have to accomplish to complete the feature in time for release? Is it a la ...her packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, does
    5 KB (775 words) - 15:42, 20 April 2015
  • ''What work do the developers have to accomplish to complete the feature in time for release? Is it a la ...her packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, does
    5 KB (797 words) - 15:54, 21 June 2010
  • Meeting: Kickoff, have a big chat with teachers and developers where the teachers drive the meeting and talk about what they're trying to Folks on the ground deploy, developers sit back and work on documentation of the project so that others can use what they've built.
    3 KB (420 words) - 21:43, 23 February 2010
  • ...user experience tracking and help provide helpful (hard data) feedback to developers who can improve the platform. == Documentation ==
    2 KB (338 words) - 23:26, 21 November 2011
  • ...ilitate upstream maintenance of our code while asking little more of Sugar developers. None of these additional fields need be required, but their inclusion woul ...s it need a UI?'' It has a very minor impact (optional) impact on activity developers in that they need to add additional fields to the activity.info files; it w
    4 KB (571 words) - 11:42, 6 November 2013
  • == Documentation == ...g list or during a meeting? Link to that material here so other interested developers can get involved.''
    3 KB (417 words) - 16:31, 5 November 2013
  • ''What work do the developers have to accomplish to complete the feature in time for release? Is it a la * documentation changes.
    3 KB (499 words) - 08:42, 5 April 2020
  • ...e harder part of solving this problem is spreading the word among activity developers to update their .xo bundles accordingly. * identify activity developers who don't know about compatibility issues and the importance of testing on
    3 KB (491 words) - 01:56, 18 October 2009
  • ...o leverage age and gender for their program analysis. Also, Sugar activity developers can begin to incorporate age and gender into their activities where appropr == Documentation ==
    3 KB (404 words) - 07:56, 18 July 2014
  • == What is new for developers? == *A new SUGAR_VERSION environment variable is available to activities developers.
    3 KB (496 words) - 13:26, 13 February 2016
  • ...e in Android would be able to do same in Sugar using the same code. So the developers don't need to recode their apps to get them to the Sugar environment. All t ...rdova helps us to make cross platforms apps. This will attract the web app developers to sugar community and help them launch their activities in sugar without p
    8 KB (1,321 words) - 12:10, 2 September 2014
  • ** more developers are needed ...t FlossManuals folks and others who have previously already contributed to documentation efforts)
    3 KB (505 words) - 20:10, 24 February 2010
  • ...is is a great opportunity for Sugar Labs to recruit its next generation of developers.
    1 KB (167 words) - 11:50, 30 November 2012
  • ...d other Desktops. Does all the repetitive parts, for be more friendly with developers. It's divided in modules, they can be included in an activity for do a spec == Documentation ==
    4 KB (573 words) - 18:12, 4 November 2012
  • ...her packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, does == Documentation ==
    5 KB (816 words) - 15:05, 22 November 2011
  • ...her packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, comp == Documentation ==
    3 KB (513 words) - 16:33, 5 November 2013
  • ...her packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, does == Documentation ==
    5 KB (772 words) - 16:37, 16 November 2011
  • ...now if you can use the 64-bit version. If your computer says on the box or documentation that it is 64-bit, you may use the 64-bit download version of Sugar called Fedora developers reported these minimum requirements for the Fedora 17 distributions.
    2 KB (344 words) - 06:22, 24 December 2019
  • ...roblem report is added, the server sends an email out to a mailing list of developers and interested parties. ...cimal number). They can use this if they wish to follow up with the Sugar developers by email.
    5 KB (834 words) - 10:23, 20 December 2009
  • ...update to point to ASLO will require clear communication to end users and developers. == Documentation ==
    4 KB (556 words) - 15:38, 5 November 2013
  • ''What work do the developers have to accomplish to complete the feature in time for release? Is it a la * documentation changes.
    4 KB (635 words) - 07:34, 30 August 2019
  • ''What work do the developers have to accomplish to complete the feature in time for release? Is it a la ...her packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, does
    6 KB (978 words) - 12:30, 21 February 2011
  • ...progresses over the next four weeks). Students have done a great job with documentation, for example, there is now a chapter in '''[http://booki.flossmanuals.net/m ...as been instrumental not only in writing code, but also in mentoring other developers and one whom grew up with Sugar, bringing us the perspective of the Sugar u
    3 KB (463 words) - 15:25, 29 December 2012
  • Add developer API documentation to sugar-toolkit-gtk3 in a consistent format. Then, create a site to make * Percentage of completion: 10% (see [https://developer.sugarlabs.org/sugar3/ documentation website])
    4 KB (484 words) - 02:01, 3 January 2017
  • ''What work do the developers have to accomplish to complete the feature in time for release? Is it a la ...her packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, comp
    5 KB (851 words) - 01:25, 18 October 2009
  • 7. Documentation: There are a number of complementary efforts for documenting the Sugar API ...[Documentation Team/API Documentation]]). David is soliciting modules from developers to add to the build_api.sh script, which he plans to run daily.
    7 KB (1,121 words) - 09:37, 19 December 2016
  • This page would be the start of a documentation effort aimed to document those basic interfaces: Actually will be mostly a documentation effort - no impact on code in this phase.
    5 KB (663 words) - 13:21, 31 January 2014
  • ...ifi or through a [[olpc:Community Jabber Servers | Jabber network]]. Sugar developers are encouraged to write activities with collaborative elements that are aut Puede explorar la [[Documentation Team/Glossary|interface]] de Sugar en la XO-1 [http://laptop.org/en/laptop/
    4 KB (645 words) - 01:39, 19 December 2016
  • ...are. Furthermore it provides a flexible and powerful platform for activity developers. == What's new for developers ==
    7 KB (914 words) - 13:04, 5 March 2012
  • ...mit set is to get feedback when too many activities are launched. Activity developers can set a limit to the number of instances that can be launched. == Documentation ==
    4 KB (632 words) - 07:55, 18 July 2014
  • ''What work do the developers have to accomplish to complete the feature in time for release? Is it a la == Documentation ==
    7 KB (1,158 words) - 18:23, 17 April 2016
  • ...be provided until it is modified to use the telepathy APIs directly. Etoys developers have expressed interest on this work. == Documentation ==
    4 KB (610 words) - 16:05, 5 November 2013
  • ...ther packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, does ...y so that it can be retroactively installed on earlier Sugar versions. The documentation will specify how and to which versions this is supported.
    6 KB (939 words) - 01:42, 23 April 2016
  • ''What work do the developers have to accomplish to complete the feature in time for release? Is it a la ...her packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, does
    3 KB (515 words) - 07:58, 18 July 2014
  • ...h their service, see their [http://www.gnu.org/software/mailman/docs.html documentation page]. ....sugarlabs.org/listinfo/sugar-devel Sugar-devel] || The Sugar and Activity developers' email list<br>&nbsp;&nbsp;&nbsp;(See the graphic [[Sugar Labs/SOM#Sugar_Ma
    5 KB (836 words) - 11:30, 29 August 2019
  • ...and help with quality assurance; some are writing documentation for Sugar developers and for those who use Sugar in the field; some are developing new scenarios ...mages. In support of the Developer Team, he is setting up an automated API documentation generator set up as well as jhbuild. He is seeking some help from the learn
    8 KB (1,314 words) - 08:24, 19 December 2016
  • <!-- The way features happen in Fedora is that early in the release process, developers propose features, and they are approved by a feature freeze date (which is ...the work to program, prepare and coordinate the work with many other sugar developers for this release.
    8 KB (1,323 words) - 01:08, 27 June 2012
  • ''What work do the developers have to accomplish to complete the feature in time for release? Is it a la * documentation changes.
    5 KB (858 words) - 18:01, 14 September 2017
  • development team and other Sugar developers. A lot of work has been The way features happen in Fedora is that early in the release process, developers propose features, and they are approved by a feature freeze date (which is
    9 KB (1,493 words) - 21:52, 2 August 2013
  • <!-- The way features happen in Fedora is that early in the release process, developers propose features, and they are approved by a feature freeze date (which is ...the work to program, prepare and coordinate the work with many other sugar developers for this release.
    9 KB (1,360 words) - 21:03, 8 July 2012
  • development team and other Sugar developers. A lot of work has been ...the work to program, prepare and coordinate the work with many other sugar developers for this release.
    8 KB (1,243 words) - 11:52, 9 December 2014
  • development team and other Sugar developers. A lot of work has been ...the work to program, prepare and coordinate the work with many other sugar developers for this release.
    8 KB (1,250 words) - 02:35, 3 December 2018
  • ...o have grown up with Sugar have transitioned from Sugar users to Sugar App developers to Sugar maintainers. They hang out on IRC with the global Sugar developer [See https://developers.google.com/open-source/gci/resources/getting-started]
    11 KB (1,695 words) - 20:00, 13 November 2019
  • ...orted for existing activities to run without a hitch. This would represent developers who prefer python 3 as well as those who prefer python 2.7+ to be able to c ...eveloper reach. This issue I believe can be circumvented by writing proper documentation which I plan to do towards the end of the project.
    10 KB (1,766 words) - 13:53, 21 March 2014
  • ...her packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, comp == Documentation ==
    6 KB (976 words) - 07:58, 18 July 2014
  • Developers may focus on either Fedora or Debian when setting up a development environm .../fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi Fedora Raspberry Pi Documentation], or [https://unetbootin.github.io/ UNetBootin]
    2 KB (390 words) - 17:22, 17 December 2019
  • ...illa.dev.embedding/c_NMcO-N8wo/discussion actively discouraged] by Mozilla developers, who are focusing all their efforts on Firefox. From the perspective of a f ...onment. However, this is not possible, for 2 reasons (as explained by pygi developers Tomeu and J5):
    11 KB (1,752 words) - 15:49, 5 November 2013
  • == What is new for developers == * New documentation page ([[Activities/Turtle Art]])
    4 KB (676 words) - 09:03, 10 March 2010
  • development team and other Sugar developers. A lot of work has been The way features happen in Fedora is that early in the release process, developers propose features, and they are approved by a feature freeze date (which is
    10 KB (1,588 words) - 21:50, 2 August 2013
  • ...i]] or through a [[olpc:Community Jabber Servers | Jabber network]]. Sugar developers are encouraged to write activities with collaborative elements that are aut Read the [[Documentation Team/User Manual/Connecting to the Internet|Connecting to the Internet page
    5 KB (729 words) - 07:47, 16 February 2011
  • ...orm_Team/Guide/Sweets_Usage|Sweets]], and asks about introducing it to non developers, {{Bug|3249}}. ...you [originally addressed to [[User:Inkyfingers|Inkyfingers]]] look at the documentation with the eye toward drafting an introductory posting and page for new non-t
    10 KB (1,480 words) - 15:56, 3 July 2012
  • ...her packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, does == Documentation ==
    9 KB (1,405 words) - 15:51, 5 November 2013
  • 3. A few of the activities do not start, so perhaps its documentation would be misleading if included in Help Activity. Instead, the documentation could be moved to the source repository(temporarily)
    17 KB (2,531 words) - 03:38, 10 January 2019
  • As most software developers would agree, the best way to learn how to write a program is to write one, ...nstead of a text file, a story. In order to support this concept, activity developers may define object types and associated icons to represent them.
    6 KB (898 words) - 22:42, 22 December 2011
  • ...ript API. I will then update documentation for this new API so that future developers can easily make web activities that enable collaboration just like the stan ...rogram I have to make the new collaborative JavaScript API and its updated documentation for sugar-web. I will be using JavaScript mostly for updating and adding co
    11 KB (1,975 words) - 12:31, 21 March 2014
  • * better documentation of the benefit of the trip, * key messages for potential developers,
    4 KB (617 words) - 19:08, 5 April 2019
  • * In order to not surprise the activity developers/partner, we should try to notify them before we put them up there since the * Documentation/associated content (e.g. support on relevant site, mktg, help info, etc…)
    9 KB (1,423 words) - 19:30, 4 April 2009
  • ...nterface on the laptops. Though most of the available controls will match developers' expectations, we've also developed some new controls and altered behaviors ...ations for the widgets and their various states. Finally, we're providing developers with an Adobe Illustrator file of the most up to date Sugar Control Specifi
    6 KB (882 words) - 13:14, 18 May 2015
  • * Lack of proper documentation for the set of activities. Sugar activities are scattered, not all are on G * We are failing in attracting new consistent developers despite being a popular organization in the Google programs. There are very
    3 KB (482 words) - 09:02, 4 November 2020
  • Developers of activities will have: == Documentation ==
    7 KB (1,143 words) - 04:30, 3 October 2012
  • ...iveUSB, LiveCD, and Appliance efforts, but also further consideration (and documentation) of the various hardware one might find in the field and more detailed inst ...opers need a more focused list to alert them to needs specific to activity developers, such as changes to APIs, a forum for soliciting help, etc. The downside of
    7 KB (1,117 words) - 08:31, 19 December 2016
  • ...s.org/go/Fedora_32#Rpi]], this will become increasingly important, so that developers and testers do not have to purchase one of each. There are emulation module ...packages on Debian, Ubuntu, and related distros. Otherwise, consult system documentation for package installation or installing from source.
    6 KB (969 words) - 08:26, 16 November 2019
  • == What's new for developers == ...communities. On behalf of the community, we give our warmest thanks to the developers and contributors who made this Sugar release possible.
    9 KB (1,336 words) - 15:38, 21 May 2019
  • The way features happen in Fedora is that early in the release process, developers propose features, and they are approved by a feature freeze date (which is Activity developers weren't informed of changes in the libraries their Activities depended on,
    12 KB (1,849 words) - 01:01, 27 June 2012
  • ...017/10/welcoming-25-mentor-organizations-for.html application] to [https://developers.google.com/open-source/gci/ Google Code In 2017]. Sugar Labs community memb https://developers.google.com/open-source/gci/resources/contest-rules
    10 KB (1,567 words) - 08:03, 16 October 2018
  • ...ssment of bugs to be moved over. Basic, *basic* triage from knowledgeable developers. | (later I want to start adding documentation)
    3 KB (394 words) - 21:33, 23 February 2010
  • ...018/10/welcoming-25-mentor-organizations-for.html application] to [https://developers.google.com/open-source/gci/ Google Code In 2018]. Sugar Labs community memb https://developers.google.com/open-source/gci/resources/contest-rules
    10 KB (1,567 words) - 13:59, 21 October 2018
  • ...lopers to settle easily into the SugarLabs world and provide a centralized documentation portal. ::* '''Login won’t be compulsory to view the documentation.'''
    17 KB (2,810 words) - 14:03, 20 March 2018
  • Many developers worked in this Feature, with implementation, improvements, testing, reviews == What's new for developers ==
    9 KB (1,382 words) - 16:44, 9 March 2014
  • ...gar-devel@, which may not always be fair), and coordinator/requester/other-developers can track such events ..., we could share the same place for non-tech users, experienced doers, and developers. [[#Implementation_ideas|But that doesn't mean]] we should have only collab
    7 KB (1,009 words) - 23:16, 7 February 2012
  • ...tive prompts of reportbug do not resolve, you can refer to the rest of the documentation at the link above, or ask the [http://lists.debian.org/debian-user/ Debian * [http://www.altlinux.org/ALT_Linux_Bugzilla ALT Linux Bugzilla] Documentation (in Russian)
    7 KB (1,131 words) - 10:08, 30 May 2011
  • ...osting on activities.sugarlabs.org, it was a sign that educators, not just developers, were beginning to take a lead in determining the shape of Sugar. But even 3. The Sugar-on-a-Stick team is looking from someone to help them with documentation. Please contact the list (soas@) if you are interested.
    3 KB (487 words) - 19:37, 27 July 2010
  • ...Though it is currently quite sparse, the source code is included with the documentation and it's useful to have that at your fingertips. ...tation] that touches on many of the issues encountered by first-time Sugar developers. Some items covered are: What is Sugar and Sugar Labs; What are some develo
    11 KB (1,550 words) - 22:18, 16 January 2018
  • * Topic for #sugar-meeting is: The meeting channel for the sugar developers (sugarlabs.org) | see also #sugar | meeting time: thursdays 14.00 UTC :'''<walter>''' As Tomeu suggests, feedback to developers is very important
    20 KB (3,741 words) - 20:15, 24 February 2010
  • == What's New For Developers == ...//wiki.laptop.org/go/Sugar_Almanac guide] is a nice starting point for new developers and an interesting read up for the pros.
    12 KB (1,855 words) - 14:16, 3 July 2012
  • Sugar Labs will award certificates to developers to acknowledge and celebrate their contributions to the Sugar Learning Plat ...ation, including the submission of a POT file to the Translation Team, and documentation, including the creation of a page in the wiki under the Activity category.
    5 KB (871 words) - 13:18, 23 July 2012
  • [[Category:Documentation]] ...' is documentation that applies to ''a program'' and its interfaces. It is documentation that explains to a developer who is going to work with the program, or a de
    26 KB (4,344 words) - 15:34, 2 November 2011
  • Share the activity for testing among developers, testers in the community. == Documentation ==
    12 KB (2,019 words) - 08:11, 18 July 2014
  • '''Note''': The [[olpc:Developers manual]] provides more comprehensive and up-to-date introductions to the is ...Activity API]] page attempts to cover this, but is frequently incomplete. Documentation help would be very useful.
    10 KB (1,624 words) - 21:33, 23 February 2010
  • ...change of experiences between Sugar users and between Sugar user and Sugar developers (You can follow the development in the wiki at [[Deployment Team|Developmen ...ease see [[:Category:Stub]] for a list of where you could help us with our documentation efforts.
    7 KB (1,076 words) - 09:32, 19 December 2016
  • ...rticipants. Such as Sugar Activities, content created by Sugar Activities, documentation and educational materials, etc. ...2). Besides, there is no convenient and direct (between users and Activity developers) ways to share technical information when Sugar Activity fails.
    10 KB (1,569 words) - 20:00, 27 January 2012
  • Organize and proofread documentation ...e built using Qt but are not part of KDEEdu. This will save Sugar activity developers from having to write applications that may already exist but are not built
    11 KB (1,944 words) - 15:59, 8 April 2009
  • == What is new for developers? == *Updated documentation for Sugar Toolkit API, see [https://developer.sugarlabs.org/sugar3 sugar3],
    7 KB (1,023 words) - 20:08, 8 October 2017
  • |Work with Trisquel||Maintain communication with Trisquel developers and collaborate on a way to promote free/libre tools for education * Objective: Actively recruit and maintain developers for Sugarizer
    19 KB (2,866 words) - 20:30, 5 May 2017
  • The way features happen in Fedora is that early in the release process, developers propose features, and they are approved by a feature freeze date (which is Activity developers weren't informed of changes in the libraries their Activities depended on,
    15 KB (2,373 words) - 00:05, 3 February 2013
  • ...mage" button is not working as expected.It is really great experience when developers around the globe are working together to make our life easy and to make int ...around sugar labs.This project can attract a wide range of community from developers to teachers and parents.It helps to connect all communicate together on one
    16 KB (2,687 words) - 06:37, 16 October 2018
  • ...ctive and user friendly. There will be more scope of work for the activity developers, as they will get many additional features from the Cordova container.<br> | Adding documentation on how the activities can exploit the hardware interfaces using the API's w
    19 KB (3,168 words) - 14:08, 21 March 2014
  • * our user and teacher documentation is in need of work, particularly for Sugar and Sugarizer, * we would expect both developers and an education team to be interacting with the technical writers,
    5 KB (796 words) - 22:56, 5 April 2019
  • ...ancements and bug fixes you can expect. Furthermore it has information for developers, packagers and deployers. == What's new for developers ==
    13 KB (1,886 words) - 05:18, 21 October 2011
  • ...developers has begun. The next step is for some of the teachers to become developers. ...f 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 i
    8 KB (1,252 words) - 09:34, 19 December 2016
  • ...communities. On behalf of the community, we give our warmest thanks to the developers and contributors who made this Sugar release possible. ...eading a discussion about building an embedded-Sugar community. A group of developers have been assembled to port Sugar to the ([http://beagleboard.org/ Beaglebo
    6 KB (877 words) - 09:34, 19 December 2016
  • == What is new for developers == * gconf documentation string for logout option
    6 KB (848 words) - 12:43, 25 September 2009
  • ...and this project would bring just that to sugar web, allowing web activity developers to incorporate collaboration associated features in the activities. ...tion methods between server and client which would be used by web activity developers.<br>
    10 KB (1,616 words) - 17:26, 25 March 2015
  • * Documentation ...sort of items for [http://wiki.laptop.org/go/Creating_an_activity Activity developers] to include our API and be able to extend it.
    12 KB (1,855 words) - 00:05, 6 June 2016
  • ...eories and obstacles, paedagogy, ability to communicate with and influence developers. * | [[Documentation Team]] | [[Marketing Team]] | [[Wiki Team]] | [[Deployment Team]] | [[Local
    10 KB (1,415 words) - 10:20, 18 March 2019
  • ...Sugar software should visit our [http://developer.sugarlabs.org/ developer documentation website]. ...) is that, with the full VM documentation provided online, you follow that documentation to install the VM on your PC or Mac. VirtualBox<sup>®</sup> is a suitable
    9 KB (1,441 words) - 03:59, 26 March 2020
  • == Sugar Activities Developers: Take 10 Minutes to move to Github Today! == So we now invite all Activity developers to do 2 things to complete this transition.
    28 KB (3,867 words) - 08:11, 27 June 2016
  • .... The mission of Sugar Labs is to support the Sugar community of users and developers and establish regional, autonomous “Sugar Labs” around the world to tai Sugar is a community project. We hope to grow our community of developers through our participation in GSoC. In particular, we see GSoC as a good opp
    9 KB (1,355 words) - 12:49, 7 August 2014
  • :'''Note:''' Most of this page was copied from [[OLPC:Developers/Stack#Activity Development Stacks]], so most of the links refer to pages in == Interfaces provided to activity developers ==
    10 KB (1,495 words) - 14:00, 13 September 2011
  • ...Colombo University Information Technology Faculty and open source software developers have supported the software developing process. Over 850 software programme ...gsoc2012] is gearing up for 2012. It is a nice opportunity to get some new developers on board. As a community, we need to get ourselves organized: specifically,
    6 KB (948 words) - 14:40, 22 March 2012
  • ...o have grown up with Sugar have transitioned from Sugar users to Sugar App developers to Sugar maintainers. They hang out on IRC with the global Sugar developer ;Documentation/Training: Tasks related to creating/editing documents and helping others le
    18 KB (2,354 words) - 10:26, 30 November 2012
  • ...|| Testing transformation of "media", "sensors" and "etras" blocks. Write documentation |9 Aug - 15 Aug || Testing and fixing bugs. Write documentation
    9 KB (1,627 words) - 14:54, 27 March 2015
  • ...providing localization and internationalization of software, content, and documentation; and providing integration and customization services.” It is worth check ...sight board passed a motion to empower Sugar Labs to award certificates to developers to acknowledge and celebrate their contributions to the Sugar Learning Plat
    6 KB (965 words) - 11:22, 22 August 2011
  • * [http://lists.sugarlabs.org/archive/iaep/2011-September/014011.html Documentation] ...n sugar-toolkit, and help to improve it, doing easier the work to activity developers.
    18 KB (2,725 words) - 23:07, 16 September 2011
  • Contribution: ''Documentation'' ...reate final presentation for tonights Pythonistas meeting. Complete group documentation.
    8 KB (1,254 words) - 17:03, 18 December 2013
  • ...d questions, and present a logical path forward that can be adopted by the developers. * A number of developers will be needed at each stage to successfully execute this; Daniel offers hi
    20 KB (3,339 words) - 15:30, 5 November 2013
  • This allows developers to concentrate on refining the new features instead of adding yet more func ...o focus on stability and bug-fixing rather than UI changes. At this point, documentation writers do not have to worry that their work will become outdated.
    11 KB (1,705 words) - 19:51, 16 January 2018
  • Documentation tools have become modern, lighter, easier to use with the use of Sphinx, Gi ...in turn, help the entire community to grow and expand. If the information (Documentation) is accessible fast, easily comprehensible, simple enough to edit and manag
    28 KB (4,403 words) - 13:45, 30 May 2018
  • * Karma is for web developers who want to contribute to Sugar using their current skills ...torage, and certain types of animation should be abstracted so that novice developers don't have to understand them in order to effectively use Karma. Karma stri
    13 KB (1,938 words) - 01:31, 19 December 2016
  • ...ips between members of the project, and can act as a reward to "sponsored" developers. ...ditionally, DebConf acts as a venue for airing ideas and proposals between developers and for gathering feedback on controversial issues.
    10 KB (1,664 words) - 07:41, 19 August 2009
  • '''Rationale''': Gives a visual cue for developers that one or more criteria are not complete or accurate. '''Rationale''': Add ranking to criteria to encourage better documentation.
    13 KB (1,592 words) - 16:08, 29 December 2015
  • ...ans "someone in the audience for this change", which could be Sugar users, developers, or system administrators. ...e subject asking for feedback. This is to give the community (deployments, developers, teachers etc) the chance to comment.
    16 KB (2,587 words) - 18:51, 8 September 2017
  • ...al content developers, within the Sugar Learning Platform. This will allow developers to integrate speech-enabled interfaces to their Sugar Activities, letting u ...xpected results of this project include not only the code, but also proper documentation of the API and a proof-of-concept voice-user interface for a Sugar Activity
    14 KB (2,210 words) - 10:25, 28 May 2014
  • == What's new for developers == The following changes are important for developers using the Sucrose 0.96 developer platform:
    14 KB (2,020 words) - 03:00, 6 June 2012
  • * https://github.com/adambard/learnxinyminutes-docs (Code documentation written as code! How novel and totally my idea!) meaningful features that help make ASLO easy to use both for developers and users, doing
    10 KB (1,650 words) - 16:49, 17 May 2017
  • ...nt to create, it almost creates the policy for us. Of course this involves documentation! ...many developers and users as possible. To that end, it seems the .AU OLPC developers have done a lot of cleaning up and modularising of the current XS code. Tha
    16 KB (2,739 words) - 00:39, 17 May 2016
  • # perhaps encourage more developers to incorporate more programmatic elements in their activities.<br/> * Improve the Documentation of Turtle Block.
    14 KB (2,287 words) - 16:27, 26 March 2015
  • ...you may know of), as well as your perceptions on the challenges users and developers of ICT solutions face and the future of this field." Their report will be p ...that multiple platforms and host configurations may be tested seamlessly; developers can more readily perform regression testing on their Activities, enhancing
    7 KB (1,036 words) - 08:28, 19 December 2016
  • ...o update to the latest version of a given Activity, and makes smoother for developers to publish and distribute newer version of Activities. ...re information is available in this [[Features/Keyboard_CP_Section|Feature documentation]].
    18 KB (2,591 words) - 03:29, 4 October 2010
  • {{Developers}} For Activity Developers:
    19 KB (3,169 words) - 00:26, 14 August 2017
  • :Documentation is available from [[Activity Team/Resources]]. :Check [[Activity Team/Resources]] for a comprehensive list of developer documentation, tutorials and support channels.
    7 KB (1,161 words) - 22:11, 16 January 2018
  • ...ent with the opportunity to work in big open source projects with the core developers. This makes me excited and eager to participate in it. ...to do be done again in coming years. This project also aims to provide new developers platform where they can do their job easily and help maintain sugar support
    15 KB (2,415 words) - 01:22, 22 March 2018
  • 16. Sugar control panel: Simon added documentation for the graphical control panel (Please see [http://wiki.laptop.org/go/Suga ...licensing functionality in the Journal was discussed at this week's Sugar developers meeting (Please see [[Development Team/Meetings#Creative_commons_licensing_
    11 KB (1,760 words) - 09:34, 19 December 2016
  • ...sugarlabs.org/archive/sugar-devel/2012-June/037996.html asked to the Sugar Developers mailing list] about how to do this and they told me that I should change th As [http://developer.gnome.org/gtk3/3.5/GtkHBox.html#GtkHBox.description its documentation says], Gtk.VBox and Gtk.HBox have been deprecated. So, we should use Gtk.Bo
    15 KB (2,510 words) - 20:37, 22 December 2016
  • This project also targets the developers, they can use our application to # Secondary aim would be to increase Scope for development for future developers.
    20 KB (3,300 words) - 07:23, 16 April 2009
  • ...workshop will be organized all around the day: technical, pedagogical and documentation. The full agenda is not closed so do not hesitate to submit a workshop prop 9. We held the first "mini developers tutorial" this week on IRC. The idea is to feature a topic in a five minute
    7 KB (1,184 words) - 19:37, 27 July 2010
  • ...into sugar that will open whole new set of opportunities both for Activity developers and end users (especially for physically challlenged.) : Implementation of Speech Recognition will provide activity developers an opportunity to create more interactive activities, where users can inter
    20 KB (3,293 words) - 06:30, 5 April 2010
  • ...umentation will include the user's documentation as well as the deveoper's documentation. ...ribution in Sugarlabs as it will let the children grow their skills as web developers.<br />
    11 KB (1,908 words) - 13:28, 30 March 2015
  • large sector of developers. Sugar Labs has been a good starting point for open source contribution and ...a platform that can utilized by different sectors of people like children, developers, contributors, etc.
    27 KB (4,199 words) - 12:51, 17 May 2017
  • ...e contributions to Sugar core, numerous Sugar activities, and enhanced our documentation. Ignacio wrote two new web services &ndash; [https://github.com/ignaciouy/u
    5 KB (777 words) - 18:58, 9 March 2014
  • :Sugar is a community project. We hope to grow our community of developers through our participation in GSoC. In particular, we see GSoC as a good opp ...licit community-building programs like GSoC are especially important. Most developers will not become familiar with the software and comfortable contributing thr
    22 KB (3,477 words) - 19:49, 12 March 2010
  • ...ound Sugar Labs. The goal of this project is to attract Teachers, Parents, Developers and fully communicate together in one platform. : It's a social website t ...1) document how the Music Blocks source code works for current and future developers to learn and benefit from and 2) project manage this portion of Music Block
    29 KB (4,376 words) - 06:50, 16 October 2018
  • ...are. Furthermore it provides a flexible and powerful platform for activity developers. Thanks to '''''all''' the activity maintainers and developers'' for making this happen.
    16 KB (2,388 words) - 11:43, 23 July 2012
  • ** translating existing documentation (e.g. FlossManuals) * getting more developers to work on Sugar related tasks
    5 KB (766 words) - 20:10, 24 February 2010
  • ...into sugar that will open whole new set of opportunities both for Activity developers and end users (especially for physically challlenged.) : Implementation of Speech Recognition will provide activity developers an opportunity to create more interactive activities, where users can inter
    22 KB (3,563 words) - 01:13, 9 April 2010
  • == What is new for developers == ...e Sucrose 0.84 developer platform. If you're not interested in changes for developers, you can skip forward to Section [[0.84/Internationalization|Internationali
    17 KB (2,678 words) - 03:30, 4 October 2010
  • ...nstead of a text file, a story. In order to support this concept, activity developers may define object types and associated icons to represent them. --> ...nterface Guidelines/The Laptop Experience#The Journal|Journal]], a written documentation of everyday events, is generally understood, albeit in various forms across
    7 KB (1,120 words) - 22:34, 26 August 2009
  • ...e (GSoC)] is gearing up for 2012. It is a nice opportunity to get some new developers on board. As a community, we need to get ourselves organized: specifically, 3. There will be a OLPC/Sugar documentation sprint from April 6-10 at the OLPC headquarters in Cambridge, Massachusetts
    6 KB (950 words) - 04:22, 23 February 2012
  • ...port for teachers and schools what OLPC laptops concern – troubleshooting, documentation creation, development of new activities (programs). ...ll provide the Curricular specifications and content and User service team developers will create the programming part.
    18 KB (2,636 words) - 04:38, 1 January 2009
  • This is the project page for the Sugar Labs application to [https://developers.google.com/open-source/gci/ Google Code In 2016]. Sugar Labs community memb https://developers.google.com/open-source/gci/resources/contest-rules
    27 KB (4,064 words) - 00:28, 30 November 2016
  • * Contact former + current activity developers. [[User:Wade|Wade]] 17:26, 12 January 2009 (UTC) ** Documentation tutorial. Guidelines for activity documentation, and perhaps instructions on how to create a FLOSS manual about your activi
    9 KB (1,352 words) - 04:58, 6 April 2014
  • developers all across the world and developing software that millions of people # Talk to Debian developers (Jonas, Sebastian) to ensure that my work is included in their task.
    19 KB (3,344 words) - 15:51, 17 May 2017
  • ...he means of communication between users, like students or deployments, and developers to reach out for feedback and interact. One of the biggest issue Sugar on a ...iteration of Sugar on a Stick, enabling them to interact directly with our developers, resulting in a better product. [[User:Sdz| Sebastian Dziallas]]
    11 KB (1,921 words) - 16:44, 8 April 2010
  • ...together with some Python scripts for image processing. You can find some documentation here: http://openimageio.org/wiki/index.php?title=Python_bindings , and my #*I consider this a good project since (I do suppose Sugar developers will agree) Python is an important language and its simple and intuitive sy
    13 KB (2,344 words) - 16:13, 9 April 2010
  • ...ts/sugar/repos/yevlempy/commits/973b0bd9def313cf6cf9ffea967c4626ebb9ffc6), Documentation(http://yevlempy.wordpress.com/2010/03/27/the-sugar-font-panel/). Have also #*In the first trimester (from around 23 May - 22 June) : I will be reading documentation of various stuff like ldtp, mago various python specific stuff i require (i
    10 KB (1,759 words) - 05:17, 9 April 2010
  • {{Developers}} You can find all documentation you need about the contents of a XO Bundle file [[Bundle]] but here give a
    7 KB (1,072 words) - 17:39, 30 August 2009
  • Developers and educators from [http://www.ceibal.edu.uy/ Plan Ceibal] and [http://www. Thanks to '''''all''' the activity maintainers and developers'' for making this happen.
    23 KB (3,516 words) - 13:16, 23 July 2012
  • Linux technical community, application developers, industry, and end ...d.de/Start?action=AttachFile&do=view&target=LinuxTag-2008-OLPC-Deutschland-Developers.jpg).
    10 KB (1,502 words) - 09:37, 19 December 2016
  • ...intain the activities available for Sugar. The team encourages independent developers to write activities and will support them in those efforts. ...rlabs.org/wiki/images/2/2d/TAPortfolio-1.xo TAPortfolio-1.xo]. Preliminary documentation can be found on [[Activities/TAExperimental]]. TAPortfolio is a presentatio
    9 KB (1,488 words) - 19:37, 27 July 2010
  • ...and help with quality assurance; some are writing documentation for Sugar developers and for those who use Sugar in the field; some are developing new scenarios
    11 KB (1,798 words) - 16:17, 26 November 2011
  • :2) Alternative acceptable (localized elsewhere) with clear documentation of how to participate in localization and get the localized PO files from t ...is no question that we could use some improvement to our Translation Team documentation, including a better "Developer's Guide" entry point. [[User:Cjl|Cjl]] 17:14
    11 KB (1,874 words) - 10:36, 13 July 2010
  • ** http://www.djangoproject.com/documentation/forms/ ** http://twistedmatrix.com/projects/core/documentation/howto/plugin.html
    7 KB (1,054 words) - 02:41, 3 July 2009
  • :* Yup, we need to seek help from the community to do this. The developers team is small and overworked. --[[User:Marcopg|Marcopg]] ...ult of mime handling done not-quite-right (and a great argument for better documentation so people will do it correctly!) [http://dev.laptop.org/ticket/4001 #4001]
    11 KB (1,772 words) - 14:47, 6 June 2019
  • ...s below are random useful techniques that have come up as I write code and documentation for this reference. They have yet to be categorized, but will be as a suffi This is the basic series of steps that most online documentation on python suggests to use when trying to work with threads in python. The p
    19 KB (2,917 words) - 19:28, 15 August 2012
  • ...would like to begin helping with infrastructure / testing / development / documentation / bug killing. Testing is to be used as a staging for developers and testers to use and abuse the new code before it goes into production.
    7 KB (1,195 words) - 12:55, 19 October 2010
  • As most software developers would agree, the best way to learn how to write a program is to write one, ...nstead of a text file, a story. In order to support this concept, activity developers may define object types and associated icons to represent them.
    12 KB (967 words) - 22:32, 26 August 2009
  • This project also targets the developers, they can use our application to # Secondary aim would be to increase Scope for development for future developers.
    20 KB (3,283 words) - 20:44, 7 April 2009
  • As most software developers would agree, the best way to learn how to write a program is to write one, ...nstead of a text file, a story. In order to support this concept, activity developers may define object types and associated icons to represent them.
    11 KB (1,845 words) - 13:08, 11 July 2009
  • ...opportunities. This program proves to be a boon for all those enthusiastic developers who are willing to spend their entire summers contributing to a specific op ...ity (Anita Borg Institute). I am also a member of my college’s Open Source Developers Group. The journey so far with FOSS organizations have been wonderful. Espe
    19 KB (2,998 words) - 16:43, 17 May 2017
  • : Not at this time, although there are some developers working to change that situation. See this [http://www.mail-archive.com/iae ...pport base and gathering place for the community of educators and software developers who want to extend the Sugar platform and who have been creating Sugar-comp
    15 KB (2,443 words) - 19:53, 7 April 2019
  • * Topic for #sugar-meeting is: The meeting channel for the sugar developers (sugarlabs.org) | see also #sugar | meeting time: thursdays 14.00 UTC ...nteresting PHD thesis I read about the other types of contributions, e.g., documentation, testing, support, that are vital parts of the community in FLOSS
    29 KB (5,188 words) - 09:35, 1 March 2011
  • | 4 August-11 August (Week 12)|| Brushing up the code , adding tests and documentation , removing bugs. ...re of Python. It has better unicode support which would make it easier for developers to work with strings which would now be in unicode as unicode is easier to
    12 KB (2,086 words) - 05:05, 22 March 2014
  • ====[http://docs.fedoraproject.org/en-US/ Fedora 18 Documentation]==== :Was broken in 3.8 kernel due to changes by gnome3 developers.
    16 KB (2,165 words) - 09:08, 11 May 2019
  • ...8n) and localization (l10n). The first step (I18n) is to provide tools and documentation to facilitate the second step (L10n). ...nds using the procedure adopted for turtleblocks.js. We need corresponding documentation of this process to enable it to be used immediately by GSOC participants wh
    20 KB (3,239 words) - 22:41, 6 June 2016
  • ...selves, e.g., a backup mechanism, documentation, etc. On the one hand, the developers have completed their work and are preparing to move on to the next phase: S
    7 KB (1,124 words) - 22:56, 28 July 2010
  • :'''Icarito-d234''': walterbender: we're working on documentation too: *Mission* :'''Icarito-d234''': cjl: sugar environment is developed by professional developers under contract for third parties
    25 KB (4,043 words) - 15:32, 2 December 2011
  • -> Start writing documentation of both Music Widgets and Music Blocks Challenges -> write tests and remaining documentation of work done,
    17 KB (2,852 words) - 09:36, 8 April 2016
  • ...en [[Sugar_Network/Concept#Targeted_audience|students, educators, software developers]]. It offers a social network to [[Sugar_Network/Declaration_of_purpose|ask :* 28-3 August - Write documentation (docstrings, a wiki page with description, help page to Help activity maybe
    16 KB (2,676 words) - 23:42, 23 March 2014
  • :'''<walter>''' Simon, please nominate lots of developers!! ...ething like this by requiring that new developers be sponsored by existing developers.
    43 KB (7,925 words) - 09:34, 1 March 2011
  • ...w to define a <code>Primitive</code> for a new block, so other TA (plugin) developers can make their blocks exportable. *** Write new documentation about how to create a new block, including creating new <code>Primitive</co
    9 KB (1,339 words) - 14:18, 7 October 2013
  • Activity Help https://help.sugarlabs.org provides documentation for Sugar and the XO laptop. ...hundreds of other applications. There are currently thousands of software developers around the world developing content for the Sugar and OLPC .
    9 KB (1,453 words) - 16:33, 29 April 2020
  • ...e and I like the idea of learning while contributing to both end users and developers. | August 11-15, 18-22 || Writing documentation
    8 KB (1,359 words) - 17:22, 25 March 2014
  • have the opportunity to tap the knowledge of the world’s best developers, and work with them. * Documentation of features that are implemented, on wiki pages.
    16 KB (2,657 words) - 16:58, 17 May 2017
  • ...pport base and gathering place for the community of educators and software developers who want to extend the platform and who have been creating Sugar-compatible * To provide localization and internationalization of software, content, and documentation.
    10 KB (1,382 words) - 14:22, 8 April 2024
  • The meeting is targeted to Sugar core and activity developers, but everyone interested is welcome to join. We try to open the development ...ks planet, preparing new release, pitch visualisation, Clock activity user documentation, and creating tasks for GSoC.
    59 KB (8,636 words) - 17:29, 10 April 2018
  • ...ter alternative).I will add speech recognition within activities and add a documentation for every activity with certain keywords that will perfrom a task. | 1 August- 11 August || Add tests and documentation
    13 KB (2,101 words) - 09:53, 21 March 2014
  • https://developers.google.com/open-source/gci/resources/contest-rules https://developers.google.com/open-source/gci/resources/contest-rules
    42 KB (6,086 words) - 20:49, 29 December 2016
  • ...ftware that would be used by millions of people by coordinating with other developers all round the globe, is something that has always fascinated me. * Documentation and Update the wiki page of Journal, describe the new features that are add
    18 KB (2,900 words) - 07:37, 28 March 2016
  • ...eciate their kids' creations by commenting on their projects. For activity developers they could show what their activities can do and how to do them in Teacher' | July 14 - July 29 || Buffer time for any delays and documentation.
    13 KB (2,005 words) - 08:24, 4 May 2013
  • ...g glue between the speech-recognition technologies and educational content developers. This project is about filling the gap &ndash;within the Sugar Learning Pla ...n be tested in the field; an Assistive Technology Guide for Sugar Activity Developers
    20 KB (3,134 words) - 09:37, 5 June 2014
  • ...is now managed by a whole bunch of people contributions including code and documentation and translation and all that so that's sugar it's an entity that we've esta ...ion because in the world of feature the way they manage things is software developers do teachers are not comfortable with a lot of things that software developm
    29 KB (5,557 words) - 16:21, 26 June 2016
  • ...providing localization and internationalization of software, content, and documentation; and providing integration and customization ser *(09:48:01 AM) aa: I´m worried about how to include the documentation, translation, and pedagogical responsabilities we talked about in a busines
    41 KB (6,361 words) - 20:15, 24 February 2010
  • ...r_Plan | our plan]] and document everything we do weather it works or not. Documentation will either be on this wiki or directly in the code that we modify and/or c ...emailing the Math4 group to explain our situation and look for interested developers to continue this project.
    10 KB (1,732 words) - 21:52, 31 August 2009
  • ...he project up or continue it. Final delivery will be an OLPC activity with documentation, artwork, and source code.
    9 KB (1,434 words) - 13:46, 8 September 2010
  • ...removing bugs, improving compatibility, improving code structure and begin documentation * If I am unable to reach them, I can ask other community developers for help in the IRC and the mailing list
    10 KB (1,662 words) - 14:10, 25 March 2016
  • ..., and reflect with the mission to support the Sugar community of users and developers and establish regional, autonomous "Sugar Labs" around the world to help le *Documentation for the dashboard
    10 KB (1,600 words) - 09:49, 25 March 2016
  • | Gonzalo Odiard||Add Poll activity documentation ...communities. On behalf of the community, we give our warmest thanks to the developers and contributors who made this Sugar release possible.
    24 KB (3,501 words) - 11:09, 15 May 2016
  • This is the basic series of steps that most online documentation on python suggests to use when trying to work with threads in python. The p ...ctivity, we can be more comfortable writing entries in the Almanac to help developers write error-free code.
    19 KB (2,915 words) - 21:32, 23 February 2010
  • ...o have grown up with Sugar have transitioned from Sugar users to Sugar App developers to Sugar maintainers. They hang out on IRC with the global Sugar developer Tasks must fall within one of these five categories: [[#Documentation/Training]]; [[#Outreach/Research]]; [[#User Interface]]; [[#Quality Assuran
    31 KB (4,396 words) - 00:58, 21 November 2013
  • <walterbender> Documentation is a acceptable task. ...ome ideas regarding tasks which range from social media to our core design documentation. I want the students to feel that what they've made is being used by SL, be
    24 KB (3,900 words) - 17:16, 5 October 2018
  • ...ter met with Samson after the meeting to discuss details of a Music Blocks documentation project for teachers might look like. ...al-template Creating the organization proposal | Season of Docs - Google Developers Season of Docs Language English Bahasa Indonesia Deutsch Español Français
    11 KB (1,950 words) - 19:56, 17 March 2021
  • | <5 August - 11 August> || Clean up UI, Fix bugs, Write documentation ...olvement. If my mentor isn't around, I'm sure there will always be willing developers from the sugar community that I can depend on. Also, depending upon the typ
    10 KB (1,675 words) - 10:01, 21 March 2014
  • * Documentation # Write documentation
    17 KB (2,668 words) - 05:34, 10 April 2015
  • ...up the documentation for Turtle Confusion JS on wiki page.<br> Update the documentation of Abacus JS and FotoToons JS If my mentor is not around, there would be other open source developers on IRC whom I can reach out for help. I also have a lot of seniors in my co
    17 KB (2,841 words) - 12:41, 27 March 2015
  • My working style is characterized by a high level of documentation, be it inline comments or commit messages. ...ect, this experiment is a worthwhile bet at turning Sugar users into Sugar developers.
    17 KB (2,851 words) - 12:38, 13 June 2013
  • | 4 August-11 August (Week 12)|| Brushing up the code , adding tests and documentation , removing bugs. ...rease my knowledge and skill by working with very experienced and skilled developers .<br />
    13 KB (2,165 words) - 05:03, 22 March 2014
  • ...aptops, I think having better functionality (and better documentation) for developers to build rich communicative applications is a high priority.
    28 KB (3,937 words) - 21:32, 23 February 2010
  • * Topic for #sugar-meeting is: The meeting channel for the sugar developers (sugarlabs.org) | see also #sugar | meeting time: thursdays 14.00 UTC :'''<walter_>''' I'm greedy: I want the teachers to become developers!
    39 KB (7,263 words) - 09:35, 1 March 2011
  • ...and help with quality assurance; some are writing documentation for Sugar developers and for those who use Sugar in the field; some are developing new scenarios
    16 KB (2,639 words) - 16:32, 17 January 2013
  • :'''<tomeu>''' cjb: yeah, but if we stop having developers, we won't have nobody to fly around :'''<tomeu>''' mchua: we have lots of developers, few maintainers
    31 KB (5,392 words) - 00:17, 2 March 2011
  • ..., and reflect with the mission to support the Sugar community of users and developers and establish regional, autonomous "Sugar Labs" around the world to help le * Preparing documentation for final changes
    12 KB (1,876 words) - 12:25, 25 March 2016
  • Work on Documentation | Clean the code, improve documentation, and submit code .
    21 KB (3,514 words) - 04:34, 25 March 2016
  • | <16 August - 20 August> || Write the documentation and prepare for the final evaluation. ...rflow. If all other things fail, I am in a college with large community of developers to whom I can go to and seek help. If I am still stuck on the problem I wil
    13 KB (2,177 words) - 10:47, 19 April 2015
  • # This is a new project while Moodle has lots of developers and a very healthy community. Work on documentation
    20 KB (3,364 words) - 21:35, 14 April 2009
  • ...o have grown up with Sugar have transitioned from Sugar users to Sugar App developers to Sugar maintainers. They hang out on IRC with the global Sugar developer [See https://developers.google.com/open-source/gci/resources/getting-started]
    55 KB (7,873 words) - 15:24, 3 December 2014
  • * Developers: please continue to file feature requests directly in the [http://bugs.suga : This request has been posted to the Sugar developers mailing list at http://lists.sugarlabs.org/archive/sugar-devel/2010-May/024
    25 KB (4,047 words) - 00:07, 14 August 2017
  • | Aug 23-Aug 25 || Implement Mentor's suggestions if any. Write up documentation & wiki for PhysicsJS & DimensionJS ...evel.sugarlabs.narkive.com/ Mailing List]''' as well that would help other developers for regular updates on PhyscisJS and DimensionsJS Development.
    14 KB (2,237 words) - 14:35, 25 March 2015
  • ...ghest priorities, followed by the rest of the [[#Toolkits / Frameworks for developers]]. These are generally hard, though, so we would need you to give us eviden The toolkit would encapsulate the low-level interface to allow activity developers to easily deploy distributed task collaboration.
    38 KB (5,778 words) - 20:38, 22 December 2016
  • == What's new for developers == ...communities. On behalf of the community, we give our warmest thanks to the developers and contributors who made this Sugar release possible.
    37 KB (5,492 words) - 14:51, 2 July 2014
  • 14 August - 21 August Polish up the UI, and review the documentation. developers to add additional functionalities in future.
    17 KB (2,840 words) - 09:43, 17 May 2017
  • -> Documentation of work done so far ...eb, related links to the context. If it does not work, then I’ll ask other developers on irc for help, or I’ll drop a mail on mailing list. In college I’m su
    18 KB (2,994 words) - 13:55, 27 March 2015
  • ...y the community. Becoming a part of a community which involves hundreds of developers in different time zones, working together in a coordinated fashion to devel ...page of the project with knowledge base on how to best use this tool. Add documentation and polish the UI.
    22 KB (3,817 words) - 14:59, 27 March 2015
  • <noinclude>{{Developers}}</noinclude>__TOC__ ''This documentation effort was started by [[User:Bert|Bert]] on the [http://wiki.laptop.org/go/
    36 KB (5,530 words) - 22:17, 19 January 2016
  • :::Communicate with other sugar users and developers on IRC ...n-sugar-activities/ '''make-your-own-sugar-activities'''] RECOMMENDED for developers.
    68 KB (9,685 words) - 19:08, 24 June 2012
  • :[[Platform_Team/Sweets/Getting_started|Request for better Documentation of installs]] :(For developers)
    52 KB (7,644 words) - 12:15, 12 May 2019