Two weeks ago I attended a joint Web 2.0 (conference) and Web2Open (unconference) two part session on building a social strategy for your business. Web 2.0 and social software luminaries Charlene Li and Josh Bernoff presented a session " how to have a successful social strategy" based on their extensive research and book "Groundswell".

They recommend that in order to lead a successful social strategy you should assume the role of a pragmatist. Pragmatists try to meet the company's goals, usually selling a product, as well as the needs of the community which wants complete access to the company's internal resources. In the case of Drupal.org this means carefully striking a balance between adding any set of modules the community wants on Drupal.org and respecting the time of the half dozen active members of the infrastructure team who are responsible for maintaining Drupal.org software and infrastructure.

A social strategy should have clear business objectives. For over a year now, there have been active discussions about what a Drupal.org redesign should accomplish in the redesign group. The association is recruiting community and Drupal association leaders who are taking the responsibility of creating those business objectives. The leaders will be able to focus exclusively on the role of defining objectives and ensuring they are met. While those objectives have not been finalized yet, let's pick a few that are reasonable. First, a Drupal.org social strategy should make it easier to learn about Drupal. Second, Drupal.org should make it easier to contribute to the Drupal project. Third, Drupal.org should allow for income from association memberships and highly focused advertising revenue to help fund Drupal association activities like a re-design of Drupal.org. If you have some ideas about objectives for a social strategy, be sure to share them in the Drupal.org redesign group.

Charlene and Josh recommended we use their People, Objectives, Strategy, and Technology approach to frame a Drupal.org social strategy. For the Drupal.org redesign we've completed three significant People activities. First, we conducted a set of 10 interviews of Drupal.org users. Then we surveyed 1200 Drupal users about what they want to see improved on Drupal.org. Finally, we developed some personas to describe the different types of Drupal.org users. We are assembling a team of people to work on Objectives.

We've not yet spent a lot of time formally discussing our Strategy for how a re-design will change the relationship with users on Drupal.org. The Drupal community has often taken a very conservative approach to empowering users on Drupal.org. For example, we frequently leave technical barriers in place and restrict permissions so that spammers, and even legitimate businesses can not cross-promote Drupal and their business. We need further discussions on how empowering the community might change the workload of Drupal.org maintainers and how we can deal with it.

From a Technology standpoint, our choice is pretty clear, we should upgrade Drupal.org to Drupal 6 and allow for more capabilities to be handed out to maintainers. Currently, feature development on Drupal.org is restricted to half dozen maintainers who are responsible for maintaining the code. With the content listing Views module, page layout Panels module, and web form building Content Creation Kit module the 93 site maintainers don't need to install extra modules to help meet some of our objectives. This added flexibility will also help to produce better marketing landing pages.

The last step in building a successful social strategy for Drupal.org is to line up our backers. Who are these backers? First, they are the 9 members of the board of directors of the Drupal association who vote in association board meetings. Second, they are the general assembly of the Drupal association, comprised of the 26 members, who have already made a symbolic vote to make the redesign of Drupal.org the number one priority for 2008. The general assembly of the Drupal association will meet and approve a budget to fund a redesign of Drupal.org. Third, our backers include the 500 paid members of the Drupal association. Fourth, we need to line up advertisers who can help generate revenue by placing ads in limited areas of Drupal.org such as the handbooks, hosting, and paid services or jobs sections of Drupal.org web properties. This means we need to reach out to the 76 hosting companies that have posted in the Drupal.org hosting forums and see if the are interested in advertising on Drupal.org. We need to reach out to the almost 2000 people who provide Drupal services through hundreds of companies and see if they are interested in advertising on Drupal.org. Fifth, we will need to conduct a targeted fund raising campaign to help pay for the redesign. Sixth, we need to solicit and recruit a capable set of design firms who will choose to take on this project in a long term partnership. Seventh, we need to generate agreement with the infrastructure team, and maintainers who will be doing a lot of volunteer work to make the re-design happen. Finally, we are going to need to get the support of the Drupal community and ensure they are supportive of a re-design.

