Feed aggregator

Drupal Association News: A Great Reason to Join the Drupal Association: One Month of Free Training!

Planet Drupal - Tue, 08/07/2014 - 22:01

We’ve joined forces with several Drupal training companies to convince you that there is no better time to join the Drupal Association. And if you are already a member, here is a great reason to encourage your Drupal friends to join: free training!

This July 24th, look for announcements on:

Twitter @DrupalAssoc

IRC channels #drupal-association, #drupal, and #drupal-watercooler.

Sign up as one of the first 25 members to join after each announcement and you will receive a coupon for free online training from one of the participating companies. We’ve ensured all the trainers will provide you with training whether you are a novice or advanced learner. You will be supporting Drupal Association programs as a new member and you will learn new skills. Mark you calendar for July 24th.

Thanks to BuildAModule, Drupalize.Me, lynda.com, ModulesUnraveled, and OSTraining for generously providing training for this event.

Personal blog tags: Membership
Categories: Elsewhere

Blink Reaction: Drupal Coding Standards

Planet Drupal - Tue, 08/07/2014 - 20:27

When it comes to Drupal coding standards rules were NOT made to be broken. In this article Matt Korostoff explains the value of coding standards, specifically in Drupal.

Categories: Elsewhere

Wouter Verhelst: HP printers require systemd, apparently

Planet Debian - Tue, 08/07/2014 - 20:15
printer-driver-postscript-hp Depends: hplip hplip Depends: policykit-1 policykit-1 Depends: libpam-systemd libpam-systemd Depends: systemd (= 204-14)

Since the last in the above is a versioned dependency, that means you can't use systemd-shim to satisfy this dependency.

I do think we should migrate to systemd. However, it's unfortunate that this change is being rushed like this. I want to migrate my personal laptop to systemd—but not before I have the time to deal with any fallout that might result, and to make sure I can properly migrate my configuration.

Workaround (for now): hold policykit-1 at 0.105-3 rather than have it upgrade to 0.105-6. That version doesn't have a dependency on libpam-systemd.

