From: Jelle Licht <jlicht@fsfe.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Quiliro Ordonez Baca <quiliro@riseup.net>,
guix-devel <guix-devel@gnu.org>
Subject: Re: collaboration from students of a technical school
Date: Thu, 20 Jul 2017 17:26:36 +0200 [thread overview]
Message-ID: <CAPsKtf+xMyV1cEC6xH86bq8AyM9nz+ULY2jgvOrN7tbkc_GTtA@mail.gmail.com> (raw)
In-Reply-To: <877ez3tar5.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]
It could also be interesting to have the more software-engineering/devops
focused students
look at improving guix QA process.
They could work on technical solutions for making things more robust, as to
make sure
`master' is broken less often ;-). I have no specific ideas on how to
approach this though.
- Jelle
2017-07-20 16:59 GMT+02:00 Ludovic Courtès <ludo@gnu.org>:
> Hello,
>
> (Sorry for the late reply, Quiliro!)
>
> Alex Vong <alexvong1995@gmail.com> skribis:
>
> > I cannot speak for others on what are most needed in Guix. But here is a
> > page summurizing project ideas for Google Summer of Code 2017:
> > <https://libreplanet.org/wiki/Group:Guix/GSoC-2017>
>
> Yes, that’s a good start for developers.
>
> For translators, there are pointers on
> <https://gnu.org/s/guix/contribute/>. Basically, translation is handled
> by the Translation Project (TP). On the Guix side we simply grab
> updated translations (PO files) when the TP sends them to us.
>
> HTH!
>
> Ludo’.
>
>
[-- Attachment #2: Type: text/html, Size: 1728 bytes --]
next prev parent reply other threads:[~2017-07-20 15:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 22:27 collaboration from students of a technical school Quiliro Ordonez Baca
2017-07-20 10:24 ` Alex Vong
2017-07-20 14:59 ` Ludovic Courtès
2017-07-20 15:26 ` Jelle Licht [this message]
2017-07-20 23:39 ` Quiliro Ordonez Baca
2017-07-22 21:55 ` Ricardo Wurmus
2017-07-23 8:26 ` Catonano
2017-07-28 0:15 ` Adonay Felipe Nogueira
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=CAPsKtf+xMyV1cEC6xH86bq8AyM9nz+ULY2jgvOrN7tbkc_GTtA@mail.gmail.com \
--to=jlicht@fsfe.org \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=quiliro@riseup.net \
/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).