Flocon de toile | Freelance Drupal: Improve user experience with Paragraphs on Drupal 8

Planet Drupal - do, 2016/10/20 - 12:00pm

The Paragraphs module is a very good alternative to a WYSIWYG editor for those who wants to allow Drupal users ans editors to make arrangements of complex pages, combining text, images, video, audio, quote, statement blocks, or any other advanced component.


Aurelien Navarre: We should all have a Kenny in our lives

Planet Drupal - do, 2016/10/20 - 10:54am

Let me tell you a story. When I joined Acquia in April 2011, the Support group was a small pool of passionate and talented drupalists working day and night to service our customers. And there was Kenny, aka webkenny. The vocal, outspoken and hilarious personality that was going to accompany Tim Millwood and I every morning when we were holding down the fort during EMEA hours, as the company was scaling up.

So, yesterday evening, when we received an email informing us Kenny had passed away, this brought back all those memories, and a deep sadness, because we all fought closely together to make things right and help each other.

It is with great sadness that we learned today that Kenny Silanskas has passed away. This is a terrible loss for Kenny’s family, for us at Acquia, and for the the Drupal community.

Kenny joined Acquia in 2009 and was instrumental into building the Acquia spirit and bringing the energy needed to wake up everyday and start all over again. Not without a lot of laughter.

...and certainly not without killing it on stage.

When he decided to take on another challenge, I recommended him on Linkedin and wouldn't change a word today:

Kenny is a natural-born leader who has a passion for sharing knowledge and moving mountains. From Client Advisor to Technical Account Manager and then Support Team Manager, he has always gained respect from his peers both technically and by his positive and energetic attitude. Today I'm better at what I do thanks to the high standards of customer satisfaction Kenny taught me about.

Because, yes, Kenny was quite a character, a generous and kind-hearted man, but also an excellent troubleshooter and technical lead. Maybe you remember his epic DrupalCon London presentation with the 8-bit Dries?

Life's full of surprises. Kenny had just come back to Acquia. We were so happy. But unfortunately, at the end of September he suddenly resigned. I didn't really understand what was happening and didn't ask questions. So, when he last tweeted a few days ago, I obviously didn't imagine this would mean so much, after all.

Life is not a series of unfortunate events, but change that evolves you with each challenge. And no, that's mine. Not Confucius.

— Kenny Silanskas (@webkenny) October 17, 2016

Acquia's co-founder sums it best.

My heart goes out to the family of @webkenny. He was a force of nature on this earth, and I lament his passing. RIP Kenny. Sing with angels.

— Jay Batson (@jab) October 20, 2016

Never forget that smile. You will be sorely missed, my friend.

A GoFundMe has been set up in his memory. Please consider donating.


qed42.com: Ionic and Android 6 Runtime Permissions

Planet Drupal - do, 2016/10/20 - 9:46am
Ionic and Android 6 Runtime Permissions Body

Android Permission Provisioning has changed recently, If an app is using Android SDK API level 22 or below, users are asked for all the permissions in bulk at the time of installation i.e. Without granting permission user can not install the app. Now with Android 6's security patch called Run Time Permission (API level 23 and above) the app while in use can request for specific permission when the need arise ( similar to iOS ) e.g. you will be asked for the location's permission when you actually try to access the location of the device.

To work with runtime permissions on Ionic, you would need to install Cordova diagnostic plugin which gives you the function to fetch the status of the native api's exposed to the app. If a certain permission is mandatory for you app you can prompt the user to grant access to proceed. Further you have specific functions for granting permissions.

Install the plugin

cordova plugin add cordova.plugins.diagnostic

To avail the features of Run Time Permission, you have to build the app with Android platform 6.

Check you current Android platform version

ionic platform

If the version of your Android's Platform is below 5, you will need to update it to 5 or above.

Remove android platform:

ionic platform remove android

Install Android platform version 5 or above:

ionic platform add android@5

In config.xml, set the target of sdk version to 23


So far we are all set to ask user's for permission on the fly. We will have to call a functions to fetch the status of particular permission for the app. On the basis of the status we will ask the user to grant permissions or ignore it.

Add the following function in your app.js in $ionicPlatform.ready() function.

This will make $rootScope.checkPermission() global and you can call it whenever you wish to check if the user has given the permission to fetch device's location.

