Posts tagged with collaboration

twitter and identi.ca in education

So I was pondering these 2 little pieces of relatively similar technologies, wondering if there migh be much use for them in collaborative classrooms of tomorrow. It came to me that since tweeting or denting doesn't just need to be focused on the use of text, there could be countless possibilities. All of them involving human interaction, some even being easy open solutions that would otherwise be expensive and even computationally difficult.


Take the class that is studying Spanish, for example, and they want to know how certain words or sentences sound in different Spanish accents. Well, a twitter group that was linked either countrywide or even globally could then tweet the sentence in his/her accent (expaining where they are from somehow, geo location, tagging or whatever), and then a couple seconds - minutes later a reply via twitaccent.com with a reply from someone somewhere else. Such a simple application, with the advent of wonderful collaborative backbones like mesh networking and scalable solutions like ejabberd would allow for little activities to be made. I could imagine an activtiy like this one being quite the hit on Sugar.


Since I gave an example on how to do audio based twitter examples, how about a picture based one. A Biology class goes out with their laptops or mobile phones or cameras. They are told to take pictures of any edible plants they might find in their surroundings, not forgetting to tag their pictures with the area, altitude, near water or not, and other such items. At the end of the class they compile their data and the kids enter their edu-twitter accounts, or twitter-wiki accounts and this data is then uploaded to groups, where people can use that data or compare to that data in the future. Others can even grade the quality of tha data, or if its a professional botanist, tell them their right or wrong and why.


The strength of both twitter and much more so identi.ca is that they allow following and followers, so groupings of people interested in similar material. It would just take the participation of schools together to implement such little experiments to get great results. Identi.ca's grouping abilities as well as its open source platform base obviously make this the ideal choice. And anyone can go out right now, set up a laconica server and implement an idea like the 2 I've just mentioned in a couple of days, make it a web based app, but it would be much nicer to imagine such particular apps on the XOs and on Sugar in particular.

The last kind of activity I thought about was really a video based one, but then it starts to become far to similar to youtube videos and its ilk. Still, the idea that one could localise video streams that are very small (ie, perfect for sending to blogs, mobile phones etc.) and group them according to followers and following might work for ideas like multi-day events, parties, etc.


So to end with, how about a pic based identi.ca/twitter app that shows sugar deployments/OLPC in action around the world? Wouldn't that be quite simple to get updated. Someone at a particular deployment, even a student, takes pictures of the equipment, the staff, the students, teachers, etc, and groups them by tagging. Just tweets the pic with the tags and it goes into is appropriate groupings, which then everyone can look at. We could get an idea of what is going on in deployments around the world very easily this way in a matter of days (with a little coordination of course...)


Rate It! (Average 0, 0 votes)



Graz - sugar and XO deployment feedback


On Monday 19th January, the olpc.at group  was scheduled to meet 6 educators in various fields for a combined workshop, and mutual feedback session.  The meeting was off to a rocky start with neither collaboration via the local AP working, nor many of the apps on the Ubuntu sugar stick running well. On previous days I had tested many of the apps and found them to be non-functional or wrongly sized for the resolution, or lacking network neighbourhood views.

This turned out to be  an advantage in a way, as it brought up a discussion on what the educators present would like to see happen in terms of customised activities and collaborative possibilities. I'll try and list them in some organised fashion, based on activity.

  •  Flipsticks activtiy

The first activity that was questioned was flipsticks, which was seen as a great tool for younger kids, but lacking collaborative abilities. An idea which was brought up was splitting the flipsticks work into user groups, and have the groups then combine their animations to create a bigger final animation. The reasoning behind this was that often there is not much time in a class, and to have every student to their little bit, and then combine it all is much more efficient, and a lesson in collaboration at the same time.


  •  Geoquiz and other visual quiz activities

