A First Iteration for Events II

Events happening in the community are now at Drupal community events on www.drupal.org.
drob's picture

I've done more work to define what I think a reasonable "first pass" could look like for events. My objective is to establish end-to-end functionality, but to cut back on features so that this phase could be completed in a relatively short timeline. I have used the UCs from my original pass through and so this new diagram is a subset of the original:

So to be clear - I'm interested in using what is already available as well as coding up what isn't to achieve the above. Hopefully I'll start on this within the week. I've altered the UCs overall slightly - but nothing major. Also I'm using a new modeling tool - so we'll see how that goes.

AttachmentSize
FirstPass.png74.46 KB

Comments

Implementation idea

mfredrickson's picture

Hey Rob,

From the looks of it, three parts of this diagram are roles, actions, and a specified workflow. Perhaps the end result could be a relatively simple module that populates the database with a workflow, 2 roles, and some actions (the code for which could reside in the module).

Why reinvent the wheel?
-M

Possibly

drob's picture

Could you mock something up?

Relationships & site structuring

Group organizers

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds:

Hot content this week