$rootScope.checkPermission = function() { setLocationPermission = function() { cordova.plugins.diagnostic.requestLocationAuthorization(function(status) { switch (status) { case cordova.plugins.diagnostic.permissionStatus.NOT_REQUESTED: break; case cordova.plugins.diagnostic.permissionStatus.DENIED: break; case cordova.plugins.diagnostic.permissionStatus.GRANTED: break; case cordova.plugins.diagnostic.permissionStatus.GRANTED_WHEN_IN_USE: break; } }, function(error) {}, cordova.plugins.diagnostic.locationAuthorizationMode.ALWAYS); }; cordova.plugins.diagnostic.getPermissionAuthorizationStatus(function(status) { switch (status) { case cordova.plugins.diagnostic.runtimePermissionStatus.GRANTED: break; case cordova.plugins.diagnostic.runtimePermissionStatus.NOT_REQUESTED: setLocationPermission(); break; case cordova.plugins.diagnostic.runtimePermissionStatus.DENIED: setLocationPermission(); break; case cordova.plugins.diagnostic.runtimePermissionStatus.DENIED_ALWAYS: setLocationPermission(); break; } }, function(error) {}, cordova.plugins.diagnostic.runtimePermission.ACCESS_COARSE_LOCATION); };


Here is a link of the code snippet.

Of course, you can choose to skip all this and stick to sdk target version 22, but you will miss out the new cool feature of Android 6 and amazing user experience. 

abhay.kumar Thu, 10/20/2016 - 13:16

Agiledrop.com Blog: AGILEDROP: Which big names use Drupal?

Planet Drupal - do, 2016/10/20 - 9:10am
I saw a post recently about another Drupal 8 site that got launched. It was Rainforest Alliance. Nothing special at first. But then, out of curiosity, I clicked on it and checked it. While I was admiring the impressive pictures of the forests, I suddenly remembered that over a month ago I read an article about city of Boston launching its website on Drupal. Then it hit me. Who are the »big names« that Drupal can show off to the world and say 'These are our most proud members'? As you may have heard or read or anything else, Drupal is a free and open-source content-management framework that… READ MORE

myDropWizard.com: Drupal 6 security update for Webform

Planet Drupal - wo, 2016/10/19 - 7:35pm

As you may know, Drupal 6 has reached End-of-Life (EOL) which means the Drupal Security Team is no longer doing Security Advisories or working on security patches for Drupal 6 core or contrib modules - but the Drupal 6 LTS vendors are and we're one of them!

Today, there is a Less Critical security release for the Webform module to fix an Access Bypass vulnerability.

When using forms with private file uploads, Webform wasn't explicitly denying access to files it managed which could allow access to be granted by other modules.

You can download the patch for Webform 6.x-3.x.

If you have a Drupal 6 site using the Webform, we recommend you update immediately! We have already deployed the patch for all of our Drupal 6 Long-Term Support clients. :-)

If you'd like all your Drupal 6 modules to receive security updates and have the fixes deployed the same day they're released, please check out our D6LTS plans.

Note: if you use the myDropWizard module (totally free!), you'll be alerted to these and any future security updates, and will be able to use drush to install them (even though they won't necessarily have a release on Drupal.org).


BlackMesh: Don’t Set Fire to your Laptop: Managing Multiple Projects without Losing it! (PART I)

Planet Drupal - wo, 2016/10/19 - 6:30pm

Thanks to everyone who participated in this year’s New England Drupal Camp – otherwise known as “NEDCamp.” A special thanks to those of you that attended my session and to the organizers for putting together an excellent conference!

Upon posting my presentation slides online (you can find them here: https://nedcamp.org/new-england-drupal-camp/sessions/dont-set-fire-your-laptop-learn-how-manage-your-multiple-projects), I realized they’re not going to be terribly helpful since I am rarely inclined to condense all of my talking points into a slideshow. Therefore, I decided to write a two-part blog that will elaborate on crucial points I made during the presentation; this first post will focus on task prioritization and keeping all your projects and clients straight.

Throughout my presentation, we discussed different things to consider when trying to prioritize multiple projects. Three categories come into play for me when determining overall priority: 1) Client; 2) Tasks, and; 3) Other factors.

In this corner of our industry, we work with individual clients of varying sizes. It‘s therefore essential for us to understand each client’s priority.

