Topic: Drupal

Everyone dreams of making money while asleep. The term "passive income" is often defined as income that is received on regular intervals without requiring a great deal of work to sustain it. Usually some effort has to be put in upfront, but the payoff from passive income can last for years. Passive income is particularly relevant when it comes time to retire. Two techniques often recommended by financial planners are (a) rental properties and (b) dividend investing. Both can work well, not only as a retirement plan, but as a way to build steady income. Certainly the idea of collecting checks for the rest of your life with minimal effort sounds appealing.

Quite a few people that try to retire early are documenting their journey publicly. For example, Jason is trying to retire by 40 by investing in dividend growth stocks and Mr. Money Mustache retired at the age of 30 through rental properties. Many other great examples exist online; I love reading up on their stories and progress. There is a lot to like about their lifestyle too; a common theme among them is that they live frugally.

So what does this have to do with Open Source? I love Open Source and Drupal and would like to see even more contributors. I think a lot of developers would love passive income so they have the freedom to contribute to Open Source more, preferably even full-time. Many developers also live a frugal life; passive income may be a good option to explore. But also, what about a third passive income technique: (c) websites? I know several people who have a number of websites, some of which they haven't touched for months, yet they still bring in around $500 a month. Owning a few websites could provide a wonderful chance to earn passive income, and it so happens that many of us in the Drupal community have a talent for building websites ... Food for thought.

Topic: Drupal

Drupal Developer Days is a great tradition in Europe to provide space for developers and site builders to get together in the summer. After such prior locations as Barcelona and Brussels, the Drupal Developer Days is coming to Dublin this year!

The conference program includes great sessions on security, project management, automation, multilingual, mapping, REST, continuous integration and so on! Lots of opportunities to learn about Drupal and the entry ticket is only €25.

The event is also ideally timed to coincide with the last days before Drupal 8's API freeze. There is a whole weeklong sprint included for those who want to work on solving major and critical issues as well as any patches still viable before API freeze. If you are still to take your first steps to contribute, the Community Tools Workshop is for you to delve into giving back.

There will be a recruitment event there too, so when you register make sure to say that you're looking for a job. Acquia will be there so come talk with us about the work we do if you are interested in joining!

Topic: Acquia HostingAcquia

It's been a while since I wrote about Acquia Cloud so I wanted to give you a quick update. Acquia Cloud has experienced incredible growth so far in 2013. We recently crossed a milestone that I'm proud to share; we’re now running over 6,000 cloud instances on behalf of our customers in six Amazon regions stretching across North America, Europe, Asia and Australia. These instances are used to run a wide variety of Drupal sites; from e-commerce to collaboration to marketing sites, and more.

All that capacity served over 18 billion requests in May, with many more requests served via our CDN partnerships. Compared to last year, Acquia Cloud's traffic is up 200%. We also served over 232 terabytes of data in May. This astounding growth solidifies the scalability of Acquia Cloud. And it's only going to grow faster as Acquia is signing up larger websites.

Topic: DrupalDrupalConState of DrupalLocation: Portland

Two weeks ago at DrupalCon Portland, I gave my traditional State of Drupal presentation. A total of 3,500 were present at DrupalCon, a new record for DrupalCon attendance.

In good tradition, you can download a copy of my slides (PDF, 29 MB) or you can watch a video recording of my keynote (keynote starts at 14:00). The video of the White House guest appearance and the Drupal 8 demo video area also embedded in this post.

Topic: Drupal

Karen McGrane gave a great keynote at DrupalCon Portland on future-friendly content with Drupal. It's worth watching the video recording. I agree with Karen's vision for the future. With the proliferation of different devices, screen sizes and input devices, there is a growing need for structured content that can be reused in multiple channels.

From the early days, Drupal has been doing structured content and content reuse better than most competitors. Drupal's node system was introduced in Drupal 3 in 2001, and was ahead of its time compared to the "page tree"-model used by most competitors. With every release, Drupal has gotten better and better at structured content and content reuse, leading to things like CCK and Views in core. Still to date, Drupal is one of the leaders in modeling structured content and content reuse. It is is one of the primary reasons we've seen so much growth. It was great to see that recognized by Karen.

