A crucial requirement for the MSNBC's recent online TV revamp was a highly interactive user interface that didn't interfere with the site's all-important video player. In our previous work on the main MSNBC site, we had used AngularJS to decouple complex front-end UI behaviors from the Drupal-powered backend. With that experience, using AngularJS for the new requirements was a no-brainer.
Putting on three DrupalCons each year requires a huge amount of manpower and dedication. It’s a labor of love, and wouldn’t be possible without teams of passionate volunteers, working with a dedicated staff at the Drupal Association.
Who is the Drupal Association’s DrupalCon team? For those who wonder about the people behind the magical events, we’ve put together this guide to the folks who make DrupalCon happen.
Rachel Friesen, Events Manager
Rachel (racheldrupal) has been with the Drupal Association for a year, and works as an events manager to guide the DrupalCon team through the entire process of planning and executing a DrupalCon. One of Rachel’s primary functions is to set strategy for each DrupalCon, including objectives for individual conventions and how to move towards future goals. Rachel is responsible for budgeting, working with contracts, and keeping the project moving.
When not making recommendations to the board about the location of the next DrupalCon or acting as the big cheese on site for events, Rachel enjoys curling, and grew up wanting to be a marine biologist. Her favorite part of each DrupalCon event is watching the reveal for the location of the next DrupalCon during the closing session.
Amanda Gonser, Lead DrupalCon Coordinator
Amanda (amanda.drupal) joined the Drupal Association in October, and came to the Association with experience planning events around the world. As the Lead DrupalCon Coordinator, Amanda works with the community volunteers, manages the programming of each DrupalCon, and handles the website content. Amanda is working hard on DrupalCon Los Angeles and can’t wait to see it all come together this May.
Amanda spent nearly five years living in the Basque Country of Spain, and when not working, she devours books like some people eat chocolate. Amanda has two kitties who rule her life, and this year, she’s trying out her green thumb with her first flower garden.
Tina Krauss, DrupalCon Coordinator
Tina (tinakrauss) is the newest member of the DrupalCon team, and came on board in mid March. As a DrupalCon Coordinator, Tina will work with each con’s volunteers, assist in con programming and logistics, and work with website content. Tina is also focused on customer support and responds to tickets submitted to our Contact Us form related to the Cons.
A native of Germany, Tina moved to Portland, Oregon several years ago, where she currently resides. In her free time, Tina is an adventurer. She loves to travel around the world -- the farther, the better! She also enjoys outdoor activities like hiking, biking, backpacking, skiing, and more.
Timothy Constien, Sponsorship Fulfillment Coordinator
As Sponsorship Fulfillment Coordinator, Tim (timconstien) acts as a liaison between the Drupal Association’s revenue team and the DrupalCon team. His focus is on maintaining and building strong relationships with our sponsors, ensuring that sponsors’ DrupalCon experiences go above and beyond, and that each sponsor’s investment is maximized across every possible marketing platform, including social media, the DrupalCon website, at the DrupalCon event, and more.
Tim is an extreme sports enthusiast, and loves snowboarding and skateboarding. He also likes skiing and surfing, and the lifestyle around those sports. Tim enjoys spending his free time in Portland seeking out the city’s best cheap food and craft beers.
Are you interested in what is happening with Drupal Association membership? This is the first of two posts about our membership program. We've made some changes, but much remains the same. You may notice that the price slider has been removed from the contribution pages and it is replaced with price points that provide clearer options for paying. The new price points were selected after looking at the most frequent gift amounts from the slider. Don't worry, though: the minimum fee for membership will remain at the same levels as last year. We are also experimenting by testing graphics and placement of items on the pages and will let you know the results as you may find them useful for your own projects.
I want to explain why we moved away from the slider, but first, let's go over some history. The Drupal Association membership program began in 2007. For six years we kept membership dues at the same amounts. In 2013, we decided to make some changes after hearing from the community that there was a need for more price options. The idea was that, with flexible prices, more of the worldwide Drupal community could give back and become members while paying what they could afford.
To give donors more incentive to choose membership, we also decreased the minimum donation amount for individuals by 32%. Conversely, we raised the minimum amount for organizations-- Drupal itself has grown and matured, and we knew that Drupal businesses have as well. We figured, if this new structure did not work for an organization, the option for Individual membership would still be a good one.
So in mid-2013, we launched the slider pages into the universe. We learned that the slider did not provide users with enough guidance on how much to give. There was not enough information to suggest appropriate gift amounts, and members gave at many price points. So we have said farewell to the slider and will assess the price point performance in the months to come.
In the next post, we give a recap of 2014. If you have any thoughts or suggestions to share on the change or membership in general, your feedback is always welcome. Find me via contact form and reach out anytime.Personal blog tags: Membership
Drupal 7.35 and Drupal 6.35, maintenance releases which contain fixes for security vulnerabilities, are now available for download. See the Drupal 7.35 and Drupal 6.35 release notes for further information.Download Drupal 7.35
Download Drupal 6.35
Upgrading your existing Drupal 7 and 6 sites is strongly recommended. There are no new features or non-security-related bug fixes in these releases. For more information about the Drupal 7.x release series, consult the Drupal 7.0 release announcement. More information on the Drupal 6.x release series can be found in the Drupal 6.0 release announcement.Security information
We have a security announcement mailing list and a history of all security advisories, as well as an RSS feed with the most recent security advisories. We strongly advise Drupal administrators to sign up for the list.
Drupal 7 and 6 include the built-in Update Status module (renamed to Update Manager in Drupal 7), which informs you about important updates to your modules and themes.Bug reports
Drupal 7.35 and 6.35 were released in response to the discovery of security vulnerabilities. Details can be found in the official security advisory:
To fix the security problem, please upgrade to either Drupal 7.35 or Drupal 6.35.Update notes Planet DrupalDrupal version: Drupal 6.xDrupal 7.x
Interested in what is happening with Drupal Association membership? Here's a recap of 2014.
Last year, the Drupal Association membership program had a solid renewal rate, slight overall growth, and we surpassed revenue goals. We're happy to point out that even though the overall number of Organization Members has declined (our peak was 619 active organization members in 2013), it's because 82 of those companies have become our Supporters. This means they give at even greater levels than members. To all of our supporters, cheers and thank you for giving back to Drupal!
(For the general public: if you see a profile or company page on Drupal.org with a badge on it, you can thank the individual or organization for all that they do for Drupal!)
Do you have more thoughts or questions about membership? Find me via contact form anytime with your feedback.Membership
We have two team members slated to speak at two different Drupal Camps in March!
Gus Childs will be delivering a talk at MidCamp in Chicago titled, "Need a Better Way to Organize Your Features? Go Ask Alice." It’s based on a blog post of ours and he’ll cover Features best practices and how to stay sane while using them on your bigger projects.
Mark Dorison will be speaking at DrupalCamp NOLA on 3/28. His talk, "Spend More Time Surfing: Simplifying Your Code (and Life) With Entityfieldquery & EntityMetadataWrapper" will cover methods you can use right now to work with entities in Drupal 7.
If you’re attending either of these camps, be sure to say “hello” to Gus, Mark, or any other CHROMATIC team member that might be floating around. You just might land yourself a CHROMATIC t-shirt!
Today we’ll analyze the module MEFIBS (More Exposed Forms In Blocks).
Lately I often lighted on having the need to insert some exposed filters in more blocks, staying on the same view!
Since the last Drupal Core Update, the Drupal community has reduced the number of D8 critical issues to 45, and managed to keep the number of critical issues on one pagesince we hit 50 criticals on March 6th! We've also changed the behavior of the "admin role" setting so that any user with the "admin role" passes all permission checks automatically (like the superuser); added HTML5-lib to core so that HTML5 can be parsed properly; and fixed a bug preventing all PHPUnit tests from running.
Also, after a few months of work, the Technical Working Group, Drupal.org Software Working Group, Security Working Group, and frequent project application reviewers presented their proposed changes to the project application review process. They're looking for your feedback, so please read their proposal and leave your thoughts!
Some other highlights of the month were:
- xjm performed a detailed analysis of contibution and influence in Drupal 8.
- To improve user experience, field types are now grouped by category.
- Josh Taylor detailed how to automatically test contrib modules when Drupal 8 updates.
- On the front end, the $messages page element was converted into a block, a filter to render render-arrays was added to Twig, views base fields are now rendered like Field UI fields; the button, skip link, and comment components now follow CSS standards; and menu classes were added back.
- Sujith Nara wrote an overview of all the caching methods available in Drupal 8.
- To improve performance, getting fresh entity and field definitions no longer invalidates all caches, views exposed filter forms no longer cause cache tables to grow exponentially, views now sets cache tags on it's render arrays, views can now cache base tables and entity types, routes are now rebuilt on write; and the unused block_plugin cache tags were removed.
- Daniel Sipos wrote a tutorial on creating custom field formatters in Drupal 8.
- To improve developer experience, developers can enable an X-Drupal-Cache-Contexts HTML header to list cache tags, and entities and fields can now report which language their content is in.
- Amber Matz wrote an excellent article explaining dependency injection using real-world examples.
- Lee Rowlands explained the tradeoffs of using the Events system versus Alter hooks in Drupal 8.
- The procedural functions drupal_bootstrap(), drupal_get_bootstrap_phase(), language_load(), language_list(), language_default(), drupal_theme_access(), drupal_html_id(), node_type_load(), node_type_get_types(), entity_load('node_type'), entity_load_multiple('node_type'), request_uri(), system_rebuild_theme_data(), and entity_load_by_uuid() were all removed, as was the html => TRUE option to l() and the $script_path global variable.
See Help get Drupal 8 released! for updated information on the current state of the release and more information on how you can help.
We're also looking for more contributors to help compile these posts. Contact mparker17 if you'd like to help!Drupal 8 In Real Life
Voting in the Drupal Association's 2015 At-Large Board Elections ends Friday, so this is your last chance to make your voice heard! Anyone with a Drupal.org account that was created before the time nominations opened (January 31, 2015), and who has logged in at least once in the past year is allowed to vote, even if they are not a member of the Drupal Association!
Some other events happening in the coming weeks are:
- MidCamp starts tomorrow (March 19th) and runs until March 22nd at the University of Illinois in Chicago, Illinois, USA.
- DrupalCamp New Orleans will be on March 28th in New Orleans, LA, USA.
- Stanford Drupal Camp 2015 in Stanford, CA, USA will be on April 10th and 11th.
- Drupal Dev Days, a week of sprints among core contributors and Drupal veterans with awesome sessions on D8, is less than a month away (April 13—19), hosted in Montpellier, France. All the early bird tickets are gone, so buy your tickets soon!
- In case you missed it, DrupalCamp Ottawa has been postponed to summer 2015.
Do you follow Drupal Planet with devotion, or keep a close eye on the Drupal event calendar, or git pull origin 8.0.x every morning without fail before your coffee? We're looking for more contributors to help compile these posts. You could either take a few hours once every six weeks or so to put together a whole post, or help with one section more regularly. If you'd like to volunteer for helping to draft these posts, please follow the steps here!
It can be difficult to decide whether to send representatives of your organization to DrupalCon. You may find yourself asking questions like, what's the ROI? What’s the value of being there in person? Is it really worth the money? There are tremendous benefits, measurable and immeasurable, to sending your employees to DrupalCon. Here are three reasons why going is a win-win for both your employees and your organization.
For the past few months, members of the Technical Working Group, Drupal.org Software Working Group, Security Working Group, and frequent project application reviewers have been working on proposed changes to the project application review process.
The proposed changes have been posted for public review. https://www.drupal.org/node/2453587
If you have any comments or questions, please add them to the issue. This proposal is open for feedback until the end of March. We will then incorporate the feedback and start working on implementing these changes.