core

Nathaniel Catchpole (catch) will be joining Third & Grove. His primary responsibility will be to continue making Drupal 8 better. Adding Nat to the team will deepen our investment in Drupal, support the growing Drupal community, and further our growing expertise in Drupal 8. What will Nat be working on? I’m not exactly sure as he gets to decide, but I know it’s Drupal core and I know he will now be able to continue making Drupal core great. Welcome Nat!

Nathaniel Catchpole (catch) will be joining Third & Grove. His primary responsibility will be to continue making Drupal 8 better. Adding Nat to the team will deepen our investment in Drupal, support the growing Drupal community, and further our growing expertise in Drupal 8. What will Nat be working on? I’m not exactly sure as he gets to decide, but I know it’s Drupal core and I know he will now be able to continue making Drupal core great. Welcome Nat!

Nathaniel Catchpole (catch) will be joining Third & Grove. His primary responsibility will be to continue making Drupal 8 better. Adding Nat to the team will deepen our investment in Drupal, support the growing Drupal community, and further our growing expertise in Drupal 8. What will Nat be working on? I’m not exactly sure as he gets to decide, but I know it’s Drupal core and I know he will now be able to continue making Drupal core great. Welcome Nat!

When specifying dependencies in your module's .info file, you now can (and are encouraged to) specify the project that your module depends on also (since Drupal 7.40) - for example, dependencies[] = views:views_ui to declare a dependency on the Views UI module within the Views project, rather than just dependencies[] = views_ui. This extra information will help resolve ambiguities and can potentially be used by other tools in the future, for example by the drupal.org testbot or Drush to be able to automatically download dependencies that currently can't be downloaded automatically.

When specifying dependencies in your module's .info file, you now can (and are encouraged to) specify the project that your module depends on also (since Drupal 7.40) - for example, dependencies[] = views:views_ui to declare a dependency on the Views UI module within the Views project, rather than just dependencies[] = views_ui. This extra information will help resolve ambiguities and can potentially be used by other tools in the future, for example by the drupal.org testbot or Drush to be able to automatically download dependencies that currently can't be downloaded automatically.

The bottom line Investing in Drupal has helped grow our business, both in the number of projects and the size of our team. Since making this commitment, we’ve seen opportunities increase and job applicant quality improve. We've hired two additional Drupal 8 Core Developers to strengthen our investment in our future.

The bottom line Investing in Drupal has helped grow our business, both in the number of projects and the size of our team. Since making this commitment, we’ve seen opportunities increase and job applicant quality improve. We've hired two additional Drupal 8 Core Developers to strengthen our investment in our future.

We will open the core sandbox and meta issue soon, once the above dependencies are resolved or worked around, so that contributors can begin to explore what it means for Views to be in core.

We are planning one last major sprint before feature freeze in the week preceding BADCamp. (Pantheon will be hosting this sprint; more details soon.) The BADCamp sprint will be our chance to coordinate our final push to make Views core-ready. Once Views is committed to core, all further work will take place in our sandbox and the Drupal core issue queue.

All CSS in Drupal core should be defined by the theme.

This will help in a number of ways:
- Prevent the need for css overrides
- Stop all drupal sites looking drupally
- Allow full control to the themer

(me) - does not affect contrib.

Most transparent Drupal Core development... ever

last updated August 2, 2012.

We are hard at work on the next version of Drupal. Some of the great things planned include better HTML5 and mobile support, improved multilingual features, and setting up Drupal 8 on a modern web development framework. But we can't do any of it without your help!