Skip to content

Commit 90c50d6

Browse files
shiftbotshiftbot
committed
refining the words
1 parent 8085757 commit 90c50d6

5 files changed

Lines changed: 106 additions & 56 deletions

File tree

‎_posts/2011-12-31-introduction.md‎

Lines changed: 15 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -5,36 +5,38 @@ title: "An introduction to code52"
55

66
I don't know which one of my co-conspirators came up with the idea, but it all started with a simple premise:
77

8-
"A new project every week"
8+
**"A new coding project every week"**
99

10-
Madness! Surely it couldn't be possible. What would that even involve? I had so many questions, but as we discussed it we started to come to something resembling an agreement.
10+
Madness! Surely it couldn't be possible. What would that even involve?
1111

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

14-
- to introduce more developers to open-source projects and help them learn the ropes.
15-
- to create a community that encouraged contributions across a broad range of technologies.
16-
- to work on projects which both the creators and community want to improve.
14+
We wanted to:
15+
16+
- introduce more developers to open-source projects and help them learn the ropes.
17+
- foster a community that encouraged contributions across a range of technologies.
18+
- work on projects which the community want to improve.
1719

1820
Of course, that doesn't get away from the original question I had.
1921

2022
**Why a week?**
2123

22-
Depending on your perspective, a week may be a long time - or it may not. This is still a contentious point within our group, but a week suits me because:
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:
2325

2426
- shorter timelines encourage achievable goals.
2527
- shorter timelines reduce the incentive to procrastinate.
2628
- more variety of projects to work on - something different each week.
2729
- with good organisation (i.e. us having our shit together), each week should be productive out of the gate.
2830

31+
And yes, we're anticipating some hurdles getting something like this off the ground.
2932

33+
**What sort of hurdles?**
3034

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

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
39+
3240

3341

3442

35-
36-
37-
38-
- lots of projects out there are in need of contributons
39-
- people have good ideas
40-

‎_site/atom.xml‎

Lines changed: 23 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:29:00+11:00</updated>
6+
<updated>2011-12-16T20:46:48+11:00</updated>
77
<id>http://www.Code52.org/</id>
88
<author>
99
<name>Code52 Team</name>
@@ -22,32 +22,44 @@
2222
</author>
2323
<content type="html">&lt;p&gt;I don't know which one of my co-conspirators came up with the idea, but it all started with a simple premise:&lt;/p&gt;
2424

25-
&lt;p&gt;&quot;A new project every week&quot;&lt;/p&gt;
25+
&lt;p&gt;&lt;strong&gt;&quot;A new coding project every week&quot;&lt;/strong&gt;&lt;/p&gt;
2626

27-
&lt;p&gt;Madness! Surely it couldn't be possible. What would that even involve? I had so many questions, but as we discussed it we started to come to something resembling an agreement.&lt;/p&gt;
27+
&lt;p&gt;Madness! Surely it couldn't be possible. What would that even involve?&lt;/p&gt;
2828

29-
&lt;p&gt;We wanted:&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.&lt;/p&gt;
30+
31+
&lt;p&gt;We wanted to:&lt;/p&gt;
3032

3133
&lt;ul&gt;
32-
&lt;li&gt;to introduce more developers to open-source projects and help them learn the ropes.&lt;/li&gt;
33-
&lt;li&gt;to create a community that encouraged contributions across a broad range of technologies.&lt;/li&gt;
34-
&lt;li&gt;to work on projects which both the creators and community want to improve.&lt;/li&gt;
34+
&lt;li&gt;introduce more developers to open-source projects and help them learn the ropes.&lt;/li&gt;
35+
&lt;li&gt;foster a community that encouraged contributions across a range of technologies.&lt;/li&gt;
36+
&lt;li&gt;work on projects which the community want to improve.&lt;/li&gt;
3537
&lt;/ul&gt;
3638

3739

3840
&lt;p&gt; Of course, that doesn't get away from the original question I had.&lt;/p&gt;
3941

4042
&lt;p&gt; &lt;strong&gt;Why a week?&lt;/strong&gt;&lt;/p&gt;
4143

42-
&lt;p&gt; Depending on your perspective, a week may be a long time - or it may not. This is still a contentious point within our group, but a week suits me because:&lt;/p&gt;
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;
4345

