unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: Ancon Paul <anconpaul1@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Applying of Outreachy Intern for GNU Guix on Create user video documentation
Date: Mon, 5 Nov 2018 18:27:23 +0100	[thread overview]
Message-ID: <20181105182723.15af2b3b@alma-ubu> (raw)
In-Reply-To: <CAEmmVH1XxH_PKfUDtEDp1nCy1xrhOZpkzwRwFRBDZt0HOz1VtQ@mail.gmail.com>

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

On Sun, 4 Nov 2018 23:52:33 +0600
Ancon Paul <anconpaul1@gmail.com> wrote:

> Hello team,
> 
> I'm a Bolaram Paul, I'm a web developer and  graphic designer . I'd
> like to contribute on GNU Guix as a Outreachy Intern. I've experience
> with few video editing and effect collaboration softwares and
> whiteboard animation technics . Hope i'll be create some good video
> tutorials for GNU Guix.


Hello Paul,

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:27 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CAEmmVH1XxH_PKfUDtEDp1nCy1xrhOZpkzwRwFRBDZt0HOz1VtQ@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=20181105182723.15af2b3b@alma-ubu \
    --to=bjoern.hoefling@bjoernhoefling.de \
    --cc=anconpaul1@gmail.com \
    --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 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).