From: Stephan Beyer <s-beyer@gmx.net>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Lea Wiemann <lewiemann@gmail.com>,
git@vger.kernel.org, Sam Vilain <sam@vilain.net>,
Joshua Roys <roysjosh@gmail.com>,
Sverre Rabbelier <alturin@gmail.com>,
Sverre Rabbelier <sverre@rabbelier.nl>,
David Symonds <dsymonds@gmail.com>,
John Hawley <warthog19@eaglescrag.net>,
Marek Zawirski <marek.zawirski@gmail.com>,
"Shawn O. Pearce" <spearce@spearce.org>,
Miklos Vajna <vmiklos@frugalware.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Christian Couder <chriscool@tuxfamily.org>,
Daniel Barkalow <barkalow@iabervon.org>
Subject: Re: [GSoC] What is status of Git's Google Summer of Code 2008 projects?
Date: Sat, 16 Aug 2008 03:16:33 +0200 [thread overview]
Message-ID: <20080816011633.GC17121@leksak.fem-net> (raw)
In-Reply-To: <200808152236.56479.jnareb@gmail.com>
Hi,
Jakub Narebski wrote:
> Please remember that according to timeline in GSoC 2008 FAQ:
> http://code.google.com/opensource/gsoc/2008/faqs.html#0.1_timeline
> August 18: ~12 noon PDT / 19:00 UTC is "Firm 'pencils down' date."
> (suggested pencils down date was August 11). So you don't have much
> time, and you don't leave much time for review, so I guess evaluation
> would be "done, but nor merged in" or something like that.
I'm wondering about "and you don't leave much time for review".
A comment on this:
LH (from the Google Open Source Team) clarified that the state of
Aug 18 is not the date where everything should be reviewed and merged
in. It is the date where the (following) evaluation (done by the mentor)
of the code is based on.
See also
http://groups.google.com/group/google-summer-of-code-announce/browse_thread/thread/df7278c6e027dee1
Regards,
Stephan
--
Stephan Beyer <s-beyer@gmx.net>, PGP 0x6EDDD207FCC5040F
next prev parent reply other threads:[~2008-08-16 1:17 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-08 0:27 [GSoC] What is status of Git's Google Summer of Code 2008 projects? Jakub Narebski
2008-07-08 0:43 ` David Symonds
2008-07-08 1:00 ` Stephan Beyer
2008-07-08 1:14 ` Junio C Hamano
2008-07-08 1:47 ` Stephan Beyer
2008-07-08 7:39 ` Jakub Narebski
2008-07-08 14:42 ` Stephan Beyer
2008-07-08 16:12 ` Jakub Narebski
2008-07-08 16:34 ` Stephan Beyer
2008-07-08 17:31 ` Jakub Narebski
2008-07-08 4:08 ` Lea Wiemann
2008-07-08 7:20 ` J.H.
2008-07-08 4:19 ` Shawn O. Pearce
2008-07-08 16:31 ` Joshua Roys
2008-07-08 16:45 ` Johannes Schindelin
2008-07-08 17:22 ` Jakub Narebski
2008-07-08 17:00 ` Petr Baudis
2008-07-08 21:24 ` Sam Vilain
2008-07-09 10:18 ` Sverre Rabbelier
2008-07-09 10:56 ` Miklos Vajna
2008-07-09 11:36 ` Jakub Narebski
2008-07-20 22:29 ` Jakub Narebski
2008-07-20 22:43 ` Sverre Rabbelier
2008-07-20 22:57 ` Stephan Beyer
2008-07-21 0:55 ` Sam Vilain
2008-07-21 1:05 ` Johannes Schindelin
2008-07-21 10:23 ` Jakub Narebski
2008-07-21 10:40 ` Petr Baudis
2008-07-21 13:23 ` Joshua Roys
2008-07-21 3:22 ` Shawn O. Pearce
2008-08-17 5:26 ` Sverre Rabbelier
2008-08-14 2:57 ` Jakub Narebski
2008-08-14 12:42 ` Sam Vilain
2008-08-14 23:17 ` Petr Baudis
2008-08-14 23:23 ` Jakub Narebski
2008-08-14 23:04 ` Johannes Schindelin
2008-08-15 19:38 ` Lea Wiemann
2008-08-15 20:36 ` Jakub Narebski
2008-08-16 1:16 ` Stephan Beyer [this message]
2008-08-16 1:22 ` Shawn O. Pearce
2008-08-16 3:10 ` Jakub Narebski
2008-08-17 20:49 ` Marek Zawirski
2008-08-18 5:51 ` Shawn O. Pearce
2008-08-19 1:25 ` Joshua Roys
2008-08-20 6:19 ` Sam Vilain
2008-08-22 23:03 ` Stephan Beyer
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=20080816011633.GC17121@leksak.fem-net \
--to=s-beyer@gmx.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=alturin@gmail.com \
--cc=barkalow@iabervon.org \
--cc=chriscool@tuxfamily.org \
--cc=dsymonds@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=lewiemann@gmail.com \
--cc=marek.zawirski@gmail.com \
--cc=roysjosh@gmail.com \
--cc=sam@vilain.net \
--cc=spearce@spearce.org \
--cc=sverre@rabbelier.nl \
--cc=vmiklos@frugalware.org \
--cc=warthog19@eaglescrag.net \
/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).