[drupal-devel] Event changes

Kieran Lal kieran at civicspacelabs.org
Tue Apr 26 04:21:54 UTC 2005

Sorry to weight in late on this.

My only concern is that Event module has been in the works for many 
months and we are hoping that it will spawn a large amount of 
additional module development around events based applications.  There 
are lots of encouraging prototypes and designs being proposed.

I think we need a clear vision of which event concept is going to win 
in the end.  The risk is that we see two types of additional 
development going forward, development build around flexinode/CCK and 
development around event as it's own node.   If we do get competing 
event development communities this is going to cause problems.

Can we agree that the event API module is the path for additional 
development and the new eventnode is a stand alone module?

On Apr 23, 2005, at 11:54 AM, Gerhard Killesreiter wrote:

> On Sat, 23 Apr 2005, Boris Mann wrote:
>> On 23-Apr-05, at 3:48 AM, Moshe Weitzman wrote:
>>>> Let's be sure that we don't inadvertently limit that with a narrow
>>>> view of what an "event" is.
>>> a dedicated event node type would be an *option* for people who just
>>> want to add events to their site in a quick, easy way. noone is
>>> talking about precluding other node types from becoming events.
>> Exactly. It's not a move backward, it's an easy option for basic uses
>> *and it still ties into the event API*.
>> I still maintain that the current event module is actually
>> eventapi.module,
> Yes, nobody is debating that. It was the Grand Plan(TM) to make
> event.module an API.
>> but I'm not going to worry about naming issues.
> Great!
>> We'll go ahead and build a basic event module plus update.php which
>> should ease migration.
> Could you integrate this into the existing update.php script? That is, 
> if
> you agree to distribute your module as a subproject to the API.
> Cheers,
> 	Gerhard

More information about the drupal-devel mailing list