unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Gábor Boskovits" <boskovits@gmail.com>
To: "Asfaw, Nardos" <nasfaw@iu.edu>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>,
	"outreachy@lepiller.eu" <outreachy@lepiller.eu>
Subject: Re: New outreachy participant introduction
Date: Thu, 3 Oct 2019 21:18:18 +0200	[thread overview]
Message-ID: <CAE4v=pj1EC5ufe5EXLmYSW=cZsbKJ7jjtJppvXw4eHbHWiJ-WQ@mail.gmail.com> (raw)
In-Reply-To: <1570119118548.1674@iu.edu>

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

Hello Nardos,

Asfaw, Nardos <nasfaw@iu.edu> ezt írta (időpont: 2019. okt. 3., Cs, 18:13):

> Hello Guix!
>
> 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
>

Happy to see you here.


> 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?
>

This should work fine, but as Chris metioned, it might be easier to install
Guix as a package manager. One trick with the vm image is that it barely
contains enough space to be useful as is, so you will have to resize it.


> 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?
>

To open a new issue you can send a mail to either guix-patches or bug-guix
mailing list. Then the debbugs instance behind these lists creat a new
issue number for your request. Further mails should be sent to
issue-number@debbugs.gnu.org, where the issue number is in the
acknowledgement e-mail. You can see that later in an url like you posted at
issues.guix.gnu.org.

>
> 3. Any beginner tips? and a good place to start?
>
You could do some packaging, or go for an easy bug. In earlier rounds we
recommended to try to package some R stuff first, as R has a well working
importer. It is important to notice that there is a quite short deadline
for initial contribution, and having something in is strictly needed for
proceeding further. Therefore I would go for something really easy. Once
you have one contribution registered, we can find something that is nearer
to the project you are really interested in.

Another aspect is that doing a simple packaging will get you familiar with
the workflow and helps to check if everything is ok with the installation.

Also, if you have a particular project in mind please let us know.

>
> I look forward to working with you all.
>

I am also looking forward to working with you.

>
> Thanks,
>
> Nardos
>
Best regards,
g_bor

-- 
OpenPGP Key Fingerprint: 7988:3B9F:7D6A:4DBF:3719:0367:2506:A96C:CF63:0B21

[-- Attachment #2: Type: text/html, Size: 5715 bytes --]

  parent reply	other threads:[~2019-10-03 19:18 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
2019-10-03 19:18 ` Gábor Boskovits [this message]
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='CAE4v=pj1EC5ufe5EXLmYSW=cZsbKJ7jjtJppvXw4eHbHWiJ-WQ@mail.gmail.com' \
    --to=boskovits@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=nasfaw@iu.edu \
    --cc=outreachy@lepiller.eu \
    /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).