Dan Poltawski

Its less than a week till 16 of us (moodle developers) meet up in the Czech Republic for the first Moodle Hackfest!

I'm really excited, the opportunity to to hack and plan together is a unique opportunity and something we tend to miss at moots as we chat to fellow Moodlers and find out what our users are interested in, drink Mojitos and don't get so much coding done!

I had hoped to spend a few weeks bug squashing, but sadly my life got in the way.

In any case i'm very interested to hear what you love and hate about Moodle at the moment so the developer community can come up with ways to resolve your problems. If you hate moodle, please tell me why, how can we improve it?

ps. please keep your fingers crossed, I've spent months negotiating a new house which I am hoping to own the day I fly to prague!

Its not difficult for me to realise that Moodle is a popular global project - I work alongside the evidence every day; reading Moodle.org, fearing the volume of bugs which come into the tracker and in CLEO, we recently surpassed 200,000 Moodle users. Buts its actually the small events in life which help me quantify this.

When i'm fortunate enough to go to Moodlemoots the international community of Moodlers is very evident and the passion is incredible.

Often, i meet teachers at completely non-moodle related social events and discover they use Moodle.

While i'm cycling to work and pass children walking to school, I stop and realise these children are likely to be using Moodle now or some time in their future (such is the dominance of Moodle in our region).

This week I discovered my old Sixth Form College is starting to use Moodle. During my time at the college I got a passion for computer programming and also benefited enormously from my first exposure to online learning. I don't teach people (at least in the formal sense) and so this exposure certainly helps me understand the Moodle philosophy more than I would've been able to without.

One of the greatest things about working on this open source project is that my contributions hopefully go some way to benefiting all these users: The moodlers I meet at moots, the teacher I met one time at a party, the schoolchildren passing me on the way to work and the college which gave me many of the fundamentals which have helped me contribute to the project.

Having ended up with a spare iPhone from a recent upgrade I decided to try jail-breaking the old one and see what software was out there away from the restrictions of the app store. I discovered that lighttpd, php and sqlite were all available from the software repositories for download - these three combined are enough to run a Moodle server. So out the window went cleaning my flat and sensible tasks - I had to make my phone into a Moodle server!


Getting the software for moodle installed and configured was relatively painless, the 'cydia' software installer appears to use dpkg under the hood, so I installed openssh server and apt through the gui installer and then sshed onto the phone to do the work with a full size keyboard and the moodle server was up and running quite quickly. (More details for configuration below).

Sqlite is a really interesting technology which seems to be making its way into a lot of software and I was quite interested to see Moodle support for lightweight testing sorts of applications and it has made its way into Moodle thanks to the great work of Andrei Bautu in his GSOC project last year. It only exists in the highly unstable Moodle 2.0 development branch so I needed to install this on my iPhone. Development is moving incredibly fast in the Moodle 2.0 branch so I was not at all suprised to see that the sqlite driver was not working. It took a bit of time to find out what the major issue with the driver as it was a silent error. But I eventually found and fixed the major issue.

Sadly, despite successfully installing and passing most of the database unit tests on my development machine with sqlite, some database queries were continuing to cause the iPhone server issues. I spent some bit of time improving the sqlite driver to show more debugging information and get to the bottom of the issue.

After a lot of debugging and irritation, it seems that the sqlite library version (3.3.7) linked to from php has a bug/incompatibility which means it does not like queries like:

SELECT student.id FROM mdl_user student JOIN (SELECT ra.userid FROM mdl_role_assignments ra) roles ON student.id = roles.userid

It'll report: SQLSTATE[HY000]: General error: 1 no such column: roles.userid
Where as it will work fine with something like:

SELECT student.id FROM mdl_user student JOIN (SELECT userid FROM mdl_role_assignments ra) roles ON student.id = roles.userid


(That was a simple example to try and find the problem - the SQL we have in moodle is a lot more complex that that).

To confuse matters, the sqlite command line tool I was using to test on the phone itself was a newer version (3.6.12), which works absolutely fine with both queries. The same was true on my development machine, which meant that I could install with sqlite succesfully everywhere but the iPhone itself. I assume the php version has been linked to the iPhone OS version - but I am too lazy to check/do something about it!

While I don't yet have a working moodle server install running on the phone itself, the exercise in improving the sqlite driver has been really useful. I've updated the driver in CVS, on recent sqlite versions it is only currently failing 9 of 1298 tests. (CEIL and SUBSTR being the major issues - but they are only used for stats and the admin healthcheck) so its really looking like a really useful option for those situations where a full-grown database server is overkill.


I've put a video of the (disapointing) install on youtube and you can find details of the various bits of configuration below.



Configuration Details
I love apt

apt-get install lighttpd php sqlite3 git

