DerivativeTeam

Differences between revisions 5 and 6
Revision 5 as of 2007-03-02 07:49:19
Size: 1059
Editor: 69-179-20-34
Comment:
Revision 6 as of 2007-03-02 22:01:19
Size: 1560
Editor: s3-165
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
I am starting the DerivativeTeam as a response to a Lugradio segment a few weeks ago in which the presenter stated that 'Ubuntu and Linspire working together will be a cataclysmic event that will will cause the world to stop rotating around its axis.' I on the other hand, feel that collaboration with derivative distributions can be benificial for everyone. == Team Mission ==

There three areas that we can start collaboration with our derivatives: 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.

Include(DerivativeTeam/Header)

Team Mission

There three areas that we can start collaboration with our derivatives: 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.

Disclaimer, I am not an employee of Canonical, Ubuntu, Linspire, or any other derivative that I am interested in collaborating with. I do not speak on their behalf or am I privy to their internal strategy. I am a guy who likes to sit in coffee shops and peck away at my laptop when I have a few spare minutes.

Latest News

  • Team Formation

Latest Events

  • Team Formation


[:CategoryDerivativeTeam]

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