unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Joshua Branson <jbranso@dismail.de>
Cc: guix-devel@gnu.org, Luta Kalina <fufulomoffu@gmail.com>
Subject: Re: Outreachy internship
Date: Tue, 13 Oct 2020 23:51:18 +0200	[thread overview]
Message-ID: <87zh4px0a1.fsf@elephly.net> (raw)
In-Reply-To: <87sgah6dni.fsf@dismail.de>


Hi Joshua,

> I haven't really followed what others have proposed, but you could
> certainly get some ideas here:
>
> https://libreplanet.org/wiki/Group:Guix/GSoC-2020

It’s a good thought, but that’s not how it works for Outreachy.  We have
a number of Outreachy projects that internship candidates should be able
to see on the Outreachy website.  It’s separate from GSoC and operates
under different rules and guidelines.  However, that page is a good
source of ideas for Outreachy *mentors* in future internship rounds.

Hi Luta,

welcome to Guix!  Independent of the internship project you end up
choosing I recommend starting by installing Guix (as a package manager)
using the installer script at https://guix.gnu.org/install.sh and
familiarizing yourself with it e.g. by installing a package.  Once
you’re comfortable with the features Guix offers I suggest looking at
the Contributing section in the manual to set up an environment to make
your first contribution to Guix.

Be sure to ask for help on #guix whenever you feel something isn’t quite
clear.  At this point you really can’t go wrong by asking for help.
Getting started is the most important part and often the most difficult
hurdle, so we’d like to help you overcome it as quickly as possible.

-- 
Ricardo


  parent reply	other threads:[~2020-10-13 21:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-13 17:06 Outreachy internship Luta Kalina
2020-10-13 21:04 ` Joshua Branson
2020-10-13 21:07   ` Brett Gilio
2020-10-13 21:29     ` zimoun
2020-10-13 21:51   ` Ricardo Wurmus [this message]
2020-10-13 21:15 ` zimoun

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=87zh4px0a1.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=fufulomoffu@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=jbranso@dismail.de \
    /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).