Should I release through drupal.org?

Hi, all. I've written a Drupal module which I'm planning to release as open source. I need to choose where to do so: through drupal.org, or through a site of my own.

I've been reading up on the Join forces with others page. It puts a great deal of emphasis on avoiding duplication of effort, and also on trying to control the proliferation of modules which do similar things to one another. That gives me pause, because the module I've written is a light-weight replacement for the Event module. I'm not sure such a thing would be a welcome contribution.

Allow me to explain the reasons I had for writing a whole new module.

I currently work for a department at a university. We use Drupal to manage the departmental web site, and also the web sites of a few project groups within the department and so on. We used to use the Event module for publishing upcoming events, but eventually abandoned it. There were a few technical issues -- we weren't too happy with the accessibility of the code, the UI wasn't as easy to use as we might like -- but for the most part those we could work around.

The real issue was organizational. We just don't have that many public events. We host maybe 3-4 public lectures per academic term. We do lots and lots of other stuff too, but almost all of it is internal: classes, administrative meetings, project group meetings, and so on. We don't need to publicize the internal stuff on our web site. The Event module was designed to produce calendars showing when events occur, starting on a per-month basis, and we only had about 1 public event per month. As a result, our calendars were mostly empty, and that made it look like we weren't doing anything. My bosses became concerned that some of the senior administrators might look at our empty Event calendars and start cutting our funding. So we ditched the Event module. (That happened some time ago -- Drupal 4.7 era.)

We still wanted to publicize events through our web sites, though, so I wrote a module to do so. It defines a new content type called "Upcoming Event" which is almost identical to a page except that it has a date, a start time, and an end time attached. The module then defines a couple of pages, one to show events which have past, and another to show events which are ongoing or haven't started. In both cases, they're not displayed as calendars -- just a plain list of titles with teasers. There's also a block listing stuff which hasn't happened yet. And that's all it does. No RSS, no iCal integration, no calendar views -- just some lists of past or upcoming events in chronological order. It's been working quite nicely for just over a year now.

I've obtained permission to release the project as open source. Here's the code (only compatible with 6.x at the moment, though porting it to 7.x shouldn't be hard once I get a moment to sit down and do so).

The question now is -- do I apply for a Drupal CVS account and release it through drupal.org, or not? The "join forces with others" page makes some good points. There ARE a bazillion modules out there already, and it is easy for people to get confused when modules do similar things to one another. The module was originally developed for internal use only, so that wasn't really a consideration. Now that it's going public, it is. So -- would I be better advised to set up a site someplace else for it, or apply for a CVS account here and send it in?