GettingInvolved
|
Size: 524
Comment:
|
← Revision 31 as of 2010-08-03 16:29:44 ⇥
Size: 2008
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| [[Include(SugarTeam/Header)]] | <<Include(Sugar/Header)>> == Projects == Ubuntu Sugar Remix is a tightly focused project. Our goal is to combine the work of two upstream projects into a single user friendly product that will be used and supported in schools around the world. Please see the [[Sugar/Roadmap|road map]] for more details. |
| Line 3: | Line 5: |
| == Team TODO == | === Join === |
| Line 5: | Line 7: |
| * Package latest Sucrose release 0.81.6 (jmunro, joss_winn) * Review Debian packaging * Decide on whether we will use Debian packaging or not * Mail ubuntu-devel-discuss to announce team and project (morgs) * Blog on planet.u.c to announce team and project (morgs) * Review jmunro's packaging * See what dependencies we have for activities - like abiword, evince - so we can see what activities we can package * Package more activities (jmunro, joss_winn) |
The mailing list is: ubuntu-sugarteam@lists.ubuntu.com You can try the latest (not stable build) here = ?? Yes, we want your help! === Process === The Ubuntu Sugar Remix Work flow is to: * Import the Sugar packages from Debian and modify them as needed. * Test USR on the hardware software platforms currently in use. * Report problems and bugs to the bugtracker. * Triage issues to insure that we have necessary information. * Fix bugs and push them back upstream as necessary === Test === The primary method for testing and reporting issues with Ubuntu Sugar Remix is by working through the Smoke Test on your hardware. The [[Sugar/Test|Smoke Test]] provides a uniform method for determining what works and what does not work in the current release of USR. === Report === The bug [[Sugar/Report|report]] page contains information on how you can report bugs in a way that will help the team to process them more efficiently. === Triage === If you want to join the Sugar Team or just want to help out, triaging bugs is a fairly easy task that always needs to be done. Information on bug triaging can be found on [[Sugar/Bugs/Procedures|triage procedures]]. === Fix === The next step is fixing the properly triaged issue reports. Information can be found at [[Sugar/Develop|development]]. === Package === Finally, for advanced developers, help packaging is all ways appreciated. Information can be found at [[Sugar/Package|Package]]. == TODO list == * Blog on planet.u.c to announce team and project * See what dependencies we have for activities - like abiword, evince - so we can see what activities we are able to package. |
NEXT Ubuntu Sugar Team MEETING: |
Projects
Ubuntu Sugar Remix is a tightly focused project. Our goal is to combine the work of two upstream projects into a single user friendly product that will be used and supported in schools around the world. Please see the road map for more details.
Join
The mailing list is: ubuntu-sugarteam@lists.ubuntu.com
You can try the latest (not stable build) here = ??
Yes, we want your help!
Process
The Ubuntu Sugar Remix Work flow is to:
- Import the Sugar packages from Debian and modify them as needed.
- Test USR on the hardware software platforms currently in use.
- Report problems and bugs to the bugtracker.
- Triage issues to insure that we have necessary information.
- Fix bugs and push them back upstream as necessary
Test
The primary method for testing and reporting issues with Ubuntu Sugar Remix is by working through the Smoke Test on your hardware. The Smoke Test provides a uniform method for determining what works and what does not work in the current release of USR.
Report
The bug report page contains information on how you can report bugs in a way that will help the team to process them more efficiently.
Triage
If you want to join the Sugar Team or just want to help out, triaging bugs is a fairly easy task that always needs to be done. Information on bug triaging can be found on triage procedures.
Fix
The next step is fixing the properly triaged issue reports. Information can be found at development.
Package
Finally, for advanced developers, help packaging is all ways appreciated. Information can be found at Package.
TODO list
- Blog on planet.u.c to announce team and project
- See what dependencies we have for activities - like abiword, evince - so we can see what activities we are able to package.
Sugar/GettingInvolved (last edited 2010-08-03 16:29:44 by 190)