There are six factors I take into account when prioritizing my client accounts:

  1. Budget. This is generally the only factor people use in prioritization.
  2. Client Deadlines. In my kick-off meetings, I always talk about deadlines with my clients. Questions such as, “Do you have any contracts ending we need to know about?” “How about internal blackout dates?” “Any launches coming up?” Asking these questions can give us a lot of insight to the client expectations as well as what is important to them. This is also a great start for a candid conversation around those dates and expectations.
  3. Growth potential. If your current project with the client is a proof of concept or one of a series of projects, prioritize it as though you have those additional projects or the proof of concept was successful.
  4. Internal or external. Internal customers are often a bit more flexible with their deadlines and priorities with respect to external customers. Learn where that priority lies, and, if the project is critical to the organization, you need to know that when prioritizing as well.
  5. Partnership potential. This is something that can often be overlooked. If a client has potential for partnership (e.g., sending you more business, being vocal on social media, participating in a case study) take that into consideration when prioritizing.
  6. Relationship. If the relationship with the client is in a bad space, I want to make sure I take that into consideration and use the project as an opportunity to turn things around.

There are four factors for determining overall priority based on tasks:

  1. Importance. We’ll talk a lot more about importance vs. urgency in the next post, but, in short, a task is important if it moves you towards the goal of your project.
  2. Urgency. A lot of people equate urgency with importance, but these are distinct things. Urgency is deadline based and is not related to the project goals.
  3. Value. When picking what task to prioritize, higher value tasks will go to the top.
  4. Effort. If a task is low effort, but still important, those will often get prioritized just to get them complete and out of the way.

Other factors I take into account when looking at my priorities are:

  • Political ramifications
  • Overall impact
  • Overall risk to the project, client, and relationship.

When taking these factors into account, I consider the whole picture when determining my priorities. Going off just one or two of these can lead to dangerous blind spots for your projects.

Another challenge to managing multiple projects is to keep everything straight when it comes to client teams, deadlines, schedules, and resources. For all aspects of your projects, nothing is going to replace hard work. Take the time to learn your projects, teams, deadlines, schedules, and resources. Putting time into this will save time in the long run as well as potential embarrassment in front of your clients.

Be specific in your notes and don’t assume you’ll know what you mean later. It’s easy to fall into the trap of “I’ll remember what I meant,” but don’t take it for granted. If you’ve switched topics and projects three times since your notes, you probably won’t remember. Aim to write your notes as if another team member will be reading them.

For your clients, don’t underestimate the power of face time and building relationships. This not only helps you keep things straight, but also essential to a successful project. While we don’t always have the luxury of traveling to client site, there are things like conferences, hangouts, and Skype to help grow these relationships.

The first thing I do when assigned a project is read the statement of work (SOW) or contract. Knowing the documented details helps me keep things straight and facilitates conversations about changes and expectations.

Schedules, deadlines, and resources often require similar different tactics. For all three of these, I recommend you keep a master calendar. Know who is working on what and when. This will avoid overscheduling as well as insight into your team members’ priorities.

There is a good chance your resources are working on more than just your projects. Get to know your team members’ priorities. Your number one project may be number three for them. Knowing these priorities can help you schedule accordingly.

In the upcoming second half of this series, we’ll discuss common pitfalls to managing multiple projects and how to best utilize your quieter times to make your busy times more manageable.


Like this story? Follow us on Facebook and share your thoughts!

DrupalProject Manager

Dries Buytaert: Nasdaq using Drupal 8 for new Investor Relations websites

Planet Drupal - wo, 2016/10/19 - 4:59pm

I wanted to share the exciting news that Nasdaq Corporate Solutions has selected Acquia and Drupal 8 as the basis for its next generation Investor Relations Website Platform. About 3,000 of the largest companies in the world use Nasdaq's Corporate Solutions for their investor relations websites. This includes 78 of the Nasdaq 100 Index companies and 63% of the Fortune 500 companies.

What is an IR website? It's a website where public companies share their most sensitive and critical news and information with their shareholders, institutional investors, the media and analysts. This includes everything from financial results to regulatory filings, press releases, and other company news. Examples of IR websites include http://investor.starbucks.com, http://investor.apple.com and https://investor.fb.com -- all three companies are listed on Nasdaq.

