Global Training Days last weekend was a great success. There were 33 hosts from 21 countries who stepped up to introduce new people to Drupal in both half and full day sessions.
Thank you to the training companies, local groups, and site hosts who made the event possible. We were particularly excited to host a training at the Drupal Association office and we have to thank Gregory Boggs of ThinkShout for leading the full day training. Thanks to Gregory's good work, I started my week with a note from an attendee that said "I learned a lot, all while having a wonderful time!" It doesn't get much better than that.
We have one more GTD weekend this year: November 14th-15th. Join the 17 hosts who have already committed to train new Drupalers at https://assoc.drupal.org/sign-participate-drupal-global-training-days. Give a training in your community to get everyone started off in the right direction with Drupal.Personal blog tags: Drupal Global Training Day
One of our key values at the Drupal Association is communication:
We value communication. We seek community participation. We are open and transparent.
One of the ways that we try to live this value is by making our numbers -- both operating targets and financial -- available to the public. The monthly board reports share basic financial numbers and all our operational metrics. Once a quarter, we release full financial reports for the previous quarter. You can access all this information at any time on the Association web site.
At the close of each year, we take the opportunity to have our financials reviewed (and sometimes audited). The review process ensures that we've represented our financials properly. This work takes some time. Though our fiscal year closes on 31 December, it takes six to eight weeks to get the final bits and pieces handled in our financial systems. The independent review or audit adds another 8+ weeks to the process of closing out our year. Then we have to review the findings with the Finance Committee and the full Board before we share them publicly. That's why it's August and we're just now sharing the 2014 reviewed financial statements with you.
In 2014 we also began tracking our progress towards several operational goals for the first time. Though we share those numbers every month in the board report, we pulled some of our favorite stats and stories together into an Annual Report to share the work that our financials represent.
What happened in 2014?
2014 was an investment year. Per our Leadership Plan and Budget for the year, our key focus was building an engineering team to first address technical debt on Drupal.org and then take on actual improvements to the site. We purposely built a budget that anticipated a deficit spend in order to fully fund the team. The intent was to also build some new revenue programs (like Drupal Jobs) that would ramp up and eventually allow us to fund the new staff without deficit spending. And that's what we did. We went from two full time staff focused on Drupal.org to ten.
The investment has been paying off. We spent a lot of 2014 playing catch up with technical debt, but also managed to improve site performance markedly while also increasing the portability of our infrastructure. On top of that, staff worked with community volunteers to release new features related to commit messages, profiles, and Drupal 8 release blockers. Most importantly, staff and the working groups prioritized upcoming work and published a strategic roadmap for improvements to Drupal.org.
We held two huge DrupalCons, one in Austin and one in Amsterdam, and planned for a third. Our very small team of events staff and a crew of remarkable volunteers hosted over 5,500 people across our two events, all while planning our first Con in Latin America. We had some stumbling blocks and learning opportunities, and have been applying what we learned to the three 2015 DrupalCons.
We launched Drupal Jobs. This was something the community asked for very clearly when we conducted a 2013 study. We’ve seen steady growth in usage since our quiet launch and will continue to refine the site, including our pricing models, so that it is accessible to Drupalers around the world.
We diversified our revenue streams. DrupalCons used to be 100% of our funding. Not only is this a risky business strategy, it puts undue pressure on the Cons to perform financially, leaving us little room to experiment or make decisions that may be right for attendees, but could negatively impact the bottom line. As we increase the funding sources for the Association, we can make more and different choices for these flagship programs and also grow new programs with the community.
We introduced branded content including white papers, infographics, and videos. These materials have been widely used by the community and have helped us understand the Drupal.org audience in a better way. You can see a lot of this work on the Drupal 8 landing pages, where the key content pieces were downloaded thousands of times in 2014.
We released new vision, mission, and values statements for the Association. These tools are really useful in defining the focus of the organization and helping to guide how we get our work done. Working in a community of this size and diversity is extremely challenging. There is no choice we can make that will include everyone’s ideals, but our values help us make those decisions in a way that allows for transparency and open dialogue with the community. It’s something that we try to honor every day.
What about money in 2014?
As anticipated, we ran a deficit in 2014. However, we did manage to grow our overall revenue by about 6% from 2013 to 2014. This trend has continued into 2015, though not at the rate we had hoped. Still, we are now on track to support the investment we made in 2014 into the future. Another key win in 2014 is that we grew non-DrupalCon revenue to 21% of our total revenue. Diversifying our revenue streams reduces our financial risk and takes the pressure off of Cons, allowing us to experiment more.
I want all the details
Excellent! You can check out:
Look for links to our Strategic Roadmap highlighting how this work falls into our priorities set by the Drupal Association Board and Drupal.org Working Groups.
July was an action packed month at the Drupal Association - we had our quarterly prioritization with the Working Groups, our annual all-hands summer staff meeting, and mentored two tremendously dedicated interns throughout.
Our primary engineering focus was on DrupalCI and Localize.drupal.org - though we also found time to make some iterative changes to Drupal.org in a few areas, namely: issue credit refinements, performance, groundwork for the new content model.Strategic Planning
Prioritization for Q3 2015
The Drupal.org Working Groups help to provide governance for Drupal.org and to set priorities for the work of Association staff. Each quarter we evaluate our priorities with the Working Groups and update our Roadmap.
On July 15th we updated our roadmap based on the Working Groups input. Our main priorities for Q3 are Drupal.org services that are required to support the Drupal 8 release, and functional improvements to Drupal.org:
- The port of localize.drupal.org to Drupal 7, as well as a few issues that support Drupal 8 localization.
- Making sure DrupalCI meets the MVP spec set out by the core developers for providing test coverage for Drupal 8, and that it meets the functionality required to replace the old testbot system.
- Improving Drupal.org search.
- A new documentation section based on our content strategy work that will provide better organization and governance of documentation.
Additional priorities were identified for Association Staff to tackle as time permits.
Drupal Association Summer Staff Week
July was also the time for the annual all-hands staff meeting for Drupal.org. For one week, we gathered all our local and remote staff in our Portland office to discuss:
- The mission, vision, and values of the Association.
- Our ever-evolving relationship with the Drupal project itself.
- Setting engineering and design principles for the team.
- Finding sustainable revenue that will fund our work.
Internships at the Association
For 8 weeks beginning in mid-June the Association staff hosted and mentored two interns who had just completed Epicodus’ inaugural Drupal curriculum.
Bojana Skarich(BabaYaga64) and Daniel Toader(CountPacMan) worked with us on bug fixes, features, and theme work for the Conference Organizing Distribution and several related modules that allow the Association to run our DrupalCon websites.
We’d also like to thank our Supporting Partner ThinkShout for funding Daniel and Bojana’s work with us. This is just one small example of how the supporting partner program fosters our mission by promoting Drupal as part of a software development training curriculum and giving these new members of our community a great head start.Drupal.org
Issue Credit Updates
We deployed two small updates to continue to refine and iterate on the Issue credit system that we implemented in the beginning of this year.
Firstly, to support an earlier change to allow explicit attribution as a volunteer, we’ve updated the attribution :hover state display. Previously unattributed comments and volunteer attributed comments would both simply display the username in attribution, though the distinction was being made in the comments themselves. Now that distinction exists not just in the data but in the display on comments.
Since releasing the issue credit system in March, there have been over 9,500 issue credits awarded on over 5,200 issues. Over 2,400 unique users and 250 unique organizations have been awarded issue credits. Over 1,000 projects (modules, themes, distributions) have credits that have been awarded. The last 90 days of issue credits can be viewed on each user and organization profile.
Secondly, we deployed a small change that will automatically generate the first comment on a newly created issue.
This automatically generated initial comment serves two purposes: It allows the original author of an issue to be credited when the issue is resolved, even if they did not leave any subsequent comments on an issue. It provides a link to the original issue summary providing a better at-a-glance view of what the original reporter wrote, even if the summary has since been edited a large number of times by other participants in the issue.
There are still additional refinements to be made as we find time - in particular providing a ui to edit the attribution that will be made for the automatically generated first comment.
The new content model for Drupal.org requires a number of new modules on Drupal.org. To ensure that the site remains performant we are serializing these changes as much as we can. The first new module to be deployed on Drupal.org was entityreference_prepopulate.
As we work to build out the Documentation section we’ll be installing additional modules, creating some new content types, and providing a number of new resources for maintaining documentation on the site.
Improving performance of Drupal.org is an ongoing concern, particularly as we look to adding new modules that while powerful may also be somewhat heavy on a site of our scale. Utilizing advanced css/js aggregation is something we began to gradually implement towards the end of June, and in July we completed the majority of the changes laid out in this issue.
With these changes we’ve largely completed the work that will be done here for the foreseeable future, though there may be a few more performance gains to be found here and there. Thanks again to mikeytown2 for his assistance.Drupal 8 Blockers
July was a huge month for DrupalCI. There are two major milestones for the Association’s work on DrupalCI.
- DrupalCI must meet the testing requirements for Drupal 8 Core and Contrib specified by core developers.
- DrupalCI must also meet or exceed the existing functionality of the PIFT/PIFR testbots for testing Drupal 7 and Drupal 6 so that the old testbot system can be retired.
The first milestone was our primary goal in July - while the second will be our hard focus in August.
We made tremendous strides towards the first goal, starting with a reformat of the test result output to better display in Jenkins. This new format more logically organizes the test output by:
Test Group -> Test Class -> Test Method -> Output/Result
This should make understanding the results of testing easier in the long run, and is also a precursor to displaying test result information directly on Drupal.org - which we hope to complete in August.
We also made improvements to the test history pages - so that project maintainers can make better comparisons of any given test result to the status of a branch when an issue was created, for example, or against the most recent branch test. These test history pages also allow maintainers to see which user triggered the test, and are the portal to the test results.
July also saw the deployment of patch level testing with DrupalCI - which can be enabled on a per environment basis for projects on Drupal.org.
Towards the end of July we also enabled testing for Contrib projects - allowing any project maintainer on Drupal.org to begin using DrupalCI. We are asking project maintainers to enable DrupalCI for their projects and provide us with their feedback in this issue. This will be critical for us to retire the old testing infrastructure.
We also focused on improving the performance and efficiency of the tests. Minimizing the time it takes to initiate a test and complete a full test run both improves efficiency for developers and maximizes the reach of the Association budget for automated testing.
The new DrupalCI architecture automatically scales up and down the number of bots dependent on need, which will hopefully present a cost savings once we disable the redundant old testing infrastructure.
In addition to the architectural work above - we also upgraded our base environments to php 5.5 to support the change in Drupal 8 minimum requirements.
Finally, we improved the documentation for project maintainers for enabling DrupalCI testing on their projects.
Endless thanks to jthorson for his help.
After our community testing of the localize.Drupal.org Drupal 7 port in June we identified a critical path of remaining issues that needed to be resolved to allow us to complete the upgrade. Many of the issues were related to user roles and permissions do to the differences between Drupal 6 organic groups and the Drupal 7 version.
We put a hard focus on resolving as many of these issues in July as we could, so that we would be ready to perform the final upgrade in August (which was completed successfully on August 12th).
We also added the ability for event attendees to purchase or renew their Drupal Association memberships while purchasing their tickets for DrupalCon.
Finally we are in the planning phase for some additional work to support our payment processing needs in India, and to support having the registration process live for multiple events simultaneously.Sustaining Support and Maintenance
New Git Infrastructure Deployment
As mentioned in our June update - we put the bow on a long-standing project to migrate our git infrastructure to new servers in July. Much of the work to provision the new servers was completed in June - but the cutover itself was scheduled in the early weeks of July.
The new git infrastructure is now both redundant and highly available, greatly increasing the stability of a critical part of our infrastructure.
Serving Files from a Separate Domain
In July we also acquired a new domain and wildcard cert for *.drupalcontent.org. This new domain will be used to serve static files across the Drupal ecosystem of websites, providing benefits for security and reducing the size of http requests by serving these resources from a domain without cookies.
Work to serve files from the new domain name is ongoing, and many thanks to mlhess for helping us implement this change.
Load balancer stability
After continuing the debug the decreasing stability of our load balancers, we decided to swap hardware and rebuild the load balancers using different hardware. The new hardware is also using an updated configuration and operating system, which has proven to be more stable. The second load balancer is in the process of being built out using the new configuration and different hardware. The project should be completed by the end of August, bringing stability back to one of our key infrastructure components.
Many thanks to nnewton for helping us diagnose and make this change.
Updates to Updates
One of the core services that Drupal.org provides is updates.drupal.org. In essence this is a feature of Drupal itself. Because Drupal.org is the home of updates information for the entire project, we analyze our updates traffic as part of our project usage statistics.
Unfortunately the project usage stats have been somewhat unreliable - so in July (and continuing into August) we’ve given this system some attention.
Changes we’ve made or are in the process of making include:
- We moved the updates system to a CDN (and then migrating to a different CDN provider).
- We updated our processing to work with centralized logs on our loghost.
- We are improving the performance of the process from a 3-4 hour run per day’s worth of data to a 1 hour run per month of data.
- We are simplifying the process by removing an intermediate MongoDB deduplication/key-value store.
Work to improve the performance and stability of the updates stats system will be ongoing.
As always, we’d like to say thanks to all volunteers who are working with us and to the Drupal Association Supporters, who made it possible for us to work on these projects.whats new on Drupal.org
Drupal is a lot of things. It’s a platform, a CMS, software, and code. But here’s what Drupal is most of all: community.
That’s why DrupalCon has had community content baked in, first as a stand alone track across the entire event, then as a summit on the Monday of the Con. Now, we’re ready to double down on community starting at DrupalCon Barcelona. Together with Drupal’s Community Working Group, we’ve taken your feedback and devised a brand-new approach to community at the Cons.
What We Heard from You
We started with a survey to find out who’s participating in the Community content at DrupalCons and what you were hoping to achieve. You can review the full survey results, but here are a few key findings that we identified.
Meeting each other to build your network of support is the most important thing we can help facilitate. That’s followed by skills building, and then by actually getting specific work accomplished.
There is strong demand for a wide variety of skills training. We haven’t really provided this kind of content in a structured way for the community before, so we are excited to address it head on.
There was strong support for community content to be integrated into the main conference. We know that one reason community content moved to the summit format was poor attendance at community sessions at previous Cons, but we think this result means that we can integrate content back into the conference, but perhaps in a slightly different way.
What We’re Planning
Donna Benjamin, Adam Hill, and I met to discuss the survey results and get a plan together for Barcelona. Our goal was to build a comprehensive community program that provides a variety of ways to interact on community issues while also addressing the community concerns raised in the survey. In short, we’re proposing that community is integrated into every part of the Con. Here’s how it will work in Barcelona:
- Community Keynote: We did it in Amsterdam, and it was such a success, we’re bringing it back in Barcelona. Thursday’s keynote is presented by the community, for the community. Mike Bell (mikebell_) will talk about mental health in the open source world and David Rozas (drozas) will talk about the phenomenon of contributing to a community.
- Community Kickoff: On Monday, we will hold a community kickoff event for the week. We’ll begin with an introduction to all the community content at the Con, followed by exercises designed to help you meet the people that can help support you in your community work, whether you need help maintaining a long-standing camp or User Group, or if you’re new to the community and want to know where you can get involved. Then we’ll conduct breakouts to share knowledge around specific issues, and identify good topics for further discussion in the community Birds of a Feather sessions later in the week. We’ll end the day by joining the First Time Attendee social so that we can show the new folks what our community is all about.
- Community BoFs:Tuesday through Thursday we will hold Birds of a Feather sessions to focus on community issues. Some (maybe all?) will be determined at the Monday kickoff. These sessions should bring people together around a common theme, like User Group leaders discussing best practices for organizing a DUG. All BoFs will be asked to identify a note taker who records key takeaways from the conversation that can be shared back out with the community.
- Community Training: You asked for help building specific skills, so these sessions will be designed to help you learn specific takeaways and give you real tools you can use back in your community. Tentative topics include Camp Budgets and Financial Management, Conflict Resolution, Sponsor Recruitment and Management, Mentoring, and Public Speaking.
- Community Sprints: After four days sharing what you know and learning new things, you’ll be itching to put your ideas to use. On Friday, sprint tables will be set aside to work on specific community issues that are raised throughout the week. Topics could include things like building a universal camp budget template or helping to find ways to integrate community contribution on Drupal.org profiles.
You can see that we’ve tried to bake community into the Con from start to finish and address all the different needs you identified. We hope this new format will make it easier for you to get the support you need to continue to do what you do best - make Drupal great!
Where Do I Sign Up?
To help organize our space and time, we’re asking you to RSVP for both the Community KickOff and the Community Trainings. All you need to do is head over to the Community Summit Page, find the content you're interested in, and add your name to the list.
In the meantime, if you have any questions or suggestions,
Flickr photo: Boris Baldinger
Here we go again! It's your monthly summary of all things board meeting at the Drupal Association. This month we covered board governenance (there's a seat opening up), the D8 Accelerate Campaign, and the Association strategic frame. Plus, as a bonus, the board approved the Q2 financials for publication. As always, if you want to catch up on all the details, you can find everything you need to know about the meeting online, including minutes, materials, and a recording. If you're just here for a summary view, read on!
Angie Byron's term on the board is going to be up this fall, and she has expressed her desire not to renew that term. We're going to be very sad to see Angie go, but thrilled that she will have one less hat to talk about when explaining which hat she is wearing at any given point during your next meeting with her. Seriously - she's brought so much thoughfulness and passion to the board. She's not leaving us yet (her term expires 10/31), but our Governance Committee will be working with the Nominations Committee to recruit candidates and help the board make the next selection.
As I write these words there are just 10(!) release blockers standing between us and a release candidate for Drupal 8. Part of the momentum this year has come from Drupal 8 Accelerate. We've made over 40 grants, worth more than $120,000 so far. That's helped us close nearly 100 issues, addressing some really important features, like a beta to beta upgrade, security bugs, and performance. If you're curious about what's getting funded, you can always see the full list. And, we're getting close to reaching our goal - we've raised $223,000. You can help us reach our $250,000 goal by making a donation today!
Drupal Association Strategic Frame
Why are we doing the work we do? Because everyone at the Association wants to have a positive impact for Drupal. The best way for us to have an impact is to pick a few goals that we are going to focus on achieving. The Association board used their January retreat to set some 3-5 year goals for the Association:
- To develop sufficient professionals to meet global demand for Drupal
- To lead the community in focused, efficient, effective development of Drupal
- To ensure the sustainability of the Drupal project and community
- To increase Drupal adoption in target markets
- To increase the strength and resilience of the Drupal Association
We've been working since then to select the right strategies and objectives (1 year to 18 month time frame) for our work. You can see the directions we're headed in the presentation we shared. It's important to note that we expect to revisit our strategies and objectives on a quarterly basis to adjust as we go. The world of Drupal moves fast, and we need to as well. So, although we are setting 12 to 18 month objectives, we will be adjusting the frame much more frequently, and won't be sticking with objectives that we find don't really support the work.
2015 Q2 Financials
And in the most exciting news of all, the second quarter financials were approved by the board. You can always find whatever financials have been released in the public financials folder. If you have never taken a look at the financials before, I recommend it. Although I tease about them being boring, I love financial statements! A while back, I wrote up a post about how to read our financial statements. I also like pointing out that each Con has it's own tab in our financial statements, so you can see exactly how that money coems in, and where it is spent.
See you next time!
And that's it for this summary. But, if you have questions or ideas, you can always reach out to me!
Flickr photo: Joeri Poesen
Last year we conducted a Drupal Job Market survey to better understand the opportunities for those who know Drupal. The survey showed strong demand for Drupal skills and demonstrated why Drupal is a rewarding and potentially lucrative career path. We are conducting another survey this year.
This year we are adding questions about compensation to help Drupal talent and hiring organizations benchmark themselves.
You can expect to see the results from the survey published in late August. Thank you for taking the survey!
Look for links to our Strategic Roadmap highlighting how this work falls into our priorities set by the Drupal Association Board and Drupal.org Working Groups.Drupal.org
Iterative Changes to the Front Page of Drupal.org
The home page of Drupal.org has been changing in several small but important ways. The main focus of our design work in June was to provide new community metrics to replace the less meaningful and somewhat misleading metrics that were removed in the previous home page update.
We also updated the text of the Try Drupal button on Drupal.org, to better clarify the purpose of the feature. Try Drupal allows potential users to evaluate Drupal by using a highly polished demo hosted by our Supporting Partners. This gives Drupal newcomers and learners the chance to see examples of Drupal configured at its best, to encourage evaluators to choose Drupal for their needs. The program supports a core part of the mission of the Drupal Association: helping to promote Drupal and grow Drupal adoption.
Improving Drupal.org Performance with Advanced Aggregator
These configuration changes have been made carefully to ensure they don’t degrade the user experience for any user of the site - and are continuing into July.
The Plan Category for Drupal.org Issues
Another small deployment made in June was the addition of a Plan category to the Drupal.org issue queues.
The Plan category codifies the informal [meta] issues into a category selectable within the Issues UI.
This only scratches the surface of a long-buried issue in the Drupal.org issue queues - a lack of project management and prioritization tools. The larger Content Strategy work that the Drupal Association is beginning to implement will help to address this need further with a new Initiative content type to provide better hierarchy and prioritization tools.Organization and User Profile Improvements
Recent Issue Credits (3 months) now appear on individual and organization profiles.
Expanding upon the work the Association staff has done to create a system for credit and attributions in the Issue queues, the Association has begun displaying information about issue credits on user’s Drupal.org profiles.
Whenever a project maintainer has credited the user in an issue when marking the issue closed - the project will appear on the profile, along with a link to a list of the credited issues.
Additional improvements are planned for the crediting UI to allow credit attribution to users who did not comment directly on the issue. The Association will also begin to backfill historical credit data.
Organizations benefit from this change as well. When a maintainer closes an issue and assigns credit, if any of the users being credited have attributed the work to an organization - that issue credit will be displayed on the organization page. This change rewards those organizations that give their employees time to give back to Drupal.Content Strategy and Visual Design System for Drupal.org
In May, the long-running Content Strategy work culminated the presentation of the Drupal Association’s proposal for a new content model on Drupal.org. In June, after monitoring feedback from the Drupal community and the Working Groups following DrupalCon Los Angeles - we transitioned from planning the new Information Architecture to planning the implementation details to make the new content model a reality on Drupal.org.
Implementation of the new content model and governance plan is going to involve quite a few changes to the modules on Drupal.org, so we want to approach the implementation iteratively and carefully.
Our plan developed in June calls for us to create the new ‘Why Drupal’ section of the site first. In June, we prototyped an implementation of this first section using Organic Groups and Panelizer and prepared a plan for performance profiling.Issue Workflow and Git Improvements
The Association Team is excited to implement our vision for new issue workspaces on Drupal.org - including a new spin on the implementation of pull requests.
Work on the Issue Workspaces is slated to begin once major work on DrupalCI is complete, and we are able to retire the PIFT/PIFR testing system without regressions.
However, we were able to remove a blocker to this work by updating our servers for our Git architecture (more below in sustaining support and maintenance.)Community Initiatives
DrupalCI was a major focus of the Drupal Association staff in June. In June the integration between DrupalCI and Drupal.org was enabled for the first time. DrupalCI is now running in parallel with the PIFT/PIFR testbots to provide us a reference frame to prove out the implementation.
A remaining MVP hit list was codified in June - representing the few remaining issues needed to meet the guidelines set out by the Drupal core developers. (Spoilers: Most of these issues are resolved at the time of this posting in July!).
Going into July the focus will be on providing testing for Contrib through DrupalCI, and then ensuring that there are no regressions in functionality or test result detail as compared to PIFT/PIFR so that the old test bots can be retired.
Once that is achieved, the Assocation’s work on DrupalCI will scale back to maintaining the system’s stability- and more development focus will be provided to our next initiatives.
At the end of June we initiated a final round of community testing for the port of localize.drupal.org from Drupal 6 to Drupal 7.
That testing period has ended as of the first week of June, and we are now working together with the community to resolve the issues uncovered by this final testing before deployment.Revenue-related projects (funding our work)
Registration for DrupalCon Barcelona opened in June, with some small refinements to the registration process from lessons learned in DrupalCon Los Angeles.
Events.Drupal.org did receive one new front-facing feature, an opportunity in the registration process for ticket purchasers to purchase or renew their Individual or Organization memberships with the Drupal Association.
The Drupal Association is also working very closely with the DrupalCon Asia designer in preparation for the full site launch in the coming months.
Better Cart Management on Jobs.drupal.org
On Drupal Jobs we deployed a small update to the checkout workflow to make cart management easier - addressing the top support request that we receive from our users.
Future development for Drupal Jobs continues to be limited to the most high-impact bugs or features identified in the support requests we receive for job postings.
Signature Supporting Partners Page Launched
June also saw the launch of the Signature Supporting Partner program. This required a small update to our supporting partners page to support the new partner category.Sustaining Support and Maintenance
Final work preparing for deployment of our new git servers was completed in June - but for scheduling reasons the maintenance window for replacing our existing Git infrastructure was scheduled to take place on 7/9/2015. (This deployment was successful!)
Our Fastly CDN deployment for updates traffic (updates.drupal.org) was also successful. Updates now use dynamic purging to reduce the number of requests served by our origin servers and decreases the latency between packaging a release and serving the update data from a number of minutes to a few seconds.
As part of the updates deployment with Fastly, we now have a *.drupal.org wildcard TLS/SSL certificate for https://updates.drupal.org and https://ftp.drupal.org. This enables HTTPS support on all of Drupal.org and its’ sub-sites for the first time.
As always, we’d like to say thanks to all volunteers who are working with us and to the Drupal Association Supporters, who made it possible for us to work on these projects.
OSCON, the annual open source conference, brings over 4,000 people together in Portland this July. We are a proud participant again this year and we are excited to talk about Drupal to a wider audience. If you are looking for a reason to attend, you can use the code USRG which will get you 20% off your registration. Or you can use the PCEXPOPLUS code to gain admission to the exhibition hall for free.
Taking Drupal to the larger open source world is a big job, and we need our amazing community's help. Help us spread the word that Drupal is at OSCON! If you're attending, please come by and say hi, let your new friends know they can find us in the nonprofit pavilion at table #6 from Tuesday evening through Thursday afternoon. Or, if you know someone who's in open source who will be at OSCON, please encourage them to come by and say hello! Here's a tweet you can share with your networks to help us spread the word:
Thanks to the Portland Drupal community for helping out and to everyone for volunteering time at OSCON. If you want to help out by volunteering at the table, we'd love your assistance! You can sign up here.
See you at OSCON!Personal blog tags: OSCON
If you are interested in Drupal community and you are coming to Drupalcon, we are looking for your opinions!
For a very long time, community conversations at DrupalCon took place at sessions in the community track, which ran alongside all the other content at DrupalCons. The community track allowed for presentations on topics related to our community. While it was good to be able to raise the topics, there were real concerns that the session format meant that nothing productive came from the conversation. Further, the community track was just much less attended than other sessions, with 25 or so folks in a room that holds 200.
At DrupalCon Prague in 2013, we launched the first Community Summit. Held on the Monday of DrupalCon week, it is a day-long event designed in an un-conference style to bring community members together to tackle the issues that help our community achieve more together. Morten DK, Addison Berry, and others (bless you all - you have been great collaboratrs) ran the program and led a number of very useful conversations.
For the last few DrupalCons we have run these community summits, and have heard a whole new round of feedback, including:
- Work at the Summit does not tend to continue after the Summit, so we lose momentum.
- We don’t always have the right people in the room to really solve some of these problems.
We also did some surveying of our community leaders at the beginning of last year and heard that they are very hungry for skills training that can help them take their camps, meetups, trainings, etc. to the next level. They want to learn about how to manage the finances of a camp, how to recruit sponsors, and how to be better public speakers. The current community summit format does not really allow for this kind of skills training either.
So - we are looking for your feedback about how we might restructure the community content at DrupalCons.
Just so you know, I hit the woods with my family and no internet and no phones for one week a year, and that week is next week. I won’t be able to respond to comments or the survey while I’m gone, but I will do so when I return. If you have feelings, ideas, or feelings about ideas - stick them in the survey! I’ll share the results back out. If you have book recommendations for my trip, hit me up on Twitter.
First things first - an apology. I realize it's been a couple of month since I put up a post about our Board meetings. I definitely apologize, and will try not to let that happen again. However, know that you can always see the meeting minutes, materials, and recordings on our site. And, if you ever have any questions, you can find me on Twitter, D.O, in IRC (drupalhross), or you can send me an email (you know, if you are old school).
The June board meeting covered the month of May at the Association, which was a rather big month. As usual, we had a number of items to cover in our operational upate, and then we dove into updates from the Drupal.org Working Groups.
- Drupal 8 Accelerate had a great month in May, adding $55,000 to the total of over $213,000 now raised to help close D8 release blockers. Huge thanks to Catalyst IT, Open Source Developers Conference Australia, Siteground, Figleaf Software and Duo Consulting for the $1,000+ donations in May. You can see how every dollar is directly impacting Drupal 8.
- We had a DrupalCon! We'll give you a full wrap up in August when all the details, including financials are available.
- Content Strategy is coming to Drupal.org. In an nutshell, we are excited to have completed a content strategy process with Forum One. With the strategy document complete, we can begin implementation. In the next few months we'll be introducing changes to the site to support the new information architecture and content governenace. When everything is in place, you will see a site that is easier to navigate and gives topic owners more flexibility in the types of content and permissioning they can use. You can see all the details in the DrupalCon LA session we hosted.
- As we shared in last week's post, our revenue continues to come in slower than planned. In Executive Session we shared a mid-year adjustment to the plan that we have now begun executing. Although we are not meeting our original goals, we remain excited about the possibilities for the Association - we are still growing. Especially reassuring is that all the Drupal 8 content we release is snapped up quickly.
Working Group Updates
Last quarter the Working Groups met in-person at DrupalCon Los Angeles. During the meeting, the groups discussed their role in producing the Drupal.org roadmap and began the process of re-prioritizing the work. We have definitely discovered a broader need for the Association engineering team across the Drupal ecosystem, and need a better process to allow for unplanned work to be prioritized. A good example is DrupalCI, which morphed from an entirely volunteer-run initiative to work supported heavily by Association staff.
The Working Groups have also proposed charter changes in to the Executive Committee for review. We are looking to expand the number of community members on each group and further clarify the roles.
Thanks and see you next month!
That's all we had for this board meeting, but more is planned for July and beyond. Check out all our upcoming board meetings and register to attend.
Flickr photo: pdjohnson
In the next couple of weeks we'll be launching a new sponsorship opportunity for Drupal Supporters on the homepage of Drupal.org. The following is background information and a proposal for the program. We would like a period of public community feedback. Feedback is open until the 6th of July. At that time, we will incorporate the feedback into the sponsorship program plan.Background
The Drupal Association has been creating advertising programs on Drupal.org in an effort to do more to serve our mission, and to take the pressure off of DrupalCons to perform financially. We’ve been working to develop advertising products that are meaningful for advertisers, deliver value to the community, and are respectful of users contributing to the project.About the Program
The Homepage Sponsorship will highlight partners who support the community through Drupal Supporter Programs. This includes Supporting Partners, Hosting Supporters and Tech Supporters. The sponsorship will display in the 300 x 250 ad block that already exists on the Drupal.org homepage. The creative template is designed and maintained by the Association. The featured supporter will provide a logo, body copy, button copy, and a link to that will direct to their website. We will display the partner’s supporter badge, and eventually, pass in any applicable organization credits.
The idea for the Homepage Sponsorship originates from the rewards mechanism that Dries discussed in his DrupalCon Amsterdam 2014 Keynote. His vision involves building a system that creates an incentive for Drupal companies to contribute to the project by rewarding them with benefits and giving recognition.
There is a larger project in motion which includes the Drupal Association building commit credits for organizations, and developing the algorithm to apply a value to the credits. The Homepage Sponsorship is one potential reward that will eventually feed into the system. Until that larger project is complete, the Homepage Sponsorship will be available for purchase by Drupal Supporters. It will be sold in one week increments, giving the partner 100% of the page views during the campaign. The program will expand recognition for those organizations who already give back, and will encourage more organizations to participate in Supporter Programs.Homepage Sponsorship Mock
Advertising Guidelines for Drupal.org
The Drupal Association interviewed representatives of the Drupal Community to help guide our advertising strategy and ensure a positive advertising experience on Drupal.org. We developed informal guidelines; for example, advertising is not appropriate in issue queues, and when possible, products should monetize users who are logged out and not contributing to the Project. After we received feedback on our most recent program - Try Drupal, we started work on formalizing these guidelines for advertising on Drupal.org.
We created an issue to share a draft advertising policy developed by the Association and Drupal.org Content Working Group. The policy will set guidelines for how we advertise - addressing issues like the labeling of ads, content guidelines, etc. with the aim of providing an advertising experience that complements Drupal.org and supports our community values. Whatever decisions are made in that policy will be applied to existing programs, including the Homepage Sponsorship and Try Drupal program.Talk To Us
We want your input about the Homepage Sponsorship. Please comment on this post, or in the issue, with your questions and insights.
AttachmentSize HP Sponsor Mock-small.png130.36 KB
I want to share today that the Association is implementing a new financial plan to address lower than anticipated revenues in 2015. To align our spending more closely with our revenue, we are implementing expense cuts that I’m very sorry to say include staffing. Regrettably, we are losing three staff people today from operations, engineering and our community teams. This was not a decision we came to lightly, and we’re committed to helping those staff through their transition as best we can. In this post I want to share some information about how we got here, and our revised plan.
A Brief history
This is a really hard post to write because we delivered a plan to the community at the beginning of 2015, and it’s clear that we are not going to be able to fully execute to that plan. I take responsibility for that.
I started at the Association two and half years ago, at a very different time for the organization. At that point in early 2013, the Association was a handful of staff, mostly focused on the DrupalCons. The D7 upgrade of Drupal.org had been halted. Not without some good reason, community trust in the Association was low, and that’s among the people who even knew the Association existed.
When I joined, the message I heard from the board and from the many community members I talked to was that the Association had to learn to implement consistently and communicate more. In other words, we needed to build our credibility in the community by executing our work well and making sure the community knew what we were up to and how to get involved.
One thing that was clear from the outset was that Drupal.org was key to our success. If we could not begin to make visible improvements to Drupal.org with the community, we would fail. With support from the board, we decided to invest our healthy reserve in ourselves and build a team that could improve Drupal.org. As our CTO Josh Mitchel pointed out in his anniversary blog post, we’ve done a LOT on Drupal.org. We’ve also made great strides in DrupalCons, introducing more first-time attendee support, providing more resources to all the sprints, and adding the third Con in global communities that are so eager to have us there. Our marketing team has helped create some key content for Drupal 8 and we’ve even raised over $210,000 to help fund the completion of D8 release blockers, The revenue we generate to do this work has also increased, and diversified. We've grown the Drupal Jobs, and rolled out Try Drupal. You can see, even with our revised expectations for 2015, that things are still growing. One of our key programs, Supporting Partners, is up 26% over this same time period last year, for example. Growth of this program was only 4% in 2014.
So lots of amazing things are happening, but we have to address that we overestimated what was possible for revenue. We have to adjust our plan to meet reality.
Changing the Plan
Addressing our situation is not work we took lightly. We set several goals for the process that guided our thinking throughout:
- Solve for short-term revenue shortfalls while retaining resources we need to succeed long-term
- Minimize staff impact
- Do this once - find the scenario we can truly sustain, and then grow out of
- Retaining credibility with staff and ensuring we communicate how valuable they are for our future
- Maintain community confidence
The strategy we used was two-fold. First, we strove to preserve our core services to the community and our ability to fund our own work. Second, we decided to take action as quickly as possible because the sooner we made changes to the plan, the greater the long-term benefit to the organization. We know that this second strategy makes some of this seem like it's out of the blue, but it means that we impact as few people as possible.
Our leadership team looked at three approaches to addressing our cash flow issues:
- Incremental revenue: Our new forecast extends actuals from the beginning of 2015 out through the end of the year. We believe that it is possible for us to improve upon this forecast slightly because, although our primary mistake was overestimating revenue, we also had some staffing change-ups (a retirement, hiring new reps) on the team at the beginning of the year that adversely affected the numbers. There is some room to modestly improve our revenue from the forecast.
- Non-labor expense: We looked at travel, consulting fees, hardware and software, among other places in the budget where we had built in buffers or non-essential expenses. Eliminating these now, and not carrying them into 2016 was a key part of our process.
- Labor expense: This was the last option we looked at because at the end of the day, not only do all our staff give the community everything they’ve got, we really like each other here. I care deeply for the well-being of everyone at the Association. There is also lot of discussion in the business community about the long-term negative impacts of layoffs on organizations. We looked at lots of ways to reduce labor expense, but were not able to find a solution that did not include some layoffs.
Using this process, we were able to identify $450,000 in non-labor expense savings, and increase revenue projections $250,000 from July 1 2015 through December 31 2016. That was enough to solve our 2015 revenue shortfalls, but it did not address the issues long-term. We needed to reach deeper to ensure our long-term success. We had to consider labor reductions.
Prior to looking at any other staff, the leadership team at the Association decided that the first staff cut had to come from us. As a team, Megan, Joe, Josh, and Matt volunteered a 10% reduction, and I volunteered a 15% reduction. But we still weren’t there. Looking at the remaining labor cuts, we wanted to use our values as our guide. We know that our team believes in our teamwork value above all else, and would want to minimize layoffs as much as possible. With that in mind, we experimented with the model and determined that we could limit layoffs to three if we asked remaining staff to take a 5% pay cut across the board.
All told, here’s what measures look like:
We believe this approach meets our goals and puts us in the best position possible to continue the great work we’ve been doing.
What Happens Next?
On the financial front, we’ll be managing to our cash flow for the next 18 months, as well as modernizing our budgeting and forecasting tools to reflect an Agile methodology. This will let us see further into the future more often, and give us more opportunities to update our plans based on what’s actually happening. And, if we find we are performing favorably to our plan, our first action will be to restore salaries for our staff.
Most importantly, we’re going to be focused on our team. They all got the news earlier today, and we’re taking this time to talk things through all together, in our teams, and one on one. I am here to answer questions and hear concerns for every one of them. We’ll also implement monthly internal review of our progress to the new plan with staff so that they have transparency on a monthly basis about what’s happening. These people are the best thing we have going for us, and I won’t ever be able to make this up to any of them, but I am committed to helping them find the best path forward they can.
Sharing this is not easy. The only thing that makes it better is knowing that the Association, like Drupal itself, has so much potential. I want to thank our Supporters, partners, sponsors, members, and the general community for everything you’ve given us so far. The only way we will realize our potential and move forward is together, and we are so happy that we get to do that with you.
As our community grows, so do our programs. This year in addition to hosting trainings and both the Community Summit and Business Summit, we offered a Higher-Ed Summit at DrupalCon. As soon as it was announced folks clamored to sign up, and the tickets sold out at a rapid pace. We at the Drupal Association feel like this is a great example of how the growing variety of offerings at DrupalCon illustrates the increasing diversity of our community’s interests and skillsets.
The Higher-Ed Summit was a huge hit and that was due largely in part to the efforts of the Summit Leads, Christina and Shawn. They worked hard to understand what the Higher-Ed community wanted and needed from the Summit and strategized to provide it down to the last detail. Their planning and experience were integral to the popularity of the event, and we look forward to working with these awesome volunteers again in the future.
Maybe I’m naive or a wide-eyed optimist, but meeting and speaking to people from all over the world is invigorating and exciting to me. Throughout the course of DrupalCon I had the opportunity to meet with community organizers from near and far. While it’s true that many attendees came from the United States and Canada, there were also organizers who came from as far away as Latin America, Europe, India, and Japan, and talked about how Drupal has affected their communities and their livelihoods. It is always such a pleasure to see Drupal changing lives and bringing opportunities for personal growth and business everywhere.
After an exhausting week of keynotes, and BOFs, and meetings, and dinners, I launched into the sprints on Friday with the purpose of understanding Drupal more. I always enjoy discussing Drupal’s unique qualities with developers, site-builders, and themers, but this DrupalCon I really wanted to engage in more than just conversations. I wanted to experience what it is like to directly develop and work with Drupal. At the Friday sprints, my friend and new mentor Amy agreed to sit down with me and help me put together my own blog, run on a Drupal website. During the process, I realized that there is no better way to start to understand the complexity of Drupal than to use the product myself.
When learning to use Drupal in the sprint, I realized that we really are about fostering a friendly, inclusive, and diverse community. We talk the talk and we walk the walk. Amy sat down with me and patiently showed me step-by-step how to start my site. We picked a hosting site, domain name, downloaded Drupal, and began the process of organizing our modules and features. Finally, I started to really get it, which was incredibly exciting. Both personally and professionally, it meant a lot to me that someone would take the time to help me on my journey. It really brought home the fact that Drupalers genuinely care, are excited and willing to share knowledge, and have fun while doing it.
DrupalCon Los Angeles was a spectacular event. I feel like this blog wouldn’t be a proper message from LShey without some shout-outs and kudos, so please join me in celebrating others. I’d like to say out a big thank you to our talented Events team at the Drupal Association for organizing a seamless and beautiful event. Thank you to our sponsors who help us put on this event with their support. Thank you to our dedicated volunteers: whether you were a sprint-mentor, room-monitor, or speaker, your time and expertise is appreciated and valued. Our volunteers truly make DrupalCon a wonderful event. I’d like to share a special shout-out to the team who keeps us all informed, too: thank you to Alex and Paul for running the @drupalconna twitter handle. Thank you to Emma Jane, who was our MC this DrupalCon, and who engaged our keynote speakers with witty and thoughtful interviews. Lastly, thank you to you all, our community. DrupalCon would not be the same without you. I’m looking forward to seeing you all at the next one!
Community Outreach Coordinator
The Drupal Association is excited to announce that Wunderkraut, a full service European agency and longtime supporter of the Drupal project, is now our first Signature Supporting Partner. A Supporting Partner since March 2014, Wunderkraut's latest contribution deepens its commitment to advancing the Drupal project and empowering the Drupal community.
"Drupal’s community is amazing. We’re very proud to be a part of it," said Wunderkraut CEO Vesa Palmu. "We're an established provider of Drupal services, and enjoy contributing to the Drupal ecosystem however we can, whether through camps or sponsored events, and especially when we can be quirky and fun! This passion is why we're now a Signature Partner—to strengthen our commitment to growing this community and project we love."
The Supporting Partner Program includes more than 60 companies from around the world. All of the funding from the program goes directly to support maintenance and enhancements for Drupal.org. Program contributions have funded many initiatives, such as
- Advancements in security
- Improved development environments
- User-friendly content strategy and design
Partners enjoy enhanced promotional services from the Drupal Association, such as brand visibility on Drupal.org, select access at premier events like DrupalCon, and increased publicity via various online social platforms. For their elevated contributions to the program, Signature Partners will receive upgraded promotional services.
"I’m absolutely thrilled that Wunderkraut is joining us as the first Signature Supporting Partner," said Drupal Association Executive Director Holly Ross. "Their support for the Association and the project is, and has always been, top-notch. This is another great expression of how much Wunderkraut believes in the incredible work our community does."
To join Wunderkraut as one of the Drupal Association's contributing partners, start by learning more about the Supporting Partner Program.
Breaking a Guinness world record is no easy feat, but in 2014, the folks behind Bart’s Bash did just that. With help from Drupal, they coordinated the world’s largest-ever sailing race — a fundraising event in memory of Andrew “Bart” Simpson.
Bart Simpson was a British sailor who won a gold medal at the 2008 Summer Olympics in Beijing, a silver medal in the 2012 Summer Olympics in London, and medaled in numerous World and European Championships. After Simpson was killed in a sailing accident in May of 2013 when training for the 2013 America’s Cup, his friends and family went on to found the Andrew Simpson Sailing Foundation in his memory.
“Andrew had passed away six months before [we began organizing Bart’s Bash],” said David Bishop, who built the website for Bart’s Bash. David is a sailor and runs NinetyOne Consulting out of Shropshire, England with his wife, who did much of the design work for the Bart’s Bash site. “When we set out initially, our goal was [to reach] only fifty sailing clubs, to raise £10,000, and see 2,000 people on the water."
The Andrew Simpson Sailing Foundation exists to inspire personal growth in young people through sailing. According to the Bart’s Bash 2014 website, "Many of our Olympic sailors have described the first time they were given charge of a boat as their moment of clarity – the first instance they felt true responsibility and in command of their destiny. Whether or not children will take up sailing as a pastime, many studies have shown that children who are confident, have self worth and personal resilience do better in every way. They are happier in their personal and family life, they are better able to learn, do better at school and in employment and they are more open to new experiences in life. We aim to provide an avenue to that fulfilment and have global ambitions to spread the attitude, inspiration and personality of Andrew Simpson around the world."
“Initially, there was a Facebook page that had been set up in memory of Bart, and it only had about five thousand followers,” said David. “So we built a one page website for the event, and I put social sharing buttons on it. We were very quickly up to several thousand shares on Facebook, and hundreds on Twitter.
"Within three or four weeks, over 300 sailing clubs had come to us and said, ‘we want to be involved,’” David continued. “So we had to change what the event was going to be. Initially, we were just going to be a dinghy event in the UK, but because of the international interest from yacht clubs, kitesurfing clubs, model yacht clubs... all these people wanted to be a part of it, and we wanted to accommodate them as much as possible.”The perfect platform for breaking records
As it turned out, Drupal was the perfect platform for this rapidly-growing event. “The whole concept of Bart’s Bash was that there’s no overriding governance. It's about engaging sailing clubs and getting someone at each venue to say, 'I’ll hold an event here, I’ll manage it,’” said David. “From that point of view it was a massively volunteer, community driven event. We’ve been as open as possible about making sure clubs can make their own pages and manage their own content, to make the event as successful as possible."
For David, that meant building a platform that sailing clubs around the world could use and make their own.
“I’ve built the system so that each club can create their own page,” David said. "They log in to a control panel, upload their own content, and manage it themselves. With the flexibility of the Simple CCK module, and blocks and views, it was possible for me to do rapid development. I built the whole thing myself. I had a little help from a local web development company — a day’s support, maybe — but other than that, one person built this whole system, and the scale it gives you is phenomenal.
“It’s interesting, because one of the areas that this has shown that the foundation can go into is providing services around the world just as a club web page. A lot of sailing clubs might not have a page that looks as nice as this, or that isn’t mobile responsive. But all of this is. So that’s actually one of the services that the foundation is looking at: we’re thinking of turning this into a ‘Learn to Sail' directory where you can find information about sailing at clubs near you.
“It’s amazing how good Drupal is as a platform — it definitely works for something like this,” David continued. “It’s just so flexible and so scalable. We put up the site for the 2014 event, and translated one of the key pages into eight or nine different languages. As you know, you turn on the international module and add the different variations, and you’re done. Drupal is the only platform out there that does this."“A lovely festival of sailing"
Building a scalable, global website was only the beginning of holding a worldwide race, however.
“One of the biggest challenges was that it was going to be a global race — so how do you rank people racing in different time zones, in different classes?” David said. “We worked with a formula so we could calculate speed — a handicapped speed, if you will — so people in fast boats were adjusted for slow boats. Ultimately it came down to where the wind was in the world on that day. We were fortunate to receive a lot of help from the UK’s Royal Yachting Association with this challenge."
“After the race, we split the results up by age, experience, wind conditions, country, and boat class, which was key,” David continued. “We were able to produce a very nice set of statistics, and that’s something that hasn’t really been done in sailing before. In most sailing races, you just get a very straightforward set of results to see the winners. But it turns out our way was really popular— we saw a lot more traffic to the website after the events and continually for the next few weeks. As more results came in for those few weeks afterwards, seeing how the top 10 has moved up and down, it was great."
But for the sailors, it turns out it wasn’t all about winning. “We thought people were going to be obsessed about the results, and we weren’t sure how we’d validate it,” David said. “But in reality, we had massive boats in the same start lines as a 7-year-old kid in a tiny boat. It turned out people didn’t care about the race so much. Instead, it became this lovely festival of sailing."Breaking world records
With the size of the event, the Bart’s Bash organizers were certain they’d be able to break a world record.
"For Guinness we had to get video of every start and every finish, plus steward and witness statements, and then we had to send each club bundle in. With more than 500 venues around the world participating, we wound up having nearly 10,000 boats qualified as being part of the world record,” said David. In total, the group collected and calculated results for 30,754 sailors across 52 countries around the world.
“It was another great way to get people involved in the event,” he continued. “Telling them that they're going to be a Guinness world record holder."
When it comes to the next year of races, David has high hopes. “For 2015, the Guinness restrictions have been lifted as we want to encourage small clubs who were not large enough to qualify under the rules required by Guinness last year. Also in 2015, we want more non-sailors on the water at more clubs around the world. To help make this happen we have come up with an idea called “Bart’s Buddies” aimed at taking your mates sailing. There will also be a special “Bouy Race” which will make it easier to get all of the wonderful volunteers sailing. To help showcase that, this year’s website is much more geared around showing the photos and the videos taken by each club around the world."
“Ultimately, three things brought the whole event together last year, and are pushing it forward this year, too,” David said. “First, it's a worthy fundraising reason. People want to do something in Andy’s memory. Second, it's a challenge — and sailors love challenges. Lastly, though, it brings a global community together, and Drupal as a platform enabled that to happen. We could create maps showing where people were using Open Layers modules. We could personalize the website for different people, and could drill down data and results.”
“Really, this is the first census for sailing activity done around the world in one day. It hadn’t been done before, which makes this website and event historic from that point of view,” said David. “We’ve been approached by other sailing associations and foundations, saying 'we want to do this, can we use the data you’ve collected.’"
As for what comes next, David is excited for the race coming up in September.
“A big sailing club signed up to participate in Barcelona last year,” David said. “And this year, the race is on 20 September — the day before DrupalCon Barcelona happens. Perhaps we’ll be able to get some Drupalers out there?
“The fact that Drupal exists means that Bart’s Bash happened. It has a lot of thanks to give to Drupal,” David concluded.
If you're interested in participating in Bart's Bash at DrupalCon Barcelona, let us know.
Sailing image credit to Gorazd Božič on Flickr.
This quarter saw a phenomenal turn out for the Drupal Association’s May Global Training Days! 25 training companies from 15 countries participated in hosting Introduction to Drupal sessions. A huge thank you to our community organizers and trainers, you are helping grow Drupal adoption globally!
To see all the action, pictures, and new Drupalers from the May training, check out twitter #DrupalGTD!
Want to host a training for your community? We have two more dates coming up in 2015, so it’s not too late to start give back to your community. If you want to set one up, the upcoming Global Training Days are:
- Friday August 29th - Saturday 30th
- Friday November 14th - Saturday 15th
Look for links to our Strategic Roadmap highlighting how this work falls into our priorities set by the Drupal Association Board and Drupal.org Working Groups.Organization and User Profile Improvements
Explicit Attribution Option for ‘I am A Volunteer’
As a part of our effort to recognize individual contributions to the Drupal ecosystem we’ve slightly adjusted the options available to a user when making an attribution in the issue queues. Instead of simply assuming that a comment made without an attribution to an organization or customer is done by a volunteer - we now allow volunteers to explicitly mark their work as such. Requiring a positive affirmation of the volunteer attribution should improve the accuracy of the data we are gathering about the Drupal ecosystem.
This now means a user can make issue comment attributions in the following ways:
- Without attribution
- As a volunteer
- On behalf of an organization and/or customer
- Both as a volunteer and on behalf of an organization and/or customer.
We are seeing a rate of around 30% of issue comments attributed to an organization, customer or as volunteer work. We hope to see that rate increase steadily.
To date, there have also been over 7,000 issue credits that have been awarded to over 2,300 users and 175 organizations. We are looking forward to displaying these credits on user and organization profiles in the month of June and beginning to find new ways to reward our top contributors.Content Strategy and Visual Design System for Drupal.org
Our collaboration with Forum One on developing content strategy for Drupal.org finished a few weeks ago. While recommendations were published in the issue queues earlier, we decided to use DrupalCon Los Angeles as an opportunity to present the work done and future plans in more detail, and get direct feedback from community members. Check out session slides or video if you want to know more on proposed changes to Drupal.org IA and content strategy.
Right now we are working on a few preparations steps before we can start implementing the changes. The first one of those steps would be a card sort exercise to validate our proposed IA and navigation with Drupal.org users. More blog posts and issues will follow as we move further.Issue Workflow and Git Improvements
The Drupal Association has been preparing a plan for a new issue workflow on Drupal.org - with some very exciting improvements planned to create a workflow that is both familiar to other repository hosts and yet unique to the needs of the Drupal community.
Perhaps the greatest value of the new Git workflow will be the presence of per-issue repositories and pull requests on Drupal.org issues without forking the issue conversations. Drupal.org will use git namespaces to provide every developer working on an issue with their own branch. Developers will be able to pull in the latest changes from HEAD, or changes from other users’ branches. Drupal.org will be able to summarize the commits, take the changeset and run tests, and help maintainers manage the merge process to push changes upstream.
This architecture will make additional features possible as well:
- The patch based workflow will continue to work - behind the scenes Drupal.org will create commits on namespaced branches from these patches so that these code contributions will be first-class citizens with the new git workflow.
- We will be able to provide an inline editor for code in issues - simplifying the workflow for contributions such as code style fixes, documentation, quick typo corrections, etc.
- We can provide the option to compare any two changes in an issue, giving us automated interdiff functionality.
- We can identify merge conflicts across issues - to hopefully prevent conflicts across issues before they become too deeply entangled.
This planning work culminated in a presentation at DrupalCon Los Angeles - where the community provided some great feedback, and dove into help us with some architectural components during the extended sprints.
Implementation of the new Issue Workspaces architecture will certainly take some time - but we’re excited to have a plan to work from as we move forward.Community Initiatives
Two Factor Authentication
May saw the initial roll out of Two-Factor Authentication on Drupal.org. Users with elevated privileges on Drupal.org now have the option of enabling TFA, and this may become required for all elevated roles in future.
Next we want to make two factor available to all authenticated users on Drupal.org. However, before we can allow every user to enable two factor it is important that we create a support policy for resetting accounts with TFA enabled, which is still under discussion.
DrupalCon Los Angeles was a great opportunity to meet with the community and talk about the current state of DrupalCI, and it’s upcoming release.
As of the end of May, DrupalCI is very close to being ready for integration on Drupal.org. All of the environments requested for the MVP deployment are functional, and the Drupal Association staff is getting ready to demo the integration with Drupal.org on a development site - at the same time work is continuing on the results site componenet and the test-runner’s results publishing capabilities.
DrupalCI will be rolled out in parallel with the existing PIFT/PIFR infrastructure for at least a few months following initial deployment as a sanity check.
Click-testing has identified several additional issues going into the end of May, and the Association team continues to work on knocking the issues down as they appear. When the current set of identified issues is resolved, we intend to notify the most active translation groups and ask them to perform a final round of testing on the staging environment.
When any issues from that final round of testing are resolved, we will deploy the D7 version of Localize.drupal.org.Revenue-related projects (funding our work)
DrupalCon Los Angeles was a productive and fun event for the community and the Association staff - in every way a success. At the conference we made several announcements about the upcoming DrupalCons, including 2016 locations.
First, we announced the opening of the call for papers for DrupalCon Barcelona, September 21st-25th. The call for papers for Barcelona closes on June 8th.
We then announced our next two conferences, and launched their websites.
DrupalCon Asia will be held in Mumbai in February of 2016.
And the next DrupalCon North America will be held on May 9th-13th, 2016 in New Orleans!Sustaining Support and Maintenance
The Git servers replacing our existing Git infrastructure are nearly ready for thorough testing and deployment. These servers give us a highly available cluster for git.drupal.org, in addition to increased storage capacity, a newer operating system, and dedicated hardware for Git services on Drupal.org.
Our Fastly CDN deployment for downloads (ftp.drupal.org) was a success, and soon to follow is the same new architecture for updates traffic (updates.drupal.org). This new architecture uses dynamic purging to reduce the number of update requests served by our origin servers. It also decreases the latency between packaging a release and serving the update data from a number of minutes to a few seconds.
As always, we’d like to say thanks to all volunteers who are working with us and to the Drupal Association Supporters, who made it possible for us to work on these projects.
The sky is truly the limit for getting value from attending a DrupalCon. There are so many ways to involve yourself, be a part of different opportunities to give back, and meet many people from all over the world and of all walks of life. At DrupalCon Los Angeles, we saw so many of our wonderful community members coming together to share their experiences and learn from each other -- and one of the places where this happened most was at our Monday summits.
A much anticipated part of my job is to host the Community Summit at DrupalCons. It’s a truly wonderful and humbling experience to stand in is a room filled with like-minded caring people, all of whom are ready to roll up their sleeves and work on some community topics and projects.
This DrupalCon we had some folks working on COD, which stands for Conference Organizing Distribution. COD packages all of the features event organizers need to create a website for their event. One of the coolest features is that they can update their site for multiple events and years. We also had participants discuss Drupal and non-profits. They sprinted on how to incorporate CiviCRM into their work, best practices for site builders to utilize and pro-tips for those in non-profit using Drupal.
Additionally, we had Donna Benjamin come out to represent the Drupal Association board. Donna and her group discussed governance and conflict resolution for the Drupal community. The group learned about the Community Working Group, its goals, and generated some great ideas on how to keep DrupalCon a warm and inviting event.
Other groups sprinted on community topics such as a Campus Ambassador program, International Collaboration and Community building, Large Scale Drupal, and Building local Drupal Communities.
All in all, it was a successful day, with around 60 participants from Australia, North America, South America, Europe, and Asia. However, the fun and networking didn’t stop at the end of the summit.
More on my experiences at DrupalCon Los Angeles next week, until then, cheers!
Community Outreach Coordinator
On March14th 2015, the Chinese Drupal Community gathered in Shanghai for DrupalCampChina 2015. With two keynotes, three one-hour presentations, nine thirty-minute sessions and a great after party, it was a busy day of learning and sharing ideas.
Learn from the best
China is a large country, but on the day of DrupalCampChina 2015, attendees from cities as far away as Beijing and Hong Kong traveled more than 8 hours to the event. One of the top reasons that many Chinese Drupalers were motivated to travel from afar was the keynote speakers, who were funded by Drupal Association. Many Chinese Drupalers appreciated the opportunity to listen and meet some of the top Drupal developers in the world; furthermore, they wanted to learn more about open source culture, the organization of the Drupal Community, and Drupal core development.
This year, we were thrilled to have Ryan Szrama and Clay Shirky as our two keynotes. Ryan’s talk, “Opening Doors with Open Source eCommerce,” was inspiring. His stories charted the path he took that defined his open source career, and how it shaped both Ubercart and Drupal Commerce modules.
Our other keynote, Clay Shirky presented on “Collaborative Technologies.” Analyzing the social aspects around recent technologies, Clay’s talk demonstrated how humans are not only producing the technologies, but how those technologies in turn shape the development, distribution, and community of the future. In a way, Clay’s talk explained how Drupal and its community was born and why they are what they are today.
Both keynotes were exciting and inspiring, and boosted our attendees’ confidence and enthusiasm for Drupal and Open Source.Growing Drupal in China
As Chinese philosopher Confucius once said, “Isn’t it delightful to have a friend coming from afar?” At DrupalCampChina 2015, Adam Malone from Acquia and Felipe Rubim from CI&T travelled to Shanghai from Australia and offered their insights and guidance. I took the opportunity to discuss methods of growing Drupal in China with them based on their experiences both in Asia Pacific and the rest of the world.
Many people at the camp had fun and were inspired watching Adam present “Let's talk about web experience management with Drupal 8”. Later on, while discussing the growth of Drupal in China, Adam mentioned Acquia’s broad interest in helping Drupal grow in Asian markets. His rule of thumb is to organize more local meetups and to encourage social activities for the group where Drupal isn’t the focus. By creating friendships within the community, we make stronger ties between its members. Adam also pointed out that it’s important to learn the decision making process within different business areas. Once the requirements and priorities are better presented, Drupal usually can offer many solutions with the ability for further customization. If we want to increase Drupal adoption from the top down in China, then the developers and site builders have a lot of learning to do, and we can’t wait to get started.
Felipe Rubim has assisted with the organization of this camp over the past six months. He firmly believes in the value of DrupalCamp China, which is why he motivated a whole team of Drupalers at CI&T to travel from Ningbo to Shanghai. Their bold presence gives many newcomers a great impression of Drupal. Felipe believes Chinese developers must see more opportunities related to Drupal before they join, and that businesses may also expect a bigger pool of Drupal shops and developers before they jump in. To try and tackle both at the same time, Felipe and his team suggest that the Drupal community should focus on:
- Localized Drupal marketing (Chinese material on Drupal, locally searchable/reachable);
- The translation of more key documentation, along with support on forums;
- Increasing the number of key advocates (e.g.: D.A., local evangelists, etc), people that can speak up for Drupal across different audiences/prospects
- Implementing and marketing flagship local cases;
In early 2015, CNN claimed that China had 557 million smartphone or tablet users, which was almost double of the entire U.S. population. One thing worth noting is that these 557 million users are 80% of the total number of Chinese internet users. Furthermore, as famous Google Exec Hugo Barra pointed out, Alibaba/Taobao in China sold $5.75 billion online in one single day, comparing to $2 billion for U.S. Cyber Monday. In fact, Barra’s Chinese company Xiaomi also recently won a Guinness record for selling 2.11 million phones in 24 hours.
Given that mobile and eCommerce has exploded in China, many Chinese Drupalers have been working on mobile and eCommerce related projects lately, which made it a popular topic at DrupalCamp. We discussed how two large sets of APIs offer the integration to this massive Chinese eCommerce and mobile world. One is from Alibaba, and the other is from Tencent (WeChat). Drupal and the Commerce module offer the amazing capability to integrate Content, Workflow and Commerce together, making it incredibly easy to develop for Chinese eCommerce sites. Drupal Commerce Kickstart Distribution also lets users open a new simple eCommerce site in hours. Hundreds of thousands of Chinese Taobao shop owners have been dreaming about customized shop displays and the Commerce Kickstart distribution can make their dream come true without writing any code. Clearly, there is a lot of opportunity for Drupal in China. Now what we need to do is begin growing.
The security aspect of Drupal was another popular topic at DrupalCampChina. China experienced a lot of cyber security challenges in the past 6 months, for example the recent man-on-the-side-attack. Most Chinese internet companies gradually learned the importance of cyber security and the advantage of using open source software like Drupal. At the camp, many attendees learned about the work and responsibilities of the Drupal Security Team, and learned about Drupal security advice compared to other popular open source software. Ultimately, we concluded that it will be almost impossible for most proprietary Chinese CMS software to catch up with the security practices that Drupal can offer.
Many small and medium businesses in China were eager to learn about optimization of hosting websites for Chinese markets. Both the technical aspects like bandwidth and connectivity, and political governance of Internet are quite different when the Internet crosses border in China. Some Chinese companies host websites in China, but then must deal with increasing market demand in the rest of the world, while many international companies are uncertain of the best practices to optimize speed for Chinese market. Numerous strategies have been discussed, but thanks to the power of Drupal (e.g. CDN module, Storage API), the implementation of many optimization strategies is only a marginal investment for many companies.Attending DrupalCon LA
DrupalCampChina 2015 was held shortly after the Chinese New Year. We took the opportunity to meet and discuss the plans for the near future. Many Chinese developers had a taste of the fun and value of this camp in Shanghai, and wanted to learn more about Drupal and its community. Therefore, we formed a team to travel to DrupalCon LA. Keith Yau, Jackie Chen, Jerenus Zheng, and Everright Chen had a great time at DrupalCon LA and had lots of exciting new ideas to bring back and share with our community in China. For most, this was both their first DrupalCon and their first trip to the US. They witnessed how well the Drupal community collaborated at Sprints; learned to communicate with many Drupalers both offline and online; and they were shocked to see how many potential career choices were available at DrupalCon. When they talked about this trip after they returned, it was certain that they were amazed and inspired. Nicely done, DrupalCon LA!
The Drupal Association is thrilled to announce the start of two new employees. Many of you may have met Mark and Gener at DrupalCon Los Angeles, but for those of you who were unable to make it, or who didn’t run into them, here’s the info about our newest additions to the team.
Mark Brandstetter, Account Manager for Technology and Hosting, Revenue Team
Mark Brandstetter is helping to take over Don Page's role as one of the new Account Manager's for technology and hosting based out of the Portland office. Mark is originally from the Midwest, but most recently spent 5 years living in Brooklyn, New York. Previously, Mark worked at Yelp and AdRoll, and his background in digital marketing and strategy will prove helpful to the team! In his free time, Mark enjoys cooking, hiking and hopes to one day join his his fellow Portland-Druplers at the DA in owning his very own urban chicken(s). Fingers crossed!!
Gener Umali, Drupal.org Advertising, Revenue Team
Gener Umali will be focused on Drupal.org Advertising, with an emphasis on thoughtfully creating connections between the right people and products. Prior to joining the Drupal Association, Gener worked as a Director of Advertising Sales. In a ten-year advertising career ranging from startups to big-names like CNET, Gener has worked with Mac and Linux Developers, but has never encountered a group as passionate as Drupal developers. He is humbled and inspired by their dedication. In his free time, Gener enjoys tinkering with cars, motorcycles, or anything with a motor. He enjoys travel, and has been to more than thirty countries. He also enjoys snowboarding, skiing, fitness, photography, and collecting old mechanical watches.
Please help us give a warm welcome to Mark and Gener. They’ll be working hard to generate funding for the project we all love, and are already proving to be fantastic additions to the Drupal Association team.
Welcome, Mark and Gener!