Jump to content

Sugar Labs/TODO: Difference between revisions

From Sugar Labs
Dfarning (talk | contribs)
m include like to Wikiteam/todo
Dfarning (talk | contribs)
m add item to todo list
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==

Revision as of 16:48, 28 May 2008

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

**BugSquad--in progress

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

**BugSquad--in progress

    • 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 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 TODO Template loop detected: Sugar Labs/TODO FIXME: Inclusion of Sugar Labs/TODO is broken.

BugSquad

Bugsquad TODO


Active Tasks

  • Triaging

Requested Tasks

Help Test

UITeam

UITeam TODO UITeam/TODO

WikiTeam

WikiTeam TODO WikiTeam/TODO FIXME: Inclusion of Sugar Labs/TODO is broken.

BugSquad

Bugsquad TODO


Active Tasks

  • Triaging

Requested Tasks

Help Test

UITeam

UITeam TODO UITeam/TODO

WikiTeam

WikiTeam TODO WikiTeam/TODO