Skip to content

Commit 699667b

Browse files
committed
Editing
1 parent 90c50d6 commit 699667b

File tree

5 files changed

+81
-53
lines changed

5 files changed

+81
-53
lines changed

_posts/2011-12-31-introduction.md

Lines changed: 18 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
---
22
layout: post
33
title: "An introduction to code52"
4+
author: shiftkey
45
---
56

67
I don't know which one of my co-conspirators came up with the idea, but it all started with a simple premise:
@@ -9,9 +10,7 @@ I don't know which one of my co-conspirators came up with the idea, but it all s
910

1011
Madness! Surely it couldn't be possible. What would that even involve?
1112

12-
I had so many questions, but as we discussed it we started to come to something resembling an agreement.
13-
14-
We wanted to:
13+
I had so many questions, but as we discussed it we started to come to something resembling an agreement. We wanted to:
1514

1615
- introduce more developers to open-source projects and help them learn the ropes.
1716
- foster a community that encouraged contributions across a range of technologies.
@@ -21,21 +20,30 @@ We wanted to:
2120

2221
**Why a week?**
2322

24-
A week isn't a long time - or it may be, depending on your perspective. This is still a somewhat contentious point within our group, but a week suits me because:
23+
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:
2524

2625
- shorter timelines encourage achievable goals.
2726
- shorter timelines reduce the incentive to procrastinate.
2827
- more variety of projects to work on - something different each week.
29-
- with good organisation (i.e. us having our shit together), each week should be productive out of the gate.
28+
- with good organisation, each week should be productive out of the gate.
29+
30+
But there are some things we need to address first:
31+
32+
**What next?**
33+
34+
We need to work out:
35+
36+
- 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.
39+
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.
3041

31-
And yes, we're anticipating some hurdles getting something like this off the ground.
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.
3243

33-
**What sort of hurdles?**
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.
3445

35-
Given the variety of backgrounds and skillsets that developers have, we need to keep in mind:
3646

