Feed aggregator

Shomeya: Knowing when to use content types and when to use custom entities

Planet Drupal - Fri, 03/04/2015 - 16:15

Ever catch yourself staring at your editor? Then switching over and staring at the content types overview of your new Drupal site? Then back to the client requirements? And then doing it all over again and again while you face a decision? Drupal content types and fields vs. custom entities. That's the tough decision. The choices you make here will affect almost part of site building to come, but it's so hard to know which to choose.

On one hand, Drupal fields are getting better, faster and more flexible all the time with better integration with contributed modules like views. But at the same time the new entity API with Drupal 7 is more flexible than ever, allowing you to add fields to even your own custom entities. So which route should you go? How can you make a decision like this without second guessing yourself all the time?

Why getting it right is important

While lots of projects can go either way the downsides can make the difference between a successful web project and a maintenance or performance nightmare. Using content types and fields with a complex data model that requires lots of complex queries can hurt performance, but using custom entities when you don't need them can add a maintenance burden when it comes time to upgrade your site or make changes. So how do you make that decision?

Read more
Categories: Elsewhere

Baris Wanschers: Level up please. We’re not pushing boxes.

Planet Drupal - Fri, 03/04/2015 - 12:01

I have been active in the Drupal world since 2006 as a developer and co-own my own Drupal agency since 2011. I love to attend Drupal events. Both Local events (DrupalJam, Splash Awards) and global ones (DrupalCon). I have attended every DrupalCon since Paris 2009 and I like to attend CXO days and other “management oriented events” too. Last year, I co-organized DrupalCon Amsterdam as the lead of the local team and as the social media coordinator for the @DrupalConEur twitter account.

What I noticed in these past years is that we have grown a habit in the Drupal community of downplaying ourselves by describing agencies as shops. And that is a shame, in my opinion.

It might be a language barrier issue that makes shops sound weird. A shop in my native language is a store where you go to buy bread or a new phone. You come in, you pick a product, you pay, and you leave. It does not match with a process in which you work together with a client for months creating a great solution for their needs.

Shops makes us - Drupal agencies - feel cheap. As if we only have out-of-the box solutions that do not need love and care to be shaped into this great fit for the client.

The truth of Google

Just to compare: when I search Google for a ‘Drupal shop’ I even get more results than when I search for a ‘Drupal agency’ or  ‘Drupal company’! Meaning that we’ve truly grown a habit of using Drupal shop in our communication.

I urge you to stop using the term shop. So: let’s level up. And starting today, please use Drupal agency instead.

What do you think? Is it a language barrier? Comments are more than welcome!

Tags:  Drupal Discussion Planet Drupal
Categories: Elsewhere

Elena 'valhalla' Grandi: Leap second on 31 march

Planet Debian - Fri, 03/04/2015 - 11:48
Leap second on 31 march

A couple of days ago this appeared in my system logs

Mar 31 23:59:59 kernel: Clock: inserting leap second 23:59:60 UTC

my first reaction of course was "great! they gave us one second more of sleep! MY PRECIOUSSSS", but then I realized that yes, this year there was supposed to be a leap second, but it should have been in June, not in March.

Other people I know noticed the message, but nobody knew anything else about it, and duckduckgoing didn't find anything, so I'm asking the lazyweb: does anybody know what happened?
Categories: Elsewhere

InternetDevels: Our cool drupallers visited Vinnytsia

Planet Drupal - Fri, 03/04/2015 - 11:30

Hurray, we covered the fifth point on Ukrainian map! Its half-jubilee already and we’re not going to stop. So this time we visited Vinnytsia, and everything went really well — as usually, in fact :)

That Saturday morning was hard for our Drupal tourists: they all had to get up very early to leave the city already at 4 AM! But we’re strong and we did it. In the end it was nothing to regret about, Vinnytsia welcomed us very warmly and eagerly.

Read more
Categories: Elsewhere

KnackForge: Hide "Promoted to front page" and "Sticky at top of lists" options in Drupal