Another suggestion that came after showing Geoquiz was the development of some sort of authoring tool for this kind of activity, which generally involves showing images and asking questions. This could then be applied for many localised activities. In the case of Austria, for example, children of a younger age learn about Austria itself, in a geographical sense, but not too much about the rest of the planet until they are older. The Geoquiz activity as it stands was criticised for not telling a user when an answer is correct or wrong, for not having good controls, and for having unchangable content. The other option that would be a requirement for these kind of activities is a score card or report that the teacher could somehow store and print, based on children collaborating on quiz type activities. It is good to know that there are currently Sugar developers that are working on implementing some of these features, and really make a generic quiz generator that could be used for any subject.


  •  Other Quiz type examples that were brought up

Examples of quiz type activities that were brought up were types of flowers, the environment, nature, animals, the house, etc.


  •  Main subject matter requested as simple activities with lesson plans

The main subjects that were requested were German (first language) and Mathematics, which seems to coincide with the requirements of other deployments like the Nepali deployment. In terms of mathematics, these activites should be as simple as possible, for example, the multiplication/division/adding/subtraction tables done in such a way that the teacher could choose which numbers were to be selected and practiced on any given day and by any given student. It should also, then, be possible to pair up students collaboratively to answer these, and once again, at the end of the session, collect the answers in a score card or report, that could be saved or printed by the teacher.


 


  • Typing tutor or spelling activities

In a similar vein, some kind of activity for practicing spelling should be implemented and monitored in the same way as a maths apps... A general request for all activities was the ability to have an admin view/session that the teacher could use to follow scores, assignment of individual objects of a particular activity and their layout, and the users themselves. This would be something like a monitoring tool.


  •  Simple UI and Simple app rules

It was emphasised that the simplicity of applications is extremely important for younger children, and that many ported apps are just too cluttered to be useful in any way. They were very happy with the simplicty and usability of sugar itself, but were disappointed with many of the apps, which either ignored design conventions or were simply ports of already complex and badly layed out activities.


  •  Collaborative typing tool with speed recognition

Another example of an application they wanted to see was a simple typing activity which would involve the teacher typing an example text, and then the kids trying to type the same phrase as quickly as possible with the times to completion and error/rate being calculated for each child, and then reported to a score card or report followed by saving of this or printing out.


  • Gcompris is a hit, but needs the admin tool

While we focused on presenting gcompris as a great tool for younger children with hundreds of mini apps, it was asked if one could seperate these mini apps into layouts for particular groups of students, or individual students, and again have a central admin part to keep track of what children are working on and even suggest a progression plan (activities to be worked through and scores for those activities to be achieved.) G compris already has an admin part and this should be included within sugar, as it seems to be a vital component to get it to be anything more than a fun experimental game. 



  • The simplest app wins (speak)

The app they found most to their liking due to its simplicity and the fun surrounding it was the speak application. The criticism was that speak should really be having the letters sound like they do in words. For example, 'M' should be pronounced mmmm and not emmm. This would require the fixing of only the sound bytes of single characters.


  • Meshed collaboration extremely shaky, especially with more than 6 users.

There was some skepticism as to how well collaboration would work as we seemed unable to get it to work well due to multiple wireless signals. A server was suggested by us to overcome this and other issues (storing of lesson plans for the activities in moodle, backups to prevent local storage problems, ejabberd for collaboration between xos and non-xos.)


  •  Sugar on a stick, sugar on Ubuntu not Ready

Finally, it was concluded by us after presenting sugar on a stick with the very latest binaries and packages, that, at least on ubuntu, sugar is not ready for even experimental use, as more than 50% of the apps do not work, and networking seems to be broken too.


Present at the deployment were me and Christoph Derndorfer, as well as the education specialists themselves.



Rate It! (Average 0, 0 votes)



LTSP and collaborated netbooks (not just xos)

We recently held a olpc / LTSP presentation in Vienna, which had the enormous turnout of 11 people. Though the turnout was pretty bad, it did give us the opportunity to be experimental and check the wonderful world of using sugar on various platforms via LTSP.

We hooked up 2 acers, a thin can (artec), a laptop acting as LTSP and ejabberd server, along with 2 traditional xos. Before going into the details of the experiment some explanation is due. LTSP stands for Linux Terminal Server Project, and refers to the use of a mainframe like infrastructure, where minimal systems without hardrives and little cpu and ram can be used as diskless terminals. The idea is that everything runs from the server, with the client netbooting the environment and using the little ram and cpu it has to load the kernel and connect its display session to the server.

