Search results

Jump to: navigation, search
  • Sugar Labs Activity Team - Goal is to provide high quality activities for Sugar. This site lists responsibilities and tips. On their contact page they hav
    12 KB (1,966 words) - 09:50, 7 February 2017
  • '''Sugar Labs Project''' ... the form or reports. Each ticket is structured in the same way as in the Sugar Lab Project
    8 KB (1,236 words) - 09:38, 7 February 2017
  • Sugar Labs==== * Development Team: build and maintain the core Sugar environment; there is no coordinator and 4 "people" listed; there is no ove
    15 KB (2,418 words) - 14:39, 19 June 2018
  • === Sugar Labs === ==== What is unique about each Sugar Labs team? ====
    30 KB (5,015 words) - 09:37, 7 February 2017
  • === The Sugar Labs Project === The Sugar Labs bug tracker page lists the following information about each bug ticket:
    12 KB (1,965 words) - 09:26, 7 February 2017
  • ==== The Sugar Labs Project ==== *#* Builds and Maintains the core Sugar Project.
    12 KB (1,906 words) - 09:34, 7 February 2017
  • ==== Sugar Labs ==== ...butor? How is this structure different than the one you found on the Sugar Labs website?
    17 KB (2,676 words) - 09:49, 7 February 2017
  • 1. Sugar Lab <br> C. Repository. The Sugar Labs repository appears to be a public repository that individuals clone.
    3 KB (440 words) - 01:49, 7 February 2017
  • Sugar Labs Project Repository -- https://github.com/sugarlabs/sugar/ Click the "Commits" link and determine the date of the last commit (an upd
    17 KB (2,625 words) - 12:13, 25 October 2017
  • ...p/Project_Anatomy_Activity Anatomy of a FOSS Project] - Guided Tour: Sugar Labs Project''' ...eams have clearly defined mission statements and distinct roles within the Sugar Project and collaborate/coordinate with other teams. Both the Activity and
    8 KB (1,195 words) - 12:54, 16 October 2017
  • * The Sugar Labs Project ** ''Summarize the information under 'Contacts' for several teams of Sugar Labs.'' It is typical for a team to provide information about team coordinator(s
    20 KB (3,136 words) - 01:47, 7 February 2017
  • === Project Anatomy Activity - Sugar Labs === ...ings that students ''do'' to foster learning) that consequently run on the Sugar platform
    32 KB (5,316 words) - 01:49, 7 February 2017
  • == Sugar Labs Entry == Community: The Activity Team for Sugar had a large list of people and two coordinators. I thought it was interesti
    14 KB (2,482 words) - 01:49, 7 February 2017
  • '''SUGAR LABS PROJECT''' ...ers, they provide resources and oversight for the organized development of Sugar.
    34 KB (5,610 words) - 01:48, 7 February 2017
  • ====The Sugar Labs Project==== ...gar environment; and the Documentation team is in charge of supporting the Sugar community with helpful documentation (tutorials, reference materials, etc.)
    20 KB (3,186 words) - 01:49, 7 February 2017
  • Project Anatomy Activity - Sugar Labs ...s to be a web-based common repository. The URL is git://git.sugarlabs.org/sugar-base/mainline.git
    14 KB (2,177 words) - 12:54, 15 October 2018
  • :'''The Sugar Labs Project''' :''The types of tickets found on the Sugar Labs bug tracker are <nowiki>"</nowiki>defect<nowiki>"</nowiki> and <nowiki>"</n
    9 KB (1,361 words) - 01:48, 7 February 2017
  • ===Sugar Project=== * The Sugar code repository is web-based, as evidenced by the fact that I can browse th
    13 KB (1,934 words) - 01:36, 7 February 2017
  • '''Sugar Labs Project''' ...butor? How is this structure different than the one you found on the Sugar Labs website?
    13 KB (1,985 words) - 01:29, 7 February 2017
  • '''Sugar Labs Project''' ...ttention to the issue is desired it should be announced with a link on the sugar-devel list serve.
    20 KB (3,138 words) - 01:29, 7 February 2017

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

Personal tools
Namespaces
Variants
Views
Actions
Events
Learning Resources
HFOSS Projects
Evaluation
Navigation
Toolbox