Scaling Langdale Pikes in The Lake District made me think of the peaks Drupal has to scale in the near future. Luckily @missymelliott and I had expert guidance climbing the peaks in the form of @tomstannard and having watched the recent keynote speeches I feel we also have a good leader in Dries.
There are many pitfalls in both walking in The Lakes and developing the core Drupal system but here are a few I've picked out:
- Trusting in your leader and their expertise leads to a quicker ascent
- Working as a team will make the journey more enjoyable and have better results
- Taking time out to stop and review the situation makes you appreciate how far you've come and how far you have to go
- Taking short cuts may be tempting but could prove fateful in the long run
- Reviewing all possible options and taking feedback from your team before attempting something is a must.
Drupal 8 is coming to fruition and thanks to Dries and our great community we'll have a powerful system to rival a lot of enterprise software out there.
A few of the main highlights for the next release of Drupal will be better HTML5 and mobile support, improved handling of multilingual features and integration with the Symfony framework.
I've read a number of posts that err on the negative side when it comes to the amount of changes in Drupal 8 but instead of being part of the problem we should come together to be the solution to make sure it works.
I'm still confident Drupal is heading in the right direction, what's your take, is Dries doing the right thing? Is Drupal 8 really going to take us forward or divide the community?