From: Blackbeard <barbanegra+guix@posteo.mx>
To: guix-devel@gnu.org
Subject: [GSOC 2020] Introduction and asking for feedback
Date: Fri, 6 Mar 2020 00:33:53 -0600 [thread overview]
Message-ID: <3eff499a-b60a-6952-9e6f-0e3aa9fd337f@posteo.mx> (raw)
[-- Attachment #1: Type: text/plain, Size: 1294 bytes --]
Hello everyone,
My name is Alberto Flores, I am an student from Mexico, I've been part
of the
#guix IRC channel as 'happy_gnu' and 'Blackbeard'. I've used Guix for a
few years, both as a package manager and distribution.
I want to apply to Google Summer of Code. The ideas I am most interested are
a) for GNU Guix: 'Content-addressed protocol for substitutes' and b) for
GNU Shepherd: "Syntax and semantics of systemd units in the Shepherd",
because I have a feeling any of this two would improve the experience of
most
Guix users.
However, I would like to ask for feedback in which might be a better option,
I would like to chose a project that I can get help and the community is
interested in.
Any help with the project and proposal would be much appreciated.
I am open for other ideas too. I know Christopher Webber started a thread
about Guile based build-tool and it looks great, but it seems like a huge
project for me and I would not like to fail in case I were accepted.
On other notes, I'll be sending my first patch this weekend, I packaged
the game widelands and it works, hopefully it will be accepted.
I also plan to send patches to the manual, and participate as much as I can.
Thank you all for your feedback and comments.
Alberto
[-- Attachment #2: Type: text/html, Size: 1890 bytes --]
next reply other threads:[~2020-03-06 6:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 6:33 Blackbeard [this message]
2020-03-11 14:35 ` [GSOC 2020] Introduction and asking for feedback 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3eff499a-b60a-6952-9e6f-0e3aa9fd337f@posteo.mx \
--to=barbanegra+guix@posteo.mx \
--cc=guix-devel@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.