unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: nasfaw@iu.edu
Cc: guix-devel@gnu.org
Subject: Re: New outreachy participant introduction
Date: Thu, 03 Oct 2019 18:29:23 +0100	[thread overview]
Message-ID: <878sq1pwjw.fsf@cbaines.net> (raw)
In-Reply-To: <1570119118548.1674@iu.edu>

[-- Attachment #1: Type: text/plain, Size: 2117 bytes --]


Asfaw, Nardos <nasfaw@iu.edu> writes:

> My name is Nardos, and I am an Outreachy participant from Indiana
> University, Bloomington. I am a first time open source contributor
> hopeful. I am excite to be here, but I will admit I am also a little
> nervous. I welcome feedback as I am here to learn from all of you. I
> can be reached at nasfaw@iu.edu or www.nardos.dev

Hello Nardos,

> I also have a few questions:
>
> 1. I am opting to run Guix in a virtual machine on a kali linux.  I
> have found this resource:
> https://guix.gnu.org/manual/en/html_node/Running-Guix-in-a-VM.html#Running-Guix-in-a-VM. Given
> your experience, would this cause a problem down the line? Any
> recommendation on running Guix in a virtual machine vs on my PC?

If you're happy installing Guix as a package manager within Kali, that
might be easier than using a virtual machine. Both approaches should
work though, and when you have an idea of what contributions you want to
make, then you can work out which approach will be easier.

> 2. Upon making contributions, where is it posted? and how do I see
> feedbacks? I have seen lists of open projects and discussion treads
> such as this (https://issues.guix.gnu.org/issue/22138) on the Guix
> patch tracker. Are these the issues we currently working on?

It depends on the contribution, but in general patches are sent to the
guix-patches@gnu.org email address, and then appear on the
https://issues.guix.info/ site. There's some relevant guidance here:

  https://guix.gnu.org/manual/en/html_node/Submitting-Patches.html#Submitting-Patches

> 3. Any beginner tips? and a good place to start?

I believe there are two Outreachy projects for Guix, so if you have a
particular one in mind, let us know.

If you're looking for where to begin contributing, it could be something
to do with one of the Outreachy projects, working on packages for Guix,
working on the documentation, fixing bugs, or something else.

But from your first question above, it looks like you've started in the
right place, getting Guix up and running on your machine is a
prerequisite to everything.

Chris

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 962 bytes --]

  reply	other threads:[~2019-10-03 17:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-03 16:11 New outreachy participant introduction Asfaw, Nardos
2019-10-03 17:29 ` Christopher Baines [this message]
2019-10-03 19:18 ` Gábor Boskovits
2019-10-05  9:28   ` Gábor Boskovits
2019-10-08  3:23     ` [External] " Asfaw, Nardos
2019-10-08  6:48       ` Christopher Baines
2019-10-08 13:24         ` zimoun
2019-10-13  0:41           ` Asfaw, Nardos
2019-10-16  8:00             ` Gábor Boskovits
2019-10-16 14:16               ` Asfaw, Nardos
2019-10-19 20:33                 ` Ludovic Courtès
2019-10-24 12:51                 ` Gábor Boskovits
2019-10-04 18:50 ` Julien Lepiller

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=878sq1pwjw.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=guix-devel@gnu.org \
    --cc=nasfaw@iu.edu \
    /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).