Dries Buytaert: Visiting China and Japan

Planet Drupal - Wed, 03/09/2014 - 19:55
Topic: Drupal

After spending the summer in Boston, I'm ready to fly across the world ... literally, as I'm leaving on a two week trip to China and Japan later this week. I'm very excited about it as I've never had the opportunity to see either of these countries.

I will arrive in Beijing on Saturday, September 6th, for the Young Global Leaders Annual Summit. A private path from where I'll be staying, Commune by the Great Wall, leads to a non-restored section of the epic Great Wall of China. Exploring this truly untouched piece of Chinese history still in its original landscape should be a special experience! Stay tuned for photos.

Following my time in Beijing, I'll transfer to Tianjin to attend Summer Davos. In addition to that, we're organizing a meetup with the local Drupal community - https://groups.drupal.org/node/434658. If you are in the area on September 10th, please stop by for a drink. I'd love to meet you and learn about the State of Drupal in China.

I'll end my two week trip in Tokyo, Japan. My time will be split between meeting the local Drupal community - https://groups.drupal.org/node/440198, understanding the adoption rate of Drupal in the Japanese market, and attending private meetings with digital agencies, Acquia partners and others to learn about the state of the web and digital in Japan.

Xièxiè and dōmo arigatō to those that have helped plan these events and gather the Drupal community for some fun evenings!

If you aren't able to make either Drupal meetup, feel free to leave your thoughts in the comments.

Categories: Elsewhere

Cruiskeen Consulting: Yet Another Drupal News Source

Planet Drupal - Wed, 03/09/2014 - 18:55

The world is full of Drupal news sources - Planet Drupal, Drupal Fire, Groups.Drupal.Org, and many many more.  So of course we've decided to build another one. 

Why?  Because we can. And because we've been spending a lot of time playing around with Rebelmouse.  So - aggregating content from all over the planet, we bring you Drop News

Categories: Elsewhere

Phase2: Better Development Through Emotional Intelligence

Planet Drupal - Wed, 03/09/2014 - 18:11

I am unabashedly an engineer. I obsess over the pursuit of finding the most efficient solution to any problem.

In the realm of open source software, this approach has served me well. We read, reverse-engineer, fork, improve, and share. I want my process to be faster, more flexible, and maintainable for the long haul.

As I’ve investigated different methodologies, one characteristic I constantly underestimate is the team dynamic. I tend to pigeon-hole my mind into thinking that the solution to a problem is the most important goal.

Hey look! There’s a problem! I must find a solution for it.

  • What if complex problems can’t be solved by me?
  • What if, when I suggest a tool or a programming philosophy, it masks the need to dive deeply into other factors?

The more I researched my approach, I came across a concept that is vital to team effectiveness when solving complex problems: emotional intelligence.

Emotional Intelligence, sometimes referred to as EQ (emotional intelligence quotient) to complement IQ (intelligence quotient), is the ability to be aware of, express, control, reason, and interpret emotions appropriately.

Within a team, many, many, many studies have shown that EQ, more than IQ, is the key to solving complex problems.

The team dynamic is engrained with the DNA of open-source projects. Any Drupal issue queue or Packagist library commit log supports that.

The better question I ask myself, however, is:

  • Are the teams I work on the most emotionally intelligent?
  • If not, what am I doing to improve that metric?

Peeling back this onion revealed the societal constructs that affected how I view an effective team.

Typically, I look to the most technical people I know for answers. In some cases, I follow the stereotypical engineer playbook of positing a hypothesis, demanding evidence, and playfully browbeating a decision.

Put another way, how many times have I jokingly used the phrase ” Are You  doing it wrong?” and is that the most effective solution?

As the research suggested, this emotionally oblivious approach was philosophically incongruent with proven science!

  • How could I call myself an engineer?!?!
  • How could I obsess about the pursuit of efficiency and solution, when my own attitude was blunting my team’s effectiveness?

I needed to do better.

I needed to find something, rooted in math and science, that helped me understand how to refactor my way of thinking.

