forked from Code52/code52.github.com
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathintroduction.html
More file actions
123 lines (93 loc) · 5.24 KB
/
introduction.html
File metadata and controls
123 lines (93 loc) · 5.24 KB
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
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta content="en-au" http-equiv="Content-Language" />
<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
<link href="/rss.xml" type="application/rss+xml" rel="alternate" title="Blog Feed" />
<link href="/atom.xml" type="application/atom+xml" rel="alternate" title="Blog Feed" />
<link href="/projectsrss.xml" type="application/rss+xml" rel="alternate" title="Projects Feed" />
<link href="/projectsatom.xml" type="application/atom+xml" rel="alternate" title="Projects Feed" />
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1" />
<title>Introducing code52 - code52</title>
<link rel="stylesheet" type="text/css" href="/css/style.css" />
<link rel="shortcut icon" href="/img/favicon.ico" />
</head>
<body>
<div id="container">
<div id="side">
<a href="/" id="home" title="home" alt="home"><img src="/img/logo.png" alt="Code 52 - a new coding project every week" /></a>
<div id="hometext"><a href="/" >code52</a></div>
<div class="section">
<ul>
<li><a href="/about.html">about</a></li>
<li><a href="http://talk.code52.org/">discussion</a></li>
<li><a href="http://twitter.com/code_52">twitter</a></li>
<li><a href="http://jabbr.net/#/rooms/code52">jabbr</a></li>
<li><a href="http://code52.uservoice.com">uservoice</a></li>
<li><a href="/contributing.html">contributing</a></li>
<li><a href="/projects.html">previous projects</a></li>
</ul>
</div>
</div>
<div id="content">
<div class="entry-container">
<div class='entry'>
<h1> Introducing code52 </h1>
<span class="postdate">31 December, 2011
</span>
<p>This all started with a simple premise:</p>
<h2>"A new coding project every week"</h2>
<p>Madness! I was hooked and <a href="http://dictionary.reference.com/browse/gobsmacked">gobsmacked</a> at the same time. I had so many questions, and as we discussed it we started to come to something resembling an agreement.</p>
<h2>Who's behind this idea?</h2>
<p>We are (in alphabetical order) <a href="http://twitter.com/tobin">Andrew Tobin</a>, <a href="http://twitter.com/shiftkey">Brendan Forster</a> and <a href="http://twitter.com/aeoth">Paul Jenkins</a>.</p>
<h2>What are your goals?</h2>
<p>We want to:</p>
<ul>
<li>introduce developers to open-source projects and help them learn the ropes.</li>
<li>foster a community which encouraged contributions across a range of technologies.</li>
<li>work on projects which the community (i.e. YOU) want to improve.</li>
</ul>
<p> Of course, that doesn't get away from the original question I had.</p>
<h2>Why a week?</h2>
<p> A week isn't a long time - or it may be, depending on your perspective. This is still a somewhat contentious point within the group, but a week suits me because:</p>
<ul>
<li>shorter timelines encourage achievable goals.</li>
<li>shorter timelines reduce the incentive to procrastinate.</li>
<li>more variety of projects to work on over a period of time.</li>
<li>with good organisation, each week should be productive out of the gate.</li>
</ul>
<h2>What next?</h2>
<p> But there are some things we need to address first:</p>
<ul>
<li>how do we determine which projects to work on?</li>
<li>how do we organise each project?</li>
<li>how do we (as co-ordinators) deal with the skill gap between experienced and junior developers?</li>
</ul>
<p> We want to <strong>build fun stuff</strong>, <strong>give back</strong> to the projects which have been useful to us, and potentially <strong>create a community</strong> around this crazy idea. So whatever your background - if you want to get involved and work with others in the developer community, we'd love to hear from you.</p>
<p> Do you have an project which suits this idea? <a href="http://code52.uservoice.com">Vote on it</a></p>
<p> Want to discuss your ideas and suggestions? <a href="http://code52.tenderapp.com">Share it</a></p>
<p> Want to get in touch? Follow us on <a href="http://twitter.com/code_52">Twitter</a>!</p>
</div>
</div>
<div id="page-navigation">
<div class="left"> </div>
<div class="right"> <a href="/downmarker" title="next Post: Week 1: Downmarker WPF">Week 1: Downmarker WPF → </a> </div>
<div class="clear"> </div>
</div>
<div id="disqus_thread"></div>
<script type="text/javascript">
/* * * CONFIGURATION VARIABLES: EDIT BEFORE PASTING INTO YOUR WEBPAGE * * */
var disqus_shortname = 'code52'; // required: replace example with your forum shortname
/* * * DON'T EDIT BELOW THIS LINE * * */
(function() {
var dsq = document.createElement('script'); dsq.type = 'text/javascript'; dsq.async = true;
dsq.src = 'http://' + disqus_shortname + '.disqus.com/embed.js';
(document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(dsq);
})();
</script>
<noscript>Please enable JavaScript to view the <a href="http://disqus.com/?ref_noscript">comments powered by Disqus.</a></noscript>
<a href="http://disqus.com" class="dsq-brlink">blog comments powered by <span class="logo-disqus">Disqus</span></a>
</div>
</div>
</body>
</html>