DerivativeTeam
|
Size: 992
Comment:
|
Size: 4120
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 5: | Line 5: |
| This team is currently up for adoption. There are a number of issues that must be worked out between Canonical the company and Ubuntu the community before the team can move forward. If you have the time and energy, drop me a note and I will reassign ownership. Thanks David |
|
| Line 6: | Line 9: |
| = Mission = | |
| Line 7: | Line 11: |
| This is an example of a sample team website, and you can use these pages when building your own website. This very first paragraph should be used to explain what your team does, the aims of the team and how people can get involved. This paragraph is where you really grab the interest of the reader s make it exciting, easy to read and concise. | '''Make it easy and efficient to create and maintain a Linux distribution that is based on Ubuntu''' |
| Line 9: | Line 13: |
| This is the front page of your team's website, and you may want to put recent news, events and other information on here to help keep it current and interesting. Use your imagination, and you can create a really nice website. :) | = Goals = |
| Line 11: | Line 15: |
| == Latest News == | There three areas where Ubuntu and Ubuntu derivative distributions can collaborate: bug handling, code sharing, and code customizations. |
| Line 13: | Line 17: |
| * News item * Another news item |
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 16: | Line 19: |
| == Latest Events == | 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 18: | Line 21: |
| * This event * That event |
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 [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. |
Include(DerivativeTeam/Header)
ContentsBRTableOfContents |
This team is currently up for adoption. There are a number of issues that must be worked out between Canonical the company and Ubuntu the community before the team can move forward. If you have the time and energy, drop me a note and I will reassign ownership. Thanks David
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 [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
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.
DerivativeTeam (last edited 2020-01-05 04:38:23 by haydenb)