-
Notifications
You must be signed in to change notification settings - Fork 0
/
speaking.html
executable file
·144 lines (112 loc) · 8.18 KB
/
speaking.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
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<link rel="icon" href="images/icon.png">
<meta name="description" content="Python Cameroon">
<meta name="keywords" content="python cameroon user group,Python conference, programing Africa,Programing,python cameroon,pycon,python">
<meta http-equiv="X-UA-Compatible" content="ie=edge">
<title>Speak at Pycon </title>
<link rel="stylesheet" href="css/bootstrap.min.css">
<link rel="stylesheet" href="css/font-awesome.css">
<link rel="stylesheet" href="css/style.css">
<link rel="stylesheet" href="css/animate.css">
</head>
<body id= "top">
<style>.container{
padding:20px;
border-radius:3px;
background-color: rgb(61, 69, 71);
color:white;
}
.navbar-fixed-top .sclp{
padding-top: 280px;
}
</style>
<div class="container">
<nav class="navbar navbar-default" role="navigation">
<div class="navbar-header">
<button type="button" class="navbar-toggle" data-toggle="collapse"
data-target="#navbar">
<span class="sr-only">Toggle navigation</span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
</button>
<a class="navbar-brand" href="index.html"> <img src="images/pythonlogo.png" class="img-responsive" width="200" height="120"> </a>
</div>
<div class="collapse navbar-collapse" id="navbar">
<ul class="nav navbar-nav navbar-right" id="nav">
<li >
<a href="pycon.html">PyCon</a></li>
<li><a href="index.html#coc">COC</a></li>
</ul>
</div>
</nav></div>
<div class="container">
<div class="slcp" id="one">
<h2 > Speak at PyCon</h2>
<p>PyCon is seeking speakers of all experience levels and backgrounds to contribute to our conference program! If you use Python professionally, as a hobbyist, or are just excited about Python or programming and open source communities, we'd love to hear from you. Speakers also get prioritized access to financial aid, so please don't let that be a deterrent either! We want you and your ideas at PyCon!</p>
<p>We've got lots of good information and resources below that you should read, but in case you've already read it and want to dive in now.</p>
<p>Here are the PyCon 2018 Call for Proposals deadlines:</p>
Tutorial proposals — deadline is 24 November 2017 23:59:59 pm GMT.
Talk, Poster, and Education Summit proposals — deadline is 3 December 2017 2017 23:59:59 pm GMT.
<p>Where to submit your proposal </p><h3 class="text-center"> All proposal should be sent to : <span class="text-primary">pycameroon@gmail.com</span></h3>
<p>
Due to the competitive selection process, we encourage prospective speakers to submit their proposals as early as possible as it allows for feedback prior to the CFP deadline.</p>
Guidelines for Proposal Submission
Everyone is encouraged to submit a proposal, regardless of experience level. PyCon thrives on having talks ranging from introductory to advanced. If you are reading this, and you are interested in speaking at PyCon, we want you to submit a proposal.
</div><hr>
<div class="sclp" id="two">
<h2 >Talks</h2>
<p>These are the traditional talk sessions given during the main conference days, Friday through Sunday, january 28–May 29.</p>
<p>PyCon is dedicated to featuring a diverse and inclusive mix of speakers in the lineup.</p>
<p>
All speakers are expected to have read and adhere to the conference Code of Conduct. In particular for speakers: slide contents and spoken material should be appropriate for a professional audience including people of many different backgrounds. Sexual language and imagery are not appropriate, and neither are language or imagery that denigrate or demean people based on race, gender, religion, sexual orientation, physical appearance, disability, or body size. </p>
<p>
We will make every effort to provide accommodations for speakers and attendees of all abilities—all we ask is that you let us know so we can prepare accordingly.</p>
<p>
Most talks are 30 minutes long, but we do offer a limited number of 45-minute slots for important topics that promise to benefit from a more extensive treatment. We organize the schedule into five "tracks", grouping talks by topic and having them in the same room for consecutive sessions.</p>
<p>
There is no official restriction on the topic that you propose for a talk session. Talks about Python or the Python community are most likely to line up with the interests of PyCon's audience, and a key consideration that the talk selection committee will be thinking about is your talk’s ability to draw an audience. We observe a limit of one talk per presenter. You may propose more than one, but the committee will ask you to choose only one talk if more than one of your proposals is accepted.
</p></div><hr>
<h2>Tutorials</h2>
<p>
As with the talks, we are looking for tutorials that can grow this community at any level. We aim for tutorials that will advance Python, advance this community, and shape the future. Each tutorial session runs for 3 full hours plus a break for coffee. There is both a morning tutorial session and an afternoon tutorial session on the two days preceding the main conference — this year, the tutorial days are Wednesday and Thursday, january 23–26 in the same venue that hosts the main conference days that follow.</p>
<p>As tutorials are longer than talks and are in an interactive classroom-like setting, they require much more preparation. Due to the amount of work involved, tutorial instructors are compensated. There is a limit of at most two tutorials given by one presenter.</p>
</div>
<br>
<h3 class="text-center"> All proposal should be sent to : <span class="text-primary">pycameroon@gmail.com</span></h3>
<p class="text-center"> For any more information or concernces contact <span class="text-primary">pyconcamroon@gmail.com</span></p>
<hr>
<footer>
<i class="fa fa-slack fa-4x icon"></i>
<p> Designed & Developed with <i class="fa fa-coffee"> </i> & <i class="fa fa-heart"></i> by Python Cameroon © Copy rights 2017 </p>
<a rel="license" href="http://creativecommons.org/licenses/by-nc-sa/4.0/"><img alt="Creative Commons License" style="border-width:0"src="https://i.creativecommons.org/l/by-nc-sa/4.0/88x31.png"></a><br />This work is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by-nc-sa/4.0/">Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License</a>.
</footer>
<a href="#top" id="scrollTop"><i class="fa fa-hand-o-up fa-2x"></i></a>
</div>
<script src="js/jquery.js"></script>
<script src="js/bootstrap.min.js"></script>
<script src="js/scrollreveal.min.js"></script>
<script src="js/js.js"></script>
<script type="text/javascript">
</script>
<script type="text/javascript">
$(function(){
removeSection = function(e) {
$(e).parents(".section").remove();
$('[data-spy="scroll"]').each(function () {
var $spy = $(this).scrollspy('refresh')
});
}
$("#myScrollspy").scrollspy();
$('#myScrollspy').on('activate.bs.scrollspy', function () {
var currentItem = $(".nav li.active > a").text();
$("#activeitem").html("Currently you are viewing - " + currentItem);
})
});
</script>
</body>
</html>