SoC

For this Summer of Code, I'll apply for reworking the Project module to free it of CVS specifics. The greater plan is, of course, to get SVN support into project.module (and pave the way for other RCS backends), but if I am to believe knowledgable developers like dww and chx, getting the revision control functionality abstracted out into an RCS API module is already a lot of work. In case it should work out faster than expected ("unlikely" :D ) I figure I can still do the SVN specific bits in the time that remains.

You can find my application here. It's essentially complete, but before submitting it to Google I'm still waiting for feedback from dww, and yours can be helpful as well! As a short teaser, here's the introductory part of my application as copied from my website:

Make case tracker more project management friendly.

Motivation

This is a copy of a proposal on the OpenAcademic wiki -- feel free to edit it there -- for those with an OpenID, it's OpenID enabled.

It's on d.o at http://drupal.org/node/127554

1. Overview

This is a list of 7 successful candidates proposals from soc2006:

Name: [Project title]
link-to-proposal

I will add the rest of the proposals as and when i find them but hopefully these lot should be helpful enough in seeing what kinda of proposals where accepted and the styling etc.

This is just an idea.

We've built sites on Mambo/Joomla in the past. mosforms, an extension to build and output custom forms and store the input much like CCK works for Drupal, was yet a simple, but great component to design site contact and other forms for Joomla. mosforms has evolved and is available as Fabrik - Joomla Application Builder now. There is nothing that might compete with our CCK here, but the last line of the published roadmap for Fabrik sounds quite interesting to me:

SoC is ending soon and a lot of code has been written. So I would appreciate if you could help testing my modules!

The modules I've built are:

• nodeprofile.module - Marks content types as profiles
• usernode.module - Automatically creation of usernodes
• nodefamily.module - Builds nodefamilies based on content types and author information
• views_fusion.module - Provides fusing of multiple views.
• pageroute.module - Allows the creation of userfriendly wizards

All this modules are compatible with drupal 4.7, so use a recent 4.7 install to test.
All modules except of the nodeprofile module have been built generally, so that they are useful for all nodes, not only for nodeprofiles!

Hello, all,

Rob is hammering out the gradebook, and for those interested, you can check out the current code in cvs.

Things are moving forward nicely -- look for more to come next week.

Cheers,

Bill

Just released new version. Included in the this release is the new-fangled cre query object and comment_recommendation.module which recommends comments within the current node being viewed.

The object allows for joining on any table. Please remember to use {} and a name to identify your table.

For instance node_recommendation does this:

Ok major speed fixes. Redid the query compeletly and added a average user vote table. This allows for the movelens database to run MUCH MUCH MUCH MUCH FASTER. I will begin testing it later this week and give back some scores that should be interesting. Try running the update script for me. I did not test it out and I am worried that I didn't write it properly (my first update() :-D ).

Still working on creating a query object that will prevent the one issue that is in the queue right now. More to come soon...

http://drupal.org/project/cre

Scott

I've got a views integration for my nodeprofile modules working. This also works for general nodes, not only for nodeprofiles.

By doing the nodefamily views integration I ended in writing the module views_fusion:

With this module its possible to build views which display information of several nodes in one view - useful for tabular views.

This is achieved by defining multiple views, one for each node. Then the views fusion module is used to melt these views to a big one which contains all the information.

More information on this module

This module works great together with the nodefamily module, so it's possible to use nodefamily relations for joining the views/nodes. However I've written the module in a general way so that it's possible for other node relation modules to use it the same way.

Of course testers and feedback are welcome.. :)