Global Training Days this quarter had 38 locations. Not only was this event hosted around the world, but one of the online trainings had students join from 6 continents! Some trainings came together thanks to collaborations of several partners; for example, the NYC training was jointly hosted and organized by Phase2 and Sego Solutions in partnership with Stony Brook University, DoSomething.org, TekSystems, and NY Public Library. We also saw camps hold #DrupalGTD training sessions as part of their events at DrupalCamp Transylvania and DrupalCamp Guadalajara. Each participant helps to make the Drupal community stronger, so we'd like to say a big thanks to everyone involved!
Each training helps to make Drupal more accessible because attendees are given the fundamentals needed to get started with making their own web projects. See the full list of participants at https://www.drupal.org/global-training-days/2016 and mark your calendar for the next training events on September 9th and 10th.[View the story "Drupal Global Training Days in April 2016" on Storify] Personal blog tags: Drupal Global Training Day
Hello, Drupal world! We are thrilled to be able to give you an inside peek at what goes into planning DrupalCons. Throughout 2016, we’ll share a series of posts, and a few webcasts, to show some behind-the-scenes aspects of DrupalCon. In honor of National Volunteer Week, this month's DrupalCon post highlights how an army of amazing, dedicated volunteers is behind every DrupalCon.
If you’ve ever attended a DrupalCon, you probably remember the Drupal Association standing onstage and saying that this event ‘couldn’t happen without our amazing volunteers.’ We normally have a round of applause for the volunteers at each particular Con, but that still doesn't fully convey how much of the Con is lead by some fantastic community members. In this blog we want to help quantify how much time and energy these volunteers give to help create a memorable and enriching Con for you.
Before you even know there is a Con happening in any city, volunteers are already on board helping to make it happen. Once the city has been decided and finalized by the Drupal Association, we loop in a small group of community leaders in the secret city to come together and help us make a splash when we announce the next year’s Con location.
Besfore the Con has even been announced, these 4-6 volunteers work to put together a document that guides our designer in the logo creation and branding of the still-secret event. The community gives input during the design process of the logo, sticker and splash page that goes live after the announcement. The announcement is another way that the volunteers make an impact by dreaming up an awesome way to tell you about how awesome their city is and why you should come to DrupalCon the next year.
Once we have publically announced a location, the Drupal Association reaches out to more volunteers to build the Program Team. This team includes various groups of volunteers who make a huge impact on your DrupalCon experience. Here is a quick rundown of how committed these volunteers are and how their contribution shapes the Con.
- Track Team - with two to three volunteers per track, this is the team that sets the tone of what content you will be hearing in sessions. They begin thinking about this at least 5 months before the Con and meet weekly to move the session content forward. Between writing track descriptions, reaching out to speakers to curate sessions, reading every single session submission, helping build the schedule and later acting as coaches for their speakers, this team signs up for a long and heavy time commitment and the fruits of their labor results in amazing sessions. In New Orleans we have 130 hand-selected sessions thanks to this dedicated team. Additional Selection Committees - we also call on the help and expertise of various other community volunteers in selecting more things related to DrupalCon. For the incredible training course proposals that we get, we have a team dedicated to selecting the 15 that should be offered. We also have a team tasked with the duty of reading each grant and scholarship application and making the difficult decisions about who is given an award to come to the DrupalCon.
- Summit Leads - each Summit is led by a small team who works to develop a full day of engaging and educational content that will allow attendees to get the most out of the Con by adding this Monday ticket event to their trip. Our Summit Leads begin working 4 months before the Con to line-up panel guest speakers, organize multiple round table topic leaders, create the flow of the day as well as emcee their event. If you’ve ever attended a Summit, we hope that you appreciate the time and energy that these Leads have committed to making your day great.
- Sprint Leads - this team of leads works year-round to help create sprints that are welcoming and engaging and DrupalCons are no different. Beginning planning a few months in advance of the Con, this team takes on 9 days of sprint coordination (all those extended sprints on the weekends before and after the Con, Monday Contribution Sprints, Sprint Lounge during the week and Friday Sprint Day). They also have a booth in the Exhibit Hall where you can learn about sprinting, contributing and how you can get involved. They also work to lead an amazing group of additional volunteer Sprint Mentors who help make these sprints a learning experience for many newer contributors.
- Sprint Mentors - this group of sometimes up to 75 is mainly recognizable in their bright colored Con shirts on Fridays - helping to make sure new contributors are set-up to learn how to give back to Drupal. These mentors come from around the world and attend a training on being mentors to hundreds of DrupalCon attendees and truly dedicate their time and energy to the community with this role.
- Community Leaders - after helping plan the big reveal of their city, the community leaders stay throughout the months before the Con to make sure that the Con gets an injection of the host city into the fun-filled week. If you’ve ever found a blog about local restaurants or learned about a popular app in a new country, the local community leads are more than likely to thank as the work to provide helpful content that makes your time in their city the best ever.
- Prenote Performers - now an institution at DrupalCon, the Prenote has become a staple of Con content. The known suspects as well as local participants put in countless hours of time to craft a script, original songs and multiple antics that share the story of Drupal while making us laugh -- kicking the Con off right.
Apart from the Program Team, there are still many more volunteers who give time and knowledge to making DrupalCon special. Below are some of the many ways that volunteers are involved with shaping the Con:
- Speakers - although the speakers get a free ticket to the Con, we consider them volunteers because in choosing to speak at DrupalCon they are providing us with an incredible session that takes a lot of time and energy to create. Many hours go into a single presentation before you hear it at the Con, and with over 150 speakers at DrupalCon New Orleans, we are thankful to have so many talented volunteers sharing their experience with our Drupalistas.
- On-site Volunteers - the days before the Con involve over 50 volunteers who help us prepare for the barrage of Drupalers who arrive to enjoy a week of all things Drupal. From organizing over 3,000 t-shirts to stuffing that tote bag you get with multiple sponsor goodies, this power-team of volunteers are like a machine and deserve a huge round of applause for hard work. Once those tasks are complete, we have many volunteers who also help at the registration desk, counting session room attendance, and checking in with sponsors. There is literally of sea of volunteers at all times making sure DrupalCon is going smoothly.
- Recurring Con Volunteers - some volunteers take on an element of the Con and just own it. Group photos and photography shots come from an amazing photography team composed of new volunteer photographers and some that have been taking photos at Drupal events for years. Our social media team is on point year-round to make sure that you’re always getting the most up-to-date info about the next Con. These volunteers have become almost permanent extensions of our Drupal Association team. We're grateful to work with our recurring volunteers because not only do they rock at what they do, but gosh, they're fun!
- The Community Working Group - with the Code of Conduct in effect at every Con, this group might go unnoticed but plays a huge role in making DrupalCon welcoming and inclusive for all attendees. Available to mediate and work through incidents, this group is an important part of making a Con a Con.
As you can see, when we say this couldn’t happen without the volunteers, we MEAN IT.
I consider myself very lucky to primarily work with volunteers around the world who are so passionate and invested in creating a DrupalCon for you. I spend a lot of time on Zoom calls and in Slack channels with many of these volunteers. During working hours, on weekends, and at the event itself, these volunteers put a lot of themselves into these Cons and I sometimes step back and appreciate how incredible the Drupal community is.
I do my best to thank these volunteers often, reminding myself that each and everyone of them has a life and other priorities and that they are choosing to make DrupalCon important, but as it is National Volunteer Week, I would like to take a moment to list the DrupalCon New Orleans volunteers below and specifically say THANK YOU for all of your hard work - it is valued and appreciated not only by the team at the Drupal Association but by the community as well.Program Volunteers
Pamela Barone, Donna Benjamin, Pedro Cambra, Michael Cannon, Ian Carrico, Karyn Cassio, Stuart Clark, Matt Davis, Jess Dearie, Shawn DeArmond, Jeff Diecks, Mauricio Dinarte, Robert Douglass, Larry Garfield, Rob Gill, Becca Goodman, Paul Grotevant, Adam Hill, Lucas Hedding, David Hwang, Paul Johnson, Sherri Johnson, Adam Juran, Alex Laughnan, Dan Linn, Greg Lund-Chaix, Alina Mackenzie, Kathryn McClintock, Jeffrey McGuire, Ashok Modi, Diana Montalion, Mike Nielson, Steve Parks, Jon Peck, Joel Pittet, Koen Platteeuw, Tim Plunkett, Ryan Price, Justin Rhodes, Jason Savino, Michael Schmid, Sabrina Schmidt, Eric Schmidt, Eric Sembrat, Seth Silesky, Lauren Smith, Nikki Stevens, Joe Stewart, Ashleigh Thevenet, Cathy Theys, Campbell Vertesi, Shannon Vettes, Jason Want, Heather White, Jason YeeSprint Mentors
Alina Mackenzie (alimac), Adam Smeets (asmeets), Ravindra Singh (RavindraSingh), Cathy Theys (YesCT), Gobinath Mallaiyan (gobinathm), David Valdez (gnuget), Aman Kanoria (amankanoria), Joël Pittet (joelpittet), John Cook (John Cook), Chris McCafferty (cilefen), David Hernandez (davidhernandez), manmohan bisht (manmohandream), Mike Keran (mikeker), Ashwini Kumar (ashwinikumar), Eleanor Wai (eleanor_wai), Mauricio Dinarte (dinarcon), Prabhu Narayanpethkar (prabhurajn654), Maninder Singh (Maninders), Maninder Singh (Maninders), Lucas Hedding (heddn), Hitesh Jain (hitesh-jain), Steve Purkiss (stevepurkiss), Anto Jose (antojose), Piyuesh Kumar (piyuesh23), Saket Kumar (saki007ster), Manauwar Alam (manauwarsheikh), Les Lim (Les Lim), Ajit Shinde (AjitS), Marc Drummond (mdrummond), Nikki Stevens (drnikki), Neetu Morwani (neetu morwani), Prashant Goel (prashantgoel), Tim Erickson (stpaultim), Daniel Carvalhinho (dscl), Lalit Nirban (lalit3007), Joaz Rivera (m3chas), Junaid Masoodi (junaidmasoodi), Christian Manalansan (cmanalansan), Blake Hall (blakehall), Abhishek Anand (abhishek-anand), Amber Matz (Amber Himes Matz), Darryl Norris (darol100) David Needham (davidneedham), Kristin Bradham (kristink2), Diana VanRooy (thenyouDi), Marc Isaacson (vegantriathlete), Carlos Ospina (camoa), Patrick Storey (Patrick Storey), William Hetherington (willwh), Ravish Gupta (ravyg), Valery Lourie (valthebald) Seth Silesky (sethsilesky), Stuart Clark (Deciphered), Barbara Errickson (barbarae), Cristina Chumillas (ckrina)Speakers
Hussain Abbas, Mary Albert, John Albin Wilkins, Kelly Albrecht, Greg Anderson, Geoff Appleby, Ronald Ashri, Ryan Aslett, Morten Birch, Kristina Bjoran, Abe Brewster, Jesse Browne, Amitai Burstein, Angie Byron, Ian Carrico, Leigh Carver, Karyn Cassio, Marji Cermak, Matt Cheney, Gus Childs, Chaz Chumley, Courtney Clark, Casey Cobb, Ashish Dalvi, Matt Davis, Aimee Degnan, George Demet, Alex Dergachev, Suzanne Dergacheva, Nikhil Deshpande, Frederic Dewinne, Jeff Diecks, Daniel Dreier, Marc Drummond, Jeff Eaton, Stephanie El-Hajj, Adam Englander, Brad Erickson, Lauri Eskola, Edward Faulkner, Mark Ferree, John Ferris, Jessi Fischer, Fabian Franz, Pieter Frenssen, Larry Garfield, Yuriy Gerasimov, Aditya Ghan, Mike Gifford, Matt Glaman, Micah Godbolt, Drew Gorton, Nicolas Grekas, Rudy Grigar, Jody Hamilton, Mike Herchel, David Hernandez, Michael Hess, Jason Hibbets, Amber Himes Matz, Mikkel Høgh, Gábor Hojtsy, Chris Hoult, David Hwang, Marcus Iannozzi, Allie Jones, Adam Juran, Adam Kapp, John Kary, John Kennedy, Greg Knaddison, Randall Knutson, Josh Koenig, Charles Kreitzberg, Michelle Krejci, Kat Kuhl, Ashwini Kumar, Saket Kumar, Piyuesh Kumar, Wim Leers, Brian Lewis, Les Lim, Dan Linn, Clay Marshall, Tom Martin, Sophie Matson, Jeffrey McGuire, Catharine McNally, Oscar Merida, Steven Merrill, Brett Meyer, Michael Miles, Josh Miller, Tim Millwood, Igor Minar, Gaurav Mishra, Jesus Molivas, John Money, Jess Mybro, David Needham, Narayan Newton, Dani Nordin, Darryl Norris, Ron Northcutt, Dick Olsson, John Ouellet, Jason Pamentalm, Jon Peck, Steve Persch, Piyush Poddar, Kristen Pol, Fabien Potencier, Alex Pott, Taco Potze, Ellie Power, Luke Probasco, Ilan Rabinovitch, Scott Reeves, Dave Reid, Adrian Rollett, Chris Rooney, Chris Russo, Susan Rust, Terrence Ryan, Peter Sawczynec, Dave Sawyer, Michael Schmid, Roy Scholton, Michael Sherron, Joe Shindelar, Sebastian Siemssen, Michael Silverman, Preston So, David Spira, Anne Stefanyk, Nikki Stevens, Karen Stevenson, Nick Stielau, Matt Stratton, David Strauss, Ryan Szrama, Patrick Teglia, Chris Teitzel, Dave Terry, Kyle Theobald, Ashleigh Thevenet, Bjorn Thomson, Travis Tidwell, Matthew Tift, Howard Tizzo, Vanessa Turke, Tatiana Ugrimova, Chris Urban, Kristof Van Tomme, Jeff Walpole, Ryan Weaver, Daniel Wehner, Moshe Weitzman, Lynn Winter, Peter Wolanin, Chris Wright, Bojan Živanović, Helena Zubkow
Image credit goes to the following photographers:
DrupalCon Asia Volunteer Selfie : Michael Cannon
Education Summit Meeting : Paul Johnson
Zoom Screenshot Photo : David Hwang
DrupalCon Los Angeles Sprint Mentors: Jared Smith
The Drupal Association is seeking a Design Partner for creative and graphic design services for the 2017 European DrupalCon. We’re looking for people who understand that each DrupalCon is a singular expression of the Drupal community, DrupalCon location, software innovation, and extreme nerdiness and know how to turn this into compelling designs that are functional, fun, and make people look twice.
The Design Partner’s main responsibilities include:
- Site design
- Digital and print graphic design
- Overall conference branding that captures the flair and flavor of the host community
Scope of Work
The Design Partner’s work will reinforce a positive brand image of DrupalCon to attendees and within the Drupal community in the months leading up to, and during, the conference. The design should reflect DrupalCon’s position as a major international software conference and the local flavor that makes the host city an exciting location for the event.
The Scope of Work may include (but is not limited to) the following:
- Overall creative design of DrupalCon conference
- Digital outreach: newsletter templates, social media profiles (theme/icons), badges, ads
- Signage: venue signage, banners, sponsor signs
- Materials: slide decks, volunteer/staff clothing, giveaway item
- Print: letterhead/templates, badgelettes, sponsorship guide
- Style guide: production and use guidelines
These compositions consist of design elements, typography treatments, and a branding style guide.
Development Approach (Website)
The DrupalCon website will be developed using the COD installation profile. The Drupal Association staff will build the website from COD. Our Design Partner will be heavily involved in creation of the new design, and will receive several rounds of input from the local community.
The Design Partner will coordinate final design deliverables and production schedule with Drupal Association staff, and will actively participate in weekly planning meetings.
All proposals submitted in response to this call should directly address fulfillment and qualifications of this scope of work and should include the following:
- Company overview (company size, background, etc)
- Company qualifications (experience with this scope/project)
- Work samples (examples of artwork/sites/print deliverables)
- Any relevant involvement with the Drupal community
Submit proposals to: Amanda Gonser, Lead DrupalCon Coordinator via email email@example.com.
The respondent whose proposal best meets the needs of the project will be selected according to the following criteria:
- Thoroughness of proposal
- Demonstrated understanding of the project
- Quality of work samples provided
- Outcome phone/skype interview
- Availability and responsiveness of project team
Designer Selection Timeframe
Release RFP April 1
Bid deadline April 15
Interviews during late April
Selection notification made by May 25
The Drupal Association’s budget for DrupalCon design work is a fixed amount of $25,000. The design company will also receive public recognition on the site via footer credits and volunteer credits, and will receive a Silver Sponsorship for the 2017 European DrupalCon.
At the Drupal Association, we love to highlight that contribution comes in all forms. We are extremely grateful to the Association board members who contribute an enormous amount of time and are so generous with their knowledge and contacts in building a stronger Drupal community. Anyone who has ever served on or worked with a board knows that it's important, hard, and sometimes fun work.
We're thrilled that two more folks are joining us on the board. Help us welcome them both:Steve Francia, Class Director
Steve Francia was just nominated and elected to a Class Director seat on the board, a three year term. Steve Francia is a very active member of the open source community. He has been responsible for two of open source's largest projects as the Chief Operator of the Docker project and the Chief Developer Advocate of MongoDB, as well as creating some of the top community-based open source projects: Hugo, spf13-vim, Cobra and Viper. He has spoken all over the world delivering inspiring talks and workshops and has even organized a few conferences. He's written books for O'Reilly, blogs at http://spf13.com and tweets as @spf13. He's used Drupal since Drupal 4. He lives outside NYC and enjoys having fun outdoors with his wife and four children.Shyamala Rajaram, At-Large Director
Shyamala Rajaram is the newly elected At-Large Director. With over a decade of experience in designing and developing solutions using open source platforms, Shyamala has acquired a rich and varied expertise in many different technologies related to web, mobile and cloud. She is a co-founder and Director of Social Media Solutions at UniMity Solutions based in Chennai, India. Shyamala manages and builds the Drupal Solutions Practice at UniMity, including their hugely popular Drupal-based Social Workspace platform. Shyamala is an active participant in the Drupal community and has made contributions to the enhancements, usage and adoption of Drupal (Drupal.org redesign and Drupal 8 Mobile initiative being the main ones). She is an Engineer from the Indian Institute of Technology, Madras—one of India’s premier technology institutions.
The Drupal.org Engineering team is on a roll with many new improvements, thanks to Drupal organizations who fund their work by joining the Supporting Partner Program. In March alone, the team made more progress on Composer for Drupal, content restructuring of the Documentation section, and better data insight into organizational contributions. You can see the full list of their improvements here— we hope you'll be impressed by all their hard work.
Many of the improvements to Drupal.org have been funded by our 112 Supporting Partners. These are Drupal agencies, Drupal customers, hosting companies, and software companies who want to give back to the community that helps them succeed. The program allows organizations to crowdsource the investment needed to improve the Drupal.org contribution journey, making it faster and easier for community members to innovate the software. Plus, the funding improves the Drupal.org adoption journey so it’s easier for organizations to make Drupal their platform of choice. The supporting partner program is a real partnership between the Drupal Association and organizations to sustain the Project with these kinds of improvements.
Several companies joined or renewed their membership this past quarter. We'd like to say a big thank you to these companies:
- Breakthrough Technologies
- Catalyst IT
- Cheeky Monkey Media
- Elevated Third Interactive Agency
- Project Ricochet
- Srijan Technologies
- Therefore Interactive Inc.
If you want to give back to the Project and help fund this important work, please contact our COO, Megan Sanicki, for details. Your participation will fund Drupal.org improvements (as found on our roadmap).
Everyone on the staff and Board of the Drupal Association would like to congratulate our newest board member:
In addition to congratulating Shyamala, please join me in thanking the 22 other candidates who put themselves out there in service of Drupal and volunteered for election. It's brave and generous to nominate yourself for this work, and we should all be very grateful that our community has so many people willing to contribute this way.
This was the fifth election we've held for at-large board seats at the Drupal Association. This year, we had two specific goals for the elections:
- More candidate diversity - We had four female candidates this year, representing 17% of the field. This was a big improvement over last year, when there was one female candidate. We also had 23 candidates, from 12 different countries—including South American and Asian countries.
- Increase voter turnout - This year, 2,126 of you voted in our election. Our pool of eligible voters was 135,747, so that means our voter turnout was 1.56%. This is still low, but a vast improvement over the last election, which saw a .89% turnout.
Our next steps will be to reach out to the candidates for their evaluation of the elections experience. We also want to hear from you. Please tell us about your experience with the elections process in the comments below so that we can include them in our planning for the 2017 elections.
And finally, you may recall that after some public conversation last year we also changed our self-nomination process in 2016 to ask candidates to opt-in for sharing their election voting data. We use IRV voting and are glad to share that data with you. We've redacted the names of candidates who did not opt-in to share their voting data, though vote counts are still represented.
Counting votes using Instant Runoff Voting. There were 23 candidates competing for 1 seats. The number of voters was 2,126 and there were 2,126 valid votes.
- Round 1
- Round 2
- Round 3
- Round 4
- Round 5
- Round 6
- Round 7
- Round 8
- Round 9
- Round 10
- Round 11
- Round 12
- Round 13
- Round 14
- Round 15
- Round 16
- Round 17
- Round 18
- Round 19
- Round 20
- Round 21
- Round 22
The bar charts below show the vote counts for each candidate in each round. Place the mouse over a bar to see the number of votes.
- Yellow — Votes carried over from the previous round.
- Green — Votes received in this round.
- Red — Votes transferred away in this round.
A candidate's votes in a round is the sum of the yellow and green bars. Since the green and red bars represent votes being transferred, the sum of the green and red bars is the same.
The exhausted bar represents votes where the voter did not indicate a next preference and thus there were no candidates to transfer the vote to. The threshold bar (where shown) indicates the number of votes that ensures that a candidate will win a seat.
Count of first choices.
Count after eliminating tolabs and transferring votes.
Count after eliminating shehrevar and transferring votes.
Count after eliminating Kenndillard and transferring votes.
Count after eliminating krylov and transferring votes.
Count after eliminating knibals and transferring votes.
Count after eliminating Redacted and transferring votes.
Count after eliminating tomgrandy and transferring votes.
Count after eliminating Redacted and transferring votes.
Count after eliminating Gemdev and transferring votes.
Count after eliminating TheJustinRhodes and transferring votes.
Count after eliminating voidberg and transferring votes.
Count after eliminating drupalviking and transferring votes.
Count after eliminating Redacted and transferring votes.
Count after eliminating jpamental and transferring votes.
Count after eliminating davidhernandez and transferring votes.
Count after eliminating johnkennedy and transferring votes.
Count after eliminating rachit_gupta and transferring votes.
Count after eliminating svettes and transferring votes.
Count after eliminating danigrrl and transferring votes.
Count after eliminating MatthewS and transferring votes.
Count after eliminating -enzo- and transferring votes. Candidate Shyamala is elected.
Winner is Shyamala.
Flickr photo: Clyde Robinson
The Drupal community is diverse. We're from different places. We speak different languages, code in different languages, and use Drupal in different ways. But the one thing we all have in common is that we care about the fate of Drupal. We invest our time, intellect, and emotions into this project. And we want that investment to make the project successful.
We have a lot to be proud of. In the last few years, Drupal use and community contribution has grown tremendously. Some metrics—like comments and commits created each month—are available at drupal.org/metrics. We share project usage and track BuiltWith statistics. We've also started reflecting company contributions in the marketplace and on organizations list.
The Association's mission is to unite a global open source community to build and promote Drupal. One of its 3-to-5 year goals is to ensure the sustainability of our project and community. To meet that goal, we need to get much better as a community at answering the question: Is Drupal healthy? But that's not an easy question to answer.
In the last board meeting, board members and staff talked about what kinds of metrics show health. In this post, I share some of that thinking, and ask for your ideas. But before we get into recommendations, let’s start at the beginning.What's project health?
Association staff and board members use “project health” as shorthand for project success. "Health" is robust. Think about your own health. You might think first about physical aspects (Do I have a fever?). But you also might think about emotional aspects, like depression or stress. You may even think about social aspects (Do I have the right people around me to support me and keep me focused on the right habits?). Health isn't binary. Health is multi-dimensional.
So, too, is the health of an open source project. It's easy to take the temperature of a project with metrics like usage or number of committers. But to understand the complexity of our project's health, we need broader measurements. In our work on staff, we've defined four dimensions of product health1 we think we need to explore:
- Product: whether the business of the Drupal product (the software) is sound. Examples of areas to explore: marketshare; Drupal businesses' revenue.
- People: whether we have the right kinds of people contributing the right kinds of things. Examples of areas to explore: number of contributors; kinds of contributions; contributors' skills.
- Process: how the way we do things contributes to the project. Examples of areas to explore: ability to meet published release dates; succession planning.
- Systems: whether we use the right tools. Examples of areas to explore: testing times for DrupalCI; amount of documentation edits; responses to posts in forums; issue resolutions; commits and integrated repositories.
There's the ideal, and then there's reality. We know we won't be able to track everything we want to. So, we'll have to make choices. We'll have to choose metrics that give us directional, even if not precise, accuracy. So, what are some of our limitations?
The future of the project
Knowing what categories of metrics we need to track is necessary, but not enough. Setting metrics also requires knowing where we want the project to go. Taking your temperature is only helpful if you know what you want it to be (and what it means if it's not).
Tracking project health is an Association priority, but it’s not its only mandate. It has to consider the time and expense invested in DrupalCons and Drupal.org too, for example. Unfortunately, budget limitations mean not hiring analysts or consultants to help. For the most part, they mean working with the (wonderful) people already on staff.
So, for example, measuring contribution only by code or comment attribution isn't enough. People contribute in so many ways. (There's even an issue open on this topic already.) Will measuring contribution expand to include other things? Yes. But will it also likely still not give some contributions the attention they deserve? Unfortunately, yes. Hard choices will mean we'll all have to accept some less than ideal outcomes.
Balancing competing frames and other fun factors
Once we know what outcome we want and have found things we can actually measure, we'll still need to do more. Any metric we choose has to also align with the project's mission and our community’s values. We also can't be too dependent on internal metrics. We'll have to measure our success with external indicators too. (See? There's a lot to think about here!)Examples, please
There’s good news and bad news here. The good news is that we are definitely not alone. Many software projects—including open source projects—have worked on these same issues. There are resources all around us. We've created lists of some of them already.
Open source projects on GitHub
- Symfony Code Stats
- Symfony Contributors
- Estimating the Total Development Cost of Linux Foundation’s Collaborative Projects
- Linux Jobs Report 2015
- Who Writes Linux: Linux Kernel Development: How Fast it is Going, Who is Doing It, What They are Doing, and Who is Sponsoring It
- WordPress Activity
- Ultimate List of WordPress Statistics
- Apache development statistics
- Ruby on Rails contributors
There's a lot to consider when we think about the health of the Drupal project. We've just begun this conversation and want to make sure you're part of it from the beginning. So, now we turn things over to you.
Which metrics are indicative of Drupal project health? Share your ideas in the comments section. We'll include your feedback in a document we'll share with you.
Flickr photo: Thomas Haynie
Voting is now open for the 2016 At-Large Board positions for the Drupal Association! If you haven't yet, check out the candidate profiles and review the Meet the Candidate sessions (we ran three) that we held. Get to know your candidates, and then get ready vote.
How does voting work? Voting is open to all individuals who have a Drupal.org account by the time nominations open and who have logged in at least once in the past year. These individuals' accounts will be added to the voters list on association.drupal.org and they will have access to the voting.
To vote, you will rank candidates in order of your preference (1st, 2nd, 3rd, etc.). The results will be calculated using an "instant runoff" method. For an accessible explanation of how instant runoff vote tabulation works, see the this video.
Elections will be held from 7 March through 18 March (midnight UTC) 2015. During this period, you can still review and comment on candidate profiles.
Have questions? Contact Drupal Association Executive Director Holly Ross.
Hello, Drupal world! We are thrilled to be able to give you an inside peek at what goes into planning DrupalCons. Throughout 2016, we’ll share a series of posts, and a few webcasts, to show some behind-the-scenes aspects of DrupalCon. First, we met the events team that produces 3 Cons a year. Now, meet the production team that makes DrupalCon a reality.
The Drupal Association aims to produce DrupalCon conferences in alignment with our commitment to environmental and social responsibility. As the production manager, I have an important role in making sure we make informed purchasing decisions and form strategic partnerships with our venue and vendors. I’d like to share just a few of the things we address behind the scenes during the planning process.First Step: Selecting a Venue
The planning for a DrupalCon starts a few years prior to the event date, when we select a venue. Hosting a sustainable event is only possible if the venue’s infrastructure and operations practices are already "green", so vetting the venue is a big criteria.
The good news: For the most part, all new convention centers in the U.S. are built according to LEED standards. By selecting LEED certified buildings we are supporting these principles. Energy efficiency is another criteria we scrutinize: we look for ENERGY STAR® standards. We're often encouraged to see that many convention centers go beyond simply having smart energy management systems -- it is not uncommon to find solar power systems and green roofs. We are also pleased to see a surprising number of bee hives appearing on those living roofs, supporting local bee populations and providing the convention center kitchen with fresh honey.
Each venue comes with a small number of exclusive vendors, and the one with the highest opportunity to affect the sustainability of operations is the in-house caterer. We have the ability to request that our meal and break activities are carried out with the lightest impact possible. We build these requests into our catering contract when we commit to working with the venue.
Catering for 3500+ people for most of a week is a daunting thing to consider. Catering is a complex set of operations that affects our air, land, and water supply, and these activities represent the greatest opportunity for us to make a difference. Here's what we do:
- We request that the caterer source from local farms when possible, resulting in low food miles and lower greenhouse gas emissions. In order be good partners, we often agree on a “chef’s choice” menu. What this means is that the chef does not have to commit to a menu until about 60 days prior to the event, when it is clear what items are abundant and locally available.
We aim to conserve our natural resources. To do that we avoid use of non-renewable resources, and live the mantra "Reduce, Reuse, and Recycle" to limit our additions to the community landfill. Here are a few of the ways we lessen our impact:
- We request that our beverages be served via bulk containers, such as water bubblers or pitchers of ice tea and lemonade. This avoids what would be the use and disposal of over 10,000 water bottles at each U.S. event, and 5,000 water bottles at our European event.
- We take the box out of the “box lunch.” No matter how recyclable the cardboard is, the box has a useful life of about 5 minutes. We avoid manufacturing energy and pollution, and avoid a large volume of cardboard that needs to be recycled just by saying "No box please.”
- We request biodegradable or compostable serving ware. We also request that recycling containers be placed throughout the venue to divert almost all waste from community landfills. Our goal is to make sure that almost all materials are recycled or composted.
After the venue is selected, we set our sights on other strategic partners.
- For our printed materials, we specify to our vendors that they use 100% recyclable materials, and print with FSC-approved paper and organic inks.
- We rent our audio-visual and other equipment rather than purchase it, as this avoids the unnecessary extraction of raw materials and manufacturing waste.
- We source many things from vendors in the city we are working in. For example our signage is always printed locally to avoid unnecessary packaging and to reduce emissions generated from transportation. This comes with the added bonus of putting even more money into the local economy, too!
- We request that all leftover food be donated to food banks or other agencies that deliver food to those who need it.
- We donate leftover T-shirts and tote bags to local agencies who distribute them to people in need.
For those in the community who are curious about why we put so much effort into making DrupalCon as ecologically sustainable as possible, it's important to understand the wider events industry. From public conferences, to industry meetings, to world summits, events are where people gather to announce academic breakthroughs, discuss industry changes and societal challenges, and put forth our best ideas and thought leadership. As our world becomes increasingly connected, it is clear that live events are not going away.
Unfortunately, there is a shadow side to the event industry: large-scale events have a big environmental and social impact. Environmental impacts include landfill waste, toxics, and water usage. Social impacts can involve human and labor rights in a global supply chain.
Carbon emission data can give a sense of the scale of this industry and its footprint. There are 1.8 million meetings (the industry term for any sort of live conference or summit event) in the U.S. alone each year. Meetgreen, a green meetings leader, calculates that each attendee at an average event produces 0.176 metric tons (MT) of CO2 per event day. According to the EPA, in 2012 in the U.S. alone, 225 million people attended meetings. With 225 million participants attending an average of two days per event, that’s 79.2 million MT of CO2 per year. How much is that? According to the EPA, that’s the same amount of CO2 emitted by 16.6 million cars for an entire year, which is more than all the cars currently registered in all of California.
All of us who plan events need to understand how the decisions we make at even the smallest level contribute to a global meeting industry impact. The Drupal Association aims to act on our values by making informed decisions in order to minimize our impact and support vendors and suppliers who are making a difference.
Diana Connolly is the production manager for DrupalCon. She founded the event production company Groundswell Marketing in 1994, after a combined ten years in corporate marketing and the trade show exhibit industry. Her clients are primarily in the technology sector, and range from startups to the Fortune 100. Ms. Connolly has an MBA in Sustainable Enterprise and is passionate about triple bottom line results. You can learn more at Groundswell Marketing, or contact Diana via LinkedIn or e-mail.
Huh? What are we Electing?
In case you missed it, the Drupal community is electing one candidate to serve a two-year term on the Drupal Association Board of Directors. There are two At-Large (community elected) seats on the Board. The other seat is currently held by Addison Berry. We've got a really global slate of candidates to consider, and we encourage you to get to know them by listening to the Meet the Candidates sessions and asking them questions on their candidate profile pages.
Who can vote?
Voting is open to all individuals who have a Drupal.org account by the time nominations opened and who have logged in at least once in the past year. These individuals' accounts will be added to the voters list on association.drupal.org and they will have access to the voting.
To vote, you will rank candidates in order of your preference (1st, 2nd, 3rd, etc.). The results will be calculated using an "instant runoff" method. For an accessible explanation of how instant runoff vote tabulation works, see videos linked in this discussion.
Voting will be held from 7 March, 2016 through 18 March, 2016. During this period, you can review and comment on candidate profiles on assoc.drupal.org.
Flickr photo: Clyde Robinson
Last May we released issue credits and comment attributions on Drupal.org. At that time, I suspected that this would tell us two things: that contribution to Drupal is funded more by companies that pure volunteerism and that the diversity of contributors would be greater than we are able to see in Drupal Cores (not that Drupal Cores is not awesome, it just does only what it does). The jury is still out on my first point — we are just getting the right quantity of commits with this data and we haven't done a real analysis. But the second point proved to be true very quickly. Especially when it comes to India.
In preparing for my #Driesnote intro at DrupalCon Asia, I asked Josh to pull some stats for me. Based on his reasearch, we learned some really interesting numbers:
- India is the second largest region of users for Drupal.org—behind only the United States in traffic. In 2014, India represented 9.6% of our traffic (that's 4,691,785 sessions)." For 2015, the percentage of traffic from India has gone up to 10.48%—still second largest.
- As of February 2nd, 1,290 credits were awarded to users who from reported timezones in Asia. (Out of a total of 8819 credits awarded.) That is 14.6% of issue credits!
- 1815 of total credits (Nov-Jan) were for Drupal core. 279 of those credits were from Asia. (15.4% of credits awarded.)
- 47 organizations from Asia are listed in the Drupal Marketplace. 9 are Drupal Association Supporting Partners.
So I knew, going in that Asia, and India in particular, was having a really big impact on the project, approaching the US and a combined Europe for participation in code. We also knew that India had a huge camp scene, with many camps of several hundered, and one above 1,000, attendees.
Asia, by the Drupal numbers, is truly impressive. But numbers are only half the story.
When I was pregnant, my friends and relatives would all give me lots of advice. One thing I heard all the time was "Sleep when the baby sleeps. You are going to be exhausted, let the house chores go and let yourself rest instead." At the time, I thought sleep was something you did when there was nothing left to do with your day, but I tried to internalize that and planned for it in my maternity leave. I knew I was going to be tired. Then I actually had the baby. I was tired. TIRED. And I went from intellectually understanding that I would need more rest to knowing it with every cell of my body, because I was living it.
DrupalCon Asia was like that for me. I knew intellectually (because of the numbers) that this was a vibrant, active community. It was not until I saw that community in action that I realized just what that really meant. I saw them organize Bollywood style flash mobs and create intricate replicas of the conferene logo with sand. (SAND!) I listened to and talked with hundreds of people who wanted to share their Drupal experience. I posed for a lot of selfies. A LOT OF SELFIES.Working in the future
I loved joking with colleagues back in the states that I was tweeting from the future becasue time zones are fun that way. I even made the joke from the main stage. It ocurred to me later that (time zones aside) it really is true. In many ways, Asia is the future of Drupal. We still have lots of room to grow project adoption and contribution in the US and Europe, but Asia is probably smack dab in the middle of its hockey stick moment. We're going to see a lot more users, a lot more contribution, and a lot more adopters from that continent in the next 5 years. Given that there are about 1.2 billion people in India alone (the country leading the growth in Asia), simple math tells us that this region will easily eclipse every other region in our community if it can stay the course.
The work coming out of Asia is also future forward. With companies like TCS, Cap Gemini, and Accenture heavily invested in the success of the project, we are seeing more and more name brand and enterprise adoptions of Drupal coming out of Asia. We also have an Asian Drupal shop community that is pushing the boundaries of Drupal away from strictly CMS and into the app server and other headless use cases. Axelernt, Blisstering Solutions, and Srijan are just a few of the companies I talked to at the Con, and I learned that they are all investing heavily into the future of Drupal that Dries keeps referencing.Embracing the Future
I filled in for Megan Sanicki on a panel at the Con discussing contribution in India. One of the main questions we explored was what Indians needed to do to make a bigger difference for Drupal. There were lots of great ideas about how and where to contribute to get more recognition and responsibility within the community. But most impoertantly, I think Drupal leadership — in the project and in the Association — need to be proactively searching for the leaders from Asia who can serve in visible leadership roles. If Asia is going to increase in importance to the project, we need to embrace that future now.
I am really terrible about prognisticating, but I know one thing is true: Drupal five years from now is going to look radically different from Drupal today. The code, the product, and the community will not be the same. In many ways, that's exciting: the future holds new possibilities, new people, and new fun! In other ways, it's sad: old traditions and long-time community members lost. In other ways, it's scary: you wonder, "what will my role be? Will I matter to the project then?" But change IS coming, so we're going to have to do our best to tackle all those feelings using our community values and lots of communication.
When it comes to our future, I am certain of this though: the Asian community is ready for it. And if the wider Drupal community is smart, we'll be ready for them
Flickr photo: Michael Cannon
Hello, Drupal world! We are thrilled to be able to give you an inside peek at what goes into planning DrupalCons. Throughout 2016, we’ll share a series of posts, and a few webcasts, to show some behind-the-scenes aspects of DrupalCon. First, meet the team that produces 3 Cons a year!Rachel Friesen: Events Manager
What do you do for DrupalCons?
I consider myself a full-time plate-spinner. I focus on our DrupalCon planning and strategy, high level project management, site selection and managing our awesome Events Team. I work to distill the goals of the community, the Drupal Association, and sponsors to make sure we have healthy and sustainable events.
I’m also the financial gatekeeper for the Cons, so I manage our budget of ticket revenue and expenses for about 6 DrupalCons at a time. (Yep! We're working that far out & beyond!)
Favorite part of your job?
Telling Drupal community leads that we're bringing DrupalCon to their city. People are so excited and it's such a thrill to be able to bring the DrupalCon spotlight to their nook of the earth.
Favorite DrupalCon Moment?
My favorite DrupalCon moment was the front line band that came out to officially introduce DrupalCon New Orleans. I just really wanted people to feel New Orleans-y goosebumps when we announced the next location. It was important to me that people felt a connection with the fun vibe that New Orleans has, and felt compelled to come to DrupalCon New Orleans!
What about DrupalCons has surprised you?
One of the more interesting things to me is the random clauses that convention centers have banned in their contracts. I know it sounds weird, but there's specifically a “no glitter” clause in our New Orleans contract. It makes me daydream about what type of glitter incident lead to that clause being required. Ah, fun!Amanda Gonser: Lead DrupalCon Coordinator
What do you do for DrupalCons?
I manage various community volunteer teams that select the content that goes on at DrupalCons. If you're attending a session, taking a training, networking at a summit, listening to a keynote or participating in sprints, I probably worked with some amazing volunteers to help make those things come to life.
I also work directly with the amazing local communities that host our Cons. We plan things like Trivia Night, Women in Drupal, and Extended Sprints. Last but not least, I work with our team on our site selection process for future Con sites (don't think you can sweet talk me though!).
Favorite part of your job?
I love the moment when I meet someone in person that I’ve been spending weeks on video calls with. I work with so many incredible community members who give a lot of their personal time and effort to these Cons. It's great to see them for the first time and give them a big Drupal hug. It makes seeing them at a Camp or at another Con a great moment to look forward to as well.
Favorite DrupalCon moment?
I think my favorite moment so far (because there’s a new favorite moment at each Con) was in DrupalCon Barcelona, when the Indian community got up to promote DrupalCon Asia. Between the dancing, the words, and the videos of so many Indian communities welcoming us to Mumbai, I was really touched and so excited about attending the Con. I've been in India for a month now, experiencing that amazing hospitality firsthand before the Con, and am sure that DrupalCon Asia will leave me with another favorite moment too.
What about DrupalCons has surprised you?
Having not come from a tech background, I feel like each day is its own opportunity to learn something new—about open source, Drupal, community management. There are so many things I can learn to better understand and serve all of the great Drupalistas who work to make DrupalCon happen.Tina Krauss: DrupalCon Coordinator
What do you do for DrupalCons?
I handle registration and am the first point of contact for DrupalCon attendees. If you submit a question or request through our contact forms, I'll most likely be the one responding to you. At DrupalCons, you can find me at the Registration Desk.
I also work on Drupal training courses and the Association's scholarship program. The rest of my time is filled with a lot of behind-the-scenes work on hotels, travel arrangements, event logistics, and production tasks.
Favorite part of your job?
I love traveling, and visiting exciting cities for work is a big bonus for me. Working with highly dedicated people from around the world and my amazing team at the Association are things I wouldn't want to miss either.
Favorite DrupalCon moment?
Hard to decide! Being surprised with a big birthday cake at DrupalCon Los Angeles was definitely a highlight, but I also enjoy the Association's traditional celebratory get-together on the last morning of the Con, when most of our work is done and we can look back at a successful event.
What about DrupalCons has surprised you?
How to work and have fun at the same time. I never thought this was possible. :)Tim Constien: Sponsorship Fulfillment Coordinator
What do you do for DrupalCons?
I work with all of our awesome sponsors, making sure that all of their benefits are fulfilled and maximized. It's important to me that they have a great experience sponsoring DrupalCon. It's always fun to see what they dream up as cool ways to support the community.
Favorite part of your job?
I love finally meeting all of the people I work with after months of emails and calls. I also enjoy the gratification of being the one to help guide newer sponsoring companies into the unique world of the Drupal.
Favorite DrupalCon moment?
What about DrupalCons has surprised you?
I think it's awesome to see how many companies, made up of extremely talented people, are truly invested in Drupal and its community.
Thanks for reading. Our next post will focus on the environmental and social responsibility work related to producing DrupalCons.Meet us in New Orleans
Nominations are now closed for the single At-Large seat on the Association Board of Directors. We have an astounding number of candidates from all over the world running for this seat. We're thrilled that so many of you are so invested in our community that you're taking this step. As with any election, we want to have an informed electorate. So, we invite you to get to know these candidates in a couple of important ways.Learn about the candidates online
Check out the slate of candidates and read what they had to say about their backgrounds and interest in serving on the board. Each candidate page also features a comments section where you can ask about their plans, hopes, and views for the Association and the project. We only ask that you use this comments section as a place to ask questions, not endorse candidates please.Join a Meet the Candidates webcast
In addition to the candidate profiles, we're hosting three live question and answer sessions where you can chime in and hear from the candidates directly. Not all candidates will be on each call, but don't worry! If you aren't able to connect with a candidate in one of the sessions, we'll be recording them, so you can check them out later. Here are the sessions (register at the links):
- 7 AM PST, US and Canada
- 10 AM EST, US and Canada
- 1 PM, São Paulo, Brasil
- 3 PM, London
- 11 PM, Beijing
- 2 AM, Wednesday, February 24, Sydney, Australia
- 12 PM PST, US and Canada
- 3 PM EST, US and Canada
- 5 PM, São Paulo, Brasil
- 8 PM, London
- 4 AM, Thursday, February 26, Beijing
- 7 AM, Thursday, February 26, Sydney, Australia
- 4:00 PM PST, US and Canada
- 7:00 PM EST, US and Canada
- 9:00 PM, São Paulo, Brasil
- 12:00 AM, Friday, February 26, London
- 8:00 AM, Friday, February 26, Beijing
- 11:00 AM, Friday, February 26, Sydney, Australia
I hope we'll hear from you during this important part of the elections process. And mark your calendars: voting begins on March 7!
We kicked off the 2016 Global Training Days on February 5th. Twenty-two sites held a training in 11 countries, making it a great start to all things training in 2016.
Training events were held all over the globe in a variety of spaces. From offices to the public library and spaces where public university and governmental institutions collaborated with private organizations, Drupal was brought to a wide audience. Trainers gave introductory lessons with demos and hands-on site building exercises to attendees. Thank you to everyone who participated!
Here are just a few of the tweets we received about the first of the 2016 Global Training Days.
— Neeraj Kumar (@neerajskydiver) February 6, 2016
— Lemberg Solutions (@lemberg_co_uk) February 8, 2016
— Bmeme (@bonsaimeme) February 5, 2016
Drupal Global Training DayGTD
— Drupal Hub (@thedrupalhub) February 5, 2016
From October 13 to December 30, 2015, we ran our biggest membership drive campaign ever. We did a lot of experimenting and I want to share some results and learnings with you.
But first, I'll tell you about our program. Drupal Association membership is for anyone who uses Drupal, and anyone who wants to support our community and the project through a donation of membership dues. Membership is one way to contribute to Drupal, but it is by no means the only way.The biggest accomplishment in this campaign: 10% growth
During the campaign period, we saw 10% overall growth in our membership (3,266 to 3,590 members). For the last two years over this same period of time, we had seen 1% growth in membership. Last year’s growth is a huge win.Goal vs actual
Our campaign goals were to raise $100,000 and to have 1,000 new members sign up.
The results looked more like this: $50,896 and 480 new members.
We also had 148 lapsed members return and our overall membership grew. Despite not hitting our goals, we are happy to have new and renewing members and some new knowledge about campaign content.Testing content
When the campaign launched on October 13, we put our first banner ever on drupal.org to test whether an increased presence on the site would make a difference in membership sales. The answer is a big Yes. There were spikes in membership sales around the times we launched and changed the content of the banners. The biggest day of sales took place on the day after the launch, Oct. 14, when 74 members paid dues.
On December 14, we refreshed the banner to include a photo and quote from a member who gave us a testimonial. We rotated the banners and a separate block on the drupal.org homepage until the end of the campaign to highlight a few members.
This graph shows the results during our December banner rotation period. There was a trough around the Christmas holiday, so testing this at a non-holiday time of year will be beneficial in a future campaign.What we learned
A greater drupal.org presence helps sell memberships, and being mindful about what content to show our active members is important for inspiring people to share the campaign. If members see a banner, they should easily be able to share it or hide it.
We need to keep telling your stories. I saw some of the members who gave testimonials were given kudos in the community. It feels good to see the faces of the community and to see just why you care. We have continued sharing stories, starting with DrupalCon Asia.
On days we launched banners or refreshed content, we saw the biggest sales spikes and flurries of social activity. The time of year when many people step away from their computers could impact campaign performance, so testing at another time of year should be done.
Thanks to everyone who participated in this campaign. From the 27 members who gave testimonials, to everyone who joined or renewed membership or encouraged the community to be a part of the drive, we appreciate your help.Membership
It’s a great time to be part of the Drupal Association. We’ve done some amazing work in the last few years, and we’re in a great position to work with the community to continue to improve and grow fully into our mission. As a Drupal Association At-Large Director, you’d be in the center of the action. The At-large Director position is specifically designed to ensure community representation on the Drupal Association board and we strongly encourage anyone with an interest to nominate themselves today.
The Board of Directors of the Drupal Association are responsible for financial oversight and setting the strategic direction of the Drupal Association. New board members will contribute to the strategic direction of the Drupal Association. Board members are advised of, but not responsible for matters related to the day to day operations of the Drupal Association, including program execution, staffing, etc. You can learn more about what’s expected of a board member in this post and presentation.
Directors are expected to contribute around five hours per month and attend two in-person meetings per year (financial assistance is available if required). All board members agree to meet the minimum requirements documented in the board member agreement.
Today we are opening the self-nomination form that allows you to throw your hat in the ring. We're looking to elect one candidate this year to serve a two-year term.How to Nominate Yourself
To nominate yourself, you should be prepared to answer a few questions:
- About Me: Tell us about yourself! Your background, how you got into Drupal, etc.
- Motivation: Why are you applying for a board position? What initiatives do you hope to help drive, or what perspectives are you going to try and represent?
- Experience: What Drupal community contributions have you taken part in (code, camps, etc.)? Do you have experience in financial oversight, developing business strategies, or organization governance?
- Availability: I am able to travel to three in-person board meetings per year (either self-funded, or with financial sponsorship)
- IRC Handle
- Twitter Handle
We've also made a few changes to the process based on community feedback from the 2015 election:
- We now display your username, not your given name, on your candidate profile to address privacy concerns that had been raised. Nominees should note that given names are required on legal documentation such as our 990 IRS filings, but we will do our best to preserve your privacy where we can.
- Updated sidebar block has more information about the elections, making it easier to the information you need.
- When you nominate yourself we will ask if you would like to opt-in to share your election results data. Last year was the first time we published full results from the vote data. Candidates that opt-in will have their name displayed next to their vote counts, as in this example from 2015.
We will also need to know that you are available for the next step in the process, meet the candidate sessions. We are hosting 3 sessions:
Meet the Candidate Web Conferences:
Tue 23 Feb 2016 at 16:00 UTC
- 7 AM PST Tue 23 Feb, US and Canada
- 10 AM EST Tue 23 Feb, US and Canada
- 1 PM Tue 23 Feb, Sao Paulo Brasil
- 3 PM Tue 23 Feb, London
- 11 PM Tue 23 Feb, Beijing
Wed 24 Feb 2016 at 21:00 UTC
- 12 PM PST Wed 24 Feb, US and Canada
- 3 PM EST Wed 24 Feb, US and Canada
- 5 PM Wed 24 Feb, Sao Paulo Brasil
- 8 PM Wed 24 Feb, London
- 4 AM Thu 26 Feb, Beijing
- 7 AM Thu 26 Feb, Sydney Australia
Thu 25 Feb 2016 at 01:00 UTC
- 4:00 PM PST Thu 25 Feb, US and Canada
- 7:00 PM EST Thu 25 Feb, US and Canada
- 9:00 PM Thu 25 Feb, Sau Paulo Brasil
- 12:00 AM Fri 26 Feb, London
- 8:00 AM Fri 26 Feb, Beijing
- 11:00 AM Fri 26 Feb, Sydney Australia
The nomination form will be open February 1, 2015 through February 20, 2015 at midnight UTC. For a thorough review of the process, please see our announcement blog post.
If you have any questions, please contact Holly Ross, Drupal Association Executive Director.
Flickr photo: Clyde Robinson
Happy birthday, Drupal community! Today is the Drupal project's 15th birthday. In honor of the upcoming year, we've put together a retrospective of some of the incredible changes and accomplishments we made together last year.
2015 was a landmark year for Drupal: between three DrupalCons, the release of Drupal 8, and numerous improvements to Drupal.org, there's a lot for everyone to be proud of. None of our amazing accomplishments would been possible without our community of passionate Drupalers. As you read the infographic, we invite you take a moment to congratulate yourself for all the ways that you've helped make the project strong. Because Drupal's 15th birthday isn't just an accomplishment for the software—it's an occasion to celebrate everyone who has helped get the entire project and the community to where they are today.
The Drupal community is full of people who make the world a brighter place. Now that we’ve made it through the holidays, we’d like to start the new year by winding up our 12 days of Drupal blog series. Thank you to our community for inspiring us every day.Mike Anello (ultimike)
One would think that Mike never has time for sleep. He has been a Drupal developer, trainer, and consultant for almost 10 years, as well as a Drupal 8 Core Migrate module contributor, and a volunteer manager of the Community Cultivation Grants program. Mike also helps produce the DrupalEasy podcast and trains new Drupalers via a career mentorship program. If all that wasn't enough, he also organizes the Florida Drupal user's group.
What Mike says about membership
I doubt that the Drupal project would be where it is today without the Drupal Association. It takes a dedicated team of professionals to keep the servers humming along as well as organizing multiple DrupalCons around the world.
It’s often the small things that go the longest way. During the DrupalCon Barcelona sprint, I met a gentleman whose goal was to figure out how to use a new feature of one of the migration-related contrib modules. I didn’t have much experience with it, but together we figured it out in short order. He was super-thankful and promised he would write up the documentation page for the feature. Even though it was a small moment, it was one of many made possible by the Association’s constant support of the community.
If you are not yet a member, join the Drupal Association and be part of our success together.Personal blog tags: Membershipcommunitymembership 2015 series