Off-hand questions:

  • Why does one need to log in to an init system? (yes, yes, it's probably a session PAM module, not an auth or password module. Still)
  • What does policykit do that can't be solved with proper use of Unix domain sockets and plain old unix groups?

All this feels like another case of overengineering, like most of the *Kit thingies.

Ah well.

Categories: Elsewhere

Mediacurrent: Meeting Marketing Challenges with Automation and Drupal

Planet Drupal - Tue, 08/07/2014 - 20:06

Often marketing's biggest challenges are long sales cycles, complex decision-making processes, and multiple stakeholders. There is increasing pressure on marketing professionals to find the most qualified prospects and build relationships with them before the lead is passed to sales.

Categories: Elsewhere

Acquia: Conference Organizing Distribution (COD) 7 Beta2

Planet Drupal - Tue, 08/07/2014 - 20:01
COD Beta 2

Over the Holiday weekend, over 25 tickets were solved coming out of the Alpha6 and Beta1 release of COD. Late Monday night, COD Beta2 was released! This release includes fixes to the session submission system, specifically where time-slots and tracks weren't being properly saved in some conditions. We also made changes to the administration menu paths to de-couple them from the node and be less confusing. You can see the full release notes here: https://www.drupal.org/node/2299327

Categories: Elsewhere

kevinquillen.com: Media Migration Tip in Drupal

Planet Drupal - Tue, 08/07/2014 - 20:00

If you’re doing a migration of media files, you most likely will be working with a list of URLs. Other times, you will have a local file system from which to pull in media. When working with just a list of URLs though, you’re somewhat working with a ‘blind’ import.

Categories: Elsewhere

Open Source Training: The State of Drupal 8: July 2014

Planet Drupal - Tue, 08/07/2014 - 19:30

It's been 8 months since our last overview of Drupal 8.

A good number of OSTraining members went to DrupalCon Austin or to DrupalCamps this summer and came back with questions about Drupal 8.

So, here's an update on Drupal 8 and when you can plan on using it.

Categories: Elsewhere

Greg Knaddison: Drupalcamp Colorado 2014 Preview: Large Scale Drupal

Planet Drupal - Tue, 08/07/2014 - 14:48

This year, Drupalcamp Colorado is taking on the topic of "Large Scale Drupal" - a phrase that was popularized by Dries Buytaert. We're taking that phrase and using it in a generic sense to help set a focus for our event.

Matthew Saunders wrote a great overview of the camp, so if you're interested and need more convincing to come, read that. This is an update on our tracks and some great sessions that have been accepted already.

Tracks and session submission requests

We're taking that theme as inspiration for our sessions which will be across 4 tracks:

  • Business and Open Source
  • DevOps
  • Commerce
  • Design and Front End
  • Development and Site Building

Today we are excited to announce the first 9 sessions that have been selected. Session Submission is still open until July 11th. We've currently got too many sessions in /Development and Site Building/ and not enough sessions in the other categories. So...if you have something to say in those other areas, please submit a session (note, you have to login first, and you should register too).

First sessions that have been accepted:

There are some sessions we know we're going to accept because they come from great presenters on popular topics that match our theme. Below are the 9 sessions we knew we could accept now.

I think you could attend just these 9 sessions and really have a great weekend of Drupal content and there are going to be dozens more. If you look at the titles and the presenters I think you'll see that there's a lot of people working on interesting problems as a result of dealing with "large scale" sites built in Drupal.

Categories: Elsewhere

Steve Kemp: What do you do when your free service is too popular?

Planet Debian - Tue, 08/07/2014 - 11:56

Once upon a time I setup a centralized service for spam-testing blog/forum-comments in real time, that service is BlogSpam.net.

This was created because the Debian Administration site was getting hammered with bogus comments, as was my personal blog.

Today the unfortunate thing happened, the virtual machine this service was running on ran out of RAM and died - The redis-store that holds all the state has now exceeded the paltry 512Mb allocated to the guest, so OOM killed it.

So I'm at an impasse - I either recode it to use MySQL instead of Redis, or something similar to allow the backing store to exceed the RAM-size, or I shut the thing down.

There seems to be virtually no liklihood somebody would sponsor a host to run the service, because people just don't pay for this kind of service.

I've temporarily given the guest 1Gb of RAM, but that comes at a cost. I've had to shut down my "builder" host - which is used to build Debian packages via pbuilder.

Offering an API, for free, which has become increasingly popular and yet equally gets almost zero feedback or "thanks" is a bit of a double-edged sword. Because it has so many users it provides a better service - but equally costs more to run in terms of time, effort, and attention.

(And I just realized over the weekend that my Flattr account is full of money (~50 euro) that I can't withdraw - since I deleted my paypal account last year. Ooops.)


Happy news? I'm avoiding the issue of free service indefinitely with the git-based DNS product which was covering costs and now is .. doing better.

Categories: Elsewhere

DrupalCon Amsterdam: Session selection for DrupalCon from the inside-out

Planet Drupal - Tue, 08/07/2014 - 08:14

Like almost everything in the Drupal world, DrupalCon is, in part, a labor of passionate enthusiasts who donate their time. Every year, the Drupal Association appoints a program team who work together to select sessions for upcoming DrupalCons. The program team is unique to every conference, but volunteers of past cons (called “globals”) are asked to join the committee to assist the newer members and pass on historical knowledge.

DrupalCon sessions are divided into tracks, which generally stay the same, but have evolved over the years. For Amsterdam, we have:

  • Coding and Development
  • Core Conversations
  • DevOps
  • Drupal Business
  • Frontend
  • Site Building

For Amsterdam, we’ve added two new mini tracks; Case Studies and PHP. We’ve also added Business Showcase (formerly Day Stage) and the Community track is now a full day summit on the Monday.

Each track has a Chair (or Lead) - someone who takes the lead on setting the theme of the track, generating interest and inviting speakers, and selecting sessions. Last year, I was the Track Chair for the Coding and Development track for DrupalCon Prague. This year, I was lucky enough to be asked to be a “Global” (or co-chair) for the Coding and Development track for Amsterdam. This means that I was there as support for the new track chair, Pedro Cambra (pcambra). I was helped by veterans of previous DrupalCons, Jason Yee (jyee) and Larry Garfield (Crell).

Pedro and team have done a fantastic job of canvassing for speakers and helping people with their session proposals.

There’s a lot of elements to session selection. We need to make sure that sessions are of value to a wide audience. The presenters must be engaging speakers who can interest a large crowd of attendees. We try as hard as we can to bring in new (to DrupalCon) speakers, and speakers who bring something from outside of the Drupal sphere. We want to make sure that the diversity of the community is represented and encouraged. And we need to work across track teams to ensure that one speaker is not speaking in several tracks; both for the sake of their stress and sanity in preparing the talks and to ensure that everyone who applied has the best chance of speaking. Finally, we need to make sure that sessions fit both the theme of the track and of the conference.

As you can imagine, balancing all of this can be quite challenging!

Each track team ranks their sessions as makes sense to the team. In the Coding and Development track, Pedro, Jason, and I rated each session and speaker out of 5, paying special attention to the quality and relevancy of the submission and the speaker's rapport with their audience. If we're lucky, we've seen the speaker present before, but if not, we can view any available slide decks or recordings to get a sense for their presenting ability. This is why it’s very important for prospective speakers to include speaking history in their session proposal. A speaker doesn't need to have sessions online to be selected - it just makes our job easier. We refined the 128 submissions in the Coding and Development track down to a top rated 25 or so sessions, which were then filtered to make sure that there is no overlap and that the speaker wasn’t speaking in another track.

Being so involved in the planning of content for DrupalCon is an enlightening experience. The breadth of knowledge, experience, and creativity in the Drupal community is quite literally overwhelming. The 510 sessions submitted this year illustrate just how passionate the community is.

There’s no better way to get a sense of the Drupal zeitgeist than to pore over hundreds of sessions. This discovery exposes us all to new technologies, projects, and methodologies, and at least for me has made me aware of people in the community that are doing fascinating, challenging, and important work - people I might never have found otherwise. There’s also a degree of humility to be observed when considering the diverse and very well informed views of your fellow content team members.

After two weeks of review, ranking, and deliberation across timezones, I present to you with the 90+ DrupalCon Amsterdam selected sessions.

View selected sessions

If you are interested in becoming involved in DrupalCon planning in the future, let the DA know. It's very rewarding, and the team dinner during the conference just caps it all off!

Cameron Tod (cam8001)
DrupalCon Amsterdam Coding and Development Co-Chair

Categories: Elsewhere

Matthew Palmer: Doing Password Complexity Wrong

Planet Debian - Tue, 08/07/2014 - 07:00

I just made an account on yet another web service. On the suggestion of my password manager, I attempted to use the password “W:9[$X*F”. It was rejected because “Password must contain at least one non-alphabet character, one lowercase letter, one uppercase letter”. OK, how about “Passw0rd”? Yep, that’s fine.

Anyone want to guess which of those two passwords is going to fall victim to a brute-force attack first? Go on, don’t be shy, take a wild shot in the dark!

Categories: Elsewhere

Kristian Polso: Fix Drupal Registry with Registry Rebuild

Planet Drupal - Tue, 08/07/2014 - 06:45
It has happened to all of us. You mistakenly remove a module directory or migrate your site and forget to include some necessary modules. This causes your Drupal site only to show the WSOD and perhaps the following error:
Categories: Elsewhere

Joey Hess: laptop death

Planet Debian - Tue, 08/07/2014 - 02:00

So I was at Ocracoke island, camping with family, and I brought my laptop along as I've done probably half a dozen times before. An enormous thuderstorm came up. It rained for 8 hours and thundered for 3 of those. Some lightning cracks quite close by as we crouched in the food tent, our feet up off the increasingly wet ground "just in case". The campground flooded. Luckily we were camped in the dunes and tents mostly avoided being flooded with 2-3 inches of water. (That was just the warmup; a hurricane hit a week after we left.)

My laptop was in my tent when this started, and I got soaked to the skin just running over there and throwing it up on the thermarest to keep it out of any flooding and away from any drips. It seemed ok, so best not to try to move it to the car in that downpour.

Next time I checked, it turned out the top vent of the tent was slightly open and dripping. The laptop bag was damp. But inside it seemed ok. Rain had slackened to just heavy, so I ran it down to the car. Laptop appeared barely damp, but it was hard to tell as I had quite forgotten what "dry" was. Turned it on for 10 seconds to check the time. It was 7:30 and we still had to cook dinner in this mess. Transferred it to a dry bag.

(By the way, in some situations, discovering you have a single dry towel you didn't know you had is the best gift in the world!)

Next morning, the laptop was dead. When powered on, the fan came on full, the screen stayed black, and after a few seconds it turned itself back off.

I need this for work, so it was a crash priority to get it fixed or a replacement. Before I even got home, I had logged onto Lenovo's website to check warantee status and found 2 things:

  1. They needed some number from a sticker on the bottom of my laptop. Which was no longer there.
  2. The process required some stange login on an entirely different IBM website.

At this point, I had a premonition of how the beuracracy would go. Reading Sesse's Blehnovo, I see I was right. I didn't even try. I ordered a replacement with priority shipping.

When I got home, I pulled the laptop apart to try to debug it. I still don't know what's wrong with it. The SSD may be damaged; it seems to cause anything I put it into to fail to work.

New laptop arrived in 2 days. Since this model is now a year old, it was a few hundred dollars cheaper this time around. And now I have an extra power supply, and a replacment keyboard, and a replacement fan etc. And I've escaped the dead USB port and broken rocker switch of the old laptop too.

The only weird thing is that, while my old laptop had no problem with my Toshiba passport USB drive, this new one refuses to recognize it unless I plug it into a USB 1.0 hub. Oh well..

Categories: Elsewhere

Steinar H. Gunderson: Blehnovo

Planet Debian - Tue, 08/07/2014 - 00:00

Here's my own little (ongoing) story about Lenovo's customer support; feel free to skip if you don't like rants. (You may remember that it took me several months to get to actually buy this laptop in the first place.) Everything within “quotes” are actual quotes from Lenovo, except where otherwise noted.

May 30th: My laptop accidentially goes into the ground, and the screen cracks. Gah. Oh well, I'll be without laptop over the weekend, but I have this nice accident warranty and NBD thing from Lenovo, right? I go to their support web site; they recommend that I register with IBM and file a service ticket. I do so. Their site says I will receive a confirmation email within ten minutes.

Jun 1st: I realize I haven't received anything from Lenovo or IBM, despite 36 hours passing. Oh well.

Jun 2nd: The web system claims Lenovo has “successfully contacted” me several times, despite me never hearing anything from them.

Jun 3rd: I call Lenovo. They don't speak any English. They say there's an error in the “type” I've given them; seemingly “X240” is an invalid type, I needed to write “20AL”. I get it corected.

Jun 4th: Lenovo calls. I talk to them in German and explain what happened (again). They say that I have the choice between paying €150 + parts and sending it in, or €450 + parts to have a serviceman come to me. (I am not 100% sure these numbers are correct, but they're in the right ballpark.) I say that this sounds very weird since I have accident insurance, but the guy from Lenovo seems unfazed and says they will only cover things under warranty if it's a design mistake. Eventually I say that sure, I'll pay for the serviceman; I just want my laptop fixed, fast. They ask for photos of the damage, which I send immediately.

Jun 6th: A week after the damage, and nothing has happened.

Jun 12th: Still nothing has happened. I press the “escalate” button on the web page.

Jun 18th: Still nothing has happened. I send Lenovo email asking what the heck is going on. My case now changes to “the customer will send the machine in to the depot for servicing” (not an exact quote; I don't have this text anymore), and I get an email with an address. I reply asking why on Earth this is, quoting their web page for saying “If you are entitled to Onsite Warranty, your Accidental Damage Protection claim may be repaired at your location”.

Later that day, Lenovo calls me again. It turns out they have no extended warranty or insurance registered on me. They ask me to provide “proof of purchase”, and give me a new case number (since the old one is now seemingly locked into a “will send to depot” situation). I send them the warranty email they originally sent me, including a long warranty code (20 alphanumeric digits) and a PIN. (In passing, I notice that due to a very delayed shipment, this warranty seemingly started running a month or so before I actually received the laptop, so the so-called 4-year warranty is seemingly 3 years 11 months. Oh well.)

Jun 19th: I am contacted by Lenovo. They say this information is not good enough as “proof of purchase”. They reiterate that I need to send them “proof of purchase”. I send them every single email I have ever received for them regarding my purchase.

Jun 24th: Nothing has happened. I email Lenovo asking for a status update. I get an email saying they have “forwarded all the needed information to the warranty service, so that the extended warranty will be registered”. All I can do is wait.

Jun 30th: I miss a telephone call from Lenovo. I get an email saying they'll close the case in two days. I call them, choosing English in the telephone menu. I get to a polite gentleman who speaks English well, but all the case notes are in German, so he can't make heads or tails of my case. He says he'll have the technician responsible for my case call me back.

He does really call me back the same day. He says what they have received is not valid as “proof of purchase”. I become agitated over the phone, pointing out that it should not be my problem if their internal systems are messed up; I've obviously paid 228 CHF for something. He claims to understand, but says that the systems will not work without a “proof of purchase”. He says I need to call Digital River (the company that operates shop.lenovo.ch). He gives me their telephone number. I think it looks funny, and asks him if this is really the right number; he says oh, no, that's the German one, not the Swiss one. He gives me the Swiss one. I call the number and it's for some completely different company, so I try the German one. It gives me a telephone menu, which says that for ThinkPad warranty questions, I need to call <some number>. I call that number; it's for Lenovo tech support in Germany. The tech in the other end of the line does not understand why Digital River would send me to Lenovo for warranty questions, but gives me their Swiss number and email address. The Swiss number is indeed correct, but just sends me to exactly the same menu. I send them an email.

On a whim, I check my warranty page on lenovo.com. It clearly says I have the extended warranty properly registered already! I forward a screenshot to Lenovo.

Jul 1st: I get an email from Lenovo: “Although the warranty appears on Lenovo website to be ok, please send us the proof of purchase from the extended warranty, so we can register it in our database(it appears NOT to be registered). Thank you.”

Jul 3rd: I get an email from Digital River, pointing me to a web page where I can print out some very nondescript-looking bill. I make a PDF out of it and send it to Lenovo.

Jul 7th: I still haven't heard anything from Lenovo. But! Now I am in Norway on vacation, which means I have a new trick up my sleeve: I call Lenovo Norway. I describe the case. The man says that this won't be covered by warranty, and I point out that I have accident insurance. He says (my translation/paraphrasing): “Oh, you're right, it does show up in this other system here! Don't worry, we'll fix this.” He asks me to send him an email with the screenshot of the warranty. I do so. He opens a new case, tells me that I'll have to send it in (seemingly onsite is only for warranty coverage after all?), but that it'll usually take less than a week. I receive an email with a link to DHL for ordering pickup, packaging instructions and pre-filled customs documents. It also has a form where I am supposed to briefly describe the case again (sure), say what I want them to do if the SSD is damaged (give it back to me unrepaired so I can do my own rescue; no Windows 8.1 reimaging, please) and write down all my passwords (fat chance).

So, there we are. Seven minutes with Lenovo Norway got me where 38 days of talking to Lenovo Switzerland/Germany couldn't—now let's just hope that DHL actually picks it up tomorrow and that I get it repaired and back within reasonable time.

The end? I hope.

Categories: Elsewhere

Drupal.org Featured Case Studies: Newstica

Planet Drupal - Mon, 07/07/2014 - 22:51
Completed Drupal site or project URL: http://www.newstica.com

Newstica.com is an intelligent news reading application operated by a Canadian company. The website collects hundreds of news stories daily and creates a unique set of articles on each page view with the use of sophisticated algorithms that operate off individual users' preferences.

Key modules/theme/distribution used: PanelsViewsZenFeedsFeeds XPath ParserTeam members: highvrahos
Categories: Elsewhere

Mediacurrent: Using Sass Breakpoints Effectively

Planet Drupal - Mon, 07/07/2014 - 22:02

There have been plenty of blog posts touting the reasons to use Sass as a CSS preprocessor, and if you've been doing responsive design for a while, you're probably already using the Breakpoint gem with Sass. But there are many ways to use both of these tools, so let's talk about using breakpoints effectively. 

Start with the small screen first, then expand until it looks like sh*t. Time for a breakpoint!
- Stephen Hay.

Categories: Elsewhere

Chuva Inc.: Entity Metathing what? -- A very brief introduction on entity_metadata_wrappers

Planet Drupal - Mon, 07/07/2014 - 21:57

Are you familiar with entity_metadata_wrappers? If you’re not, oh boy, you should be!

Entity Metadata Wrapper is the right way - and, after you get the grip of it, the easiest way - for you to manipulate anything with a field when coding your module. Sure, since the old days of CCK we are used with dealing with our fields in our nodes. Except they are a little messy.

Cleaner code!

Instead of doing this:

$first_name = '';
if (!empty($node->field_first_name)) {
  $name = $node->field_first_name[LANGUAGE_NONE][0]['value'];

Let’s condense that, shall we?

$node_wrapper = entity_metadata_wrapper('node', $node);
$first_name = $node_wrapper->field_first_name->value();

Sure, the name “metadata wrapper” may be a little intimidating, but it does shortens your code and makes it clearer. Oh, and if you have an entity reference field, or a file field, you can just do this:

$image = $node_wrapper->field_image->value();

And the $referenced_node is already a loaded file object, not a useless “fid”.

Wrappers for dealing with entity reference: cleaner-er code!

Suppose you have two node types: Employee and Department. There is an Entity reference field from "Employee" to "Department" and on the "Department" node you have a field called "field_dept_phone" that stores the phone number. (for simplicity, I'm assuming that field_employee_dept is required).

If you have the $employee node, how to fetch the phone number?

Hard way:

$phone = '';
$department = node_load($employee->field_employee_dept[LANGUAGE_NONE][0]['target_id']);
if ($department && !empty($department->field_dept_phone[LANGUAGE_NONE][0]['value'])) {
  $phone = $department->field_dept_phone[LANGUAGE_NONE][0]['value'];

And the wrapper way:

$wrapper = entity_metadata_wrapper('node', $employee);
$phone = $wrapper->field_employee_dept->field_dept_phone->value();


Now what?

Well, this post is not intended to be a full entity metadata wrapper course, so, if I have convinced you, take 15 minutes of your day and do this:

  1. Download Entity API from http://drupal.org/project/entity
  2. Read this, now: https://drupal.org/node/1021556
  3. Your life quality will improve, proportionally to your code quality!

Photo credits: https://www.flickr.com/photos/81564552@N00/3208209972/

PHPentityentity_metadata_wrappersdrupal planet
Categories: Elsewhere

Drupal governance announcements: Shared Values and the Drupal Community

Planet Drupal - Mon, 07/07/2014 - 21:50

Dries recently wrote a blog post about the challenges of fostering diversity and inclusivity in the Drupal community. This is the latest installment of a conversation that’s been going on for years.

In 2012, a group of Drupal community members worked together to draft a Code of Conduct that could be used to supplement the Drupal community’s Code of Conduct at DrupalCon and other in-person events.

This effort prompted a large (and sometimes heated) conversation that involved people from all corners of the Drupal community. This conversation was a difficult one, and many of us disagreed about many different things, but ultimately, we all agreed on several general principles:

We are a group of diverse people from a wide variety of ethnic, cultural, and religious backgrounds, and we embrace that.
Making all attendees feel welcome and included at DrupalCon is everyone’s job.
We treat each other with dignity and respect.
We take responsibility for our words and actions and the impact that they may have on others.

These principles informed the DrupalCon Code of Conduct, which was ratified by the Drupal Association in the summer of 2012 and has been used at every DrupalCon since.

At the last few DrupalCons, there have been a number of reported incidents, including groping, sexual harassment, physical assault, inappropriate comments made about female speakers, and more. While we are grateful that these incidents are being reported, even a single incident is too many.

In early 2013, the Community Working Group was chartered by Dries to uphold the Drupal Code of Conduct and to maintain a friendly and welcoming community for the Drupal project.

As a community, it’s important that we always keep our shared principles and values in mind when interacting with others, whether that be in person at DrupalCon, in the issue queues on Drupal.org, on IRC, or via social media. As the DrupalCon Code of Conduct states, the purpose is not to restrict the diversity of ideas and expression, but instead to ensure that there is a place for everyone in the Drupal community who agrees to abide by these basic principles.

Even when everyone has the best intentions, however, it’s inevitable that conflicts will occur. To ensure that these are addressed in a manner consistent with our shared values, the Community Working Group has worked with the community to develop a conflict resolution policy that lays out the process for addressing disagreements. This policy was developed by participants in the Community Summits at DrupalCons Prague and Austin, with additional review on Drupal.org.

This policy seeks to first and foremost empower individuals to resolve issues between themselves when possible, asking for help when needed, and only after that fails to escalate further. This approach gives people more control over their dispute and is the most likely to result in a positive outcome for everyone involved.

For matters that cannot or should not be resolved in any other way, the Community Working Group is available as a point of escalation. Incidents can be confidentially reported to the Community Working Group using the Incident Report Form. If the issue falls within the purview of the Community Working Group’s jurisdiction, we will then work with the involved individuals to find a remedy.

In her DrupalCon Austin keynote Erynn Petersen talked about how diversity is a key component of a healthy and productive community. While the Drupal community is one of the most diverse and welcoming communities in open source, we still have room for improvement. If you’re interested in joining us in that effort, let us know by responding to our call for volunteers or by participating in a Community Summit at an upcoming DrupalCon.

Actively supporting and maintaining a welcoming environment is something that every one of us in the Drupal community needs to be a part of, and it’s essential to the long-term health and growth of the project and community that we all love so much.

Categories: Elsewhere

Jonathan McDowell: 2014 SPI Board election nominations open

Planet Debian - Mon, 07/07/2014 - 21:30

I put out the call for nominations for the 2014 Software in the Public Interest (SPI) Board election last week. At this point I haven't yet received any nominations, so I'm mentioning it here in the hope of a slightly wider audience. Possibly not the most helpful as I would hope readers who are interested in SPI are already reading spi-announce. There are 3 positions open this election and it would be good to see a bit more diversity in candidates this year. Nominations are open until the end of Tuesday July 13th.

The primary hard and fast time commitment a board member needs to make is to attend the monthly IRC board meetings, which are conducted publicly via IRC (#spi on the OFTC network). These take place at 20:00 UTC on the second Thursday of every month. More details, including all past agendas and minutes, can be found at http://spi-inc.org/meetings/. Most of the rest of the board communication is carried out via various mailing lists.

The ideal candidate will have an existing involvement in the Free and Open Source community, though this need not be with a project affiliated with SPI.

Software in the Public Interest (SPI, http://www.spi-inc.org/) is a non-profit organization which was founded to help organizations develop and distribute open hardware and software. We see it as our role to handle things like holding domain names and/or trademarks, and processing donations for free and open source projects, allowing them to concentrate on actual development.

Examples of projects that SPI helps includes Debian, LibreOffice, OFTC and PostgreSQL. A full list can be found at http://www.spi-inc.org/projects/.

Categories: Elsewhere

Jan Wagner: Monitoring Plugins release ahead

Planet Debian - Mon, 07/07/2014 - 15:41

It seems to be a great time for monitoring solutions. Some of you may have noticed that Icinga has released it's first stable version of the completely redeveloped Icinga 2.

After several changes in the recent past, where the Team maintaining the Plugins used for several Monitoring solutions was busy moving everything to new infrastructure, they are now back on track. The recent development milestone is reached and a call for testing was also sent out.

In the meanwhile I prepared the packaging for this bigger move. The packages are now moved to the source package monitoring-plugins, the whole packaging changes can be observed in the changelog. With this new release we have also some NEWS, which might be useful to check. Same counts for upstream NEWS.

You can give the packages a go and grab them from my 'unstable' and 'wheezy-backports' repositories at http://ftp.cyconet.org/debian/. Right after the stable release, the packages will be uploaded into debian unstable, but might get delayed by the NEW queue due the new package names.

Categories: Elsewhere


Subscribe to jfhovinne aggregator