All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: Google Summer of Code '07 application
Date: Sat, 10 Mar 2007 12:39:04 -0500	[thread overview]
Message-ID: <20070310173904.GD29710@fieldses.org> (raw)
In-Reply-To: <20070309153934.GA1131@spearce.org>

On Fri, Mar 09, 2007 at 10:39:34AM -0500, Shawn O. Pearce wrote:
> "J. Bruce Fields" <bfields@fieldses.org> wrote:
> > On Thu, Mar 08, 2007 at 09:21:18PM -0500, Shawn O. Pearce wrote:
> > > I have updated the wiki with the final draft, and taken into account
> > > the copy editing that people were trying to do last night in parallel
> > > with me overwriting their changes all of the time.  ;-)
> > 
> > I see a few more minor language fixes--do you want them by wiki or
> > email?
> 
> Wiki would probably just be quicker.  Feel free to edit away.

OK, I did a little more editing.  A couple more changes to consider:

At

http://code.google.com/p/google-summer-of-code/wiki/AdviceforMentors

they suggest that smaller completed projects are easier to pick up than
larger unfinished work,  Makes sense to me.  That might suggest a
slightly different approach here:

	"In the unfortunate event that a student abandons and does not
	complete his/her GSoC project, the Git community will try to
	pick up and continue the work without the student.  This is one
	reason why we will require frequent publishing of project
	materials to repo.or.cz."

But I'm not sure what exactly--maybe say something about encouraging
small incremental steps?

Also they suggest that "students should not be forced to do anything
that other contributors do not do, so if the student wants to blog, let
them do so, but do not force them."  So maybe we should ditch the
"weekly project updates" requirement.  Those might not end up being very
substantive anyway.  Maybe replace that with some sort of private
communication with the mentor?  (And the irc office hours thing sounds
like a good idea too--might be worth mentioning.)

--b.

      parent reply	other threads:[~2007-03-10 17:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-08  5:07 Google Summer of Code '07 application Shawn O. Pearce
2007-03-09  2:21 ` Shawn O. Pearce
2007-03-09  6:01   ` J. Bruce Fields
2007-03-09 15:39     ` Shawn O. Pearce
2007-03-09 22:09       ` Junio C Hamano
2007-03-10  7:06         ` Andy Parkins
2007-03-10 17:39       ` J. Bruce Fields [this message]

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=20070310173904.GD29710@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=git@vger.kernel.org \
    --cc=spearce@spearce.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.