Community/TODO

From Sugar Labs

Jump to: navigation, search
  Google Translations-Español-Български-‪中文(中国大陆)‬-‪中文(台灣)‬-Hrvatski-Česky-Dansk-Nederlands-Suomi-Français-Deutsch-Ελληνικά-हिन्दी-Italiano-日本語-한국어-‪Norsk (bokmål)‬-Polski-Português-Română-Русский-Svenska

Contents

Community

Below are links to the todo lists of the teams within the Sugar community.

Sugar Labs TODO

Establish Sugar Labs as a Not For Profit Organiztion.


Bugsquad TODO

Form the TestingTeam at the sugar dev meeting DevelopmentTeam/Meetings. </noinclude>

DevelopmentTeam TODO

The DevelopmentTeam TODO list is currently empty.

DocumentationTeam TODO

User Documentation

We will need to create documentation for our own work, and we should contribute to OLPC documentation.

We need to decide on document formats and tools. At some point we will create new formats, based on our research into new textbook capabilities given Sugar software.

EducationTeam TODO

The EducationTeam TODO list is currently empty.

InfrastructureTeam

Backups

We are considering a couple of possibilities:

  • MIT provides a backup service for a few bucks per machine per month via Tivoli
  • Harvard Computer Society filer

Shell accounts

Setup workload will be distributed between the sysadmins and a few members of the core team.

General

  • CMS to host a few, nice looking, official pages.
  • git for both core and activities. personal repos. (ssh access for devs)
  • Trac for core and activities
  • buildbot, master + a few slaves (ssh access for devs)
  • RT system
    • Is this really needed? We can just use other infrastructure for help requests... Firefoxman 19:27, 18 May 2008 (UTC)
  • Pootle
  • LDAP or OpenID authentication across various Sugarlabs tools

MarketingTeam TODO

Active Tasks

Task Owner Due Date Notes
Create mailing list gregdek asap We need a mailing list to discuss very specific marketing activities. Bernie is working with Ivan on this.

Completed Tasks

Task Owner Completion Date Notes
xxx xxx xxx xxx

</noinclude>

DesignTeam TODO

This article is a stub. You can help Sugar Labs by expanding it.

Human Interface Guidelines

WikiTeam TODO

Introduction

People are needed mostly for writing and editing, but there are many other ways of making a useful contribution. For example, simply pointing out errors (such as typos, grammar and spelling, and technical errors) is an extremely useful way to help.

  • Fix spelling and formatting errors
  • Simplify the structure of long pages
  • Organize untidy pages so that they are easy to read
  • Fix broken links
  • Add new documentation to the wiki
  • Add category tags where appropriate

Before you start contributing to the wiki, you should read the Wiki Guide for information on how to edit pages correctly. See the **Wiki Cleanup** page for tips on cleaning-up wiki pages.

Cleanup

The pages listed on **CategoryCleanup** are in need of a thorough cleanup.

These pages either:

  • Do not follow the standards of documentation,
  • Contain incorrect or out-of-date information, or
  • Are formatted incorrectly.

Feel free to dive in. Tidy up a page and remove the Cleanup **tag**!

If you find a page that needs to be cleaned up, DO NOT add it here. Follow the instructions as laid out on the Tag page.

Organize

Much of our work is getting the wiki organized. We look through Special:Allpages to ensure that content is in the correct place

Coordinate

Coordination between wiki.laptop.org and wiki.sugarlabs.org.

Move content between w.s.o and w.l.o so that it lands in the most appropriate place.

Expand

Want to contribute your knowledge?

As an open source Wiki, we have a wide range of individuals working to help expand our resource, and we want your help.

Check out the list of articles with the Needs Expansion tag for articles that are formatted correctly, but simply need to be expanded to cover the full topic.


Personal tools
Sugar
Community
Sugar Labs
Using the Wiki