One of the biggest gaps in Drupal has been the authoring experience. Two of the most noticeable authoring experience improvements that we are adding to Drupal 8 core are WYSIWYG editing and in-place editing. Where I disagree with Karen is with her belief that in-place editing and WYSIWYG editing are bad. Sure, WYSIWYG and in-place editing definitely can be problematic when combined with structured content. However, I believe we’ve implemented them in a good way -- it can't be compared to Microsoft Word's blob-like approach. I wish that Karen better understood how we have implemented this functionality. It would have been helpful if she had offered concrete suggestions on what better solutions would look like. Until we know what better tools look like, I'm convinced that Drupal 8's approach to WYSIWYG and in-place editing are a big step forward. It makes for another intermediate step towards a bigger vision.

We've been talking about the advantages and disadvantages of WYSIWYG for more than 10 years now, and we still haven't figured out better approaches. The best we've been able to do is to evolve WYSIWYG editing and in-place editing to apply to individual chunks instead of the entire page, to generate clean markup and to better guide authors to make them aware that their input may end up in many forms of output.

While implementing Drupal 8's WYSIWYG and in-place editing functionality, a lot of attention was spent on ensuring that these features are compatible with structured content:

• WYSIWYG editors used to generate bad markup. Drupal 8's WYSIWYG editor guarantees clean markup thanks to the new "Advanced Content Filter" feature in CKEditor.
• Drupal applies WYSIWYG editors to individual form fields instead of the entire page. You are encouraged to break up your content in many fields. Similarly, in-place editing is triggered on the entity level, not the page level, which means the user declares his intent to edit a specific entity and can then edit a specific field within that entity. In-place editing is only designed for quick edits, it wants to delight the author for those small edits, rather than forcing him to go back to the potentially overwhelming back-end form every time. At no point are authors given the impression they are editing the entire page.

For a more detailed explanation, see Wim's article: “Drupal 8: best authoring experience for structured content?”.

Topic: Drupal

In Drupal core, we use issue thresholds to manage technical debt. Both critical (release-blocking) and major (non-release-blocking, high-impact issues) are considered. When we have more open issues than our thresholds, we do not commit new features.

Currently, we have 27 critical bugs, 41 critical tasks, 155 major bugs, and 149 major tasks. This is more than twice our current thresholds for critical issues, and about 50% more than our thresholds for major issues. We need your help to resolve these issues so that we can resume adding new features to Drupal 8. That would be a very exciting place to get to!

There are many ways to help, including not only programming but also updating these issues' summaries, testing the patches, and making sure the patches still apply. I encourage everyone to collaborate on major and critcal issues, and to consider making them a focus at the DrupalCon Portland sprints.

Post-Drupal 8's feature freeze, we find ourselves in a similar state as we did after Drupal 7's feature freeze:

• Some initiatives are mostly done, and now onto clean-ups.
• Others are mostly architecturally there, but still have some pretty big gaps.
• Still others are either not yet architecturally complete, have a major amount of integration/conversion work left, and/or have many outstanding critical/major bugs.

From here on out, we need to be more strategic about what patches we do and do not allow into Drupal core directly, and this means we have to make some tough decisions. Every patch we commit needs to not move Drupal 8 further from a "shippable state".

There are essentially two categories of initiatives (both official and unofficial) that are incomplete:

1. Code already in HEAD, that we do not plan on reverting, and completion of which is critical to releasing Drupal 8. Examples are CMI, Entity NG, Router conversions. Incremental patches committed to these issues help move Drupal towards release.
2. Code not currently in HEAD, or libraries that are sitting around effectively unused by the rest of Drupal. Examples are Twig, CSS re-organization, and parts of SCOTCH. Incremental patches committed to these issues move Drupal towards "uncharted territory", and could put the release of Drupal 8 at risk.

Therefore, the core committers plan to employ the following strategy when deciding what we do/don't commit to Drupal 8 going forward:

First, a patch will be evaluated to see if it belongs to a larger "meta" issue. For the vast majority of issues in the Drupal 8 queue, the answer will be no. For example, routine bug fixes and self-contained DX (Developer Experience) improvements can simply be committed once they're ready.

If an issue is part of a larger meta issue, the question will be whether that meta issue is critical to shipping Drupal 8. If so, the "does this move us towards release?" question is satisfied, and these patches will be committed as they're ready. An example of this is individual CMI conversions; we cannot ship Drupal 8 without all parts of it being deployable through the configuration management system. Similarly, we cannot ship with two methods of declaring routes.

