User:DancesWithCars/DevelopmentIdeas

Earlier:

Put output of the Record activity (video, photos, audio) to an external USB Stick and/or SD Card.

Allow recording as long as the memory holds out.

Easily save as a file & convert the output to .ogg, etc for posting elsewhere, on email, websites, etc... (The cut and paste metaphor in Sugar escapes me as an old person, with decades of other computer experience, and might some teachers, etc)

--danceswithcars 15:08, 20 September 2009 (UTC)

From Book Sprint Experience:

[SpeakSign]: Modify Speak and/or create another app/ activity to finger spell sign language what is typed in as output for deaf, teaching sign to others, and disability accessiblity... See elsewhere for more info...

Make "The Little Green Penguin That Could" (above) into an animated character that can go all through the [1] sections, and start up an image LiveCD/ SD card of SugarLabs Live CD and start and execute each of the examples of software showing the person in a demo like environment what implementation things we are talking about...

Use for training too...

Demo mode might help for trade shows (FOSE, NECC, USENIX, etc) conferences and training manuals too... Parents' Machine:

Since the parent is probably involved in the kids education and stated goals is that the kids remotely will be bringing computer tech home to villages,

In the US, many parents/ adults have higher end machines to start with, and maybe experience with other systems. Sugar, while appropriate for kids, may be counter intuitive for adults with other computer experience, but should be an option, as Parental Roles need to understand and do kid stuff too.

So the assumption here in the US, may not hold elsewhere, that parents already have machines, probably bigger and more expensive, etc.

GrandParents Machines:

But consider GrandParents, who may be technically challenged, or anti-tech, but want to connect with the kids that are using the XO and maybe other machines. GrandParents probably want artwork from the kids, email, photos, etc.

This is amplified by AARP (American Association of Retired Persons), a Non Profit of retirees, older persons, who currently probably didn't grow up in the computer age, and may or may not be interested in the latest whiz bang tech, but may or may not be in the role of spoiling the kids, teaching them, backup or primary babysitting, etc.

Cross-Culturally, historically and remotely, many grandparents are in the home with the parents and children, though in the USA, maybe not as much.

Teacher Machine:

Talk before (several OLPCLearning Club meetings, over many months) and during the ClassActs, of having an XO act as a School Server. Maybe an XO 1.5 machine can be capable of being an Adult teachers machine. Someone on chat / phone said the XO 1 could run server software, though all the functions of server are probably not implemented... Check out what would fit, and what wouldn't. Maybe a chart?

Assumptions about the teacher, uses more and different software than the children, administrative, grading, etc, needs to store student info (with some probably inherent privacy and security requirements enforced by the school system), and probably has experience with other hardware/ software/ operating systems/ desktop environments, needs to be a go between with Parent Teacher Association (PTA), other community members, maybe involved in computer users groups, if has the energy after dealing with kids all day long, low pay, etc...

Teacher machine may not be the wireless access point, but central in what goes on in the classroom, and sometimes after school activities.

Uncle's Machine:

As an occasional adult, has some of the parent machine needs, teacher machine needs, maybe technical too, but like grand parents and teachers, gets to give the kids back to more guardian / parent responsibilities...

Development Machine:

Needs multiple versions of the software, development tools (compilers, languages, toolchains, developer and technical documentation, etc), connectivity for reporting/ learning and releasing software. Repositories of systems software, multiple versions for development, testing, and production.

Compiling/ interpreting may be higher memory requirements. CPU needs higher than just running the software,

quick turnaround may be necessary for fixing problems, especially when critical...

Sugar Bug Reporting Activity:

If users are to be able to have control of the machine, they need to be in the loop for development, reporting bugs, issues, compliments, complaints, etc.

Queue up reports until connected. Offer an option of giving the bug/ report to someone who is going to be connected. I.e. Handoff to a teacher/ travelling techie, etc to send on to Cambridge/ Internet cloud, to get the word out. Next find a way for the improvements/ fixes to come back, if remotely reported, not that different from the old store and forward UseNet? with dialin, no??? Dialin was sometimes connected, sometimes not, unlike internet hardwired, where it is assumed you'd be connected all the time (assumed server rooms, etc before laptops), then wireless came along, and sometimes in the office, sometimes not, but usually in an area where it might be a possibility, now consider more remote, more like martian landings, going to the moon, etc and going very very remote, only occasionally, after trip connectivity? Store more, need more space, briefcase/ journal capacity issues, then get to a docking station/ school server, type thing.

Filtering for privacy information and young people, consolidating and summarizing the multiple reporting stuff, as someone remote might not be able to get the list mail those on this Support-Gang, bugs list, and other high volume Sugar and OLPC mailing lists are seeing, even before a new release, XO-1.5 hardware release, etc...