unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: "Essy Muthoni Mwangi" <mwangi.essy@students.jkuat.ac.ke>,
	"Gábor Boskovits" <boskovits@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: ENQUIRY ON ASSISTANCE ON CONTRIBUTION URL
Date: Mon, 5 Nov 2018 18:19:53 +0100	[thread overview]
Message-ID: <20181105181953.3af3c528@alma-ubu> (raw)
In-Reply-To: <CAOgY-dr-4k_rPnh1Pd1HvOFYEcwQ1u9W7hzBA=LmaLW1FpX5pA@mail.gmail.com>

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

On Mon, 5 Nov 2018 14:38:58 +0300
Essy Muthoni Mwangi <mwangi.essy@students.jkuat.ac.ke> wrote:

> Hello,
> I need help on how to submit my contribution specifically what to
> write on the Contribution URL on the " Create user video
> documentation for GNU Guix" i made a video on GuixSD installation .
> 
> Kindly advise soon,
> Essy Muthoni

Hello Essy,

we were a bit surprised to see a new face in this Outreachy round as
the application period ends tomorrow, to be specific at:

 Application deadline: Nov. 6, 2018 4pm UTC


The idea of the contribution was to install Guix, get familiar with it
and add a new package that is not yet part of Guix (importing one from
CRAN is generally considered easy). Creating a video documentation
should only be part of the internship and should follow the discussions
we head in this thread:

https://lists.gnu.org/archive/html/guix-devel/2018-10/msg00500.html

Would you like to give it a try?

If you have any further questions, please also put the
devel-mailinglist at least on CC, so other community members can
quickly answer.


Björn

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

           reply	other threads:[~2018-11-05 17:20 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CAOgY-dr-4k_rPnh1Pd1HvOFYEcwQ1u9W7hzBA=LmaLW1FpX5pA@mail.gmail.com>]

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=20181105181953.3af3c528@alma-ubu \
    --to=bjoern.hoefling@bjoernhoefling.de \
    --cc=boskovits@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=mwangi.essy@students.jkuat.ac.ke \
    /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).