Talk:ILXO Boston Pilot

How this will work

Things to do this week

• Make a build and customization key for CFS.
• Make a school server for CFS.
• Document all of the above.
• Do the parent/student intro.
• Teacher training.

Roles

• Katie: Teachers/CFS-to-us interface.
  • Make sure teacher training happens
  • Get the parent/student intro to be awesome
  • Teacher interface for build & customization keys (Arjun is tech minion)

• Arjun: Build and customization keys (tech minion for Katie), documentation (mostly XS, but of everything in general), FUDcon presentation

• Jason: XS (Scott as Jason's technical minion)

Things that would be nice

• Train the student tech team.
• Sugar Labs - XS, testing

January 3, 2009-January 9, 2009

• January 3-talked delegated roles
• January 4-met with Harvard OLPC chapter, prepared the first set of activities for teacher meeting on the 5th
• January 5-tested and finalized activities and had teacher meeting, got a response from all teachers as to what specific activities they would like
• January 6-test day and work day, tested additional activities and made up the FINAL LIST for teacher training. had a general customization key and then favorite different activities for the circle view
• January 7-second teacher training workshop
• January 8-after school activity for children (student tech team)
• January 9-FudCON presentation

January 3, 2009

+Explained basics of how an XO works (technical aspect)

+Software stack-layering model-each layer interacts with the other (layered from physical (bottom) to activities (top)

XO/Application Interface (API):

+Activities

+Journal

+Sugar Non-Sugar

+OS (Fedora-ish)

+Open Firmware

Shell, Kernel, Network

+Hardware Define

Build: Activities-->OS (Fedora-ish)

Customization Key--> Activities (bundles)

Development Key--> password that gives you permission to use currently being developed builds (builds that are non-signed and non-released)

Sugar::windows; education::business

WINDOWS

business based

i.e. my documents/files

SUGAR

education based

i.e. communities, activities

1.sharing=collabration (mesh network, my neighborhood)

2.reflecting/documenting=journal

3. discovery=activities

everything is automatically saved-->history is logged by the applications;shows learning/process of thinking

The Development Cycle::Textbook writing Process

Build 1--> Build 2--> Build 3-->Build 4

release a build every six months

first start adding whatever you want

then start editing

get a release candidate

fact check

spell check

release. (but at the same time everything is still being updated) you can update like firefox(?)

School Server and Mesh Network

SERVER

one hub with people connecting from one distance

MESH

one hub with one person connected...one person connected from them...peer to peer connecting much better when in a faraway place (i.e. village in the middle of the dessert); one access point

SCHOOL SERVER

1. gives infrastructure access point; mesh

2. squid=local cache; able to see what is used a lot, save on the server and save it locally

3. local moodle=community level content; common web server

+mailserver

+establishing a city library

January 4, 2009

+Prepared for meeting with Mac/Katelyn at 5PM 30 minutes

+success criteria: know what we're doing with CFS through Harvard when

"working relationship"

+Tried to use Emulator on Windows

at first try, cannot connect to network even after entering wireless name into server shut down

open again-worked on jason's and katie's computer

check for software updates

it works!

+Learned Terminal

command lines

cd: change directory

ls: list contents

cp: copy

cd ..: go up in directory

cp -r: copy recursive (copies everything in the folder)

rm: remove

wget: download

mu: move

Journal (technical)

Backlight

Compiled a list of possible activities for the customization stick

available at https://spreadsheets.google.com/ccc?key=pFAYZYtRIh1CR_8ry7Tg8QQ&hl=en and

will get a prototype customization stick done by tomorrow

teacher meeting: 3:30PM the next day; awaiting confirmation

student server-Tuesday

teacher meeting-Wednesday (moved from Thursday)

after school: Thursday

Other points on agenda

How to download new programs

What build is and why it matters

Brief introduction in how networking works

Sharing activities with each other

Connecting to an access point

January 7, 2009

Agenda for second teacher' meeting 1. How to connect to wireless/do collaborative activities (first thing on agenda for Wednesday), demo with Chat) a. have to be on the same mesh network in order to see each other and share stuff; technically, should be able to be on the same wireless and mesh network and be able to share-best case scenario b. when sharing multiple activities, all activities will be shown on the neighborhood view, but only the one might not be able to share more than one activity c. you can only pick one: either mesh or wireless..one always takes the other off 2. Explain differences among Read E-text (zipped+plain text), Read (PDF) and View Files (zipped+Jpgs) a. Shared an example of each document on the XOs…see if people can view b. explain to teachers that they have to download the actual file and then share it on neighborhood 3. Demo one on one with each teacher’s lessonone on one, show all activities on the Favorites view a. Arjun- Biology b. Katie-History c. Jason-Spanish

info

software stack

• layers of abstraction
• clear interface between layers (API)

build and customization

What flavor of Sugardo you want What apps should be available