Xeno Media: Faster, Smarter Web Maintenance through (Semi) Automation

Planet Drupal - Fri, 2018/04/13 - 8:00pm

Website maintenance is needed to address any vulnerabilities identified in software over time.

Thanks to the collaborative nature of the open source communities of Drupal and WordPress, we get a heads up when new vulnerabilities are identified (Read more about why open source is great for business). When the fixes and security updates for those vulnerabilities are released, they need to get installed and tested as soon as possible.

There are benefits and drawbacks to fully automated website maintenance, just as there are for fully manual website maintenance. The best path is to do both.

A machine never forgets a step in a process. It just gets confused when it's presented with the unexpected. A person can introduce human error, but can create novel solutions to unexpected problems.

Benefits of Automation Fast

Machines are much faster than people at reading code. Computers are fast and they can apply steps in a process much quicker than we can. They can also run multiple tests simultaneously, leading to even more time savings. There is an inherent, upfront time investment to program the scripts, but once that time investment is made, all subsequent processes are significantly faster.

Accurate

A machine can repeat the exact same process, in the exact same way, thousands of times. It can also log processes, errors and results at every step, every time. A person couldn’t log the results of every single step, or, if they did, they would take significantly longer than usual to finish each test and there’d be many more opportunities for human error. This accuracy in repetition and recording means that we have a clearer picture of the test and its results available to us.

Thorough

A machine checks everything within the scope you set for it and nothing outside of it. It doesn’t care if “this little change isn’t going to mess anything up”. It checks everything you set it to. That total adherence to process is key when testing a system with multiple, related, and moving parts, like a website.

The Human Advantage We’re innovative

A machine never forgets a step, ever. It just gets confused when presented with the unexpected. People are needed to create novel solutions to those unexpected problems. A developer can invent new processes, fixes, and features and create new applications for existing ones. 

We can give human feedback

A machine won’t tell you if the final result looks professional and aesthetically appealing. It can only check if objects are rendered in specific predefined colors, object types appear in the correct spot on the screen and so on.  A person can see if everything comes together and looks good. They can provide feedback on the branding of your site, give you unquantifiable assessments of how your site makes them feel as a person.

We can do ad-hoc testing

Automated tests have to be developed, programmed and tested themselves before they can begin to test new features for your site. A person can run through some manual tests very quickly when there isn’t a need to develop a deeper test.

How we put it into practice

Our system automatically creates a cloned copy of our clients' sites and applies updates. It then runs a battery of automated tests on the patched clone sites, out of public view, before notifying our developers to review the results. 

Once the updates are confirmed to be working properly and that nothing untoward is going on, the developer pushes the site to live. If anything is off, the developer can dive right in and make any needed adjustments, again, behind the scenes. For anyone visiting a site during this process, it's business as usual.

Website maintenance solutions like this are critical to any business. Gone are the days (if ever they existed) of launch and forget websites. Websites vulnerabilities are identified over time as intruders' techniques become more sophisticated. You can't prevent 100% of all data breaches, just like you can't prevent every burglar from trying to break into your house. But you can fix the porch light when it gets broken, and tighten up the deadbolt if it gets loose. So long as you've got someone checking the lights and testing the doors.

 

Keep up your Website's Performance with Website Maintenance!

 

 

Categories:

Security public service announcements: Drupal Core - Highly Critical - Public Service announcement - PSA-2018-002

Planet Drupal - Fri, 2018/04/13 - 7:36pm
Description

This Public Service Announcement is a follow-up to SA-CORE-2018-002 - Drupal core - RCE. This is not an announcement of a new vulnerability. If you have not updated your site as described in SA-CORE-2018-002 you should assume your site has been targeted and follow directions for remediation as described below.

The security team is now aware of automated attacks attempting to compromise Drupal 7 and 8 websites using the vulnerability reported in SA-CORE-2018-002. Due to this, the security team is increasing the security risk score of that issue to 25/25

Sites not patched by Wednesday, 2018-04-11 may be compromised. This is the date when evidence emerged of automated attack attempts. It is possible targeted attacks occurred before that.

Simply updating Drupal will not remove backdoors or fix compromised sites.

If you find that your site is already patched, but you didn’t do it, that can be a symptom that the site was compromised. Some attacks in the past have applied the patch as a way to guarantee that only that attacker is in control of the site.

What to do if your site may be compromised

Attackers may have copied all data out of your site and could use it maliciously. There may be no trace of the attack.

Take a look at our help documentation, ”Your Drupal site got hacked, now what.”

Recovery

Attackers may have created access points for themselves (sometimes called “backdoors”) in the database, code, files directory and other locations. Attackers could compromise other services on the server or escalate their access.

Removing a compromised website’s backdoors is difficult because it is very difficult to be certain all backdoors have been found.

If you did not patch, you should restore from a backup. While recovery without restoring from backup may be possible, this is not advised because backdoors can be extremely difficult to find. The recommendation is to restore from backup or rebuild from scratch. For more information please refer to this guide on hacked sites.

Contact and More Information

We prepared a FAQ that was released when SA-CORE-2018-002 was published. Read more at FAQ on SA-CORE-2018-002.

The Drupal security team can be reached at security at drupal.org or via the contact form at https://www.drupal.org/contact.