If the meta issue is not deemed critical for release, but we can still ship Drupal 8 with part of it done, then we will also commit patches as they're ready. Views conversions are a good example of this. While it would be nice to ship Drupal 8 with all administrative pages converted to Views, we can still ship Drupal 8 with some converted and others not.

If the patch is part of a larger, non-critical meta issue, but getting part of it done is worse than getting none of it done (an incomplete state will hold up release of Drupal 8), then we're in a "danger zone" and need to look at possible options:

1. First, we should see if the patch can be re-worked, or parts of it split off, into self-contained issues. Then those issues' patches can just be committed via the normal process.
2. If there is no other option than completing the entire meta issue, then core maintainers will work with each individual team to determine a "cut-off date" for their work (which allows sufficient time prior to July 1 for integration), as well as the safest way for their work to continue without holding up the release. Possible strategies could include:
   • a larger patch containing the meta issue in its entirety, with no follow-ups, where it is still feasible to use a patch-based workflow (e.g. CSS re-organization).
   • a branch off the Drupal core repository that is merged in when deemed acceptable in the case of larger conversion efforts (e.g. Twig)
   • a sandbox project where larger refactoring is still necessary (e.g. SCOTCH).
   If the work is ready in its entirety (i.e. working upgrade path, passing all core gates) by the cut-off date, it will be eligible for Drupal 8. However, if not ready in time, it will have to be postponed to Drupal 9. While this is definitely painful for teams that have worked so hard but yet still miss the deadline, it is preferable to delaying the Drupal 8 release indefinitely.

Summary The bottom line is that every patch we commit to Drupal 8 from now on has to help us get to a shippable state: it has to work, be performant (or be a required stepping stone towards more performant code), be well-documented and well-tested, and provide the right developer experience (DX). Getting Drupal 8 ready for release will take a big effort, and the core contributors could use all the help they can get. Now is the time to jump in and help.

Topic: DrupalBranch maintainer

I'm pleased to share that Alex Pott (alexpott on drupal.org) has accepted my invitation to become another Drupal 8 co-maintainer, to help move along important issues as we gear up to head into code freeze and then release.

Alex has been working in Drupal for almost 6 years. While relatively new to the core development team, he has nevertheless been an instrumental force in the Drupal 8 Configuration Management Initiative (CMI). This development experience has given him a detailed understanding of various underlying Drupal 8 APIs, which makes him ideally suited to the task of reviewing and signing off on highly technical patches. Alex is furthermore thorough and patient in his technical reviews, and he has been a reliable leader and problem-solver during the Drupal 8 cycle. He is also currently taking time off from work, in order to have more time to dedicate to his family and to Drupal. It's a perfect fit.

When catch, webchick and myself were discussing who would be best to join the core maintainer team, Alex's name was enthusiastically +1ed from each of us. Please make him feel welcome!

Topic: DrupalAcquiaWordpress

A couple of weeks ago Acquia, the Red Hat of Drupal, reached out to fellow CMS founder, Matt Mullenweg of WordPress, to see if he would consider switching to Drupal. As luck would have it, this was enticing to Matt. He has long understood the value of the Drupal community and has been looking for ways to leverage our community to make WordPress even better. When Acquia suggested switching to Drupal, it dawned on Matt that this was certainly the easiest way to integrate with Drupal without irritating his webmaster.

"I have always wanted to be part of the Drupal community, where technical expertise is sought after to create some of the most advanced websites. This move demonstrates the synergy between WordPress and Drupal without the possibility of function name conflicts." - Matt Mullenweg

We, at Acquia, couldn't be more excited to have Matt and the Automattic team on board, because some things are just better together ... like e-mail and spam filters.

Several months ago I started working with some of our top developers to try to come up with a practical integration strategy between Drupal and WordPress. We had been struggling with this for some time when webchick said jokingly: "It would be a lot easier if they would just use Drupal instead".

To be honest, I felt a bit silly even talking to Matt about using Drupal, but I didn't know at the time that he had been struggling with exactly the same goal and the same problems. webchick's inadvertent idea has ushered in new possibilities for innovation and frankly this is such a fundamental change for us I can't even imagine the world as it was before.