I've never configured lighttpd before, but a quick search for configuring with php and I made a very simple config with /etc/lighttpd/lighttpd.conf and /etc/lighttpd/mod_fastcgi.conf

JB-Phone:~ root# cat /etc/lighttpd/lighttpd.conf
include "mod_fastcgi.conf"
server.document-root = "/htdocs/moodle"
server.port = 80
server.tag ="lighttpd"
server.errorlog = "/htdocs/log/error.log"
accesslog.filename = "/htdocs/log/access.log"
server.modules = (
"mod_access",
"mod_accesslog",
"mod_fastcgi",
"mod_rewrite",
"mod_auth",
"mod_fastcgi"
)

index-file.names = ( "index.html", "index.php" )



# cat /etc/lighttpd/mod_fastcgi.conf
fastcgi.server = ( ".php" =>
( "localhost" =>
(
"bin-path" => "/usr/bin/php-cgi",
"socket" => "/tmp/php.socket"
)
)
)


And started the webserver manually with:

lighttpd -f /etc/lighttpd/lighttpd.conf


I created the /htdocs/ directories - and git cloned moodle into /htdocs/moodle and created the moodle config file as mentioned in the sqlite moodle docs:

$CFG->prefix = 'mdl_'; // prefix to use for all table namesV
$CFG->dbtype = 'sqlite3';
$CFG->dblibrary = 'pdo';
$CFG->dbhost = 'localhost';// leave dbhost to localhost (or blank) to store the database file in Moodle data directory


