Elsewhere

PreviousNext: A quick gotcha with Drupal 8's libraries.info.yml and aggregated JavaScript

Planet Drupal - Wed, 29/06/2016 - 08:17

This one tripped me up on a recent Drupal 8 project.

Easy to miss when you're working in a development oriented environment with things like JavaScript preprocessing turned off.

A JavaScript file was being added just fine with aggregation turned off, but not getting added with it turned on.

 

Categories: Elsewhere

Talha Paracha: GSoC’16 – Pubkey Encrypt – Week 5 Report

Planet Drupal - Wed, 29/06/2016 - 02:00

This week I worked on making the module a bit flexible via integrating pluggable systems into it. This is something we had planned initially while writing the architecture document for the module, but couldn’t pursue it earlier because our focus was on developing a working prototype first. But since that’s done, we’ve reached the perfect time for this development. It should be noted that the pluggable systems are important because Pubkey Encrypt deals with security, and it is essential for the module’s success to be as flexible as possible. In this way, users would be able to configure the behavior of the module as per their organizational security standards and other demands not provided by the out of the box functionality.

Categories: Elsewhere

Reproducible builds folks: First steps towards getting containers working

Planet Debian - Wed, 29/06/2016 - 01:19

Author: ceridwen

The 0.1 alpha release of reprotest has been accepted into Debian unstable and is available for install at packages.debian.org or through apt.

I've been working on redesigning reprotest so that it runs commands through autopkgtest's adt_testbed interface. For the most part, I needed to replace explicit calls to Python standard library functions for copying files and directories with calls to adt_testbed.Testbed.command() with copyup and copydown, and to use Testbed.execute() and Testbed.check_exec() to run commands instead of subprocess.

To test reprotest on the actual containers requires having containers constructed for this purpose. autopkgtest has a test that builds a minimal chroot. I considered doing something like this approach or using BusyBox. However, I have a Python script that mocks a build process, which requires having Python available in the container, and while I looked into busybox-python and MicroPython to keep the footprint small, I decided that for now this would take too much work and decided to go straight to the autopkgtest recommendations for building containers, mk-sbuild and vmdebootstrap. (I also ended up discovering a bug in debootstrap.) This means that to get the tests run requires some manual setup at the moment. In the long run, I'd like to improve that, but it's not an immediate priority. While working on adding tests for the other containers supported by autopkgtest, I also converted to py.test so that I could use fixtures and parametrization to run the Cartesian product of each variation with each container.

With tests written, I started trying to verify that my new code worked. One problem I encountered while trying to debug was that I wasn't getting full error output. In VirtSubproc.check_exec(), execute_timeout() acts something like a Popen() call:

(status, out, err) = execute_timeout(None, timeout, real_argv, stdout=stdout, stderr=subprocess.PIPE) if status: bomb("%s%s failed (exit status %d)" % ((downp and "(down) " or ""), argv, status)) if err: bomb("%s unexpectedly produced stderr output `%s'" % (argv, err))

The problem with this is that if the call returns a non-zero exit code, which is typical for program failures, stderr doesn't get included in the error message.

I changed the first if-block to:

if status: bomb("%s%s failed (exit status %d)\n%s" % ((downp and "(down) " or ""), argv, status, err))

Another example is that autopkgtest calls schroot with the --quiet flag, which in one case was making schroot fail without any output due to a misconfiguration. I'm still trying to find and eliminate more places where errors are silenced.

