Sugar Labs/TODO: Difference between revisions
m add item to todo list |
m fixed typos |
||
| Line 5: | Line 5: | ||
==Community== | ==Community== | ||
*This seem to be the core functional team we should start forming. | *This seem to be the core functional team we should start forming. | ||
**Accessibility team | **Accessibility team | ||
** | **Bug Squad | ||
**Build team | **Build team | ||
**Documentation team | **Documentation team | ||
**Marketing team | **Marketing team | ||
| Line 19: | Line 19: | ||
**Wiki Team | **Wiki Team | ||
*Should the Sugar community get involved with deployments? Or should deployments be left to the various | *Should the Sugar community get involved with deployments? Or should deployments be left to the various distributions. | ||
**Deployment team | **Deployment team | ||
*I do not yet under stand the organization of the sugar stack very well. But, I like the way gnome splits their software in modules. This would split Glucose in several manageable size chunks. Then each core activity would become a separate module. | *I do not yet under stand the organization of the sugar stack very well. But, I like the way gnome splits their software in modules. This would split Glucose in several manageable size chunks. Then each core activity would become a separate module. | ||
**Glucose team | **Glucose team | ||
**Content team | **Content team | ||
Revision as of 17:04, 28 May 2008
This article is a stub. You can help Sugar Labs by expanding it.
Here is a list of pages which are incomplete or even contain just a discussion. We need to improve them as soon as possible to get more people involved by increasing the transparency of our infrastructure, code and processes.
Community
- This seem to be the core functional team we should start forming.
- Accessibility team
**Bug Squad
- Build team
- Documentation team
- Marketing team
- Release team
- System Administration team
- Translation team
- UI team
- Web Develpment team
- Wiki Team
- Should the Sugar community get involved with deployments? Or should deployments be left to the various distributions.
- Deployment team
- I do not yet under stand the organization of the sugar stack very well. But, I like the way gnome splits their software in modules. This would split Glucose in several manageable size chunks. Then each core activity would become a separate module.
- Glucose team
- Content team
Sugar Labs
Sugar Labs TODO Template:Community/Header
This article is a stub. You can help Sugar Labs by expanding it.
Here is a list of pages which are incomplete or even contain just a discussion. We need to improve them as soon as possible to get more people involved by increasing the transparency of our infrastructure, code and processes.
Community
- This seem to be the core functional team we should start forming.
- Accessibility team
**Bug Squad
- Build team
- Documentation team
- Marketing team
- Release team
- System Administration team
- Translation team
- UI team
- Web Develpment team
- Wiki Team
- Should the Sugar community get involved with deployments? Or should deployments be left to the various distributions.
- Deployment team
- I do not yet under stand the organization of the sugar stack very well. But, I like the way gnome splits their software in modules. This would split Glucose in several manageable size chunks. Then each core activity would become a separate module.
- Glucose team
- Content team
Sugar Labs
Sugar Labs TODO Template loop detected: Sugar Labs/TODO FIXME: Inclusion of Sugar Labs/TODO is broken.
BugSquad
Active Tasks
- Triaging
Requested Tasks
Help Test
UITeam
WikiTeam
WikiTeam TODO WikiTeam/TODO FIXME: Inclusion of Sugar Labs/TODO is broken.
BugSquad
Active Tasks
- Triaging