Selena Deckelmann selenamarie

Turn virtualization ON in the BIOS
http://sharadchhetri.com/2014/01/23/this-kernel-requires-an-x86-64-cpu-but-only-detected-an-i686-cpu/
various vagrant issues in the event you need it: https://github.com/mitchellh/vagrant/wiki/%60vagrant-up%60-hangs-at-%22Waiting-for-VM-to-boot.-This-can-take-a-few-minutes%22#resolve-it
Turn secureboot off in the BIOS
http://docs.fedoraproject.org/en-US/Fedora/18/html/UEFI_Secure_Boot_Guide/ch02s02.html
Use unetbootin to fetch Saucy Ubuntu, install
http://unetbootin.sourceforge.net/
Upgrade to Trusty (base install of Fedora and Trusty failed initially)
Install ppa for firefox-trunk
This is what got me to upgrade from saucy to trusty (even though saucy is out of support.. lol)

RVLVVR is a chat client/server that enables GPG-encrypted messaging. It uses keybase.io and is a distributed application, using rvlvvr.net as a hub for discoverability and message passing.

Client code is: https://github.com/rvlvvr/rvlvvr-client

ednapiranha's post: http://ednapiranha.com/2014/distribute-everything/

can post images and videos by just putting the URL in the message
need to keybase track anyone you want to talk with

During the PyLadies lunch here at PyCon, I heard 5 people stand up and say that they would not have given a talk if an individual (in many cases Jessica McKellar) hadn't pestered them repeatedly to give a talk. I saw later that someone else had heard this from 10+ people at the lunch.

Increasing speaker diversity is both about sending emails "to the right mailing lists" but it is also largely dependent on individuals reaching out to new (and veteran) speakers to get them to submit talks.

So - a lot of this work has to happen on multiple fronts at the same time - the CFPs need to go out to lots of lists, and individuals need to reach out to lots of individuals.

The only way I have seen this be consistently successful is if many people on the conference committee are all making individual requests to speakers, and the people making the requests are trusted by the talk submitters. It's a systemic issue involving visibility, trust, mentorship in general, talk submission mentoring, and mentorship of talk c

Keybase proof

I hereby claim:

I am selenamarie on github.
I am selenamarie (https://keybase.io/selenamarie) on keybase.
I have a public key whose fingerprint is 27DF C0BB 7DD6 5ED2 EA12 E223 C34E 5747 E23D D677

To claim this, I am signing this object:

	selena@taiping:decision #2004 11:57 ♥: nvm install 4.0.0
	bash: [: 000000000400000000000000000000: integer expression expected
	^C
	selena@taiping:decision #2005 11:57 😱: nvm install 4.0
	######################################################################## 100.0%
	Checksums empty
	Now using node v4.0.0
	selena@taiping:decision #2006 11:58 ♥: nvm install 4
	######################################################################## 100.0%
	Checksums empty

	* how would you write a pure restful service in django from scratch?
	https://gist.github.com/peterbe/4337d96d0afd53505cbb

	from django import http

	def meaningoflife(request):
	return http.HttpResponse(json.dump({'number': 42}}, mimetype="application/json")

	* where in config/setup do you put this information


	# start dataservice_app.py

	socorro/dataservice/dataservice_app.py

	# insert these into postgresql:
	insert into bugs values (1, 'done', 'good', 'stuff');
	insert into bug_associations values (1, 'a signature');

	# test POST

	-- this output is interesting :)
	SELECT json_object_field_text(ucm.rewrite, 'rewrite_to') as release_channel,
	json_array_elements(ucm.rewrite->'BuildID') as buildid, -- yeah this is not good here :D
	product_versions.product_version_id,
	trim(both '"' from (ucm.rewrite->'Version')::text) as version_string,
	product_versions.version_string
	FROM
	product_productid_map ppm
	JOIN update_channel_map ucm USING (productid)
	JOIN product_versions ON ppm.product_name = product_versions.product_name


	from crashstats.dataservice.models import magic
	globals().update(magic)
	import sys