| 1 |
On Tue, Mar 17, 2009 at 10:59 AM, Eitan Mosenkis <eitan@××××××××.net> wrote: |
| 2 |
>> Probably git <http://git-scm.com/>. That's what most people in Gentoo |
| 3 |
>> use for new, standalone projects these days. |
| 4 |
> |
| 5 |
> |
| 6 |
> So here's a totally useless patch on gstats.git attached. |
| 7 |
> |
| 8 |
|
| 9 |
lrn2use `git format-patch`. Now, send us one! </joke> |
| 10 |
|
| 11 |
Seriously though, the purpose behind all this is not *just* to show |
| 12 |
that you can edit files or create diffs, since those are the most |
| 13 |
*basic* necessities which we'll assume you're aware of, and if we find |
| 14 |
out otherwise at a later stage... |
| 15 |
|
| 16 |
The most important thing IMO is to be able to show that you're |
| 17 |
actually interested in seeing this whole thing through till the end. |
| 18 |
Your purpose should not be to finish the project, but making sure that |
| 19 |
we're able to make use of it. That will involve more than just blind |
| 20 |
coding for the project. It requires (at least) the following: |
| 21 |
|
| 22 |
1. A drive to fix the issue or deficiency which the project aims at |
| 23 |
fixing ("scratching the itch") |
| 24 |
2. Keeping the project's goals, uses, and most importantly, *users* in mind |
| 25 |
3. Making sure others can contribute to the project with minimum |
| 26 |
barrier to entry |
| 27 |
* This involves social engineering, and good documentation + |
| 28 |
clean and simple code design |
| 29 |
|
| 30 |
Of course, there are *several* other desirable skills, but the |
| 31 |
all-encompassing one is the ability to "slurp up" skills on-the-fly, |
| 32 |
have an open mind (not so much that your brains fall out), and be |
| 33 |
gracious in criticism (but don't fall over yourself being gracious). |
| 34 |
|
| 35 |
|
| 36 |
Oh, and Arun will probably stab me if I don't mention this: DO NOT |
| 37 |
OVERENGINEER :) |
| 38 |
|
| 39 |
-- |
| 40 |
~Nirbheek Chauhan |
Archives