What’s the difference between voice and tone? Think of it this way: You have the same voice all the time, but your tone changes. You might use one tone when you’re out to dinner with your closest friends, and a different tone when you’re in a meeting with your boss.

Your tone also changes depending on the emotional state of the person you’re addressing. You wouldn’t want to use the same tone of voice with someone who’s scared or upset as you would with someone who’s laughing.

Voice and Tone | MailChimp Content Style Guide

Call me naive, but I refuse to sit back and let our digital culture fade to corporate beige. That’s not a digital world I want to be a part of, and I’m going to fight every step of the way to fuck up the plan.
[…] those of us who are willing to stick our necks out […] have an advantage […] that the machines and machine-thinkers will always be reluctant to admit:

Humans are unpredictable mushy bags of irrationality and emotion.

Travis Gertz, Design Machines

WordPress.org and Git(Hub)

I’ve just come across this comment from Samuel Wood aka Otto42 at the GitHub Updater repo regarding the WordPress.org plugin repository and its potential Git(Hub) support. Thought I’d post it here, more for personal archiving than anything else.

After pointing out how it’s actually possible to have an extra branch for releases in a GitHub repo and dcommit a release from there to the plugins repo on WordPress.org, Otto says:

The problem with git is that honestly, it keeps too much data. People commit too often, as weird as that sounds. And while lots of committing for development purposes is fine, the plugin repository is a release repository. We don’t need the commit history of every little change you make to your plugin. Every commit causes us to parse the plugin, build zip files, send update notifications if needed. There’s a lot of activity that happens on commits.[…]

WordPress.org provides release and hosting systems, not public repositories to be used as development environments.

I think that answer may be valuable for many developers who rather use Git than SVN and were wondering why WordPress.org would stick to SVN. Makes senses, imo, when explained like that.