This weekend, Trinity Gay was shot, accidentally, as she was hanging out with her friends in a South Broadway restaurant where my daughter used to hang out with her friends. Several people were arguing in the parking lot, and traded shots. A bullet went stray and stuck Trinity in the neck, killing her.

Trinity was a student at Lafayette High School, where one of my kids is a student, and another recently graduated. Lafayette brought in grief counselors, and is having a memorial tonight after the football game.

These are the right things to do, because Trinity was part of the school community. She had friends and family who will grieve her passing, and need to do this in community.

Trinity was 15. She was a promising track star. Her father is an Olympic sprinter.

On September 26th, Jordan Perkins, another Lafayette student, was driving with three of his friends, and was involved in a car crash, in which he was killed. All three of his friends have serious injuries. Jordan was 15, a Freshman, and was on the football team.

Lafayette High School did not send email home to parents about this incident. They did not bring in grief counselors, nor did they have any kind of a memorial for Jordan. Presumably this is because the car that Jordan was driving was stolen, and had weapons and drug paraphernalia in the trunk, and Jordan is rumored to have been high and possibly drunk at the time of the crash. Jordan can be said, objectively, to have reaped the rewards of his own decisions.

But, here’s the thing. The Fayette County Schools’ motto is “it’s all about kids”. Jordan was a kid. He did something stupid, and he died as a result. His friends were hurt with him. But pretending that it didn’t happen – not giving Jordan’s friends and acquaintances a space to struggle with the senselessness of it, a place to grieve, a time to remember him – communicates that he’s less important because he made a mistake. It tells other kids that are on this same trajectory that their struggles are less important than those of a beautiful track star with lots of friends and a famous dad.

Please don’t hear me saying that the school should have done less for Trinity. My heart is broken for her family, her friends, and even the kids who only knew her from seeing her passing in the hall. If only we could do more.

But they should also do as much – exactly the same things – for Jordan. Because it’s all about kids. And he was another kid, with friends, with acquaintances, with family. And now he’s gone, too.

I’ve attached the big red button to the raspberry Echo, so the wires are all hidden underneath the shelf now. Just need to get some mounting hardware for the pi. 

At LinuxCon, I won a Raspberry Pi in a raffle, and someone suggested that I make an Amazon Echo with it.

There are two sets of instructions for making an Echo from a Pi.

There’s the set from Amazon, at https://github.com/alexa/alexa-avs-raspberry-pi/blob/master/README.md which is about 93 steps, cleverly disguised as 12 steps, and looked way too much work.

Then there’s Sam Machin’s version, at https://github.com/sammachin/AlexaPi which is one step. Sort of.

And there’s a YouTube video – HERE – which every article about this topic links to. The video, while helpful, skips several important steps, and uses the word “obviously” just often enough to make me feel like a drooling idiot. ‘Cause it’s not obvious, that’s why.

However, with persistence, and a lot of guess work, I got it working.

The instructions go something like this, with some of the details filled in.

Obtain a Raspberry Pi. This is pretty much the only step that is actually obvious.

Attach necessary hardware. Plug a speaker into the headphone jack, and a USB mic into one of the USB ports. I used my Samson Go Mic, and a little speaker I wasn’t using. You’ll need to use a powered (amplified) speaker, if you want to actually hear anything. Finally, you need to attach a push-button across two of the pins on the Raspberry Pi board. The pins are BPIO 18 and ground. Pin GPIO 18 is the sixth pin from the top right, when you hold the board with the pins to your right. Ground is the bottom left pin. There’s a diagram of the pins below, as well as a photo of mine.

Note that I soldered the wires to the pins, but there are also slide-on pin jumpers that you can acquire to do this without soldering. I just didn’t have any handy.

You can use any simple electronics kit pushbutton. I got mine at Radio Shack – you know, when there used to be Radio Shacks. 🙁

Register for an Amazon Echo developer account. You’ll do this at https://developer.amazon.com/edw/home.html#/ and this will give you access to the tools necessary to write your own Alexa apps, as well as to register your Raspberry Pi Echo.  Now, go to the 3:44 mark in the video and follow his instructions for registering your device. Give it a name you will remember – I called mine AlexaPi, but anything’s fine. Once it’s registered, leave this browser tab open. You’ll need it below.