If you are interested in learning more about developing a social strategy for your business, read Groundswell. If you are interested in participating in the development of a social strategy for Drupal.org, join the redesign group, and look for an upcoming meeting between the redesign group and Charlene and Josh who have agreed to meet with us when we are ready.

Yesterday the Drupal association added it's 500th paid member. 350 individuals paid 22 Euros for an individual membership and 150 organizations paid 73 Euros for an organizational membership. In total the association has received $21 448.45 from paid memberships. This revenue has allowed us to help operate events such as Drupalcon Barcelona, and Drupalcon Boston. It has also covered hardware purchases, RAM upgrades, and support contracts for those purchases. This financial support has allowed us to get ahead of Drupal.org's growth curve and ensure we have the infrastructure in place to meet a growing demand.

The Drupal association has prepared and reached initial agreement for a 2008 Budget, which will be voted on in an upcoming meeting. Part of that budget will be an allocation towards a re-design of Drupal.org. If you would like to be part of the re-design of Druapl.org you can participate by sharing your ideas in the Drupal.org redesign group. You can also request to become a Drupal.org webmaster or participate in the Drupal.org infrastructure list.

If you would like to become a paid member of the Drupal association, you can purchase a membership here.

First let me thank almost 500 people who've purchased a Drupal association membership. Your support makes it possible to hold Drupal events like Drupalcon North America, Europe, and soon hopefully a Drupalcon Asia. It's also allowing us to purchase the hardware we need to run Drupal.org and help prepare for a redesign.

There's been a backlog in processing memberships and we are working to fix this problem. Let me give you a bit of a technical explanation and then explain what we are doing to fix this.

When a person purchases a Drupal association membership, they may use up to five different email addresses when communicating with us.

1) When they apply for the membership the will use their personal email. For example: kieran at acquia.com.

2) When they pay for their organization membership they will use their companies paypal account say payment at acquia.com. In some cases, it may be the most convenient PayPal account, usually their spouses. Spouse at gmail.com

At this point if they have successfully paid for their membership then they will have a new contact record in the associations contact relationship manager, CiviCRM. If CiviCRM receives notification from PayPal that the payment was successful, then CiviCRM will automatically process a one year membership starting at the time of payment. If CiviCRM does not receive notification, then your membership is left pending. On March 27, 2008 payment notification stopped working and we are left with a backlog of 58 memberships that we have to manually verify. In total we have a backlog of 295 pending payments, most of which will be people who either chose not to complete payment or who are spammers.

3) Next people will want to update their information in the membership directory. They can do this by creating an account at http://association.drupal.org. This introduces two possibilities, they can create an account with their drupal.org login or they can create a new account. Let's assume they use they kieran@drupal.org as their login. We now have three separate email addresses that need to be resolved: CiviCRM contact, Payment email, and Drupal.org user account.

4) If they create a new account, and most do there's a good chance they will use yet another email. If for example, they purchased an organizational membership they might want the account to use info at acquia.com or support at acquia.com. Once again, we've likely got three emails to resolve: contact record, payment email, and the company email.

5) If you contact the association to help you resolve why your membership isn't showing up chances are, you are going to use yet another email, probably a personal email like say kieran.lal at personal.com. Or you might use highschoolnickname-graduateyear@gmail.com. That also makes it fun to try and map who you are to the existing three email addresses we have for you.

These five are the base cases. There are other edge cases involving multiple memberships, multiple user accounts, and multiple payment methods.

You might ask, why are we having these problems, you've seen membership processing done more effectively elsewhere. There are three underlying problems. First, we want your support and it's easier to let you pay for a membership first, and then work with you to resolve your email roulette problems after you purchased your membership. Right now about 50% of people who who fill out their personal details in the membership application don't complete payment. I don't want to add even more barriers.