Learn more about the Drupal Security team and their policies, writing secure code for Drupal, and securing your site.

Categories:

OPTASY: Adaptive vs Responsive Design: What Is the Difference? Which One Is Better for You?

Planet Drupal - Fri, 2018/04/13 - 6:40pm
Adaptive vs Responsive Design: What Is the Difference? Which One Is Better for You? silviu.serdaru Fri, 04/13/2018 - 16:40

Adaptive vs responsive design. Is there really a matter of “better vs worse”? What's the difference anyway?

For the boundaries sure look blurry enough. Especially since both types of web design provide you with a solution to the same challenge. The one you're facing as a web designer:

A design that should cater to all screen sizes.

Now, instead of delving into this confusion even deeper, let's shed some light on:
 

Categories:

Amazee Labs: Lessons In Leadership From DrupalCon Nashville

Planet Drupal - Fri, 2018/04/13 - 5:53pm
Lessons In Leadership From DrupalCon Nashville

Taking on a leadership position can be a very rewarding but also draining experience. I’d like to share some of the exciting things that stood out to me at DrupalCon in terms of leadership. In the last few years, I was able to take on a number different leadership positions such as CTO at Amazee Labs, running the #d8rules initiative or co-organizing camps in Austria and Switzerland. To me, it’s a deeply satisfying experience to be part of a team that works towards a common goal and see myself being able to help drive us to be successful. At the same time, leadership always felt very difficult to me. Why wasn’t I able to take decisions effectively? Why wouldn’t others follow my advice as I wanted them to?

Looking up to other leaders at work and in our community is really valuable to me. It allows me to feel inspired, keep improving, and relate my own struggle to the struggles of others. I’d like to share an overview of the things that inspired me during this DrupalCon Nashville.

Josef Dabernig Fri, 04/13/2018 - 17:53 Leadership lessons at DrupalCon Nashville

The Diversity & Inclusion team ensured me that fighting for a common cause with a well structured approach can lead to great results. This DrupalCon featured 40% speakers who identified as part of an underrepresented group. This is an awesome achievement and I appreciate the group and the DrupalCon program team who made this possible. I also really like how D&I tries to lead by example as they extend their attribution system to credit for non-code contributions such as attending an initial meeting. Finally, Nikki Steven handed over initiative leadership to Fatima and they mentioned how helpful it can be to distribute ownership of an initiative to make sure the cause is more important than the actual person leading it.

The Community Working Group (CWG), together with Jordana & George, explained their approach to ensuring safety within the Drupal Community. I appreciate the hard work they put into such a thoughtful process that helps us deal with difficult situations. An important aspect of the communication is to always try to separate internet and impact. A person might have the best intentions when they do something, but it is also really important that they understand the impact their actions have on others. A lot of the work that the CWG does goes into the mediation process. This brings disagreeing parties together to reach an understanding their own actions and how others feel about it. Not every difficult situation can be solved in a mediation process so it was great to learn that the CWG also relies on a careful process that leads to taking action if needed.

On Tuesday I was able to attend a Leadership workshop that was organized by the CWG and facilitated by Adam Goodman, Chairman of the Drupal Association. Adam is Director for the Center of Leadership at Northwestern University and I really appreciated his thoughtful approach to this workshop. Together as a group of roughly 50 attendees, we used individual and group exercises to discuss our different perspectives on leadership. Adam was able to make sure that there was a balanced discussion, added plenty of valuable insights, and reassured us that leadership is not always an easy topic. There was also a controversial discussion about the boundaries of leadership and I would like to thank Donna Benjamin for writing her thoughts on it.

In his keynote, Dries took a good amount of time to reflect on the leadership of Drupal. In his section on fostering the community, Dries presented his version of Drupal’s values and principles. I think this is an exciting move forward for us as a community to being able to define and iterate on our values and principles definition. I like how Dries stressed that he put a lot of effort into working on those but at the same time, that he also recognizes that they by no means will be perfect from the beginning. We’ll need a good amount of feedback & collaboration to help make sure that the values & principles definition of the Drupal community, as diverse as it is, serves the purpose and needs of our extensive community.

Rachel Lawson, Community Liaison at the Drupal Association, shared her story at the beginning of Wednesday’s keynote. I appreciated finding out how her feeling welcomed enabled her to become a key contributor and leader within our community. Rachel’s open and candid approach has always been a refreshing experience for me. Over the years, Rachel has always provided an open ear for me to discuss leadership challenges. It’s great to know there are people available that will listen to you and that want to help you to become better at what you do.

Finally, in the keynote itself, Steve Francia shared his very inspiring journey leading various open source community projects. There were tears in my eyes when I found out that Steve had been struggling with the responsibility of being the lead of these big, successful projects, especially when he wasn’t aligned with the project's goals anymore. Steve realised he needed to step down in order to focus on what he wants to work on. I especially appreciated Steve’s honest approach to giving genuine feedback to himself and us as a Drupal community. Steve’s presentation was full of great feedback for us a Drupal community and how we have inspired him to develop the communities he is working with.

Final thoughts

It’s awesome to look at what others do when it comes to leadership and get inspired by them. But without introspection, true leadership cannot really emerge. I’d like to conclude with my own notes from the leadership workshop:

What is teamwork?

The work performed together as a group of individuals towards shared goals.

What is leadership?

Everything that helps the teamwork such as leading by example, principles, coaching or being a servant leader.

How do people learn to become more effective team members, followers, and leaders?

When we learn to express our needs, feelings, and provide feedback. When we understand what our peers need and learn how to create safe spaces for interaction and collaboration. When we listen actively, take responsibility and are open to learning something new every day.

What’s next?

Today is the most collaborative day for DrupalCon. At the sprints we all come together to work on Drupal initiatives. On my side, I’m looking forward to meeting the DrupalCon Europe team to discuss the program. If you are interested, check out the website to get your ticket or sign up as a volunteer.

I want to get better at enabling others. In that spirit, I am looking for a new #d8rules initiative coordinator. If you are interested in helping the Rules module to Drupal 8, this might be a great opportunity for me to learn how to coach you. Feel free to reach out to me.

Categories:

CU Boulder - Webcentral: Change My View: D8 isn't the best upgrade path for 1000 D7 EDU sites

Planet Drupal - Thu, 2018/04/12 - 9:31pm

Like many other Drupallers, I'm in Nashville this week. Unlike previous DrupalCons, I'm less excited about being here than previous year. While my team at the University of Colorado Boulder currently manages 1000 D7 sites, it looks increasingly less likely that we'll be upgrading to D8.

Angela “Herder of Cats” Byron recently tweeted...

OK, time for our semi-annual poll/group therapy session. ;)

What are the 5 top things you or your clients run into problems with on #Drupal 8?

— webcsillag (@webchick) March 9, 2018

The last time she tweeted this, we responded with a few specific issues we had at the time. After maintaining a handful of D8 sites in production for a few months and meeting with 20+ developers and designers from teams at all campuses in the University of Colorado system earlier this year, we now have a more comprehensive list to answer the question of why the University of Colorado Boulder isn't moving forward with updating the Express install profile to D8.

We've already written and presented about some of these, but my goal at DrupalCon is to find people who will convince me that we're wrong or point out what we're missing. I can't emphasize this enough that we really want to be proven wrong and pointed in the right direction about some of these so we can stop evaluating options other than D8:

  • When running 1000 sites, D8 requires much more CPU and memory resources to render the same HTML output as D7. Because D8's core can't be run from symlinks, it doesn't support atomic deployments or efficient opcode caching when running 1000 copies of the same codebase. This leaves traditional multisite or containers as options. Multisite's limitations are well known. Containers add complexity and require more resources that provide little benefit when running Drupal as a service.
  • D8 seems slower than D7 or other PHP alternatives. Everything from updating with Composer, menu routing, and editing pages. While this isn't as much of an issue for users browsing the sites since the output is cached and served by Varnish, the slow renders are very noticeable to editors and developers.
  • Install profile inheritance is still unstable. Despite 6 years of development, being included in popular D8 distributions like Lightning, and Dries blogging about it, it is unclear this core patch will ever be committed. Acquia drove the patch in a different direction for over a year trying to make a base profile's dependencies optional. When we suggested making the Umami demo a sub-profile of Standard, it became clear how few members of the core team knew anything about profile inheritance or supported updating core to support it.
  • Our experience with highly promoted D8 "successes" like Webform wasn’t great. The D7 version of Webform reports more than > 440K installs. The D8 version, ~32K reported installs. This isn't a criticism of @jrockowitz or the Webform code. He is doing amazing work, but we felt the lack of a larger base of developers contributing fixes and extending Webform when working with Webform and Views.
  • The lack of license compatibility with 2 of the 3 most popular licenses off the island (Apache-2.0 and GPL-3.0) is a dead end. This is related to @jrockowitz's repeated attempts to find away to give work away while earning a living developing for Drupal. Drupal's strict GPL policies now seem to stifle development vs. encouraging it when compared to the more balanced approach taken by projects like WordPress.
  • D8’s Layout Initiative isn’t a good match for how we currently manage Drupal as a service. Now that the dust has settled on 8.5.0, we'll post more on this soon.
  • We're finding fewer well-maintained contrib projects. While using contrib projects can be golden handcuffs that only get you 80% of a solution with options and assumptions you end up fighting against in the end, we've mastered the embrace and customized/extend/contribute back approach. We rely heavily on contrib and actively contribute back. We maintain or co-maintain projects used by more than 100K D7 sites. When we find fewer D8 contributions to meet even 80% or our needs, it makes less sense to develop our own solutions for Drupal than a leaner, faster framework.
  • The "let's throw everything in core" approach results in an increase in critical security releases for code we aren't using. This is an issue in environments with distributed development, systems, networking and security teams, where a security team is periodically scanning for known vulnerabilities with tools like Qualys, Arachni or Nessus. With something like sa-core-2018-001, these scans don't care that the Comments module is disabled or even deleted. They scan the code looking for anything less than Drupal 8.4.3 and report that the entire code base is a security issue. We can respond to the issue by explaining that it is mitigated by X, but that fact remains that more code in core will likely translate to more staff time applying security updates to 1000+ sites. Ideas like what @davidhernandez suggested package Drupal both framework (essential core) and product (core) aren't getting the same attention from the DA as demos and other improvements to attract non-technical users to Drupal. LTS support services offered for D6 aren't really enough since they aren't altering the code fingerprint that the security scans are looking for.

