Planet Drupal

Subscribe to flux Planet Drupal
Drupal.org - aggregated feeds in category Planet Drupal
Mis à jour : il y a 16 min 58 sec

Drupal Association News: Announcing the Drupal 8 Accelerate Program

sam, 06/12/2014 - 00:16

We are thrilled to announce that, in collaboration with the Drupal 8 branch maintainers, the Association is launching a brand-new program: Drupal 8 Accelerate. Modeled after our Community Cultivation Grants program, Drupal 8 Accelerate is a $125,000 fund to help solve critical issues and accelerate the release of Drupal 8.

The Drupal community is filled with a plethora of opinions and ideas, but there’s one thing we likely all agree on; we’re ready for Drupal 8 to be released! This anticipation is underscored by the record number of contributors to D8 - over 2400. Now it’s time for the Drupal community to rally and finish the job. The Drupal Association wants to help you make that happen. After all, our mission is to unite a gobal open source community to build and promote Drupal.

The Drupal 8 Accelerate Program is a $125,000 fund provided by the Drupal Association (and by extension, all the Association members and Partners who fund our work - so thank you). Grants will be made in two categories: branch maintainer requests and community requests. This two-branch system means that funds can be directed by the people most intimately familiar with the project needs while still allowing for our amazing community to come up with innovative ideas that have a big impact. The Association will also be providing logistical support to the branch maintainers throughout the process.

While the Association is providing the funds and the support, we are not deciding WHAT gets funded. This gets handled by the branch maintainers, keeping the Association on the right side of the “we don’t direct the project” line. The Drupal 8 Accelerate program is a fantastic opportunity for the Association to support and amplify community efforts. All of our favorite work at the Association follows this model - DrupalCon session selection, Community Cultivation Grants, Global Training Days, and DrupalCamp Fiscal Sponsorship to name a few. We’re here to make it easier for you to innovate, and this program is yet another example.

Of course, this is the first time our community has tried anything like this, so we expect that we’ll be learning a lot as we go. As always, we are looking for your feedback and help so that we can improve.

How can you help? Let me count the ways:

  • Help promote the program. Share this blog post on Twitter, Facebook, and other places your Drupal friends hang out online.
  • Apply! Take this program back to your user group, company, or friends and dream big. If you have a great way to help push Drupal 8 to release, we want to hear about it.
  • Help fund the grants. The Association has pledged $125,000 because we think this program is THAT important. But we’re looking for community support to help make this investment. You can become member, a partner, or talk to us about making a contribution directly to the fund.

A huge round of thanks goes to Angie, Jess, Gabor, Cathy, Nate and the other branch maintainers who helped develop and review this program. We’re excited to see what happens next!

Catégories: Elsewhere

Drupal core announcements: Priorities for the upcoming Drupal 8 critical issue sprint (Dec. 10-14 in Ghent, Belgium)

ven, 05/12/2014 - 23:32

It's just a few days now until our Drupal 8 criticals sprint in Ghent! The sprint will be held December 10-14, 2014 and hosted at the Wunderkraut offices.

Upgrade path blockers

Our top priority for the sprint will be to make progress on D8 upgrade path blockers (critical issues with the 'D8 upgrade path' tag) that affect the Entity Field API, Views, and the Configuration System. Here are the specific issues we have targeted:

#2372855: Add content & config entity dependencies to views
#2341357: Allow the entity area to use UUIDs instead of IDs and provide autocompletion

