-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathcall-for-workshops.html
181 lines (176 loc) · 14.3 KB
/
call-for-workshops.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
<!DOCTYPE html>
<!--[if lt IE 7 ]> <html class="ie ie6 no-js" lang="en"> <![endif]-->
<!--[if IE 7 ]> <html class="ie ie7 no-js" lang="en"> <![endif]-->
<!--[if IE 8 ]> <html class="ie ie8 no-js" lang="en"> <![endif]-->
<!--[if IE 9 ]> <html class="ie ie9 no-js" lang="en"> <![endif]-->
<!--[if gt IE 9]><!-->
<!--[if lte IE 9]>
<![endif]-->
<html class="no-js" lang="en">
<!--<![endif]-->
<head>
<meta charset="utf-8" />
<!-- Design by
```` ``` ```` ```````` ``````````` `````````
oMMy dMM/ -NMM: `MMMMMMMMMmy/` dMMMMMMMMMm mMMMMMMMMMNds:
oMMy dMM/ -NMM/ `MMMo+++oymMMm+ dMMy++++++/ mMMy+++++oyNMMm+
oMMy dMM/ .mMM+ `MMM` :dMMs dMM/ mMM: :dMMd`
oMMy dMM/ .mMMo `-/oymy `MMM` `NMM- dMM/ mMM: yMMy
oMMy dMM/ `mMMd+shNMMMMMd` `MMM` dMM: dMMNNNNNNNd mMM: .MMN`
oMMy dMM/ `dMMMMMMmhsmMMd` `MMM` +MMm` dMMdyyyyyyo mMM: -MMN`
oMMy dMM/ `hNdyo/- oMMm` `MMM` ./hMMm- dMM/ mMM: .dMMo
oMMMNNNNNNNNMMM/ `. +MMm. `MMMNNNNNMMMm+` dMM/ mMM: -sNMMo
oMMmyyyyyyyyNMM/ +MMN. `MMMyyyyso/. dMMmhhhhhhy mMMmhhhhdmNMMNy.
+ddo ydd: -ddd- `ddd` sdddddddddy yddddddddhyo:`
-->
<title>Call for Workshops — NodeConf Argentina</title>
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
<meta name="viewport" content="width=device-width, initial-scale=1.0" >
<link rel="shortcut icon" href="images/favicon.png">
<meta name="theme-color" content="#1A2024">
<meta name="msapplication-navbutton-color" content="#1A2024">
<meta name="apple-mobile-web-app-status-bar-style" content="#1A2024">
<meta name="keywords" content="nodeconf,argentina,konex,buenos aires,javascript,nodejs,node,js">
<meta name="description" property="og:description" itemprop="description" content="Join us for NodeConf Argentina! Our first edition will be held at Ciudad Cultural Konex, in November 17-19, 2016. This will be the first international Node.js conference held in Buenos Aires, Argentina.">
<meta property="og:site_name" content="NodeConf Argentina">
<link rel="canonical" href="https://2016.nodeconf.com.ar/call-for-workshops.html">
<meta property="og:url" itemprop="url" content="https://2016.nodeconf.com.ar/call-for-workshops.html">
<meta name="twitter:title" itemprop="name" property="og:title" content="NodeConf Argentina">
<meta name="twitter:description" content="Join us for NodeConf Argentina! Our first edition will be held at Ciudad Cultural Konex, in November 17-19, 2016. This will be the first international Node.js conference held in Buenos Aires, Argentina.">
<meta name="twitter:card" ontent="summary_large_image">
<meta name="twitter:site" content="@nodeconfar">
<meta name="twitter:creator" content="@nodeconfar">
<meta name="author" itemprop="creator" content="NodeConf Argentina <hello@nodeconf.com.ar>">
<meta property="og:image" itemprop="images" content="https://2016.nodeconf.com.ar/images/cfp.png">
<meta property="og:image" content="https://2016.nodeconf.com.ar/images/logo.svg">
<!-- twitter only cares about the last meta image repeat the cover -->
<meta name="twitter:image:src" content="https://2016.nodeconf.com.ar/images/cfp.png">
<link rel="stylesheet" type="text/css" href="assets/css/bootstrap.css" />
<link rel="stylesheet" type="text/css" href="assets/css/nodeconf.css" />
<link href="https://fonts.googleapis.com/css?family=Abel" rel="stylesheet" type="text/css">
<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.5.0/jquery.min.js" type="text/javascript" ></script>
<script src="assets/js/bootstrap.min.js" type="text/javascript" ></script>
<script>
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
})(window,document,'script','https://www.google-analytics.com/analytics.js','ga');
ga('create', 'UA-35043128-11', 'auto');
ga('send', 'pageview');
</script>
</head>
<body>
<section id="conduct" class="dark-theme">
<div class="container"> <a href="index.html" class="back-home">
<div class="tooltip">back</div>
</a>
<div class="plain-header row col-md-8">
<h3>Call for Workshops</h3>
<p>“NodeConf hits the ground running in Latin America”</p>
<p>We are inviting the JavaScript community to submit workshops.</p>
</div>
<div class="call-speak">
<div class="col-md-2 menu-call pull-right">
<nav>
<ul>
<li><a href="#topic">Topics</a></li>
<li><a href="#help">We Can Help</a></li>
<li><a href="#perks">The Perks</a></li>
<li><a href="#process">The Selection Process</a></li>
<li><a href="#submission">Example Submission</a></li>
<li><a href="#guide">Guidelines</a></li>
<li><a href="#form">Apply here</a></li>
</ul>
</nav>
</div>
<div class="col-md-10 call-for-speakers pull-left">
<ul id="topic">
<h4>Topics</h4>
<li>
<p>To get a feel for what we are interested in hearing about, you might want to look at other NodeConf chapters around the world (<a href="http://london.nodeconf.com/#speakers" target="_blank">London</a>, <a href="http://oslo.nodeconf.com/#speakers" target="_blank">Oslo</a>, <a href="http://barcelona.nodeconf.com/#speakers" target="_blank">Barcelona</a>).</p>
<p>We like to see anything that squarely fits into the spectrum of:</p>
<p class="bullet">Cutting-edge technological advances in the world of JavaScript or computer science in general, if somehow applicable to Node.js.</p>
<p class="bullet">We love hearing about the ingenious ideas & cool hacks you’re working on.</p>
<p class="bullet">JavaScript-related art installations or hacks.</p>
<p class="bullet">Hardware-related applications of JavaScript.</p>
<p class="bullet">Node.js community, history, past, present & future.</p>
<p class="bullet">Open Source projects.</p>
<p class="bullet">And finally: Whatever the hell you want; this is your conference.</p>
</li>
</ul>
<ul id="help">
<h4>We Can Help</h4>
<li>
<p>Not everybody is a natural talent on stage. Not everybody can produce kick-ass slide-decks. Not everybody is a live-demo-god. Not everybody knows they have something great to talk about.</p>
<p>There are about a million reasons why you don’t consider yourself a speaker, let alone at NodeConf Argentina, part of an established brand where all your heroes have spoken in the past. <strong>We are here to prove you wrong.</strong> If all you have is a gut feeling that you should be on stage, we are here to reach out and help you to develop or hone the skills you think you lack to deliver a great presentation.</p>
<p class="bullet"> We are happy to brainstorm your interests to see if a great topic is hiding.</p>
<p class="bullet"> We are happy to connect you with experienced speakers to help prepare your submission, or you can refer to the “Example Submission” section below for tips.</p>
<p class="bullet"> We are happy to review and advise on how to produce a slide deck. If you don’t feel creative, just use these JSConf <a href="https://github.com/jsconf/presentation-templates/downloads" target="_blank">Keynote and PowerPoint templates.</a></p>
<p class="bullet"> If you need practice giving talks, get in touch, we can hook you up with local meetup groups or set up a stage for you and a bunch of friends in advance, so you can practice in front of a friendly crowd.</p>
<p class="bullet"> Again, whatever else you might need, we’re here to help.</p>
<p>Get in touch: <a href="mailto:hello@nodeconf.com.ar">hello@nodeconf.com.ar </a>(just don’t use this to submit a proposal).</p>
<p>If you need more encouragement, check out the <a href="http://weareallaweso.me/">We Are All Awesome</a> site that tries to convince you to speak!</p>
</li>
</ul>
<ul id="perks">
<h4>The Perks</h4>
<li>
<p>If you get selected as a speaker at NodeConf Argentina, here’s what you get:</p>
<p class="bullet"><strong>Travel to Buenos Aires covered.</strong> This usually means we pay for your plane ticket, boat, raft, hyperloop pod, or space pod. We are happy to assist with booking your itinerary, but if you can do it yourself, we can focus on making the conference more awesome.</p>
<p class="bullet"><strong>Entrance to the conference.</strong> We won’t be done with the speaker selections by the end of the ticket sales, so if you want to make sure you can attend, you may want to purchase a ticket regardless. If you get selected to speak and if you need to, we can refund your ticket, but if we don’t, we can spend more money on making the conference more awesome.</p>
<p class="bullet"><strong>We cover your stay in Buenos Aires</strong> in a fancy hotel near the venue (including free Wifi) for the days of the conference and a day before and after (e.g. November 16th-20th). If you want to stay longer, we can arrange things, just let us know. You will have to cover extra nights, though.</p>
<p>If your employer can cover your travel and hotel, we are happy to list them as an awesome company sponsor. The money we save will be used to make our conference more awesome. (You might see a pattern …)</p>
<p>If you have any special requirements, non-return trips (say you are going to awesome Patagonia for wine tasting, asado and whale sighting), just let us know, we can usually work these things out. Just note that every minute we spend on this, we don’t spend on making the conference more awesome ;)</p>
<p>If you want to bring a significant other, or bring your kid(s) and need child-care to be sorted out for the time of the conference, please also get in touch. We are here to make this easy for you!</p>
</li>
</ul>
<ul id="process">
<h4>The Selection Process</h4>
<li>
<p>Here’s roughly how we will select the workshops:</p>
<p>Anonymize submissions, so we don’t bias against anything related to the submitter.</p>
<p class="bullet">Two rounds of voting:</br>
- The first round rates each workshop on a scale from 1 to 10.</br>
- The top-N (~50) submissions are rated again on a 3-point scale (“meh”, “yay”, “MUST HAVE”).</br>
<p class="bullet">De-anonymize so we can (finally) bias against speaker details (based on our budget, we might opt for a local or at least closer-by [read: cheaper to transport] speaker).
(and a number of details that we make up as we go along)</p>
<p> We expect 100-200 excellent submissions for 20-30 speaking slots. The process helps us select the right ones.</p>
</li>
</ul>
<ul id="submission">
<h4>Example Submission</h4>
<li>
<p>Here’s an example conference talk proposal from JSConf EU 2011:</p>
<p><strong>How To Be Better</strong></p>
<p>You’re read the Definitive Guide and flicked through the standard, you know how to assign default values with OR and you go to your local usergroup once in a while.</p>
<p>How do you move your JS skills along and upwards on the unstoppable path of true mastery? Do you want to be one of those folks who dismisses wtfjs.com with a sniff, a wave of the hand and an offhand comment of “call recasts the parameter as an object”?</p>
<p>From the blindingly obvious (write more javascript) - through the positively heretical (never ever use JSLint - except when it’s a really good idea) - to the bizarre (take up needlework), come and be guided toward the bright shiny light where the gods live.</p>
</li>
</ul>
<ul id="guide">
<h4>Guidelines</h4>
<li>
<p>Submit your proposal by <strong>August 11th, 23:59:59 ART (GMT -3).</strong> No excuses.</p>
<p>Workshops can be <strong>in English or Spanish,</strong> but take in consideration that workshops will not count with live interpreting.</p>
<p><strong>Workshops can have a duration up to 3 hours.</strong>We suggest timing your presentation in advance. </p>
<p><strong>Make sure you care,</strong> and make sure we see you care. Typos, sloppy formatting and all-lowercase submissions make our reading of your proposal tedious. These things will definitely count against your proposal.</p>
<p><strong>Don’t overdo it</strong> either. If you need more than two paragraphs to get to the point of your topic, we need to ask you to slim things down. With the amount of submissions we get, the quicker you can to make a good impression, the better.</p>
<p>“I would have written a shorter letter, but I did not have the time” — Blaise Pascal</p>
<p><strong>Original Topics.</strong> One of the things we strive to do with NodeConf Argentina is to push the community forward. We can’t do this if the same people keep talking about the same things all the time. Thus, we favour original content. If you want to discuss a topic that you have talked about elsewhere, try to add a twist, or new research, or development, something unique. Of course, if your workshop is plain awesome as-is, go for that :)</p>
</li>
</ul>
<ul id="form">
<iframe src="https://docs.google.com/forms/d/e/1FAIpQLSc09FQaU1TQ8YN2A84N0-RgOLjW93rojRhPCqi97dIaFD0EeA/viewform" width="100%" height="800" frameborder="0" marginheight="0" marginwidth="0"></iframe>
</ul>
</div>
</div>
</div>
</section>
<footer>
<div class="container">
<div class="col-xs-6"><a href="index.html"><img src="images/footer.svg"></a></div>
<div class="col-xs-6 text-right"><a href="code-of-conduct.html">code of conduct</a></div>
</div>
</footer>
</body>
</html>