From: Jakub Narebski <jnareb@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
Ramkumar Ramachandra <artagnon@gmail.com>,
Avery Pennarun <apenwarr@gmail.com>,
Sverre Rabbelier <srabbelier@gmail.com>,
Git Mailing List <git@vger.kernel.org>,
Daniel Barkalow <barkalow@iabervon.org>,
Christian Couder <chriscool@tuxfamily.org>,
Stephan Beyer <s-beyer@gmx.net>,
"Shawn O. Pearce" <spearce@spearce.org>
Subject: Best example of GSoC student participation (was: Re: native-git-svn: A Summer of Code 2010 proposal)
Date: Sun, 21 Mar 2010 09:43:38 -0700 (PDT) [thread overview]
Message-ID: <m3ljdlk4nw.fsf_-_@localhost.localdomain> (raw)
In-Reply-To: <alpine.DEB.1.00.1003211236050.7596@pacific.mpi-cbg.de>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> The mistakes in the sequencer project were more than this. Not only was
> the development of the branch almost invisible, when it was done, it was
> basically with a comment "here it is, take it or leave it", and good
> suggestions as to improve the code went unheeded.
>
> That's why I suggested frequent progress reports on the mailing list.
> Of course, these reports should only be commented upon by people who are
> fully informed about the project, they should not be invitations to
> everybody and her dog to distract the student by putting in unreasonable
> or uninformed wishes.
By the way, which of the former GSoC students (and for which project)
can serve as the best example of good interaction with the git
community and with GSoC mentors?
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2010-03-21 16:43 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 17:18 native-git-svn: A Summer of Code 2010 proposal Ramkumar Ramachandra
2010-03-19 18:32 ` Avery Pennarun
2010-03-19 18:39 ` Sverre Rabbelier
2010-03-19 21:30 ` Avery Pennarun
2010-03-20 9:19 ` Ramkumar Ramachandra
2010-03-20 10:48 ` Johannes Schindelin
2010-03-20 20:34 ` Ramkumar Ramachandra
2010-03-20 20:55 ` Ramkumar Ramachandra
2010-03-20 21:04 ` Jonathan Nieder
2010-03-21 10:26 ` Johannes Schindelin
2010-03-21 11:08 ` Jonathan Nieder
2010-03-21 11:47 ` Johannes Schindelin
2010-03-21 12:25 ` Ramkumar Ramachandra
2010-03-21 12:31 ` Johannes Schindelin
2010-03-21 12:36 ` Sverre Rabbelier
2010-03-21 17:58 ` Jonathan Nieder
2010-03-22 0:33 ` Daniel Barkalow
2010-03-22 2:41 ` Christian Couder
2010-03-22 3:49 ` Ramkumar Ramachandra
2010-03-22 11:33 ` Johannes Schindelin
[not found] ` <f3271551003220643j3a726d09o2d3a078292fd8bf6@mail.gmail.com>
2010-03-22 19:52 ` Johannes Schindelin
2010-03-23 7:49 ` Ramkumar Ramachandra
2010-03-21 16:43 ` Jakub Narebski [this message]
2010-03-21 17:27 ` Best example of GSoC student participation Johannes Schindelin
2010-03-20 21:58 ` native-git-svn: A Summer of Code 2010 proposal Daniel Barkalow
2010-03-20 22:19 ` Ramkumar Ramachandra
2010-03-21 5:36 ` Ramkumar Ramachandra
2010-03-21 22:56 ` Daniel Barkalow
2010-03-21 17:08 ` Ilari Liusvaara
2010-03-21 7:40 ` Peter Baumann
2010-03-21 23:51 ` Dave Olszewski
2010-03-19 20:53 ` Jonathan Nieder
2010-03-19 21:00 ` Johannes Schindelin
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=m3ljdlk4nw.fsf_-_@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=apenwarr@gmail.com \
--cc=artagnon@gmail.com \
--cc=barkalow@iabervon.org \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=s-beyer@gmx.net \
--cc=spearce@spearce.org \
--cc=srabbelier@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).