autopkgtest was designed to be installed with Debian's packaging system, which handles arbitrary files and directory layouts. Unfortunately, setuptools is completely different in a way that doesn't work well with autopkgtest's design. (I'm sure this is partly because setuptools has to support all the different major OSes that run Python, including Windows.) As I discussed last week, autopkgtest has Python scripts in virt/ that are executed by subprocess calls in adt_testbed. Because these scripts import files from lib/, there needs to be an __init__.py in virt/ to make it into a package and a sys.path hack in each script to allow it to find modules in lib/. Unfortunately, setuptools will not install this structure. First, setuptools will not install any file without a .py extension into a package. Theoretically, this is fixable, the files in virt/ are Python scripts so I could rename them. (Theoretically, there's supposed to be some workaround involving MANIFEST.in or package_data in setup.py, but I have yet to find any documentation or explanation giving a method for installing non-Python files inside a Python package.) Second, however, setuptools does not preserve the executable bit when installing package files. The obvious workaround, changing the subprocess calls so that they invoke python virt/foo.py rather than virt/foo.py requires changing all the internal calls in the autopkgtest code, which I'm loathe to do for fear of breaking it. (It's not clear to me I can easily find all of the calls, for starters.)

There are about three solutions to this I see at the moment, all of them difficult. The first involves using either the scripts keyword or console_scripts entry point in setup.py, as explained here. The scripts keyword is supposed to preserve the executable bit according to this StackExchange question, but I haven't verified this myself, and like everything to do with setuptools I don't trust anything anyone says about it without testing it myself. It also has the disadvantage of dumping them all into the common scripts directory. Using console_scripts involves rewriting all of them to have an executable function I can refer to in setup.py. I worry that this would be both fragile and break existing expectations in the rest of the autopkgtest code, but it might be the best solution. The third solution involves refactoring of all the autopkgtest code to import the code in the scripts rather than running it through subprocess calls. I'm reluctant to do this because I think it's almost certain to break things that will require significant work to fix.

Getting setuptools to install the autopkgtest code correctly is one blocker for the next release. Another is that autopkgtest's handling of errors during the build process involves closing the adt_testbed.Testbed so it won't take further commands. Unfortunately, this handling runs before any cleanup code I write to run outside it, which means that at the moment errors during the build will result in things like disorderfs being left mounted.

The last release blocker is that adt_testbed doesn't have any way to set a working directory when running commands. For instance, the virt/schroot script always calls schroot with --directory=/. I thought about trying to use absolute paths, but decided this was unintuitive and impractical. For the user, this would mean that instead of running something simple like make in the correct directory, they would have to run make --file=/absolute/path/to/Makefile or something similar, making all paths absolute. I worry that some build scripts wouldn't handle this correctly, either: for instance, running python setup.py from a different directory can have different effects because Python's path is initialized to contain the current directory. Changing this is going to require going deeper into the autopkgtest code than I'd hoped.

I intend to try to resolve these three issues over the next week and then prepare the next release, though how much progress I make depends on how thorny they turn out to be.

Categories: Elsewhere

Jose M. Calhariz: at daemon 3.1.20, with 3 fixes

Planet Debian - Tue, 28/06/2016 - 23:14

From the Debian BUG system I incorporated 3 fixes. One of them is experimental. It fixes a broken code but may have side effects. Please test it.

  • New release 3.1.20:
* Add option b to getopt, (Closes: #812972). * Comment a possible broken code, (Closes: #818508). * Add a fflush to catch more errors during writes, (Closes: #801186).

You may download from here at_3.1.20.orig.tar.gz.

Categories: Elsewhere

Mediacurrent: 4 Benefits of Decoupled Architecture for Enterprise Digital Marketers

Planet Drupal - Tue, 28/06/2016 - 21:59

Since the web was born, information technology (IT) professionals have been working to make sure their organizations had a presence online. In the past few years, we have seen a shift in those digital dollars - right onto the Marketing Department’s doorstep. This signals a larger pivot in thinking. Your website is no longer a stagnant or a “nice to have” piece of technology, but a dynamic, evolving hub for your company’s marketing, branding and lead generation efforts.

Categories: Elsewhere

Paul Wise: DebCamp16 day 5

Planet Debian - Tue, 28/06/2016 - 21:14

Beat head against shiny cats (no animals were harmed). Discuss the spice of sillyness. Forward a wiki bounce to the person. Mention my gobby git mail cron job. Start adopting the adequate package. Discuss cats vs licensecheck with Jonas. Usual spam reporting. Review wiki RecentChanges. Whitelisted one user in the wiki anti-spam system. Finding myself longing for a web technology. Shudder and look at the twinklies.

Categories: Elsewhere

Tyler Frankenstein: DrupalCamp Michigan 2016 Last Call for Sessions

Planet Drupal - Tue, 28/06/2016 - 18:45

Hello Michigan Drupal folks and beyond,

The final call for sessions for this year's DrupalCamp Michigan will be July 5th. Please submit your session proposals before that time:

http://2016camp.michigandrupal.com/sessions

In the mean time take a look at some of the great sessions proposed by the community:

http://2016camp.michigandrupal.com/sessions/proposed

Categories: Elsewhere

Cheeky Monkey Media: Drupal and Masonry, without the tears of Frustration

Planet Drupal - Tue, 28/06/2016 - 17:16
Drupal and Masonry, without the tears of Frustration micah Tue, 06/28/2016 - 15:16

I recently had to create a new layout that mimicked the Pinterest layout. Masonry to the rescue! (sorta...) With Drupal already crapping out the content via views, we could just use the Masonry views plugin right? Sorta. Well, it worked. ... sorta. There were problems, and I don’t like problems, only solutions.

I like a very NON-hacky way of doing things. Masonry views worked for the desktop screen size but failed miserably for anything smaller. We were working with a responsive design, so it was unacceptable. There was simply just no amount of tweaking the options and CSS that it came with, that I was happy with. I’m also not a fan of CMS plugins controlling layout. There tend to be crappy implementations and far less control. I don’t speak for everything, of course, just my experience.

I wanted to control.. as much as I could. So I abandoned the views plugin, and just decided to use the raw jQuery plugin, and use my own CSS.

This assumes ya know how to use requireJS and jQuery plugins.

Categories: Elsewhere

Janez Urevc: We loved Drupal Developer Days!

Planet Drupal - Tue, 28/06/2016 - 16:27
We loved Drupal Developer Days! slashrsm Tue, 28.06.2016 - 16:27

Last week part of the MD Systems team attended Drupal Developer Days in Milan.

Italian style dinner at Navigli in Milano. #drupaldevdays pic.twitter.com/CQOpIpmSGg

— Dragan Eror (@draganeror) June 23, 2016

I'd like to invite you to check our blog post to see how we liked it.

Categories: Elsewhere

Cryptic.Zone: Extending Drupal's Node.js Integration

Planet Drupal - Tue, 28/06/2016 - 16:24

The Node.js integration Drupal module offers an API that allows developers to add real-time push notification functionality to their modules. Real-time communication could enable features like chat, pop-up notifications, or real-time content update. Chatroom is a great example of how a module can leverage Node.js. 

Categories: Elsewhere

Amazee Labs: Impressions from Drupal Developer Days in Milano

Planet Drupal - Tue, 28/06/2016 - 14:37
Impressions from Drupal Developer Days in Milano

Last week, Sebastian and I attended Drupal Developer Days in Milan. An international group of 400 people gathered for a full-week conference in Italy to work and talk about Drupal 8.

Josef Dabernig Tue, 06/28/2016 - 14:37

The local team put up an outstanding conference, featuring a complete program with a week of sprints, high-quality talks and a lot more to like.

Sprinters

We could only attend from Thursday to Sunday, but the event already started Tuesday with 100 sprinters working on initiatives to move Drupal 8 and its contributed modules forward.

A look at the sprint planning sheet highlights the variety of topics that different sprinters have been working on.

The UX sprint was probably the biggest one with Gábor Hojtsy, Peter Droogmans (attiks) and Bojhan attending. I was especially excited to see ifrik and Rachel Lawson (rachel_norfolk) work on improving the organization of the Drupal admin UI. See their plan issue “Restructure the Admin interface” for further details on that.

A lot has been improved related to the UX process of Drupal. You can find a good read here, follow the DrupalUX twitter account and get more info on the initiative page.  

The multilingual initiative has been sprinting as well. Check out the great #d8mi initiative page to find out more. Gábor Hojtsi even presented his experiences with the initiative at the WordCamp Europe in Vienna, the same weekend.

Related to the media initiative, Christian Fritsch from the Thunder core team has been sprinting together with people like Janez Urevc. Check out the initiative page or follow via twitter for more info.

The Search API sprints were packed again. Thomas Seidl, Markus Kalkbrenner, Joris Vercammen, Mattias Michaux and Christian Spitzlay amongst others have been working on issues for Search API, Facets, Search API Solr and Search API Solr Multilingual.

A lot more had been sprinted on during the week, almost impossible to give a precise overview. Some examples are Drupal Commerce 2 with Bojan Živanović, GraphQL with Sebastian Siemssen, Paragraphs with Miro Dietiker. As part of the #d8rules initiative, yanniboi and various others helped out with issues and we will announce our next initiative meeting soon via the #d8rules twitter account.

Sprints are really the key element that allow for collaboration between so many great minds. Its great to see more and more camps taking in sprints as part of their program and having Drupal Developer days as the leading format in that area.

Keynotes

There was a great variety in keynote topics. We built it, now what good is it? by Jeffrey A. McGuire, Evangelist at Acquia gave a deep dive into the new features of Drupal 8 and what they mean to our customers. Making a Drupal shaped dent in the universe by Bojan Živanović, Development Lead at Commerce Guys is a talk to show how cross-community has developed over the recent years. With Drupal getting off the island, Commerce 2 for example is taking a very forward-thinking approach by developing features not as Drupal modules but small, interoperable PHP libraries first.

On Friday, Data Triangulation: Moving beyond Qual and Quant by Razan Sadeq, User Researcher at Spotify brought in the perspective of an expert working for a big product. Razan was able to show by real world examples from her work at Spotify how UX can be driven by data successfully.

Following up, there was Transforming the experience: pixel by pixel by Alessia Rullo, Software solutions user experience lead at Hewlett Packard. In her keynote, Alessia talks about aesthetic considerations with regards to web design and UX.

Saturday’s keynote was Automating Access to Development by Jessica Rose, Developer Relations at DreamFactory Software. Jessica brought together a variety of interesting topics such as diversity and automation.

Sessions

Check out the program to find a list of outstanding sessions being presented during the “talk days” of the conference from Thursday to Saturday.

Sebastian’s talk Decoupling Drupal with GraphQL & Relay was packed as usual and gave a great opportunity to share the details about how we build a decoupled architecture based on GraphQL and Relay that talks to Drupal as a datasource. The slides are up already.

I was excited to be able to talk about our experience at Amazee of using Scrum for project management. SOS - We need a Scrum process! Going from specification to collaboration is a walk through of how we managed the whole process of introducing the process and was a great opportunity to share hands-on experience of the learnings we had so far. You can find the slides here.

Are Geeks from Mars and Geekettes from Venus? - I was glad to be invited for a panel discussion on gender & diversity in tech led by Alessandra Petromilli. Together with Razan Sadeq, Kristof Van Tomme, Alessia Rullo and Jessica Rose we had inspiring discussions around the topic.
 

Conference

Besides the great experience of  sprinting & watching sessions, conferences are mainly about connecting with others from the community. The Drupal Dev Days team has made great effort to make sure all the required facilities to make this happen were provided. I’d like to especially highlight the quality of food. Good catering with healthy options makes sure that attendees don’t dehydrate and get the vitamins required to stay energetic over days and avoid the Drupal Flu.

The social program featured a Night at the museum @ Leonardo3, Galleria Vittorio Emanuele II with inspiring looks at all the impressive work that Leonardo Da Vinci did. Also many thanks to the Italian community for inviting everyone on Thursday evening for the official social event at a great bar in Milano!

I was really excited to see #TourDeDrupal bringing together a motivated group of 8 cyclers. We rode over 50km along the Martesana canal and back into the city. On Sunday, Riccardo Bessone and I had the pleasure of cycling along Lago de Como and experiencing true retro cycling up to Madonna del Ghisallo.

Volunteers & Sponsors

It was especially great to see this size of event to be realized in Italy. In 2011 I had first met Claudio Beatrice (omissis) at DrupalCamp in Brixen/Bressanone with less than 50 attendees. The Italian community has organized a couple of camps over the last years and now, with Drupal Dev Days, they could really show that an international camp with 400 people can happen really well in Italy.

A successful Drupal event wouldn’t be possible without a lot of effort being put into the event. Having organized a DrupalCamp myself, I know how much of your free time you need to sacrifice to make it happen. A big thank you to Claudio (omissis), Marco (mavimo), Riccardo (bessone).

Here’s the full list of volunteers: Alessandra Petromilli, Alessandro Sibona, Andrea Pescetti, Antje Lorch, Chandeep Khosa, Chiara Carminati, Claudio Beatrice, Edouard Cunibil, Fabiano Sant'ana, Guillaume Bec, Julien Dubois, Kester Edmonds, Luca Lusso, Marcello Testi, Marco Moscaritolo, Paolo Libanore, Pierluigi Marciano, Riccardo Bessone, Simone Lombardi, Tamer Zoubi, Yan Loetzer, Yi Yuan, Zsófi Major.

Also many thanks to all the sponsors.

Upcoming events

Which events are coming up after dev days? Here’s my short list:

Where are the next Drupal Dev Days going to be? Get in touch via the twitter account, they'll soon announce how new locations can sign up for the next year.

If you are interested in organizing a similar event, you might also be interested in checking the following presentation: Drupal Camp Organization: The Good Parts by Zsófi Major. Her slides are up already.

Thanks again to all the volunteers of Drupal Dev Days Milan. Amazee Labs was glad to be a sprint sponsor. More pictures can be found on our flickr album. See you again soon!

Categories: Elsewhere

Miloš Bovan: Midterm evaluation of GSoC Mailhandler project

Planet Drupal - Tue, 28/06/2016 - 09:58
Midterm evaluation of GSoC Mailhandler project

As usual, Tuesday is the day to update you on the progress of Google Summer of Code 2016 project - Mailhandler.

Last week both mentors and students had to fill Google Summer of Code midterm evaluation. The evaluation happened after 5 weeks of work and consisted of questions about the chosen organization, program, mentors (for students) and students (for mentors).

I am happy to announce that I have passed the midterm evaluation. Yay! I would like to give thanks to my mentors Primož and Miro. They were supporting me with reviews, ideas and suggestions in the past weeks. I hope we will continue the great cooperation in the second phase of the project as well. Here is the review I received from my mentors:

Miloš is very diligent and capable of self organising. There were no instances where we needed to remind him of his obligations or upcoming milestones. This goes equally for the technical as for the non-technical side of the project. He is always prepared to investigate the subject very carefully and find the best solutions to his knowledge. As a result his code never feels sloppy or produced just for the sake to make progress. He genuinely cares about the project. Being very goal oriented he sometimes neglects the discussion part slightly. This could be improved by requesting more feedback before jumping to implementation.

This week, GSoC students will continue the coding until the final evaluation which is scheduled for the second part of August 2016.

Back to the project updates. The last meeting with my mentors was very productive. We were talking about the weekly goal and had the broader discussion about the second phase of the project.

More specifically, we discussed the possibility to introduce the user context as a core feature of Inmail. I was writing about Inmail’s concept of plugins (analyzers, deliverers, handlers). Each analyzer has an option to analyze the mail message that is being processed and update the properties of a shared result object. This would allow collaboration between Inmail analyzers. To discuss different approaches, I created an issue on this topic. For now, the properties are updated on MailhandlerAnalyzerResult object.

Based on the discussion with mentors, we decided to split huge MailhandlerAnalyzer into several smaller analyzers. A pull request with the implementation can be followed on Github. The following analyzers were created (sorted by defaults execution order):

  • PGP (Pretty Good Privacy) analyzer analyzes the PGP-signed email messages, verifies the signature, parses the mail body and sets the sender. Although there is specific BodyAnalyzer, for signed messages we have to parse the mail body to extract the signed text and PGP signature.

  • Entity type analyzer - we have a concept of detecting an entity type and bundle information for the mail subject. For now, we only support: [node][{node_type}]. Later on, we will extend it to support comments entities too. The purpose of this analyzer is to recognize [{entity_type}][{bundle}] pattern, extracts the metadata information, do the validation and update the subject - without metadata.

  • Sender analyzer uses a well-known feature of Mailhandler for Drupal 7. It extracts the mail address from From mail header field and finds the corresponding user. It is worth to mention that user is only set in case the user context is not already populated (by some other analyzer). This prevents us from changing the user context when it is set by PGPAnalyzer, for instance. Also, since this method is not entirely safe - From mail address can be faked by a malicious user, this analyzer is disabled by default.

  • Footer analyzer detects the mail footer/signature in a mail body and updates footer and body properties. Two most used footer separators are supported. This analyzer was described in the previous blog post.

  • Body analyzer works with the actual mail body. It has pretty limited functionality. It removes the white spaces before and after the body string using PHP’s standard method trim(). Also, in case processed body is not received as HTML, it replaces new lines \r\n with <br /> HTML tag. As the analyzer was implemented as a plugin, it can be easily extended.

MailhandlerNode is becoming much “cleaner”. Our algorithm has 3 steps:

  1. Get MailhandlerAnalyzerResult which contains the result of all Mailhandler analyzers

  2. Authenticate and authorize a user

  3. Create a node.

The original complexity from one analyzer is now shared between 5 independent Inmail analyzers. This architectural simplification was made thanks to the great Drupal 8 plugin API. If you are more interested in exploring this topic, Drupalize.me published a great article about Drupal 8 plugin system.

Next week, I am going to work on extending the test coverage for the module. The plan is to create one kernel test per each created analyzer. The existing MailhandlerNodeTest will serve as a general test of all Mailhandler analyzers and MailhandlerNode handler. Also, I will provide additional test coverage of the Mailhandler’s user interface.

 

Milos Tue, 06/28/2016 - 09:58 Tags Open source Drupal Google Summer of Code Drupal Planet Add new comment
Categories: Elsewhere

John Goerzen: A great day for a flight with the boys

Planet Debian - Tue, 28/06/2016 - 05:57

I tend to save up my vacation time to use in summer for family activities, and today was one of those days.

Yesterday, Jacob and Oliver enjoyed planning what they were going to do with me. They ruled out all sorts of things nearby, but they decided they would like to fly to Ponca City, explore the oil museum there, then eat at Enrique’s before flying home.

Of course, it is not particularly hard to convince me to fly somewhere. So off we went today for some great father-son time.

The weather on the way was just gorgeous. We cruised along at about a mile above ground, which gave us pleasantly cool air through the vents and a smooth ride. Out in the distance, a few clouds were trying to form.

Whether I’m flying or driving, a pilot is always happy to pass a small airport. Here was the Winfield, KS airport (KWLD):

This is a beautiful time of year in Kansas. The freshly-cut wheat fields are still a vibrant yellow. Other crops make a bright green, and colors just pop from the sky. A camera can’t do it justice.

They enjoyed the museum, and then Oliver wanted to find something else to do before we returned to the airport for dinner. A little exploring yielded the beautiful and shady Garfield Park, complete with numerous old stone bridges.

Of course, the hit of any visit to Enrique’s is their “ice cream tacos” (sopapillas with ice cream). Here is Oliver polishing off his.

They had both requested sightseeing from the sky on our way back, but both fell asleep so we opted to pass on that this time. Oliver slept through the landing, and I had to wake him up when it was time to go. I always take it as a compliment when a 6-year-old sleeps through a landing!

Most small airports have a bowl of candy setting out somewhere. Jacob and Oliver have become adept at finding them, and I will usually let them “talk me into” a piece of candy at one of them. Today, after we got back, they were intent at exploring the small gift shop back home, and each bought a little toy helicopter for $1.25. They may have been too tired to enjoy it though.

They’ve been in bed for awhile now, and I’m still smiling about the day. Time goes fast when you’re having fun, and all three of us were. It is fun to see them inheriting my sense of excitement at adventure, and enjoying the world around them as they go.

The lady at the museum asked how we had heard about them, and noticed I drove up in an airport car (most small airports have an old car you can borrow for a couple hours for free if you’re a pilot). I told the story briefly, and she said, “So you flew out to this small town just to spend some time here?” “Yep.” “Wow, that’s really neat. I don’t think we’ve ever had a visitor like you before.” Then she turned to the boys and said, “You boys are some of the luckiest kids in the world.”

And I can’t help but feel like the luckiest dad in the world.

Categories: Elsewhere

DrupalCon News: Expanding Drupal's Horizons

Planet Drupal - Tue, 28/06/2016 - 00:43

We already know that Drupal is more than just PHP. Now that the community has embraced the "proudly found elsewhere" mantra with the adoption of software projects outside the Drupal ecosystem, we're looking even further beyond. We want to hear about all the interesting ideas and projects you've been working on at the fringes of Drupal. We're not only interested in technical solutions, but also thoughts around what we can learn as a community from all the other people out there building things on the Internet.

Categories: Elsewhere

Jonathan McDowell: Hire me!

Planet Debian - Tue, 28/06/2016 - 00:21

It’s rare to be in a position to be able to publicly announce you’re looking for a new job, but as the opportunity is currently available to me I feel I should take advantage of it. That’s especially true given the fact I’ll be at DebConf 16 next week and hope to be able to talk to various people who might be hiring (and will, of course, be attending the job fair).

I’m coming to the end of my Masters in Legal Science and although it’s been fascinating I’ve made the decision that I want to return to the world of tech. I like building things too much it seems. There are various people I’ve already reached out to, and more that are on my list to contact, but I figure making it more widely known that I’m in the market can’t hurt with finding the right fit.

  • Availability: August 2016 onwards. I can wait for the right opportunity, but I’ve got a dissertation to write up so can’t start any sooner.
  • Location: Preferably Belfast, Northern Ireland. I know that’s a tricky one, but I’ve done my share of moving around for the moment (note I’ve no problem with having to do travel as part of my job). While I prefer an office environment I’m perfectly able to work from home, as long as it’s as part of a team that is tooled up for disperse workers - in my experience being the only remote person rarely works well. There’s a chance I could be persuaded to move to Dublin for the right role.
  • Type of role: I sit somewhere on the software developer/technical lead/architect spectrum. I expect to get my hands dirty (it’s the only way to learn a system properly), but equally if I’m not able to be involved in making high level technical decisions then I’ll find myself frustrated.
  • Technology preferences: Flexible. My background is backend systems programming (primarily C in the storage and networking spaces), but like most developers these days I’ve had exposure to a bunch of different things and enjoy the opportunity to learn new things.

I’m on LinkedIn and OpenHUB, which should give a bit more info on my previous experience and skill set. I know I’m light on details here, so feel free to email me to talk about what I might be able to specifically bring to your organisation.

Categories: Elsewhere

Attiks: Dream Fields for Drupal 8 - part 2

Planet Drupal - Mon, 27/06/2016 - 23:36

Follow up post, to catch up read the first post

This time I went to Drupal Dev Days in Milan to work some more on the new Field UI proposal. @Bojhan a UX specialist suggested to use images/tiles to make it easier to use, he started working on designing some images, while I adapted the code.

By Peter Droogmans

Categories: Elsewhere

myDropWizard.com: Drupal 6 Is Dead. Long Live Drupal 6!

Planet Drupal - Mon, 27/06/2016 - 23:08

Is Drupal 6 Finally Dead Yet?

The Drupal Community is doing all that we can to move beyond Drupal 6.

We're working hard. We're improving Drupal 8. We're keeping Drupal 7 secure.

You may have heard about the DRUPAL 6 FUNERAL at DrupalCon New Orleans. It's true! There certainly was a fun funeral for Drupal 6 - we even put together a montage of some of the highlights. Of course, we at myDropWizard joked that perhaps we should have dressed as "the ghost of Drupal 6".

Video of Drupal 6 Funeral

The thing is, there are still thousands of websites that are working just fine under Drupal 6. So, while we had a great time at the "funeral", and this milestone will no doubt help move things along faster, we are not dropping Drupal 6 support at myDropWizard any time soon!

If you are able to move to Drupal 8 already, that's great! We love Drupal 8, and we look forward to supporting you in the future. If you are almost done with a Drupal 7 migration, that's fantastic! When Drupal 7 itself is retired, we'll be supporting Drupal 7 into the future as well.

"It's not any easier losing your 6th after losing your first 5."

Dries Buytaert

For the rest of us - the thousands of Drupal 6 installations - that are just not quite yet ready for a jump to Drupal 8, rest assured, we have your back with long-term support.

Categories: Elsewhere

Paul Wise: DebCamp16 day 4

Planet Debian - Mon, 27/06/2016 - 22:25

Usual spam reporting. Review wiki RecentChanges. Rain glorious rain! Err... Update a couple of links on the debtags team page. Report Debian bug #828718 against tracker.debian.org. Update links to debtags on DDPO and the old PTS. Report minor Debian bug #828722 against debtags.debian.org. Update the debtags for check-all-the-things. More code and check fixes for check-all-the-things. Gravitate towards the fireplace and beat face against annoying access point, learn of wpa_cli blacklist & wpa_cli bssid from owner of devilish laptop. Ask stakeholders for feedback/commits before the impending release of check-all-the-things to Debian unstable. Meet developers of the One^WGNU Ring, discuss C++ library foo. Contribute some links to an open hardware thread. Point out the location of the Debian QA SVN repository. Clear skies at night, twinkling delight.

Categories: Elsewhere

Scarlett Clark: Debian: Reproducible builds update

Planet Debian - Mon, 27/06/2016 - 19:58

A quick update to note that I did complete extra-cmake-modules and was given the green light to push upstream and in Debian and will do so asap.
Due to circumstances out of my control, I am moving a few states over and will have to continue my efforts when I arrive at
my new place of residence in a few days. Thanks
for understanding.

Scarlett

Categories: Elsewhere

Chapter Three: Paragraphs vs. ECK for Drupal 8

Planet Drupal - Mon, 27/06/2016 - 19:53

Paragraphs has become a popular site building tool for Drupal. In the feedback to our recent blog post, some asked why the Chapter Three team has not fully embraced the module. Most of our Drupal 8 sites use Entity Construction Kit with Inline Entity Form (ECK/IEF) to achieve what others do with Paragraphs.

Categories: Elsewhere

Pages

Subscribe to jfhovinne aggregator - Elsewhere