{"id":4960,"date":"2011-03-09T11:36:55","date_gmt":"2011-03-09T10:36:55","guid":{"rendered":"http:\/\/tokao.com\/?p=4960"},"modified":"2011-03-09T11:36:55","modified_gmt":"2011-03-09T10:36:55","slug":"looking-ahead-to-drupal-8","status":"publish","type":"post","link":"https:\/\/tokao.com\/wordpress\/2011\/03\/09\/looking-ahead-to-drupal-8\/","title":{"rendered":"Looking Ahead to Drupal 8"},"content":{"rendered":"<h1><span style=\"font-size: 13px; font-weight: normal;\">In the opening keynote for <a href=\"http:\/\/chicago2011.drupal.org\/\" target=\"_blank\">DrupalCon 2011<\/a>, Drupal founder Dries Buytaert laid out what they&#8217;ve learned from Drupal 7, and his initial plans for Drupal 8.<\/span><\/h1>\n<div id=\"article-body\">\n<h3>Looking Back<\/h3>\n<p>Drupal 7 was a huge endeavor. The release took three years and had 1,000 contributors, with 30 people being responsible for 50% of the improvements. In discussions with the community, Buytaert feels that the things they did well were:<\/p>\n<ul>\n<li>Test-driven development<\/li>\n<li>Updating the development documentation as patches were accepted<\/li>\n<li>Having a usability team<\/li>\n<li>Taking development snapshots, especially at the code freeze stage<\/li>\n<li>Having an accessibility team<\/li>\n<\/ul>\n<p>On the other hand, there were things they could do better. Buytaert identified the following areas where he&#8217;d like to improve during the cycle for Drupal 8:<\/p>\n<div>\n<div>\n<div id=\"google_ads_div_Inline-300x250--01\"><ins><ins><\/ins><\/ins><\/div>\n<\/div>\n<\/div>\n<ul>\n<li>Many people wanted to work on a feature or a bug but weren&#8217;t sure if they&#8217;d be accepted<\/li>\n<li>Some felt the release cycle was too short, and some too long \u2014 the main complaint was that no one knew when it would be ready<\/li>\n<li>Lack of high-bandwidth communication<\/li>\n<li>Better and stronger priorities, rather than letting them get muddy at the end<\/li>\n<li>Too many critical bugs, there were 400-500 in the code freeze<\/li>\n<li>Performance seemed like an afterthought<\/li>\n<\/ul>\n<h3>Drupal 8<\/h3>\n<p>The development branch for Drupal 8 opens today. People will work on their code in a Git sandbox, and it will have to pass through a number of gates before it&#8217;s accepted into the main tree. These gates will mostly involve the main priorities (which he&#8217;s dubbed initiatives) for the next version:<\/p>\n<ul>\n<li>Performance<\/li>\n<li>Accessibility<\/li>\n<li>Usability<\/li>\n<li>Documentation<\/li>\n<li>Testing<\/li>\n<li>No critical bugs<\/li>\n<\/ul>\n<p>Rather than having a single co-maintainer, Buytaert will appoint an owner for each of the initiatives. This move, he hopes, will increase the project&#8217;s bandwidth and communication internally. Other focuses for Drupal 8 will include:<\/p>\n<ul>\n<li>Publishing to any device, which means being more flexible in the types of code Drupal 8 can output<\/li>\n<li>Pulling information from any source<\/li>\n<li>Social features and the individual experience<\/li>\n<\/ul>\n<p>Initiatives he&#8217;s identified for multi-device publishing include web services, contexts, CSS3, HTML 5 and mark-up free core. For dealing with any information, they&#8217;ll focus on interoperability, such as clean APIs and standards-based connectors. And to provide a &#8220;delightful experience,&#8221; the push for usability will continue.<\/p>\n<p>To help large-scale Drupal users, there are two more important features Drupal 8 needs to address:<\/p>\n<ul>\n<li>Configuration management<\/li>\n<li>Content staging<\/li>\n<\/ul>\n<p>Finally, Buytaert discussed the need to have a strong ecosystem around Drupal, as that is how the top players in techology today are driving adoption. To that end, they&#8217;ll be focusing on further improvements to Drupal.org and initiatives such as the Git migration.<\/p>\n<p>This isn&#8217;t a short or simple list. To get started, he says they&#8217;ll focus on web services, HTM L5, UUIDs and configuration management.<\/p>\n<h5>(from <a href=\"http:\/\/www.cmswire.com\/cms\/web-cms\/looking-ahead-to-drupal-8-drupalcon-010441.php?utm_source=twitter&amp;utm_medium=twitterfeed&amp;utm_campaign=Social%20Media%20%28Twitter%29\" target=\"_blank\">cmswire<\/a>)<\/h5>\n<\/div>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In the opening keynote for DrupalCon 2011, Drupal founder Dries Buytaert laid out what they&#8217;ve learned from Drupal 7, and his initial plans for Drupal 8. Looking Back Drupal 7 was a huge endeavor. The release took three years and had 1,000 contributors, with 30 people being responsible for 50% of the improvements. In discussions [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[2],"tags":[13,142,97],"class_list":["post-4960","post","type-post","status-publish","format-standard","hentry","category-technology","tag-cms","tag-cmswire","tag-drupal"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/tokao.com\/wordpress\/wp-json\/wp\/v2\/posts\/4960","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tokao.com\/wordpress\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/tokao.com\/wordpress\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/tokao.com\/wordpress\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/tokao.com\/wordpress\/wp-json\/wp\/v2\/comments?post=4960"}],"version-history":[{"count":0,"href":"https:\/\/tokao.com\/wordpress\/wp-json\/wp\/v2\/posts\/4960\/revisions"}],"wp:attachment":[{"href":"https:\/\/tokao.com\/wordpress\/wp-json\/wp\/v2\/media?parent=4960"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/tokao.com\/wordpress\/wp-json\/wp\/v2\/categories?post=4960"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/tokao.com\/wordpress\/wp-json\/wp\/v2\/tags?post=4960"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}