I am very excited about this collaboration. WordPress and Drupal form a killer combination that can't be beat in today's CMS market. I can hardly wait for the WordPress developers to get their drupal.org accounts set up, so we can work together in ways that were never possible before. I also suggested xjm to setup extra "WordPress tables" at the DrupalCon Portland code sprint.

A new Drupal module has been created to ease the transition. The "WordPress_iframe" module will be available on drupal.org soon. It facilitates a rapid integration of existing WordPress sites into their Drupal counterparts. We are excited about the debut of this new module because it embodies the Drupal community's open acceptance of this partnership while it allows us to roll out literally millions of these new Drupal/WordPress sites over the coming weeks.

As part of the agreement, Matt didn't want to completely move away from the WordPress branding, so we have incorporated it into Acquia's logo. Phonetically Acquia is pronounced ah-kwee-uh, so we've swapped out our Q for the well-known WordPress "W". The name is still pronounced "ah-kwee-uh" but will now be spelled "Acwuia". This visually puts WordPress right in the center of our logo - exactly where it belongs. This is WordPress, powered by Drupal.

We are very proud of this partnership and look forward to serving many more customers as a result. You can expect many more great things from Acwuia coming soon.

Matt, your Red Press of Drupal t-shirt is on the way. Let's stand together as brothers, united in Drupal!

Topic: AcquiaIndustry: Non-profit

Last week it was Red Nose Day, a UK-wide fundraising event organized by Comic Relief every two years. A combination of television programs, local community events, social media and Drupal websites were used to raise £75 million ($113 million) in one day. On Red Nose Day everyone is encouraged to cast inhibitions aside, put on a Red Nose and do something funny for money. The money is used to make a difference to the lives of countless people across Africa and the UK who are facing terrible injustice or living in desperate poverty.

Rednoseday.com and Comicrelief.com are built in Drupal and the Acquia team have been supporting their talented web team with Drupal expertise and use of the Acquia Cloud to ensure a stable and massively scalable platform.

During the live show there were massive peaks in website traffic and every hour there were special heartfelt appeals within the program which results in a frenzy of donations. To deal with the sudden, massive spikes (they call them 'slams'), we had to employ 24 load balancers, 28 web heads and 2 database servers. We had an additional 12 load balancers and 2 web nodes ready for failover. This happens so quickly that it would not give you enough time to spin up additional servers once the traffic starts to ramp up. Along with the hardware, Acquia had 11 people helping with the infrastructure the night of the event.

As you can imagine, there is nothing like a live, six-hour televised national charity event where millions of dollars are at risk, to put fear into the hearts of any web team. To be able to do help inspiring charities such as Comic Relief gives the entire Acquia team an exceptional sense of accomplishment. I am very proud of their dedication and commitment to this project.

In fact, we've been doing our bit with some Harlem Shake videos from both our Reading (UK) and Burlington (US) offices to raise donations. It's not too late to help this tremendously worthwhile and life changing cause: https://www.rednoseday.com/donate.

Topic: MollomAcquiaDrupal

Today I'm excited to announce that we've released the next generation of Mollom - our Content Moderation Platform. For the past five years, we have worked hard to help companies stay ahead of the curve when it comes to content moderation. With today's release, I feel like we've secured our place as the leading enterprise-ready content moderation system.

With over 2 years in development, and 600 beta users, the new content moderation platform is built to help companies handle extensive amounts of user generated content with ease. The main features of the Content Moderation platform are:

• Easy team management. Site admins can add moderators, assign privileges, and monitor how moderators are performing - keeping an eye on productivity while trusting that no malicious content is making it to their site.
• Fast moderation. If we know it's spam, your team never sees it. If we're sure it's good content - we'll publish it to your site. For the content we're unsure about - moderators now have a very easy user interface where they can view the contributor, their comment, and their reputation, spam, and profanity score all within seconds. They can approve or decline, and even take bulk actions to speed things up.
• Custom filters. The system allows each user to create custom filters so they can focus on a specific subset of commenters. If they only want to see users with low spam and profanity scores - creating a filter takes just a couple seconds and they now have a customized view.
• Multi-site management. All customers can have from one to hundreds of sites in their system - which makes moderation for big brands with multiple site properties very easy. Adding a site takes just a couple minutes, and customers can view analytics separately across all site properties.

