From: Michael Haggerty <mhagger@alum.mit.edu>
To: git discussion list <git@vger.kernel.org>
Cc: Sun He <sunheehnus@gmail.com>
Subject: Students: Please only do one microproject!
Date: Thu, 27 Feb 2014 22:20:09 +0100 [thread overview]
Message-ID: <530FAC09.3080403@alum.mit.edu> (raw)
Students,
Please don't solve more than one microproject. Since the coding part is
such a small part of a microproject, doing many is not much more
impressive than doing just one. And it takes quite a while to come up
with ideas for microprojects! (I can already see that we are running
out and will need more...)
Rather, please pick one microproject and do it *perfectly*. And after
you've done that, if you are still itching to do more, then get involved
in other ways, like
* Find *other* little (or big!) problems in the code and either fix them
or suggest them as additions to the list of microprojects for other
students to work on.
* Help review other people's patches--students' or anybody else's. A
well-thought-out code review is a very valuable thing.
* Fix other things, like documentation.
* Answer questions on the mailing list or in IRC.
* Write tests for bugs that people report on the mailing list.
etc. etc. In other words, do things that other people on the mailing
list do.
Thanks!
Michael
--
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/
reply other threads:[~2014-02-27 21:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=530FAC09.3080403@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=git@vger.kernel.org \
--cc=sunheehnus@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).