DerivativeTeam

Differences between revisions 1 and 15 (spanning 14 versions)
Revision 1 as of 2007-03-02 05:38:46
Size: 1366
Editor: d26-97
Comment:
Revision 15 as of 2007-03-14 12:09:28
Size: 3935
Editor: 69-179-21-245
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
[[Include(DerivativeTeam/Header)]]
Line 3: Line 5:
= Mission =
Line 4: Line 7:
= Introduction =
## Describe:
## the teams's purpose and community role
## the team tasks and work
## who might be interested in joining/getting involved with the team
'''Make it easy and efficient to create and maintain a Linux distribution that is based on Ubuntu'''
Line 10: Line 9:
= 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.
== Goals ==
Line 13: Line 11:
= 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.
There three areas where Ubuntu and Ubuntu derivative distributions can collaborate: bug handling, code sharing, and code customizations.
Line 16: Line 13:
= 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.
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 19: Line 15:
= Launchpad Membership Policy =
## Describe your Launchpad team membership policy here.
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.
Line 22: Line 17:
= Meetings =
## Link to Meeting Agendas and old meeting summaries here.
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.

== 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 [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. Work together on bug handling.
 1. Share a common code base.
 2. 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.



= Latest News =

 * Team Formation

= Latest Events =

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

----
CategoryUbuntuTeams
[:CategoryDerivativeTeam]

Include(DerivativeTeam/Header)

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 Ubutu 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 [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. 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.

Latest News

  • Team Formation

Latest Events

  • Team Formation


[:CategoryDerivativeTeam]

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