Activity Library/Devel

From Sugar Labs
< Activity Library
Revision as of 12:55, 19 October 2010 by Tomeu (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
Pencil.png NOTICE:  This page is a draft in active flux...
Please contribute to these contents and discuss issues on the discussion page.


We are adapting Remora, the software behind, as a Sugar Activities user-facing infrastructure for installation, reviews, and ratings. (Activity development infrastructure will be hosted elsewhere.)

Design (both UI and app)

We are collaborating on the AddonsPortal Design Page Josh is working on a mockup so that we can then do a peer review and then fit it into the Remora code. Remember, as few changes to the code as necessary (focus mainly on CSS and not changing the Views -- where possible)


Kinds of help needed

  • Infrastructure - installation, running, maintaining the instance once it's live/stable/usable.
  • Development - fixing bugs, committing patches, and pushing them upstream.
  • Testing - filing bugs against the latest version.
  • Coordination - keeping track of goings-on, acting as a source of up-to-date information and concrete tasks, and making sure the delta from upstream does not get too large.


  1. Add your name to the list below.
  2. Look at the latest live version at - does it look like something you can use and test? Development is being done on:
    1. If yes, try using it until you run into a bug, then file it at under the component. Keep in mind that this is an unstable alpha and all work is considered test data that can be wiped out at a moment's notice.
    2. If no, look at the trac query for and see if there's a ticket you can take/help with (helping with a ticket can include reproducing it, rewriting and clarifying the bug report, checking if a patch is being pushed upstream, etc). Installing a local copy may help.
  3. If you have questions, find one of the people below on IRC (, #sugar) and ask. If none of us are online, contact Mchua.

People involved

  • User:Mick - infrastructure, development, and testing; coordinator
  • User:Dfarning - infrastructure and development
  • User:Josh - design
  • User:Mchua - testing/QA
  • User:Tomeu - infrastructure and development (not involved any more)
  • User:Wade - Activity Team lead
  • User:LFaraone - testing/QA, bugfixing
  • User:ChristophD - not yet contributing, but would like to help with planing
  • User:wwdillingham - would like to begin helping with infrastructure / testing / development / documentation / bug killing.
  • Sign your name here if you're contributing

Coordination is hosted on the sunjammer server. (It's named 'addons' because we may host more than activity bundles in the future; Language packs, Library Packs...)

Development is coordinated using the standard three stages; production, testing, and development plus upstream svn. Each stage runs as its own user and has its own database. The source code is in individual branches of .


The production instance currently runs as user production. The source code is in the production branch.


The testing instance currently runs as user testing. The source code is in the testing branch.

Testing is to be used as a staging for developers and testers to use and abuse the new code before it goes into production.

We need lots of help testing the site. (It is currently in pre-alpha and not particularly interesting to test, so if you're not a developer you may want to add this page to your watchlist and check back in a week.) Add new tickets for bugs that you find to Trac with the component. Feature and design ideas are also welcomed.


Remora is written in php, so primarily php/mysql hackers are needed. The development instance currently runs as user devel. The source code is in the devel branch.

Devel is your playground. You can either work directly on the devel instance on sunjammer or you can follow the instructions at Activity Library/Devel/Installing to set up your own personal aslo on your computer at home. Using git makes it really easy to recover from mistakes. As long as you have not pushed your commits you can just 'git --hard reset origin' to permanently delete any local changes (see --mixed for not actually deleting).

If you really break things, the steps to restore it to its former glory are:

  1. read these instructions and ask for help on IRC if any of them are not clear
  2. delete the instance
  3. git clone from master
  4. checkout correct branch for the instance
  5. svn pull the vendor stuff
  6. recreate the tmp dir stuff
  7. install the config.php

See for upstream project information, and for instructions on how to install a local copy to play with. Then check this trac listing for development tickets and pick one to fix or to ask questions about.


There is a fourth branch named svn which is used to merge upstream changes for

One of our key goals is to keep also as close as possible to amo, so rebasing isn't so costly. If at all possible, try to refactor your patches so that they can be pushed upstream.

Happy Hacking

Meet us in #sugar on freenode if you'd like to jump in and help. Formal meetings should be planned soon. Meetings will be in #sugar-meeting and announced here. If you watch this page, you will receive email notifications when it changes.

Should an email be sent to the IAEP and/or sugar-devel mailing lists to announce meetings? tomeu 09:10, 1 February 2009 (UTC)

File a ticket on with the component 'infrastructure' if you need an account for development or testing (you do not need a sunjammer account to do user-facing testing on this). Make sure to include your desired account name and PGP key.

Historical discussion

There have been a number of mailing list threads about the AddonsPortal; this page has been updated to reflect the content of the latest messages, but they are listed here for historical purposes.

For information on Amo, the upstream project please see the Remora project page.