Second, we need to build out our infrastructure to support OpenID. This means we need to support Chad and Derek to finish porting the Project module to Drupal 6, by helping Earl finish Views for Drupal 6, which project module now depends on. When Drupal.org upgrades to Drupal 6 we will have OpenID. Then we have to ensure Narayan has the infrastructure he needs to install and run an OpenID server. He's already added an SSL certificate so that administrators can log in securely to: drupal.org, association.drupal.org, drupalcon.org, infrastructure.drupal.org, security.drupal.org, testing.drupal.org.

Third we are using open source software to manage our contacts. We use open source software because we believe in the principles of open source, and that by using software and contributing back feedback we are helping to improve it for other organizations. We also don't have to pay for the software, and we can use the most effective payment engine which allows us to keep more of the money from members. While some membership software services will charge as much as 14% to process a paid membership, we only pay around 3% for fee processing. We are currently using CiviCRM 1.8. CiviCRM 1.9 mostly had mail upgrades which we didn't need. CiviCRM 2.0.2 is out and it will help to do a better job of merging these five potential email addresses, and removing duplicate contact records.

Raising money for a non-profit is hard work. But supporting the Drupal project is a very rewarding experience. If you've got 5 hours to help, I'll gladly take some volunteers and train you on how you can help us catch up on membership backlog. This will help to free me up so I can work on the underlying issues of upgrading Drupal.org to Drupal 6, getting CiviCRM 1.8 upgraded to CiviCRM 2.0, and working on user experience improvements for the Drupal.org redesign.

Kieran Lal
Drupal association board member - Fund raising

The summer is off to a great start as Google continues to blow loving kisses at Drupal.

Google just announced that they will sponsor 21 Drupal developer stipends in this year's Summer of Code program (SoC). To inspire young developers to work on FOSS projects during the summer, Google will provide a stipend of 5,000 USD to each student developer, of which 4,500 USD goes to the student and 500 USD goes to Drupal Association (or to the mentors). With 21 accepted applications this adds up to a 105,000 USD investment over a three-month period.

The accepted students, their projects, and the mentors are listed on the official Drupal.org announcement. Many of the listed projects touch Drupal core, so it looks like I'm in for a really busy summer. Congratulations to all successful applicants, and thanks to the Drupal Summer of Code organizers, the Drupal mentors, and last but not least, Google. Great!

Today, the Google Summer of Code 2008 accepted students were announced. 7,000+ applications to 175 mentoring organizations from nearly 4,000 students, of which 1,125 will be funded. Altogether, this means a $5.6+ million dollar investment in open source from our buddies at Google. Kick ass!

How did Drupal make out? We will be mentoring 21 Summer of Code projects from our 84 submissions. Drupal's mentor team did an outstanding job of weighing the pros and cons of each proposal, making difficult decisions, and ultimately choosing an exciting mix of projects and students:

read more

Good news! The next Drupal conference (DrupalCon) will take place in Szeged, Hungary from August 27-30. If you want to learn more about Drupal, or if you want to capture and absorb the passion and enthusiasm behind the Drupal project, this is the place to be.

DrupalCon Szeged will bring together hundreds of Drupal users and developers from all around the world. Whether you are a Drupal professional or an enthusiastic user coming to find out more, you're invited to join us in Szeged. Mark your calendars!

This will be the first Drupal conference in Central Europe, and I'm excited by that. There are a lot of Drupal people in Central Europe, probably more so than in Western Europe, and this is a great way to reach out them. Plus, I've been to Hungary twice and liked it very much.

Today I was a guest speaker at the business day of the Dutch Joomla Days. While this might seem odd, the subject of these days is "building bridges". Building bridges towards other CMS-es, other databases, other communities and hence towards Drupal.