4446
&lt;ul&gt;
4547
&lt;li&gt;shorter timelines encourage achievable goals.&lt;/li&gt;
4648
&lt;li&gt;shorter timelines reduce the incentive to procrastinate.&lt;/li&gt;
4749
&lt;li&gt;more variety of projects to work on - something different each week.&lt;/li&gt;
48-
&lt;li&gt;&lt;p&gt;with good organisation (i.e. us having our shit together), each week should be productive out of the gate.&lt;/p&gt;&lt;/li&gt;
49-
&lt;li&gt;&lt;p&gt;lots of projects out there are in need of contributons&lt;/p&gt;&lt;/li&gt;
50-
&lt;li&gt;people have good ideas&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;
51+
&lt;/ul&gt;
52+
53+
54+
&lt;p&gt; And yes, we're anticipating some hurdles getting something like this off the ground.&lt;/p&gt;
55+
56+
&lt;p&gt; &lt;strong&gt;What sort of hurdles?&lt;/strong&gt;&lt;/p&gt;
57+
58+
&lt;p&gt;Given the variety of backgrounds and skillsets that developers have, we need to keep in mind:&lt;/p&gt;
59+
60+
&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;
5163
&lt;/ul&gt;
5264

5365
</content>

‎_site/index.html‎

Lines changed: 22 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -37,32 +37,44 @@ <h1><a href="/introduction">An introduction to code52</a></h1>
3737

3838
<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>
3939

40-
<p>"A new project every week"</p>
40+
<p><strong>"A new coding project every week"</strong></p>
4141

42-
<p>Madness! Surely it couldn't be possible. What would that even involve? I had so many questions, but as we discussed it we started to come to something resembling an agreement.</p>
42+
<p>Madness! Surely it couldn't be possible. What would that even involve?</p>
4343

44-
<p>We wanted:</p>
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>
4547

4648
<ul>
47-
<li>to introduce more developers to open-source projects and help them learn the ropes.</li>
48-
<li>to create a community that encouraged contributions across a broad range of technologies.</li>
49-
<li>to work on projects which both the creators and community want to improve.</li>
49+
<li>introduce more developers to open-source projects and help them learn the ropes.</li>
50+
<li>foster a community that encouraged contributions across a range of technologies.</li>
51+
<li>work on projects which the community want to improve.</li>
5052
</ul>
5153

5254

5355
<p> Of course, that doesn't get away from the original question I had.</p>
5456

5557
<p> <strong>Why a week?</strong></p>
5658

57-
<p> Depending on your perspective, a week may be a long time - or it may not. This is still a contentious point within our group, but a week suits me because:</p>
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>
5860

5961
<ul>
6062
<li>shorter timelines encourage achievable goals.</li>
6163
<li>shorter timelines reduce the incentive to procrastinate.</li>
6264
<li>more variety of projects to work on - something different each week.</li>
63-
<li><p>with good organisation (i.e. us having our shit together), each week should be productive out of the gate.</p></li>
64-
<li><p>lots of projects out there are in need of contributons</p></li>
65-
<li>people have good ideas</li>
65+
<li>with good organisation (i.e. us having our shit together), each week should be productive out of the gate.</li>
66+
</ul>
67+
68+
69+
<p> And yes, we're anticipating some hurdles getting something like this off the ground.</p>
70+
71+
<p> <strong>What sort of hurdles?</strong></p>
72+
73+
<p>Given the variety of backgrounds and skillsets that developers have, we need to keep in mind:</p>
74+
75+
<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>
6678
</ul>
6779

6880

‎_site/introduction.html‎

Lines changed: 22 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -32,32 +32,44 @@ <h1> An introduction to code52 </h1>
3232
</span>
3333
<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>
3434

35-
<p>"A new project every week"</p>
35+
<p><strong>"A new coding project every week"</strong></p>
3636

37-
<p>Madness! Surely it couldn't be possible. What would that even involve? I had so many questions, but as we discussed it we started to come to something resembling an agreement.</p>
37+
<p>Madness! Surely it couldn't be possible. What would that even involve?</p>
3838

39-
<p>We wanted:</p>
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>
4042

4143
<ul>
42-
<li>to introduce more developers to open-source projects and help them learn the ropes.</li>
43-
<li>to create a community that encouraged contributions across a broad range of technologies.</li>
44-
<li>to work on projects which both the creators and community want to improve.</li>
44+
<li>introduce more developers to open-source projects and help them learn the ropes.</li>
45+
<li>foster a community that encouraged contributions across a range of technologies.</li>
46+
<li>work on projects which the community want to improve.</li>
4547
</ul>
4648

4749

4850
<p> Of course, that doesn't get away from the original question I had.</p>
4951

5052
<p> <strong>Why a week?</strong></p>
5153

52-
<p> Depending on your perspective, a week may be a long time - or it may not. This is still a contentious point within our group, but a week suits me because:</p>
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>
5355

