From: Catonano <catonano@gmail.com>
To: Quiliro Ordonez Baca <quiliro@riseup.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: collaboration from students of a technical school
Date: Sun, 23 Jul 2017 10:26:06 +0200 [thread overview]
Message-ID: <CAJ98PDx==9qxQ_K+_c+u2OR=TWO6oNR2Of+3x4Y3TkWz6-Yj0w@mail.gmail.com> (raw)
In-Reply-To: <871sp8l9oo.fsf@riseup.net>
[-- Attachment #1: Type: text/plain, Size: 2036 bytes --]
2017-07-21 1:39 GMT+02:00 Quiliro Ordonez Baca <quiliro@riseup.net>:
>
> > Quiliro Ordonez Baca <quiliro@riseup.net> writes:
> >
> >> I spoke with the director of a technical school (small universtity) that
> >> offers degrees in computer science. He said he could establish
> collaboration in
> >> free software projects as part of the syllabus for the students. I
> could ask
> >> them to contribute to Guix.
> >> What tasks should I ask them to do? They
> >> must collaborate between 80, 120 and 800 hours before graduating,
> >> depending on their area of study. There are students of languages
> >> too. Perhaps they can add the descriptions to the packages. Maybe
> >> editorial contributions to the manual or contributing to the
> >> translations. Descriptions could indeed be translated:
> >> LANG=fr_FR.utf-8 guix package --show=hello
> >>
> >> We could also ask them to have a hydra mirror or another server for
> >> Guix.
> >>
> >> It would be nice to have a list of TODO tasks...with knowledge
> >> dependencies specified in order to have them done by contributors. I
> >> think that easy tasks are a great way to help motivate people to learn
> >> more in order to contribute with the harder tasks later. Is there a
> >> place where tasks are described?
>
> Alex Vong <alexvong1995@gmail.com> writes:
>
> > Hello,
> >
> > 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>
>
> Thank you very much, Alex. Will this mean that Google will provide
> funding or it is just the task to take into consideration? Of course
> that I think that the later is more important. But I just need to know
> the considerations about the financing.
>
>
Apart from the ideas indicated above, I would like to suggest the simple
task of creating new packages and new services.
It's basic but II don't know the skills leve of these students. It might be
a good introduction to Guix, Guile, Scheme
[-- Attachment #2: Type: text/html, Size: 2917 bytes --]
next prev parent reply other threads:[~2017-07-23 8: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
2017-07-20 23:39 ` Quiliro Ordonez Baca
2017-07-22 21:55 ` Ricardo Wurmus
2017-07-23 8:26 ` Catonano [this message]
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='CAJ98PDx==9qxQ_K+_c+u2OR=TWO6oNR2Of+3x4Y3TkWz6-Yj0w@mail.gmail.com' \
--to=catonano@gmail.com \
--cc=guix-devel@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).