All IR websites are subject to strict compliance standards, and security and reliability are very important. Nasdaq's use of Drupal 8 is a fantastic testament for Drupal and Open Source. It will raise awareness about Drupal across financial institutions worldwide.

In their announcement, Nasdaq explained that all the publicly listed companies on Nasdaq are eligible to upgrade their sites to the next-gen model "beginning in 2017 using a variety of redesign options, all of which leverage Acquia and the Drupal 8 open source enterprise web content management (WCM) system."

It's exciting that 3,000 of the largest companies in the world, like Starbucks, Apple, Amazon, Google and Facebook, are now eligible to start using Drupal 8 for some of their most critical websites. If you want to learn more, consider attending Acquia Engage in a few weeks, as Nasdaq's CIO, Brad Peterson, will be presenting.


Third & Grove: Third & Grove releases a Hybris Drupal integration module

Planet Drupal - wo, 2016/10/19 - 4:58pm
Third & Grove releases a Hybris Drupal integration module mike Wed, 10/19/2016 - 10:58

Mediacurrent: Webinar: International SEO + Drupal with Lingotek

Planet Drupal - wo, 2016/10/19 - 3:15pm

If you're a digital marketer, SEO is likely one of your many priorities. Since Google released "Mobilegeddon" last April, your primary focus may have shifted to mobile optimization - but have you noticed a struggle to successfully reach and engage with prospects from across the globe? If you target multiple countries and languages, your site needs to be optimized not just for Mobile SEO, but for International SEO as well. 


Web Wash: How to Make Fields Persistent in Drupal 8

Planet Drupal - wo, 2016/10/19 - 12:01pm
I wrote a custom module recently where I needed to programmatically attach a field; similar to how a Body field gets added to content types. If you create a content type, via the "Content types" page, a Body field is automatically added to the content type. If you don't need the field just delete it, but the default functionality is to have it added. I wanted this same functionality in my custom module; when an entity is created a field is programmatically attached to it. So I reverse engineered how the Body gets added to content types. In the Node module, the Body field is exported as field.storage.node.body.yml and the field is attached using the node_add_body_field function.

Blair Wadman: Understanding Drupal 8 Routes and Controllers

Planet Drupal - wo, 2016/10/19 - 10:33am

Two weeks ago I wrote about routes and controllers in the introduction to namespaces. This week we are going to take a much closer look at routes and controllers. 

So, what exactly is a route and a controller?

When you create a custom page in Drupal with code, you need both a route and a controller. You define the URL for the page with the route. And then you create a controller for that page. This will be responsible for building and returning the content for the page.


A route determines which code should be run to generate the response when a URI is requested. It does this by mapping a URI to a controller class and method. This defines how Drupal deals with a specific URI.


Controllers take requests or information from the user and decide how to handle the request. For the example module in this tutorial, the controller is responsible for generating the content and returning it for the page.

Read on to learn more about routes and controllers in Drupal 8 modules...


Enzolutions: A week in Colombia

Planet Drupal - wo, 2016/10/19 - 2:00am

Last week I had the opportunity to back to Colombia as para of my tour Around the Drupal world in 140+ days.

To be honest, this stop wasn't planned, during my visit to France the border control officer inform to me about a situation with my passport, I was almost done with the space for new stamps. That situation forces me to try to get a new passport as soon as possible; After checking to Colombian embassy in Costa Rica, I confirm that renew my passport in Costa Rica wasn't an option due the return time. For that reason, I have to travel to Colombia to renew my passport there.

With this un expected trip I tried to use in as many activities I could. In Drupal Side, I participated in a Drupal Meetup organized by Seed, and particularly by Aldibier Morales. They rent and space and organize the event to enable me to talk about Drupal Console and Drupal Community in general, I enjoy the Q & A session, where I could provide some points of view I have about how to handle local communities.

With my new passport on my hands, I start a marathon to visit my mother and father familly located in Bucaramanga, Santader. Was really good because for many years I haven't visit them.

So, as many time in my #enzotour16 I overcome the adversities and transform in something positive as much I could it.

Airplane Distance (Kilometers) San Jose, Costa Rica → Bogota, Colombia → San Jose, Costa Rica 2.576 Previously 106.561 Total 109.137 Walking Distance (steps) Dublin 39.597 Previously 1.897.088 Total 1.936.685 Train Distance (Kilometers) Today 0 Previously 528 Total 528 Bus/Car Distance (Kilometers) Today 796 Previously 2.944 Total 3.740