I then learned about perspective and heuristic techniques. Perspective is how one looks at a problem. Heuristic is the mental shortcut one uses to arrive at a solution. Both are shaped by experience and knowledge, but the nuance in process from a variety of individuals is key.

Dr. Scott Page elaborates :

The diversity of an agent’s problem-solving approach, as embedded in her perspective-heuristic pair, relative to the other problem solvers is an important predictor of her value and may be more relevant than her ability to solve the problem on her own. Thus, even if we were to accept the claim that IQ tests, Scholastic Aptitude Test scores, and college grades predict individual problem-solving ability, they may not be as important in determining a person’s potential contribution as a problem solver as would be measures of how differently that person thinks.

It opened my eyes to how I’ve been going about solving complex problems all wrong.

In the context of a complicated problem, there is a higher likelihood of finding a global optimum (the best solution) when you have a diverse set of team members with local optimum (their best solution). Put simply, I needed to engage more (not less) with people who were different than me.

In essence, given the right conditions, diversity trumps ability!

What’s interesting about this research, however, is the fact that communication among members with different perspectives is very difficult.

In fact, as Dr. Page continues:

Problem solvers with nearly identical perspectives but diverse heuristics should communicate with one another easily. But problem solvers with diverse perspectives may have trouble understanding solutions identified by other agents.

Thus, we’ve come full circle to why EQ is so important.

If team members are not in-tune with each other, the benefits gained from their diversity can be lost. It is vital, therefore, in my unabashed obsession to being an engineer, that I not only need to improve my EQ, but surround myself with colleagues who have a high EQ and learn from them.

So what are the characteristics of high EQ individuals? Statistically, who has high EQ?

Some of our thought leaders here at Phase2 have answered that question.

If you’re interested in learning more, find me as I share my ideas on a building a more inclusive community at various conferences and camps!

Categories: Elsewhere

Michael J. Ross: Drupal 8 Core's Own Directory

Planet Drupal - Wed, 03/09/2014 - 17:08


This article was published in the print magazine Drupal Watchdog, Volume 4 Issue 1, 2014-05, on page 21, by Tag1 Publishing. The magazine was distributed at Drupalcon Austin, 2014-06-02.

Prior to Drupal 8, the core directories (includes, misc, modules, profiles, scripts, and themes) were located in the installation's root directory. Drupal 8 consolidates them into a new "core" subdirectory, which tidies up the root directory and should make it easier to track changes to core versus contrib or custom files. There are still three root subdirectories for modules, profiles, and themes, which can be used for custom and contrib projects. Each directory initially contains only a README.txt file explaining the repurposing and how developers can still use the pre-D8 "sites/all" scheme.

Figure 1. Drupal 8 root directories and files

Copyright © 2014 Michael J. Ross. All rights reserved.

Categories: Elsewhere

Michael J. Ross: Drupal 8 Core Theme Improvements

Planet Drupal - Wed, 03/09/2014 - 17:07


This article was published in the print magazine Drupal Watchdog, Volume 4 Issue 1, 2014-05, on page 21, by Tag1 Publishing. The magazine was distributed at Drupalcon Austin, 2014-06-02.