I wish moving from D7 to D8 was an obvious move for us. It would make my job much easier. After watching the normal stability requirements ignored to sneak Umami into 8.5 and realizing that the initiatives DA was promoting for core (automatic updates, project browser, telemetry and in site announcements from the DA) are NOT features we'd use in our service, it's becoming increasingly clear our needs no longer align with what is driving the priorities of the Drupal project. When I evaluate D8 through the Umami demo, it's clear that we aren't even the target audience for what the project wants to highlight to people evaluating it. When we evaluate a framework, product or service, part of what we evaluate is the cost to maintain. When fatal errors are acceptable in a demo after a core update, we question whether we'll be able to easily apply upgrades if the developers most familiar with this framework can't upgrade the demo?

The Express install profile we've developed and use at multiple campuses is the 5th most popular D7 distribution on Drupal.org.

It's not that the entire University of Colorado system is against D8 either. Both the University of Colorado Colorado Springs (UCCS) and Auraria Library are both using D8, but for very different use cases than the Web Express service we offer for free on the Boulder campus.

UCCS is moving from Ingeniux to D8. For those of you who aren’t familiar with Ingeniux, it is a XML/XLST static site generator with limited features for dynamic content.  UCCS initial D8 offering has similar limitations to Ingeniux, but they are leveraging Migrate to move sites from Ingeniux to Drupal very quickly.  They are also hosting their Drupal 8 sites themselves on the most advanced server architecture within the CU system which well set them up well to add new features in the future.

Auraria Library is another high profile D8 site.  This site has more features and functionality than the UCCS sites, but it also has a small development team supporting a small group of content editors and is hosted on Pantheon.

While D8 makes sense for both of these use case, neither of these groups had insights on how we could overcome what we think are D8's short comings for the ~1000 sites we manage for the University of Colorado Boulder.

While I'd prefer to continue maintaining D7 sites while developing new projects in D8, the lack of clarity from the DA around the EOL of D7 is forcing us to invest time in evaluating alternatives now. When I read that Symfony 4.1's router is now the fastest PHP router, I get both excited and terrified. I'm excited since, in some ways, this would prove everyone that pushed to get off the island and collaborate with the larger PHP community right. I'm terrified because I realize that Drupal going from Symfony 3 to Symfony 4 most likely means D8 to D9. If D9 means the end of support for D7 and quarterly justification for running software our security team views as insecure, we have to go all in on a direction other than D8 soon.

We've spent some time trying to answer the question, "if not Drupal, then what?" If we can't figure out how to make D8 work for us, I'll post more about what we found when evaluating alternatives to D8. This week, I'm focused on trying to make D8 work well when hosting Drupal as a Service in higher ed.

If you see me at DrupalCon, PLEASE change my view. I won't be hard to spot.

I've started a thread on r/drupal/ for everyone who's not at DrupalCon.

Developer Blog
Categories:

Acro Media: Drupal Commerce 2: How to Add a Shipping Method

Planet Drupal - Thu, 2018/04/12 - 4:45pm

 

Drupal Commerce 2 shipping module let you quickly add and configure various shipping methods for your site. Out-of-the-box, you can easily set up basic shipping methods for flat-rate per-order or per-item shipping options. The plug-in based system allows for more advanced shipping integrations with suppliers for real-time rate calculation.

In this Acro Media Tech Talk video, we user our Urban Hipster Commerce 2 demo site to show you just how easy it is to create a simple flat-rate shipping fee for your eCommerce store. We set it up and then run through the checkout so that you can see exactly what your customers would see.

Its important to note that this video was recorded before the official 2.0 release of Drupal Commerce useing a beta release of the Commerce Shipping module. You may see some differences between this video and the current releases. The documentation is also evolving over time.

Urban Hipster Commerce 2 Demo site

This video was created using the Urban Hipster Commerce 2 demo site. We've built this site to show the adaptability of the Drupal 8, Commerce 2 platform. Most of what you see is out-of-the-box functionality combined with expert configuration and theming.

More from Acro Media Drupal modules in this demo

Categories:

myDropWizard.com: Drupal 7 Long-Term Support ... for after official support ends!

Planet Drupal - Thu, 2018/04/12 - 4:24am

You may already know that we've been providing Drupal 6 Long-Term Support (D6LTS) for over two years.

What we have been hearing over and over lately - especially at Drupalcon - is "what about Drupal 7?"

Typically, only two major versions of Drupal are supported at once: the latest version, and the previous one. Right now, that means Drupal 7 and Drupal 8.

We don't know when the community's support for Drupal 7 will end or if the community itself will do some kind of LTS. But we do know that community support will come to end at some point. While the details will depend on what the community does, we just wanted to let everyone know...

We intend to provide Long-Term Support for Drupal 7, in order to keep your site going long after the end of official support!

Read more to learn more about our plans for D7LTS...

Categories:

Chapter Three: Presentation: A Drupal City

Planet Drupal - Wed, 2018/04/11 - 5:57pm

