SoC 2007

The first release of DAST is available on d.o: http://drupal.org/project/DAST. See the INSTALL.txt and README.txt - you'll need to download additional dependencies from http://www.abeharry.info/stuff/dast-deps.tar.gz or http://www.abeharry.info/stuff/dast-deps.zip A guide to using the dast-patch build file is available here: http://groups.drupal.org/node/5124 I'd appreciate feedback from anybody who wants to try it out - for what the project is trying to accomplish see here: http://groups.drupal.org/node/3913 .

Again, I got lots of valuable responses from my mentors and Morbus, they really kindly follow my work and tell the problems and the suggestions.
You can install the FeedAPI modules to any Drupal 5 site and you can do the following:

So this has been a good week for files. File uploads are mostly completely working and interfaces are being changed over to use the new file object interface. Right now there is an expected release date of August 5th and most of the code should be done by then. As usual you can check out the current code at http://drupal.codeincarnate.com with bazaar.

Well, I promised you an update on the API module, so that's what you'll get. Just a short notice beforehand: the CVS backend's database structure is now online and available for everyone's reviewing pleasure. Module functions will be added in a week or two, but before that, I'll get the xcvs-* scripts to fill in the entries for the new database structure. I've also made a (slightly different, but largely similar) SVN version of the .install file, you can find that one attached to this post. (As a Subversion backend module is only an optional deliverable, I'd rather not start a versioncontrol_svn project and its directory in CVS just yet.) So it seems to me that deliverable number three, a finished database schema for the CVS backend, can be marked as done.

Get to the point, dude!

Ok, ok. My remaining problem with the Version Control API was that it lacked a way to consistently deal with tags and branches, and to uniquely identify files and directories even if they are not versioned themselves (which is the case for directories in CVS and other version control systems). So I thought a bit more about how to deal with this, and the outcome is a new building block object for items, in addition to the previously existing ones for repositories and commits.

I'm contemplating how to implement a scoring factor hook into my new fuzzy search engine module. I believe what may work out to be the best way of doing this is allowing modules to tap into this scoring hook at the time of indexing.

Each hook should return a value between 0 and 10 as a score to add to the node being indexed. Then in the administration screen an administrator would be able to set the importance of the score given by that hook. This would allow the administrator of a drupal site to manage the scoring from different contributed modules.

Lately I have been scrambling to get the passkey portion of the tracker working. The system is designed to keep track of users even if their IP changes. Passkey also adds a layer of security to the tracker, making it almost impossible for non-registered users to use the tracker. The way the system works each user has a passkey assigned to them. This passkey is placed in the announce url of the torrents that the user downloads, (http://example.com/announce.php?passkey=).

[disclaimer] I'm writing this update while drupal.org (including g.d.o) is attacked by database-eating gremlins, so I can't currently check back on previous entries. Apologies in advance if I mention something that has already been said before. Yes, I could use the Google cache, but that's kinda tedious. [end of disclaimer]

So, I've been pretty absent for quite some time. After getting my university stuff finished, I found a bit less time for my Summer of Code project than I had expected, moving out from the dorms, packing bags, wrapping up undone stuff, whatever. Last week (June 29th to July 7th) I've been attending aKademy, the KDE conference, as previously announced. Great event, great people, great location (this year it took place in Glasgow, Scotland). You can read lots of coverage on KDE Dot News - start here (you can find me in the group photo) and go left in the navigation at the buttom, the marketing team has been active as never before. I wonder in which ways DrupalCon will be different from aKademy, as in my view the projects and their attitudes already differ fundamentally. Ok, so that's that.

Not having found the time before, I reallocated a few hours from aKademy's hacking sessions to my Summer of Code project. Since the last real update, the RCS API module has changed its name to Version Control API (versioncontrol.module), and the former project_rcs.module is now Version Control / Project Node Integration (versioncontrol_project.module). Both now contain a good amount of API functions for accessing commit data. Even if the implementation is still missing out (which, according to the project proposal, has been planned this way), they are the core of what other modules will use from the API module. (Read more...)

Last week there were important decisions again:

The only update of interest to the general populace is the creation, together with Matthias Hutterer of the Taxonomy Manager GSOC project, of the Taxonomy Drupal Group on this site.