DerivativeTeam

Differences between revisions 14 and 23 (spanning 9 versions)
Revision 14 as of 2007-03-14 11:29:29
Size: 3717
Editor: 69-179-21-245
Comment:
Revision 23 as of 2008-08-06 17:01:22
Size: 3837
Editor: localhost
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
[[Include(DerivativeTeam/Header)]] <<Include(DerivativeTeam/Header)>>
Line 3: Line 3:
||<tablestyle="float:right; font-size: 0.9em; width:30%; background:#F1F1ED; background-repeat: no-repeat; background-position: 98% 0.5ex; margin: 0 0 1em 1em; padding: 0.5em;">'''Contents'''[[BR]][[TableOfContents]]||


'''Draft v1:''' DavidFarning

[rephrase - not from Ubuntu's perspective]
||<tablestyle="float:right; font-size: 0.9em; width:30%; background:#F1F1ED; background-repeat: no-repeat; background-position: 98% 0.5ex; margin: 0 0 1em 1em; padding: 0.5em;"><<TableOfContents>>||
Line 14: Line 9:
== Goals == = Goals =
Line 18: Line 13:
1 Bug handling. Make Ubuntu's bug process compatible with derivative distribution's bug processes to ease the flow of information back and forth. This includes issue triage and automatic crash reporting systems.  1. Bug handling. Make Ubuntu's bug process compatible with derivative distribution's bug processes to ease the flow of information back and forth. This includes issue triage and automatic crash reporting systems.
Line 20: Line 15:
2 Code sharing. Insure that Ubuntu and Ubuntu derivative distributions are able to easily share the same code base. Combine resources so that the Ubuntu and it's derivative community's can develop and push good patches upstream.  1. Code sharing. Insure that Ubuntu and Ubuntu derivative distributions are able to easily share the same code base. Combine resources so that the Ubuntu and it's derivative communities' can develop and push good patches upstream.
Line 22: Line 17:
3 Code Customizing. Insure that it is easy and efficient for Ubutu derivative distributions to customize Ubuntu code to meet their user's and customers needs.  1. Code Customizing. Insure that it is easy and efficient for Ubuntu derivative distributions to customize Ubuntu code to meet their user's and customers needs.
Line 24: Line 19:

and 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.

== Philosophy ==
= Philosophy =
Line 31: Line 23:
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. 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 35: Line 27:
 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.
 1. As the number of computers running the distribution growths, so does the hardware support.
 1. As the number of installed systems grow, so does the third party software support.
Line 43: Line 35:
 2. Encourage Customizations.  1. Encourage Customizations.
Line 49: Line 41:
== Common Code base == == Common Code Base ==
Line 51: Line 43:
Currently, the single biggest source of friction in maintaining a derivative is merging changes with the base distribution. Establishing a common code base will allow hardware and outside software vendors to develop products with the knowledge that they work across all distributions.
Line 53: Line 45:
Establishing a common code base will allow hardware and outside software vendors to develop products knowing that they work across all distributions.

  This friction can be reduced by sharing an easily extendable base of common code.



== Patch Management ==

Collaborative patch management will help maintain the common code base.
Collaborative patch management will help maintain the common code base. Currently, the single biggest source of friction between Ubuntu and Ubuntu derivative's is sharing changes. It is often necessary for Ubuntu derivatives to maintain large patch sets. In many cases it is more efficient to merge these patches into the Ubuntu code and push them upstream. It makes no sense for all of us to drag around huge patch sets.
Line 65: Line 49:
== Customizations ==
Line 66: Line 51:
= Latest News = '''Write'''
Line 68: Line 53:
 * Team Formation target audiences:
 1. loco localizations
 1. package super sets
 1. lightly modified (fluxbuntu)
 1. heavily modified (linspire)
Line 70: Line 59:
= Latest Events = we should take steps to insure that a derivatives value added bits integrate closely with Ubuntu's base.
Line 72: Line 61:
 * Team Formation This friction can be reduced by sharing an easily extendable base of common code.
Line 75: Line 64:
[:CategoryDerivativeTeam] [[CategoryDerivativeTeam]]

Mission

Make it easy and efficient to create and maintain a Linux distribution that is based on Ubuntu

Goals

There three areas where Ubuntu and Ubuntu derivative distributions can collaborate: bug handling, code sharing, and code customizations.

  1. Bug handling. Make Ubuntu's bug process compatible with derivative distribution's bug processes to ease the flow of information back and forth. This includes issue triage and automatic crash reporting systems.
  2. Code sharing. Insure that Ubuntu and Ubuntu derivative distributions are able to easily share the same code base. Combine resources so that the Ubuntu and it's derivative communities' can develop and push good patches upstream.
  3. Code Customizing. Insure that it is easy and efficient for Ubuntu derivative distributions to customize Ubuntu code to meet their user's and customers needs.

Philosophy

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

According to 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. Work together on bug handling.
  2. Share a common code base.
  3. Encourage Customizations.

Bug Handling

Collaborative bug handling 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.

Common Code Base

Establishing a common code base will allow hardware and outside software vendors to develop products with the knowledge that they work across all distributions.

Collaborative patch management will help maintain the common code base. Currently, the single biggest source of friction between Ubuntu and Ubuntu derivative's is sharing changes. It is often necessary for Ubuntu derivatives to maintain large patch sets. In many cases it is more efficient to merge these patches into the Ubuntu code and push them upstream. It makes no sense for all of us to drag around huge patch sets.

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

Customizations

Write

target audiences:

  1. loco localizations
  2. package super sets
  3. lightly modified (fluxbuntu)
  4. heavily modified (linspire)

we should take steps to insure that a derivatives value added bits integrate closely with Ubuntu's base.

This friction can be reduced by sharing an easily extendable base of common code.


CategoryDerivativeTeam

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