NEWMEDIA: How To Use HTML Meta Tags to Tailor Your Story When Your Content is Shared Across Social Media Platforms

Planet Drupal - wo, 2016/10/19 - 12:47am
How To Use HTML Meta Tags to Tailor Your Story When Your Content is Shared Across Social Media Platforms We are thrilled when clients seek us out to create beautifully designed and highly functional websites. However, we often find ourselves spending a lot of time to convince clients that creating compelling content is a critical component of finding and growing a highly engaged audience. Once they are on board, they begin to realize that creating great content isn’t always easy and can take a lot of time and effort. Rick Manelius Tue, 10/18/2016 - 22:47

It is disheartening to see what can happen when a link is shared on Facebook without proper meta tags, which often results in the wrong image or description being displayed. Not only is this sloppy, but it relies on users to manually correct that information (if the particular social media platform even allows for that flexibility). Worse, your audience is unlikely to take the time to make those same adjustments when they are sharing your content. The solution to this is to leverage HTML meta tags to tell and tailor your story to each social media platform.

A Real Life Example

Imagine you show up at a dinner party. You look around and discover that you don’t know anyone there! You keep scanning the unfamiliar faces when someone bumps into you and strikes a conversation. Inevitably, the other person asks you “so, what do you do for a living?”

Such a simple question, but you probably have anywhere from 2-5 canned responses to pick from depending on the background of the person that asks. If you had an inkling that the person worked in a similar industry or knows of the company you work for, you might provide a somewhat detailed answer going into specific nuances that they might understand and appreciate. On the opposite end of the spectrum, you might overwhelm someone that has no frame of reference. Here you are more likely to give a generic answer, which is why I simply tell my mom “I work with computers” and that’s sufficient to keep the conversation going.

In short, different people get different answers based on what will best support the conversation with that person or audience. We now need to apply those same principles for your content as it is interacted with on different social media platforms.

Part 1: Creating Your Sharing Strategy

Before we discuss the mechanics, it’s important to review your goals for each social media platform. Similar to the dinner party analogy, there are a variety of factors that you need to consider when deciding on what to communicate.

While the following is an overly simplistic breakdown of LinkedIn, Facebook, and Twitter, it will reinforce the need to tailor the messaging to each platform. Typically, Linkedin is geared towards conversations relating to careers, networking, business opportunities, and etc. Facebook started primarily as a way to connect with friends but has rapidly evolved into a mix that depends greatly on how you’ve been using it and what types of connections you already have. Twitter is based on real-time communication and information sharing.

It’s possible to create a piece of content that is useful to share across all 3 platforms at the same time, but it’s unlikely that it’s appropriate to present the content in the same way due to the different audiences and expectations on each platform. In short, posting an adorable picture of my two and a half-year-old daughter is encouraged on Facebook, arguably not something I would do on Twitter, and something I would never, ever do on LinkedIn.

Part 2: The Mechanics

If you’ve never built a website before, it’s unlikely that you’ve peaked under the hood to see the guts of an HTML page. If you’d like to get a very quick overview, here is a basic tutorial to get started. And if you really want to take a deep dive, here’s a comprehensive overview on Wikipedia.

Traditionally, when you share a link to the social media outlets, each platform does its best job to scrape the page’s HTML and try to extract the pertinent details. In general, getting the title of the page is a no-brainer, but the description can be messed up in a variety of ways. Sometimes it will pull the wrong description or give up and show nothing at all. Twitter’s character limit can also cause a truncation that can either change the meaning or not accurately describe the page.

Picking an appropriate image can often feel like a game of Russian roulette. While you may expect the platform to pull an image from within the article, it will sometimes pull an image from a completely unrelated part of the page. Unfortunately, this can not only harm the quality of the share result but sometimes the two juxtaposition can result in an unappealing or inappropriate result. Just imagine an article on depression pulling an image of a specific person’s picture and you may be setting the reader up with the wrong expectation.

