unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Pjotr Prins <pjotr.public12@thebird.nl>
To: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: FOSDEM 2019 stand applications
Date: Fri, 23 Nov 2018 12:54:34 +0100	[thread overview]
Message-ID: <20181123115434.lkxen5umdwepnlhe@thebird.nl> (raw)
In-Reply-To: <20181123090242.65bcc4a9@alma-ubu>

On Fri, Nov 23, 2018 at 09:02:42AM +0100, Björn Höfling wrote:
> On Thu, 22 Nov 2018 23:16:47 -0600
> Brett Gilio <brettg@posteo.net> wrote:
> 
> 
> > Bummer,
> > 
> > Did they provide any more feedback so that we can be more prepared
> > next year as more likely candidates?
> 
> No.
> 
> I think in general there is the problem of high demand and only a
> fixed size of stands. I'm not sure if there is anything we could do to
> improve our application text. On FOSDEM I will be asking other stands
> how they did it, how much effort they put into it and what tricks they
> have.
> 
> Anyway, it was a first trial, we didn't put too much effort into it and
> we can now just concentrate on the 2 Guix-days before FOSDEM.
> 
> Björn

Yes, it is very competitive.

What we still can do is have promotional materials and provide them
through an existing stand. There are probably a few sympathetic to GNU
Guix. There are also some common tables we can use for that and (of
course) the minimalism devroom on Saturday.

Pj.

  reply	other threads:[~2018-11-23 12:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-22 22:28 Fw: FOSDEM 2019 stand applications Björn Höfling
2018-11-23  5:16 ` Brett Gilio
2018-11-23  8:02   ` Björn Höfling
2018-11-23 11:54     ` Pjotr Prins [this message]
2018-11-23 13:28       ` Ludovic Courtès
2018-11-23 18:49         ` Brett Gilio
2018-11-23 19:32           ` Ludovic Courtès
2018-11-23 19:35           ` Tobias Geerinckx-Rice
2018-11-24  1:04         ` Tonton

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=20181123115434.lkxen5umdwepnlhe@thebird.nl \
    --to=pjotr.public12@thebird.nl \
    --cc=bjoern.hoefling@bjoernhoefling.de \
    --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).