SoC 2009

This is the third update of the Rules Monkey Summer of Code project. The enhancements for the Rules Scheduler module are now finished and have been reviewed many times by my mentor and me. (see the issue for patches and details). They will be comitted to the official Rules CVS development branch in the next days.

Alright, after much mucking about with licensing issues and contacting library owners and further code merging and committing, it looks like we are back on track. Late night hacking has resulted in the following features:

• An administration page where you can log into a Google Account via AuthSub
• A testing query page where you can see what data Analytics will send back

I miss one WU again(:-( mainly because of final deadlines in my courses last week), but here are the news for both weeks.

It's divided in 3 sections: tests, stable branch and oop branch.

This is the second update of the Rules Monkey Summer of Code project. I'm sorry for the relatively long pause between this post and the previous update (university kept my quite busy in June, but now I'm full-time available).

The progress that has been made so far:

• Work on the Rules Scheduler issue (http://drupal.org/node/455560)
• Successfully explored Views, DB-Schema and Rules hooks
• Scheduled tasks can now be viewed, a Rules action is available to cancel specific scheduled tasks

Completely forgot that we need to write weekly updates, thought everything moved to the wikis, sorry about that.

I missed one WU, so what have been done since then:

• array access really helps to migrate to OOP, so each class implements that SPL interface
• Like it was expected, dia auto-generation only did the easy part, and like it's mentionen in WU2 I made a bulk update on each class trying map all needed functions as methods. After that I needed to make lots of manual changes, to use the methods and data members, but also fix the last ones to made relations between classes.
• I'm using references to the "parents" on "children", instead of lists of "children" on "parents" or both approaches (like item class repository data member instead of list of items on repository). This is not definitive, but now it's like this.
• Replace username on versioncontrol core in favor of author and commiter.
• Use already defined database identifier names instead of "id". This is mainly for use the cool drupal_write()
• New stuff working pushed on versioncontrol core oop branch, but like you imagine I needed a backend to test, so I used my own branch of git backend
  • Repository add/edit/delete/fetch
  • VCS Account add/list

(For information about my project, see here. Put shortly, it's about enabling Solr to index RDF data via drupal.)

Before starting the actual coding, even on prototypes, the basic options for implementing this will have to be discussed. At the moment, my mentors and I see the following three possibilities:

All approved students will be asked to keep track of the pertinent details about their project in a central wiki page on this group. The following is a template for them to use to do this.

Project information

Project page on drupal.org: http://drupal.org/project/bot (original module, customizations are going to be placed into sandbox)
Student: Balazs Dianiska (snufkin on d.o, snufkin@drupal.org on g.d.o)
Mentor: Morbus (Morbus)
Co-mentor: dmitrig01 (dmitrig01)

Current status: Working on setting up PHP IRCd for automated connection and other unit testing for the bot.

Description

Bot module is a Drupal PHP IRC bot written by Morbus Iff. It runs on many Drupal related channels, providing various tools from code documentation to collaboration between users. It utilizes the CMS as its storage and code handling back-end, but until now not many public modules exploit the potential in this website - IRC interaction, interacting with Drupal content, site users for instance. This project will extend its core in this direction, and by writing tests and documentation for it will make further contribution easier.