Planet Drupal - Fri, 03/04/2015 - 06:30
This blog describes how to hide "Promoted to front page" and "Sticky at top of lists" options from node editing page in Drupal. When adding or editing a node, you can see "Publishing options" at bottom of the page which contains 'Published', 'Promoted to front page' and 'Sticky at top of lists' checkbox options. The below image shows you the three options:         The "Published" option is used to publish the content. The "Promoted to front page" option is used to display content in the front page. The 'Sticky at top of lists' option is used to keep the content sticked to the top of front page. If you don't need to show "Promoted to front page" and "Sticky at top of lists" options, then you can hide those options easily. You can hide these options by altering the form either using either hook_form_alter() or hook_form_form_id_alter(). <?php /** * Implement hook_form_FORM_ID_alter(). */ function kf_form_article_node_form(&$form, $&form_state) { // hide promoted to front page option if (isset($form['options']['promote'])) { $form['options']['promote']['#access'] = FALSE; } // hide sticky at top of lists option if (isset($form['options']['sticky'])) { $form['options']['sticky']['#access'] = FALSE; } } ?>
Categories: Elsewhere

KnackForge: Cleanup of Drupal modules folders

Planet Drupal - Fri, 03/04/2015 - 06:30

Keeping your drupal modules folder very clear is important part of development. This is the common structure :

  • Contrib - modules from Drupal.org
  • Custom - modules developed for the specific project
  • Features - exported features for Features-driven development

This structure will give better understanding about the modules to other developers and prevent them from hacking the Drupal's contributed modules.

In my case, all the contrib, custom, features were placed in single folder (sites/all/modules/). So the modules folder had nearly hundred modules, its too irritating for any developer. So I planned to move all the modules to their corresponding folders according to the common drupal folder structure. There were many issues after moving all the modules into specific folders.

Drupal's Registry rebuild module gave the opportunity to clear the registry through cli (drush/php) 

  1. Backup your database,
  2. Download and place the registry_rebuild module into your drupal modules folder,
  3. Move all the modules into their corresponding folders,
  4. Run drush rr command to clear all the registry in the database.

After clearing the registry the site is working like a charm, and its a big relief for any developer. 

Categories: Elsewhere

Francois Marier: Using OpenVPN on Android Lollipop

Planet Debian - Fri, 03/04/2015 - 05:45

I use my Linode VPS as a VPN endpoint for my laptop when I'm using untrusted networks and I wanted to do the same on my Android 5 (Lollipop) phone.

It turns out that it's quite easy to do (doesn't require rooting your phone) and that it works very well.

Install OpenVPN

Once you have installed and configured OpenVPN on the server, you need to install the OpenVPN app for Android (available both on F-Droid and Google Play).

From the easy-rsa directory you created while generating the server keys, create a new keypair for your phone:

./build-key nexus6 # "nexus6" as Name, no password

and then copy the following files onto your phone (e.g. via Google Drive):

  • ca.crt
  • nexus6.crt
  • nexus6.key
  • ta.key
Create a new VPN config

If you configured your server as per my instructions, these are the settings you'll need to use on your phone:


  • LZO Compression: YES
  • Type: Certificates
  • CA Certificate: ca.crt
  • Client Certificate: nexus6.crt
  • Client Certificate Key: nexus6.key

Server list:

  • Server address: hafnarfjordur.fmarier.org
  • Port: 1194
  • Protocol: UDP
  • Custom Options: NO


  • Expect TLS server certificate: YES
  • Certificate hostname check: YES
  • Remote certificate subject: server
  • Use TLS Authentication: YES
  • TLS Auth File: ta.key
  • TLS Direction: 1
  • Encryption cipher: AES-256-CBC
  • Packet authentication: SHA384 (not SHA-384)

That's it. Everything else should work with the defaults.

Categories: Elsewhere

Wuinfo: Should We Do Something With Core Field SQL Storage?

Planet Drupal - Fri, 03/04/2015 - 03:15

Drupal field was part of the Drupal core since version 7. The Field extends her ability to build different kinds of systems. Since it is basic units of each entity, it is one of the most important parts of the open source software. But, when it comes to the efficiency of using SQL storage engine, the field can still do better with efficiency. I sincerely believe that we may not afford to ignore it. Let put it under a microscope had a close look at field SQL storage.

