unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Hello from new Outreachy applicant
Date: Mon, 12 Oct 2020 14:11:52 +0200	[thread overview]
Message-ID: <87tuuzr6d3.fsf@gnu.org> (raw)
In-Reply-To: <CAJ3okZ1Uh5O3H1eBFu7kbfbFuDe-+TiaOhTiYohKfo0YJOak_A@mail.gmail.com> (zimoun's message of "Fri, 9 Oct 2020 10:01:10 +0200")

Hi Lulu,

Welcome!  :-)

zimoun <zimon.toutoune@gmail.com> skribis:

> Basically, the key to success is communication.   Raise the hand _as
> soon as possible_.
>
> Then my advice is: everyday log what you are doing.  It may be only
> one or two lines, sometimes more.  Once a week (at least), collect the
> items and send me (privately) maybe with some patches or a branch to
> pull for testing.  The idea is to know your progress and your blocking
> points and then help you.  On a weekly or bi-weekly basis, voice (or
> video) chat with any mean which suits you (especially your timezone).

These sound like great ideas.

I would add that Outreachy is not just about technical contributions but
also about enabling the intern to become part of the group, possibly
serving as a model for contributors-to-be.  So I encourage you to
interact with the wider group in addition to your mentor, I think it can
be beneficial to all of us.

Thanks for joining!

Ludo’.


      reply	other threads:[~2020-10-12 12:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-07 17:16 Hello from new Outreachy applicant Lulu
2020-10-07 21:51 ` Brett Gilio
2020-10-08 15:04   ` Lulu
2020-10-08 21:40 ` zimoun
2020-10-09  3:40   ` Lulu
2020-10-09  8:00     ` Gábor Boskovits
2020-10-09  8:18       ` zimoun
2020-10-09  8:01     ` zimoun
2020-10-12 12:11       ` Ludovic Courtès [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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87tuuzr6d3.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=zimon.toutoune@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.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).