I presented at DrupalCon Nashville about working with the City of San Francisco to make a better transaction experience for residents. Moving beyond a simple content site where we tell users how to do things, we are now developing a brand new city website in Drupal 8, where residents can actually do those things online. The presentation covers how to run an agile project of this scale in a government environment, what we did as a part of discovery, where we're going, and how our foray into design & development is progressing so far.

Here are the slides to digest. Don't hesitate to reach out if you have any questions!

Categories:

ComputerMinds.co.uk: Rebranding ComputerMinds - Part 1: Branding

Planet Drupal - Wed, 2018/04/11 - 4:35pm

After seeing our logo alongside others in various places it was clear to us that we were starting to look outdated. The work we were doing was getting more and more advanced and our branding did not reflect this. We needed to rebrand.

We briefly stripped things right back and considered a company name change, as although it did represent what the company did when starting out, it didn’t completely represent what we do now. We quickly concluded that this was too big a change, it was important to keep the name for existing clients and also for the history of the company. This discussion did get me thinking, though, and although we weren’t changing the name, we could look toward representing the name differently. We often referred to the company as ‘CM’ and I was keen to explore using this more prominently.

One thing not so obvious that I wanted to consider was future proofing. Our current logo looked outdated, I wanted to avoid this happening to the new logo a few years down the line. It was important not to choose current styles that could easily date.

Although discussions and research revealed that the squares in our logo didn’t represent anything, we kinda liked them so I was happy to attempt to include them. This would also create a better transition from the old logo, as if I was to consider representing the company without the name fully displayed, including squares would mean it would be recognisable to existing clients.

Next up, we would need a new font, or two. Only one for the logo but I also wanted a second font for body text that could be used throughout the whole brand. Having had concerns from working with clients about the cost of using certain fonts, as these would be used throughout all official documentation these fonts had to be free to use.

What was really important to me when facing the rebrand was colours. I felt the old red was too aggressive and strangely even felt it was an outdated colour. Perhaps it was through looking at it for many years, either way it needed to change. I was very keen to introduce multiple colours that would not just be used in the logo, but spread throughout the website and other places. These colours needed to be softer, happier, current and accessible. I was also very keen to be exact even on somewhat less important colours like greys and blacks.

The last thing I needed to consider before starting was responsiveness. More and more over the years I’ve seen companies creating multiple logos that can be used in differing scenarios based on available space. Having had issues with our wide logo in the past I was keen to create 3 logos for this reason.

So, now I had a clear understanding of what I needed to create and of the deliverables we would have at the end of the process. Here’s a summary list of everything above, which I used as a reference when completing the next phase.

  1. Experiment using CM instead of ComputerMinds in logo.
  2. Future proof as best possible.
  3. Use squares in logo.
  4. Use free fonts; we need a heading and a body font.
  5. Create a palette of soft, happy, current, accessible colours
  6. Create logos for use at different sizes.

Now I could begin. It was important to create SVGs for scalability, so using Adobe Illustrator I started experimenting with squares, fonts and colours before settling on the final look. Rounded corners, 3D effects, crazy concepts were all experimented with but following feedback sessions from other ‘Minds I was happy with what we had.

 

I created three logos, each for use at different widths of available space and in different scenarios. The smallest did not display the company name as discussed earlier, I was excited to see it in use.

In addition to the logos, I also chose two free-to-use fonts from Google Fonts and compiled an assortment of colours fitting earlier requirements. Being keen for consistency, I produced a brand guidelines document available to all ‘Minds. This detailed each logo and in which circumstance to use each, all the colours with a sample and both hex and RGB values. Each heading and paragraph font samples and other specific brand guides, leaving no room for confusion and inconsistencies going forward.

 

Categories:

ComputerMinds.co.uk: Rebranding ComputerMinds - Introduction

Planet Drupal - Wed, 2018/04/11 - 4:30pm

After 7 years of our brand and website, we felt the outdated look did not reflect the cutting edge work we were doing, so it was time for a change.

With the relatively recent release of Drupal 8 there was no better time for a complete overhaul, so I set to work. But before any website design or build could begin it was important to rebrand the company fully so this could be carried through and be consistent throughout.

We released the new site and branding at the same time a few weeks ago. This series of articles talks through the complete process from rebranding to designing, development and deployment. Here’s what we’ll look at:

  1. Branding
  2. SEO analysis, planning and Information Architecture
  3. Website design
  4. Pattern lab
  5. Development
  6. Migration
  7. Deployment
  8. Lessons learned and looking forward

So, let’s jump straight in to the branding!

Categories:

Jeff Geerling's Blog: Installing PHP 7 and Composer on Windows 10, Using Ubuntu in WSL

Planet Drupal - Wed, 2018/04/11 - 3:34pm

Recently, I detailed how to get PHP 7 and Composer installed natively inside Windows 10, but there are now two easy ways to get started with PHP on Windows, since Windows 10 introduced the Windows Subsystem for Linux (WSL), which is by far the easiest way to run Linux environments within Windows.

To get the WSL, and in our case, Ubuntu, running in Windows 10, follow the directions in Microsoft's documentation: Install the Windows Subsystem for Linux on Windows 10, and download and launch the Ubuntu installer from the Windows Store.

Once it's installed, open an Ubuntu command line, and let's get started:

Install PHP 7 inside Ubuntu in WSL

Ubuntu has packages for PHP 7 already available, so it's just a matter of installing them with apt:

Categories:

OPTASY: Collecting Requirements for Your Project: Best Tools and Techniques

Planet Drupal - Wed, 2018/04/11 - 2:06pm
Collecting Requirements for Your Project: Best Tools and Techniques adriana.cacoveanu Wed, 04/11/2018 - 12:06

Instead of stubbornly keeping yourself stuck, thinking that “Clients don't really know what they want”, how about you... give them a hand? Helping them identify and clearly articulate their needs! Especially since there are so many effective, tried-and-tested tools and techniques that grant you success when you're collecting requirements for your project.

And it sure is worth all the effort. Or, to put it this way:

It will cost you/your project a lot if you're doing it wrong.

In this respect, numbers make the most reliable proofs:

Behind the great majority of project failures, there's a lack of clarity on requirements.

Therefore, learning how to collect requirements for your project:
 

Categories:

Tim Millwood: Should Drupal's installer be tailored towards the Enterpise?

Planet Drupal - Wed, 2018/04/11 - 12:47pm
Should Drupal's installer be tailored towards the Enterpise?

In Dries' keynote at DrupalCon Nashville 2018 he discussed a blog post by Matthew Grasmick where the "first impression" or installer experience of Drupal was compared with Wordpress, Symfony, and Laravel. A tweet by Jeff Eaton then got me thinking:

Kind of weird that the #driesnote compares the install complexity of Drupal, Wordpress, Laravel, and Symfony. Why aren't AEM and Sitecore in there?

— Actually, (@eaton) April 10, 2018

Drupal powers about 2% of the web, but when looking at top websites, either by NASDAQ, FTSE, or number of visitors, Drupal powers a much bigger percentage of sites. This shows that Drupal is an Enterprise platform. When an enterprise level client is evaluating Drupal they would have much difference "first impression" experience than for example a hobbyist or blogger. Enterprise users would not often use the inbuilt installer, they'd be looking at tools such as Drush or Composer to facilitate the installation for them via some kind of continuous integration platform. For example, in my day job we install an instance of Drupal most hours of the day, this is all handled by a python script running on iron.io.

When tweeting about this blog post I had an interesting response from Kevin Oleary:

#2 is already true. The question should be “should Drupal go back to the simple install and extend model that produced it’s period of explosive growth”

— Kevin Oleary (@kolearyUX) April 10, 2018

This tweet made me readjust my thinking. Drupal was almost a ground up initiative. Drupal may not have had it's success without people like me running a blog on it, contributing to it, and fostering it within enterprise organisations. Kevin also completely derailed what the conclusion of this post was going to be. The post was going to conclude with thoughts and ideas about making things easier for enterprise clients. However, maybe the proposal in Dries' keynote to improve the installer experience will help grow Drupal from the ground up, yet again.

timmillwood Wed, 11/04/2018 - 11:47 Tags drupal planet drupal-planet drupal Add new comment
Categories:

Specbee: How to configure views REST export in Drupal 8

Planet Drupal - Wed, 2018/04/11 - 8:34am

As all know, Drupal 8 is API driven first and keeps on adding in new API's which can be altered, extended for different decoupled Applications. When we talk about of decoupled Drupal, developers are allowed to use any technology frontend to bring in better User experiences. The actual UI experience is met when we present contents which fulfill the needs and requirements of the user.

Categories:

Agiledrop.com Blog: AGILEDROP: What got us here, won't get us there.

Planet Drupal - Wed, 2018/04/11 - 6:46am
Day one at DrupalCon Nashville started with the traditional keynote by Drupal's founder Dries Buytaert. Dries talked about what is new and where are we heading. One of the main announcements was the Promote Drupal Initiative. The goal of this initiative is to start a promotional campaign that will enable to make Drupal known and loved by new decision makers. The same evening I happen to see a tweet from a formal active Drupal contributor that was questioning the director of Drupal. The tweet that got deleted very quickly said that we are compromising quality with marketing bulls**t. My first… READ MORE
Categories:

Drupal Association blog: We asked, you answered. DrupalCon North America Location Survey Results

Planet Drupal - Tue, 2018/04/10 - 10:17pm

Over the past few years, we’ve been listening to the community ask for explanation as to why we haven’t had any DrupalCon North America locations outside of the United States - after all it’s called DrupalCon North America, not DrupalCon U.S.A. This isn’t something we’ve taken lightly or ignored. DrupalCon North America is a major funding source for the Drupal Association, and in that regard, a major funding source of Drupal.org and the engineering work that keeps the code accessible and available for everyone.

We’ve looked at many North American cities over the years - a lot in the United States, but some outside the U.S. also. For our 2019 and 2020 location search we directly asked several cities in Canada to bid on this event, so that we could do financial and accomodation comparisons against U.S. options. I will give you the spoiler up front: 2019 and 2020 will not be in Canada or Mexico, they will be in the United States. The cities that bid were competitive, but in the end did not prevail due to things like dates overlapping with Passover and simply not being the most effective bid in comparison to the winners.