You can learn more on the Mollom site, the video below, or in the press release we issued this morning.

I'm really excited to finally show this off to the world, and continue to help more companies embrace social without fear!

Topic: Personal

I was quite surprised when I opened my email to find "You have been honoured as a Young Global Leader 2013".

The Forum of Young Global Leaders is a community formed by the most exceptional leaders from every region of the world and every stakeholder in society. The Young Global Leaders (YGLs) commit their energy and knowledge to the most critical issues facing humankind.

I feel very privileged to be included in such a diverse, yet cohesive group, that is passionate about shaping the future of the world. As a member of YGLs, I will work with others to initiate, develop and drive solutions on important, globally oriented issues, including health, education, the environment, global governance and security, and development and poverty. The past initiatives have ranged from freeing hundreds of millions of school-age children from parasitic worms, to a collaborative task force between company cafeterias and NGOs that is providing 23,300 children every day with school meals. Other projects include developing country-wide infrastructure for electric vehicles and sailing a catamaran made out of 12,500 reclaimed plastic bottles halfway round the world to draw attention to marine pollution and climate change.

Being a member will allow me to do of what I'm passionate about; evangelizing the Forum of Young Global Leaders about the benefits of Open Source in their missions, as well as directly putting to work the knowledge I have gained from my experiences with Drupal and Acquia. Can't wait to work with a group of leaders who are committed to "doing well and doing good".

Topic: Drupal

This Saturday and Sunday, March 9-10, over 30 locations around the world will participate in Global Drupal Sprint Weekend, coordinated by Cathy Theys (YesCT). The sprint weekend is a grassroots initiative for people all over the world to get together and contribute to Drupal. You can join a local sprint, start your own, or participate remotely in IRC.

The sprint weekend is a unique opportunity to make big strides on the Drupal 8 release, and I encourage everyone to find something you are passionate about and dive in. For example, you can help reduce Drupal 8's accumulated technical debt by targeting the major and critical threshold issues, to kick off our cleanup phase and make Drupal 8 stable enough that we can continue to innovate. We're currently at 18 critical bugs, 124 major bugs, 33 critical tasks, and 130 major tasks. It'd be great to see how many of these we can fix by this time next week! :-)

Or, try your hand at upgrading a module to Drupal 8, and provide input and feedback on the "Developer Experience", as well as identify missing or incomplete APIs while we can still change them. You can find resources to help you with porting modules on the sprint wiki page.

Whatever you work on, blog or tweet about it after the sprint is done. Let us know what you worked on. You can also share what worked well for your sprint, or things you learned. Tag your posts with #SprintWeekend so we can use your feedback to help shape future sprints!

Finally, if you're local to the Boston area, Acquia is also hosting an Open Drupal 8 Core sprint in our Burlington office that will target core threshold issues, including work on the Blocks UI. Lots of active contributors to Drupal 8 will be here to help you find something awesome to work on. Stop by!

Topic: DrupalDrupal Association

Last summer, a number of Drupal community members as well as key figures from other major open source projects met in Portland for the first-ever Drupal governance sprint. The proposal from that sprint recommended the creation of a number of chartered "working groups" to better formalize the existing governance of various aspects of the Drupal project, now that our community is at its current scale. We have now chartered the first of these working groups: the Community Working Group. Thanks very much to everyone who participated in the vigorous community discussion and drafting efforts around this.

However, while the governance proposal coming out of Portland provided some fairly solid direction on the governance of the Drupal project itself, it left some pretty big questions unanswered as it related to the governance of Drupal.org. Drupal.org isn't just some ordinary website. While it was originally a small portal with a few hundred members hosted on a friend's shared server, it is now serving millions of page views to over 2 million unique visitors per month, as well as terabytes of data, and is home to almost a million active members, among them thousands of contributors committing code, reviewing patches, improving documentation, etc. at all hours of the day. The old "do-ocracy" model of getting things done on Drupal.org isn't scaling for our community anymore, and lack of clarity around decision-making has cost us repeatedly, in the form of slow progress on the Drupal.org Drupal 7 upgrade, Drupal Association funding challenges and staff inefficiency, and various community volunteer frustrations.

I've therefore spent time over the past few months talking with a number of members of the Drupal Association, various Drupal.org volunteers, Drupal core/contrib developers, as well as other interested parties, in order to determine how to put into place a structure that clarifies the decision-making processes around Drupal.org. The following is the overall proposal for Drupal.org governance we've come up with, as well as links to more specific draft charters for community review.

