The River

I'm working on a site that's asked for a golf scores tracking page where they can record scores and dates for a host of golfers to calculate handicaps and track things like tournament eligibility, etc. A key element of the system is that my admin needs the ability to enter 10 or more scores for a single golfer in one session (he typically updates the system every 2 weeks). Simple enough, right?

Our first Drupal based site is almost ready to go live. So far, Drupal has been a very powerful and fun environment to work in. We've started with the Open Publish distribution of Drupal, and have made a number of customizations to meet our needs, primarily in creating a sub-theme based on the Open Publish theme, and adding, removing, and configuration of modules. And of course blocks, views, and contexts.

Hey all!

Hope Christmas was great and Happy 2011!

In the past, we've sponsored development of a few modules, but those have always been added under the developer's drupal ID. Now, we've got a module the community chipped in $1,000 for and we've submitted it to be added...on December 3rd.

I know things are busy for the volunteers approving modules with D7 and all, but will it ever get approved?

Here it is: http://drupal.org/node/988244

Any ideas or feedback from others who have been through the module approval process appreciated!

How do most people approach updating core on their sites? My instinct is to wait 2 weeks after a release for people to come across any problems and to give maintainers time to release patches for the major modules. Is that reasonable or is the core code so rock-solid that I am waiting for no good reason?

Purcell