But with these cities in mind, and the voices of the community in our ears, we decided to go deeper and explore what a Canadian or Mexican DrupalCon would look like, based on survey feedback from the community and hard numbers from our history and bids. Here is that deeper look.

First, let me say that Drupal Association staff does not think solely about finances in making these decisions. We spend a lot of time getting to know the city, the vibe, the culture and the openness to a community that celebrates diversity and has a plethora of unique needs. It’s important to you, and it’s important to us.

Let’s also acknowledge that DrupalCon North America greatly underwrites the Drupal Association work and Drupal.org infrastructure to help keep the project going. So while money is not the only thing - it is very important.

So, let’s talk about finances. There are a lot of things that go into making a DrupalCon financially viable, and we did a pretty thorough job of outlining them all in our blog series last fall dedicated to the finances of DrupalCon Europe. I suggest you take a look at those, specifically the one on Solving The Financial Problem to get a good understanding on what it takes to make DrupalCon happen. A truncated look shows that there are three (3) main aspects and goals to DrupalCon finances:

  • Expenses: everything we have to spend to make it happen
    • Goal: produce show on a tight budget
  • Revenue, attendee tickets: how many people will show up
    • Goal: people show up
  • Revenue, sponsorship commitment: how much sponsors will spend to support the event
    • Goal: sponsorships have value and continue to support us
Expenses

In a look at expenses there are a vast array of things that we spend money on - from facilities and catering to program guides and paying the person who watches coat check while you’re sprinting on Friday. And overall, the proposals we’ve received from cities within the United States and outside of the United States have been fairly competitive for expenses directly related to the venue and infrastructure. That’s awesome!

There are some other indirect expenses we consider too like cost of hotel rooms, which can greatly affect whether people can afford to stay in the city, and generally Canadian cities - for example - tend to be a bit more expensive than some of our U.S. options. Other considerations include: whether the city is a airport hub for enough domestic and international flights to get people there easily; ease of setting up foreign bank accounts or legal business statuses in specific countries in order for us to operate there (including increased staff time to do this); cost of import/export for our production gear (this applies to sponsors as well). There are workarounds for some of these, and that's what we explore during an RFP process. Based on estimates, a DrupalCon outside the United States tends to pen out to be at least 10% more expensive than one within the United States - that’s around $100,000 - $150,000.

In general, the expenses section is a place where we can explore more work-arounds and potentially find a way to make a non-U.S. DrupalCon happen. However, because of DrupalCon team capacity during 2017 (the timeframe while we were contracting 2019 - 2020 cities) this is not something we could do for the immediately upcoming DrupalCons.

Revenue

As I mentioned above, revenue from DrupalCon North America is a driving force for the Drupal Association and Drupal.org. Ensuring attendee ticket sales and sponsorship revenue remain consistent from year to year (or grow) is extremely important to helping ensure our staff are funded and Drupal.org is kept running. In order to make certain that funding holds consistent and we’re able to keep Drupal.org healthy we need to keep DrupalCon North America profit margins around roughly 30-35% per event.

Here is where things start to fall apart for non-U.S. cities in the immediate future.

To better evaluate our current and potential revenue, we created 2 surveys and put them out to the public/community to participate.

Survey targets:

  • Past and potential attendees
  • Past and existing sponsors
Revenue, Attendee Ticket Sales

DrupalCon attendees are the main audience where we hear the cry for a DrupalCon outside of the United States. Individual ticket sales make up 62% of our event revenue.

Our survey to attendees had 1258 respondents. 92% of those people have attended DrupalCon North America in the past, and 99% have attended a DrupalCon somewhere in the world. So this sample represents people who are likely to attend in the future.

Since we’re talking about Revenue, it’s important to know who is paying for these people to attend. 79% of these attendees are funded by their employers. That’s a significant number and important to think about as we move into a business case for companies to attend DrupalCon.

Next, we followed up on that. “If your employer funds your trip to DrupalCon, are they willing to pay for you to travel outside the U.S.?” Of our 79% - 38% answered “No” (this number is adjusted from the chart percentages below because the question was “IF your employer pays”, and 120 people answered that they pay for themselves). That means, of our original sample size, now only 71% of attendees are still eligible to attend (22% self-funded + (62% of 79%) = roughly 71%).

Based on the responses, our projected revenue would decrease by roughly 29%.

Revenue, Sponsorships

Sponsors provide 38% of DrupalCon revenue, their sponsorships currently underwrite the cost of early bird tickets (that’s a whole other problem), and the event would simply not happen without them. They provide the foundation for the event in financing, they are the exhibit hall, and a large portion of our attendees are sponsor company employees. If sponsors don't come, we lose money and don't achieve a key purpose of our event: connecting new business decision makers with agency owners to grow adoption.

In our survey to them, we presented a hypothetical scenario in which DrupalCon takes place in Canada.

Our leading question for sponsors was “Do you do business in Canada?” and 70% of 44 responses said “No”. This doesn’t eliminate possibility, but it is the trend for the questions that followed.

We also asked “Would you sponsor a DrupalCon in Canada at same levels as you have in the past?” and only 39% of respondents answered “Yes”.

Of these sponsors, many wrote anecdotally that they simply could not support a business case for having an event in Canada.

To Sum it Up

