Port RSVP to Drupal 7

Has anybody thought about a total rewrite of the module? Right now the RSVP module is to big and does to much. It also seems that the module is not well maintained right now.

What I see is an entity based approach that is fieldable (including some default fields [yes/no/maybe]) so that it can be attached to almost every other type of entity like nodes, users or organic groups. That would allow flexible storage of the data (even outside of Drupal [external services]) and fields could be shown in different widgets and displays. The advantages of this can be seen in commerce and organic groups.
If we would combine this with a tight views and panels integration I see a really flexible system that would be ready for a lot of use cases.

There is just one white spot in this. What plugin mechanism to use for better extensibility. Right now I'm in favor of ctools, but open for new ideas.

So what do you think? What use cases do you have?

If there are enough people interested in a rewrite I would start it as soon as possible.

Today I started with a complete rewrite of the module for D7 using a fieldable entity. If all goes well there will be a working dev release by the end of next week. The new RSVP will depend on the entity module.

If you have any suggestions or use cases you want to see implemented please or have suggestions comment. Now is the time to speak out loud. :) RSVP is a huge module and we have to make priorities what features need to be reimplemented first.

I stopped my inital rewrite of the modul and am now looking for the "relation" module that might solve many issues. If you think about RSVPs as basic graphs then this should make you very excited, because with relation you can create really powerful relations out of the box between all kinds of entities.

So you could have a user entity and create your own rsvp entity or just a node bundle (node type) and create a fieldable relation between them. The relation itself would have fields that add the need functionality for the individual RSVP settings (as in og, media, commerce).

I think that would allow a huge amount of flexibility. What needs to be solved are the administrative processes and how they are integrated. Right now I would like to use a similar approach as seen in og and commerce. Create as many admin listings using views, individual adjustments using rules and bind this all in a admin ui like og it does.

I would love to discuss the pros and cons of such an architecture before I start my work again.

Link: http://drupal.org/project/relation

Yes that's right you can come up with all those crazy ideas, where an RSVP could be added to files, comments, users, taxonomies, etc… And along with the basic RSVP field you can add other fields that add settings for the RSVP like access.

I think it's worth thinking that trough before starting to code a new version from scratch. :)

Right now I'm simply out of time and do not have the time to code the module. The solutions discussed are still valid. I'll post a message in the queue when I can start.