carljm

export GEM_HOME=$VIRTUAL_ENV/rubygems
export GEM_PATH=

export PATH=$VIRTUAL_ENV/rubygems/bin:$PATH

sebleier

HenrikJoreteg

"""
Straight Include template tag by @HenrikJoreteg

Django templates don't give us any way to escape template tags.

So if you ever need to include client side templates for ICanHaz.js (or anything else that
may confuse django's templating engine) You can is this little snippet.

Just use it as you would a normal {% include %} tag. It just won't process the included text.

toastdriven

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>author</key>
	<string>Daniel Lindsley</string>
	<key>name</key>
	<string>My Twilight</string>
	<key>settings</key>
	<array>

jnoller

Internal Communication DRAFT

• Use asynchronous communication when possible (issues and email instead of chat), issues are preferred over email, email is preferred over chat, announcements happen via email or team standup, and people should be able to do their work without getting interrupted by chat.
  • More importantly, a verbal or chat record does not spread communication widely and can vary based the person delivering the message (bias) or other tribal interpretation. A written record is always critical when it comes to questions, strategy and decisions. When decisions or information is ad-hoc is reinforces the idea that people are treated unequally, do not have a voice and are kept in the dark.
• It is very OK to ask as many questions as you have, but ask them so many people can answer them and many people see the answer (so use issues or public chat channels instead of private messages or one-on-one emails) and make sure you try to document the answers.
• If applicable, use github to track

idan

[
    {
        "keys": ["super+alt+shift+5"],
        "command": "set_layout",
        "caption" : "1-2 Grid",
        "args":
        {
            "cols": [0.0, 0.5, 1.0],
            "rows": [0.0, 0.5, 1.0],
            "cells":

jleclanche

Moved here:

https://github.com/HearthSim/django-intenumfield

SaraDGore

Ideas for DjangoCon US talks

• How to be an ally

• An accessibility talk that goes beyond visual or mobility impairment

• How to bridge from introductory materials to the skills needed as a junior developer

• Recruiting, hiring, and interviewing skills

jcroft

// REQUIRED VARS. Defaults to a 950px wide, 24-column grid that has 30px wide units and 10px wide
// gutters. If you do the fluid grid, then this 950/24/30/10px size will become the maximum size.
$grid_type: fixed !default
$grid_columns: 24 !default
$grid_column_width: 30 !default
$grid_gutter_width: 10 !default

// GENERATED VARS. You can ignore these.
$grid_full_width: $grid_columns * $grid_column_width + $grid_columns * $grid_gutter_width - $grid_gutter_width
$grid_column_width_percent: ($grid_column_width / $grid_full_width * 100) * 1%

alexwybraniec

sudo apt-get update
sudo apt-get install munin-plugins-extra
cd  /etc/munin/plugins
sudo ln -snf /usr/share/munin/plugins/memcached_ memcached_bytes
sudo ln -snf /usr/share/munin/plugins/memcached_ memcached_counters
sudo ln -snf /usr/share/munin/plugins/memcached_ memcached_rates
sudo aptitude install libcache-memcached-perl 
sudo /etc/init.d/munin-node restart
sudo tail -f /var/log/munin/munin-node.log