All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Yurii Shevtsov <ungetch@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [GSoC] Applying for conversion scripts to builtins
Date: Mon, 16 Mar 2015 19:03:16 +0100	[thread overview]
Message-ID: <vpqpp884y6z.fsf@anie.imag.fr> (raw)
In-Reply-To: <CAHLaBNJkL1CUJEk=cH=CLcDvZtoAr+PiCo2KHjfMLUKsugtRPA@mail.gmail.com> (Yurii Shevtsov's message of "Mon, 16 Mar 2015 18:49:59 +0200")

Yurii Shevtsov <ungetch@gmail.com> writes:

> I'm going to write for this idea. As I know good proposal should
> contain timeline and Todo estimations. What should I write in my
> proposal, since there is no clear plan for converting scripts to
> builtins. Thanks in advance!

The fact that there is no clear plan is part of the plan. The idea is
that how much can be converted depends highly on how the GSoC goes. You
already saw with your microproject that something apparently easy can be
harder than it seems.

See this thread for a discussion on the topic:

  http://thread.gmane.org/gmane.comp.version-control.git/264050/focus=21366

Now, it's up to you to make a good proposal, i.e. both convince people
that you can do a good job, and OTOH be realistic about what can be done
in a GSoC.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/

  reply	other threads:[~2015-03-16 18:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-16 16:49 [GSoC] Applying for conversion scripts to builtins Yurii Shevtsov
2015-03-16 18:03 ` Matthieu Moy [this message]
2015-03-17  0:22 ` Paul Tan
2015-03-17  1:34   ` Duy Nguyen
2015-03-17 11:56   ` Johannes Schindelin
2015-03-17 18:38     ` Junio C Hamano

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=vpqpp884y6z.fsf@anie.imag.fr \
    --to=matthieu.moy@grenoble-inp.fr \
    --cc=git@vger.kernel.org \
    --cc=ungetch@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 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.