647
edits
Changes
Jump to navigation
Jump to search
Line 3:
Line 3: − +
Development Team/Code guidelines (view source)
Revision as of 04:30, 7 August 2009
, 04:30, 7 August 2009→Introduction
= Introduction =
= Introduction =
The community around Sugar is very diverse and only a small part of it are directly involved in software development. Of those, an even smaller part is personally responsible for the quality of the software, its growth, and its availability to localizators, distributors and deployers. See [[Development_Team/Release/Modules]] for a list of modules with their maintainers and peers.
The community around Sugar is very diverse and only a small part of it are directly involved in software development. Of those, an even smaller part is personally responsible for the quality of the software, its growth, and its availability to translators, distributors and deployers. See [[Development_Team/Release/Modules]] for a list of modules with their maintainers and peers.
But this smaller group of people aren't the only ones that can contribute to the development of Sugar itself. Anyone with some spare time and enough skills and passion can make significant contributions to Sugar, but in order to bound to a limit the maintenance work the submitted code needs to have some characteristics, explained in this page.
But this smaller group of people aren't the only ones that can contribute to the development of Sugar itself. Anyone with some spare time and enough skills and passion can make significant contributions to Sugar, but in order to bound to a limit the maintenance work the submitted code needs to have some characteristics, explained in this page.