Download Noobs – the starter Pi boot image, from https://www.raspberrypi.org/downloads/noobs/ and unpack that zip file onto a micro SD card that is freshly formatted with a FAT filesystem.

Boot the Pi from that card, and follow the instructions to install Raspbian.

Update Raspbian, and install necessary things. SSH to your newly running Pi (your username is ‘pi’, and your password is ‘raspberry’), and run the following commands.

sudo apt-get update
sudo apt-get install git

Now, obtain and run Sam’s code:

git clone https://github.com/sammachin/AlexaPi.git
cd AlexaPi
./setup.sh

This script will walk you through the installation process, and will require information from the Amazon developer website that you have open in your browser. You’ll need the name you gave your device, and three long hex strings (numbers and letters) which you’ll paste into the script inputs. The video says that you’ll need to edit a configuration file, but that’s no longer the case, so I presume that there used to be a bug in the script that is now fixed.

The script will tell you to reboot the Pi. Do that.

When it comes back up, it will be running the Alexa service. You press the button to talk to it, and release to tell it you’re done talking. Ask it for the weather. (You can tell your new Echo where you live in the phone app, so that it gives you your local weather, rather than Seattle, which appears to be the default location.)

This is a picture of the finished product.

My plan is to attach a nicer button, like, say, one of the Staples “that was easy” buttons, if I can get one back from the kids, and then put the rest of this stuff in a more attractive container. But everything works as desired, with one exception. Turns out that the Raspberry Echo doesn’t have access to the Amazon music services, so you can’t actually play music from Prime Music, Pandora, or other music services that are available from the “real” Echo. It’s still a very useful, and cheap, alternative to buying an actual Echo. I did all of this with parts that I already had laying around, and a Pi that I won in a raffle, so it was essentially “free”. But if I had to guess, I’d say you could do the whole project for under $75, including the Pi, a USB mic, and a speaker. Perhaps a little more, depending on what mic and speaker you go with.

If I missed any steps, please let me know, so that I can update the article. Thanks.

Last week I attended LinuxCon North America in Toronto, where I represented the RDO project in the Red Hat booth, and also gave two presentations.

My first presentation – Introduction to OpenStack – was attended by about 50 people and was, as the name suggests, an introduction to OpenStack. I talked about the project’s history, the way that the Foundation works, and the software itself.

My second presentation was titled ‘RTFM? Write a better FM‘, and  as about documentation, end-user support, and treating customers  with compassion and respect. This talk was also well received, however, I always get the sense that people are only going to attend a talk like this if they are already predisposed to the message. I’ve been giving this talk, in one form or another, for most of 10 years. However, the last 3 or 4 times I’ve given it, I’ve rewritten it each time. I have so much to say on the topic that I can’t fit it all into an hour, so I emphasize different things each time.

The LinuxCon audience is very diverse, in terms of technology interests and depth of knowledge. So it was gratifying to have so many good conversations after my OpenStack talk, and a few at the booth, about what people are doing with OpenStack.

In the hours that I worked the Red Hat booth, we had very few OpenStack/RDO questions. Most of the conversations were around containers, or people that were looking for jobs at Red Hat. (Yes, we’re hiring!) The LinuxCon audience is very diverse, in terms of technology interests.

Photos from LinuxCon are HERE.

My presentations are HERE and HERE.

It’s also worth mentioning that I have awesome coworkers. It’s always a pleasure to do events with them. They work hard, and they also know how to have fun, and I’m very lucky to work on such an amazing team.

I started reading Wizard, by John Varley. Unfortunately, about 2 chapters in, I suddenly realized that it’s the second in a trilogy – the Gaea Trilogy. The first book is Titan, and the third is Demon.

I’ve set this aside for the moment, and am now reading The Name Of the Wind. I’ll get back to Gaea soon. ish.

​It’s the same story the crow told me; it’s the only one he knows

Like the morning sun you come and like the wind you go
Ain’t no time to hate, barely time to wait
Wo, oh, what I want to know, where does the time go? 

Uncle John’s Band, the Grateful Dead

We’re first in line for Rhi’s student id card. The last 18 years have gone by in a flash and my baby girl is off on her own.

We drove 1200 miles listening to The Grateful Dead and talking about everything. It was wonderful. And now, just a few hours left with her. 

What a long strange trip it’s been.