When custom and contributed themes are added to a fresh Drupal installation, the core themes often fade into the background, even though they are valuable, particularly for learning theming. In Drupal 7, those core themes are: Bartik (enabled by default), Garland (Drupal 6's default), Seven (optimized for site administration), and Stark (minimalist and thus useful for module output debugging). The sole template engine is the venerable PHPTemplate. Drupal 8 adds Twig as the canonical template engine. Garland is gone, while Bartik, Seven, and Stark have been HTML5-ified and Twig-ified.

Figure 1. Drupal 8 core themes

Copyright © 2014 Michael J. Ross. All rights reserved.

Categories: Elsewhere

Michael J. Ross: Drupal 8 Core Module Changes

Planet Drupal - Wed, 03/09/2014 - 17:05


This article was published in the print magazine Drupal Watchdog, Volume 4 Issue 1, 2014-05, on page 20, by Tag1 Publishing. The magazine was distributed at Drupalcon Austin, 2014-06-02.

Compared to its predecessor, Drupal 8 offers website builders far more capabilities without the use of contributed modules, because it incorporates many of the most popular ones into core (e.g., Actions, CKEditor, Configuration Manager, Entity, and Views), as well as useful field types (e.g., Datetime, E-mail, Entity reference, Link, Options, and Telephone). Conversely, less popular core modules (e.g., Dashboard, OpenID, Overlay, PHP, and Poll) have been dropped. These improvements greatly increase the range of websites that can be built with vanilla Drupal, and reduce the time spent downloading commonly-used modules and scrolling past rarely-used ones.

Figure 1. Drupal 8 core modules sample

Copyright © 2014 Michael J. Ross. All rights reserved.

Categories: Elsewhere

Michael J. Ross: Admin Toolbar Changes in Drupal 8

Planet Drupal - Wed, 03/09/2014 - 17:03


This article was published in the print magazine Drupal Watchdog, Volume 4 Issue 1, 2014-05, on page 20, by Tag1 Publishing. The magazine was distributed at Drupalcon Austin, 2014-06-02.

In Drupal 7, site administrators can utilize its core Toolbar module for speeding navigation. Drupal 8's equivalent improves upon it, sporting a more readable interface, with clear icons. Admin menu items are grouped into: "Manage" (encompassing the menu items of its predecessor, with "Modules" renamed to "Extend"), "Shortcuts", and a user menu for profile management and logging out. The toolbar is responsive to the device's screen width, switching to a vertical orientation for narrow displays — which can be forced by clicking the arrow button on the far right of the toolbar's (white) second level.

Figure 1. Drupal 8 admin toolbar vertical

Copyright © 2014 Michael J. Ross. All rights reserved.

Categories: Elsewhere

DrupalCon Amsterdam: Training spotlight: Views from the Ground Up

Planet Drupal - Wed, 03/09/2014 - 14:41

Drupal users who want to build or customize displays or layouts, or simply build their own administrative areas will love Views from the Ground Up and now is your chance to attend this training at DrupalCon Amsterdam!

Views from the Ground Up consists of 8 real world (and useful) views that are created with an increasing level of complexity. By the end of this class, students will be able to take almost any views display currently being used in Drupal, and override it, to fit better to their particular admin style and needs.

Meet the Trainer from the NorthCross Group

Chris Porter (netw3rker) has spoken at DrupalCon Barcelona, Munich, and San Francisco and has provided this training for the past four years to a variety of global clients, including Fortune 500 companies.

Attend this Drupal Training

This training will be held on Monday, 29 September from 09:00-17:00 at the Amsterdam RAI during DrupalCon Amsterdam. The cost of attending this training is €400 and includes training materials, meals and coffee breaks. A DrupalCon ticket is not required to register to attend this event.

Our training courses are designed to be small enough to provide attendees plenty of one-on-one time with the instructor, but large enough that they are a good use of the instructor's time. Each training course must meet its minimum sign-up number by 5 September in order for the course to take place. You can help to ensure your training course takes place by registering before this date and reminding friends and colleagues to attend.

Register today

Categories: Elsewhere

Modules Unraveled: 117 The Drupal Project Application Process with Jeremy Rasmussen - Modules Unraveled Podcast

Planet Drupal - Wed, 03/09/2014 - 13:07
Published: Wed, 09/03/14Download this episodeProject

It’s easier than you think to publish your module on Drupal.org. This is my experience going through the entire process. Sharing this experience I hope to convince you and others to do the same. Contributing back to the community that gives all of us so much, to many of us our livelihood.

  • When Doug first recommended that I talk to you about this, I wasn’t really thrilled. But, I took a look at your slides, and thought that it actually looked like really good information. So, what made you decide to put together a presentation on the project application process in the first place?
    My “Why”
    Finally published a module to help solve my own problem
    My project that took me through this process is Display Suite Extra Layouts
    Projects don’t have to be the 100% perfect solve for everyone, everywhere
    It’s more about: Giving back, centralizing code, helping others make great projects too.

  • So what are the steps to getting a project reviewed and accepted?
    Where to start and basically the entire guide to submitting a module
    “Apply for permissions to create full projects” https://www.drupal.org/node/1011698
    Some things to know
    One time process
    Reviews are primarily by your peers
    Learns/reiterates code standards and best practices
    Do your Research First
    Check if your idea exists already
    Combine efforts where you can
    Volunteer as a co-maintainer where needed

  • Okay, let’s get down to the nitty-gritty. What are the technical steps you need to follow to get your project approved?
    Setup Git Access
    Learn some Git basics
    Google is your friend
    Github & Code School’s tutorial http://try.github.io
    Setup your Git Access in your D.o profile
    Basically just need to add an SSH key
    Instructions here: https://www.drupal.org/node/1047190
    With Git access setup you can now create sandboxes or “experimental” projects
    Instructions here: https://www.drupal.org/node/1011196
    Take advantage of these, having a commit history of changes is a good thing.
    Use sandboxes to get your code “production ready”
    The Checklist (Pre-Application)
    Before starting the application make sure you run through the checklist
    Setup Readme, Git Branches, well commented, etc...
    Link to checklist: https://www.drupal.org/node/1587704
    The process goes much much faster, many people skip it
    PA Review Bonus
    Part of the checklist asks you to run your sandbox through a bot.
    Catches the majority of problems.
    You can setup your own Review Bot
    “Full Stop” - Took me a while to figure that out.
    You get a review bonus when everything is fixed.
    The Application
    In the title include core version: [D7]
    Write a Clear Descriptions… can be the same as your project/sandbox page
    Clear descriptions help people understand better the purpose of your project
    Provide links to your Sandbox, the Git clone command, and PA Review
    When you are ready set the status to “Needs Review”

  • I noticed when I looked through your slides that you mentioned reviewing other projects as a part of this. Why is that needed?
    Reviewing other projects
    You must review at least 3 other people’s projects
    Post a link to your reviews in your own project application
    It’s just like trying a new module.
    Download it, enable it, try it
    Report back your findings… good, bad, and suggestions
    I learned a lot from doing this
    Now you wait.
    Others will review your project and post feedback.
    be prompt to fix issues
    Once all is well someone should mark your project “Reviewed and Tested by the Community”
    Then you wait for someone with the “Power” to grant you full project status

  • Once someone has approved your project, what’s involved with getting the official project page setup?
    Into the Wild!
    You can now create your project page
    be mindful of your project URL, you can’t change it
    Create a new release on your project page and in Git
    Creating a release: https://www.drupal.org/node/1068944
    Tag Nameing Convention: https://www.drupal.org/node/1015226

Questions from Twitter
  • timani.co.zw
    Will this cover D.O vs github for projects? Pros & cons of staying with current design vs migrating to github?
  • Joshua Turton
MUP117 When are we going to see movement on the project application issue queue? MUP117 process seems broken - have to apply... but once past "quality control" you can release any junk u want. MUP117 Also: encouraged to review others to boost your app's priority, but why would we trust reviews from users who haven't passed through process? (speaking of high priority list/review bonuses) Episode Links: Jeremy on drupal.orgJeremy on TwitterJeremy on Google PlusDrupalCamp Utah Session PageSession SlidesCreating a SandboxApplication ChecklistPareview.shProject ApplicationTags: drupal.orgProjectsplanet-drupal
Categories: Elsewhere

Stefano Zacchiroli: interview for the gnu linux setup

Planet Debian - Wed, 03/09/2014 - 10:48
my setup, take #1

Among the various things I've catched up with during the summer, I've finally managed to set aside some time to answer a pending interview request for The [GNU/]Linux Setup: a blog run by Steven Ovadia that collects interviews about how people use GNU/Linux-based desktops.

In the interview I discuss my day to day work-flow, from GNOME Shell to Mutt, from Emacs to Notmuch, and the various glue code tools I've written for integrating them.


Feedback is most welcome.

Categories: Elsewhere

Junichi Uekawa: Can't link qemu with static.

Planet Debian - Wed, 03/09/2014 - 10:04
Can't link qemu with static. I was puzzled but this looks wrong that pkg-config libssh2 doesn't output -lgpg-error. gcrypt depends on gpg-error.

Categories: Elsewhere

Dirk Eddelbuettel: littler is faster at doing nothing!

Planet Debian - Wed, 03/09/2014 - 04:25

With yesterday's announcement of littler 0.2.0, I kept thinking about a few not-so-frequently-asked but recurring questions about littler. And an obvious one if of course the relationship to Rscript.

As we have pointed out before, littler preceded Rscript. Now, with Rscript being present in every R installation, it is of course by now more widely known.

But there is one important aspect which I stressed once or twice in the past and which bears repeating. Due to the lean and mean way in which littler is designed and set-up, it actually starts a lot faster than either Rscript or R. How, you ask? Well we actually query the environement at build time and hardcode a number of settings which R and Rscript re-acquire and learn each time they start. Which is more flexible. But slower.

So consider the following, really simple example. In it, we create a simple worker function f which launches the given (and simplest possible) R command of just quitting 250 times (by launching a shell command which loops). We then let littler, Rscript and R (in its just execute this expression mode) run this, and time it via one of the common benchmarking packages.

R> library(rbenchmark) R> f <- function(cmd) { system(paste0("bash -c \"for i in \\$(seq 1 250); do ", cmd, " -e 'q()'; done\"")); } R> res <- benchmark(f("r"), f("Rscript"), f("R --slave"), replications=5, order="relative") R> res test replications elapsed relative user.self sys.self user.child sys.child 1 f("r") 5 32.256 1.000 0.001 0.004 26.538 5.706 2 f("Rscript") 5 180.154 5.585 0.001 0.004 152.751 28.522 3 f("R --slave") 5 302.714 9.385 0.001 0.004 270.569 33.098 R>

So there: littler does "nothing" about five times as fast as Rscript, and about nine times as fast as R. Not that this matters greatly -- but when you design something for repeated (unsupervised) execution, say in a cronjob, it might as well be lightweight.

This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.

Categories: Elsewhere

Drupal Easy: Drupal Career Online: a Surprise Advantage Over In-Person Training

Planet Drupal - Wed, 03/09/2014 - 02:32

What do you get when you combine a state-of-the-art open source content management system with a seemingly endless need for developers, an instructor passionate about developing Drupal talent with solid fundamentals and best practices (yours truly), six eager, geographically diverse students (pictured above - more on them in future blog posts), and a modern online classroom environment (the topic of this post)? If the content management system is Drupal, then the only answer is the online version of the Drupal Career Starter Program: Drupal Career Online.

This week marks the start of the first session of Drupal Career Online, an immersive 12-week online training program designed to take people passionate about technology and turn them into Drupal professionals. The curriculum is the result of continuous development and improvement over the past three years, and now features a dedicated web site, PDF handouts and reference documents for every lesson, weekly self-assessment quizzes, screencasts covering important concepts and a healthy dose of Drupal community involvement.


read more

Categories: Elsewhere

Mario Lang: exercism.io C++ track

Planet Debian - Tue, 02/09/2014 - 22:20

exercism.io is a croud-sourced mentorship platform for learning to program. In my opinion, they do a lot of things right. In particular, an exercise on exercism.io consists of a descriptive README file and a set of test cases implemented in the target programming language. The tests have two positive sides: You learn to do test-driven development, which is good. And you also have an automated validation suite. Of course, a test can not give you feedback on your actual implementation, but at least it can give you an idea if you have managed to implement what was required of you. But that is not the end of it. Once you have submitted a solution to a particular exercise, other users of exercism.io can comment on your implementation. And you can, as soon as you have submitted the first implementation, look at the solutions that other people have submitted to that particular problem. So knowledge transfer can happen both ways from there on: You can learn new things from how other people have solved the same problem, and you can also tell other people about things they might have done in a different way. These comments are, somewhat appropriately, called nitpicks on exercism.io.

Now, exercism has recently gained a C++ track. That track is particularily fun, because it is based on C++11, Boost, and CMake. Things that are quite standard to C++ development these days. And the use of C++11 and Boost makes some solutions really shine.

Categories: Elsewhere

Ian Campbell: Becoming A Debian Developer

Planet Debian - Tue, 02/09/2014 - 19:58

After becoming a DM at Debconf12 in Managua, Nicaragua and entering the NM queue during Debconf13 in Vaumarcus, Switzerland I received the mail about 24 hours too late to officially become a DD during Debconf14 in Portland, USA. Nevertheless it was a very pleasant surprise to find the mail in my INBOX this morning confirming that my account had been created and that I was officially ijc@debian.org. Thanks to everyone who helped/encouraged me along the way!

I don't imagine much will change in practice, I intend to remain involved in the kernel and Debian Installer efforts as well as continuing to contribute to the Xen packaging and to maintain qcontrol (both in Debian and upstream) and sunxi-tools. I suppose I also still maintain ivtv-utils and xserver-xorg-video-ivtv but they require so little in the way of updates that I'm not sure they count.

Categories: Elsewhere

Drupal Watchdog: Composer: Sharing Wider

Planet Drupal - Tue, 02/09/2014 - 18:52

Drupal has long had a strong collaborative culture. We share modules, we share development tasks on core and modules, and we share infrastructure on Drupal.org. That's a critical part of the health of our community: Sharing is how Open Source works.

The broader PHP world, however, has long sucked at sharing. Every project is its own island; sharing code between projects has been difficult, and managing third party libraries a pain. Just about the only option was PEAR, but unless you had root access on every server you needed, and were running only a single application per server, it wasn't really useful.

That was then, this is now. Enter Composer, a PHP dependency management tool that works. Composer began life in late 2011 in the Symfony community but was deliberately built to be project-agnostic, and today is being used by thousands of projects large and small, including Drupal.

Composer Basics

Composer consists of two parts. One is Packagist.org, which is a central clearinghouse of Composer-compatible packages. As of July 2013, Packagist offers over 13,000 packages, ranging from simple libraries to complete frameworks. The other part is Composer itself, a command line PHP application that is dead simple to install. By default, Composer will download packages from Packagist.org but you can also set up your own package server, or even just one-off Git repositories, to host Composer-capable code. All you need to make it work is a simple JSON file.

Let's start off with a trivial example. We’ll write a super-simple script that uses the Guzzle HTTP client (now bundled with Drupal 8). To start off, create your project folder. Inside it, create a directory called src. That's where we'll put all of our code. Now create a file called composer.json with the following contents:

Categories: Elsewhere

Rapha&#235;l Hertzog: My Free Software Activities in August 2014

Planet Debian - Tue, 02/09/2014 - 17:58

This is my monthly summary of my free software related activities. If you’re among the people who made a donation to support my work (65.55 €, thanks everybody!), then you can learn how I spent your money. Otherwise it’s just an interesting status update on my various projects.

Distro Tracker

Even though I was officially in vacation during 3 of the 4 weeks of August, I spent many nights working on Distro Tracker. I’m pleased to have managed to bring back Python 3 compatibility over all the (tested) code base. The full test suite now passes with Python 3.4 and Django 1.6 (or 1.7).

From now on, I’ll run “tox” on all code submitted to make sure that we won’t regress on this point. tox also runs flake8 for me so that I can easily detect when the submitted code doesn’t respect the PEP8 coding style. It also catches other interesting mistakes (like unused variable or too complex functions).

Getting the code to pass flake8 was also a major effort, it resulted in a huge commit (89 files changed, 1763 insertions, 1176 deletions).

Thanks to the extensive test suite, all those refactoring only resulted in two regressions that I fixed rather quickly.

Some statistics: 51 commits over the last month, 41 by me, 3 by Andrew Starr-Bochicchio, 3 by Christophe Siraut, 3 by Joseph Herlant and 1 by Simon Kainz. Thanks to all of them! Their contributions ported some features that were already available on the old PTS. The new PTS is now warning of upcoming auto-removals, is displaying problems with uptream URLs, includes a short package description in the page title, and provides a link to screenshots (if they exist on screenshots.debian.net).

We still have plenty of bugs to handle, so you can help too: check out https://tracker.debian.org/docs/contributing.html. I always leave easy bugs for others to handle, so grab one and get started! I’ll review your patch with pleasure.


After my last batch of contributions to Tryton’s French Chart of Accounts (#4108, #4109, #4110, #4111) Cédric Krier granted me commit rights to the account_fr mercurial module.

Debconf 14

I wasn’t able to attend this year but thanks to awesome work of the video team, I watched some videos (and I still have a bunch that I want to see). Some of them were put online the day after they had been recorded. Really amazing work!

Django 1.7

After the initial bug reports, I got some feedback of maintainers who feared that it would be difficult to get their packages working with Django 1.7. I helped them as best as I can by providing some patches (for horizon, for django-restricted-resource, for django-testscenarios).

Since I expected many maintainers to be not very pro-active, I rebuilt all packages with Django 1.7 to detect at least those that would fail to build. I tagged as confirmed all the corresponding bug reports.

Looking at https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=python-django@packages.debian.org;tag=django17, one can see that some progress has been made with 25 packages fixed. Still there are at least 25 others that are still problematic in sid and 35 that have not been investigated at all (except for the automatic rebuild that passed). Again your help is more than welcome!

It’s easy to install python-django 1.7 from experimental and they try to use/rebuild the packages from the above list.

Dpkg translation

With the freeze approaching, I wanted to ensure that dpkg was fully translated in French. I thus pinged debian-l10n-french@lists.debian.org and merged some translations that were done by volunteers. Unfortunately it looks like nobody really stepped up to maintain it in the long run… so I did myself the required update when dpkg 1.17.12 got uploaded.

Is there anyone willing to manage dpkg’s French translation? With the latest changes in 1.17.13, we have again a few untranslated strings:
$ for i in $(find . -name fr.po); do echo $i; msgfmt -c -o /dev/null --statistics $i; done
1083 translated messages, 4 fuzzy translations, 1 untranslated message.
268 translated messages, 3 fuzzy translations.
545 translated messages.
2277 translated messages, 8 fuzzy translations, 3 untranslated messages.

Misc stuff

I made an xsane QA upload (it’s currently orphaned) to drop the (build-)dependency on liblcms1 and avoid getting it removed from Debian testing (see #745524). For the record, how-can-i-help warned me of this after one dist-upgrade.

With the Django 1.7 work and the need to open up an experimental branch, I decided to switch python-django’s packaging to git even though the current team policy is to use subversion. This triggered (once more) the discussion about a possible switch to git and I was pleased to see more enthusiasm this time around. Barry Warsaw tested a few workflows, shared his feeling and pushed toward a live discussion of the switch during Debconf. It looks like it might happen for good this time. I contributed my share in the discussions on the mailing list.


See you next month for a new summary of my activities.

2 comments | Liked this article? Click here. | My blog is Flattr-enabled.

Categories: Elsewhere

Appnovation Technologies: My Local Development Evolution

Planet Drupal - Tue, 02/09/2014 - 17:49

Over the last eight months, I have been a developer at Appnovation.  During my time here, I have learned plenty new things and worked on a lot of different projects.

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

Drupal core announcements: No Drupal 6 or Drupal 7 core release on Wednesday, September 3

Planet Drupal - Tue, 02/09/2014 - 16:34

The monthly Drupal core bug fix release window is scheduled for this Wednesday. However, there have been three releases (security releases as well as bug fix releases) in the last month and a half, and not as many changes have been committed to the development version since then as would normally warrant yet another new release.

A Drupal 7 bug fix release during the October release window is likely instead.

Upcoming release windows include:

  • Wednesday, September 17 (security release window)
  • Wednesday, October 1 (bug fix release window)

For more information on Drupal core release windows, see the documentation on release timing and security releases, and the discussion that led to this policy being implemented.

Categories: Elsewhere


Subscribe to jfhovinne aggregator - Elsewhere