DerivativeTeam
|
Size: 992
Comment:
|
Size: 1560
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 5: | Line 5: |
| == Team Mission == | |
| Line 6: | Line 7: |
| There three areas that we can start collaboration with our derivatives: Bug handling, patch pushing, and developing a code base that is easily customizable. |
|
| 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. | 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. |
| Line 9: | Line 15: |
| 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. :) | 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. |
| Line 13: | Line 28: |
| * News item * Another news item |
* Team Formation |
| Line 18: | Line 32: |
| * This event * That event |
* Team Formation 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. |
Include(DerivativeTeam/Header)
ContentsBRTableOfContents |
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.
Latest News
- Team Formation
Latest Events
- Team Formation
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.
DerivativeTeam (last edited 2020-01-05 04:38:23 by haydenb)