Case study:

I had built a patient scheduling system for a couple clinic offices. The project itself is not complicated. I have attached the patient profile picture on this article. We built a patient profile node type on the form. It is not a complicated form, but there are over 40 fields. It is not difficult to set up a nice patient profile node form. I also created appointment node type that connected patient profile and doctor profile with entity reference fields. Using views with exposed filter for the various reports.

It was the project where I find the issue. I am a little bit uncomfortable after I take a close look at the database. Each field has two almost identical tables. I think fields took too much unnecessary database space. I have dumped one of the fields database information to explain my concern.

1) Base table: field_data_field_initial +----------------------+------------------+------+-----+---------+-------+
| Field                | Type             | Null | Key | Default | Extra |
| entity_type          | varchar(128)     | NO   | PRI |         |       |
| bundle               | varchar(128)     | NO   | MUL |         |       |
| deleted              | tinyint(4)       | NO   | PRI | 0       |       |
| entity_id            | int(10) unsigned | NO   | PRI | NULL    |       |
| revision_id          | int(10) unsigned | YES  | MUL | NULL    |       |
| language             | varchar(32)      | NO   | PRI |         |       |
| delta                | int(10) unsigned | NO   | PRI | NULL    |       |
| field_initial_value  | varchar(255)     | YES  |     | NULL    |       |
| field_initial_format | varchar(255)     | YES  | MUL | NULL    |       |

Base table SQL script:

CREATE TABLE `field_data_field_initial` (
`entity_type` varchar(128) NOT NULL DEFAULT '',
`bundle` varchar(128) NOT NULL DEFAULT '',
`deleted` tinyint(4) NOT NULL DEFAULT '0',
`entity_id` int(10) unsigned NOT NULL,
`revision_id` int(10) unsigned DEFAULT NULL,
`language` varchar(32) NOT NULL DEFAULT '',
`delta` int(10) unsigned NOT NULL,
`field_initial_value` varchar(255) DEFAULT NULL,
`field_initial_format` varchar(255) DEFAULT NULL,
PRIMARY KEY (`entity_type`,`entity_id`,`deleted`,`delta`,`language`),
KEY `entity_type` (`entity_type`),
KEY `bundle` (`bundle`),
KEY `deleted` (`deleted`),
KEY `entity_id` (`entity_id`),
KEY `revision_id` (`revision_id`),
KEY `language` (`language`),
KEY `field_initial_format` (`field_initial_format`) 2) Revision table: field_revision_field_initial +----------------------+------------------+------+-----+---------+-------+
| Field                | Type             | Null | Key | Default | Extra |
| entity_type          | varchar(128)     | NO   | PRI |         |       |
| bundle               | varchar(128)     | NO   | MUL |         |       |
| deleted              | tinyint(4)       | NO   | PRI | 0       |       |
| entity_id            | int(10) unsigned | NO   | PRI | NULL    |       |
| revision_id          | int(10) unsigned | NO   | PRI | NULL    |       |
| language             | varchar(32)      | NO   | PRI |         |       |
| delta                | int(10) unsigned | NO   | PRI | NULL    |       |
| field_initial_value  | varchar(255)     | YES  |     | NULL    |       |
| field_initial_format | varchar(255)     | YES  | MUL | NULL    |       |

Revision table SQL script:

CREATE TABLE `field_revision_field_initial` (
  `entity_type` varchar(128) NOT NULL DEFAULT '',
  `bundle` varchar(128) NOT NULL DEFAULT '',
  `deleted` tinyint(4) NOT NULL DEFAULT '0',
  `entity_id` int(10) unsigned NOT NULL,
  `revision_id` int(10) unsigned NOT NULL,
  `language` varchar(32) NOT NULL DEFAULT '',
  `delta` int(10) unsigned NOT NULL,
  `field_initial_value` varchar(255) DEFAULT NULL,
  `field_initial_format` varchar(255) DEFAULT NULL,
  PRIMARY KEY (`entity_type`,`entity_id`,`revision_id`,`deleted`,`delta`,`language`),
  KEY `entity_type` (`entity_type`),
  KEY `bundle` (`bundle`),
  KEY `deleted` (`deleted`),
  KEY `entity_id` (`entity_id`),
  KEY `revision_id` (`revision_id`),
  KEY `language` (`language`),
  KEY `field_initial_format` (`field_initial_format`) Here are my concerns. 1) Normalization.