I give these kinds of "pro Drupal" talks almost a bi-weekly basis now, where often other CMS-es are present as well. Last week I did one at eduvision where 100+ people where impressed by Drupal. Most often, the "competition" is Joomla and Typo3, both rather popular in The Netherlands (and Germany). While I do think that Joomla is good (enough) for the SoHo market and the audience of Drupal is much broader (from enterprises to personal blogs) and deeper (from video towards for example a resume site), these CMS-es are often compared. So normally, I try to make clear why Drupal is so much better then Joomla; better user management, roles, hooks, CCK, views, workflow, tableless design, multi-site install and almost forgotten but still miles ahead of any other CMS; taxonomy. There are zillion of ways where Drupal is clearly the leader in the field, but leading is sometimes not the same as "fitting".

This time however, I tried not too bash Joomla to much but to start building bridges. We do have a lot of the same problems that we can work on together. For example, we both use the GPL and we both have to protect our assets. Be both have a legal body protecting the community and facilitating the community, in Drupal's case, the Drupal Association.

That is why I was interested in the talk of one other speaker; James Vasile. James works for the SFLC and he is on the board of OpenSourceMatters and helping as a legal counsel for the Drupal Association. Most of the other Board Members of the Association spoke to James on the Boston DrupalCon ut since I was not there, it was good to speak to James during Lunch.

We taled about his passion, RMS, his other Open source projects / customers, how the SFLC is financed and the GPL3 as well as some other things. It is good to say the face you have exchanged mails with and it is good to build a relation between the SFLC, Joomla and Drupal. Communications is all about building bridges.

If you run a popular Drupal site, you'll sometimes find more queries in your MySQL server's slow query log than you really want to.

Sometimes the unruly queries can be eliminated easily by adding an index or two. Sometimes, they can be avoided alltogether (for example, the query in theme_forum_topic_navigation can be avoided by overriding the function with an empty one in your theme).

Sometimes, you need to be more ingenious. The queries in tracker.module have plagued drupal.org for a log time now. They added about 2000 slow query log entries per week on the slave server and did contribute to the melt-down we experienced last summer. There have been a lot of suggestions on how to best deal with them, but none was really a good solution.

The problem could only be resolved by a rewrite of the tracker module to use index tables. This rewrite is called tracker2 and was created by David Strauss. Since I deployed the module on drupal.org about two weeks ago, the tracker induced slow queries have disappeared alltogether. Great work, David!

Now, we need to find a way to deal with the slow queries generated by the rest of the modules, such as the search module. If you are interested in helping out: the slow query logs get posted to the infrastructure list each Saturday.

In case word hasn't reached you yet for some reason, Summer of Code 2008 is a go, and this is the week for college/university students to submit applications to work on projects for their mentoring organization of choice over the summer. Our hope is of course that a whole bunch will choose Drupal, which is an awesome, knowledgeable, and fun community to be a part of, and very supportive of SoC students (I know, because I was one myself back in 2005! :D).

As part of my duties for the Drupal Association, I help to administer initiatives that help bring in new contributors, like Drupal's involvement in Google Summer of Code. A huge thanks to the admin team -- chx, cwgordon7, and dmitrig01 -- for their tremendous efforts in getting the program kick-started!

We're trying something new this year that we haven't done in years past: public community review of student ideas and proposals, prior to their submission as formal applications for Summer of Code. There are multiple reasons why we chose to "beta test" this approach, which I will detail after the break.

However, for those who want to help bring new contributors to the Drupal project, and have a hand in deciding what new awesome projects get funded over the summer with Google's multi-thousand dollar investment, please jump in and help review some student proposals! The absolute deadline for student applications is Monday, March 31, 2008 at 17:00 PDT, so it's imperative that students get their questions answered and their proposals reviewed and refined as soon as possible so they have ample time to get their applications in.

read more

In 2006 Drupal was the runner up for the precious Webware CMS Award. And last year our beloved CMS even was the overall winner. By winning the competition, the Drupal Association got 5000 Dollars that was used for amongst others funding Drupal Conferences and to buy hardware for hosting the Drupal infrastructure. But even better then the money, Drupal got more airtime and more and more people recognized the power of Drupal.

