SoC

I posted the week 5 update on my site a few days ago, and not much changed since then. I'm still waiting to hear any feedback on the client I released a week ago. I didn't want to release the module until some testing was done on the client separately, but looks like I'll have no choice. For now, I've decided to make a few additional changes to the client, and the next version will be posted in a day or two. The module will follow shortly after.

-Max

So work on public and private files is really starting to pick up. A fair amount of work has gone into file.inc which includes adding a path for private files, switching file_create_url to use the database and adding some functions to swtich files to public or private. Things are becoming somewhat functional and progress is going well. If you want to check out the changes you can use bazaar to grab the code at http://drupal.codeincarnate.com.

This week was a big milestone for me, because I made the first release of the XMPP library that will eventually turn into a Drupal module. For now, the library contains just the client component which can connect to XMPP servers and send instant messages to other users. There is still a bit more work to be done (particularly on the Publish-Subscribe extension, which is currently non-existent), but I think this is a good first step.

So my computer died completely and I've been in the process of moving. But nonetheless I've made some progress. Since I am going to be making a batch against core I decided to make a bazaar branch. I'm mirroring this publicly and is accessible by the following command if you run linux.

I'll be updating this mirror periodically and a lot more stuff will be going into it in the next couple weeks.

I had my last exam yesterday, which is why you didn't hear from me since the last write-up from nearly a week ago. One more assignment is likely to keep me busy until Monday, but when that's done I can fully focus on my SoC project. That is, apart from the week-long interruption by the KDE conference where I head to on next week's Friday.

Oh boy, I wish I could borrow just a fraction of the time that I have in July and August, and use it before the mid-term deadline x-)

Short report about what's going on with the taxonomy manager. Last week my exams at university started (until end of June), so not much coding yet.

Very short update for this week. I'm trying to finish the parts of my client needed for sending and receiving messages. Next week I plan to start working on the Drupal module and API. Hopefully by the first or second week of July I'll be able to put something on my development site to demo the publish-subscribe functionality using an external server. Should be just in time for mid-term evaluations :)

That's all for now.
-Max

So this has been the quite week and I've been in the process of moving and thus been quite busy. Nonetheless most of the changes have been in upload.module so that there is now some visible change. Stayed tuned as the development pace will just pick up from here.

So, Mercurial, or "hg" in short. One of the two revision control systems originally written for being the Linux kernel's BitKeeper replacement - in the end, git was chosen for that job, but Mercurial lived on nevertheless. The requirement of being suitable for kernel development implied two features: performance (although git is still a tiny bit faster) and distributed development methodologies. Both are also present in git, and in fact, the two systems are very similar in scope, paradigms and usage patterns.

While git is written in pure C, Mercurial mostly consists of Python code, with only small, critical code paths implemented in C. This has benefits for Mercurial's portability, as can even be observed with other SoC students. git is pretty much focused on just Linux, whereas Mercurial can also be installed more easily on Windows and other Unixes. Not that straightforward graphical tools are yet as mature as the ones that exist for CVS or SVN.