Difference between revisions of "Development Team"

From Sugar Labs
Jump to navigation Jump to search
m (create page)
 
 
(84 intermediate revisions by 23 users not shown)
Line 1: Line 1:
{{DevelopmentTeam/Header}}
+
==Outdated==
{{stub}}
+
When Sugar Labs was very large, we found it convenient and effective to divide into teams.  This was one of the teams.
  
 +
==Mission==
 +
{{:Development Team/Mission}}
  
[[Category:DevelopmentTeam]]
+
== Meetings ==
 +
The development team had regular IRC meetings on Tuesdays at 5PM ET (22UTC) in the #sugar-meeting channel of irc.freenode.net (See the Sugar Labs [[Sugar Labs/Events|calendar]]). One could 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]]
 +
 
 +
== Team lead ==
 +
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 had clear goals and was 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:
 +
 
 +
* Making sure that the [[Features/Policy]] is followed by submitters,
 +
* Completing a formal test before release,
 +
* Making releases.
 +
 
 +
== 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 hosted 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 ==
 +
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 ==
 +
See [[Features/Feature Template]] for an example.
 +
 
 +
== Code review ==
 +
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 ==
 +
* 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. Join the [[Platform Team]].
 +
 
 +
== Kill Bugs! ==
 +
* Help test. See [[{{Upcoming Stable Release}}/Testing]].
 +
* See our bug tracking system https://bugs.sugarlabs.org/ or Issues on GitHub.
 +
 
 +
== 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.
 +
* Prepare a new Sugar [[Features/Policy|Feature]].
 +
* 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 ==
 +
{{Special:PrefixIndex/Development Team/}}
 +
 
 +
 
 +
[[Category:Development Team]]
 +
[[Category:Team]]

Latest revision as of 18:13, 27 November 2019

Outdated

When Sugar Labs was very large, we found it convenient and effective to divide into teams. This was one of the teams.

Mission

The mission of the Development Team is to build and maintain the core Sugar environment. This includes specifying and implementing new features in conjunction with the Design Team, fixing bugs as they are found by the Testing team and the Sugar community, and generally making Sugar awesome in all ways.


Meetings

The development team had regular IRC meetings on Tuesdays at 5PM ET (22UTC) in the #sugar-meeting channel of irc.freenode.net (See the Sugar Labs calendar). One could find out more about the meeting time and upcoming and earlier meetings here. Help: Using IRC

Team lead

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 had clear goals and was 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:

  • Making sure that the Features/Policy is followed by submitters,
  • Completing a formal test before release,
  • Making releases.

Schedule

A schedule was based on GNOME releases, a 6-month release cycle.

Now, releases are scheduled in an ad-hoc manner if at all.

Development systems

All of core Sugar development except system-dependent modifications can be done on a standard computer by installing Sugar.

Activity (aka application) development can be done in many environments using pre-compiled packages ("sucrose") or images ("starch"). For example, see Debian, Ubuntu, or Fedora.

See also the now unmaintained Platform Team/Sweets technology.

Document your work

See Features/Feature Template for an example.

Code review

Patches to Sugar are more than welcome. There are guidelines for code review to get them accepted.

Package Sucrose for your distribution

  • 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. Join the Platform Team.

Kill Bugs!

Project Ideas

  • Want to work on an interesting Sugar project, or have an idea of your own? Check the project ideas page.
  • Prepare a new Sugar Feature.
  • See the Summer of Code project; ideas, students, mentors, and organization help are welcomed.

Platform Release Cycles

Sugar platform release version cycle: | 0.82 | 0.84 | 0.86 | 0.88 | 0.90 | 0.92 | 0.94 | 0.96 | 0.98 | 0.100 | 0.102 | 0.104 | 0.106 | 0.108 | 0.110 | 0.112 |

Template:Current Stable Release holds the release number.

See 0.112/Notes for the release notes.

Development Team/Release

Subpages