This year, Drupal was once again nominated in the category "Publishing" and you are encouraged to vote on Drupal to make sure we win again this year. Please help by spreading the word and vote, you deserve it!

Aspiring Drupalcon organizers may be interested in understanding what went into organizing the conference content and coordinating volunteers. We've stripped the emails and private information from the Boston 2008 group so you can now take a look at one part of the organizing effort.
If you attended Drupalcon Boston you can now Click Here to take survey. If you like to provide feedback, we've created a wiki page for you to suggest improvements. We just request that you review the information in the group so that your suggestions are constructive and well informed.

Hello, one of the many improvements to this Drupalcon was the coordinated effort to capture sessions on video. The conference organizers purchased tapes for all the sessions in advance and kept a library of all 90 hours on MiniDV tapes.

The video recording team managed to capture all the sessions on video with some level of audio. They also managed to capture a separate audio channel on volunteer's laptops from the audio system. That audio is being uploaded to archive.org.

We first have to rewind all the 65 tapes and then send the tapes to be converted from tape to hard drives. We are currently rewinding the tapes. Each 1.5 hour session takes about 20GB of disk space. We have to order drives to work with the conversion company preferred disk format and their preferred file system. Narayan, Jamie, Heidi, and I are working to purchase the drives and get them to the conversion company.

We hope to get the terrabyte of video in batches, and shipped to the OSUOSL data center where they will be made available under access control. Then volunteers from the Drupal community will download the raw video format and convert to a H.264 .mp4 format. We are working out the logistics of getting volunteers to divide and download a terrabyte of data for post processing. In some cases we may need even more drives to divide and conquer.

Once the video is transcoded we need to get the audio and mix them together and make it available to our team of volunteers. The audio was not managed as tightly as the video, so if you are willing to own tracking down the audio please get in touch. It would be great to get 100% clear audio channel to complement the audio channel recorded by the video cameras.

Next we need to get all the presenters to make their slides available. Ideally, we would have had tighter expectations about slide deliverables, but the community can only absorb so much change at a time. If someone would like to step forward and chase down all the presenters to get slides that would be greatly appreciated. Please contact the video team.

Once we have video, audio, and slides our team of video editors can mash-up the Drupal sessions from Drupalcon Boston and make them available. We've got about 8 volunteers working on this right now, but we could use about 20 more and at least two individuals with determination to chase down the audio, and slides.

There's almost 1200 people in the Drupal dojo so we are hoping some volunteers step forward to help get all the Drupalcon videos available for everyone.

If you are surprised to see how much work is going to Drupalcon Video post production you are not alone. Just keep in mind, you've just been given insight in what it takes to run 0.5% of a Drupalcon.

Also, everyone once in a while a person emerges from the Drupal community that just blows me away. This volunteer worked countless hours on the http://drupalcon.org site. He did this despite having his house almost blown down during the Tennessee tornados and his community was devastated. He coordinated the video team, and basically skipped all the sessions to sit behind the desk and answer your questions for five days. Unfortunately he also managed to loose his tripod he brought to help with video recording. If you could send Jamie Meredith a couple of dollars via chipin that would be appreciated.

More Drupalcon updates coming soon!

Hello, one of the many improvements to this Drupalcon was the coordinated effort to capture sessions on video. The conference organizers purchased tapes for all the sessions in advance and kept a library of all 90 hours on MiniDV tapes.

The video recording team managed to capture all the sessions on video with some level of audio. They also managed to capture a separate audio channel on volunteer's laptops from the audio system. That audio is being uploaded to archive.org.