Here is one of the fields' data record.

| entity_type | bundle | deleted | entity_id | revision_id | language | delta | field_initial_value | field_initial_format |
| node        | patient_profile      |       0 |      1497 |        1497 | und      |     0 | w                   | plain_text        |

We have value "W" in the Initial field. One character took 51 bytes for storage that had not included index yet. It took another 51 byte in the revision table and more for index. In this case here, only less than two percents of space are used for real data the initial 'W', and over 98% of space is for other purposes.

For the sake of space, I think we should not use varchar for entity_type, bundle, language, field_format column. Use small int, tiny int or intÎÎ that will only take one to four bytes. The field is a basic unit of a Drupal website. A medium website can hold millions of fields. Saved one byte is equal to multiple megabytes in precious MySQL database.

2) Too complicated primary key

Each field table has a complicated primary key. Base table use `entity_type`, `entity_id`, `deleted`, `delta`, `language` as primary key. Revision table use `entity_type`, `entity_id`, `revision_id`, `deleted`, `delta`, `language` as primary key. "In InnoDB, having a long PRIMARY KEY wastes a lot of disk space because its value must be stored with every secondary index record."ÎÎÎ. It may be worthy to add an auto increasing int as a primary key.

3) Not needed field column

I found bundle type column is not necessary. We can have the system running well without bundle type column. In my clinic project, I named the node type "patient profile". The machine name patient_profile appears in each field record's bundle type column. As varchar (255), it uses 16 bytes for each table record. Let do a quick calculation. if there are 100, 000 nodes and each node have 40 fields, 100,000 x 40 x 2 x 16 = 122MB are taken for this column. Or at least, we use 2 bytes small int that will take only one-eighth of the spaces.

4) Just use revision table.

Remove one of the field's data tables. It may need a little bit more query power to get field data, but it save time when we insert, update and delete field's data. By doing so, we maintain one less table per field, edit content faster. It helps to bring better editor experience and to save on database storage space.

A contributed module field_sql_leanÎÎ addressed some of the concerns here. It still needs a lot of work on itself and if we want other contributed modules compatible with it. After all, it changed the field table structure.


1: http://dev.mysql.com/doc/refman/5.1/en/integer-types.html
2: http://dev.mysql.com/doc/refman/5.0/en/innodb-tuning.html
3: Field SQL storage lean solution
4: Patient profile form:

Categories: Elsewhere

Rudy Godoy: No SSH for you – how to fix OpenRG routers

Planet Debian - Fri, 03/04/2015 - 00:46

I find interesting when faced a taken-for-granted situation, in particular in the tech world. This time’s history is about an Internet ADSL connection that allows all traffic but SSH. Yes, you read it correctly. It was very bizarre confirming such event was a real-life situation.

I don’t claim to be a networking expert but at least I want to think I’m well educated. After few minutes I’ve focused my efforts on dealing with the ADSL router/modem’s networking configuration. The device is provided by Movistar (formerly Telefonica) and it runs OpenRG. I’ve discovered that other people have experienced the same issue and what Movistar did was basically replacing the device. Of course the problem is gone after that.

So, this post is dedicated to those who don’t give up. Following the steps below will allow SSH outbound traffic for a OpenRG-based device.

OpenRG device specs Software Version: Upgrade Release Date: Oct 7 2014 Diagnostic

When you do the command below, it shows nothing but timeout. Even when you SSH the router it doesn’t establish connection to it.

ssh -vv host.somewhere.com Solution Change router’s SSH service port.

This step will allow you to access the console-based configuration for the router (since I haven’t found any way to do the steps described below from the web management interface).

