1,285
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − <noinclude>{{GoogleTrans-en}}{{TeamHeader|Development Team|roadmap_link=Release/Roadmap/{{Upcoming Stable Release}}}}</noinclude>{{TOCright}}+ Line 5:
Line 5: − + − + − + + + + + + + + + + + + + + + + + + + − + + + + + − + − + − + − + − + + − + − + − '''[[/Release/CurrentRelease/Sucrose]]'''+ + + + + + + + +
bugsquad obsolete
{{Graduate|Move to http://developer.sugarlabs.org}}
==Mission==
==Mission==
== Meetings ==
== Meetings ==
The development team has a regular IRC meeting (See the Sugar Labs [[Sugar Labs#Calendar|calendar]]). Find out more about the meeting time and upcoming and earlier meetings [[Development Team/Meetings|here]]. Help: [[Sugar_Labs/Contacts#IRC.2C_Internet_Relay_Chat |Using IRC]]
The development team had regular IRC meetings up until 2010 (See the Sugar Labs [[Sugar Labs/Events|calendar]]). Find out more about the meeting time and upcoming and earlier meetings [[Development Team/Meetings|here]]. Help: [[Sugar_Labs/Communication channels#IRC.2C_Internet_Relay_Chat |Using IRC]]
== Mini tutorials ==
== Team lead ==
The development team hosts mini tutorials covering short (five-minute) topics relevant to writing Sugar activities. Please refer to the [[Development Team/Mini tutorials|Mini tutorials page]] to sign up for teaching a topic.
The Development Team coordinator position carried administrative tasks such as organizing regular meetings, keeping the TODO list updated, keeping the development team membership list updated, and making sure that the team has clear goals and is kept focused. We were accepting nominations for an election for this position, see [[Development_Team/Team_Lead_Candidates_2010_05]], but the position is now open.
== Releases ==
See the [[Development Team/Release]] page.
== Release manager ==
We have defined the role of the release manager for the past 3 releases as the following:
* Setting the schedule.
* Making sure that the [[Features/Policy]] is followed by submitters.
* Keeping this wiki updated with the released modules and making sure to have final release notes available.
* Sending email reminders about approaching Freezes, tarball due dates, etc.
== Schedule ==
A schedule was based on [http://live.gnome.org/Schedule GNOME releases], a 6-month release cycle.
Now, releases are scheduled in an ad-hoc manner if at all.
<!-- == Mini tutorials ==
The development team hosts mini tutorials covering short (five-minute) topics relevant to writing Sugar activities. Please refer to the [[Development Team/Mini tutorials|Mini tutorials page]] to sign up for teaching a topic. -->
== Development systems ==
== Development systems ==
All of core Sugar development except system-dependent modifications can be done on a standard computer by compiling [[Development Team/Jhbuild|jhbuild]] and editing with your favorite editor (eclipse/pydev, emacs, vim, etc.). Activity (aka application) development can be done in many environments using pre-compiled [[Supported_systems#Sucrose|packages]] ("sucrose") or [[Supported_systems#Starch|images]] ("starch").
All of core Sugar development except system-dependent modifications can be done on a standard computer by [https://developer.sugarlabs.org/dev-environment.md.html installing Sugar].
Activity (aka application) development can be done in many environments using pre-compiled [[Supported_systems#Sucrose|packages]] ("sucrose") or [[Supported_systems#Starch|images]] ("starch"). For example, see [[Debian]], [[Ubuntu]], or [[Fedora]].
See also the now unmaintained [[Platform Team/Sweets]] technology.
== Document your work ==
== Document your work ==
See [[/Feature Template]] for an example.
See [[Features/Feature Template]] for an example.
== Code review ==
== Code review ==
Patches to Sugar are more than welcome. There are guidelines for [[Development Team/CodeReview|code review]] to get them accepted.
Patches to Sugar are more than welcome. There are guidelines for [[Development Team/Code Review|code review]] to get them accepted.
== Package Sucrose for your distribution ==
== Package Sucrose for your distribution ==
* Currently there are efforts to maintain Sugar as part of [[Community/Distributions/Debian|Debian]], [[Community/Distributions/Ubuntu|Ubuntu]], and [[Community/Distributions/Fedora|Fedora]].
* Currently there are efforts to maintain Sugar as part of [[Debian]], [[Ubuntu]], and [[Fedora]].
* Help us maintain good communication with distribution packagers to assist in this.
* Help us maintain good communication with distribution packagers to assist in this. Join the [[Platform Team]].
== Kill Bugs! ==
== Kill Bugs! ==
* See our bug tracking system http://dev.sugarlabs.org/
* Help test. See [[{{Upcoming Stable Release}}/Testing]].
* See our bug tracking system https://bugs.sugarlabs.org/ or Issues on GitHub.
== Project Ideas ==
== Project Ideas ==
* Want to work on an interesting Sugar project, or have an idea of your own? Check the [[Development Team/Project Ideas|project ideas]] page.
* Want to work on an interesting Sugar project, or have an idea of your own? Check the [[Development Team/Project Ideas|project ideas]] page.
* See the [[Summer of Code]] and [[Sugar Summer Program]] efforts; ideas, students, mentors, and organization help are welcomed.
* Prepare a new Sugar [[Features/Policy|Feature]].
==Release Notes==
* See the [[Summer of Code]] project; ideas, students, mentors, and organization help are welcomed.
== Platform Release Cycles ==
{{Template:Platform Cycle Linkbar}}
[[Template:Current Stable Release]] holds the release number.
See [[{{Current Stable Release}}/Notes]] for the release notes.
[[Development Team/Release]]
== Subpages ==
== Subpages ==