cczona

## NOTE: quit Chrome first

# use native print dialog
defaults write com.google.Chrome DisablePrintPreview -boolean true 

# use Chrome's print dialog
defaults write com.google.Chrome DisablePrintPreview -boolean false

cczona

Tech Initiatives for marginalized groups

##mailinglists

• devchix
• tech lady mafia
• Systers

##list of speakers

cczona

[ZeroVM talk proposals to OpenStack Summit Paris 2014](https://www.openstack.org/vote-paris/SearchForm?Search=ZeroVM)


	[2014-08-05] "ZeroVM Architecture and ZVM Runtime (ZRT)" by Ryan McKinney at University of Texas San Antonio Cloud & Big Data Laboratory

[slides (work in progress)](http://www.slideshare.net/sgt_mac/zero-vm-architecture)

 
 
	[2014-08-01] "Changing the world with ZeroVM and Swift" Jakub Krajcovic at PyConAU OpenStack Miniconf

cczona

Hi, I'm the community manager of ZeroVM. Good question. Background info on NaCl (which is what ZeroVM relies on) briefly mentions GHC https://developer.chrome.com/native-client Some issues ppl have raised re porting GHC to NaCl:

2013: https://ghc.haskell.org/trac/ghc/ticket/8206

2012: http://www.reddit.com/r/haskell/comments/ppdgq/gsoc_2012_project_proposal_ghci_in_the_web_browser/

Our team are happy to help you out with more details. All of the core engineers hang out on #zerovm (freenode) and http://groups.google.com/forum/#!forum/zerovm so either is a good place to You're also welcome to ping me at carina.zona@rackspace.com

cczona

**NOTE:** "*" indicates funds were increased through full or partial donation matching.

# Tech conferences that have successfully used their registration page to do substantial fundraising for expanding diversity:

* [$10] PyCon 2014 (PyLadies) 

* Steel City Ruby (attendee travel fund) https://twitter.com/ashedryden/status/282572950366986240

* [$10, pre-checked box] Fluent Conf 2014 (Women Who Code) https://twitter.com/suzaxtell/status/488709539777105920*

cczona

Some excellent examples to draw upon when developing a CFP. Highlights include communicating to proposers:

  * conference's distictive character
  * suggested or preferred topics
  * logistics such as where, when, audience size, etc
  * speaker package such as travel, honorarium, etc
  * evalution process
  * timelines
  * assistance available for new speakers
  * mutual expectations

cczona

Greg Wilson (@gvwilson)
“Surprised to see @CallbackWomen promoting @TRUCEConf - see http://jacobian.org/writing/truceconf/ … for reasons”

TRUCEConf (‏@TRUCEConf)
“Quite honestly a lot of changes have been made since that post. See http://truceconf.com/2013/11/10/a-few-changes-to-truceconf/ & http://truceconf.com/2013/11/17/clearing-a-few-things-up/ “

cczona

source 'https://rubygems.org'

# Bundle edge Rails instead: gem 'rails', github: 'rails/rails'
ruby '2.1.0'
gem 'rails', '4.0.2'


# Use SCSS for stylesheets
gem 'sass-rails', '~> 4.0.0'

cczona

source 'https://rubygems.org'

# Bundle edge Rails instead: gem 'rails', github: 'rails/rails'
ruby '2.0.1'
gem 'rails', '4.0.2'


# Use SCSS for stylesheets
gem 'sass-rails', '~> 4.0.0'

cczona

Everyday Sins of Internationalization
=========


When we think of internationalization, we're drawn to technical aspects. Are we using the right character set? Can this wording be translated? And what about content negotiation? Ugh, such a pain in the ass.

Many of the conversations wind up being deferred for later -- for the day when we're preparing to expand into another country. Meanwhile, we're unknowingly committing everyday sins. Users, please forgive us.

Cultures vary. People within them do too. Porting out local certainties can set a course to epic fail. There are easy opportunities we're missing out on, right now.