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 | ||