Line 5: |
Line 5: |
| | | |
| ==Community== | | ==Community== |
| + | *This seem to be the core functional team we should start forming. |
| + | **Accessibility team |
| + | **BugSquad--in progress |
| + | **Build team |
| | | |
− | * [[Community/FAQ]] | + | **Documentation team |
− | * [[Documentation]] | + | **Marketing team |
− | * [[Community/GettingInvolved]] | + | **Release team |
− | * [[BugSquad]] | + | **System Administration team |
− | * [[Supported systems]] (rename to [[Distribution]]?) | + | **Translation team |
− | * [[CodeReview]] | + | **UI team |
− | * [[Infrastructure]] | + | **Web Develpment team |
− | * [[Roadmap]] and [[Release]] | + | **Wiki Team |
− | * [[Meetings]] | + | |
− | * Wiki-barnraising, harmonization of familiar and useful templates, plug-ins, extensions (e.g. traclink,etc.) from OLPC wiki. | + | *Should the Sugar community get involved with deployments? Or should deployments be left to the various distrbutions. |
| + | **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== |