To do so, go to System > Management > SSH. Update the service port to something else than 22, for instance 2222.

OpenRG SSH service configuration

Connect to the SSH interface

Once you have changed the SSH service port, you can access it from a SSH client.

ssh -p 2222 admin@ admin@'s password: OpenRG>

Once you have the console prompt, issue the following commands to allow SSH outbound traffic coming from the LAN and Wifi networks. After the last command, which saves and updates the device’s configuration, you should be able to do SSH from any computer in your network to the Internet (thanks to tips from inkhorn).

OpenRG> conf set fw/policy/0/chain/fw_br0_in/rule/0/enabled 0 Returned 0 OpenRG> conf set fw/policy/0/chain/fw_br1_in/rule/0/enabled 0 Returned 0 OpenRG> conf reconf 1 Returned 0

Related posts:

  1. Getting Movistar Peru ZTE MF193 work in Debian GNU/Linux How to get Movistar Peru (Internet Móvil) ZTE 3G MF193...
  2. Subversion auth using SSH external key-pair Usually, when using Subversion’s SSH authentication facility, Subversion’s client will...
  3. s3tools – Simple Storage Service for non-Amazon providers Using s3tools to interact with a S3-compatible storage service for...
Categories: Elsewhere

Ben Hutchings: Debian LTS work, March 2015

Planet Debian - Fri, 03/04/2015 - 00:14

This was my fourth month working on Debian LTS. I was assigned 14.5 hours by Freexian's Debian LTS initiative, but I only worked 11.5 as I had a week's holiday and then was ill for part of this week.


My first task was to complete the eglibc update that I began at the end of February. There were a few unexpected failures in the regression test suite, but on inspection these turned out to be quirks of the build environment:

  • A test of the nice(2) function failed because I ran the build itself with nice(1). I should probably use a cgroup to reduce its priority instead; this time I re-ran without using either.
  • Several tests of cancellation failed because they rely on a socket write blocking due to filling up the buffer, while the kernel's minimum socket buffer size has increased such that the write isn't big enough to block. (The host kernel was Linux 3.16 from jessie.) I found and applied a fix for this from the (glibc) upstream repository.

