i've had this sitting around in my sandbox for a while, but with the 4.8/5.0 dev cycle, I was too busy to do much with it. it's a proposed relationship API for inclusion into drupal's core.

Schema-wise, it works like this:

required fields:
rid -- the relationship id. just an auto-id to give us something concrete to connect to. term_node lacks this, and it's a PAIN.
source_nid
target_nid -- the two nodes being connected to each other
relationship_type -- a simple descriptor like 'child' for a book page or 'comment' for a comment or 'describes' for a taxonomy-term-as-a-node.

optional fields:

The revision system.

Drupal has a great feature whereby editing a node can create a revision of that node. Whenever create new revisions is checked under Publishing options, editing a node will result in a new revision. Users with the view revisions or administer nodes permissions will see a Revisions tab on node viewing pages. The Revisions tab interface allows you to view the individual revisions, revert to an earlier revision, and delete revisions.

One interesting detail of the system is the behavior of the reverting mechanism. Let's say you have revisions {1,2,3,current}. If you revert to revision #2, a copy of #2 is made and the copy is set as the current revision. Thus, after reverting you'll have {1,2,3,4,current}, where current is a clone of #2, and #4 is the previous current revision.

On the drupal shop talk call today the issue of spam user registration came up (see notes). Laura suggested asking the question here.

How are people dealing with spam (in all its forms)
1) spam user registrations
2) spam content
3) comment spam

are you using Captcha or other user challenges?
Heavy moderation?
user based spam flagging?

let's here it!

I have a mostly-working Views Calendar module available at http://www.drupal.org/project/calendar. It's still a little buggy and the css needs tweaking but it is generally working. Create a view and select the Calendar display (instead of table or teaser). Add any date field to the view (CCK dates, event dates, node updated dates, whatever). Add three arguments, Calendar: Year, Calendar: Month, and Calendar: Day.

Navigate to the view where you will see a year of mini calendars. Click on a month name to see the month or a day name to see the day. Back and next navigation is provided for month and day views (not yet added to the year view). It comes with a default calendar that displays all nodes in a calendar by their last updated dates. If you like, select the Calendar view for the block, too to get a mini calendar in a block.