Blog Educativo Plan del Proyecto
Lugar para el plan del proyecto con horario y enlaces
Page for the project plan including schedule and key links
Contents
Requisitos - Requirements
http://wiki.laptop.org/go/Blog_Educativo
El Desafio - The Goal
Mas blogs de los estudiantes de Uruguay!
More blog posts from the students in Uruguay!
Requirements ("must" means its critical to success, "should" means it very valuable but can be deferred):
Not in priority order. 1 - Must make it easy for kids and teachers to post to Blogs on the internet. Should allow posting to multiple blog sites.
2 - Must make it easy for kids and teachers to post to blogs visible only in the school. Must work with Moodle and Mediawiki. Should allow easy inclusion of other blog sites (e.g drupal, wordpress, others?). Must work with School Server.
3 - Must have an option for teacher to review post before its sent to 1 or 2 above. Should also have option to post directly without teacher approval.
4 - Must allow preview and editing of posts by author before being posted.
5 - Must have GUI for teacher or admin management of the options.
6 - Should allow editing and review by multiple students and teachers before posting.
7 - Should allow removing the blog after its posted and adding comments to blogs.
8 - Must allow posting to multiple blogs in school or on internet at same site (e.g. a blogger.com site for each class).
9 - Must be installable and included in future build of School Server.
10 - Should be easily installable on XO or even better not require any new software on XO
11 - Should allow synchronizing of blog posts to more than one server within school network. e.g. move all posts from school in Soriano to the school in Colonia.
12 - Must not require user name or password entry to post blogs. Should allow addition of user name and password or better automatic tracking of user identity when identity management is available on school server/XO.
13 - Must allow posting of text, images from XO and video from XO. Should allow formatting of blog post text.
Functional Design and Work Flow
(note: this is usually written by the engineer but I folded in a lot of work flow and give my latest ideas. I mention apache but I'm open to any software that follows this basic workflow and let's kids post quickly)
- Student
1 - Kid opens browser and goes to web page hosted on School server (XS)(Apache or maybe wordpress?). Better to push a bookmark to the browser and they can just click on it instead of typing in long URL.
2 - Edit Web page has a form where can kid can enter text. Also has an option (button? can someone tell me how you upload a picture or video from XO camera to web site?) to upload image or video. No user name tracking here so kids need to sign their posts in text if they want to have their name on them.
3 - Edit Web page has button to preview. When clicked it shows the post in HTML form. Preview page has a button to edit again.
4 - Edit and Preview pages have one or more of the following buttons depending on management setup (see below): send to teacher, post to school blog, post to internet blog.
5 - Send to teacher button returns sent message on HTML page and button to create another post. Once clicked the post goes to the teacher queue (see teacher section below).
6 - Send to school blog or internet posts the blog, returns sent message and redirects the kids browser to the blog.
7 - Edit web page has a list of previous posts at the bottom which are saved locally on kids XO. Kid can click on any and go to the preview page for that post (can they edit and then repost to the same place?).
- Teacher
1 - Teacher opens browser and goes to teacher page on XS (Apache?). Can be password protected or just a different URL (comments?)
2 - Teacher see a list of posts from students and can click on any to look at them. Previously posted items are also saved on a link from this page (needed?)
3 - Next to each post are options to: send to school blog, send to internet blog, edit or reject.
4 - Reject deletes it. (could send it back to students XO and goes on students edit page but XS/Apache will now know which XO it came from!) May have to start with reject and delete only and then the teacher has to find the kid to tell them to try again.
5 - Send to school or send to internet posts the blog to the relevant place at the top of the blog. There can be more than one of each of these buttons, see management interface below for how its determined which will appear.
6 - Edit button opens in edit page view. Save button return on edit page returns to teacher home.
- Management
1 - Management interface is a web page on XS/apache. Includes a form to enter the blog (URL, user name and password, school name (the text used when linking to URL), anything else needed to post). Each blog is flagged as school internal (moodle, mediawiki, drupal?) or Internet (blogger.com etc.). This flag is used to categorize the site when seen by the kids.
2 - Once the list of blogs is added, each has a "enable/disable" radio button. If enabled it shows up on the list of sites used in teacher (and student?) pages above.
3 - There is room for up to 20 blogs (number of blogs should be number of classes in a school x2?).
4 - Management page has an option to allow post without teacher review. One for internal and one for external sites.
Diseno del Software - Software Specification
Horario - Schedule
May 15 - Finalize suggestions for Ceibal Jam coding days (see below) May 16, 17 Ceibal Jam happens in Montevideo (http://wiki.laptop.org/go/Ceibal_Jam)
May 30 - Development server available on the internet.
May 30 - Work plan defined, infrastructure for where code gets checked in and how its shared defined
May 30 - Key volunteers identified, deadline for initial feedback from users on requirements and functional specification June 2 - Tarun finishes exams and starts work ~ full time June 15 - Functional specification final and coding work clearly defined.
June 30 - First look at some design elements and first rough code checked in
July 15 - First look at code shared with end users. Deadline for comments and changes.
July 30 - Beta test starts. New blog posts generated out of Uruguay.
August 15 - Finalize presentation for OLPC (worst case the interface, best case show new blog posts by kids)
August 30 - Code included in School server build (and XO build if necessary) and start deployment of version 1.0.
September 1 - Day off before building maintenance plan and thinking about version 2.0.