Usually older computers (pentium 200hz+ with 64 MB ram) are re-used in this way, though there are various dedicated thin terminals that are mobile phone sized and are highly energy efficient. LTSP terminals usually have no moving parts, making them hard to break. Whereas the XO, and rightly so, has been marketed as the guerrilla
educational device for the 3rd world, it is a little tied in with a specific company and a specific set of hardware. Sugar on the other hand is not, and in my view the more hardware can run sugar natively and flawlessly, the closer we get to a solution that can really feed the masses. As the politics of OLPC grow and change, such as dropping
sugar support, or moving to windows (these are just speculations), Sugar's growth and deployment should not be affected. If anything gives sugar and Sugar Labs a firm grounding its its ability to run on multiple systems and scenarios. I am aware that Sugar Labs is in communication with various vendors and distributors, and it is only a matter of time before some interesting deals are struck.

In our presentation case, for a mobile server, we used a dual core 1.8ghz with 2 gigs of RAM. Setting up the server on the laptop was pretty straight forward, and involved installing LTSP on top of a base Ubuntu system, and then
adding ejabberd as well as Sugar sessions for all newly created users. One can choose other sessions of course, but our interest was to test collaboration on all the machines, in which case Sugar was our environment of choice, and the login session for all our users. Installing ejabberd on the ltsp server was the only requirement for sharing across all machines. I followed the instructions as layed out on the laptop.org wikipedia and nubae.com site. There are still some issues installing ejabberd, such as permissions of the /etc directory, but it has generally become much simpler to install for anyone. Without ejabberd the machines did see each other via xmpp-local, including seeing shared activities, but they tended to fall of the network neighborhood. With ejabberd the machines were visible continuously and were very responsive to connections.

For testing purposes we tried sharing chat across all the machines, which worked flawlessly. The applications in general seemed to load much faster than with the xo hardware, both on the thin can and the acer ones. It was nice to see that a dual core laptop with 2 gigs of ram was more than happy to serve 6 thin terminals at once. This makes
the perfect mobile school, with all the machinery fitting into one backpack!

The laptop server was set up to get wireless internet, and then hand out LTSP through the wired interface, using a gigabit switch as a connector. One of the things that still requires a lot of work, and perhaps this
is due to using Ubuntu, is getting all the activities to work. I tested various activities like puzzle slider and jigsaw puzzle, which just left the activity icon cursor flashing on the screen and eventually fell back to the main screen. Another problem was that turning off or restarting the session was nonreactive. Also many, of the items in the control panel either crashed sugar out completely (date/time) or didn't work. These problems have recently been turned into bug reports, so we hope by the next release of Ubuntu, the environment works as it should.

LTSP and sugar are a great combination and much wished for in schools in the developing and developed world. We will talk a little more about the advantages of LTSP, Sugar and scaling, as well as wireless LTSP and Fat clients in another article.

Rate It! (Average 0, 0 votes)



Telepathy, Empathy and collaboration

The idea of collaboration as implemented by Sugar Labs in the XOs is something truly fascinating. The direction is definitely to incorporate desktop wide collaboration in all future operating systems. I read a recent article in Wired that actually spoke about the future direction of Microsoft windows being this type of unified integration in their OS. They have started on this, but it probably won't show for a good number of years. On linux we have it a lot of it now! and its improving all the time. The service responsible for this is called Telepathy, and is at the heart of not only Sugar, but Gnome and Kde now too. Because of this standardization of a xmpp communication protocol across the entire desktop, instead of having to build a new comms protocol every time for every application, it is making it very easy for application developers to add collaborative functionality to their apps.

This is done through tubes. Tubes are a way for the server to offer a socket to a messenger contact, the remote contact accepts the socket and they can begin to write/read data on it. the big advantage is that with tubes, even if the connections are NATed on both sides, the apps can still share data.

What follows is an experiment in setting up a collaborative environment under Gnome. A lot of the collaborative stuff is really quite alpha/beta still, so this is just an exercise in setting it up for research purposes.