Discuss and plan our approach. (The second issue, #2341357, is a soft blocker that covers part of the scope of the first, #2372855.)
 

[PP-1] Figure out what to do in Views when entity schema changes

Discuss and plan our approach.
 

#1934152: Figure the out if we want global config overrides to stick (settings.php overrides don't work on all pages)

Discuss, make a decision, and move forward.
 

#2278017: [PP-1] When a content entity type providing module is uninstalled, the entities are not fully deleted, leaving broken references
#2338873: [PP-2] Modules providing non-configurable field storage definitions can be uninstalled, leaving orphaned unpurged data

These issues are postponed on #2335879: Change SqlContentEntityStorageSchema::requiresEntityDataMigration() to ask the old storage handler if it has data rather than assuming yes unless NULL storage, but that will hopefully land before the sprint. The first issue (#2278017) is proceeding well and can hopefully be wrapped up in the sprint, and then the second (#2338873) will hopefully be a straightforward application of the same pattern. In addition to these issues, we may also want to create a new issue to add a config validator that does the same validation check during a config deployment.
 

#2183983: Find hidden configuration schema issues
#2387149: Display extenders are not possible to describe with config schema
#2387157: Cloning display into another display also stores options that are not supported by the new display type

Agree on the API needed for the Views child issues. Then, continue to resolve outstanding failures in the main issue. It would be great to either finish these by the end of the sprint or get far enough to know the reason for each remaining failure to have confidence there's no lingering huge problem! (#2387141: Missing field configuration schemas across core tests should be hopefully done before the sprint starts.)
 

#2232477: Fatal when adding new fields with NOT NULL constraints in a base table that contains existing entities

This issue was discussed in Amsterdam, committed, and then reverted. yched has been working on the patch since; we could probably focus on this issue together and discuss the issues with the previous patch to move this forward.
 

Critical issue triage

Another goal of the sprint is to triage critical issues in the core queue to assess their relevance and priority. (You can help by making sure any open critical issues you are following have up-to-date issue summaries.)

Sponsors

Thanks to the Drupal Association and Wunderkraut for sponsoring this event!

More information

If you have any questions about the upcoming sprint, contact xjm.

Catégories: Elsewhere

David Norman: Drupal 8's installer and Xdebug don't mix

ven, 05/12/2014 - 23:20

Anecdotally, Drupal 8 is slower than anything before it - maybe 4x slower. While installing Drupal 8.0.0-beta3 so I could work on upgrading the Masquerade module, I found the installer dreadfully slow. I started a timer when I got to the Batch API-enabled "Install site" page. The installer ran for 10 minutes to get as far as step 32 of 37. Then it errored-out.

An AJAX HTTP error occurred. HTTP Result Code: 200 Debugging information follows. Path: http://localhost/drupal8/core/install.php?langcode=en&profile=standard&i... StatusText: OK ResponseText: ( ! ) Fatal error: Maximum execution time of 30 seconds exceeded in /Users/davidnorman/Sites/drupal8/core/lib/Drupal/Core/Extension/ModuleHandler.php on line 261

I've installed Drupal probably thousands of times and I knew my MacBook Pro Retina, 3rd-generation quad core i7 processor with a SSD wasn't a bottleneck. At the time, I only had one extra PHP extension enabled - Xdebug (see my phpinfo()). It only had a basic configuration. Sometimes I enable things like xdebug.collect_assignments or xdebug.show_local_vars, but even those weren't enabled at the time.

[xdebug] zend_extension="/usr/local/Cellar/php56-xdebug/2.2.6/xdebug.so" xdebug.auto_trace = On

To get Drupal to install, I commented the Xdebug zend_extension at /usr/local/etc/php/5.6/conf.d/ext-xdebug.ini, did a brew install php56-apcu, and restarted my MacBook.

After I swapped Xdebug for APCU, the "Install site" portion of the Drupal 8 installer took only 30 seconds to complete and did not time-out, versus the 10 minutes with ultimate failure while Xdebug was enabled.

At this point, I'm seem to be left to conclude that if I wanted to use Xdebug to debug the installer, that my only option is to increase the default 30 second timeout in my /usr/local/etc/php/5.6/php.ini. Alternatively, if I want to use Xdebug for day-to-day module development, that I'll need to disable Xdebug temporarily to get a local install setup.

Drupal 8 does a lot more stuff to process a page. Core developers have succeeded in moving most of the code to use object oriented methods with namespaces and protected variable spaces, but at the expense of turning a vanilla install into about 76MB. Drupal 7.34 is only 15MB.

To make a point, I inserted a debug_print_backtrace() in EntityAccessControlHandler::access(). This is a basic call in core that would check access on anything that's an entity - users, nodes, etc. After Firefox choked on the resulting output, I attempted to make a snapshot of the page using Evernote to link to in this article. Instead, even Evernote told me that the page was too big to capture.

I guess I don't really have any other point to make. It's not like this article is going to make Drupal 8 faster. I don't have advice for making it lightweight. It's what we have to live with now in the supposed pursuit of progress and modern sophistication. I'm just leaving my breadcrumb for other developers who might find it impossible to even get Drupal 8 installed using an environment that worked for Drupal 7 since I was able to get through the "Install site" part of the Drupal 7.34 installer with Xdebug enabled and with APCU disabled in only 14 seconds.

Post categories Drupal
Catégories: Elsewhere

Mediacurrent: A better Access Denied (403) page with Panels

ven, 05/12/2014 - 22:53

What happens when a user bookmarks an access-protected page? If their session expires before they next visit the bookmark, they'll see an "Access Denied" message with no login form. How confusing for the end user! Let's change that.

Catégories: Elsewhere

Drupal Watchdog: Drupal in Context

ven, 05/12/2014 - 19:57
Column

A funny thing happened in 1991, when the Americans with Disabilities Act started compelling businesses to make their premises more accessible. People discovered that long-handled faucets are easier to turn when your hands are wet; wheelchair ramps enabled parents to bring their strollers inside; and athletes relied on handrails after twisting their ankles during practice. In short, ease of use benefited everybody, not just the targeted population.

It's a lesson the Drupal community has struggled gamely to learn: consider Drupal 7's extensive (and expensive) user-interface revamp. And yet beginners still find Drupal much harder to use than, say, WordPress. Meanwhile, technologists who are weighing Drupal against its competitors reach for the handrail, find it missing, and assume that this lack of “polish” is more than skin deep.

Sometimes, they're right.

'tis a Gift to be Simple

If the history of technology teaches us one thing, it's this: Simplicity wins every time. It beats features, security, and price. Examples abound both within and outside of the world of computers: Packaged goods beat out bulk service even as they partly eliminated customer choice, and Twitter dumbed down blogging to become an essential part of digital life. But fighting against the need for simple, reliable tools is quixotic: It's easier and more fun to create new features than to perfect the ones you have.

Certainly Drupal has long been guilty of this. We've held onto poorly implemented core features, even when their function has diminished and the market has passed them by. The mostly pointless and hard-to-use Actions module is a great example. The disease is evident outside of core, too. Features get more attention than interface bugs in the queues of contributed modules; and five years after its release, the Mac version of Acquia Dev Desktop still can't serve web pages on the standard HTTP port 80, or shut down gracefully when you restart your computer.

Catégories: Elsewhere

Commerce Guys: Drupal Commerce Site Spotlight: Flixbus.de

ven, 05/12/2014 - 19:20

We're always on the lookout for great sites built with Drupal Commerce, our truly flexible software that's changing the face of eCommerce one site at a time.

Traveling this Holiday Season? Well if you're in Germany, you might be taking FlixBus. And if you are, then chances are you just purchased your ticket on their new site hosted on Platform.sh. The site features a robust ticketing engine powered by the flexibility of Drupal Commerce and was built by the talented team at Wunderkraut, a Drupal Commerce Delivery partner that has just recently announced their plans to move all the organizations development to Platform.sh, our Continuous Delivery Cloud built to enable and enhance agile development from day one.

 

To see Drupal Commerce sites we've Spotlighted in previous weeks view Other Spotlight Sites

Catégories: Elsewhere

Creative Juices: I Survived Drupalgeddon: How Hackers Took Over My Site, What I Did About It, And How You Can Stay Safe

ven, 05/12/2014 - 14:32
I Survived Drupalgeddon: How Hackers Took Over My Site, What I Did About It, And How You Can Stay Safe Fri, 12/05/2014 - 08:32 matt
Catégories: Elsewhere

InternetDevels: What’s new in Drupal 8?

ven, 05/12/2014 - 13:45

If you stop, you loose. This rule works always, especially speaking about IT industry. Those, who work with Drupal for a long time, probably remember how hard it was to switch from Drupal 6 to its 7th version. Seems, that it all took place not so long ago, but official release of Drupal 8 took place recently…

Read more
Catégories: Elsewhere

Pronovix: Hosting and playing videos in Drupal: Part 2

ven, 05/12/2014 - 10:02

Part 2 of our series about hosting and playing videos in Drupal explores hosted video solutions in detail, and offers some basic information about using video sharing sites. See part 1 for a short explanation of the most popular Drupal modules for video handling, and an introduction of CDNs and cloud storage services.

Catégories: Elsewhere

Freelock : Drupal Dates off by timezone offset, after upgrading date module

ven, 05/12/2014 - 02:41

Just a quick note of how we resolved an issue related to an upgrade to Date.

We recently updated Date in our core distribution to date-7.x-2.9-beta1 and on one site, we had a number of date fields set up as just "Date". After the update, the display of all of these ended up 7 - 8 hours off -- when you edit the node, it shows up with the correct time, and when you display the node, it's off by 8 hours.

DrupalDrupal PlanetUpdatesDate ModuleTime zone
Catégories: Elsewhere

Blue Drop Awards: Blue Drop Awards 2015: Join Us!

jeu, 04/12/2014 - 23:33

Although the Blue Drop Awards are still a few months away, preparation has already begun. However, this isn’t a one-man show; we need your help. There are many ways to get involved such as volunteering, becoming a sponsor, posting to your social media networks and more.

In case you were not aware, in 2012, a group of volunteers set out to create an annual program that aims to increase the awareness of Drupal and it’s capabilities. Now in it’s fourth year, this community-nominated, publicly-voted event recognizes the contributions of individuals, companies, and projects. The Blue Drop Awards are 100% volunteer-organized so we need your help to highlight and showcase the best Drupal websites/modules out there.

There are lots of ways of getting involved! Currently we're looking for sponsors to help us continue this annual project and volunteers to help us run the project. 

We're looking for kind volunteers, who are interested in helping with verifying nominations, web design, development, running the booth at DrupalCon LA, wrangling other volunteers and sponsors, and more.

Sponsors are the only way for us to make this a sustaining project because it takes significant amounts of time and resources to put this project on every year. Luckily for our fantastic sponsors, there are tons of benefits of becoming a sponsor! For 2015 we have four sponsorship packages to choose from; sign up and we’ll get your brand in front of tens of thousands of people in the Drupal community. This is a great lead generation and branding opportunity for our sponsors.

Regardless of whether you decide to sponsor or volunteer, we can't wait to see all of the great Drupal nominees come February!

A big THANK YOU to our talent in this Drupal video: Doug Vann (DougVann.com), Arnold Leung (Appnovation), Michael Spinosa (Unleashed Technologies), Stephen Weinberg (Commerce Guys), Ben Finklea, Erik Wagner, Brian Solka, Alexander Popov, and Gilbert Sauceda (Volacci).

Tags:  Planet Drupal Drupal blue drop awards
Catégories: Elsewhere

Drupal Association News: Global Training Days 2014 Wrap-up

jeu, 04/12/2014 - 23:01

In our third year supporting the Drupal Global Training Days Initiative, we have seen more training companies, more community leaders, and more individuals participate than ever before. 

Each quarter, communities and training companies host Introduction to Drupal sessions, building better and brighter community members. Global Training Days (GTD) is an opportunity for local training companies and community leaders to build their local community by offering low cost/free Introduction to Drupal training. The Drupal Association lists your training on our site, promotes GTDs and is available to consult on planning and curriculum.   Offering these trainings has anecdotally shown to significantly grow individual participation in communities, build a pool of developers, and raise general awareness for the Drupal project. 

This year 35 countries hosted over 170 low cost or free trainings. This year our Asian-Pacific communities really embraced GTDs! We had 8 Indian companies host trainings in Srinagar, Bangalore, Ghaziabad, Delhi, Mumbai, Kolkata, and Gurgaon -- the most trainings in one individual country. China, South Korea, Pakistan, New Zealand, Australia, and Japan also hosted training sessions, really highlighting our growth and momentum in Asia-Pacific. 

Feeling inspired?  Sign up to host a GTD at your DrupalCamp, meet-up, or your local user group.  Are you new to Drupal, or do you want to participate in an introductory training? Try reaching out to local Drupal training company to host an event.

Make sure you save the following dates to host and participate in Global Training Days in 2015:

  • February 27/28
  • May 22/23
  • August 21/22 
  • November 20/21

For more details on the benefits of why you should participate and spread the word about GTDs, check out our webcast and video.  Let’s grow Drupal and our community one person at a time.

Amazing Drupal learning session #DrupalGTD #Drupal @DrupalMumbai @DrupalAssoc pic.twitter.com/8E2xNYxBgE

— Rachit Gupta (@tweet_rachit) September 6, 2014

Catégories: Elsewhere

Marek Sotak: Making Drupal Commons look like facebook - part 1

jeu, 04/12/2014 - 15:45

Acquia Commons is a Drupal distribution that is for building communities within your organization. I have been able to play around with its competitor JIVE and must admit, it stands quite well next to it.

We were approached by Gary Conroy from Specsavers, who have introduced Commons within their organization and needed to do some additional tweaks to make it a bit similar to Facebook. This will be a series of two blog posts, in first we will show how we have made similar functionality to Facebook Like links and in the second how did we change the status form widget.

Catégories: Elsewhere

Drupal Commerce: How to switch your payment settings based on environment variables using Platform.sh

jeu, 04/12/2014 - 14:00

When working on a Commerce project which uses a payment gateway, you need to always make sure that your Staging and Development environments are properly targeting the sandbox or test mode of your payment gateway, and that your Production site is targeting the live account.

This is actually true for any third-party service integration which provides a sandbox where you can test. The objective is to make sure you never send test data on a live account, no matter the service you're testing on.

For this tutorial, I will focus on payment method settings, but the principle remains the same for any other third-party integration.

I will start from an empty Drupal site hosted on Platform.sh and go through the following steps:

  • Enable and configure Paypal WPS payment method
  • Export its configuration to a settings.local.php file
  • Override its Sandbox configuration on the Staging environment
  • Write custom code to read the configuration from the settings.local.php

As you see, the goal (as always with Drupal) is to read the configuration from your code so that you can easily switch from a sandbox mode to a live mode.

Catégories: Elsewhere

tanay.co.in: Book - D8 Module Porting 101 - Porting Simple FB Connect Module to D8

jeu, 04/12/2014 - 12:43
Probably the first book on Drupal 8. But honestly this is not worthy of being called a book. Just a collection of notes that I took as I ported the simple_fb_connect module to D8. Felt it was too long for a blog post and hence the book below! Read More @ http://www.tanay.co.in/blog/book-d8-module-porting-101-porting-simple-fb-connect-module-d8.html

If you see nothing above probably your browser does not support PDF embed. Try from a desktop with the latest version of Chrome or Firefox.

Catégories: Elsewhere

CMS Quick Start: Publishing Drupal 7 Content to Social Media: Part 2

jeu, 04/12/2014 - 10:02
Today we're going to look at how to push your site content to social media services using contributed Drupal modules. If you want full control over how social media integrates with your site and allow extra features to be used on site, this is the way to go. The major tradeoff comes with increased time for configuration and testing, and possibly troubleshooting if something doesn't work correctly.
 

Let's get started.

read more

Catégories: Elsewhere

Propeople Blog: Prototypes: A Better Approach to Development

jeu, 04/12/2014 - 00:21

Traditional web design has always involved creating flat, two-dimensional designs in wireframes or high-definition design comps. While this process feels natural and intuitive for designers, it presents significant shortcomings when it comes to the increasing demand for modern, responsive websites.

Building a website in Drupal typically follows this process:

  1. create low-definition conceptual designs, wireframes, and sketches

  2. create high-definition design files in Photoshop

  3. configure the site and build out various functionalities

  4. create a base theme and apply it to complete functionalities

 

 

This process, tried-and-true as it may be, leads to a lot of challenges:

Synchronicity of frontend and backend development

Building functionality is tied to internal elements that sometimes are not exposed to UI at all. For example, integrations with external systems or implementing editorial workflows. This sort of work can represent hundreds of hours from a development perspective, but the theming required is marginal. On the other hand, some parts of web design work--like assembling pages with node listings or just the pages themselves--can involve 10 hours of development and 20 hours (or more!) of theming due to custom Javascript and layouts. In this situation it can be challenging for a busy frontend developer to know how to organize his/her time most effectively.

Clients can't test the site until most of the functionality is done

Theming only after a site’s functionality is ready leads to a problematic situation wherein a web design team can't actually show its client polished work until the end of the project. Theoretically, of course, we can show some functionality or provide elaborate descriptions, but the “bells and whistles” still tend to be missing until a project nears completion. This leads to a huge bottleneck effect as both clients and quality analysts turn their attention to testing a new website on multiple devices and platforms. At this stage, most of the bugs reported will be related to responsive behavior or small changes to theming. This can be a nightmare for frontend developers; they receive tons of work all at once, even as the project is about to finish.

Enabling frontend developers

Frontend developers are forced to learn a lot about preprocess functions and how Drupal works. This whittles down the time frontend Drupal developers have to introduce cool new technologies that exist elsewhere in the frontend world. Despite multiple attempts to make Drupal’s HTML output cleaner, Drupal still produces a lot of code that, most of the time, is superfluous. The truth is the frontend world develops at a faster pace than our PHP tools. New Javascript frameworks mature at lightning speed and we are not really all that good at adopting them. What we would really like to see is frontend developers progressing in their field, rather than getting bogged down by more Drupalisms. But how?

Prototypes to the rescue

Lately Propeople has been rewriting the web design process, building prototypes right after designs become available. In fact, the main deliverables of our design work are the prototypes themselves. Technically, the prototypes we build are sets of HTML pages. The idea here is for these prototypes to empower frontend developers to build a site how they see it, instead of how Drupal dictates. Prototypes free up frontend developers to use new technologies and to properly organize code. Another advantage is that prototypes can be built before Drupal functionality is finalized. In other words, clients can start test driving their website early on in the development process and have a clear idea of how the site is going to look and behave. By the time Drupal functionality is ready, all frontend bugs are resolved, specifically the ones related to responsive behavior. There are multiple PHP-based template engines to use, platesphp.com being one. Our developers use assemble.io.

 

Prototype-based theming

Let’s say you’ve got your prototypes just the way you want them. Now Drupal’s backend HTML should be made to match the prototypes as precisely as possible. The bad news: this is not easy as it may sound. The good news: we’ve compiled some best practices to lead the way.

  1. Panels, panels, panels. We use a stack of panels modules. It is pretty simple to build custom layouts out from the prototypes, replacing static blocks with implemented panes.

  2. Custom panes with custom templates. In order to control the HTML of custom panes, we create a template file for each one. This makes it easy to tweak the HTML of a single pane as needed. We even display custom panes in lieu of views panes, executing views under the hood. We skip rendering views in order to keep all the theming for one block in one template.

  3. Display entities as view modes. For most view modes (different kinds of teasers), we use separate custom templates.

Prototypes make building a website much more exciting and improves the web design process for everyone involved. Backend developers can actually watch the site’s theming implemented as they complete functionality. Frontend developers have more freedom and fewer Drupalisms to remember. Best of all, prototypes increase client satisfaction because prototypes allow clients to feel more involved in the implementation of their projects.

 Tags: PropeoplePrototypesDesignService category: TechnologyCheck this option to include this post in Planet Drupal aggregator: planetTopics: Tech & Development
Catégories: Elsewhere

Drupal core announcements: Drupal core updates for December 3, 2014

mer, 03/12/2014 - 23:29
What's new with Drupal 8? Where's Drupal 8 at in terms of release?

Since the last Drupal Core Updates, we fixed 18 critical issues and 12 major issues, and opened 9 criticals and 18 majors. That puts us overall at 110 release-blocking critical issues and 705 major issues.

Part of managing Drupal 8 toward its release is continuously reassessing what must block a release of 8.0.0. (Remember, hundreds of thousands of people will benefit from all the great new functionality in Drupal 8, so we need to be smart about what does or doesn't hold up that release!) The chart below illustrates not only those newly discovered and newly fixed critical issues each week, but also issues that are promoted to critical and demoted from critical based on our latest understanding. For more information on what is (and isn't) release-blocking, see the handbook page on issue priority.

Current focus

The current top priority in Drupal 8 is to resolve issues that block a beta-to-beta upgrade path (critical issues tagged 'D8 upgrade path'). We also need core contributors to continue evaluating issues for the beta phase based on the beta changes policy.

Finally, keep an eye out for critical issues that are blocking other work.

How to get involved

If you're new to contributing to core, check out Core contribution mentoring hours. Twice per week, you can log into IRC and helpful Drupal core mentors will get you set up with answers to any of your questions, plus provide some useful issues to work on.

If you are interested in really digging into a tough problem and helping resolve a stagnating release blocker, or if you are stuck on a critical currently, join the #drupal-contribute IRC channel during weekly critical issue office hours on Fridays at 12:00p PST. See chx's office hours reports for an idea of what we've done so far!

If you'd like to contribute to a particular Drupal 8 initiative or working group, see the regularly scheduled meetings on the Drupal 8 core calendar. Google calendar ID: happypunch.com_eq0e09s0kvcs7v5scdi8f8cm70@group.calendar.google.com

You can also help by sponsoring independent Drupal core development.

Notable Commits

The best of git log --since "1 week ago" --pretty=oneline (70 commits in total):

  • Issue 2359369 by mpdonadio, Berdir, bdurbin: Render cache is not cleared when module is uninstalled - cache invalidation is always hard :)
  • Issue 2377281 by hussainweb, dawehner: Upgrade to Symfony 2.6 stable - getting close to the 2.7 LTS release
  • Issue 2342593 by znerol, grendzy, David_Rothstein: Remove mixed SSL support from core - aligning Drupal with the wider web trends regarding https
  • Issue 2369781 by larowlan: Ensure twig_debug output has needed sanitization - another critical security fix down
  • Issue 2384581 by cilefen, Wim Leers: Security: Update CKEditor library to 4.4.6 - brings some security improvements
  • Issue 2384163 by yched: Entity render cache is needlessly cleared when an Entity*Fom*Display is modified - performance++
  • Issue 2368275 by martin107, dawehner, znerol, Crell, Wim Leers: EntityRouteEnhancer and ContentFormControllerSubscriber implicitly depend on too many services - ensuring our critical execution path is a lean as posisble
  • Issue 2348459 by larowlan, alexarpen: Fields of type 'Text (formatted)' do NOT save values - a critical that was causing data loss when editor module was enabled
  • Issue 2235901 by alexpott, mdrummond, iMiksu, sun, Wim Leers: Remove custom theme settings from *.info.yml - theme system using config objects like everything else
  • Issue 2212335 by jhodgdon: Separate out NodeSearch::execute() into finding vs. processing results
  • Issue 2377397 by Wim Leers, alexpott: Themes should use libraries, not individual stylesheets - moving us towards simplifying ajax page state, and smaller Javascript settings object - and hence increased performance

