I've seen some Drupal module developers out there have a lot of trepidation about moving to Drupal 8, most often via hearsay from others or via occasionally dipping in to look around and being spooked by newfangeldy stuff like namespaces, object-oriented code, and weird directory structures.
(Sorry for spamming Drupal Planet with this, but a few people on IRC were saying it might be a good idea for people to get a wider heads-up, given the number of Drupal community hats I wear.)
Here's an outline of how that may or may not affect you, and who to talk to instead:
As Gábor pointed out, now's the time to help make Drupal 8 more unified and user/developer friendly. A great way to do that is try porting your modules, now, while there's still time to fix the APIs before code freeze.
But wait, there's more! ;)
This was originally posted to the "The influence of subtlety" thread on the Drupalchix group back in 2010, but since that was awhile ago now, and since I'm giving a talk on How to Create Ravenously Passionate Contributors at DrupalCon Sydney (and this experience played a huge part) I figured I'd post this to Drupal Planet as well.
Here are some highlights from my first DrupalCon (Vancouver, 2006).
Join Tatiana / tvn, Drupal.org Project Coordinator, for a series of BoFs on major new features for Drupal.org and how you can help!
13:00-14:00 Drupal.org office hours BOF
Come meet the Drupal.org team and learn more about how you can help make awesome changes to Drupal.org!
The Spark distribution is a Drupal 7 distribution which aims to prototype cutting-edge authoring experience improvements that we hope to propose for inclusion in Drupal 8 core, announced back in May. Please download the latest release and check it out, and give us lots of feedback! (And/or patches! ;))
Greetings, Drupal Planet!
Here are the slides from my DrupalCamp Vancouver "hook_future_alter()" talk. This outlines the major changes currently in development for Drupal 8, how Drupal 8 will impact end users, site builders, designers, and developers, and how to jump in and help!
Back in September, http://drupalcontribstatus.com/ was launched to track the porting status of the top 60 contributed projects to Drupal 7. Since then, we've whittled the list down to just 20 projects remaining, as well as tons of progress on the rest! YEAH!
I contacted each of the maintainer(s) of those remaining projects and have come up with a list of next steps for each. Your help is needed if we want to get that graph up to 100% by year's end. (Just in time for Drupal 7's first birthday! :))
As a general rule, help is needed in the following areas:
- Issue queue triage (Difficulty: Novice): Going through the issue queues of these modules and doing things like closing duplicate reports, verifying that bug reports are valid, and so on. None of this is particularly difficult work, but time that maintainers have to spend doing it is time they can NOT spend porting their modules to Drupal 7.
- Reviewing patches (Difficulty: Intermediate): Going through the issues in the queue marked "needs review" and making sure patches still apply, then testing to make sure that they still work, then reporting on the results of your testing are all critical things that really help save maintainers time, and ensure that any actionable issues are escalated to their attention.
- Experience in various core sub-systems (Difficulty: Intermediate to Advanced): If you know how to write automated tests, are familiar with how the render API works, can answer questions about the new Field API or File API, there are several issues identified that could use YOUR help! Note that you don't necessarily need to be in MAINTAINERS.txt to provide this help, either; if you've already started building Drupal 7 sites and modules, you likely know enough to be helpful!
- Co-maintainership (Difficulty: Intermediate) Many of these projects are seeking co-maintainers. If you or your business/customers depend on any of these modules, investing solid time in the issue queue to help review and roll patches for issues in need would be of tremendous benefit, and would help position yourself to ask for commit rights so that you can ensure these modules stay solid going forward.
So, without further ado, here are some specifics on how you can help Drupal 7, and the maintainers whose code you rely on!
Here are some notes from the Drupal 8 status update talk that Dries and I gave today to the Acquia team, since this seemed like useful info for the community to know as well. :) It covers both process changes for addressing previous issues that arose in Drupal 7, as well as a status update on Drupal 8 progress to-date. This could be useful to folks who have been wondering where all of the various Drupal 8 status updates fit into the "bigger" picture.
Please comment here if I left anything out, or messed up anything.