While we’ve had advanced talks with Canadian cities, and two were finalists for 2019 and 2020 making it past initial RFP rounds, as of now we haven’t found solutions to enough of these issues to fit a DrupalCon North America within our required profit margin.

The numbers presented by the surveys would put profit margin for a DrupalCon North America outside the U.S. at an estimated 6% profit margin and would risk actually losing money for the Drupal Association. A situation and risk we cannot allow the Association to bear.

This is disappointing for many of us - and we know it is for many of you as well. We would love to see DrupalCon North America move beyond the U.S. borders, however it will not happen until at least 2021.

In between now and our next location RFP, we will continue to look at models that might make this possible. As we explore these challenges and talk more with sponsors and cities, we will share with the community any progress or new challenges as they become relevant. We appreciate your passion on this topic and understand the concerns with hosting DrupalCon in the United States for another two (2) years, especially based in our current climate of travel restraints in to the U.S. We wish it were not difficult for our community to come together.

We appreciate everyone who took the time to participate in our surveys and were honest about their desires, motivations and realities of their travel to and participation in DrupalCon. We're excited seeing many of you in Nashville this week, and hope many of you will join us in 2019 for DrupalCon Gedfyuikemndjfkioiujhtrj - sorry, something has happened to my keyboard. ¯\_(ツ)_/¯

_________________________

We invite you to share thoughts in the comments section below on how you think DrupalCon 2019 and 2020 can help provide more opportunity for community members outside the United States to participate in the event - either through direct attendance or through virtual participation of some kind. What are your ideas?

File attachments:  Business in Canada.png Employer Fund International Travel.png WhoFunds.png Would you Sponsor.png
Categories:

Mobomo: Mobomo Speaks at the Government Summit

Planet Drupal - Tue, 2018/04/10 - 10:08pm

The post Mobomo Speaks at the Government Summit appeared first on .

Categories:

Dries Buytaert: Defining Drupal's values and principles

Planet Drupal - Tue, 2018/04/10 - 5:47pm

Since its founding, Drupal has grown a great deal, and today there are thousands of contributors and organizations that make up our community. Over the course of seventeen years, we have spent a great amount of time and effort scaling our community. As a result, Drupal has evolved into one of the largest open source projects in the world.

Today, the Drupal project serves as a role model to many other open source projects; from our governance and funding models, to how we work together globally with thousands of contributors, to our 3,000+ person conferences. However, the work required to scale our community is a continuous process.

Prompted by feedback from the Drupal community, scaling Drupal will be a key focus for me throughout 2018. I have heard a lot of great ideas about how we can scale our community, in addition to improving how we all work together. Today, I wanted to start by better establishing Drupal's values and principles, as it is at the core of everything we do.

Remarkably, after all these years, our values (what guides these behaviors) and our principles (our most important behaviors) are still primarily communicated through word of mouth.

In recent years, various market trends and challenging community events have inspired a variety of changes in the Drupal community. It's in times like these that we need to rely on our values and principles the most. However, that is very difficult to do when our values and principles aren't properly documented.

Over the course of the last five months, I have tried to capture our fundamental values and principles. Based on more than seventeen years of leading and growing the Drupal project, I tried to articulate what I know are "fundamental truths": the culture and behaviors members of our community uphold, how we optimize technical and non-technical decision making, and the attributes shared by successful contributors and leaders in the Drupal project.

Capturing our values and principles as accurately as I could was challenging work. I spent many hours writing, rewriting, and discarding them, and I consulted numerous people in the process. After a lot of consideration, I ended up with five value statements, supported by eleven detailed principles.

I shared both the values and the principles on Drupal.org as version 1.0-alpha. I labeled it alpha, because the principles and values aren't necessarily complete. While I have strong conviction in each of the Drupal principles and corresponding values, some of our values and principles are hard to capture in words, and by no means will I have described them perfectly. However, I arrived at a point where I wanted to share what I have drafted, open it up to the community for feedback, and move the draft forward more collaboratively.

While this may be the first time I've tried to articulate our values and principles in one document, many of these principles have guided the project for a very long time. If communicated well, these principles and values should inspire us to be our best selves, enable us to make good decisions fast, and guide us to work as one unified community.

I also believe this document is an important starting point and framework to help address additional (and potentially unidentified) needs. For example, some have asked for clearer principles about what behavior will and will not be tolerated in addition to defining community values surrounding justice and equity. I hope that this document lays the groundwork for that.

Throughout the writing process, I consulted the work of the Community Governance Group and the feedback that was collected in discussions with the community last fall. The 1.0-alpha version was also reviewed by the following people: Tiffany Farriss, George DeMet, Megan Sanicki, Adam Goodman, Gigi Anderson, Mark Winberry, Angie Byron, ASH Heath, Steve Francia, Rachel Lawson, Helena McCabe, Adam Bergstein, Paul Johnson, Michael Anello, Donna Benjamin, Neil Drumm, Fatima Khalid, Sally Young, Daniel Wehner and Ryan Szrama. I'd like to thank everyone for their input.

As a next step, I invite you to provide feedback. The best way to provide feedback is in the issue queue of the Drupal governance project, but there will also be opportunities to provide feedback at upcoming Drupal events, including DrupalCon Nashville.

Categories: