Nos acaba de llegar la portada, índice y prologo del nuevo libro de Psicología Comunitaria llamado Psicología Comunitaria y Políticas Sociales: reflexiones y experiencias el cual ya está disponible en las librerías nacionales y en la Paidos (http://www.libreriapaidos.com/9789501245684/PSICOLOGIA+COMUNITARIA+Y+POLITICAS+SOCIALES/) A continuación unas palabras de una de sus autoras Alba Zambrano, Psicóloga de la Universidad De La Frontera (Temuco): La creciente incorporación de psicólogos comunitarios a los programas desarrollados en el marco de políticas sociales plantea nuevas preguntas y retos tanto a los teóricos de la intervención social como a las disciplinas de referencia. Teniendo como foco esas prácticas, Psicología comunitaria y políticas sociales. Reflexiones y experiencias analiza la relación entre la psicología comunitaria y las políticas sociales, compilando la producción de un grupo de académicos iberoamericanos que versa sobre los límites y potencialidades de esta relación en el plano de sus modelos de referencia y sus estrategias. El propósito es recoger enseñanzas y aprender lecciones acerca de las tensiones y límites de esta relación, como sobre el horizonte potencial de un proceso crítico y de colaboración desde esta disciplina en sus vertientes teórica y práctica, integrando planos reflexivos y experiencias generadas desde distintas realidades nacionales y locales. Esta obra está dividida en tres partes. En la primera, se revisan los antecedentes y se exponen las principales líneas de reflexión acerca de las posibilidades que surgen de la relación entre psicología comunitaria y políticas sociales. En la segunda, se reportan y analizan experiencias y prácticas realizadas desde la perspectiva de la psicología comunitaria en políticas sociales de infancia y derechos, asociatividad y seguridad ciudadana, participación social y violencia de género, discapacidad, salud mental, y desarrollo local. En la tercera, se analizan los desafíos formativos y organizativos planteados en las experiencias de trabajo comunitario en el marco de las políticas sociales. Si quieres leer la portada, índice y prologo lo puedes hacer siguiendo el siguiente link http://es.scribd.com/klbun/d/93073074-Psicologia-comunitaria-y-politicas-sociales-Reflexiones-y-Experiencias (http://es.scribd.com/klbun/d/93073074-Psicologia-comunitaria-y-politicas-sociales-Reflexiones-y-Experiencias)

 La Coordinadora de Trabajadores del area social (CITAS) Santiago, los invita al 2° Foro del Ciclo "En Casa de Herrero, Cuchillo de palo: Reforma previsional, Avanza la precariedad laboral", cuyo objetivo es informar y discutir en torno a las consecuencias de la reforma previsional en quienes trabajamos muchas veces ejecutando políticas públicas en precarias condiciones laborales, además de entregar perspectivas para la organización de los trabajadores del área.  Este foro se llevará a cabo el Sábado 12 de Mayo en el Centro Cultural Naitún (Compañía 2820) de las 11:00 a las 14:00 hrs., contando con la participación de CENDA (Centro de estudios nacionales de desarrollo alternativo), Luis Mesina (de la Confederación de Sindicatos bancarios y Afines), y Margarita Peña, Abogada Laboral.  

Drupal.org and its sub-sites (api.drupal.org, groups.drupal.org, etc) will be going down for 20 minutes Monday, May 7, 5:00 PDT (May 8, 00:00 UTC). This maintenance window will be used to upgrade our single sign on system. Please follow the @drupal_infra twitter account for updates during the downtime and thanks for your patience!

Sites will remain functional for the majority of the scheduled downtime, but everyone will be logged out. You may not be able to log into sub-sites for a few minutes as the update is rolled out.

El Plan Nacional de Salud Mental y Psiquiatría (MINSAL; 2000), señala como uno de los desafíos de salud pública la salud mental de la población. El incremento de las patologías mentales junto a las enfermedades psicosomáticas y crónicas se encuentran entre las principales causas de morbi-mortalidad y pérdida de calidad de vida. Chile tiene una de las más altas tasas de prevalencia de trastornos mentales, los estudios epidemiológicos señalan que alrededor del 40% de la población presentará algún tipo de patología en el curso de su vida. Por lo anterior, es que el Plan Nacional de Salud Mental ha privilegiado las intervenciones grupales, ya sea con un enfoque psicoeducativo, preventivo o terapéutico. Por tanto, la presente propuesta tiene su origen en la necesidad de una formación rigurosa en la comprensión y abordaje de los procesos grupales y su relación con el bienestar subjetivo y el aprendizaje. Para ello se hace necesario comprender la relación entre lo subjetivo y lo grupal, así como apropiarse de métodos de análisis e intervención. Todo lo cual facilitaría la coordinación e intervención en grupos, no solo como herramienta terapéutica, sino también como recurso en otros ámbitos, como el educacional y el laboral. Objetivos 1. Distinguir las herramientas conceptúales necesarias para una compresión de los procesos y dinámicas que se presentan en todo grupo. 2. Conocer las diversas expresiones psicopatológicas existentes en la actualidad, considerando las problemáticas sociales y culturales que las sostienen, así como las posibilidades concretas de ser abordadas desde la creatividad y del vínculo psicoterapéutico. 3. Adquirir metodologías específicas para el diseño y la elaboración de dispositivos grupales y de intervención institucional, así como de proyectos de investigación para su ulterior puesta en práctica. Modalidad Presencial. Clases una vez por semana, en horario vespertino Duración Dos semestres Requisitos · Título profesional y/o Grado académico · Entrevista personal Malla curricular I Semestre Epistemología Relacional del campo grupal Módulo 1 Introducción a los Nuevos Paradigmas en Ciencias, los aportes de la Epistemología Relacional: Bases conceptuales de la relación como Teoría Módulo 2 Teoría Vincular y entorno Módulo 3 Campo de Análisis y Campo de Intervención Módulo 4 Historización Crítica y Escuelas del Pensamiento Grupal II Semestre Grupalidad y contexto de intervención: Ámbitos de intervención, aspectos metodológicos Módulo 5 Contexto Actual y Grupalidad Módulo 6 La Intervención y los Contextos Institucionales Módulo 7 Los Componentes de la Técnica para la gestión del Conflicto y la Generación de Redes Estratégicas Módulo 8 Diseño de Encuadres y Dispositivos de Trabajo Grupal. Más información de aranceles y docentes acá (http://elap.uarcis.cl/presentacion-diplomado-en-intervencion-grupal-e-institucional.html)

Drupal 7.14 is now available, which contains bug fixes as well as fixes for security vulnerabilities from Drupal 7.13.

Drupal 6.26, which fixes known bugs (no security issues) is also available for download.

Download Drupal 7.14
Download Drupal 6.26

Upgrading your existing Drupal 7 and 6 sites is strongly recommended. There are no new features in these releases. For more information about the Drupal 7.x release series, consult the Drupal 7.0 release announcement, more information on the 6.x releases can be found in the Drupal 6.0 release announcement. Drupal 5 is no longer maintained, upgrading to Drupal 7 is recommended.

Security information

We have a security announcement mailing list, a history of all security advisories, and an RSS feed with the most recent security advisories. We strongly advise Drupal administrators to sign up for the list.

Drupal 7 and 6 include the built-in Update status module, which informs you about important updates to your modules and themes.

Bug reports

Both Drupal 7.x and 6.x branches are being maintained, so given enough bug fixes (not just bug reports) more maintenance releases will be made available, according to our monthly release cycle.

Changelog

Drupal 7.13 only includes fixes for security issues. Drupal 7.14 also includes bugfixes. The full list of changes between the 7.12 and 7.14 releases can be found by reading the 7.14 release notes. A complete list of all bug fixes in the stable 7.x branch can be found in the git commit log.

Drupal 6.26 only includes bugfixes.

Security vulnerabilities

Drupal 7.13 were released in response to the discovery of security vulnerabilities. Details can be found in the official security advisory:

• SA-CORE-2012-002

To fix the security problems, please upgrade to Drupal 7.13.

What is included with each release?

We made two versions of Drupal 7 available, so you can choose to only include security fixes (Drupal 7.13) or security fixes and bugfixes (Drupal 7.14). You can choose your preferred version. We are trying to make it easier and quicker to roll out security updates by making security-only releases available as well as ones with bugfixes included. We hope this helps you roll out the fixes as soon as possible. Read more details in the handbook.

Known issues

- #1558548: Notice: Undefined index: default_image in image_field_prepare_view() - Upgrading from Drupal 7.x to Drupal 7.14 will yield a harmless but annoying PHP notice. Patch has been committed to 7.x-dev, and will be available in 7.15. A workaround in the meantime is visiting the field settings page and saving.
- #1541792: Enable dynamic allowed list values function with additional context - This issue introduced an more context to hook_options_list(). However, because Entity API was calling this hook directly it causes errors such as Warning: Missing argument 2 for taxonomy_options_list() in taxonomy_options_list() (line 1375 of modules/taxonomy/taxonomy.module).. Fixed in Entity API module at #1556192: Incorrect invocation of hook_options_list().
- #1171866: Change notice for: Enforced fetching of fields/columns in lowercase breaks third-party integration - This issue accidentally introduced an API change that affected both Migrate and Backup and Migrate modules. Solution for Migrate is to rename tables in scripts back to their proper names. Solution for Backup and Migrate is at #1576812: Could not complete the backup.

El Instituto Pikler-Lóczy de Budapest, creado en 1946, para acoger a los bebés sin familia de la post guerra, y que demostró por más de 60 años que los cuidados cotidianos respetuosos y la actividad motriz autónoma evitan los efectos del Hospitalismo y promueven un desarrollo psicomotor sano, ha sido cerrado en marzo de 2011. Hoy sobrevive solo el Jardín Infantil y la sala de Juego Libre, mantenidas precariamente con los aportes de la cooperación internacional. La proyección de ésta cinta busca difundir la pedagogía Pikler y promover un gesto de solidaridad desde Chile hacia el equipo de profesionales del Instituto en Hungría, en reconocimiento a su ardua labor de investigación en primera infancia y formación de las niñas y niños pequeños que ahí residían.   Sábado 12 de Mayo, de 10:00 a 14:30 horas, Aula Magna de la UCINF, Av. Pedro de Valdivia 450, Providencia, Santiago.   Adhesión General: $ 2000. Consultas e inscripciones: redpiklerchile@gmail.com      

The call for papers is still open for DrupalCon Munich -- but only until May 11!  Trainings too! The DrupalCon content team is looking for sessions that cover pushing the boundaries of Drupal and its increasing use as a cross platform system. Help shape what is presented at DrupalCon with this year's theme, "Open Up! Connecting systems and people."

Any proposals for sessions should fit within one of the following tracks:

• Coding and Development
• Community
• Design and Theming
• Business and Strategy
• Site building
• DevOps

To learn more about each topic, view the Session Track page. Here you can find out the anticipated audience and the topic focus, as set forward by each track chair. Selected Sessions and Trainings will be announced May 29.

Curious to learn how sessions are selected at DrupalCon? Learn more about the session selection process.

Core conversations will open for submissions on May 29, read more about Core Conversations on our website.

We are also inviting all organizations with training experience to submit proposals for the Pre-Conference Trainings, to be held on Monday, 20th August 2012.

Open Up - submit your session before May 11!  We look forward to seeing you in Munich August 20-24. Join the Drupal community in Europe this summer and register now for early-bird pricing.

We are thrilled to announce that Google will be sponsoring 13 Drupal projects for Summer of Code 2012. We would like to extend our sincere thanks to Google, who are investing over $72,000 in the Drupal project.

As always, we had many more projects that we would have liked to accept than we were able to. The mentoring team deliberated fiercely over the past two weeks, and arrived at the final acceptance list.

Drupal will benefit from microdata support for contrib field types, help topic module for documentation team, sales reports integration for drupal commerce, materialization plugin support for views, search api statistics etc.

If you would like to keep up to date on Summer of Code happenings, would like to volunteer to help test students' projects, and/or would like to help students as they find their way in our community, please join the SoC 2012 working group and help out in whatever ways you can.

Here's to another great summer! :)

Application Student Mentors Auto Tagging Articles using Semantic Analysis/ Topic Modelling Arjun Kapur Matt Chapman Enhancing Feedback module (D7) Manu Chaudhary Alex Weber Enhancing Secure Code Review Module Udit Jaggi Michael Hess Extend microdata support to contrib field types Anca Dumitrache Lin Clark Help Topic module for the Drupal Documentation Team and for the help system temaruk Jennifer Hodgdon Improving RESTful Web Services Sebastian (sepgil) klausi Materialization Plugin for Views Dhruv Baldawa Janez Urevc Phone / SMS / VoIP integration with Drupal Commons nitech Leo Burd Port Og_panels to D7 and Improve Message notify to make it the source of email notifications sanjay rohila ezra-g Preparing Menu Block Module for Drupal 8 Core Chad Whitman Dave Reid and John Albin Wilkins Sales Reports for Drupal Commerce Christophe Van Gysel Daniel Wehner Search API Statistics Michael Timofejev Thomas Seidl Translation Management Tools Server Sebastian Siemssen Miro Dietiker

               Diplomado en Resolución de Conflictos  y Mediación Comunitaria           (Programa a distacia)     Director del Programa: Enrique Vidaurrázaga Meza.   Magíster en Psicología Social. U. Autónoma de Barcelona. Mediador, docente, e investigador de la Fundación D.C. Barcelona (1998 - 2008). Miembro del Equipo externo de Mediación de la Municipalidad de Barcelona.(2005-2008)   Contenidos   Primer módulo: Conflicto y Mediación Comunitaria: teoría y conceptos fundamentales   - La mediación comunitaria en Chile. - Cultura de mediación y cambio social. - Abordaje psicosocial del conflicto. - Negociación y resolución de conflictos. - Mediación Comunitaria y conflictos urbanos.   Segundo módulo: Metodologías de diagnóstico y de intervención.   - Investigación y resolución de conflictos. - Modelo de Mediación Comunitaria Fundació Desenvolupament Comunitari. - Estrategia de mediación para conflictos en escalada. - Mediación Comunitaria y diversidad cultural    Tercer módulo : Implementación Institucional de la Mediación. Estudio de casos.   - El servicio de Mediación Comunitaria en la provincia de Barcelona. - Descripción de un modelo de intervención comunitaria en Barcelona y su área conurbana. - Los servicios de Mediación Comunitaria. Propuestas de actuación. - Implementación en Chile de centros de mediación para la solución de conflictos comunitarios.   Cuarto módulo: Diseño Proyecto de Intervención. Práctica profesional (optativa)     Aranceles   El Programa tiene un valor de 384.000 pesos. Este costo puede ser cancelado al contado o en un máximo de 12 cuotas (sin intereses) de 32.000 pesos documentadas con cheques a nombre de la Universidad del Mar.   Para alumnos de fuera de Chile el valor del programa es de 690 dólares a pagar al contado vía transferencia bancaria.   Consultas:                       Dolors Sala i Bernabé - Coordinadora Pedagógica.                                                          E-mail:  dolors.sala@udelmar.cl   Ver Programa en:            http://www.udelmar.cl/vina/  (Consultar apartado de Postgrados)    

Drupal.org and its sub-sites (api.drupal.org, groups.drupal.org, git.drupal.org, etc) will be going down for 45 minutes Thursday, April 19, 5:00 PDT (April 20 00:00 UTC). This maintenance window will be used to upgrade our backend media servers. Please follow the @drupal_infra twitter account for updates during the downtime and thanks for your patience!

NOTE: During this downtime window, we will also disable access to the git repositories via SSH. The git:// protocol will still be functional.

Back in 2009, Groups.Drupal.Org (GDO) went through a major transition including upgrading from Drupal 5 to Drupal 6, a redesign, and adding new maintainers. We are currently in the process of a similar transition. The site has already gone through a redesign, and as we make plans to transition to Drupal 7, we will also be moving to new maintainers for the next year.

Making it easier to contribute to GDO

Between the Drupal Association’s initiative to improve *.drupal.org, the community brainstorming on site improvements, and feature requests in the Groups.Drupal.Org issue queue, there is clearly a lot of interest in making improvements to GDO. However, for folks who want to roll up their sleeves and help by filing a patch, the path to replicating GDO for development purposes hasn’t always been clear. As a strategy for making it easier for anyone in the Drupal community to file a patch and streamlining maintenance efforts for the site, we have proposed that GDO will run the Commons distribution of Drupal for Drupal 7. Of course, this means that improvements made to GDO benefit sites powered by Drupal Commons and vice-versa, that generic improvements to Commons will benefit GDO.

New maintainers: Meet Ezra, Scott, and Justin

Helping with this transition, Ezra Gildesgame (ezra-g), maintainer of Drupal Commons, is also now a maintainer of groups.drupal.org. Ezra is the technical lead for Drupal distributions at Acquia, has been contributing to Drupal for over 5 years, and also maintains the Conference Organizing Distribution (COD).

Our other new Groups.Drupal.Org maintainers are Scott Reynen (sreynen) and Justin Toupin (justin2pin) from Aten Design Group. Scott is Lead Developer at Aten and has been contributing to Drupal for over 5 years, including helping to organize the Denver group on GDO. Justin Toupin is CEO at Aten, and has been leading the organization’s involvement in Drupal since version 4.7.

Getting involved: How you can make GDO better

This process of upgrading Groups.Drupal.Org is an especially good time to get involved by joining a few different groups and queues:

• Commons related are the Commons group, and the Commons issue queue for bugs/ideas that affect all Commons sites.
• The GDO issue queue is for features and tasks specific to Groups.Drupal.Org.
• Groups to discuss the site: http://groups.drupal.org/maintenance and http://groups.drupal.org/groups-drupal-org

Note that Ezra, Scott, and Justin have agreed to work on the site for at least a year. If you think you might want to take over in a year, the best way to do that is to get involved working on the site in these issue queues.

Thanks, Greg & Josh!

This is also a great opportunity to thank Greg Knaddison (greggles) and Josh Koenig for their help maintaining Groups.Drupal.Org over the past few years. Josh and Greg found they were too busy with other projects unrelated to community site building which made it harder to find time for GDO (Josh building Pantheon and Greg working with Acquia’s Profesional Services Security Group and the Drupal Security Team). Greg and Josh hope that transitioning to people who spend more of their lives working on community sites will help GDO be an even more valuable collaboration platform for our community.

Hi friends. I'm hoping that you'll support another Drupal community initiative that I've recently dreamed up. All you have to do is add a /drupalgive page to your organization's web site.

Two organizations have published already at http://www.acquia.com/drupalgive and http://www.chapterthree.com/drupalgive. These pages are based on a design by Nica Lorber of Chapter Three. Feel free to reuse this design or just publish a plain listing page. It is better to publish a plain page than none at all. Or use the Feature at http://drupal.org/project/drupalgive.

A /drupalgive page highlights the great work that your organization is doing for the Drupal project. Not only does your organization receive credit for the work you do, but we also nudge other organizations to give back as well. I expect that employees and potential hires from non-contributing organizations will start demanding to give back. This initiative gives those folks something to point to when advocating and educating inside their organization.

Here are examples of appropriate and inappropriate items for a /drupalgive page:

Appropriate

1. A podcast educating folks about great Contrib modules.
2. A link to a significant patch review or commit on drupal.org.
3. A blog post about Drupalish wireframe templates that anyone can use.

Inappropriate

1. An announcement about your latest site launch (even whitehouse.gov).
2. A new video was added to your commercial video subscription service.
3. New features for your paid Drupal hosting service.

Your /drupalgive page should also emit an RSS feed at /drupalgive/rss. We'll add your feed to the new Planet Drupalgive (page, RSS). To get added to the feed, follow the Drupal Planet process. Lastly, please include a link to http://drupal.org/project/drupalgive so that folks can learn more about the initiative.

One simple way to build a /drupalgive page is to add a 'drupalgive' term to your site taxonomy and tag posts with it. Alias the term detail page to /drupalgive and you are done. An alternative is to create a dedicated content type for these entries and a simple View at /drupalgive will show the listing.

Please comment below and lend your support or provide other input.

Está abierta la postulación para la Pasantía Emociones Para Aprender. Este año además del enfoque habitual de Terapia de Juego, tendremos un equipo de trabajo de primera infancia con un enfoque Psicoanalítico y un equipo de trabajo con adolescentes desde una perspectiva Narrativa. Como estas áreas son nuevas, la difusión para ellas ha sido más difícil, por lo que les pido encarecídamente que extiendan esta invitación a todos quienes puedan resultar interesados. El plazo de postulación es hasta el 13 de Abril. Información sobre admisión Corporación MenteSana e-mail: info@mentesana.cl Web: www.mentesana.cl

Bojhan Somers and Roy Scholten are the Drupal UX Team leads.

We believe that Drupal 8 User Experience needs a lot of work to truly make all users of Drupal love what they are working with. We believe that by improving core, we improve the entire Drupal experience for everyone.

How are we doing this? By working with core initiatives, providing ideas, sketches, wireframes, detailed designs, and actively engaging in discussion. D7UX taught us a lot of hard lessons, we now know how to communicate our design rationale more clearly, maintain a UX vision throughout the maze of issues, and empower developers.

What are we working on? We are working on a few initiatives; mobile, blocks & layouts, multilingual and leading a lot of smaller efforts around improving our content authoring and site building experiences.

Drupal 8 design progress so far Content creation

Our content creation experience is still far from being great, but we have been improving the content creation experience from all angles. We have received lots of feedback on our proposals, and iterated with the community on various parts of this experience.

• Research on a interaction model for the content creation page
• Redesigning the Create Content page
• Find content iterations

We have now finalized most of our research activities and we want to start implementing a few of our major ideas. For this to happen, we need developers who want to improve this part of core.

There are two very actionable issues at #1510532: Implement the new create content page design and #1510544: Actual preview of content for you to help out on!

Blocks & Layouts

The blocks & layout initiative started by EclipseGC focuses on solving the messy experience of placing parts (blocks, views, panes) on the page. We believe this can be fundamentally better if we tackle it in core. This initiative will allow us to arrange and organize blocks into flexible layouts through a drag and drop interface. This initiative has many UX components, from finding the right blocks, to selecting the context, to creating mobile layouts.

We have done a lot of research the past few months to understand the space we are designing for. It’s incredibly complex, but will be a huge win if we can provide a great solution straight out of the box.

• Research on pages & components; what are the fundamental concepts?
• Research on context usecases; what are the primary use cases?

We will need help from everyone; developers, designers, user researchers, end users and business owners! Become part of the discussion in the Drupal 8 Blocks & Layouts everywhere initiative group.

UX team activities

UX team bi-weekly office hours

We started to hold bi-weekly UX "office hours" (next one will take place 16 April, 20:00 UTC, 4PM NYC, 4 AM Tuesday Singapore/Shanghai), where we will discuss recent activities of the team but also review contributed modules. This has resulted in modules such as Taxonomy Acces Control making major improvements.

UX team activity

The team has been busy in Q1 2012:

• Becky Gessler, Garen Checkly and Jen Lampton conducted a usability study at the Google offices, resulting in a detailed findings report and Drupalcon Denver core conversation talk on how to solve it.
• Lisa Rex, Dharmesh Mistry (dcmistry), Erik Stielstra (sutha), Alexander Ross (bleen18) have done a total of 22 interviews about how people use the module page.
• Lewis Nyman has been working hard on designing Drupal’s mobile interface, resulting in interesting discussions around navigation, principles and actual implementation of ideas in the mobile issue queue.
• Roy Scholten (yoroy) has presented on Core product: 3 is the magic number and organised several sprints around UX at Drupalcon. There was also a BoF.
• Jared Ponchot has been contributing design proposals, to our effort to redesign the content creation page.
• Kristjan Jansen (kika), Jeff Noyes (Noyz) and Kevin O'Leary (tkoleary), Michael Keara (UserAdvocate) have put out various ideas around media UX, creating UI standards for add/edit flows, optimizing the content listing and research for the Blocks & layout initiative.

We have also released our ideas around redesigning the module page, adding a project browser to core, adding search everywhere, draft revisions and much more in the usability issue queue!

We need your help!

We need volunteers:

• Developers who can help us with the PHP, CSS or JS parts of these changes.
• New and experienced UX designers to work on the new features that we want to introduce in Drupal 8.
• A project manager who can help break down tasks, coordinate contributors, update blog posts and issues, and help the UX team & leads focus more on UX.

If you're interested in becoming a contributor to the UX Team in one of the roles above, contact Bojhan Somers and/or Roy Scholten.

You can find us in in the usability group, contact us directly by e-mail (or drupal.org contact form), join us on IRC in #drupal-usability, or find us in person at Frontend United.

The cool stuff we're working on

Still not sure? We we love a lot more help to pursue all these crazy ideas within the next 7 months:

• Improving the content creation experience. Discussion take place in our design proposal, and implementation is taking place in #1510532: Implement the new create content page design
• Layouts & Blocks initiative, building a drag & drop editor where you can place components, build layouts and manage pages. Discussions take place in the Layouts & Blocks group.
• Mobile administration, Drupal 8 should be great to use on any phone help us in making the administration mobile friendly. Discussions are taking place in the Mobile group

Thanks!

- Bojhan and Roy

AttachmentSize ux_sprinting.jpg55.93 KB

Hello from Jennifer, your friendly Drupal Documentation Team leader! It’s time for a quarterly update on what’s happening in the Documentation team.

First off, I just want to remind everyone that I’m still planning to step down as Documentation Team Leader at the end of 2012. If you’re interested in becoming the co-leader or assistant leader now, and taking over at the end of 2012 as the main team leader, see http://groups.drupal.org/node/203258 for more information. It would be good to find someone soon!

Events

• The Documentation Team is currently holding weekly "Documentation Office Hours"—one-hour IRC meetings on Tuesday afternoon (North American time), open to anyone for questions and discussions about contributing to documentation. This schedule is likely to change soon; join the discussion about a new time for office hours.
• The API documentation cleanup sprint from last quarter has continued into this quarter. The goal is to bring the Drupal 7 and 8 core API documentation much more in line with our documentation standards. To join in, visit the issue page.

Milestones and Accomplishments

• Lots of content was updated on Drupal.org this quarter. Of particular note:
• There used to be a "Community and Support" link in the top navigation of Drupal.org; now there are separate Community and Support links, and the Support page has been completely redone (a redesign of the Community page is also in the plans). Hopefully this will help people new to Drupal connect with the help they need to get started. Thanks to Lisa Rex, David Hernandez, and others for making this happen!
• The Omega theme project organized a group to update the Omega section of the Community Documentation.
• The Media module project organized a group to update the Media documentation.
• An effort is underway to create a Mobile section in the documentation.
• We started a New Contributor Tasks section on Drupal.org. This is a place where people new to contributing to Drupal can go to find meaningful and doable tasks to start with. If you have ideas for the section, there’s a page describing how to add to it (with templates), and a suggestions page too.
• 712 different contributors made a total of 3976 revisions to documentation pages on Drupal.org. Wow! (I have a new statistics page that totals this up). Apologies if your project didn't make it into the list above -- there's a lot going on and I can't keep track of it all!
• Neil Drumm and I (with the help of other patch contributors) are continuing to make updates to the software for http://api.drupal.org. This quarter, there were major improvements to the linking and references features of the site -- check it out if you haven't been there lately! If you would like to work on the API module, check out the issue queue (http://drupal.org/project/issues/api) or find jhodgdon in IRC to get oriented.
• I was given permission to commit Drupal Core 7/8 documentation and coding standards patches in February, and to help out in case of "Core Is Broken!!" emergencies. Hopefully this will lessen the burden on Angie, Nat, and Dries, freeing them up to concentrate on bugs that improve the Drupal software functionality.

Docs Infrastructure

Last year, the Docs Team (or at least its leadership) got a bit discouraged about Documentation infrastructure improvements taking quite a while to get deployed to Drupal.org. But now there's a new process for getting improvements deployed, and Neil Drumm is working on them with hours funded by the Drupal Association. So, I'd like to get us working on improvements to "docs infrastructure" (tools, navigation, etc. for Drupal documentation writers and users) again.

I started working on that this quarter, and several small things were deployed. That went well, so there are now more in progress. Two that we hope to get done soon are a Docs Team effort to have better navigation for Community Docs, and LoMo's project to replace the Books page with a content type/View. Join in the discussion and/or help out!

And as a preview, this summer I would like to really get working on the "curated docs" we've been talking about for a year or more... Watch http://groups.drupal.org/documentation-team for updates!

Next Steps

If you're interested in helping with Drupal documentation:

• New contributors: Check out the tasks in the New Contributor Tasks section, or read http://drupal.org/contribute/documentation to learn all about contributing to documentation. Or come to the weekly office hours (see Events section above) to ask questions and get started.
• Drupal Documentation announcements, discussions, and events are posted on http://groups.drupal.org/documentation-team and on Twitter (@drupaldocs).
• API documentation cleanup sprint (for programmer-documenters): http://drupal.org/node/1310084
• Work on the API module: http://drupal.org/project/issues/api

As announced on stage at DrupalCon Denver, we have just opened the Call for Papers for DrupalCon Munich 2012, as well as keynotes, call for trainings, scholarships, and registration. The Drupal Association and the Munich DrupalCon committee have been preparing for the next DrupalCon for months now. Things will move into high gear once DrupalCon Denver closes its doors, later this week.

Announcing ...

Keynote speakers

DrupalCon Munich announces three keynotes by open source and industry visionaries, including Dries Buytaert - the founder of the Drupal project talking about the future of Drupal on Tuesday, August 21; Anke Domscheit-Berg, a renowned expert in open government and open data, speaking on Tuesday, August 22; and Fabien Potencier, CEO of SensioLabs and founder of the Symfony project speaking on Wednesday, August 23.

Call for papers

Your contribution is needed! Come to Munich and share your expertise with the most amazing open source community in the world. Submit your session ideas at http://munich2012.drupal.org/call-for-papers

Early Bird registration opens today!

Registration for DrupalCon Munich is now open. The special early-bird rate is €350 for the first 300 tickets, after that the price is €400 until June 15, and 475 until July 31. Late registration after this date until August 17 will be €525. On-site registration will be €575. The is a limited number of tickets available at a rate of €200 for students and non profit organisations (all prices inclusive of VAT). Register now at http://munich2012.drupal.org/register.

Call for trainings

The Drupal project needs more contributors, site builders, users, and developers. We’re looking to cover the gamut from beginner to highly advanced trainings. Trainers and training companies, submit your trainings now! http://munich2012.drupal.org

Scholarship applications are now open

Drupal is for everyone and everyone can enrich the project. If you would like to come to DrupalCon Munich but cannot afford the cost, a limited number of scholarships will be available. Submit your application at http://munich2012.drupal.org/community/scholarships

Keep up-to-date with all things Drupalcon Munich; follow @DrupalCon on Twitter.

-- Florian Lorétan (floretan) and Karsten Frohwein (kars-t), co-chairs of DrupalCon Munich

Some of Drupal's Summer of Code success stories include:

Angela Byron (webchick) the Drupal 7 co-maintainer, Director of Community Development at Acquia, a Google-O'Reilly Open Source Hall of Famer and a Drupal Association board member. She originally got her start in Drupal writing Quiz module for GSoC 2005. Sumit Kataria, started as a GSoC student back in 2009 working on OAuth module, and now not only is one of the foremost experts in the Drupal community on mobile (look for his mobile apps for DrupalCon Denver in an app store near you!), but co-manages Drupal's involvement in GSoC. He works as a Drupal consultant with companies like CivicActions and Lullabot. Bojan Zivanovic (bojanz) became a preeminent contributor to views and contributed to EntityFieldQuery for Drupal 7. Gábor Hojtsy, the co-maintainer of Drupal 6, and the Initiative Lead for the Drupal 8 Multilingual Initiative worked over GSoC in 2006 to get i18n in Drupal core in Drupal 6. He is now an engineer for Acquia. Jimmy Berry (boombatower) was instrumental in the development of Drupal's automated testing framework, and he and his father Jim Berry (solotandem) were the first Google Summer of Code father/son team! :) They both offer testing-related services at http://boombatower.com. Lin Clark (linclark) created SPARQL Views, making it possible to query SPARQL endpoints from Views, as part of GSoC 2010. Her demonstrations of Linked Data capabilities in Drupal have been published on IBM Developer Works. She is now an independent consultant working data publishing and consumption using Drupal.

So if you're:

• a post-secondary student looking for an exciting project with a thriving development community and tons of smart people you can work with
• an existing Drupal contributor who happens to be attending college/university and would love a chance to get paid over the summer to work on the "Next Big Drupal Thing"
• a seasoned Drupal developer with some time over the summer, who'd truly enjoy mentoring and helping the next generation of contributors make Drupal the best that it can be
• a Drupal community member who might not have the time or coding experience to mentor, but knows where to find resources and enjoys helping others find them.
• someone with a great project idea for an improvement in Drupal that would be perfect for a student to work on over the summer
• a Drupal evangelist who wants to help grow the community by actively engaging students

...then there's something for you in Summer of Code! Read on to find out more.

Prospective Students

If you have enthusiasm the drive to work on something great, now is the time for you to get started! Subscribe to the Google Summer of Code group, look over the developer's guide and API reference, stop by Core Office hours and take on some new contributor tasks, find a Drupal event near you to get to know Drupal's amazing community, and take on a few bite-sized tasks in the Novice Issue Queue.

Most importantly, start thinking about your project proposal! Prior to submitting your application, stop by #drupal on irc.freenode.net or post your project ideas to the Summer of Code 2012 group to get community feedback. Your chances of getting into Summer of Code increase if the community has the opportunity to review your ideas and offer feedback to help you in improving your project idea.

We have already started accepting applications. For more tips, students should check out the Student Template Page.

Mentors

Please sign up to be a mentor if you have either experience with Drupal development or expertise in a particular area of interest (for example, newspapers, education...) and have some free time from now until the end of August.

To become a mentor,  join the Drupal SoC-2012 group and the sign up on Google's SoC mentor web app (now known as Melange). Please describe who you are, what your level of Drupal experience is, and your motivation for being a mentor. Your application will be reviewed by SoC admins (Chx, SumitK).

You can go through Advice for mentors page to find more tips on mentoring students.

The more mentors we have, the more students we can get in, and the more exciting projects of varying types we can accept.

Community members

Great project ideas are vital to attracting both great students and great mentors. If you've ever thought "if Drupal could be...", now is the time to turn it into a project idea. The project should be feasible for a Drupal-novice developer student to achieve in a 3-month time frame. Suggest a SoC project idea in the SoC 2012 group or help elaborating already proposed ideas

In addition, you can help review the existing SoC project ideas by providing students and other community members with feedback. Community members are in the best position to help students understand the finer intricacies of existing modules, and help their energies to meet the the priorities of the Drupal project.

To help the new Drupal family members, we need some existing community members to be active in #drupal-contribute on irc.freenode.net to answer student questions, point them to the correct resources, and people with expertise.

If you think this sounds like fun, be sure to get on to IRC!

Estimadas y estimados, este año la Universidad ARCIS de Valparaíso impartirá el Diplomado en Enfoque Comunitario y Trabajo de Redes (http://elap.uarcis.cl/presentacion-diplomado-en-enfoque-comunitario-y-trabajo-de-redes.html), cuyo objetivo principal es: Desarrollar conocimientos y habilidades del trabajo en Red, potenciando de esta forma las competencias laborales de los profesionales que actualmente trabajan en Intervención Psicosocial Este responde a la constante necesidad de capacitación y actualización de los equipos psicosociales en su amplio espectro de intervención, que ven en este enfoque y en el trabajo coordinado y colaborativo en red una fortaleza para poder llevar a cabo sus objetivos. Es así como se ha estructurado el proceso de formación en la profundización de contenidos propios de la Intervención Comunitaria, la Teoría e Intervención Social, vinculado a un proceso formativo en una visión de trabajo con grupos y técnicas de trabajo comunitario, todo ello sumado a la formación en procesos de sistematización de nuestras practicas que posibilitan el desarrollo de mejores diseños, planificaciones y evaluaciones de nuestras propias intervenciones. Esta dirigido a profesionales, y también a todas aquellas personas que por interés y trayectoria desean profundizar en este tipo de conocimientos, que sedesempeñen en diversos campos de la intervención psicosocial ya sea en instituciones publicas o privadas con y sin fines de lucro, pero que desarrollan como norte de trabajo la superación de las condiciones de vulnerabilidad de gran parte de nuestra sociedad. El valor del diplomado es de 755.000 pesos y la matrícula tiene un valor de 40.000 pesos. Existen diversos descuentos para grupos, instituciones y estudiantes egresados de esta Universidad.el diplomado se comenzará a dictar durante la segunda quincena de Abril y la primera semana de Mayo, con el objetivo de poder atender a todas las consultas necesarias, el horario de funcionamiento sera los viernes por la tarde y los sábados por la mañana. Para mayores antecedentes pueden preguntar al correo kentyicheung@gmail.com (mailto:kentyicheung@gmail.com ), o bien a la ejecutiva de ventas de la universidad: Daniela Brito, correo dbrito@uarcis.com (mailto:dbrito@uarcis.com) o a los fonos 02-3866646 y 76703806

Why Drupal was chosen: 

After considering the landscape of both proprietary and open-source solutions, Symantec decided to use Drupal as a foundation for their community initiative. Symantec recognized Drupal to be offering:

• a wealth of out of the box CMS and social media features and functionality
• the ability to scale for high usage sites
• the theme and development flexibility to customize the user experience quickly without the typical lag they had experienced requesting new features from proprietary vendors
• a recognized developer community from which to draw quality development talent

Symantec’s internal UX team even installed and configured rough prototypes in Drupal leveraging the vast library of existing contrib modules to experiment with various use cases for the upcoming project. This ability to rapidly create functional prototypes further cemented the choice of Drupal as the platform for development.

Completed Drupal site or project URL:  http://www.symantec.com/connect/

Symantec Connect is an enterprise class, community-driven, social business support and information portal for Symantec products, offering users of Symantec’s deep catalog of applications and services a platform to interact with one another and Symantec employees through rich web-based tools. Connect enables the rapid publishing of information about the day-to-day use of Symantec products through key community-centric features which facilitate the customer’s ability to:

• Ask the community for help with issues and flag solutions when they are posted for easy discovery in the forums
• Suggest and vote on product enhancements
• Publish helper applications and scripts as community downloads
• Publish user-submitted screencast videos for enhanced knowledge sharing
• Build online/offline product centric user groups with events, private content publishing and messaging in the groups
• Keep up with content on a variety of topics within the IT and security-related fields through articles and blog entries
• Enjoy a highly qualified community experience enabled by a suite of Symantec employee moderation, organization, and publishing controls.

All of these features also empower Symantec employees to quickly publish official versions of forum discussions, blog entries, articles, events, downloads, and videos while moderating and vetting content, helping steer the community in the right direction.

Describe the project (goals, requirements and outcome): 

A Brief History

Symantec, founded in 1982, is one of the world's largest software companies with more than 17,500 employees in more than 40 countries. The company provides both security and storage and systems management solutions. Their customer base includes consumers, small businesses, and some of the world's largest global organizations. The company's phenomenal growth can be attributed to a combination of market acceptance and strategic acquisitions.

In early 2008, Symantec's Customer Experience team began crafting a roadmap designed to consolidate several existing support and discussion sites into a consistent, best-of-breed community offering. The goals of this consolidation were to:

Give Symantec customers a single point of contact where they could engage with the company's support, marketing, and product management teams,
Draw on other customers experience and expertise,
Reduce the support and licensing costs of maintaining a collection of disparate community offerings.

Modules Key modules used:  Content Construction Kit (CCK) Views Apache Solr Search Integration Why these modules were chosen:  Solr allowed faceted searching of forum results to indicate their state in the search results. Community contributions: 

n/a

Team members:  jeffrey.dalton Project team: 

The project was structured to allow Symantec Customer Experience team to provide input on the design and planning of the site while collaborating with a group of Drupal experts. Symantec’s internal team is augmented with Drupal expertise in the key areas needed for successful Drupal development.

• WebWise Solutions Inc. leads Connect’s project development and is the principle contact on the project providing long-standing expertise in Drupal-centric project management and user community development. WebWise handles all day-to-day operations and oversight of everything from server deployment to administering the rewards system and offering a first line of customer support for the site’s users, all of which enables Symantec to focus on utilizing Connect to serve their customers instead of having to worry about maintaining the platform.
• Tabs & Spaces Inc. brings the heavy lifting of custom module development creating upwards of 50 custom modules to augment and extend Drupal to meet the unique needs of building a customer support community around a deep catalog of products and services.
• Jeffrey Dalton Design Inc. adds the “hot sauce” of user experience centered design and theme work leveraging Drupal’s powerful theme system to tailor the interface to the specific needs of the community. After the initial launch the redesign process allowed Jeffrey Dalton Design to fully invest in re-visioning the theme and leveraging user feedback collected throughout the initial months of Connects operation. During this process the Symantec Corporation even went through a brand change of their own which was easily rolled into the new theme.
• Tag1 Consulting delivers the performance and scalability tuning that is essential for Drupal sites with millions of users. With multiple layers of content caching in multi-server configurations, world class scalability expertise allows Symantec Connect to continue it’s rapid growth in a high demand environment.

This augmented team approach allows for rapid expansion of area-specific development expertise when new features and functionality are requested while minimizing Symantec’s development overhead.

Why Drupal was chosen: 

Made with Drupal 5 this site is still an awesome example of successful implementation. The owners of this site are not going to upgrade it until D8 is in production. We are looking forward to "the migration" case study then!

Completed Drupal site or project URL:  http://www.popsci.com/

In February 2008, Popular Science, the fifth-oldest continually-published monthly magazine, relaunched its online presence with an enterprise-level website developed by pingVision, powered by Drupal.
http://drupal.org/node/233090

Describe the project (goals, requirements and outcome): 

Until the year of relaunch, Popular Science's online presence was dominated by proprietary web content management solutions. With this relaunch, the Popular Science team wanted to take the online presence of the magazine into the open source world.

Website Goals and Challenges

Prior to its relaunch, the Popular Science website used various different systems to deliver content. One of the goals for the new site was to bring these disparate sites together into a unified user interface while increasing usability and functionality. Drupal's inherent flexibility and extensibility afforded the delivery of Popular Science's usability and functional requirements. One of the big challenges, however, was converting and importing several years' worth of content from a Vignette 7 CMS and several TypePad blogs.

Another challenge was the integration of several third-party services, including a fantasy stock trading system, video conversion and hosting services, and advertising.

In approaching the development of the new PopSci.com, we took advantage of various contributed modules, and created a number of custom modules, including the Drupal Markup Engine for content placement within nodes and Node Carousel for displaying content.

Finally, scalability was a primary concern, as PopSci already had a large and active user base. By specifying a load-balanced multi-server cluster to serve up the site, combined with the use of Memcache, PopSci.com post-relaunch was able to weather an average load of 60 pages per second with a spike of over 1.1 million page views in 24 hours -- a new record for Popular Science.

Content Types

It was important to the PopSci.com editors that they have complete control over the placement of media and supporting content not only in full node view but also in teaser view. They wanted the ability to paginate long articles and place any number of images or even related blocks into the content of a node. The media placement also needed to be intelligent enough to work with legacy content imported from Vignette and Typepad. Most of this was accomplished with the creation of a new module called the Drupal Markup Engine, or DME. The DME works in conjunction with the content-types that were created for this project with the Content Construction Kit (CCK) by providing a custom, extensible input filter.

Articles

Articles are the main content-type on the site. All blog posts from TypePad and articles from Vignette were consolidated as articles in Drupal.

The article content-type uses the DME extensively. Referenced images can be placed anywhere in an article using the DME. If a referenced image node isn't specifically placed within the content body by the DME, it is automatically displayed at the top of the article and in the article's teaser view.

Images may also be placed directly in the teaser using the DME. This approach provides maximum flexibility with images entered through Drupal and with images from legacy content, which required no human intervention to make the latter work.

The DME is also used to place a related content block (containing links to nodes in Node Reference fields or nodes with similar taxonomy terms) into the content and to set pagination for the article.

Article Structure

• Article Images -- Node Reference to images used in the article.
• Associated Photo Gallery -- Node Reference to an Photo Gallery.
• Body -- The article's body.
• Category Badge -- A taxonomy image that will apply a graphical badge to the article.
• Credit -- The credit is the contributor of the article.
• DEK -- A brief description of the article.
• Primary Category -- The primary taxonomy for the site represented by the main navigation areas.
• Related Articles -- Node Reference field to relate other articles.
• Tags -- An auto-fill taxonomy field.
• Title -- Core title field.
• V7id -- The Vignette 7 ID of the original article so that it can be cross-referenced. This was useful for redirecting old urls to new Drupal content. [See discussion about imports below]
• Video Link -- Node Reference to related videos.

Current Issue

The "current issue" node type represents an issue of the magazine. It is used to store images of the magazines cover associated with dates. This node type is used in various promotional content throughout the site.

Current Issue Structure

• Cover -- An image representing the magazine cover.
• Issue Date -- Publication date of the issue.
• Title -- Core title field.

Featured Tout

The Featured tout is a node type created to be used solely in a Node Carousel driven by a Node Queue. The featured touts simply require the Popular Science editors to create graphics that are of the appropriate dimensions. These can be seen on the front page of http://popsci.com/.

Featured Tout Structure

• Associated Article -- Node Reference to the article being touted.
• DEK -- A brief description of the article being touted.
• Index Display Link -- The word used as the link in the tout.
• Title -- Core title field.

Images

Images are used extensively on the site and needed to be invoked in a number of ways. Images are used in different forms in articles, teaser widgets, and photo galleries. If an image has related content, links to that content are shown in all but teaser views. Images are not served as stand alone images on the site but are invoked in Articles and Photo Galleries.

Image Structure

• Credit -- The contributor of the image.
• DEK -- A brief description of the image.
• Photo Gallery Link -- Node Reference to Photo Galleries. If an image references a gallery it shows up in that Photo Gallery.
• Photo Gallery Weights -- This field contains a series of number pairs with each pair representing the photo gallery and the image's weight in that photo gallery.
• Primary Category -- The primary taxonomy for the site represented by the main navigation areas.
• Title -- Core title field.
• V7id -- The Vignette 7 ID of the original image so that it can be cross-referenced. This was useful for redirecting old urls to new Drupal content.
• Video Link -- Node Reference to related videos.

Photo Gallery

A Photo Gallery is a node type serving to collect image nodes and content to be displayed to the end user as a photo gallery. The images are designated for a photo gallery by editing the image and entering the gallery title in the appropriate Node Reference field. Galleries are presented as Node Carousels to give them a slick, interactive feel.

Photo Gallery Structure

• Category Badge -- A taxonomy image that will apply a graphical badge to the image.
• Credit -- The contributor of the image.
• DEK -- A brief description of the image.
• Icon -- A Node Reference field to the image to use when viewing the gallery in teaser view.
• Primary Category -- The primary taxonomy for the site represented by the main navigation areas.
• Tags -- An auto-fill taxonomy field.
• Title -- Core title field.
• V7id -- The Vignette 7 ID of the original image so that it can be cross-referenced. This was useful for redirecting old urls to new Drupal content.

User Video

The Video node enables posting of video to either YouTube or OnStream. We developed a custom media module, which creates a custom Media Profile CCK field that can be attached to any node, allowing editors and admins to restrict the services used on a per-content-type basis.

The custom media module differs from the existing emfield module by offering greater flexibility -- such as allowing users to upload videos to the services straight from Drupal.

Video Structure

• Category Badge -- A taxonomy image that will apply a graphical badge to the video.
• Credit -- The contributor of the video.
• DEK -- A brief description of the video.
• Primary Category -- The primary taxonomy for the site represented by the main navigation areas.
• Tags -- An auto-fill taxonomy field.
• Title -- Core title field.
• Video Link -- A hosted video handled by an extension to the media module.

Data Import

Part of the motivation to move the existing content over to Drupal was to escape the rigid complexity and cost associated with the Vignette CMS. The Vignette dataset was a 1.66GB Oracle database -- and that didn't include the more than 15,000 images referenced in the Vignette data which also had to be imported into the new site.

The first step in the migration process was to use the MySQL Migration Toolkit to transfer the data to MySQL. We wrote a custom module that used cron to feed the Oracle data through Drupal's APIs in manageable chunks. And finally, we imported the images by extracting their locations from the Oracle data and, via shell script, executing a series of wget commands to download the images.

As each piece of content was created in Drupal it was tagged with the Yahoo Terms module, which despite some odd results provided a good start on tagging the immense amount of un-tagged Vignette data.

Once the preparations were in place, the entire import process took approximately two solid days of execution time to complete.

A portion of the import process centered around how to deal with the urls that had been generated by Vignette, so that an article called up by its old Vignette address could be found in the new Drupal architecture. In order to accomplish this, during the import we took the associated Vignette ID for each unit of information imported from Vignette into Drupal and placed it into a CCK field in its destination node in Drupal. To actually find those articles in Drupal, a hook was written that works with the Custom Error module to look for the old Vignette ID in the url when a 404 occurs and issues the correct redirect code. Not only were we able to handle the redirects while historic links were used, but in a very short time Google had updated their search results showing the new paths.

Search

The design of the PopSci search results required the search results to be grouped by content type, with tabs allowing re-sorting of the results by Most Relevant, Most Recent, Most Viewed, Top Rated, and Most Commented. On top of that, users needed to be able to subscribe to rss feeds of the results.

We achieved this functionality by developing an extended version of Drupal's core search, displaying the various results in blocks of paginated content, with AJAX tabsets to access other sortings of the results.

Each search is also cached, given a hashed id, and associated with the user performing the search to allow the saving the searches for future reference.

AJAX Tabs

In many instances the design comps we received required a nested set of tabs that could function to filter the content being displayed on a particular page. This was largely handled by the Tabs component of the Javascript Tools module. However, the large tabbed datasets displayed on each of the main category pages and in searches needed to be a custom coded solution to be able to work in a responsive fashion with larger amounts of data.

Performance

Naturally, there is a hefty selection of hardware powering the Popular Science website, but the true performance winner of this project was the Memcache module which integrates Drupal with Memcached and the PECL Memcache library. Out of the box, this module worked extremely well for us, with the exception of path aliases: A full page load was generating as many as 700 queries to determine path aliases. Pulling these queries through Memcache gave us the speed we needed to maintain an initial average load of approximately 60-70 page views per second.

Modules Key modules used:  abuse Avatar Approval Custom Error jQuery Update Pathauto Update Status URL list Account reminder LoginToboggan Content Construction Kit (CCK) Date Fivestar ImageField Link AdSense API Coder dba views Devel Javascript Tools SimpleTest Filter by node type HTML corrector ImageCache Taxonomy Image CAPTCHA Import Typepad / MoveableType Memcache API and Integration Omniture Integration Service links XML sitemap Yahoo Terms Mime Mail Send Nodecarousel Nodequeue Sitemap Views Views Bookmark Meta tags Scheduler SimpleMenu Token Voting API Why these modules were chosen:  These modules were chosen to be able to reach demanded functionality. All of them are stable and proven by the community. Community contributions: 

Unknown. Some of the customizations and adjustments would (were?) be contributed as modules for Drupal 6.

Team members:  AjK alasda cyberswat coltrane ezra-g greggles gregnostic jcfiala laura s matthews skywalker2208 3goose Zarabadoo Project team: 

Katherine Lawrence http://drupal.org/user/42890