10 sessions in media related field for the next DrupalCon in Paris and more to come ? Please help to choose

Foreign Affairs is the journal of the Council on Foreign Relations, a non-partisan member organization dedicated to improving the understanding of U.S. foreign policy and international affairs through the free exchange of ideas. Since its inception in 1922, articles and essays published in Foreign Affairs have helped shape political debate and policy on some of the most important issues of the day. Authors who have written for the journal have included influential intellectuals and political leaders ranging from W.E.B. DuBois to Henry Kissinger to Hillary Clinton.

This session will explore how the new Foreign Affairs Web site, which was developed by Palantir.net and launched in March 2009, showcases Drupal’s wide variety of capabilities. In addition to leveraging existing modules, the site features a significant amount of new functionality developed for the site and contributed back to the Drupal community.

Material covered in this presentation will include:

• Developing a custom import system that processed 60 years worth of existing content for integration into the new site.
• Making that content easy to navigate so that users can find articles, essays, and book reviews by a variety of categories, including date, region, topic, and author.
• Seamlessly integrating 150,000 subscribers from several different authentication sources into the new site.
• Developing a tiered access scheme that enables Foreign Affairs' paid-content model while still providing free access to their latest content.
• An IP address-based access system that allows users from institutions with existing site licenses to access premium content without having to log into the site.
• E-commerce gateway integration that allows visitors to purchase PDF reprints of past articles, subscribe or renew a subscription to the print edition, and manage their own account information online -- all within Drupal.
• Integration with multiple analytics and advertising systems as well as Google Search Appliance.
• A Drupal deployment framework that allows data to be securely and reliably transmitted between development, staging, and production servers. This includes content (nodes, taxonomy, users, etc) as well as configuration (views, content types, system settings, etc.).

Quite a a loot of comments on http://paris2009.drupalcon.org/session/foreign-affairs-case-study

got a ticket for this really looking forward to it..

Jill xx

http://www.firstbathrooms.co.uk

Interesting project, quite a large challenge. I'm curious how everything went.

Regards

- online adverteren rick

A real-world presentation on how to bulletproof your Drupal development process with EC2, Hudson, Simpletest, Selenium and JMeter
Austin Smith, David Strauss, Josh Koenig and Moshe Weitzman present real-world lessons learned and practical how-to examples for creating a robust Continuous Integration environment for enterprise-level Drupal development.
This talk will briefly explain the concept and value Continuous Integration (CI), but focus primarily on the nuts and bolts challenges and techniques of getting a CI environment working with Drupal. The touchstone for our presentation is a case-study of the infrastructure developed by The Economist Group (economist.com) to utilize four teams in five timezones from London to California to effectively collaborate on developing a complex, high performance Drupal application.
Specific topics we will cover include:

Please comment http://paris2009.drupalcon.org/session/continuous-integration-and-drupal
Esdaniel on June 24, 2009 - 16:43.

  <p>This is a session I'd hate to miss, good to see the best practices getting some limelight!</p>

The Economist describes its decision to migrate to Drupal and the changes this has brought about
Track: Business development and strategy
Session Type: Panel
Level of expertise: Beginner
Language: English
The Economist was founded in 1843 to take part in “a severe contest between intelligence, which presses forward, and an unworthy, timid ignorance obstructing our progress”. In 2008 Economist.com undertook the mission to move from a traditional online magazine publishing model and build the 'foremost destination online for analysing and debating the global agenda, drawing on the intelligence of journalists, readers and guests'.

Economist.com, initially launched in 1997, was conceived largely as an online companion--offering the weekly newspaper to subscribers plus daily 'web-only' news analysis. Since the new strategy was adopted a new online debate product was launched, the ability to comment on articles was rolled out site-wide and basic reader-profiles were introduced.

In the past year European page views and unique visitors to Economist.com have mirrored worldwide growth averaging year-on-year increases of 44% and 34% respectively. In addition newspaper circulation worldwide and in Europe grew during this period. Given the successful change in strategy the decision was taken to reorganise Economist.com and replace the proprietary CMS (and other proprietary technologies) with an open publishing and community platform to enable rapid product development and foster innovation.

