Welcome to the Drupal events working group. This group is for discussion of modules and code related to events, calenders, timezones, and related issues. This is NOT a group for posting about (real or virtual) meetups and similar "events".
Folks interested in this group may also be interested in the Conference Organizing Distribution group, an installation profile for conferences built in Drupal.
Scope, scope creep, requirements and software goodness
Folks,
I'm really getting excited with all the participation! Let me take a moment to start a new thread regarding the "meta-process" I'm engaging in and what my goals and objectives are:
- Get out a new version of Events - soon!
- Work in a community context
- model good software development behavior
- document the hell out of Events for future generations...
We all agree on the basics - but I think that some of the comments are out of scope for what I'm interested in. Here's what I'm interested in - I want to get functionality out that can be used for grassroots, community based organizing - in this case Houseparties. I would also like to see the system usable by political and other campaigns to do less-formal campaign based events. In my view (which is subject to change) this does not include "volunteering", "choosing a date for a meeting", "pre-event organizing" - you get the idea.
That being said I would be happy to help document all these other issues/scopes - but I would probably need to see a clearly defined statement of functionality/description.
So if you would like to see a broader scope - this is the place to have that discussion.
Read moreGoJoinGo flowcharts
Here are some workflow documents from GoJoinGo which might be helpful.
Read moreAttendees Screens
Another in the series of screens. This is a list of attendees - versions could be used for public, attendee and event organizers.
Read moreTime for another events call
Dan's made some great progress in defining the space. CivicSpace is going to be bundling some of this documentation over the next few days to make it more presentable to potential contributors.
Let's get a Skype conference call scheduled so we can keep this momentum on events going.
Cheers,
Kieran
RSVP/Register Screens
Here's a mock-up of an RSVP/Register Screen. Hopefully it isn't too busy. So the obvious question is how to use "Signup". The biggest issue is that I want to be able to use CiviCRM as the data store - anybody should be able to define their own data store. Signup has a nice "lightweight" store which is cool for lots of uses - but this may be too complicated?
Also looking at RSVP - but I dont' think there are CiviCRM hooks....
Read moreAdd Event Screen
Here's a screen mockup of "Add Event". No surprises here. I've introduced a concept of "no time" (at least I think I have) - stolen from my Palm scheduler. Obviously location comes from the "location" module. I've added a concept of "publishing location" which means whether or not the location you input shows up in the node. It would be nice if the location information could be sucked in via a filter in either the description or instructions text. "Instructions" could be detailed instructions about how to find the event, or information on how to join a call. There is also the concept of "private" - what that actually does needs to be worked out in more detail.
Read moreRoles and Relationships in Events
I'm copying out jimw's recent comments (http://groups.drupal.org/node/465#comment) to begin a separate thread.
jimw brings up a couple of issues that has been talked about at some length. Specifically he is interested in roles like "volunteer", "presenter" etc. as they relate to Events:
Read moreClass Diagram for First Pass
Here's a class diagram covering all of the classes I've discovered that would be used in the first pass. I'm sure this will change in the next few days. I'm going to break this down in subsequent posts so we can look at some of the more interesting issues in greater detail. See below:
Read moreSequence Diagram III for First Pass
This is the third of three sequence diagrams for the first pass at Events -
Read moreSequence Diagram II for First Pass
This is the second of three sequence diagrams for the first pass at Events -
Read moreSequence Diagram I for First Pass
This is a sequence diagram (1 of 3) that covers most of the UCs in the first pass. Sequence diagrams are useful for looking at the relationships between different classes in the system within particular Use Cases or scenarios. They are pretty straight forward and I find them pretty useful.
Read moreA First Iteration for Events II
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:
Read moreEvents Use Cases and User/Event Relationships
Here is a first pass at documenting all of the use cases* to be touched on by the Events system. This list drew from the existing documentation that I could find and tries to be inclusive and exhaustive. I will update as people point out additions, mistakes etc.
- Use Cases are a notation meant to capture meaningful system capability from an end-user perspective. They can be used to document requirements and inform implementors as to the intent behind requirements. There are some standard ways to create and use Use Cases - but personally I feel that they are what you make of them. The image below does not contain Use Cases per se, but the titles of Use Cases. They are meant to describe the scope of the project in a way that is useful to all participants.
Action Items from IRC meeting 2006-05-08
During our IRC meeting and phone call we came to the following list of action items:
- Define Relationships via a common API – crunchywelch
- Mail UI – drob – check-in with Amazon and the folks working on mail
- Mail API – drob – check-in with Amazon and the folks working on mail
- Use Cases on groups.drupal.org – drob to put up his UC titles for others comments
- Librarian - ?? - drob thought it a good idea to have a committed Librarian for all things events - however no-one volunteered
- Theme and/or helper functions that modules can use to help with theming - grugnog
define_relationship(nid = INT, uid = INT, status_flag = STR, module_name = STR);
retrieve_relationships(array(nid = INT, uid = INT, status_flag = STR, module_name = STR));
retrieve_relationships(array(nid = ARRAY, uid = ARRAY, status_flag = ARRAY, module_name = ARRAY)); ?
retrieve_relationship(rid);
– statusflag value = string defined within moduleResources
Here's a centralized list of resources related to improving event management:
- Event Improvement DEP: The beginnings of a full-blown DEP on the subject of events in Drupal.
- Event mangement module comparison: A breakdown of all event-related modules, where there is overlap, etc.
- Mail working group: Collection of individuals working on Drupal email solutions
IRC Channel: #drupal-events on Freenode
Please feel free to add to this list either by editing it directly or posting a comment.
Read more

