DerivativeTeam
|
Size: 1279
Comment:
|
Size: 3717
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 8: | Line 8: |
| == Team Mission == | [rephrase - not from Ubuntu's perspective] |
| Line 10: | Line 10: |
| There three areas that we can start collaboration with our derivatives: Bug handling, patch pushing, and developing a code base that is easily customizable. |
= Mission = |
| Line 14: | Line 12: |
| 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. |
'''Make it easy and efficient to create and maintain a Linux distribution that is based on Ubuntu''' |
| Line 18: | Line 14: |
| 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. |
== Goals == |
| Line 23: | Line 16: |
| 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. |
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 community's 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. |
| Line 29: | Line 25: |
| == Latest News == | 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 == 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 == 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 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. The kernel development process has shown how well distributive version control systems such as git and brz can work. = Latest News = |
| Line 33: | Line 70: |
| == Latest Events == | = Latest Events = |
Include(DerivativeTeam/Header)
ContentsBRTableOfContents |
Draft v1: DavidFarning
[rephrase - not from Ubuntu's perspective]
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 community's 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.
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
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.
- As the number of knowledgeable users of grows, so does the developer base.
- As the number of computers running the distribution growths, so does the hardware support.
- 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:
- Work together on bug handling.
- Share a common code base.
- 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
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 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.
The kernel development process has shown how well distributive version control systems such as git and brz can work.
Latest News
- Team Formation
Latest Events
- Team Formation
DerivativeTeam (last edited 2020-01-05 04:38:23 by haydenb)