First up we have the telepathy layer and common apps that run with it. We will be installing Empathy for chat, video, audio and sending files. This fairly newcomer is quickly becoming the de facto standard chat client due to its wide support for other protocols and deep integration of telepathy into itself and the desktop, as well as tube support. It will most likely replace pidgin as the standard chat client in Ubuntu starting with Jaunty. Here's a screenshot with a variety of plugins installed and a custom theme:

I have been running it for a good week now, and it seems very stable, albeit requires installation from the Telepathy PPA to give it the latest features.

Add the the telepathy intrepid ibex PPA and install empathy:

sudo echo "deb http://ppa.launchpad.net/telepathy/ubuntu intrepid main" | tee -a /etc/apt/sources.list /dev/null
sudo echo "deb-src http://ppa.launchpad.net/telepathy/ubuntu intrepid main" | tee -a /etc/apt/sources.list /dev/null
sudo apt-get update
sudo apt-get install empathy telepathy-idle

If you had pidgin before, empathy will automatically import all your accounts into it upon first start up. You can then remove it afterward as there is no point in having 2 apps that do the same thing. If you plan to use facebook messaging, you'll have to patch haze.manager and add a facebook-im profile. Also note I did this already having the facebook plugin installed for pidgin, so ymmv:

wget https://bugs.freedesktop.org/attachment.cgi?id=20810
mv attachment.cgi?id=20810 ~/.local/share/telepathy/managers/haze.manager
wget https://bugs.freedesktop.org/attachment.cgi?id=20811
mv attachment.cgi?id=20811 ~/.local/share/mission-control/profiles/facebookim-haze.profile

One thing that is currently sort of missing from empathy is file transfer, which is only possible over Salut. The good thing is, that making a Salut connection is incredibly simple, and requires no server as it works directly over avahi. This is the same protocol used by Ichat.

The really interesting stuff, though, happens when you set up an ejabberd server which allows for collaboration to happen across a variety of applications in a variety of ways. To set up ejabberd, take a look at a previous article I wrote, and follow the ejabberd parts:

http://www.nubae.com/sugar-on-ltsp-ubuntu-intrepid-ibex

Once ejabberd is setup, you can add accounts to be used on your local network via the web interface by browsing to: localhost:5280 and clicking on users to add them. You can then use those details to connect to a jabber server via empathy. Other plugins for empathy are being worked on and include things like sharing webpages to contacts and sharing contact details from calendars. The future looks bright, but there are already some applications that work well with telepathy and collaboration in various forms.

Inkscape is a vector based imaging application that allows for collaboration via its messageboard facility. It's easy to install:

sudo apt-get install inkscape

It is currently a way to send files to and from other jabber apps, as well as chatting, but it will certainly grow to incorporate other collaborative functions. Here's a screenshot of it in action:

The other big app to do collaboration is Abiword, and it allows multiple users to edit a document in real time, each writing their little bit and collaboratively changing areas. The collaboration for Abi Word is done either through the standard ejabberd manner, or via a direct tcp connection. This works not only across computers and networks, but across operating systems too! You can collaborate with windows users just as easily as with Linux users and apple users. Install it:

sudo apt-get install abiword

Here is a screenshot:

A well known app amongst developers, Gobby allows for users to create sessions and then join them, and work on documents together. It is highly useful for hackfests and gatherings, and is used by the Ubuntu devs when they are at such gatherings. It can show a list of documents, users, and then the ability to work on those. Right now, Gobby is avahi based, with plans to support xmpp/empathy in the future.

sudo apt-get install gobby

To get an idea of where this is all going, I looked at a couple of other apps, which are not quite finished yet, but certainly give food for thought. One was Jokosher, which intends to allow collaboration through audio, allowing instruments across the network, voice over ip interviews, and all of this streaming in real time.

The Rythmbox music program has many advanced features, one of which is showing the status in your im according to the music playing. It also allows for sharing of music across the network, with password protection if needed.

Finally there are various games like tictactube and gtetrinet which create tubes to share sessions between each other, and I imagine this trend will multiply across gnome games, allowing for collaborative gaming experiences.

Rate It! (Average 0, 0 votes)