With those changes, the regression test results are the same as for previous package versions. (There is still one 'unexpected' failure, but I didn't investigate because it is not a regression within squeeze.)

I reviewed the backported patches again to check as well as I could that they did not depend on other upstream changes, and they did not seem to. I also received positive feedback from further testing - I can't find the message now, but I think it was that the Univention application test suite passed with the updated eglibc package installed.

With that confirmation and no regressions reported, I uploaded eglibc 2.11.3-4+deb6u5 and issued DLA 165-1.


A large number of vulnerabilities in font file parsing in Freetype were reported by Mateusz Jurczyk. I think these were less critical in squeeze than in wheezy, because while current web browsers use Freetype to render untrusted 'web fonts' we don't support any web browsers in squeeze LTS. But it seemed like they ought to be fixed anyway, and it was not too hard to backport the patches included in the wheezy security update.

Freetype doesn't have a regression test suite and I didn't have samples of the broken fonts, so I came up with some ad hoc tests for regressions. I viewed several of each of the affected font formats with the ftview demo application. I then wrote a script to match up the dependencies of a package (in this case, libfreetype6) with those used by Freexian's customers; the top results were fontconfig, xfonts-utils and imagemagick. So I ran some basic tests against each of the affected formats with each of these (fc-list, mkfontscale, and the simple text label recipe for ImageMagick) and found no regression. Uploaded freetype 2.4.2-2.1+squeeze5 and issued DLA 185-1.

Categories: Elsewhere

Drupal core announcements: D8 Accelerate Performance Sprint at Drupal Developer Days in Montpelier, France

Planet Drupal - Thu, 02/04/2015 - 23:54
Start:  2015-04-13 (All day) - 2015-04-19 (All day) Europe/Paris Sprint Organizers:  Wim Leers


The goal of this sprint is to uncover the "unknown unknowns" blocking Drupal 8 from shipping, performance-wise. The main focus will be on profiling Drupal 8 under a variety of scenarios to determine the next places to start optimizing, then creating issues for these things so that a wider group of folks can work on them.

We're specifically looking for two types of sprinters:

  1. Finders: Those with profiling experience, using tools like XHProf, Blackfire, and flame graphs, who can analyze profiling data to flag problems and come up with recommendations on optimization targets. Your goal is to keep drilling down until we get to the bottom of what's making Drupal 8 slow.
  2. Fixers: Those who can both work on existing known performance issues, as well as take direction from the first group and create/review patches to improve areas of performance. We're especially looking for those with experience with things like the routing system, bootstrapping, container services, route access checking, and asset handling.

The Sprint Planning Doc has everything you need to know, including stuff to do before the sprint and a nice list of all the outstanding critical issues to tackle.

If you're planning to attend (remote attendees welcome!) fill your details in the DevDays Sprint Attendance sheet.

Hope to see you there!

Categories: Elsewhere

Drupal core announcements: Drupal core updates for April 2nd, 2015

Planet Drupal - Thu, 02/04/2015 - 22:15

Welcome to the second quarter of 2015! In the past two weeks, Dries proposed an evolution to Drupal core's structure and decision-making process, the Drupal Community mourned the passing of Aaron Winborn and the Drupal Association announced The Aaron Winborn Award to honor amazing community members in his memory, Addison Berry was elected the 2015 Drupal Association Director At-Large, and lastly, a group to help mentors was formed.

What's new with Drupal 8?

Since the last Drupal Core Update, Drupal 8.0.0-beta9 was released (beta8 was skipped due to installer issues), all known critical issues with the Drupal 8 configuration system were fixed, and the taxonomy term reference field was removed in favor of entity reference fields.

Some other highlights of the month were:

How can I help get Drupal 8 done?

See Help get Drupal 8 released! for updated information on the current state of the release and more information on how you can help.

You can also raise money and/or donate to the Drupal 8 Accelerate grant program to fund Drupal 8 contribution sprints. For more information about how your donations are used, see webchick's detailed analysis.

We're also looking for more contributors to help compile these posts. Contact mparker17 if you'd like to help!

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. If you'd like to volunteer for helping to draft these posts, please follow the steps here!

Categories: Elsewhere

Zlatan Todorić: Programmers life

Planet Debian - Thu, 02/04/2015 - 21:30

Categories: Elsewhere

DrupalCon News: Join the DrupalCon Los Angeles Business Summit

Planet Drupal - Thu, 02/04/2015 - 20:32

The Business Summit is a highly valuable event for business executives in the Drupal space to learn from each other, receive expert advice, and network. It is a one-day event held on Monday at the Los Angeles Convention Center. Along with the Higher-Ed and Community Summits, the Business Summit will meet on Monday, May 11.

Together we will share best practices, tips for staying relevant in a fast moving market, how to collaborate and compete, and tools for generating value for your business. It's also a great way to meet other business leaders and growing organizations.

Categories: Elsewhere

Midwestern Mac, LLC: Drupal on Mothballs - Convert Drupal 6 or 7 sites to static HTML

Planet Drupal - Thu, 02/04/2015 - 17:35

Drupal.org has an excellent resource page to help you create a static archive of a Drupal site. The page references tools and techniques to take your dynamically-generated Drupal site and turn it into a static HTML site with all the right resources so you can put the site on mothballs.

From time to time, one of Midwestern Mac's hosted sites is no longer updated (e.g. LOLSaints.com), or the event for which the site was created has long since passed (e.g. the 2014 DrupalCamp STL site).

Categories: Elsewhere

Paul Tagliamonte: Oatmeal Raisin Cookies

Planet Debian - Thu, 02/04/2015 - 16:54
Oatmeal Raisin Cookies:


  • 3/4 cups soylent
  • 1 ½ cups rolled oats
  • 1/2 cup sugar (white & dark brown)
  • 1/4 cup flour
  • ¾ cup raisins
  • 1/2 tsp baking soda & powder
  • 1/2 tsp salt
  • 1 stick butter (roomtemp - NOT melted. Don’t even try that. Stop. You. I see you.)
  • 1 egg
  • 1 tsp vanilla

Combine butter,…

Categories: Elsewhere

Pronovix: D8upgrade.org a community service that tells you when to upgrade your site to Drupal 8

Planet Drupal - Thu, 02/04/2015 - 14:53

With the imminent release of Drupal 8, a lot of site owners will need to figure out when they should upgrade. This is not an easy question, and there are a ton of variables: the importance of the site, how much you need Drupal 8’s new features, and of course your budget... For most organisations with a limited budget however, the key factor will be how fast the required upgraded contributed modules will become available.

Categories: Elsewhere

Doug Vann: I’m Not going to DrupalCon 2015 in Los Angeles

Planet Drupal - Thu, 02/04/2015 - 14:52
Given the date I’m publishing this, April 2nd, you can rest assured that this is not an April Fools Joke.

I’ve attended 7 North American DrupalCons, and 50 DrupalCamps, a plethora of LinuxFests, etc. But I’m skipping DrupalCon Los Angeles. This year alone I’ve presented at Drupal User groups in Philly and Austin, a 4hr Drupal 8 workshop at SxSw, at NJ camp, MidCamp, and 2 weeks at Temple University. In the next 60 days I have gigs in Philly, DC, and Vegas. There are some other speaking/traveling engagements that I haven’t mentioned.

My point…

I’m worn out!
Between scheduled onsite training gigs, potential training gigs, a family trip, etc, I had to take something out. Oh yah! I’m also in the middle of purchasing my 1st house! So, we have moving to do. There are some DrupalCamps coming up that I know I really want to attend.

And Another Thing…
With so many “regional camps” available now, I get my Drupal Community fix quite nicely at BADCamp, MidCamp, and NYCCamp. 

I can’t do it all! :-( [NOTE: DrupalNorth in Toronto is looking to be AWESOME! I may have to add that to my list!]

What I’ll miss most by missing DrupalCon 2015 in L.A. :

* Hanging out in the exhibit hall and the hallways seeing old friends and making new ones
* The many social events including sponsor parties and group meals
* Getting to meet new people and find out what they do with Drupal and why they came [Might just be my FAV]
* I have been known to catch the occasional session, but I WILL miss seeing the DriesNote LIVE :-(
* And of course… I’ll be glued to my Mac watching the PreNote to see what outrageous hilarity ensues with jam, Robert Douglass, and company!

Dear dear friends... I will miss you all! I'll watch the tweets and pics as I live vicariously through social media! :-)

Drupal Planet

View the discussion thread.

Categories: Elsewhere

Code Karate: Setting and configuring a Local Host on Mac - 1 of 3

Planet Drupal - Thu, 02/04/2015 - 13:13
Episode Number: 200

It’s our 200th episode! For this video, I wanted to take a look at how to set up a local development system and then configure that to build a Drupal 7 site. In this video, I show you how to download MAMP, a local solution stack. For those not familiar with MAMP, MAMP stands for Mac OSX, Apache, MySQL, and Php. This full stack allows you to run a server on your local computer.

Tags: DrupalDrupal 7Drupal PlanetDeploymentServers
Categories: Elsewhere

Michal &#268;iha&#345;: GSoC 2015 applications for phpMyAdmin

Planet Debian - Thu, 02/04/2015 - 06:00

As usual, I look at the application stats for phpMyAdmin just after student application period of Google Summer of Code is over.

First of all we got way more proposals than in last years, but also number of bogus proposals went up (you can see them as ignored in the chart).

Same as in past years, people leave the submission to the last moment, even though we encourage them to submit early so that they can adjust the application based on our feedback. But still we got more than half of the proposals in last three days.

Anyway we're just working on evaluation and will finalize it in upcoming days. Of course you will know the results from Google on April 27th.

PS: You can compare to our 2014, 2013 and 2012 numbers.

Filed under: English phpMyAdmin SUSE | 0 comments | Flattr this!

Categories: Elsewhere


Subscribe to jfhovinne aggregator