DerivativeTeam
|
Size: 1366
Comment:
|
Size: 1560
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| [[Include(DerivativeTeam/Header)]] |
|
| Line 3: | Line 5: |
| == Team Mission == | |
| Line 4: | Line 7: |
| = 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 |
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 10: | Line 11: |
| = 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. |
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 13: | Line 15: |
| = 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. |
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. |
| Line 16: | Line 20: |
| = 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. |
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 19: | Line 25: |
| = Launchpad Membership Policy = ## Describe your Launchpad team membership policy here. |
|
| Line 22: | Line 26: |
| = Meetings = ## Link to Meeting Agendas and old meeting summaries here. |
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 |
| Line 26: | Line 37: |
| '''Sub-pages :''' [[Navigation(children,1)]] ---- ---- CategoryUbuntuTeams |
[:CategoryDerivativeTeam] |
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.
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
DerivativeTeam (last edited 2020-01-05 04:38:23 by haydenb)