You can also always check the Change records for Drupal core for the full list of Drupal 8 API changes from Drupal 7.

Drupal 8 Around the Interwebs Drupal 8 in "Real Life" Whew! That's a wrap!

Do you follow Drupal Planet with devotion, or keep a close eye on the Drupal event calendar, or git pull origin 8.0.x every morning without fail before your coffee? We're looking for more contributors to help compile these posts. You could either take a few hours once every six weeks or so to put together a whole post, or help with one section more regularly. Read more about how you can volunteer to help with these posts!

Catégories: Elsewhere

Appnovation Technologies: Uploading videos with Brightcove FTP Batch Provisioning

mer, 03/12/2014 - 23:26

Brightcove is a leading platform for cloud-based online video hosting and publishing.

var switchTo5x = false;stLight.options({"publisher":"dr-75626d0b-d9b4-2fdb-6d29-1a20f61d683"});
Catégories: Elsewhere

Drupal Association News: 2015 Leadership Plan and Budget

mer, 03/12/2014 - 23:12

During the last Drupal Association meeting, the board approved the 2015 Leadership Plan and Budget. We are very pleased to make the related documents available to you in their entirety:

However, these documents can be a lot to parse on their own, so let me provide some context and summary here in this post as well.

In short…

With a full engineering team and a bigger staff overall, 2015 presents more opportunities for the Association to directly impact the community. There are still far more projects and services that we could pursue than we can pursue, so we will use a couple of strategies in our work that will help us find the right approaches quickly and in collaboration with the community. Can we do everything that needs to get done? No. But we can and will do more in 2015.

