unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: "Aurélien Aptel" <aurelien.aptel+emacs@gmail.com>
Cc: Emacs development discussions <emacs-devel@gnu.org>
Subject: Re: Google Summer of Code - some ideas
Date: Sun, 21 Apr 2013 19:25:12 +0200	[thread overview]
Message-ID: <87ehe3iyo7.fsf@bzg.ath.cx> (raw)
In-Reply-To: <CA+5B0FOGbY53P+c9DMMaYXPdWQsNQSuCQ7XX1VgDeF+Rvsysiw@mail.gmail.com> ("Aurélien Aptel"'s message of "Sun, 21 Apr 2013 19:16:47 +0200")

Hi Aurélien,

Aurélien Aptel <aurelien.aptel+emacs@gmail.com> writes:

> On Sun, Apr 21, 2013 at 6:46 PM, Aurélien Aptel
> <aurelien.aptel+emacs@gmail.com> wrote:
>> So, If an emacs hacker is interested in mentoring any of these
>> projects please manifest yourself :) !
>
> I should mention some things :
> - being a mentor does not take too much time (GSoC FAQ says 5 hours a
> week is a reasonable estimate).

Well, depends.

I was a not-so-good mentor last year because I had two students to
take care of (including you), and I think it does take time to be a
good one.

There is always this temptation to say "Well, you're a grown up,
just make progress and report blockages.  But I don't think it is
very effective -- I least I think we lost of lot of your precious
time and energy last year but relying to much on this.

> - a project can have multiple mentors (less work for each !)

... if they are well organized enough :)

> - I'll be asking most of my questions to the mailling list or the
> irc channel

That's very good.  When we switched to this way of working last
year I think it was more effective.

> As far as I know, anyone sufficiently involved in Emacs can mentor.
> You basically have to review my progress, give some advice when I'm
> stuck and check up on me if I don't give any news in a long time.

Let me insist on this: this is soft-mentoring and can work, but I
think "deep" mentoring would much more worth--both for you and for
the project.

> If you're still interested head to the GSoC webpage where you can
> register (you need a google account I think)
>
> http://www.google-melange.com/gsoc/homepage/google/gsoc2013

Another thing: one point about GSoC is to "recruit" new contributors
for the project.  I was happy with your contributions, but slightly
disappointed that you did not involve more into Org's community after
it was done: finishing the redmine sync, promoting your library, etc.

It's fine, because obviously there is no obligation here, and maybe
I was a bit naive about this -- I had this picture that finally we'll
work as a close team with all those new GSoC students (3 just for Org!)

Anyway, again, each mentor will have his expectation and I was faulty
of not having time enough for you.  And I'm sure you'll contribute
with great code and ideas, so I'd be happy to see you step onboard
again.

-- 
 Bastien



  reply	other threads:[~2013-04-21 17:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-21 16:46 Google Summer of Code - some ideas Aurélien Aptel
2013-04-21 17:16 ` Aurélien Aptel
2013-04-21 17:25   ` Bastien [this message]
2013-04-21 17:53     ` Aurélien Aptel
2013-04-21 23:05       ` Bastien
2013-04-21 18:34 ` joakim
2013-04-22 14:34 ` Stefan Monnier
2013-04-22 16:48   ` Eli Zaretskii
2013-04-23  3:23     ` Stefan Monnier
2013-04-22 17:51   ` Aurélien Aptel
2013-04-22 18:26     ` Eli Zaretskii
2013-04-22 20:16       ` Jérémie Courrèges-Anglas
2013-04-22 20:30         ` Eli Zaretskii
2013-04-22 20:39           ` Jérémie Courrèges-Anglas
2013-04-23  2:38             ` Eli Zaretskii
2013-04-23 16:21               ` Eli Zaretskii
2013-04-22 15:52 ` Lennart Borgman

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ehe3iyo7.fsf@bzg.ath.cx \
    --to=bzg@gnu.org \
    --cc=aurelien.aptel+emacs@gmail.com \
    --cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).