You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _posts/2011-12-31-introduction.md
+16-17Lines changed: 16 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,21 +4,19 @@ title: "An introduction to code52"
4
4
author: shiftkey
5
5
---
6
6
7
-
I don't know which one of my co-conspirators came up with the idea, but it all started with a simple premise:
7
+
This all started with a simple premise:
8
8
9
-
**"A new coding project every week"**
9
+
##"A new coding project every week"
10
10
11
-
Madness! Surely it couldn't be possible. What would that even involve?
11
+
Madness! I was hooked and [gobsmacked](http://dictionary.reference.com/browse/gobsmacked) at the same time. I had so many questions, and as we discussed it we started to come to something resembling an agreement. We wanted to:
12
12
13
-
I had so many questions, but as we discussed it we started to come to something resembling an agreement. We wanted to:
14
-
15
-
- introduce more developers to open-source projects and help them learn the ropes.
16
-
- foster a community that encouraged contributions across a range of technologies.
17
-
- work on projects which the community want to improve.
13
+
- introduce developers to open-source projects and help them learn the ropes.
14
+
- foster a community which encouraged contributions across a range of technologies.
15
+
- work on projects which the community (i.e. YOU) want to improve.
18
16
19
17
Of course, that doesn't get away from the original question I had.
20
18
21
-
**Why a week?**
19
+
##Why a week?
22
20
23
21
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:
24
22
@@ -27,21 +25,22 @@ I had so many questions, but as we discussed it we started to come to something
27
25
- more variety of projects to work on - something different each week.
28
26
- with good organisation, each week should be productive out of the gate.
29
27
30
-
But there are some things we need to address first:
31
28
32
-
**What next?**
29
+
##What next?
33
30
34
-
We need to work out:
31
+
But there are some things we need to address first:
35
32
36
33
- how do we determine which projects to work on?
37
-
-[DVCS](http://en.wikipedia.org/wiki/Distributed_revision_control) is still a relatively new concept - how can we help getting new developers familiar with it?
38
-
- how do we organise each project? We want to give value both to the project owners and the contributors.
34
+
- how do we organise each project?
35
+
- how do we (as co-ordinators) deal with the skill gap between experienced and junior developers?
36
+
37
+
We want to **build fun stuff**, **give back** to the projects who have helped us over the years, and **create a community** 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.
39
38
40
-
We want to **build fun stuff**, **give back** to the projects who have helped us over the years, and **create a community** around our crazy ideas.
39
+
Do you have an project which suits this idea? [Vote on it](http://code52.uservoice.org)
41
40
42
-
So whatever your background and skillset, if you want to get involved and learn from others in the community, we'd love to hear from you.
41
+
Want to discuss your ideas and suggestions ? [Share it](http://code52.tenderapp.com)
43
42
44
-
So drop in on our [UserVoice](http://code52.uservoice.org) channel and suggest or vote on projects, discuss your ideas and suggestions on the [TenderApp](http://code52.tenderapp.com) site, and follow us on [Twitter](http://twitter.com/code52_org) to hear more about it.
43
+
Want to get in touch? Follow us on [Twitter](http://twitter/code_52)!
<contenttype="html"><p>I don't know which one of my co-conspirators came up with the idea, but it all started with a simple premise:</p>
23
+
<contenttype="html"><p>This all started with a simple premise:</p>
24
24
25
-
<p><strong>"A new coding project every week"</strong></p>
25
+
<h2>"A new coding project every week"</h2>
26
26
27
-
<p>Madness! Surely it couldn't be possible. What would that even involve?</p>
28
-
29
-
<p>I had so many questions, but as we discussed it we started to come to something resembling an agreement. We wanted to:</p>
27
+
<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. We wanted to:</p>
30
28
31
29
<ul>
32
-
<li>introduce more developers to open-source projects and help them learn the ropes.</li>
33
-
<li>foster a community that encouraged contributions across a range of technologies.</li>
34
-
<li>work on projects which the community want to improve.</li>
30
+
<li>introduce developers to open-source projects and help them learn the ropes.</li>
31
+
<li>foster a community which encouraged contributions across a range of technologies.</li>
32
+
<li>work on projects which the community (i.e. YOU) want to improve.</li>
35
33
</ul>
36
34
37
35
38
36
<p> Of course, that doesn't get away from the original question I had.</p>
39
37
40
-
<p><strong>Why a week?</strong></p>
38
+
<h2>Why a week?</h2>
41
39
42
40
<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>
43
41
@@ -49,24 +47,24 @@
49
47
</ul>
50
48
51
49
52
-
<p> But there are some things we need to address first:</p>
<p> But there are some things we need to address first:</p>
57
53
58
54
<ul>
59
55
<li>how do we determine which projects to work on?</li>
60
-
<li><a href="http://en.wikipedia.org/wiki/Distributed_revision_control">DVCS</a> is still a relatively new concept - how can we help getting new developers familiar with it?</li>
61
-
<li>how do we organise each project? We want to give value both to the project owners and the contributors.</li>
56
+
<li>how do we organise each project?</li>
57
+
<li>how do we (as co-ordinators) deal with the skill gap between experienced and junior developers?</li>
62
58
</ul>
63
59
64
60
65
-
<p> We want to <strong>build fun stuff</strong>, <strong>give back</strong> to the projects who have helped us over the years, and <strong>create a community</strong> around our crazy ideas.</p>
61
+
<p> We want to <strong>build fun stuff</strong>, <strong>give back</strong> to the projects who have helped us over the years, and <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>
62
+
63
+
<p> Do you have an project which suits this idea? <a href="http://code52.uservoice.org">Vote on it</a></p>
66
64
67
-
<p>So whatever your background and skillset, if you want to get involved and learn from others in the community, we'd love to hear from you.</p>
65
+
<p>Want to discuss your ideas and suggestions ? <a href="http://code52.tenderapp.com">Share it</a></p>
68
66
69
-
<p>So drop in on our <a href="http://code52.uservoice.org">UserVoice</a> channel and suggest or vote on projects, discuss your ideas and suggestions on the <a href="http://code52.tenderapp.com">TenderApp</a> site, and follow us on <a href="http://twitter.com/code52_org">Twitter</a> to hear more about it.</p>
67
+
<p>Want to get in touch? Follow us on <a href="http://twitter/code_52">Twitter</a>!</p>
<li><ahref="http://code52.uservoice.com">submit an idea</a></li>
24
+
21
25
<li><ahref="#">past ideas</a></li>
26
+
<li><ahref="#">wall of champions</a></li>
27
+
28
+
22
29
</ul>
30
+
</div>
31
+
23
32
</div>
24
33
<divid="content">
25
34
<ulclass="ideas">
@@ -35,24 +44,22 @@ <h1><a href="/introduction">An introduction to code52</a></h1>
35
44
</ul>
36
45
</div>
37
46
38
-
<p>I don't know which one of my co-conspirators came up with the idea, but it all started with a simple premise:</p>
39
-
40
-
<p><strong>"A new coding project every week"</strong></p>
47
+
<p>This all started with a simple premise:</p>
41
48
42
-
<p>Madness! Surely it couldn't be possible. What would that even involve?</p>
49
+
<h2>"A new coding project every week"</h2>
43
50
44
-
<p>I had so many questions, but as we discussed it we started to come to something resembling an agreement. We wanted to:</p>
51
+
<p>Madness! I was hooked and <ahref="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. We wanted to:</p>
45
52
46
53
<ul>
47
-
<li>introduce more developers to open-source projects and help them learn the ropes.</li>
48
-
<li>foster a community that encouraged contributions across a range of technologies.</li>
49
-
<li>work on projects which the community want to improve.</li>
54
+
<li>introduce developers to open-source projects and help them learn the ropes.</li>
55
+
<li>foster a community which encouraged contributions across a range of technologies.</li>
56
+
<li>work on projects which the community (i.e. YOU) want to improve.</li>
50
57
</ul>
51
58
52
59
53
60
<p> Of course, that doesn't get away from the original question I had.</p>
54
61
55
-
<p><strong>Why a week?</strong></p>
62
+
<h2>Why a week?</h2>
56
63
57
64
<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>
58
65
@@ -64,24 +71,24 @@ <h1><a href="/introduction">An introduction to code52</a></h1>
64
71
</ul>
65
72
66
73
67
-
<p> But there are some things we need to address first:</p>
68
-
69
-
<p><strong>What next?</strong></p>
74
+
<h2>What next?</h2>
70
75
71
-
<p>We need to work out:</p>
76
+
<p> But there are some things we need to address first:</p>
72
77
73
78
<ul>
74
79
<li>how do we determine which projects to work on?</li>
75
-
<li><ahref="http://en.wikipedia.org/wiki/Distributed_revision_control">DVCS</a> is still a relatively new concept - how can we help getting new developers familiar with it?</li>
76
-
<li>how do we organise each project? We want to give value both to the project owners and the contributors.</li>
80
+
<li>how do we organise each project?</li>
81
+
<li>how do we (as co-ordinators) deal with the skill gap between experienced and junior developers?</li>
77
82
</ul>
78
83
79
84
80
-
<p> We want to <strong>build fun stuff</strong>, <strong>give back</strong> to the projects who have helped us over the years, and <strong>create a community</strong> around our crazy ideas.</p>
85
+
<p> We want to <strong>build fun stuff</strong>, <strong>give back</strong> to the projects who have helped us over the years, and <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>
86
+
87
+
<p> Do you have an project which suits this idea? <ahref="http://code52.uservoice.org">Vote on it</a></p>
81
88
82
-
<p>So whatever your background and skillset, if you want to get involved and learn from others in the community, we'd love to hear from you.</p>
89
+
<p>Want to discuss your ideas and suggestions ? <ahref="http://code52.tenderapp.com">Share it</a></p>
83
90
84
-
<p>So drop in on our <ahref="http://code52.uservoice.org">UserVoice</a> channel and suggest or vote on projects, discuss your ideas and suggestions on the <ahref="http://code52.tenderapp.com">TenderApp</a> site, and follow us on <ahref="http://twitter.com/code52_org">Twitter</a> to hear more about it.</p>
91
+
<p>Want to get in touch? Follow us on <ahref="http://twitter/code_52">Twitter</a>!</p>
<p>I don't know which one of my co-conspirators came up with the idea, but it all started with a simple premise:</p>
34
-
35
-
<p><strong>"A new coding project every week"</strong></p>
42
+
<p>This all started with a simple premise:</p>
36
43
37
-
<p>Madness! Surely it couldn't be possible. What would that even involve?</p>
44
+
<h2>"A new coding project every week"</h2>
38
45
39
-
<p>I had so many questions, but as we discussed it we started to come to something resembling an agreement. We wanted to:</p>
46
+
<p>Madness! I was hooked and <ahref="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. We wanted to:</p>
40
47
41
48
<ul>
42
-
<li>introduce more developers to open-source projects and help them learn the ropes.</li>
43
-
<li>foster a community that encouraged contributions across a range of technologies.</li>
44
-
<li>work on projects which the community want to improve.</li>
49
+
<li>introduce developers to open-source projects and help them learn the ropes.</li>
50
+
<li>foster a community which encouraged contributions across a range of technologies.</li>
51
+
<li>work on projects which the community (i.e. YOU) want to improve.</li>
45
52
</ul>
46
53
47
54
48
55
<p> Of course, that doesn't get away from the original question I had.</p>
49
56
50
-
<p><strong>Why a week?</strong></p>
57
+
<h2>Why a week?</h2>
51
58
52
59
<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>
53
60
@@ -59,24 +66,24 @@ <h1> An introduction to code52 </h1>
59
66
</ul>
60
67
61
68
62
-
<p> But there are some things we need to address first:</p>
63
-
64
-
<p><strong>What next?</strong></p>
69
+
<h2>What next?</h2>
65
70
66
-
<p>We need to work out:</p>
71
+
<p> But there are some things we need to address first:</p>
67
72
68
73
<ul>
69
74
<li>how do we determine which projects to work on?</li>
70
-
<li><ahref="http://en.wikipedia.org/wiki/Distributed_revision_control">DVCS</a> is still a relatively new concept - how can we help getting new developers familiar with it?</li>
71
-
<li>how do we organise each project? We want to give value both to the project owners and the contributors.</li>
75
+
<li>how do we organise each project?</li>
76
+
<li>how do we (as co-ordinators) deal with the skill gap between experienced and junior developers?</li>
72
77
</ul>
73
78
74
79
75
-
<p> We want to <strong>build fun stuff</strong>, <strong>give back</strong> to the projects who have helped us over the years, and <strong>create a community</strong> around our crazy ideas.</p>
80
+
<p> We want to <strong>build fun stuff</strong>, <strong>give back</strong> to the projects who have helped us over the years, and <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>
81
+
82
+
<p> Do you have an project which suits this idea? <ahref="http://code52.uservoice.org">Vote on it</a></p>
76
83
77
-
<p>So whatever your background and skillset, if you want to get involved and learn from others in the community, we'd love to hear from you.</p>
84
+
<p>Want to discuss your ideas and suggestions ? <ahref="http://code52.tenderapp.com">Share it</a></p>
78
85
79
-
<p>So drop in on our <ahref="http://code52.uservoice.org">UserVoice</a> channel and suggest or vote on projects, discuss your ideas and suggestions on the <ahref="http://code52.tenderapp.com">TenderApp</a> site, and follow us on <ahref="http://twitter.com/code52_org">Twitter</a> to hear more about it.</p>
86
+
<p>Want to get in touch? Follow us on <ahref="http://twitter/code_52">Twitter</a>!</p>
0 commit comments