2015 Imperatives

As mentioned above, there are plenty of things we can be doing in 2015 to serve the community. Because we can’t do them all, we’ve identified three areas that are imperatives - if we succeed in these areas, we’ve set ourselves up to grow and do more for the community in the future. Our three imperatives are:

  • Drupal.org: We spent most of 2014 focused on paying off technical debt, making the site and services more portable while improving performance and stability. In 2015, we plan to make many more visible changes, aligned with the roadmap (https://www.drupal.org/roadmap) that was developed with community input and published last month. Drupal.org is the heart of our community and we have a heavy lift to make it the useful tool it could be and to help the tools on Drupal.org better reflect our comunity processes and values. If we do this well, we will see a more engaged and growing community of developers and contributors.
  • Drupal 8 Release: We know you want Drupal 8 to be released just as much as we do. Additionally, there is a lot of opportunity during a product release that we want to take advantage of with the community. We’ll be looking to capitalize on the release to gain positive attention for the project that will result in more market share for Drupal and a growing developer community.
  • Operationalizing Revenue Programs: We’re still in a situation where most of the revenue we use to fund Drupal.org support and development, Community Cultivation Grants, and our other programs comes from the DrupalCons. Having a single major source of revenue is risky for any organization, but it also means that we are limited in terms of what we can do to improve upon or change DrupalCon formats. We are working on diversifying our revenue streams, with several new products introduced in 2014. In 2015, we need to operationalize and grow these revenue streams.
What does this mean?

That’s the work we want to focus on in 2015, but how will we do it all? The Leadership Plan and Budget lay this out in pretty complex detail, so here is a summary of our thinking and what this all represents:

  • You may recall that our original 2014 budget predicted a $750,000 deficit spend so that we could focus on building out a technical team to support our primary imperative - Drupal.org. As it turns out, we were unable to hire that team as quickly as we had hoped and we also did not utilize as much money for contractors on Drupal.org as anticipated (because it’s tough to manage contractors when you don’t have the staff). The result is that we will have a much smaller deficit in 2014.
  • It also means that we still have a lot of work to do on Drupal.org and 2015 is the year that we will actual feel the financial impact of all those engineering hires. Additionally, we need to invest in our revenue team to build out our funding streams so we can sustain the team long-term.
  • Another investment we need to make is in Drupal 8. Not only do we want to support the release, we want to help ensure that the release happens as quickly as possible. Working with the Drupal 8 branch maintainers we are developing a grants program modeled after the Community Cultivation Grants to help fund Drupal 8 development. As with the CGG program, the program is a true partnership with the community. Our role will be to provide the funds (up to $125,000) and logistical support. The branch maintainers will evaluate the proposals. We’ll have more details ready to be released next week, so stay tuned!
  • Continuing the shift we began in 2014, the Drupal.org investment in 2015 will be over $1 million - on par with the DrupalCons in terms of total expense. The bulk of this expense is in staffing, but we will make some small investments in hardware and services and a larger investment to develop a design system that will complement the user research and content strategy to fuel an iterative redesign.
  • When you put it all together, we are expecting another deficit spend, primarily to address the investments that were delayed in 2014. Though we did not have a third DrupalCon in 2014 and we did not make any new investments in revenue related staff until the fourth quarter of the year, we will still have managed to grow our gross revenue over 2013 by several hundred thousand dollars. This gives us great confidence that we can make up this deficit and support a revenue neutral or positive budget for 2016.
A word on strategy

In 2015 we’re going to tackle everything we took on in 2014 and then some. Defining our imperatives helps us understand what work to focus on, but defining our strategies allows us to understand how we will do our work and ensure that it aligns with our values.

We have two main strategies for 2015: work with and highlight community contribution and treat every project as an opportunity to run a small, fast experiment. Our best work is done in partnership with the community. A great example is testbots. In 2014, the Association took on the upkeep of the primary testbot infrastructure so that community volunteers can focus their time on a new, more modern implementation. In all of our work, we will find the right ways to leverage and celebrate these kinds of partnerships.

We also know that in a community this large and complex, giant, comprehensive projects rarely succeed. No one can anticipate every need or use case, and no individual or small group can engineer the “right” solution for every facet. Our teams will instead break big projects down into small components and test solutions, from new ideas for Cons to new UX components. We’ll implement, gather data, and iterate - repeatedly.

Join us for more conversation

The Association staff and board are very excited about the potential this budget represents for progress in areas that matter most to all of us in the Drupal community. We invite you to join us for a community webcast on 18 December at 8am Pacific (that's 11am Eastern and 4pm in London) to discuss the plan in more detail. We’ll also make a recording available for anyone who can’t join us live.

Join the Webcast

Catégories: Elsewhere

Pages