Dokeos 1.8.6 Beta... is it out already?

Hehe... Should I announce it or should I keep it quiet a little bit more? :-) The beta is now available for download from the Dokeos repository: http://www.dokeos.com/download/dokeos-1.8.6-beta.zip There has been an enormous amount of work on this version. If you find any bug, please report it in http://projects.dokeos.com, after checking that it hasn't been reported already. We'll start making proper announcements soon :-)

Only 10 days since campus cleanup, and yet...

I just checked the statistics quickly for the campus.dokeos.com portal. We've cleaned up the portal completely on the 12th of October, and yet... we have already reached 1400 courses and 13000 users.

campus.dokeos.com is provided as a free service to host courses inside Dokeos, but without any implied guarantee, so we strongly recommend you keep a backup (you can do that in your course options) at least once a month.

October Statistics

A few statistics from our database in early October 2008, from our version check script that sends a little (anonymous data to www.dokeos.com, as explained on the Dokeos admin page: Total number of portals registered (some of them might be duplicates): 6 375 Total number of courses created on these portals: 122 054 (campus.dokeos.com accounts for 32 000) Total number of users registered on these portals: 1 297 775 (campus.dokeos.com accounts for 210 000) Around 5 000 downloads per

Dokeos in Machu Picchu

As I was in Cusco the other week to hold a few speeches at a 3 days conference, I took the opportunity to go to Machu Picchu. This time, I managed to walk to the Intipunku (la Puerta del Sol, The Sun Gate) and take a picture from there, wearing my wonderful - but old now - Dokeos t-shirt from the 2005 User's Day.

Is respecting GPL too complicated?

I've had a bunch of hunches recently about companies abusing the licensing terms of Dokeos by officially declaring (but only verbally so far) that their product (being Dokeos, but not officially) is not open-source software. The GPL licensing makes it clear that the software derived from GPL software, or any alteration to a GPL software *must* be open-sourced, at least for the people it is distributed to.

Renaming things in a piece of software with users with habits

One of the terrible things that happen for users, from time to time, is that their usual actions are suddendly made completely unusual by a change of version, because the name (nothing else) of their favourite feature has been changed. We understand that, and we do everything we can to avoid it, but the truth is that some of our naming conventions don't really make sense. For example, a "learning path" is something only a guy with a degree in e-learning understands.