Elsewhere

OpenConcept: Building Community on Drupal.org

Planet Drupal - Wed, 28/05/2014 - 16:53

Yesterday we saw profile images get into Drupal.org. This has gotten a bunch of positive feedback as it both modernizes the look of the community and addresses a style bug that goes back to 2010 when the last design (Bluecheese) was applied to the site.  More importantly though it puts a face on the contributors of the d.o community -- we are no longer just anonymous blue nicknames!

The styling changes on Drupal.org are a nice improvement, mostly because it is a regular reminder about the individuals who are pushing to make Drupal better.  Hopefully when we see the images of people's faces they will be more inclined to be listen to others' opinions, be respectful of differences and work to build common solutions, or as @webchick says "Avatars also pressure people to behave more like human beings."

 

The Backstory

Leisa Reichelt had worked with designer Mark Boulton on the 2010 redesign of Drupal.org, but as is often the case, there wasn't time/budget to consider everything. After the new design was implemented Leisa engaged with the Drupal community to create what she called the Prairie Initiative. 

I remember her Core Conversations presentation at DrupalCon Chicago where she talked about how to design a better User Experience on Drupal.org. She did a great job relating it to Frank Lloyd Wright's Prairie School of architecture which saught to build an intentionally American approach to architecture. She challenged the Drupal community to step up to the challenge of building an experience that facilitated the community we wanted. I really enjoyed that DrupalCon, and the keynotes by Clay Shirky and Jared Spool both seemed to drive home the importance of UX on Drupal.org. 

 

Social Engineering

Shortly after that DrupalCon, Leisa set up the Prairie Initiative group and posted a wireframe for a re-envisioned Issue Queue page. Now obviously, creating a wireframe is easier than implementing it, and for about two years there was a lot of interest in this subject, lots of great discussions, but sadly we're really quite a long way from what was envisioned back in 2011. Nobody expected the upgrade to Drupal 7 to take as long as it did, and sadly the momentum behind this initiative died out without seeing much beyond the discussion. 

This is really barely even the tip of the iceberg when looking at functionality and design changes that could have a role in influencing community behavior.  We barely know our own community of 1 million members let alone the millions that hit all of the *.drupal.org sites every month. We really understand very little about how our community has produced people like Dave Reid, Alex Pott or Lee Rowlands, let alone how we can help sustain their contributions. The Internet keeps changing, software will always have bugs, and there just aren't enough hours in the day for the existing developers to keep up with the demands on their time.  That being said, we still don't have a scalable approach to onboard new contributors.

 

Drupal 7 in 2014

I have spent a bunch of time on Drupal.org looking at how to improve user experience this year. Mostly it was about nudging existing issues along, but building effective online communities is already a very large field and it is growing quickly.  To thrive these days, I think any online community needs to invest heavily in eliminating barriers to participation, providing an enjoyable and rewarding experience, and ensuring that users benefit enough through being involved to keep coming back. 

I've also been concerned with the the state of contributed modules and themes in Drupal 7. At this stage in this release's life cycle we should all be benefitting from the most robust and well supported assortment of modules, but sadly even as we reach over 800,000 sites using Core, we seem to lack adequeate resources to maintain Drupal 7 Contrib modules.

 

Process Problems

A big part of the problem is that we use the same process to improve Core's security as we do to determine how we would add images to landing pages. We've got this one process and often it seems we are running into bottlenecks because it's unclear who has the responsibility and authority to actually implement changes on Drupal.org.

Recently I added an issue to try to make Drupal.org more fun. Most effective community sites use humour to engage with their members.  Github uses this very effectively from their choice of mascot to their 404 pages and to their online help. Without incredible interventions from senior community members, it's unlikely we'll see changes like this to Drupal.org.  What we're likely to get is an interface that is at best generic and at worse terse and condescending.  It's something that is easy to dismiss in the range of important content issues, but that tone discourages participation.

People will keep coming back to a virtual community if they have fun there, feel like they belong and get feedback that helps them feel that they are getting better. With a vast global community of users, that's only going to happen if there is a strong intentional effort to shape engagement through Drupal.org.

 

Looking Ahead

The Drupal community is big enough that you'll never please everyone. Even with something as benign as avatars there has been a lot of debate, and now that it is rolled out, we're going to see more. We should strive to have agreement about values and tone for our sites, but we can't afford to wait until we have concensus around a perfect solution.

I do think that there are some things that the Drupal community is going to need to delegate to a properly resourced individual, a working group or to the Drupal Association. We need to see vast improvements in the user experience on Drupal.org.  To be clear, I'm not talking about a new design, what we need is a new strategy for engaging with the Drupal community through our websites.

Topic: 
Categories: Elsewhere

Hideki Yamane: no /run/systemd/private

Planet Debian - Wed, 28/05/2014 - 16:33
Setting up dbus (1.8.2-1) ...
Failed to get D-Bus connection: Failed to connect to socket /run/systemd/private: Connection refused
Failed to get D-Bus connection: Failed to connect to socket /run/systemd/private: Connection refused
Failed to get D-Bus connection: Failed to connect to socket /run/systemd/private: Connection refused
Failed to get D-Bus connection: Failed to connect to socket /run/systemd/private: Connection refused
invoke-rc.d: initscript dbus, action "start" failed.
dpkg: error processing package dbus (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
dbus
Error: Timeout was reached
E: Sub-process /usr/bin/dpkg returned an error code (1)and there is no  /run/systemd/private file :-(
After reboot it, it has been created and able to upgrade. Hmm... how I can avoid this systemd related error?
Categories: Elsewhere

Acquia: The killer Acquia Cloud feature you need to start using right now

Planet Drupal - Wed, 28/05/2014 - 15:56

Cross-posted with permission from Third and Grove

Categories: Elsewhere

Holger Levsen: 20140528-expired-my-1024bit-gpg-key

Planet Debian - Wed, 28/05/2014 - 15:34
Expiring my old 1024 bit GPG key

Today I have expired my old 1024 bit GPG, 0xAC583520, ten years and a bit after creating it, as part of my journey to become a DD. Since 2010 I've been using 0x069AAA1C instead, but up until now I haven't had done anything about the old key, also because revoking a GPG key is a permanent and unrevocable action. Thanks to an unnamed friend in Berlin who gave me the idea I can expire a key too, which basically has the same effect, except that is's possible to undo...

Categories: Elsewhere

Code Karate: Drupal 7 Weather Module

Planet Drupal - Wed, 28/05/2014 - 13:27

In this episode, you are introduced to the Drupal 7 Weather Module. This first video covers the basics of the module without using integrations with any additional modules.

Categories: Elsewhere

OhTheHugeManatee: Drupal Superheroes: ASSEMBLE!

Planet Drupal - Wed, 28/05/2014 - 12:44

Regular Drupalcon attendees know that the opening pre-keynote session is one of the highlights of the con. That’s the session where we welcome everyone to the con with stupid jokes, some well known Drupalists, and a lot of fun. This year is going to be especially good – and we need your help!

The evil Lord Over Engineering is threatening to delay the release of the CMS, which we need to save the world! The only way to stop him is to assemble the greatest force of Drupal superheroes ever assembled! Can the heroes save the day? Can we manage to make the final git push? You’ll have to be there to find out!

“If you only get up early once during DrupalCon, this is the morning to do it. And hey, at least you’ll get better seats for my keynote right after.” — Dries

In Prague we had the Drupal Opera, with solos sung by Gabor Hojtsy. In Portland we had the Drupal Game show, including Doug Vann’s amazing beatbox of the Tetris theme. In Munich, we taught the world to yodel and pour good German beer. Don’t miss out this year! The fun is just getting started!

If you want to participate onstage, you can go to Robert Douglass’ blog and sign up with our superhero/villain application form. But even if you just want to party from your comfy chair in the audience, costumes are encouraged! So get your best superhero costume together, and I’ll see you at the pre-keynote!

Categories: Elsewhere

Tanguy Ortolo: GNU/Linux graphic sessions: allowing computer suspend and disabling a monitor

Planet Debian - Wed, 28/05/2014 - 11:55
Allowing computer suspend

Major desktop environments such as Xfce or KDE have a built-in computer suspend feature, but when you use a lighter alternative, things are a bit more complicated, because basically: only root can suspend the computer. Possible solutions include:

  • using sudo to allow members of a given group to run a suspend command, e.g. pm-suspend as root;
  • using a D-Bus UPower thingy, which communicates with a running daemon upowerd: $ dbus-send --system --print-reply \ --dest='org.freedesktop.UPower' \ /org/freedesktop/UPower org.freedesktop.UPower.Suspend

With recent updates of the related Debian packages — no idea of which one exactly — the latter solution may not work any more, in which case it will only return the following error:

Error org.freedesktop.UPower.GeneralError: not authorized

It appears that this error is linked to ConsoleKit, a part of all this modern *Kit gizmo pile. If you are in this case, try prefixing your session launcher with the undocumented dark magic call ck-launch-session. For instance, this is what I have in my .xsession to launch my window manager i3:

exec ck-launch-session i3

Note: I do not know what ck-launch-session does exactly, why it is needed, and I do not want to know. To me, all that WhatsitKit pile is just some opaque, under-documented — as in: no man page — crap, that no one but their author really understand, designed to solve theoretical problems no one really cares about — like: how to allow locally connected users to use the sound card while forbidding it to remote users — while creating new issues such as this one. This stuff is too complex and under-documented for me to dive into it, so if it does not work out of the box, it is just some crap that gets in my way to using my computer as I wish.

Disabling a monitor

In some configurations, you have two monitors and want to disable one. For instance, in addition to my LCD monitor, I have a projector which I only use for movies. According to xorg.conf's man page, it can be disabled this way:

Section "Device" Identifier "Internal graphic card" Option "Monitor-DVI" "LCD Monitor" Option "Monitor-VGA" "Projector" EndSection Section "Monitor" Identifier "LCD Monitor" EndSection Section "Monitor" Identifier "Projector" Option "Enable" "false" EndSection

Except that does not work, because contrary to what the man page says the real option to use is not Enable but Disable! So here is the correct configuration to disable that monitor at start-up:

Section "Device" Identifier "Internal graphic card" Option "Monitor-DVI" "LCD Monitor" Option "Monitor-VGA" "Projector" EndSection Section "Monitor" Identifier "LCD Monitor" EndSection Section "Monitor" Identifier "Projector" Option "Disable" "true" EndSection

Note: yes, I will send a bug report with a patch against xorg.conf's man page.

Categories: Elsewhere

Mogdesign: 2/3 Using custom fields in the feed/csv

Planet Drupal - Wed, 28/05/2014 - 11:00

This is part 2 of Aegir mini-series.

Categories: Elsewhere

Drupal core announcements: Rerolling patches for PSR-4

Planet Drupal - Wed, 28/05/2014 - 08:01

All Drupal 8 core module code was recently converted to the PSR-4 standard. This issue moved hundreds of files and so many patches will need rerolls. You can update patches safely with the following workflow (provided by @donquixote):

  1. Ensure you have the latest 8.x HEAD in your Drupal 8 repository: git pull origin 8.x
  2. git checkout -b tmp 00339b3d to create a new a new (temporary) branch from the Drupal 8 commit hash before the patch for Issue #2247991 i=was committed.
  3. git apply --index the patch and commit to the new branch.
  4. git rebase 8.x -- This should actually preserve all the local changes to existing files, because git understands if a file has been moved.
  5. Run php core/scripts/switch-psr4.sh and commit the changes. This is for files that were added in the patch or local branch. Remember, this script will add and remove files without udpating the git index, so you will need to add and remove files with git add.
  6. git diff 8.x to produce a new version of the patch.
  7. Upload the new patch to the issue and set the issue "Needs review".

As always, be sure to review your updated patch carefully for any errors.

Categories: Elsewhere

Pages

Subscribe to jfhovinne aggregator - Elsewhere