From: Lulu <me@erkin.party>
To: zimoun <zimon.toutoune@gmail.com>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Hello from new Outreachy applicant
Date: Fri, 9 Oct 2020 06:40:00 +0300 (TRT) [thread overview]
Message-ID: <1767246561.13337.1602214800667@office.mailbox.org> (raw)
In-Reply-To: <CAJ3okZ17qUKUET7_1Op+k3FRRov7rMR==fQT-KBiYMBULy46nQ@mail.gmail.com>
Hi Simon,
> Have you already tried GNU Guix? The package manager on foreign
> distro? The full Guix System?
> If yes, are you comfortable with? Feedback is very welcome. :-)
I tried Guix on a foreign distro but ran into some problems with
SELinux and locales. Do you recommend using GuixSD on a virtual
machine, or do you think a foreign installation would be easier for
development? I reckon a setup for internal development wouldn't be
the same as a setup for the end-user. I think I might need to work
directly from the trunk, so maybe I need to get familiar with
`guix environment' for testing? I'd appreciate some tips on this.
> Well, last but not least, what topic you may be interested in to work on?
I decided on the task to add a `guix git log' subcommand, out of the
two tasks on the Outreachy page. :-) [1]
Aside from that, can you tell me more about how this mentorship
process works? Is there a regular schedule with meetings or progress
reports or such?
[1]: https://www.outreachy.org/outreachy-december-2020-internship-round/communities/gnu-guix/#add-a-subcommand-showing-gnu-guix-history-of-all-p
--
Lulu
next prev parent reply other threads:[~2020-10-09 6:00 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 [this message]
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
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=1767246561.13337.1602214800667@office.mailbox.org \
--to=me@erkin.party \
--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).