#4548 NORM Never A: Request to include: Joke Machine

[Zarro Boogs per Child]

#4548: Request to include: Joke Machine
-------------------------+--------------------------------------------------
 Reporter:  hummingbird  |       Owner:  jg            
     Type:  defect       |      Status:  new           
 Priority:  normal       |   Milestone:  Never Assigned
Component:  distro       |     Version:                
 Keywords:  killjoy?     |    Verified:  0             
-------------------------+--------------------------------------------------
 Joke Machine was developed for WorldWideWorkshop.

 Git source is at: dev.laptop.org/git/mamamedia/joke-machine

 XO bundle is in my dropbox:
 dev.laptop.org/~antoine/public_rpms/joyride/JokeMachine-5.xo

 Motivation:

 A. Epistemological impact—to what degree does this activity positively
 impact learning?
 Joke Machine allows kids to create a set of written jokes – a project that
 helps with reading, writing and cultural learning. Kids can enhance each
 joke by adding an image that they created with other XO activities, such
 as Paint, Record and Flipsticks. They can also include a sound effect (to
 play with the joke’s punchline delivery) made with Record. (Note: other
 image and sound files also accepted by the activity.) “Jokebooks” can be
 shared with other XO users over the mesh. During the sharing process,
 users can submit jokes for one another’s jokebooks, thereby allowing a
 user to collect jokes. The jokebook author can delete or edit any
 submissions they receive.

 B. Fun—is it fun? engaging?
 Yes. Children love to hear and tell jokes; trading jokes with friends is a
 time-honored kid pastime. Joke sharing can be a great opportunity for
 cultural learning, since different towns, countries and cultures have
 their own jokes which reflect a unique world perspective. The ability to
 add drawings and sounds allows users to personalize the experience even
 more.

 C. Quality—is the activity sufficiently robust in its implementation that
 it will not compromise the integrity or supportability of the system? Is
 the overall quality of the implementation adequate to meet our standards?
 Can the community be engaged in the process of testing and "certifying"
 and maintaining the activity?
 Yes. Joke Machine is robust and has been coded specifically to work within
 the system requirements of the XO. The development team has been testing
 and refining it for several weeks and posted it on the OLCP Activities
 grid for additional input from the community; the Developer has also been
 consulting the Sugar and Devel communities for specific issues during
 production. The OLPC team and OLPC community volunteers are highly
 encouraged and welcomed to be involved in further testing and
 certification.

 D. Sugerized—to what extent has the activity been integrated into Sugar,
 including UI, Journal, security, internationalization, etc.?
 Joke Machine has been fully Sugerized to ensure that it runs well within
 the Sugar framework and UI. It provides incentive for creating images with
 other core tools, like Paint and Record and it offers a seamless process
 for incorporating those assets in an original Jokebook. It leverages the
 Journal for keeping and resuming instances. It utilizes the mesh network
 to share creative output, and to submit new content to one another’s
 jokebooks.

 Does the activity require the folding in of additional libraries and
 resources? (This has impact on robustness—positive and negative—support,
 bloat, and overall usability, aesthetics, and perception of quality of the
 machine.)
 Joke Machine does not require additional libraries or resources that are
 not already part of the Sugar framework.

 E. FOSS—is the activity and all of its dependencies free and open?
 Yes, Joke Machine is fully open and free.
 F. Extensible—is the activity something the community can extend? Does it
 span multiple needs? (And does it have—or the potential of having—an
 upstream community of support?)
 Yes.  Joke Machine is designed to be expandable and transformable by
 users, educators and developers. Learners can create original joke books
 filed with images, text and sounds. Educators can create new Lesson plans.
 Developers and aspiring developers can add new features and customize the
 code. It is open and ready for Community use and expansion.

 G. Uniqueness—does the activity add a unique feature to the core?
 Yes. Joke Machine offers a unique opportunity to create an original
 project that incorporates text and multimedia assets made with other XO
 activities (images and sounds). Users can share creative output, submit
 new content to one another’s joke books, and accept/reject submissions
 from others, which is a new twist on the collaborative capacity of the
 mesh. It also features integrated Lesson Plans, another compelling,
 expandable feature.

 H. Expectations—does the activity meet the expectations of (children,
 teachers, parents, G1G1 audience, etc.)?
 Yes. Joke Machine is suitable for children, teachers and families
 worldwide, as well as G1G1 and other OLPC initiatives.

 I. Discoverable—is the core activity discoverable? (This is not to say
 that it shouldn't be hard work to fully exploit the power of an activity,
 but it should have a low barrier to entry.)
 Yes, Joke Machine presents a low barrier to entry via a sample jokebook
 which can inspire discussion and sharing of jokes verbally. It is also
 fairly simple to create a new jokebook with text entries alone.  The
 option to add images and sounds adds a further level of complexity. Tools
 for submitting jokes to others and reviewing jokes that were submitted to
 you offer advanced play options for more sophisticated users. Starter
 Lesson Plans also extend the depth of this activity.

-- 
Ticket URL: <https://dev.laptop.org/ticket/4548>
One Laptop Per Child <https://dev.laptop.org>
OLPC bug tracking system