Overview

Note: the finer points of this can be found in http://buytaert.net/files/drupal-governance-plan-2013.pdf.

While "governance" can sometimes sound like a scary word, really it's about coming up with a way to:

• Make decisions fast,
• In as lightweight a way as possible
• Allowing affected parties to have a say,
• With clearly-defined processes and easy to understand decision-making.

Cracking this problem for Drupal.org provides us with less frustration/uncertainty among volunteers, more money and resources funneled into improvements, and better community velocity overall.

Governance mostly comes down to establishing "working groups" around major areas of the project, many of which already have governance in at least an ad-hoc basis. Working groups will consist of a chair, plus 3-5 members who are empowered to make decisions, then a team of N volunteers and/or DA staff to help carry out their tasks/policies. The working groups are only empowered to make decisions as a whole, not on an individual basis.

Drupal project governance / Drupal.org governance compared

For the Drupal project, we are working towards developing a number of working groups related to various aspects of the community (security, documentation, conflict resolution, Drupal core, etc.), with myself as the final decision-maker:

The working groups might be compared/contrasted this way:

Community working group Technical working group Security team Documentation team Drupal core X working group Guarantee a friendly and welcoming community for the Drupal project by upholding the Drupal Code of Conduct. Maintain technical policies, procedures, and standards as required to keep the technical side of our community operating smoothly. Maintain technical policies, procedures, and standards as required to keep our projects secure Make sure that we have high quality technical documentation for Drupal, including the Drupal handbook and API documentation Provide technical leadership and project management for Drupal core development.

In the case of Drupal.org, however, it makes sense for this final decision-maker to be the Drupal Association, since they are ultimately responsible for the website, purchasing hardware, etc.

The working groups might be compared/contrasted this way:

Drupal.org infrastructure working group Drupal.org software working group Drupal.org content working group Responsible for all infrastructure-related needs of the Drupal project, including the servers, Git repositories, mailing lists, DNS management, e-mail management, network, server access and security. Responsible for guiding the planning, architecture, development, and maintenance of the Drupal.org websites. Responsible for maintaining policies around the major content areas on Drupal.org. They also manage the overall look and feel and voice of the website, including its information architecture and design elements.

This means that the existing webmasters group members can choose to participate in either the Drupal.org software working group or Drupal.org content working group, or both.

Needless to say, groups will often have to work together. For example, to answer the question of whether to keep developing project module or move our collaboration tools to Github, we'll have to get the following groups together: (i) the Drupal.org software working group because it affects the features of drupal.org, (ii) the Drupal.org hardware working group because they may need to host new features, (iii) the technical Working Group because it impacts how we collaborate on software development, and (iv) the Drupal Association Board of Directors because they have to write the check.

Draft charters for review

This is a work in progress. Please help shape the future of Drupal.org governance by reviewing and commenting on the following proposals:

• Drupal.org Infrastructure Working Group
• Drupal.org Software Working Group
• Drupal.org Content Working Group
• Technical Working Group
• Community Working Group (Already formalized)

Our plan is to allow everyone in the community to provide feedback during the next 3 weeks. Then, around the end of March I will post updated drafts based on community feedback, with the aim to finalize the charters by the mid-April.

Onward and upward

I'm really excited about the possibilities for Drupal.org in the future with this governance structure. My hope is that this helps address some of the ambiguity and confusion around the current structure, while at the same time not being overly constrictive.

Thanks in advance to everyone for their participation in helping to shape the future of Drupal.org!

Topic: Acquia

We just celebrated our two year anniversary of Acquia's expansion into the European market. It has been a phenomenal two years and as a result, we have grown to over 50 employees in Europe. Our UK office is bursting at the seams so we're about to move into our new digs in Reading. We also have a growing presence in the Benelux, France and Germany.

We are looking for more great talent, no matter what level you're at. If you are passionate about working on some of the most challenging Drupal projects alongside other talented Drupalists, we want to talk to you! Please stop by Acquia's booth at DrupalCamp London, or contact us at careers@acquia.com. We currently have vacancies for Client Advisors, Customer Support Coordinators, Customer Advocates, as well as Sales and Marketing roles.