Working group

This is our Drupal group to grow the newsletter in the Esperanto movement.

Interesaj ligiloj:

• http://drupal.org/project/Translations
• http://drupal.org/node/11130

Drupalo estas senpaga sistemo kun libere disvastigata kodo (vidu licenzon GNU) por facile krei dinamikajn retejojn kaj subteni/administri ilin. Por komenci uzi ĝin ne estas bezonataj specialaj scioj en programado kaj interretaj teknologioj.

• What Drupal can learn from RoR: Naming conventions? Ease of use? Speed of development? There is loads of stuff that has little to do with the environment, programming language or other technical thingies. But this stuff is very interesting to use in Drupal. Test Driven Development, Rapid prototyping, extreme conventions, just to name some buzzwords.
• ... and why RoR not the evil competitor. If we can learn from it, it helps us. And in fact RoR is used for entirely different situtations often, then Drupal. Lets see how we can get the "STFU about RoR" out of the Drupaleers. PHP is not evil. Ruby is not evil. Rails is not evil.

This group was started as a result of a presentation at Barcamp Brussels. We discussed that the current solutions focus too much on the exercise and not on the concept of learning which happens best in a motivating community of learners and teachers in many languages.

This group works on internationalization issues, like making it possible to translate menus, nodes and taxonomies in Drupal. This includes everything from process and workflows, to actual code issues or optimizations required. The Translations group is where to go if you are working on translating Drupal core or contrib modules.

A discussion area for people working with sites for the scouting/guiding movement

A major pain in the butt for many developers is that their patches never gets reviewed (me included), therefore this group was created. It's purpose is to help people to make reviews, to coordinate reviewers, share experience and a place for review exchanges (i.e. I'll review your patch if you review mine).

Useful links;
http://drupal.org/node/10261 - The revision process

http://drupal.org/node/10262 - Criteria for evaluating proposed changes
http://drupal.org/node/318 - Coding standards
http://drupal.org/patch/review - Tips for reviewing patches

Welcome to the Groupware group. The purpose of this group is to focus on discussing, planning and implementing a groupware solution using Drupal. All interested parties should congregate and add their input. Groupware, as Collaborative Working Environment (CWE) is the modules, contents and settings that can be used by a group of people who are co-working on the same information or knowledge space.

Welcome to the Drupal churches group. This is a group centered around building Church websites with Drupal and a point for members of The Church to go out into the Drupal community. In this group we discuss how to use Drupal, modules to use, integrating other services with Drupal, and the ins and outs of building Church websites.

The Drupal church community extends beyond this group. You can find more information and help in the IRC channel #drupal-churches on irc.freenode.org and on the Geeks and God podcast website.

• Ask questions about how to use Drupal for advocacy, fundraising, online or offline community organizing, and more

• Feature your case study of using Drupal for good

• View resources on Drupal and activism/organizing/nonprofits, including distributions/module reviews, case studies, and notes from previous meetups.

Sure, Benchmarks have their drawbacks. But they are very useful for certain types of testing. For example we can do a standard stresstest on the latest stable version of Drupal versus CVS and see where we have to gain speedwise. Or see the influence of modules and or themes on the speed of Drupal. And we can use it as well "against" other CMS'es.

Lets first come up with a standard scenario for testing that can be ported in time an place on different hardware and OS. Once we have established that we must make some decisions on standard ways of reporting and how to communicate to whom. Some reports might be for the developers, others for marketing.