We first have to rewind all the 65 tapes and then send the tapes to be converted from tape to hard drives. We are currently rewinding the tapes. Each 1.5 hour session takes about 20GB of disk space. We have to order drives to work with the conversion company preferred disk format and their preferred file system. Narayan, Jamie, Heidi, and I are working to purchase the drives and get them to the conversion company.

We hope to get the terrabyte of video in batches, and shipped to the OSUOSL data center where they will be made available under access control. Then volunteers from the Drupal community will download the raw video format and convert to a H.264 .mp4 format. We are working out the logistics of getting volunteers to divide and download a terrabyte of data for post processing. In some cases we may need even more drives to divide and conquer.

Once the video is transcoded we need to get the audio and mix them together and make it available to our team of volunteers. The audio was not managed as tightly as the video, so if you are willing to own tracking down the audio please get in touch. It would be great to get 100% clear audio channel to complement the audio channel recorded by the video cameras.

Next we need to get all the presenters to make their slides available. Ideally, we would have had tighter expectations about slide deliverables, but the community can only absorb so much change at a time. If someone would like to step forward and chase down all the presenters to get slides that would be greatly appreciated. Please contact the video team.

Once we have video, audio, and slides our team of video editors can mash-up the Drupal sessions from Drupalcon Boston and make them available. We've got about 8 volunteers working on this right now, but we could use about 20 more and at least two individuals with determination to chase down the audio, and slides.

There's almost 1200 people in the Drupal dojo so we are hoping some volunteers step forward to help get all the Drupalcon videos available for everyone.

If you are surprised to see how much work is going to Drupalcon Video post production you are not alone. Just keep in mind, you've just been given insight in what it takes to run 0.5% of a Drupalcon.

Also, everyone once in a while a person emerges from the Drupal community that just blows me away. This volunteer worked countless hours on the http://drupalcon.org site. He did this despite having his house almost blown down during the Tennessee tornados and his community was devastated. He coordinated the video team, and basically skipped all the sessions to sit behind the desk and answer your questions for five days. Unfortunately he also managed to loose his tripod he brought to help with video recording. If you could send Jamie Meredith a couple of dollars via chipin that would be appreciated.

More Drupalcon updates coming soon!

Drupalcon registration has now closed. Many people are asking if they can see the sessions by video, or if the sessions will be streamed live. Due to having 800 people on the community wireless, we don't believe we can stream 5-6 sessions simultaneously in a reliable way.

We are now requesting volunteers who can help video record sessions, and who can do video post production each night. If you are willing to learn and commit to helping one day or one night, please let me know.

Drupalcon registration has now closed. Many people are asking if they can see the sessions by video, or if the sessions will be streamed live. Due to having 800 people on the community wireless, we don't believe we can stream 5-6 sessions simultaneously in a reliable way.

We are now requesting volunteers who can help video record sessions, and who can do video post production each night. If you are willing to learn and commit to helping one day or one night, please let me know.

In September 2007, we had approximate 430 registrations from Drupalcon Barcelona. For Drupalcon Boston we aimed to provide a conference facility that could accommodate anyone who wanted to attend. As recently as two weeks ago, we had anticipated that we would reach a total of 650. We are now over 700 registered attendees. Based on current projections, we will need to close registrations before Drupalcon starts next week.

If I previously told you not to worry about registering for Drupalcon, I apologize. You should register as soon as possible. If you know someone who was planning to come, but has not registered please reach out and ensure they register before they come.

At OSCON 2007, and Drupalcon Barcelona 2007 we had Drupalers fly to the event and assume they could register at the door. In both cases people learned that registrations had closed. Let's make sure that does not happen this time.

In September 2007, we had approximate 430 registrations from Drupalcon Barcelona. For Drupalcon Boston we aimed to provide a conference facility that could accommodate anyone who wanted to attend. As recently as two weeks ago, we had anticipated that we would reach a total of 650. We are now over 700 registered attendees. Based on current projections, we will need to close registrations before Drupalcon starts next week.

