k88hudson

/* First, install dependencies:
   npm install webpack babel-loader babel-core babel-preset-react --save-dev 
   npm install react react-dom --save
   Note: babel dependencies are not needed if you aren't using jsx)
*/


// webpack.config.js
//   Note: This assumes a "main.js" file in a src/ directory, and outputs "main.bundle.js" to a dist/ directory

0XDE57

ABOUT

about:config settings to harden the Firefox browser. Privacy and performance enhancements.
To change these settings type 'about:config' in the url bar. Then search the setting you would like to change and modify the value. Some settings may break certain websites from functioning and rendering normally. Some settings may also make firefox unstable. I am not liable for any damages/loss of data.

Not all these changes are necessary and will be dependent upon your usage and hardware. Do some research on settings if you don't understand what they do. These settings are best combined with your standard privacy extensions (HTTPS Everywhere No longer required: Enable HTTPS-Only Mode, NoScript/Request Policy, uBlock origin, agent spoofing, Privacy Badger etc), and all plugins set to "Ask To Activate".

rik

On the phone:
1) Go in Settings > Developer (at the bottom)
1-a) If Settings > Developer doesn't exist, enable it in Settings > Information > More information > Developer Menu
2) Debugging via USB > Select "ADB and devtools"

On your computer:
3) Download https://github.com/mozilla/buddyup/archive/master.zip (from https://github.com/mozilla/buddyup, "download zip" in the bottom right)
4) Unzip
5) Plug in your phone

willkg

#!/usr/bin/env python
"""
james.py - Chief CLI.

USAGE: james.py ENV REF
  ENV - Environment defined in the config file to deploy to.
  REF - A git reference (like a SHA) to deploy.

Config: james.ini in the current directory should be an ini file with
one section per environment. Each environment should have a

mythmon

#!/usr/bin/env python
"""
james.py - Chief CLI.

USAGE: james.py ENV REF
  ENV - Environment defined in the config file to deploy to.
  REF - A git reference (like a SHA) to deploy.

Config: james.ini in the current directory should be an ini file with
one section per environment. Each environment should have a

jdm

diff --git a/vendor/src/django-mobility b/vendor/src/django-mobility
[jdm@rosencrantz kitsune]$ git diff
diff --git a/kitsune/questions/models.py b/kitsune/questions/models.py
index c4a6d70..20f0150 100755
--- a/kitsune/questions/models.py
+++ b/kitsune/questions/models.py
@@ -49,6 +49,15 @@ log = logging.getLogger('k.questions')
 CACHE_TIMEOUT = 10800  # 3 hours
 
 

shlomibabluki

# coding=UTF-8
from __future__ import division
import re

# This is a naive text summarization algorithm
# Created by Shlomi Babluki
# April, 2013


class SummaryTool(object):

mythmon

#!/bin/bash

function remote_by_name() {
    name=$1

    remote_line=$(git remote -v | grep push | grep $name)

    if [[ -z $remote_line ]]; then
        echo "Error: remote '$name' not found."
        exit 1

andymckay

for file in `git diff-tree --no-commit-id --name-only -r HEAD | sort | uniq`
    do
        if [ ${file: -3} == ".py" ]
        then
         flake8 --ignore=E121,E123,E124,E125,E126,E127,E128 $file
        fi
        if [ ${file: -3} == ".js" ]
        then
         jshint $file
        fi

mythmon

Problem statement

Sprints work pretty well, but they can get messy when contributors start being involved, or when bugs overflow the time boundaries of a sprint (ie a bug was started near the end of a sprint, and isn't finished at the end of the sprint). Sometimes sprints can feel like "mini waterfalls". On the other hand, sprints have the advantage of letting PMs easily define what work should be done, and helping this information flow from PMs to developers. They also help timebox projects, so that we can say "this will be done during this two week cycle. This predictability is important. Surprised estimations are teh suck. It isn't fair to ask a developer to make an estimate on something that they haven't worked on before without time to do some research.

Goals:

• Reduce dependency on a fixed two week cycle.
• Maintain a level of predictability, within the error margins of estimation.
• Keep the amount of metawork to a minimum.
• Reduce the amount of "surprise estimations".