DerivativeTeam

Differences between revisions 1 and 13 (spanning 12 versions)
Revision 1 as of 2007-03-02 05:38:46
Size: 1366
Editor: d26-97
Comment:
Revision 13 as of 2007-03-06 02:01:07
Size: 3508
Editor: 121-72-137-56
Comment: copyediting
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
[[Include(DerivativeTeam/Header)]]
Line 4: Line 6:
'''Draft v1:''' DavidFarning

[rephrase - not from Ubuntu's perspective]
Line 5: Line 10:
## Describe:
## the teams's purpose and community role
## the team tasks and work
## who might be interested in joining/getting involved with the team
Line 10: Line 11:
= Contact =
## List the contact information of the team: Mailing-list, IRC channel and Web Forum as they may apply. Provide a link to the Launchpad page as a Team Member list if applicable. Consider how people will get in touch with you based on the contact information you supply.
One great strength of open source is the ability for everyone to improve and modify their software as they see fit. Ubuntu can benefit from this by developing a healthy ecosystem of derivative distributions that contribute back to the Ubuntu project.
Line 13: Line 13:
= How to Contribute =
## Describe easy ways to contribute to the team. These should look a lot like the bulleted points on the ContributeToUbuntu wiki page. Link to more detailed subpages as necessary.
According to [http://en.wikipedia.org/wiki/Metcalfe's_law Metcalfe's law], the value of a network is equal to square of the number of nodes. The value of a software distribution also grows at a rate that equal to the square of the number of installations.
Line 16: Line 15:
= Projects =
## List the team's current projects and tasks as well as status and contact persons for each one. Make it easy for new people to know who to ask and where to go to get involved with a specific project.
Three factors contribute to this nonlinear growth.
 1. As the number of knowledgeable users of grows, so does the developer base.
 2. As the number of computers running the distribution growths, so does the hardware support.
 3. As the number of installed systems grow, so does the third party software support.
Line 19: Line 20:
= Launchpad Membership Policy =
## Describe your Launchpad team membership policy here.
The freedom to take a piece of software and modify it is both an asset and a liability. Forks encourage experimentation and creativity. They can also result in fragmentation. One way to counter fragmentation, is to foster the growth of derivative distributions.
Line 22: Line 22:
= Meetings =
## Link to Meeting Agendas and old meeting summaries here.
Derivatives distributions are different from forks in three ways. They:
 1. have a common code base
 2. collaborate on patch management
 3. collaborate on issue tracking.

== Common Code base ==

Currently, the single biggest source of friction in maintaining a derivative is merging changes with the base distribution. This friction can be reduced by sharing an easily extendable base of common code.

Additionally, establishing a common code base will allow hardware and outside software vendors to develop products knowing that they work across all distributions.

== Patch Management ==

Collaborative patch management will help maintain the common code base.

The kernel development process has shown how well distributive version control systems such as git and brz can work.

== Issue Trackers ==

Collaborative issue tracking will increase the number of knowledgeable developers available to fix reported Issues. Initial triaging should be done by the derivative and escalated to where they can be most effectively handled.

= Team Mission =

There three areas where Ubuntu can start collaboration with its derivative distributions: bug handling, patch pushing, and developing a code base that is easily customizable.

1 Bug handling. Make our bug process as compatible as possible to ease the flow of information back and forth. This includes both triaging and automatic crash reports systems.

2 Patch Pushing. Clean up our patch system so that the Ubuntu specific bits can be identified and replaced with Derivative bits. Combine our resources on the common bits so that we can develop good patches to push upstream.

3 Customizing. Insure that for the most part we are using the same code base. There is no sense in all of us dragging around huge patch sets. Instead we should take steps to insure that a derivatives value added bits integrate closely with Ubuntu's base.

= Latest News =

 * Team Formation

= Latest Events =

 * Team Formation
Line 26: Line 62:
'''Sub-pages :''' [[Navigation(children,1)]]
----

----
CategoryUbuntuTeams
[:CategoryDerivativeTeam]

Include(DerivativeTeam/Header)

Draft v1: DavidFarning

[rephrase - not from Ubuntu's perspective]

Introduction

One great strength of open source is the ability for everyone to improve and modify their software as they see fit. Ubuntu can benefit from this by developing a healthy ecosystem of derivative distributions that contribute back to the Ubuntu project.

According to [http://en.wikipedia.org/wiki/Metcalfe's_law Metcalfe's law], the value of a network is equal to square of the number of nodes. The value of a software distribution also grows at a rate that equal to the square of the number of installations.

Three factors contribute to this nonlinear growth.

  1. As the number of knowledgeable users of grows, so does the developer base.
  2. As the number of computers running the distribution growths, so does the hardware support.
  3. As the number of installed systems grow, so does the third party software support.

The freedom to take a piece of software and modify it is both an asset and a liability. Forks encourage experimentation and creativity. They can also result in fragmentation. One way to counter fragmentation, is to foster the growth of derivative distributions.

Derivatives distributions are different from forks in three ways. They:

  1. have a common code base
  2. collaborate on patch management
  3. collaborate on issue tracking.

Common Code base

Currently, the single biggest source of friction in maintaining a derivative is merging changes with the base distribution. This friction can be reduced by sharing an easily extendable base of common code.

Additionally, establishing a common code base will allow hardware and outside software vendors to develop products knowing that they work across all distributions.

Patch Management

Collaborative patch management will help maintain the common code base.

The kernel development process has shown how well distributive version control systems such as git and brz can work.

Issue Trackers

Collaborative issue tracking will increase the number of knowledgeable developers available to fix reported Issues. Initial triaging should be done by the derivative and escalated to where they can be most effectively handled.

Team Mission

There three areas where Ubuntu can start collaboration with its derivative distributions: bug handling, patch pushing, and developing a code base that is easily customizable.

1 Bug handling. Make our bug process as compatible as possible to ease the flow of information back and forth. This includes both triaging and automatic crash reports systems.

2 Patch Pushing. Clean up our patch system so that the Ubuntu specific bits can be identified and replaced with Derivative bits. Combine our resources on the common bits so that we can develop good patches to push upstream.

3 Customizing. Insure that for the most part we are using the same code base. There is no sense in all of us dragging around huge patch sets. Instead we should take steps to insure that a derivatives value added bits integrate closely with Ubuntu's base.

Latest News

  • Team Formation

Latest Events

  • Team Formation


[:CategoryDerivativeTeam]

DerivativeTeam (last edited 2008-08-06 17:01:22 by localhost)