37-
- how do we determine which projects to work on
38-
- [DVCS](http://en.wikipedia.org/wiki/Distributed_revision_control) is still a very new concept - how can we help getting new developers familiar with it
3947

4048

4149

_site/atom.xml

Lines changed: 16 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
<title>Code52</title>
44
<link href="http://www.Code52.org/"/>
55
<link type="application/atom+xml" rel="self" href="http://www.Code52.org/atom.xml"/>
6-
<updated>2011-12-16T20:46:48+11:00</updated>
6+
<updated>2011-12-16T21:12:09+11:00</updated>
77
<id>http://www.Code52.org/</id>
88
<author>
99
<name>Code52 Team</name>
@@ -26,9 +26,7 @@
2626

2727
&lt;p&gt;Madness! Surely it couldn't be possible. What would that even involve?&lt;/p&gt;
2828

29-
&lt;p&gt;I had so many questions, but as we discussed it we started to come to something resembling an agreement.&lt;/p&gt;
30-
31-
&lt;p&gt;We wanted to:&lt;/p&gt;
29+
&lt;p&gt;I had so many questions, but as we discussed it we started to come to something resembling an agreement. We wanted to:&lt;/p&gt;
3230

3331
&lt;ul&gt;
3432
&lt;li&gt;introduce more developers to open-source projects and help them learn the ropes.&lt;/li&gt;
@@ -41,27 +39,34 @@
4139

4240
&lt;p&gt; &lt;strong&gt;Why a week?&lt;/strong&gt;&lt;/p&gt;
4341

44-
&lt;p&gt; A week isn't a long time - or it may be, depending on your perspective. This is still a somewhat contentious point within our group, but a week suits me because:&lt;/p&gt;
42+
&lt;p&gt; 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:&lt;/p&gt;
4543

4644
&lt;ul&gt;
4745
&lt;li&gt;shorter timelines encourage achievable goals.&lt;/li&gt;
4846
&lt;li&gt;shorter timelines reduce the incentive to procrastinate.&lt;/li&gt;
4947
&lt;li&gt;more variety of projects to work on - something different each week.&lt;/li&gt;
50-
&lt;li&gt;with good organisation (i.e. us having our shit together), each week should be productive out of the gate.&lt;/li&gt;
48+
&lt;li&gt;with good organisation, each week should be productive out of the gate.&lt;/li&gt;
5149
&lt;/ul&gt;
5250

5351

54-
&lt;p&gt; And yes, we're anticipating some hurdles getting something like this off the ground.&lt;/p&gt;
52+
&lt;p&gt; But there are some things we need to address first:&lt;/p&gt;
5553

56-
&lt;p&gt; &lt;strong&gt;What sort of hurdles?&lt;/strong&gt;&lt;/p&gt;
54+
&lt;p&gt; &lt;strong&gt;What next?&lt;/strong&gt;&lt;/p&gt;
5755

58-
&lt;p&gt;Given the variety of backgrounds and skillsets that developers have, we need to keep in mind:&lt;/p&gt;
56+
&lt;p&gt;We need to work out:&lt;/p&gt;
5957

6058
&lt;ul&gt;
61-
&lt;li&gt;how do we determine which projects to work on&lt;/li&gt;
62-
&lt;li&gt;&lt;a href=&quot;http://en.wikipedia.org/wiki/Distributed_revision_control&quot;&gt;DVCS&lt;/a&gt; is still a very new concept - how can we help getting new developers familiar with it&lt;/li&gt;
59+
&lt;li&gt;how do we determine which projects to work on?&lt;/li&gt;
60+
&lt;li&gt;&lt;a href=&quot;http://en.wikipedia.org/wiki/Distributed_revision_control&quot;&gt;DVCS&lt;/a&gt; is still a relatively new concept - how can we help getting new developers familiar with it?&lt;/li&gt;
61+
&lt;li&gt;how do we organise each project? We want to give value both to the project owners and the contributors.&lt;/li&gt;
6362
&lt;/ul&gt;
6463

64+
65+
&lt;p&gt; We want to &lt;strong&gt;build fun stuff&lt;/strong&gt;, &lt;strong&gt;give back&lt;/strong&gt; to the projects who have helped us over the years, and &lt;strong&gt;create a community&lt;/strong&gt; around our crazy ideas.&lt;/p&gt;
66+
67+
&lt;p&gt; 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.&lt;/p&gt;
68+
69+
&lt;p&gt; So drop in on our &lt;a href=&quot;http://code52.uservoice.org&quot;&gt;UserVoice&lt;/a&gt; channel and suggest or vote on projects, discuss your ideas and suggestions on the &lt;a href=&quot;http://code52.tenderapp.com&quot;&gt;TenderApp&lt;/a&gt; site, and follow us on &lt;a href=&quot;http://twitter.com/code52_org&quot;&gt;Twitter&lt;/a&gt; to hear more about it.&lt;/p&gt;
6570
</content>
6671
</entry>
6772

_site/index.html

Lines changed: 15 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -41,9 +41,7 @@ <h1><a href="/introduction">An introduction to code52</a></h1>
4141

4242
<p>Madness! Surely it couldn't be possible. What would that even involve?</p>
4343

44-
<p>I had so many questions, but as we discussed it we started to come to something resembling an agreement.</p>
45-
46-
<p>We wanted to:</p>
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>
4745

4846
<ul>
4947
<li>introduce more developers to open-source projects and help them learn the ropes.</li>
@@ -56,28 +54,35 @@ <h1><a href="/introduction">An introduction to code52</a></h1>
5654

5755
<p> <strong>Why a week?</strong></p>
5856

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 our group, but a week suits me because:</p>
57+
<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>
6058

6159
<ul>
6260
<li>shorter timelines encourage achievable goals.</li>
6361
<li>shorter timelines reduce the incentive to procrastinate.</li>
6462
<li>more variety of projects to work on - something different each week.</li>
65-
<li>with good organisation (i.e. us having our shit together), each week should be productive out of the gate.</li>
63+
<li>with good organisation, each week should be productive out of the gate.</li>
6664
</ul>
6765

6866

69-
<p> And yes, we're anticipating some hurdles getting something like this off the ground.</p>
67+
<p> But there are some things we need to address first:</p>
7068

71-
<p> <strong>What sort of hurdles?</strong></p>
69+
<p> <strong>What next?</strong></p>
7270

73-
<p>Given the variety of backgrounds and skillsets that developers have, we need to keep in mind:</p>
71+
<p>We need to work out:</p>
7472

7573
<ul>
76-
<li>how do we determine which projects to work on</li>
77-
<li><a href="http://en.wikipedia.org/wiki/Distributed_revision_control">DVCS</a> is still a very new concept - how can we help getting new developers familiar with it</li>
74+
<li>how do we determine which projects to work on?</li>
75+
<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>
76+
<li>how do we organise each project? We want to give value both to the project owners and the contributors.</li>
7877
</ul>
7978

8079

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>
81+
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>
83+
84+
<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>
85+
8186
<br />
8287
<a href="/introduction#disqus_thread">Comments</a>
8388

_site/introduction.html

Lines changed: 15 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -36,9 +36,7 @@ <h1> An introduction to code52 </h1>
3636

3737
<p>Madness! Surely it couldn't be possible. What would that even involve?</p>
3838

39-
<p>I had so many questions, but as we discussed it we started to come to something resembling an agreement.</p>
40-
41-
<p>We wanted to:</p>
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>
4240

4341
<ul>
4442
<li>introduce more developers to open-source projects and help them learn the ropes.</li>
@@ -51,28 +49,35 @@ <h1> An introduction to code52 </h1>
5149

5250
<p> <strong>Why a week?</strong></p>
5351

54-
<p> A week isn't a long time - or it may be, depending on your perspective. This is still a somewhat contentious point within our group, but a week suits me because:</p>
52+
<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>
5553

5654
<ul>
5755
<li>shorter timelines encourage achievable goals.</li>
5856
<li>shorter timelines reduce the incentive to procrastinate.</li>
5957
<li>more variety of projects to work on - something different each week.</li>
60-
<li>with good organisation (i.e. us having our shit together), each week should be productive out of the gate.</li>
58+
<li>with good organisation, each week should be productive out of the gate.</li>
6159
</ul>
6260

6361

64-
<p> And yes, we're anticipating some hurdles getting something like this off the ground.</p>
62+
<p> But there are some things we need to address first:</p>
6563

66-
<p> <strong>What sort of hurdles?</strong></p>
64+
<p> <strong>What next?</strong></p>
6765

68-
<p>Given the variety of backgrounds and skillsets that developers have, we need to keep in mind:</p>
66+
<p>We need to work out:</p>
6967

7068
<ul>
71-
<li>how do we determine which projects to work on</li>
72-
<li><a href="http://en.wikipedia.org/wiki/Distributed_revision_control">DVCS</a> is still a very new concept - how can we help getting new developers familiar with it</li>
69+
<li>how do we determine which projects to work on?</li>
70+
<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>
71+
<li>how do we organise each project? We want to give value both to the project owners and the contributors.</li>
7372
</ul>
7473

7574

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>
76+
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>
78+
79+
<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>
80+
7681
</div>
7782
</div>
7883
<div id="page-navigation">

_site/rss.xml

Lines changed: 17 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -6,8 +6,8 @@
66
<atom:link href="http://www.Code52.org/rss.xml" rel="self" type="application/rss+xml" />
77
<description></description>
88
<language>en-au</language>
9-
<pubDate>Fri, 16 Dec 2011 20:46:48 +1100</pubDate>
10-
<lastBuildDate>Fri, 16 Dec 2011 20:46:48 +1100</lastBuildDate>
9+
<pubDate>Fri, 16 Dec 2011 21:12:09 +1100</pubDate>
10+
<lastBuildDate>Fri, 16 Dec 2011 21:12:09 +1100</lastBuildDate>
1111

1212

1313
<item>
@@ -22,9 +22,7 @@
2222

2323
&lt;p&gt;Madness! Surely it couldn't be possible. What would that even involve?&lt;/p&gt;
2424

25-
&lt;p&gt;I had so many questions, but as we discussed it we started to come to something resembling an agreement.&lt;/p&gt;
26-
27-
&lt;p&gt;We wanted to:&lt;/p&gt;
25+
&lt;p&gt;I had so many questions, but as we discussed it we started to come to something resembling an agreement. We wanted to:&lt;/p&gt;
2826

2927
&lt;ul&gt;
3028
&lt;li&gt;introduce more developers to open-source projects and help them learn the ropes.&lt;/li&gt;
@@ -37,27 +35,34 @@
3735

3836
&lt;p&gt; &lt;strong&gt;Why a week?&lt;/strong&gt;&lt;/p&gt;
3937

40-
&lt;p&gt; A week isn't a long time - or it may be, depending on your perspective. This is still a somewhat contentious point within our group, but a week suits me because:&lt;/p&gt;
38+
&lt;p&gt; 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:&lt;/p&gt;
4139

4240
&lt;ul&gt;
4341
&lt;li&gt;shorter timelines encourage achievable goals.&lt;/li&gt;
4442
&lt;li&gt;shorter timelines reduce the incentive to procrastinate.&lt;/li&gt;
4543
&lt;li&gt;more variety of projects to work on - something different each week.&lt;/li&gt;
46-
&lt;li&gt;with good organisation (i.e. us having our shit together), each week should be productive out of the gate.&lt;/li&gt;
44+
&lt;li&gt;with good organisation, each week should be productive out of the gate.&lt;/li&gt;
4745
&lt;/ul&gt;
4846

4947

50-
&lt;p&gt; And yes, we're anticipating some hurdles getting something like this off the ground.&lt;/p&gt;
48+
&lt;p&gt; But there are some things we need to address first:&lt;/p&gt;
5149

52-
&lt;p&gt; &lt;strong&gt;What sort of hurdles?&lt;/strong&gt;&lt;/p&gt;
50+
&lt;p&gt; &lt;strong&gt;What next?&lt;/strong&gt;&lt;/p&gt;
5351

54-
&lt;p&gt;Given the variety of backgrounds and skillsets that developers have, we need to keep in mind:&lt;/p&gt;
52+
&lt;p&gt;We need to work out:&lt;/p&gt;
5553

5654
&lt;ul&gt;
57-
&lt;li&gt;how do we determine which projects to work on&lt;/li&gt;
58-
&lt;li&gt;&lt;a href=&quot;http://en.wikipedia.org/wiki/Distributed_revision_control&quot;&gt;DVCS&lt;/a&gt; is still a very new concept - how can we help getting new developers familiar with it&lt;/li&gt;
55+
&lt;li&gt;how do we determine which projects to work on?&lt;/li&gt;
56+
&lt;li&gt;&lt;a href=&quot;http://en.wikipedia.org/wiki/Distributed_revision_control&quot;&gt;DVCS&lt;/a&gt; is still a relatively new concept - how can we help getting new developers familiar with it?&lt;/li&gt;
57+
&lt;li&gt;how do we organise each project? We want to give value both to the project owners and the contributors.&lt;/li&gt;
5958
&lt;/ul&gt;
6059

60+
61+
&lt;p&gt; We want to &lt;strong&gt;build fun stuff&lt;/strong&gt;, &lt;strong&gt;give back&lt;/strong&gt; to the projects who have helped us over the years, and &lt;strong&gt;create a community&lt;/strong&gt; around our crazy ideas.&lt;/p&gt;
62+
63+
&lt;p&gt; 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.&lt;/p&gt;
64+
65+
&lt;p&gt; So drop in on our &lt;a href=&quot;http://code52.uservoice.org&quot;&gt;UserVoice&lt;/a&gt; channel and suggest or vote on projects, discuss your ideas and suggestions on the &lt;a href=&quot;http://code52.tenderapp.com&quot;&gt;TenderApp&lt;/a&gt; site, and follow us on &lt;a href=&quot;http://twitter.com/code52_org&quot;&gt;Twitter&lt;/a&gt; to hear more about it.&lt;/p&gt;
6166
</description>
6267
</item>
6368

0 commit comments

Comments
 (0)