DerivativeTeam
|
Size: 1404
Comment:
|
Size: 3717
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 6: | Line 6: |
| = 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 |
'''Draft v1:''' DavidFarning |
| Line 12: | Line 8: |
| = 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. |
[rephrase - not from Ubuntu's perspective] |
| Line 15: | Line 10: |
| = 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. |
= Mission = |
| Line 18: | Line 12: |
| = 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. |
'''Make it easy and efficient to create and maintain a Linux distribution that is based on Ubuntu''' |
| Line 21: | Line 14: |
| = Launchpad Membership Policy = ## Describe your Launchpad team membership policy here. |
== Goals == |
| Line 24: | Line 16: |
| = Meetings = ## Link to Meeting Agendas and old meeting summaries here. |
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. 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 = * Team Formation = Latest Events = * Team Formation |
| Line 28: | Line 75: |
| '''Sub-pages :''' [[Navigation(children,1)]] ---- ---- CategoryUbuntuTeams |
[:CategoryDerivativeTeam] |
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)