This Cookbook shows, how you can have some different Event-types in one Event-Calendar for Drupal 7 (http://drupal.org/node/1477602). The Event-calendar shows every user only the for his role(s) allowed Event-types. You can use this e.g. to differ in internal, administrative and public Events.Read more
The Rules module allows site administrators to define conditionally executed actions based on occurring event conditions. You can read more about this topic at Wikipedia's ECA-rules article). This can be a complicated subject at first, but the most important take away message going into it is that Rules opens opportunities for site builders and developers to extend Drupal in ways not possible before.
Rules allows you to configure actions to be fired on various events. For example, if a user is creating a new content, the event "Content has been created" occurs. So Rules allows you to react to this event by firing actions. There are a lot of different events available, and contributed modules can even introduce new events. Some more examples of events would be
• a user has logged in
• content has been viewed
• a new comment has been saved
Rules events have nothing to do with calendars. ;)
Rules provides various actions, which let you actually do something. Some examples of actions are
• send a mail to a user
• unpublish content
• delete a comment
So the combination of Events and Actions could read like any of these examples:
- When "a user has logged in", "send a mail to a user".
This section describes how to organize a "sprint" (work party), to work on Drupal (code, documentation, design, etc.). On this page:
- What is a sprint
- Organizing a sprint in general
- Organizing a virtual sprint (IRC)
- Organizing an in-person sprint
- Child pages are for specific types of sprints (code, design, documentation, ...)
What is a sprint?
A sprint is getting people together for a set amount of time – usually one to two days – and just working on some aspect of Drupal. Ideally, participants will learn from others as they go, and the goal is either to get some specific work done, mentor new contributors, or both. We choose to gather in a sprint format because:
- It's fun - sometimes it is nice to have some camaraderie while working.
- It's satisfying - the group can see the progress that was made at the end of the sprint.
- It's a good way to get a focused task done (though some sprints are more general and some are more focused).
- Participants can get their questions answered immediately instead of waiting for an answer in an issue queue.
- Participants can learn from each other.
There are two types of sprints: in-person sprints, where you get everyone together in one room, and virtual sprints, where you get people together on IRC or another online resource (many in-person sprints also have some people participating remotely through IRC). Organizing an in-person sprint is described below, along with some considerations that are common to both types.Read more