This is where meta tags come in. Here we want to provide additional information to essentially tell the different platforms the specific information and media we want it to use instead of having them guess. For example, Facebook uses a protocol called Open Graph, which contains a specific subset of meta tags that live in the head region of the HTML page that is used for share results on their platform. Twitter has its own set of meta  tags that not only let you specify different information, but they also allow you to specify which style of share you would like to use (photo, video, standard, etc). And finally, Linkedin leverages the Facebook OpenGraph meta tags, so you can’t quite delineate the message between the two. Although, it is probably only a matter time before Linkedin creates their own version such that you can specify and tailor it to be a different introduction than Facebook.

Here’s a sample of the 9 lines of code we’ll be using to target our message.


If you’re using a CMS like Drupal 8, adding these values to any node page is very straightforward. Simply install the metatag module along with the OpenGraph and Twitter submodules. Then visit the configuration menu located at /admin/config/search/metatag. There you can specify the default global values and tokens for each of these meta tag options. You can then override these values on a per node basis by visiting the node edit screen and navigating to the meta tags section.

It’s worth noting that there are more meta tags available that can be used to specify content attributes ranging from a video URL to its  geographical location (i.e. longitude and latitude). Here’s just one list to emphasize the quantity and variety of tags available.

Part 3: The Outcome

Let’s use a real example from the newmedia blog. Several months ago, I published an article titled PCI Compliance & Drupal Commerce: Which Payment Gateway Should I Choose? Given the technical nature of the article for both developers and businesses, LinkedIn and Twitter would be the most appropriate place to share this page.

Without any metadata specified, the share result on Twitter is fairly bland. Here’s a quick screenshot showing it.

Figure 1: A tweet containing a link that lacks HTML Meta Tags for Twitter.

Alternatively, I can provide a very tailored title, image, and description that is far more likely to get someone’s attention and provide them with an accurate representation of the article itself.

Figure 2: A tweet containing a link with HTML Meta Tags for Twitter.

It’s important to note that these changes are more than just simple cosmetics. The share result is now taller because the images get more real estate and you’re able to leverage the full length of the description field. Both of these changes makes the tweet stand out more. If I had a video, I could put that in as well, allowing me to have an additional opportunity to communicate with a potential reader before they left Twitter. In short, I’ve dramatically improved my odds of reaching the audience.

Finally, we need to change the message on LinkedIn. By editing the "og:description" field, we could say something along the lines of "Keep your customer's credit card data safe while meeting your PCI compliance obligations for your Drupal Commerce site by using these recommended payment gateways." This way we are focusing more on a businesses need to protect their customers by choosing the appropriate gateways instead of appealing strictly to a security minded developer on Twitter.


As social media platforms continue to become a dominant traffic source for your content, it becomes even more important to put in the small amount of additional effort to ensure your story can connect with each audience. Through the proper use of metadata, you can easily achieve this goal with your existing content as well as make this a part of your editorial process moving forward.


PS. You can use the following preview tools to test what content will look like on Twitter and Facebook.


Last Call Media: A Reimagined Rainforest Alliance on Drupal 8 in 6 Sprints

Planet Drupal - di, 2016/10/18 - 10:56pm
A Reimagined Rainforest Alliance on Drupal 8 in 6 Sprints Kelly Tue, 10/18/2016 - 16:56


In the fall of 2016, the Rainforest Alliance and Last Call Media launched an exciting redesign of www.rainforest-alliance.org, built on Drupal 8 and employing impeccable agile software development methodologies.  Our productive partnership with the Rainforest Alliance resulted in a technically groundbreaking site that allowed users unprecedented access to the riches of their content after just four months of development.  The tool is now primed to drive the Rainforest Alliance’s critical end-of-year development activities. 


Drupal.org blog: Technical Advisory Committee formed to modernize developer tools

Planet Drupal - di, 2016/10/18 - 8:37pm

At DrupalCon Dublin, I spoke about The Association’s commitment to help Drupal thrive by improving the contribution and adoption journeys through our two main community assets, DrupalCon and Drupal.org. You can see the video here.

One area I touch on was my experience as a new code contributor. Contributing my patch was a challenging, but joyous experience and I want more people to have that feeling—and I want to make it as easy as possible for others to contribute, too. It’s critical for the health of the project.

At the heart of the Drupal contributor community are our custom development tools, including the issue tracker, Git repositories, packaging, updates server, and automated testing. We believe there are many aspects of Drupal’s development workflow that have been essential to our project's success, and our current tooling reflects and reinforces our community values of self-empowerment, collaboration, and respect, which we seek to continue to uphold.

