Code conventions

All languages

• Don't use more complicated constructs like ternary operators
• Keep functions short and simple.

Python

We follow PEP-8.

PHP

• K&R, 1TBS variant, including for functions
• 4 spaces as indent
• The keywords true, false and null must be in lower case.

Shell scripts

UNIX agnosticism:

• Don't assume absolue path, use `#!/usr/bin/env bash` and not `#!/bin/bash` (it could be elsewhere on BSD or Solaris)
• Use `sh` as must as possible, try to avoid `bash`, document exceptions rationale in your commits

Whitespaces:

• One whitespace line between shebang and actual content
• Indent with tabulations

File names:

• We use hyphens (-) as separators, not underscores or camelcase.
• Filename should start by a verb if it performs an action
• Don't use .sh extensions (sometimes you'll see them on Phabricator pastes' titles, but it has been added there, so Phab knows shell syntax highlighting should be used)