Austria

Wie wärs mit einem Drupal Stammtisch in Wien? Besteht Interesse? Ende August oder Anfang September noch vor der Drupalcon wäre nicht schlecht. Gibt es Vorschläge für die Location? Was erwartet Ihr Euch von so einem Stammtisch?

chris

I'm glad to announce development of a buddylist 2.x module. Our team needs buddylist's functionality for a project, but decided that buddylist's (1.x) quality is too bad for use in our project and that the effort to fix it wouldn't be worth the trouble. So we'll build buddylist 2.x..

Buddylist 2.x design decisions:

• use views (for now with usernode..) for all buddy listing, so they are
  extensible and customizable
• use workflow-ng for all notifications, which provides e-mail notifications - or whatever you want (just write the appropriate action..)
• to simplify only the buddylist modus with "Confirmed buddies" will be
  supported - no one-way buddy connections
• only implement the basics in the module, other things should be built as add-ons.
  So there will be no buddy-group functionality, or tracker integration (for
  this views can be used nevertheless).
• we have also planned to develop an extension, which shows the shortest
  buddy connection to other people later
• Probably there will be no need for changing the db-scheme. So
  upgrading would be just a matter of replacing the module.

So in short the pros/cons of this design will be:
+ small, stable, performant module
+ good code reusing
- a lot of dependencies (views, usernode, worfklow-ng for notifications)

development will be done by nodestroy

I'm happy to announce the 1.0 beta1 release of workflow-ng.

Workflow-ng allows one to customize drupal's built in workflows in a very flexible way.
In short, it's a rule-based event driven action evaluation system. Read the introduction to see how it works.

It is useful for

• sending customized mails notifying your users about important changes
• building flexible content publishing workflows
• creating custom redirections
• and a lot more....

After some hard work, the workflow-ng API is ready.

It features

• actions, which may be configurable
• conditions, which may also be configurable
• support for multiple arguments, for actions as well as for conditions
• condition evaluation with logical operations like OR, AND and NOR
• events, for which conditions and actions can be configured. They may be contributed by modules.
• dynamic loading of needed arguments
• ordered conditions and actions - they are evaluated like they are ordered
• form API style configuration and processing of conditions and actions

So workflow-ng works event based. (And no, I'm not talking of calendars ;)
E.g. workflow-ng defines some basic events for drupal core, like 'node update, 'node insert', 'user update' and so on. So this are the events you can react on by defining conditions and actions for them.
What makes workflow-ng powerful is, is it's flexible handling of arguments. Each of these events has to define a list of available arguments. Then any conditions and actions, that can work with these arguments, can be configured for this event. So an action can be used in any situation, where the suitable arguments are available. There is no need for the action, to be coded aware of every event.. :)

As modules may define further events, this enables module authors, to easily allow site administrators to customize the behavior by just defining some further events.

Read more at http://more.zites.net/workflow-ng-api-ready

I just uploaded my application to Google's Summer of Code web app, and I can say I'm quite proud of its current state. The application has seen a couple of iterations based on valuable feedback by Adam Light and Derek Wright, both of which are working on RCS stuff for the Project module. Being fed into Google, this means that the Drupal mentors can now place private comments and supporting votes there.

Given that there are a good number of comments on some of the other proposals in this group, I'm still wondering if there is something I can do to spread the word and get more input from the greater public. After all, work on the Project module severely affects the great majority of drupal.org users, and getting rid of CVS as a hard dependency should really be discussed in the wider community. So do communicate your opinions about my application, its benefits for Drupal, its chances to get elected, its shortcomings, challenges, etc. ...I'm listening.