Today, Drupalcon Copenhagen kicked off with the Core Developer Summit. At least a couple hundred Drupalistas from old school to new filtered in throughout the day, and we made tremendous progress on Drupal 7, as well as the future of the project.

The day kicked off with presentations by myself on how to improve our CVS application process, Larry Garfield with a short pitch for his talk Wednesday morning on Drupal: The Next Generation, Jen Simmons on HTML 5, its importance, and how it fits into Drupal, and David Strauss on Kargo Event-driven Drupal for crazy high-performance sites. These presentations laid out both current challenges, as well as whet our appetite for what's possible in the future in Drupal 8 and beyond.

Thanks to Justin Christofferson of larsdesigns, there are even videos of these sessions on archive.org!

• http://www.archive.org/details/AngieByronwebchickSpeaksInCopenhagenDrupa...
• http://www.archive.org/details/DrupalconCopenhagenPre-conferenceDavidStr...
• http://www.archive.org/details/JenSimmonsDrupalconPre-conference

Following these, however, the focus turned squarely back to Drupal 7. The room was split up into tables to each work on a group of critical issues blocking Drupal 7 from being released. There was a table for file system bugs, a table for upgrade path bugs, and so on. Anyone who was new was taken to a couple of tables to learn about how to write automated tests, and Ariane Khachatourians held a documentation sprint to help make progress on Drupal 7 handbook documentation.

We started the day with 32 critical issues, and ended the day with 18 (they've since gone up a little, I see ;)). Critical issues fixed during the sprint:

• Anonymous users can post comments in name of registered users (security)
• Actions/Triggers escaping issues (security)
• Themes cannot always participate in drupal_alter() (system)
• Filter system security fixes from SA-2008-073 (security)
• hook_file_references() not designed for flexible file storage (file api)
• Cannot upgrade Drupal core if the comment module is enabled. (upgrade path)
• Increase simpletest speed by running on a simplified profile. (testing)
• Entity listing and loading does not allow for node access. (node access)

...as well as a variety of major and normal/minor bugs. All critical issues that were not fixed today got unstuck, worked on, and otherwise eased along. The energy in the room was palpable and we made huge progress for such a short period of time.

Additionally, a break-out session was held on how to handle commit (push) access to our forthcoming Git repository, the consensus of which is written up here: http://drupal.org/node/781264#comment-3357720. At a high level, it will be much easier to get initial commit access to Drupal.org (essentially agree to a "Developer Code of Conduct" that talks about licensing, community philosophies, etc.), and the approval process will move instead to creating the first project release, at which point code reviewers can use the normal contribution tools such as issue queues and commit/diff viewers to help mentor new developers.

We desperately need more code reviewers for new contributors to help unclog the CVS Applications queue. If you're interested in helping, please sign up here: http://groups.drupal.org/node/88599

And that's about it! Super productive day all around, with much more to come tomorrow and throughout the week! :D