Oh and I was also naughty and made the 'zip' php extension an optional item (as it wasn't in the packed php version):

diff --git a/admin/environment.xml b/admin/environment.xml

index e15a33b..94ed8f2 100644

--- a/admin/environment.xml

+++ b/admin/environment.xml

@@ -262,7 +262,7 @@

           <ON_ERROR message="ctyperequired" />

         </FEEDBACK>

       </PHP_EXTENSION>

-      <PHP_EXTENSION name="zip" level="required">

+      <PHP_EXTENSION name="zip" level="optional">

         <FEEDBACK>

           <ON_ERROR message="ziprequired" />

         </FEEDBACK>

Enjoy!

At a moodle developer meeting recently, some developers were asking if a mentoring scheme could be started up for new developers who wish to get into moodle development. Unfortunately, there just aren't enough hands on deck with time to manage to do the mentoring for something like this, despite the obvious long term benefits.

I suspect we will always be on an uphill battle to improve our documentation and resources (like many things in life, documentation isn't very exciting or give instant payoffs to our users), but there are some resources which should be very useful to new developers: dev.moodle.org, Moodle Docs and of course the forums of moodle.org.

When I think back to how I have learnt about various aspects of moodle development i've not really used many of those resources very much, instead i've been lead by the constructivist approach! My journey into moodle development started in MDL-6784, this was my second bug report, first patch and first accepted patch into moodle! Since this first patch i've reported/fixed/watched/contributed to many many moodle bugs and I think this is my secret to moodle development!

Of course this is really no secret at all, the code and bugs are open for everyone to see. But I believe that spending time finding, reproducing and resolving bug reports gives new developers an invaluable insight into various aspects - which libraries do what, what are the caeats of x, how to fix y and where to go looking for future bugs! By watching bug reports, seeing comments, reviewing patches and fixes commited slowly your knowledge of moodle wil become massive, despite a lack of dedicated mentor!

I do have a few general tips for moodle debugging which I i'd like to share (and apologise as they feel 'obvious' to me)!

You've set debugging to DEBUG_DEVELOPER, right?!

print_object() is basically print_r with whitespace and I use it at least 1000 times a day[1]. Its not just for objects Print statement debugging might not be sexy but its essential and useful

debugging() prints a stack trace - why wouldn't you use it!

grep backwards for lang strings! (grep 'my error message', find the lang string name (myerrormessage) and then grep for that)

I die() lots.

We have CVS history and bug numbers for a reason! Look at CVS history of a file and bug numbers/linked issues!

Keeping up to speed with CVS history is a really useful exercise, if time consuming

I often wonder if I would still be in moodleland if my first patch was not reviewed as speedily as it was, I think probably not. In which case how do we ensure potential contributors such as myself don't get lost in our workloads and we encourage new contributors!? Its interesting to consider.

If you are a new contributor please don't be put off by lack of review, pester us and ensure your work is reviewed because moodle is really great place to work! You could look at some other bugs while you are waiting

I'm off hoidaying - see you all soon!

[1] I also exaggerate 100s of times a day too.

I'm really privileged to be a mentor for Google Summer of Code with Moodle again this year! If you've not heard of google summer of code before the basic premise is that google fund university students to work on open source software over the duration of their summer break. The idea is to get more contributors into open source software and moodle is a proud participant to this great scheme. The great slogan is 'flip bytes not burgers!'

Penny and I are really excited to be mentoring Christopher Waclawik in his project to make XML administrative settings for moodle. We're just coming to the end of the community bonding period, developing the specification for the project and moving towards the start of coding, but of course we still need absolute community involvement!

Moodlers, imagine the prospect of installing moodle, choosing your local language and default settings which fit best with how you would like your moodle to be setup. This is one of the great aims of the project!

The advantages of these defaults have perhaps best shown themselves to me in the lively discussions which took place recently about grades over 100%. This concept of grades over 100% doesn't seem to have spread much further than the in the USA, many outside the USA can't understand the concept and indeed the original release Moodle 1.9 didn't support this concept at all. Functionality has now been implemented in moodle to allow this - but it is not default. This choice makes sense to many but those who feel like this functionality is essential - like many localised settings in moodle its impossible to get the perfect defaults for all scenarios - this is really where I see these defaults fitting in.

In my own day job we are frequently overriding moodle defaults to fit more with our localised environment (UK schools) so I realy can envisage the advantages of these for institutions rolling out moodle. But what perhaps I think is the most exciting element of this project is that it doesn't have to be exclusive, we could all create 'dans awesome moodle settings' moodle settings, share them amongst oursleves and satisfy our local preferences or legsilsative obligations. This power of templates might help to combat the misconception that moodle doesn't fit 'x senario'.

Please contribute your thoughts to Chris' project specificaton, point out areas we've forgoten and other improvements we've missed! This is the great thing about open source, we're hoping for you all to become involved and become invaluable resource to us all!

See the progress in MDL-18548, Development:XML_Administrator_Settings and in the forums.

I read about the launch of the Guardian Open Platform and immediately thought it was cool, later considering how awesome it might be for teachers trying to find resources to support their teaching - I wanted to play. The prospect of a teacher having access to search and embed all the content which was made available from the guardian sounded great & seemed like a job for a Moodle 2.0 respository plugin - so I applied for an API key.

Last week my request for an API key was finally accepted and I spent an hour or so playing with the API last night. My first thought when reading about Guardian open platform was the prospect of using it to find and embed images. Unfortunately the platform doesn't explicitly support images at this time, and videos are supported only as a link to the source page. This means that it didn't explicitly fit with the way other repo plugins work. The guardian platform does support the full body of text articles being retrieved and so I created a very hacky plugin which would return the body of an article in the same way youtube video links are embeded with the youtube plugin. This was mostly pointless other than for my own satisfaction as there is nothing to receive this in the editor properly without copy and paste. It seems like its probably an abuse of the repository API to not retrieve files, but it was fun to play with it.



I'm not sure if the repository API is the appropriate place for embedding this content and there are significant barriers with the guardian license terms for this to be a useable plugin. The license terms for the platform wouldn't necessarily suit teaching at this time (content shouldn't be stored for more than 24 hours - though it would be fine to re-request it), but of course this shouldn't be a blocker to see if the technology would work. A lot of educational institutes have access to newspaper content via means such as lexis nexis and i'm sure a potential licensing solution for education could be developed, so its fun to play with.

On a technical level I used the openplatform-php library which guardian provide and I didn't really like. I didn't like it as it generated php warnings a plenty, and I wasn't feeling particularly motivated to rewrite all these bits, so I hacked each one I came across away in a really crappy way. The really short source code (respository.php is the only actual moodle source) can be found in my git repo. Though its not that useful (as I say, just hacking in an hour) and amongst other things doesn't deal with problems of requesting content daily according to the license terms. Even so, fun to play with open apis and integrate.

Simon Willison gave a great introduction to the whole platform, including the data store - which is equally cool.

Great news, Moodle has been accepted into Google Summer of Code 2009! Great work everyone, especially as there are for less slots for projects than last year. Lets try and come up with some more great project ideas and thank Helen for all her work in submitting our application and keeping us all organised as ever!

When I last updated on the status of the Google Docs Repository/Portfolio plugins for Moodle 2.0, I mentioned that it wasn't possible to download documents from Google and this meant it wasn't really possible to make a repository plugin.

A few weeks ago Google updated their API to allow for applications to download documents, so today I found some time to update and commit the plugin into Moodle 2.0 .

At the moment it's not possible for users to choose which format to export their document as, but the Google API allows exports in in a variety of formats. I'm hoping to work with Dongsheng to work out how we can let users choose which format they wish to export their document in on a per-file or per-user basis. The plugin also needs folder support adding.

As always, please test and file bugs in the tracker.

I came across this interesting paper on the motivations of developers contributing to Open Source projects a few weeks ago - I've finally got round to reading it & it does to seem to cover all the main motivational areas I could think of and have experienced. Though i was quite surprised that there was such a high percentage of developers paid to work on OSS seven years ago!

One element that I don't think was stressed enough in the paper was how the stimulating environment of an open source community itself is a motivating factor. I find that people who contribute to open source software tend to be highly motivated and passionate about what they do (not surprising really, since they are contributing..). This makes for a great environment to challenge and learn from each other, which is really hard to match in any other situation.

Over the past few weeks, i've been working with Francois, Penny and Matt to take over maintaining the moodle package for Debian. Unfortunately the previous maintainer could not keep up with maintenance since some time ago, and the package was orphaned (awaiting someone else to take over caring for the package). Penny invited me to get involved & we've been hard at work since: Producing a huge security update to debian stable, getting moodle accepted into lenny - the next version of debian (by fixing outstanding bugs which blocked it from being accepted) and getting on top of the debian bugs which were outstanding.

Unfortunately debian was in freeze stage for lenny when we took on maintaining moodle, so we could not upgrade the version from 1.8.2 (however this is much better than 1.6 which is currently in debian stable). Its great to keep moodle in debian with security support and a lot of thanks is owed to Francois Marrier (the debian developer who has taken this on) to make this happen. I'm hopeful i'll be able to buy francois a drink in thanks sometime soon.

Personally, I use Debian in my leisure & working life extensively (indeed, its the platform we use to provide moodle for 1000 schools), its a project close to my heart (and saves me so much time) so i'm really pleased to be able to contribute back to debian (as well as moodle). I have been interested in getting involved with debian for quite some time - doing this as part of the moodle packaging team is a great way to begin to get involved.

I'm confident that the moodle community will benefit from increased exposure of debian bug reports and the closer exposure of perspectives of upstream distribution packagers will also help the moodle development community.

I was just reporting MDLSITE-594 and I noticed Mojtos in Martins profile interests. Mojitos have become somewhat of a moot tradition which i've also come to appreciate! In the current economic climate - its probably the most stable moodle development currency!

So who is responsible for introducing the moodle's premier cocktail & is there more to it than the first two shared letters?

I came across code_swarm and couldn't resist trying it out, its cool to see the progression as more contributors come on board over the years..


7 Years of Moodle Development from Dan Poltawski on Vimeo.

One of the many major features in the Moodle 2.0 Roadmap is an overhaul to handling of the files in Moodle. The Portfolio (push from moodle) & Repository (pull to moodle) API's allow for external systems to interact with Moodle and bring exciting new possibilities!

A few months back when Penny and the gang in Australia were working toward getting a stabilised API, I decided to test them out and try to develop plugins for Google Docs during a free weekend. I was really pleased about how easy the plugins were to develop and found the process very productive - I used the api in a slightly different way to existing plugins which allowed for additional testing and we collaboratively improved things.

The Google API's are pretty simple to get to grips with - whilst there is a mammoth zend php library which will interact with google already, I wrote my own since I didn't think we really wanted that much bloat in Moodle. All in all it was quite a fun experience, and I got mostly working portfolio and repository plugins with very little work.

Unfortunately with the repository plugin, 'mostly working' was as far as I could get.. I could browse my Google Docs from Moodle, narrow down documents by text searches of the document contents and even delete the documents if I wanted - but not download the document into Moodle. Which made the plugin largely useless.. There are a few open bugs for this and it seems google are working on a solution, but for the time being its a little bit frustrating. There is a workaround using a different method of authentication but i've not yet got that to work either.

At the time I didn't commit my plugins to moodle and left them in my own git repository as I wasn't happy with this situation, I also wanted to investigate if OAuth was worth using and rapidly became busy with other things.

This weekend I finally got some time to work on this again and get some of the work into moodle core.

For authentication, i've created the plugins using Google's AuthSub (whilst keeping it pluggable), which still seems to be the best way of authenticating users for Moodle because:

• It doesn't require any administrator setup (registering, adding API keys/certificates etc)


• It doesn't make the user enter their google username and password anywhere other than google (I feel very strongly that this is security practice we should be encouraging)

OAuth looks pretty good and useful for authenticating with multiple services, but it'd require a considerable amount of administrator setup which I was keen to avoid in favour of the plugins being used

After a bit of tidying up and updating to match the recent moodle developments I've now commited the Google Docs Portfolio plugin. It allows images and documents to be exported to Google Documents in a basic manner. I've not found a solution to the google docs repository saving problem, but i've created a prototype which will just insert links to google documents (rather than embedding the content).

As the Google API's are pretty consistent, most of the work I did creating a library for Google Docs could be used to create plugins for Picasa Web Albums in very little time, so i've also created plugins for Picasa too and these allow both import and export from Moodle to Picasa. It should be reasonably simple to make other googley plugins by expanding lib/googleapi.php.

I've made a hacky little screencast to show off these features at this early stage: