[Reposted from the Drupal development list.]

An early preview release of a module that may be of interest to developers and to anyone using multisites.

OG Sites enables a multisite configuration in which a central 'hub' site has a number of associated sites. The hub site features content and users from all sites, while each associated site can access only its own data (plus content explicitly shared from the hub site).

Now that the group is out of moderation I feel comfortable announcing this group. Drupal is not and does not provide a document management system (DMS). However, by creatively assembling a few modules it is possible to provide a limited amount of functionality. I've created this group to discuss strategies for managing documents in Drupal.

There was lots of good discussion in the DrupalCon presentation on Date + Calendar. Based on Earl's suggestion to make sure the Calendar arguments will work with any view and requests from the audience to be able to combine calendar and traditional views in the page and block, I've reworked the argument handling to make the Calendar arguments work independently of the calendar theme. So in the latest commit to the 5.x and HEAD versions, you can now add calendar arguments to any view (list, table, teasers, etc) and get date-based back/next navigation just like the calendar view has.

I maintain the signup.module. This module has long struggled with the problem of how to flexibly define what fields are requested and/or required when a user signs up for something. I might have a slick solution, but I'm not sure if CCK can accomplish what I have in mind.

With 5.x CCK, you can assign any fields you want in whatever groups you need to any node type. My module could allow site admins to define the signup/reply form for any given node type as a specific group of arbitrary CCK fields. This field group would not show up on the node edit form. It would be displayed on the node view page itself, so each user could fill-in, submit, and optionally edit their own signup/reply. All fields would automatically be treated as "multiples" in terms of storage, 1 set of each field's values per user who replies, but displayed as single values for any given user viewing the node. When a user replies, the values of any fields in their reply would have to be associated with their identity (uid for auth users, email for anon).

While I'm working hard on a new drupal website, I'm also thinking hard about the User and Content Points System I am trying to create for this website. Actually I had the idea of such a system before I started with drupal. But right now I'm very happy because of drupal's great module support, it seems to me that I'm going to work on only two additional modules and here we go:

I am sorry for the poor quality of the screen cast. I've never done one, and I used "wink" to do it. I'll probabley update the "how to" later down the road.

So, I made a screen-cast of my quickbooks module. It's very pre-alpha, and the screen-cast is not the best. But I did it quickly. I've been getting a few inquiries, and I figured this would be the easiest way to explain it. I'll be releasing it to the cvs by the end of this week so hopefully I can some collaboration on it.

Link to video: http://earnestberry.com/node/7/play

Currently what it does:
- Brings in customers

I spent several hours during OSCMS clearing old issues from the TinyMCE issue queue and grouping issues that have never been resolved or the suggested resolution was never included. My ultimate goal is keep the open issues in the queue limited to 4 or 5 pages. Last weekend by closing all the 4.6 issues, closing old install issues, and marking several issues as duplicate I was able to whittle the list from 13 to 7 pages. I wish I had better tools to group issues and assign tasks, but I'm slogging through this with what I have.

The date is 10 April, the time is 6:30 pm, the place is The Railway!

I will be away for a couple weeks so wanted to get the date locked in beforehand. Mark your calendars now and let's throw around some ideas for topics. Let's keep the Drupal buzz going in Melbourne. All drupalers are welcome - join us if you can on 10 April 2007 at 6:30 .

this is an idea i've been thinking about. posting it here so other folks can add to it, provide feedback, etc.

Summary

we could really use an install profile that setup a test site similarly to how drupal.org is configured (especially the project* modules and CVS integration). obviously, it wouldn't have the bluebeach theme, but otherwise, it would look fairly similar to d.o in terms of structure, content, permissions, etc.

this would greatly help people who wanted to reproduce bugs and test patches for the project* family of modules, which is something we desperately need more of.

We are excited to announce that our 1.7 Beta release is now available for download. This release features the new CiviEvent component, which provides integrated event registration and management, along with a new "Contact Dashboard" which gives constituents a consolidated view of their subscriptions, contributions, event registrations and more.

Other release highlights include:
* Create and save re-usable email templates (with mail-merge tokens)
* CiviContribute plugins for Authorize.net and Google Checkout
* Use customized versions of templates for any screen