all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Gábor Boskovits" <boskovits@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Outreachy timeline and status report
Date: Fri, 7 Feb 2020 23:02:58 +0100	[thread overview]
Message-ID: <CAE4v=pgiJNqj3nMRGKc2P2_kDyMOEvf4fZqfifXuDyhMXE8b4g@mail.gmail.com> (raw)
In-Reply-To: <87h8022jln.fsf@gnu.org>

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

Hello,

Ludovic Courtès <ludo@gnu.org> ezt írta (időpont: 2020. febr. 7., Pén
22:06):

> Hi Gábor,
>
> Gábor Boskovits <boskovits@gmail.com> skribis:
>
> > The timeline is available here:
> > https://www.outreachy.org/apply/project-selection/
> >
> > Every date refers to 4 p.m. UTC that day.
> >
> > We kindly request proposals to be available by the 11th of February,
> > so that it will be possible to promote them on the Outreachy Twitter
> > chat.
> >
> > Please remind prospective applicants, that the initial application
> > deadline is the 25th of February.
>
> Thanks for sharing.  If you want we can add another post on the web site
> by then to publicize the offer.  WDYT?  Any other ways we could spread
> the news?
>

I intend to write up a blogpost and publish it on Monday. We also have the
twitter chat.


> BTW, i18n for the Guix Data Service is no longer listed as a project.
> Is that intentional?
>

It got in not long ago. It was already approved. At the time on the first
writing the proposal was not uploaded yet.


> Thank you!
>
> Ludo’.
>

Best regards,
g_bor

>

[-- Attachment #2: Type: text/html, Size: 2549 bytes --]

      reply	other threads:[~2020-02-07 22:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-05 10:12 Outreachy timeline and status report Gábor Boskovits
2020-02-07 21:06 ` Ludovic Courtès
2020-02-07 22:02   ` Gábor Boskovits [this message]

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='CAE4v=pgiJNqj3nMRGKc2P2_kDyMOEvf4fZqfifXuDyhMXE8b4g@mail.gmail.com' \
    --to=boskovits@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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.