|
6 | 6 | <atom:link href="http://www.Code52.org/rss.xml" rel="self" type="application/rss+xml" /> |
7 | 7 | <description></description> |
8 | 8 | <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> |
11 | 11 |
|
12 | 12 |
|
13 | 13 | <item> |
|
22 | 22 |
|
23 | 23 | <p>Madness! Surely it couldn't be possible. What would that even involve?</p> |
24 | 24 |
|
25 | | -<p>I had so many questions, but as we discussed it we started to come to something resembling an agreement.</p> |
26 | | - |
27 | | -<p>We wanted to:</p> |
| 25 | +<p>I had so many questions, but as we discussed it we started to come to something resembling an agreement. We wanted to:</p> |
28 | 26 |
|
29 | 27 | <ul> |
30 | 28 | <li>introduce more developers to open-source projects and help them learn the ropes.</li> |
|
37 | 35 |
|
38 | 36 | <p> <strong>Why a week?</strong></p> |
39 | 37 |
|
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 our group, but a week suits me because:</p> |
| 38 | +<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> |
41 | 39 |
|
42 | 40 | <ul> |
43 | 41 | <li>shorter timelines encourage achievable goals.</li> |
44 | 42 | <li>shorter timelines reduce the incentive to procrastinate.</li> |
45 | 43 | <li>more variety of projects to work on - something different each week.</li> |
46 | | -<li>with good organisation (i.e. us having our shit together), each week should be productive out of the gate.</li> |
| 44 | +<li>with good organisation, each week should be productive out of the gate.</li> |
47 | 45 | </ul> |
48 | 46 |
|
49 | 47 |
|
50 | | -<p> And yes, we're anticipating some hurdles getting something like this off the ground.</p> |
| 48 | +<p> But there are some things we need to address first:</p> |
51 | 49 |
|
52 | | -<p> <strong>What sort of hurdles?</strong></p> |
| 50 | +<p> <strong>What next?</strong></p> |
53 | 51 |
|
54 | | -<p>Given the variety of backgrounds and skillsets that developers have, we need to keep in mind:</p> |
| 52 | +<p>We need to work out:</p> |
55 | 53 |
|
56 | 54 | <ul> |
57 | | -<li>how do we determine which projects to work on</li> |
58 | | -<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> |
| 55 | +<li>how do we determine which projects to work on?</li> |
| 56 | +<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> |
| 57 | +<li>how do we organise each project? We want to give value both to the project owners and the contributors.</li> |
59 | 58 | </ul> |
60 | 59 |
|
| 60 | + |
| 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 our crazy ideas.</p> |
| 62 | + |
| 63 | +<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> |
| 64 | + |
| 65 | +<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> |
61 | 66 | </description> |
62 | 67 | </item> |
63 | 68 |
|
|
0 commit comments