In the past year European page views and unique visitors to Economist.com have mirrored worldwide growth averaging year-on-year increases of 44% and 34% respectively. In addition newspaper circulation worldwide and in Europe grew during this period. Given the successful change in strategy the decision was taken to reorganise Economist.com and replace the proprietary CMS (and other proprietary technologies) with an open publishing and community platform to enable rapid product development and foster innovation.

This case study will discuss:

The change in strategy that necessitated technology and organisational change
How and why The Economist chose Drupal over competing open-source and commercial software packages
The commitment that The Economist is making to the open-source community and how this is good for business
granting 20% of employee-time for open-source work
commitment to release all modules back to the community
How and why The Economist chose Scrum/Agile for software/product development and organisational change--and how this is ideal for working with Drupal
How The Economist took a collaborative and innovative approach towards working with partners to build the new Economist Online
employing vendors with deep roots in the Drupal community
forming non-traditional fully-agile contractual agreements
creating scrum teams with internal staff and external vendors
Successes and failures to date as well as future plans for publishing and community development. These include:
launch of drupal community features within a legacy system
migrating user-accounts and profiles fully to Drupal
public-beta of new article pages
Co-presenters

Ben Edwards
Publisher, Economist.com
Executive Vice President, Economist Group

Rob Purdie
Principal, Important Projects

Moshe Weitzman
Principal, Cyrve

David Strauss
Principal, Four Kitchens

Please vote and comment on
http://paris2009.drupalcon.org/session/transforming-economist-online-usi...

Add your vote for BoF: Drupal for Media:

http://paris2009.drupalcon.org/session/drupal-media

Seems like we should all be talking together!

Shall I add you as a speaker/attendee?

Cheers Daniel

Case study: kommentare.zeit.de - Integrate a static publishing system with a dynamic Drupal app

How we integrated a static publishing system with a dynamic Drupal app.

Established newspapers and publishing companies have lots of content. Already collected and stored in their home-grown data storage this content often is served through static files to the web - no way to interact.

This story is about how we integrated a fully static page serving mechanism based on XML and XSLT-Transformation which performs very well, with a dynamic Drupal application by lazy instantiation for ZEIT Online.

By now, the Community has more than 200k users and instantiates more than 100k high quality articles from professional editors of Die ZEIT [1]. Drupal allows our users to communicate and discuss the articles they already read online or in the printed version of the newspaper - almost 400k comments have been posted so far.

[1] http://kommentare.zeit.de
[2] http://www.zeit.de
http://paris2009.drupalcon.org/session/case-study-kommentarezeitde-integ...

Interact & Engage:

Investigative journalism can shed light on a problem, but where do we go from there? We hope that the people who read our investigations have an inherent desire to solve problems—to be the whistleblowers, the people on the front lines, the idea makers. And, we feel a responsibility to provide our readers with the tools to do so.

So, we've rebuilt MotherJones.com to be more than a news site: we want it to be a place for conversation, a forum for thinking about and debating solutions to the problems we cover. We want to actively include readers in the journalism we produce,and we want our readers to be able to interact with and inspire each other. That is why we chose Drupal as our community platform.

Whether users prefer to eavesdrop or jump right into the fray, here are four of the ways Mother Jones Comments Central allows staff and readers to find out which discussions are going on:

• Most Active: This section showcases the most commented-on articles from the last 7 days
• Most Recommended: See the stories that have generated the highest number of recommended comments in the last 7 days;
• MoJo Forums: These are curated Big Think panels in which one or more experts discuss a controversial topic with readers–and with each other. They generally last at least a week.
• Editors' Picks: These must-reads are the staff's latest favorites, and often the stories we email to our friends.

Additionally, readers who want to propose an action or solution to a problem addressed in the conversation, can tag their comment "Proposed Solution" or "Documented Result" by checking the appropriate box, at the time they submit a comment.

Why is this important? Readers are able to suggest a course of action to other readers. We hope that this forum will eventually become a vibrant place for people to hash out policy, to suggest stories for our journalists to investigate, and to organize around issues that are important to them.

Why was Drupal our platform of choice? For many reasons. For more information, please refer to the case study: http://drupal.org/node/466056. We will be providing additional information shortly.

http://paris2009.drupalcon.org/session/interact-engage-managing-readers-...