While the focus of the Copenhagen Drupal Core Development Summit was, rightly so, placed on making progress with Drupal 7 some time was dedicated to looking into the future. In this post I try to find some common themes across the requirements and challenges set for Drupal and some of the issues to look out for in order to meet these challenges.
Can Drupal revolutionise its contribution process and tap into the long tail of developers that have little time to contribute but want to help in a meaningful way? A proposal for the Drupalcon San Francisco Developer Summit.
This debate goes to the heart of what Drupal should be. Is it a framework, a CMS, a social network creation tool or all of the above. The small core movement argues for Drupal itself to focus on the absolutely essential while installation profiles offer complete solutions that address specific use cases.
As Drupal matures and its community grows the provisions made for end users to have a better experience and to enable designers to more easily mould Drupal into the appropriate looks and behaviours becoming increasingly important. The initial debates at the Drupal Conference were heated but the end results may well prove that it was all worth it.
Back home after my first Drupal conference and it was a great experience. I was obviously excited about Drupal's prospects before going, but the conference has renewed my confidence in the future of Drupal that is looking brighter than ever.
As a means to crystalize my thoughts I will try to sum up my experience of the conference and provide my own input on how I see (would like to see) the future of Drupal shaping up. The whole things is quite long so I broke it down to three parts - the community, the designers vs developers challenges and the small core movement.