forked from cappert/2011.rulu.eu
-
Notifications
You must be signed in to change notification settings - Fork 0
/
speakers.html
536 lines (486 loc) · 31.4 KB
/
speakers.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
<!doctype html>
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<meta charset="utf-8">
<meta http-equiv="x-ua-compatible" content="IE=edge">
<title>Ruby Lugdunum - 2011</title>
<link href="stylesheets/content.css" media="screen" rel="stylesheet" type="text/css">
<script src="https://ajax.googleapis.com/ajax/libs/jquery/1.6.0/jquery.min.js" type="text/javascript"></script>
<script src="https://ajax.googleapis.com/ajax/libs/jqueryui/1.8.12/jquery-ui.min.js" type="text/javascript"></script>
<script src="javascripts/rails.js" type="text/javascript"></script>
<script src="javascripts/application.js" type="text/javascript"></script>
</head>
<body>
<div class="banner_1">
<div class="center clearfix">
<header>
<a href="/"><img alt="ruby-lugdunum-logo" src="images/ruby-lugdunum-logo.png" class="logo"></a>
<div class="logo_text"></div>
<h1>
<span class="red">Ruby Lugdunum</span>
</h1>
<p id="organized-by"><small>Organized by <a href="http://lyonrb.fr">Lyon.rb</a></small></p>
<h2>
25-26 June 2011
</h2>
<h3>
Lyon, France
</h3>
<nav>
<ul>
<li>
<a href="/" >
HOME
</a>
</li>
<li>
<a href="/speakers" class='current' >
SPEAKERS
</a>
</li>
<li>
<a href="/schedule" >
SCHEDULE
</a>
</li>
<li>
<a href="/venue" >
VENUE
</a>
</li>
<li>
<a href="/sponsors" >
SPONSORS
</a>
</li>
</ul>
</nav>
<!--<div class="banner">
<img alt="Banner" src="images/banner.png">
</div>-->
</header>
</div>
</div>
<div class="banner_2">
<div class="center clearfix">
<div class="column_1">
<div class="block">
<h2>Speakers</h2>
</div>
<script>
$(function() {
$( "#tabs" ).tabs();
});
$(document).ready(function() {
if($("#tabs") && document.location.hash){
$(window).scrollTop(0);
}
});
</script>
<div id="speakers-tabs">
<div id="tabs">
<ul>
<li><a href="#blake-mizerany" class="tab"><h3>Blake Mizerany</h3></a></li>
<li><a href="#bruno-michel" class="tab"><h3>Bruno Michel</h3></a></li>
<li><a href="#elise-huard" class="tab"><h3>Élise Huard</h3></a></li>
<li><a href="#hampton-catlin" class="tab"><h3>Hampton Catlin</h3></a></li>
<li><a href="#joseph-wilk" class="tab"><h3>Joseph Wilk</h3></a></li>
<li><a href="#joshua-wehner" class="tab"><h3>Joshua Wehner</h3></a></li>
<li><a href="#michael-bensoussan" class="tab"><h3>Michael Bensoussan</h3></a></li>
<li><a href="#nick-the-german-sutterer" class="tab"><h3>Nick "The German" Sutterer</h3></a></li>
<li><a href="#r-konstantin-haase"><h3>R. Konstantin Haase</h3></a></li>
<li><a href="#sven-fuchs"><h3>Sven Fuchs</h3></a></li>
<li><a href="#josh-kalderimis"><h3>Josh Kalderimis</h3></a></li>
</ul>
<div id="speakers-tabs-people" >
<!-- START michael -->
<div id="michael-bensoussan" class="ui-tabs-panel ui-widget-content ui-corner-bottom">
<img src="/images/speakers/michael-bensoussan.jpeg" alt="michael-bensoussan">
<h3>Michael Bensoussan</h3>
<p><a href="https://github.com/mickey">@github</a> | <a href="http://twitter.com/mickeyben">@twitter</a> | <a href="http://letitcast.com"> @company</a></p>
<div class="side_pres">
<h4 class="side_title">Bio</h4>
<span class="summary">
<p>Michael is a ruby and rails enthusiast for 3 years now. He worked at various startups ; Eyeka, Seesmic and now Letitcast. Recently he had been giving Rails training in Paris for entrepreneurs and CS students. When not writing code, he can be found lost in a bookstore, losing himself in Paris or just in front of his screen waiting for the new Civ V patch.</p>
</span>
<h4 class="side_title">Abstract</h4>
<h5 class="side_title">Service Oriented Applications</h5>
<span class="summary">
<p>Not completely define yet but I'll mostly talk about how we cut our monolythic application into a rails api, 3 rails clients, 2 sinatra services and a rails engine</p>
</span>
</div>
</div>
<!-- END michael -->
<!-- START bruno -->
<div id="bruno-michel" class="ui-tabs-panel ui-widget-content ui-corner-bottom">
<img src="/images/speakers/bruno-michel.png" alt="">
<h3>Bruno Michel</h3>
<p><a href="https://github.com/nono">@github</a> | <a href="http://twitter.com/brmichel">@twitter</a></p>
<div class="side_pres">
<h4 class="side_title">Bio</h4>
<span class="summary">
<p>Lead developer at af83<br />Developer and administrator of LinuxFr.org popular website<br />President of Ruby France association</p>
</span>
<h4 class="side_title">Abstract</h4>
<h5 class="side_title">Goliath and his friends : Rack, EventMachine and Fibers</h5>
<span class="summary">
<p>Goliath is a event machine based. It uses Rack API and new features of Ruby 1.9.2. Both makes it really lightweight framework capable of processing asynchronously a large amount of data in an elegant way. It fit to write light web services as HTTP streaming file uploads, proxies, twitter, firehoses, etc.</p>
</span>
</div>
</div>
<!-- END bruno -->
<!-- START nick -->
<div id="nick-the-german-sutterer" class="ui-tabs-panel ui-widget-content ui-corner-bottom">
<img src="/images/speakers/nick-stterer.jpeg" alt="">
<h3>Nick "The German" Sutterer</h3>
<p><a href="https://github.com/apotonick">@github</a> | <a href="https://twitter.com/apotonick">@twitter</a></p>
<div class="side_pres">
<h4 class="side_title">Bio</h4>
<span class="summary">
<p>Nick Sutterer appreciates the beauty of elegant code, and the value of open source software. Through his tireless development and advocacy of the Cells and Apotomo gems, he has brought the concepts of component-oriented UI development to the world of Rails, proving that there should be no such thing as a double-render error, and that one need not be slave to the great monolithic view mentality. Also, he would like to have beer with you. </p>
</span>
<h4 class="side_title">Abstract</h4>
<h5 class="side_title">CRUD is not REST! Hypermedia for y'all!</h5>
<span class="summary">
<p>REST is an architectural style for distributed systems. However, many implementations forget about the distributed part of REST and simply map CRUD operations to HTTP verbs in a monolithic application. Hey, we want more! So let's have a look at the Roar gem and see how it helps working with representations, hypermedia, and decoupled architectures in Rails and Sinatra. While building both services and a consuming client we can discuss the sweet things about component-oriented architectures and french beer.</p>
</span>
</div>
</div>
<!-- END nick -->
<!-- START elise -->
<div id="elise-huard" class="ui-tabs-panel ui-widget-content ui-corner-bottom">
<img src="/images/speakers/elise-huard.jpeg" alt="elise-huard">
<h3>Élise Huard</h3>
<p><a href="https://github.com/elisehuard">@github</a> | <a href="http://jabberwocky.eu/">@web</a></p>
<div class="side_pres">
<h4 class="side_title">Bio</h4>
<span class="summary">
<p>After her studies in metallurgy, Élise realized job in that area were not her cup of tea, and she looked for jobs in an earlier interest, software.</p>
<p>Since then, she’s been rolling through jobs in C, C++, Java, a masters in AI, before falling in love with Ruby and going freelance. 10 years of software have helped her get a firm understanding on what works, what doesn’t, and what will make you cry blood and tears on nights before deadlines.</p>
<p>She’s a jack of all trades, loves reading, tinkering, food, travel, learning, and people out of the ordinary.</p>
</span>
<h4 class="side_title">Abstract</h4>
<h5 class="side_title">Ruby goes to Hollywood</h5>
<span class="summary">
<p>Computers are being built with more and more CPUs and those CPUs in turn have several cores. Powerful calculations are now performed either on many-cored machines, or on distributed systems. In this context, it's in the developer's interest to start thinking about concurrent programming. But concurrent programming with mutable is tricky. The last few years have conclusively shown that very few developers get this right when faced with conventional shared state threads.</p>
<p>One of the ways to simplify concurrent programming is the actor model. In the actor model, programs are made of actors sending each other messages, and acting on the messages they receive. The actors don't share any state.</p>
<p>In this talk I explore several ways to implement the actor model in Ruby.</p>
<p>The existing actor implementations in Ruby:
<dl>
<dd>- Rubinius actors</dd>
<dd>- Existing actor gems (cross Ruby implementations)</dd>
</dl>
</p>
<p>Actor implementations that are a little more 'out there':
<dl>
<dd>- Bindings with the Akka framework in Scala with JRuby</dd>
<dd>- Bindings with erlang, the first mainstream implementation of the actor model</dd>
<dd>- And their advantages and drawbacks, and code examples.</dd>
<dl>
</p>
<p>The talk will also allude to the fact that threads in Ruby should ideally have separate state, so that all programs using threads could also use the actor model (or other similar concurrency models).</p>
</span>
</div>
</div>
<!-- END elise -->
<!-- START rkh -->
<div id="r-konstantin-haase" class="ui-tabs-panel ui-widget-content ui-corner-bottom">
<img src="/images/speakers/rkh2.jpg" alt="rkh2">
<h3>R. Konstantin Haase</h3>
<p><a href="https://github.com/rkh">@github</a> | <a href="http://twitter.com/konstantinhaase">@twitter</a></p>
<div class="side_pres">
<h4 class="side_title">Bio</h4>
<span class="summary">
<p>Ruby has become Konstantin Haase's language of choice since 2005. He therefore actively participates in the Ruby Open Source community and has contributed to different widespread projects, like Rubinius and Rack and is a member of the Sinatra core team. In 2010 he successfully took part as a student in the Ruby Summer Of Code, where he was working on Rails internals. Konstantin is currently studying IT Systems Engineering at Hasso Plattner Institute in Potsdam and works part time as a software engineer at finnlabs.</p>
</span>
<h4 class="side_title">Abstract</h4>
<h5 class="side_title">Real Time Rack</h5>
<span class="summary">
<p>At least since node.js everyone knows that real time HTTP responses are the next big thing. The secrets of handling incoming requests asynchronously with Ruby is not yet far spread among Rubyists, as the internals needed for such responses are neither specified nor documented and there is a lack of tools. Still, it is possible to use Server-Sent Events, Websockets and akin with Rack today. This talk will demonstrate the underlying technologies and how to use them.</p>
</span>
</div>
</div>
<!-- END rkh -->
<!-- START joshua -->
<div id="joshua-wehner" class="ui-tabs-panel ui-widget-content ui-corner-bottom">
<img src="/images/speakers/joshua-wehner.jpg" alt="">
<h3>Joshua Wehner</h3>
<p><a href="https://github.com/jaw6">@github</a> | <a href="http://twitter.com/jaw6">@twitter</a></p>
<div class="side_pres">
<h4 class="side_title">Bio</h4>
<span class="summary">
<p>Joshua is passionate about all the little things that make each of us weird. His wife taught him that Ruby doesn't solve everything. He speaks four languages badly, plays games often, enjoys puns more than he should, and occasionally makes a lovely soufflé.</p>
</span>
<h4 class="side_title">Abstract</h4>
<h5 class="side_title">KEYNOTE Must It Always Be About Sex?</h5>
<span class="summary">
<p>Why do some people keep talking about diversity? Who cares if we're all the same? So long as we're not technically discriminating against anyone, that means we're good, right? If we only get applications from white dudes, that must mean that white dudes are the only ones out there. Right? Right?</p>
<p>When we feel threatened, we find comfort among people who seem most like us. As specialization increases in the community, we glom on to people who look like us, talk like us, and think like us. There's safety in a crowd.</p>
<p>But there are real dangers in becoming too much alike: monotony breeds more monotony. Real innovation happens when you think different than everyone else. What happens when we ruthlessly eliminate different thinkers, as we winnow the stack of resumés to those that seem most likely to "fit in"?</p>
<p>Come to this talk to find out what you can do to diversify - yourself, your organization, and your peers - and how you can help grow a better, stronger, more diverse community.</p>
</span>
</div>
</div>
<!-- END joshua -->
<!-- START sven -->
<div id="sven-fuchs" class="ui-tabs-panel ui-widget-content ui-corner-bottom">
<img src="/images/speakers/sven-fuchs.jpeg" alt="">
<h3>Sven Fuchs</h3>
<p><a href="https://github.com/svenfuchs">@github</a> | <a href="http://twitter.com/svenfuchs">@twitter</a></p>
<div class="side_pres">
<h4 class="side_title">Bio</h4>
<span class="summary">
<p>Sven Fuchs, pronounced [sfɛn fʊks], is an experienced software developer and opensource enthusiast currently based in Berlin. While focussing on Ruby/Rails development for the last 4 years he published a good number of Ruby and Rails projects, tools and libraries. Consistently ranked amongst the top 30 on Rails ranking sites he is probably best known for leading the Ruby I18n project, the Ruby gem which is shipped with Rails to provide internationalization support. </p>
</span>
<h4 class="side_title">Travis CI - Distributed, Continous Integration for the Ruby community</h4>
<h5 class="side_title"></h5>
<span class="summary">
<p>"The future is already here — it's just not very evenly distributed." (William Gibson)</p>
<p>The Ruby community is where a lot of this future already happens. We not only set the bar
higher and higher every day, we've also built most of the infrastructure use day to day.
Twitter, Github, Gemcutter, Pusher to just name a few projects that changed the world, the
way we live and work.</p>
<p>With Travis CI, an open source continous integration service for the Ruby community, we are
going to push the limits even further. We are going to build the test and integration
infrastructure you are dreaming of: The vision behind Travis CI is to become for builds
what Rubygems is for distributing libraries.</p>
<p>In this talk Josh and Sven, two of the core members of the developers team, will talk about
Travis CI and introduce you to the vision behind it and the way it is implemented.</p>
</span>
</div>
</div>
<!-- END sven -->
<!-- START josh -->
<div id="josh-kalderimis" class="ui-tabs-panel ui-widget-content ui-corner-bottom">
<img src="/images/speakers/josh-kalderimis.jpeg" alt="">
<h3>Josh Kalderimis</h3>
<p><a href="https://github.com/joshk">@github</a> | <a href="http://twitter.com/joshkalderimis">@twitter</a></p>
<div class="side_pres">
<h4 class="side_title">Bio</h4>
<span class="summary">
<p>Josh is a top-30 Ruby on Rails contributor and has been working with the framework since 2008. He maintains a massive amount of open-source Ruby projects, including multi_json, linkedin, faraday_middleware and his own completeness-fu. He's also one of Amsterdam.rb's organizers, the head PR guy and core team member for the Travis-CI team.</p>
</span>
<h4 class="side_title">Travis CI - Distributed, Continous Integration for the Ruby community</h4>
<h5 class="side_title"></h5>
<span class="summary">
<p>"The future is already here — it's just not very evenly distributed." (William Gibson)</p>
<p>The Ruby community is where a lot of this future already happens. We not only set the bar
higher and higher every day, we've also built most of the infrastructure use day to day.
Twitter, Github, Gemcutter, Pusher to just name a few projects that changed the world, the
way we live and work.</p>
<p>With Travis CI, an open source continous integration service for the Ruby community, we are
going to push the limits even further. We are going to build the test and integration
infrastructure you are dreaming of: The vision behind Travis CI is to become for builds
what Rubygems is for distributing libraries.</p>
<p>In this talk Josh and Sven, two of the core members of the developers team, will talk about
Travis CI and introduce you to the vision behind it and the way it is implemented.</p>
</span>
</div>
</div>
<!-- END josh -->
<!-- START hampton -->
<div id="hampton-catlin" class="ui-tabs-panel ui-widget-content ui-corner-bottom">
<img src="/images/speakers/hampton-catlin.jpg" alt="">
<h3>Hampton Catlin</h3>
<p><a href="https://github.com/hcatlin">@github</a> | <a href="http://twitter.com/hcatlin">@twitter</a> | <a href="http://hamptoncatlin.com">@web</a></p>
<div class="side_pres">
<h4 class="side_title">Bio</h4>
<span class="summary">
<p>Hampton Catlin is the Framework Architect for Moovweb.com and is also the creator of several successful iPhone applications, including Dictionary! the #1 dictionary on iPhone and Palm Pre. Hampton is the man behind the current Wikipedia Mobile Gateway (m.wikipedia.org). He is also inventor of the Haml markup language and Sass, a CSS generating language.</p>
</span>
<h4 class="side_title">Abstract</h4>
<h5 class="side_title">What do American Airlines, Farmville, and Wikipedia have in common?</h5>
<span class="summary">
<p>They all use several different game play mechanics to encourage addictive behaviours in their users and customers. Being a developer is much more than writing nice code... its about building an experience for your users. And, part of that is using gameplay to make sure your users have a great time and come back again.</p>
<p>Even if you never thought of what your building as being a game, I'll help show you that it gameplay is part of every life experience and is coded into our DNA.</p>
<p>To crack the code of what works and what doesn't, we need to look towards evolutionary behaviouralism as a guide. Over millions of years we have been trained to follow certain basic social behaviours and if you understand those behaviours, you can use them to give your users a very positive experience.</p>
<p>Some of the talk will be scientific, but a lot of it will highlight real usable techniques to get the desired effects. I hope to guide everyone through a lot of examples and analysis of companies where they went right ... and where they failed."</p>
</span>
</div>
</div>
<!-- END hampton -->
<!-- START joseph-->
<div id="joseph-wilk" class="ui-tabs-panel ui-widget-content ui-corner-bottom">
<img src="/images/speakers/joseph-wilk.jpeg" alt="">
<h3>Joseph Wilk</h3>
<p><a href="https://github.com/josephwilk">@github</a> | <a href="http://twitter.com/josephwilk">@twitter</a></p>
<div class="side_pres">
<h4 class="side_title">Bio</h4>
<span class="summary">
<p>Joseph Wilk is a member of the core development team for Cucumber. He has been developing for the web for 11 years in both big and small companies and as an entrepreneur. After stints working with Java and Python he finally found Ruby. Since then he has become a regular speaker at various Ruby conferences around the world. He spends his time in-between eating Cucumbers and travelling, working at Songkick.com. Having more fun than is healthy working as a Software Gardener building web systems and working on open source projects. He suffers from test obsession and has given up hope of any treatment.</p>
</span>
<h4 class="side_title">Abstract</h4>
<h5 class="side_title">The Limited Red Society</h5>
<span class="summary">
<p>During an hour of programming what do you learn about your performance? How did that last refactoring go? How does that hour compare to the previous hour? How about against last week or last month? How are your habits as a programmer improving? How does your refactoring pattern differ from a masters like Martin Fowlers?</p>
<p>Professional Tennis players learn from detailed statistics about how they performed in a game and use this information to become better players.</p>
<p>Why don't we do the same in Programming? I want to demonstrate how we can, especially how we as individual programmers can help limit the time we spend in the red (failing tests) while developing. How long we spend in the red and how often can reflect on how we are working as programmers. Joshua Kerievsky created ""The Limited Red Society"", a group of practitioners that have learned how to effectively reduce red time while test-driving and refactoring code. I want to introduce this society to the Ruby world and some of the tools and ideas I have been working on.</p>
<p>We can gain detailed insight into your programming patterns while using a TDD flow by recording the state of your tests every time you run them. From these detailed metrics we can start to visualise how you work. How long did we spend in the red with that failed test? Was that test we wrote too big a step leaving us stuck in the red for too long? Did we spend a long time in the red because we were shaving a Yak? How many unit tests did we just break with that last change?</p>
</span>
</div>
</div>
<!-- END joseph-->
<!-- START blake -->
<div id="blake-mizerany" class="ui-tabs-panel ui-widget-content ui-corner-bottom">
<img src="/images/speakers/blake-mizerany.png" alt="">
<h3>Blake Mizerany</h3>
<p><a href="https://github.com/bmizerany">@github</a> | <a href="http://twitter.com/bmizerany">@twitter</a> | <a href="http://itsbonus.heroku.com">@web</a></p>
<div class="side_pres">
<h4 class="side_title">Bio</h4>
<span class="summary">
<p>I created Sinatra (www.sinatrarb.com) and co-created Doozer (http://github.com/ha/doozerd). I saw Elvis at a gas station the other day. I speak Ruby, Go, Erlang, JavaScript, C, C++, and more. My preferred form of transportation is Git. Heroku (heroku.com) is where I hang my hat. My Mom thinks I'm totally awesome. You didn't see me.</p>
</span>
<h4 class="side_title">Abstract</h4>
<h5 class="side_title">On Distributed Failures</h5>
<span class="summary">
<p>In unreliable networks, with unreliable processors (also known as "The Cloud") one must know all the ways their thing can fail; And just as importantly, how to recover. It is even better to have the ability to recover in an automated way. I'll go over the common failure conditions in distributed systems, and then introduce you to Doozer, the highly-available, consistant data store that makes recovering from these problems easy.</p>
</span>
</div>
</div>
<!-- END blake -->
</div>
</div>
</div>
</div>
<div class="column_2">
<a href="/" class="big green awesome full_width_button">Sold Out</a>
<div id="twitter">
<p>Follow us on twitter <a href="http://twitter.com/rubylug">@rubylug</a> <a href="http://twitter.com/#!/search/%23rulu">#rulu</a></p>
</div>
<div class="gold-sponsors">
<h2>GOLD Sponsors</h2>
<!-- <a href="/sponsoring" class="become_sponsor">Become a sponsor ?</a> -->
<ul>
<li>
<a href="http://www.sogilis.com/">
<img alt="Sogilis" src="images/sponsors/logo_sogilis.png" class="bigger-logo" /><br />
</a>
</li>
<li>
<a href="http://official.fm/">
<img alt="official.fm" src="images/sponsors/logo_officialfm.png" class="bigger-logo" /><br />
</a>
</li>
<li>
<a href="http://af83.com">
<img alt="af83" src="images/sponsors/logo_af83.jpg" class="bigger-logo" /><br />
</a>
</li>
</ul>
</div>
<div class="sponsors">
<h2>SILVER Sponsors</h2>
<ul>
<li>
<a href="http://www.heroku.com/">
<img alt="Heroku" src="images/sponsors/logo_heroku.png" /><br />
</a>
</li>
<li>
<a href="http://www.shopify.com/">
<img alt="Shopify" src="images/sponsors/logo_shopify.png" /><br />
</a>
</li>
<li>
<a href="http://www.novelys.com/">
<img alt="Novelys" src="images/sponsors/logo_novelys.png" /><br />
</a>
</li>
<li>
<a href="http://www.dimelo.com/">
<img alt="Dimelo" src="images/sponsors/logo_dimelo.png" /><br />
</a>
</li>
<li>
<a href="http://www.webpulser.com/">
<img alt="Webpulser" src="images/sponsors/logo_webpulser.png" /><br />
</a>
</li>
<li>
<a href="http://www.tigerlilyapps.com/">
<img alt="Tigerlily Apps" src="images/sponsors/logo_tigerlily.png" /><br />
</a>
</li>
<li>
<a href="http://www.nuxos.fr/">
<img alt="Nuxos" src="images/sponsors/logo_nuxos.png" /><br />
</a>
</li>
<li>
<a href="http://www.microsoft.com">
<img alt="Microsoft" src="images/sponsors/logo_microsoft.png" /><br />
</a>
</li>
<li>
<a href="http://rubyfrance.org/">
<img alt="Rubyfrance" src="images/sponsors/logo_rubyfrance.jpg" /><br />
</a>
</li>
</ul>
</div>
<div class="sponsors">
<h2>Partners</h2>
<ul>
<li>
<a href="http://www.citi.insa-lyon.fr/">
<img alt="INSA" src="images/sponsors/INSA.png" /><br />
</a>
</li>
<li>
<a href="http://www.leadformance.com/">
<img alt="Leadformance" src="images/sponsors/logo_leadformance.gif" /><br />
</a>
</li>
<li>
<a alt="HESPUL" href="http://hespul.org/">
<img alt="" src="images/sponsors/logo_hespul.jpg" /><br />
</a>
</li>
<li>
<a href="http://www.clubagilerhonealpes.org/">
<img alt="CARA" src="images/sponsors/logo_cara.png" /><br />
</a>
</li>
</ul>
</div>
</div>
</div>
</div>
<footer>
<div class="center clearfix">
<ul>
<li><a href="/">HOME</a></li>
<li><a href="/speakers">SPEAKERS</a></li>
<li><a href="/schedule">SCHEDULE</a></li>
<li><a href="/venue">VENUE</a></li>
<!-- <li><a href="/sponsors">SPONSORS</a></li> -->
<li><a href="mailto:[email protected]">CONTACT</a></li>
</ul>
© 2011 <a href="http://lyonrb.fr">Lyon Ruby Brigade</a> - <a href="/legal">legal notice</a>
<hr>
<div class="organizers clearfix">
<ul>
<li><a href="http://twitter.com/21croissants"><img class="profil" alt="21croissants" src="images/organizers/21croissants.png"></a><br><a href="http://twitter.com/21croissants">@21croissants</a></li>
<li><a href="http://twitter.com/bibinou"><img class="profil" alt="bibinou" src="images/organizers/bibinou.png"></a><br><a href="http://twitter.com/bibinou">@bibinou</a></li>
<li><a href="http://twitter.com/dmathieu"><img class="profil" alt="dmathieu" src="images/organizers/dmathieu.png"></a><br><a href="http://twitter.com/dmathieu">@dmathieu</a></li>
<li><a href="http://twitter.com/cesariogw"><img class="profil" alt="cesario" src="images/organizers/cesario.png"></a><br><a href="http://twitter.com/cesariogw">@cesariogw</a></li>
<li><a href="https://github.com/ranska"><img class="profil" alt="ranska" src="images/organizers/ranska.png"></a><br><a href="http://github.com/ranska">@ranska</a></li>
<li><a href="http://twitter.com/lminaudier"><img class="profil" alt="lminaudier" src="images/organizers/lminaudier.jpg"></a><br><a href="http://twitter.com/lminaudier">@lminaudier</a></li>
<li><a href="http://twitter.com/vzmind"><img class="profil" alt="vzmind" src="images/organizers/vzmind.png"></a><br><a href="http://twitter.com/vzmind">@vzmind</a></li>
</ul>
</div>
</div>
</footer>
</body>
<script type="text/javascript">
var _gaq = _gaq || [];
_gaq.push(['_setAccount', 'UA-20067061-2']);
_gaq.push(['_trackPageview']);
(function() {
var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
})();
</script>
</html>