5456
<ul>
5557
<li>shorter timelines encourage achievable goals.</li>
5658
<li>shorter timelines reduce the incentive to procrastinate.</li>
5759
<li>more variety of projects to work on - something different each week.</li>
58-
<li><p>with good organisation (i.e. us having our shit together), each week should be productive out of the gate.</p></li>
59-
<li><p>lots of projects out there are in need of contributons</p></li>
60-
<li>people have good ideas</li>
60+
<li>with good organisation (i.e. us having our shit together), each week should be productive out of the gate.</li>
61+
</ul>
62+
63+
64+
<p> And yes, we're anticipating some hurdles getting something like this off the ground.</p>
65+
66+
<p> <strong>What sort of hurdles?</strong></p>
67+
68+
<p>Given the variety of backgrounds and skillsets that developers have, we need to keep in mind:</p>
69+
70+
<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>
6173
</ul>
6274

6375

‎_site/rss.xml‎

Lines changed: 24 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:29:00 +1100</pubDate>
10-
<lastBuildDate>Fri, 16 Dec 2011 20:29:00 +1100</lastBuildDate>
9+
<pubDate>Fri, 16 Dec 2011 20:46:48 +1100</pubDate>
10+
<lastBuildDate>Fri, 16 Dec 2011 20:46:48 +1100</lastBuildDate>
1111

1212

1313
<item>
@@ -18,32 +18,44 @@
1818
<guid>http://www.Code52.org/introduction</guid>
1919
<description>&lt;p&gt;I don't know which one of my co-conspirators came up with the idea, but it all started with a simple premise:&lt;/p&gt;
2020

21-
&lt;p&gt;&quot;A new project every week&quot;&lt;/p&gt;
21+
&lt;p&gt;&lt;strong&gt;&quot;A new coding project every week&quot;&lt;/strong&gt;&lt;/p&gt;
2222

23-
&lt;p&gt;Madness! Surely it couldn't be possible. What would that even involve? I had so many questions, but as we discussed it we started to come to something resembling an agreement.&lt;/p&gt;
23+
&lt;p&gt;Madness! Surely it couldn't be possible. What would that even involve?&lt;/p&gt;
2424

25-
&lt;p&gt;We wanted:&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.&lt;/p&gt;
26+
27+
&lt;p&gt;We wanted to:&lt;/p&gt;
2628

2729
&lt;ul&gt;
28-
&lt;li&gt;to introduce more developers to open-source projects and help them learn the ropes.&lt;/li&gt;
29-
&lt;li&gt;to create a community that encouraged contributions across a broad range of technologies.&lt;/li&gt;
30-
&lt;li&gt;to work on projects which both the creators and community want to improve.&lt;/li&gt;
30+
&lt;li&gt;introduce more developers to open-source projects and help them learn the ropes.&lt;/li&gt;
31+
&lt;li&gt;foster a community that encouraged contributions across a range of technologies.&lt;/li&gt;
32+
&lt;li&gt;work on projects which the community want to improve.&lt;/li&gt;
3133
&lt;/ul&gt;
3234

3335

3436
&lt;p&gt; Of course, that doesn't get away from the original question I had.&lt;/p&gt;
3537

3638
&lt;p&gt; &lt;strong&gt;Why a week?&lt;/strong&gt;&lt;/p&gt;
3739

38-
&lt;p&gt; Depending on your perspective, a week may be a long time - or it may not. This is still a contentious point within our group, but a week suits me because:&lt;/p&gt;
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;
3941

4042
&lt;ul&gt;
4143
&lt;li&gt;shorter timelines encourage achievable goals.&lt;/li&gt;
4244
&lt;li&gt;shorter timelines reduce the incentive to procrastinate.&lt;/li&gt;
4345
&lt;li&gt;more variety of projects to work on - something different each week.&lt;/li&gt;
44-
&lt;li&gt;&lt;p&gt;with good organisation (i.e. us having our shit together), each week should be productive out of the gate.&lt;/p&gt;&lt;/li&gt;
45-
&lt;li&gt;&lt;p&gt;lots of projects out there are in need of contributons&lt;/p&gt;&lt;/li&gt;
46-
&lt;li&gt;people have good ideas&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;
47+
&lt;/ul&gt;
48+
49+
50+
&lt;p&gt; And yes, we're anticipating some hurdles getting something like this off the ground.&lt;/p&gt;
51+
52+
&lt;p&gt; &lt;strong&gt;What sort of hurdles?&lt;/strong&gt;&lt;/p&gt;
53+
54+
&lt;p&gt;Given the variety of backgrounds and skillsets that developers have, we need to keep in mind:&lt;/p&gt;
55+
56+
&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;
4759
&lt;/ul&gt;
4860

4961
</description>

0 commit comments

Comments
 (0)