It’s time to modernize these developer tools. To support the Association with this objective The Drupal Association created a Technical Advisory Committee (TAC). The TAC consists of community members Angie Byron, Moshe Weitzman, and Steve Francia, who is also our newest Drupal Association board member. The TAC acts in an advisory role and reports to me.

Building off of the work the community has already done, the TAC is exploring opportunities to improve the tools we use to collaborate on Drupal.org. The crux of this exploration is determining whether we should continue to rely on and invest in our self-built tools, or whether we should partner with an organization that specializes in open source tooling.

Our hope is that we will be able to bring significant improvements to our contribution experience faster by partnering with an organization willing to learn from our community and adapt their tools to those things we do uniquely well. Such a partnership would benefit both the Drupal community—with the support of their ongoing development—and potentially the broader open source community—by allowing our partner to bring other projects those aspects of our code collaboration workflow.

The TAC will use a collaborative process, working with staff and community to make a final recommendation. The TAC has already begun the process and has some very positive exploratory conversations. The TAC and staff will be communicating their progress with the community in upcoming blog posts.  


OSTraining: Drupal 8 Private Online Development

Planet Drupal - di, 2016/10/18 - 3:20pm

An OSTraining member asked how you could work online and stop bots from crawling a site in development.

We are going to use 3 modules to secure our drupal 8 enviroment so we can work online in private. 


Drupal core announcements: Help steer Drupal 8, participate in key initiatives

Planet Drupal - di, 2016/10/18 - 2:17pm

Maybe you have seen Dries Buytaert's DrupalCon keynote and are looking forward to all the goodies coming in future Drupal 8 versions. The truth is none of those things will happen without people who want to make them happen to solve their own challenges with implementing Drupal solutions. Are you implementing decoupled solutions and have issues you are working on? In the middle of building up a suite of integrated media solutions? These core team meetings are ideal to bring in these issues and discuss solutions and to be part of shaping up where Drupal 8 is heading. Read on for details.

  1. The JSON API and GraphQL meeting is held every week at 2pm UTC in the #drupal-wscii IRC channel.
  2. There is a monthly meeting on all API first work (REST, Waterwheel, JSON API, GraphQL) every third Monday of the month at 11am UTC in Google Hangouts.
  3. The Panels ecosystem meeting is on every Tuesday at 10am UTC in the #drupal-scotch IRC channel.
  4. There are two usability meetings every week! One at 7pm UTC on Tuesday while the other is at 7am UTC on Wednesday. Pick the best for your timezone. The meetings are at https://drupal.slack.com/archives/ux, get an invite at http://drupalslack.herokuapp.com/
  5. There is a default content in core meeting every other week on Tuesdays at 9pm UTC, and at 3pm UTC on the opposite weeks. Pick the best for your timezone. The meetings are at https://drupal.slack.com/archives/example-content, get an invite at http://drupalslack.herokuapp.com/
  6. There are two theme component library meetings on Wednesday, one at 1pm UTC and one at 5pm UTC Pick the best for your timezone. The meetings are at https://drupaltwig.slack.com/archives/components, get an invite at https://drupaltwig-slack.herokuapp.com/
  7. There is a media meeting every Wednesday at 2pm UTC, join in the #drupal-media IRC channel.
  8. The multilingual meetings are still going on for years at 4pm UTC on Wednesdays, join at #drupal-i18n in IRC.
  9. The workflow initiative meets every Thursday at noon UTC in #drupal-contribute on IRC.
  10. Wanna help with migrate? The team has Google Hangouts at Wed 1pm UTC or Thu 1am UTC on an alternating weekly schedule. The #drupal-migrate IRC channel is also used as a backchannel.
  11. Last but not least the new user facing core theme initiative meets every other Thursday at 3pm UTC in https://drupaltwig.slack.com/archives/new-core-theme-design, get an invite at https://drupaltwig-slack.herokuapp.com/

Below is the calendar of all the meetings, subscribe to the Ical feed at https://calendar.google.com/calendar/ical/happypunch.com_eq0e09s0kvcs7v5...


InternetDevels: Drupal 8 configuration management: really easier and faster

Planet Drupal - di, 2016/10/18 - 2:12pm

It’s a joy to see how Drupal 8 fulfills its promise of becoming more convenient in every way!

Read more