If I previously told you not to worry about registering for Drupalcon, I apologize. You should register as soon as possible. If you know someone who was planning to come, but has not registered please reach out and ensure they register before they come.

At OSCON 2007, and Drupalcon Barcelona 2007 we had Drupalers fly to the event and assume they could register at the door. In both cases people learned that registrations had closed. Let's make sure that does not happen this time.

For Drupalcon we've set an explicit goal of trying to raise the quality of the conference. But like all goals, you've got to adjust based on feedback.

In order to help make the conference as high quality as possible we would like to have session drafts and a public announcement about your session being selected. This helps to accomplish two goals. First, having a session draft gives the co-chairs the opportunity to review your session and provide feedback. It helps to identify topics that might not be covered in a track, and it helps to identify topics that might be repeated. Second, asking for a blog post helps promote you, and your session. There's a lot of people coming to Drupalcon and getting a chance to learn about your session in advance can be very helpful to them.

Unfortunately, making a good idea a requirement is not necessarily a good idea. Making it a tough mandatory requirement turned out to be a bad idea. This was my idea, and I'd asked my co-chairs to enforce it, to ensure they got a chance to review the sessions and could be confident in the quality of each and every session in their track. I am asking the co-chairs not to enforce this request as mandatory any more. This was my mistake, and I apologize to the session presenters and co-chairs who had to bear both sides of this.

I am asking the session presenters to do their best to both announce their session via one announcement: blog, email to mailing list, group posting, forum topic or how ever you see fit. I am also going to ask that all session presenters get a draft of their proposal to their co-chairs. If you don't then I'll follow up with you individually to ensure your session is on track, and that people know you are giving a session.

We've modeled much of the conference on what we learned from the Plone 06 conference. They kept a wait list of sessions, in case presenters were unavailable to present. It would be a shame to have an unplanned presentation presented when 90 people were more than ready to present a planned one. I'd like to avoid this at Drupalcon. So please prepare and give your hard working co-chairs a chance to do their jobs.

Kieran Lal
Druaplcon Boston organizer

For Drupalcon we've set an explicit goal of trying to raise the quality of the conference. But like all goals, you've got to adjust based on feedback.

In order to help make the conference as high quality as possible we would like to have session drafts and a public announcement about your session being selected. This helps to accomplish two goals. First, having a session draft gives the co-chairs the opportunity to review your session and provide feedback. It helps to identify topics that might not be covered in a track, and it helps to identify topics that might be repeated. Second, asking for a blog post helps promote you, and your session. There's a lot of people coming to Drupalcon and getting a chance to learn about your session in advance can be very helpful to them.

Unfortunately, making a good idea a requirement is not necessarily a good idea. Making it a tough mandatory requirement turned out to be a bad idea. This was my idea, and I'd asked my co-chairs to enforce it, to ensure they got a chance to review the sessions and could be confident in the quality of each and every session in their track. I am asking the co-chairs not to enforce this request as mandatory any more. This was my mistake, and I apologize to the session presenters and co-chairs who had to bear both sides of this.

I am asking the session presenters to do their best to both announce their session via one announcement: blog, email to mailing list, group posting, forum topic or how ever you see fit. I am also going to ask that all session presenters get a draft of their proposal to their co-chairs. If you don't then I'll follow up with you individually to ensure your session is on track, and that people know you are giving a session.

We've modeled much of the conference on what we learned from the Plone 06 conference. They kept a wait list of sessions, in case presenters were unavailable to present. It would be a shame to have an unplanned presentation presented when 90 people were more than ready to present a planned one. I'd like to avoid this at Drupalcon. So please prepare and give your hard working co-chairs a chance to do their jobs.

Kieran Lal
Druaplcon Boston organizer

We've already counted close to 40000 downloads in only three days!

For comparison: There were about 67000 downloads of all Drupal 5 releases combined in January 2008. There were about 60000 downloads of all Drupal 5 releases in January 2007 when Drupal 5 was released.