User:Mchua/Sandbox: Difference between revisions

From OLPC
Jump to navigation Jump to search
mNo edit summary
m (Walter's rectum 21/Sandbox moved to User:Mchua/Sandbox over redirect: revert)
 
(18 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Firmware ==
Steve, can you try this and see if something like it would make it easier for you and others to use the wiki?
Type a title in the box below, then click the button.


q2e30 is the current one under test; it's new and needs a lot of hammering.
<inputbox>
type=create
buttonlabel=Propose a project
bgcolor=#fffcf9
preload=Template:Summer of Content project proposal
break=no
</inputbox>


Bug to verify and file: http://lists.laptop.org/pipermail/testing/2009-January/000763.html


Tests to run: http://wiki.laptop.org/go/Firmware_security#Multiple-Key_Support
= How to Apply =


== Smoke testing ==
In order to facilitate things we're asking that all participants submit an intention to participate. Your intent to participate should be emailed to '''ADDRESS HERE''' by 11:59pm EST on '''DATE'''. There is no application fee.


Staging-25 could use a formal smoke test run (slimming down and speeding up the smoke test as you run it is acceptable, so long as it's documented) done in parallel with an XO running 8.2.0, to check for regressions and variances.
You or your team must be capable of producing something usable and Health-related by the end of the Jam. Alternatively, you can apply to be an independent Jam consultant if you have expertise that could be used to mentor/contribute-to multiple groups (for instance, providing art/graphic/web design services to all teams, or offering to translate the output of content teams into Spanish, etc). Teams are preferred, though.


== Documentation ==
If you are looking for a team, check out the wiki Talk Page '''This should be linked''' and/or post to the '''Mailing list, which needs to be set up.'''. We will be doing a nominal evaluation of applicants skills to ensure that each participant/team is capable enough to produce work. Applicants will be notified of their status by '''DATE.'''


[[Release notes/8.2.1]] needs to be updated with things like...
There is no maximum team size, but note that the average team size for a Jam tends to be between 1-3 people because of the tight schedule constraints. The information to send in is as follows:


* instructions on how to use OFW's new multi-key + nand-blaster support
# Team name
* ALL laptops show the 'pretty boot' animation now... not just secured laptops, this isn't a bug.
# Team leader & email (main point of contact)

# Name of additional team members and email for each
== Wireless ==
# Can you attend for all 3 days of the Jam? (If not, which days can you come?)

# Which area of interest team will compete in (see About)
There have been a number of wifi tests that need to be brought up to date and filed (and rechecked against the current build if not yet carried out.)
# Basic summary of team member skills such as programming skills

# Please let us know the main language/technology/tools you intend to use (wiki, microcontrollers, pootle, pygame, etc) and whether you will be bringing your equipment yourself, or if you need help getting access to any tools
* http://lists.laptop.org/pipermail/testing/2009-January/000753.html
# Please provide a few words about why you are interested in participating.
* http://lists.laptop.org/pipermail/testing/2009-January/000758.html
# Any other special notes or things you'd like us to know
* http://lists.laptop.org/pipermail/testing/2009-January/000759.html

== Activity compatibility ==

* Gary C. Martin uncovered some [http://lists.laptop.org/pipermail/testing/2009-January/000691.html Activity compatibility issues] with staging-7.
** these need to be checked against the latest staging build, with the Activity version listed in [[Activities/G1G1]].
** ...and if the bugs are still present, they need to be filed in Trac...
** ...and the Activity maintainers contacted. Read http://lists.laptop.org/pipermail/testing/2009-January/000695.html for context before contacting Activity developers; also check to see if a later version of the Activity (which may not be listed in [[Activities/G1G1]]) might have the bug fixed.

Some specific bugs to look for:
* [http://lists.laptop.org/pipermail/testing/2009-January/000694.html in Etoys]
* [http://lists.laptop.org/pipermail/testing/2009-January/000701.html in Browse] [http://lists.laptop.org/pipermail/testing/2009-January/000696.html more in Browse] [http://dev.laptop.org/raw-attachment/ticket/9112/ filed in Browse]

== Ticket closure ==

See and verify "test in build" items from [http://dev.laptop.org/report/38 trac]; this is mostly bookkeeping.

Latest revision as of 16:01, 20 December 2009

Firmware

q2e30 is the current one under test; it's new and needs a lot of hammering.

Bug to verify and file: http://lists.laptop.org/pipermail/testing/2009-January/000763.html

Tests to run: http://wiki.laptop.org/go/Firmware_security#Multiple-Key_Support

Smoke testing

Staging-25 could use a formal smoke test run (slimming down and speeding up the smoke test as you run it is acceptable, so long as it's documented) done in parallel with an XO running 8.2.0, to check for regressions and variances.

Documentation

Release notes/8.2.1 needs to be updated with things like...

  • instructions on how to use OFW's new multi-key + nand-blaster support
  • ALL laptops show the 'pretty boot' animation now... not just secured laptops, this isn't a bug.

Wireless

There have been a number of wifi tests that need to be brought up to date and filed (and rechecked against the current build if not yet carried out.)

Activity compatibility

Some specific bugs to look for:

Ticket closure

See and verify "test in build" items from trac; this is mostly bookkeeping.

Retrieved from "http://wiki.laptop.org/mediawiki/index.php?title=User:Mchua/Sandbox&oldid=228770"