public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: k_f@gentoo.org
Cc: gentoo-project@lists.gentoo.org, Alec Warner <antarus@gentoo.org>
Subject: Re: [gentoo-project] Looking for ways the Foundation can accomplish its mission.
Date: Fri, 07 Sep 2018 15:42:03 +0200	[thread overview]
Message-ID: <3933023.NiAyXC3Sar@porto> (raw)
In-Reply-To: <36bb70a2-13e7-9c46-3173-17b880d3a143@gentoo.org>

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

Am Freitag, 7. September 2018, 15:20:36 CEST schrieb Kristian Fiskerstrand:
> On 9/7/18 3:11 PM, Andreas K. Huettel wrote:
> >>  - Fund talks about Gentoo development activities at industry
> >>  conferences.
> > 
> > Kinda makes sense. Getting some industry sponsors aboard would be nice.
> > That said, Gentoo's focus has been shifting from industry-oriented / USA
> > more to OSS-enthusiast-oriented / Europe recently. So we need to be
> > careful that this doesnt lead to conflicts.
> 
> We get these presentations for free at various conferences already, but
> I'm a bit unsure about what "fund talks about" means in this context,
> would it be purchasing stand place / sponsoring event so you also get
> talking spot kind of thing?

I guess this means dedicated industry workshops with an entrance fee too steep 
for the usual oss enthusiast.

-- 
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer 
(council, toolchain, perl, libreoffice, comrel)

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-09-07 13:42 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-06 12:47 [gentoo-project] Looking for ways the Foundation can accomplish its mission Alec Warner
2018-09-06 13:07 ` Raymond Jennings
2018-09-07  0:32   ` Richard Yao
2018-09-07  0:43     ` Richard Yao
2018-09-07  1:01     ` Rich Freeman
2018-09-07  1:47       ` Richard Yao
2018-09-07  2:15         ` M. J. Everitt
2018-09-06 13:14 ` Kristian Fiskerstrand
2018-09-06 13:39   ` Andrew Savchenko
2018-09-06 13:35 ` Andrew Savchenko
2018-09-06 15:52   ` Alec Warner
2018-09-06 20:32     ` Michael Orlitzky
2018-09-06 20:44       ` Raymond Jennings
2018-09-06 20:44       ` Alec Warner
2018-09-07  2:46       ` Yury German
2018-09-07  3:16         ` M. J. Everitt
2018-09-07  8:44     ` Andrew Savchenko
2018-09-06 13:54 ` M. J. Everitt
2018-09-06 15:22 ` Matthew Thode
2018-09-06 15:45   ` Rich Freeman
2018-09-06 16:14     ` M. J. Everitt
2018-09-06 16:31       ` Rich Freeman
2018-09-06 15:52   ` Michał Górny
2018-09-06 16:01     ` Matthew Thode
2018-09-06 18:02     ` Yury German
2018-09-06 18:35       ` Alec Warner
2018-09-06 19:32         ` Matthew Thode
2018-09-06 18:37       ` Rich Freeman
2018-09-06 19:34         ` Matthew Thode
2018-09-06 17:51   ` Kristian Fiskerstrand
2018-09-06 20:28   ` Paweł Hajdan, Jr.
2018-09-06 20:47 ` Thomas Deutschmann
2018-09-07 13:31   ` Rich Freeman
2018-09-07 14:07     ` Richard Yao
2018-09-07 14:10       ` Richard Yao
2018-09-07 14:22         ` Richard Yao
2018-09-07 13:11 ` Andreas K. Huettel
2018-09-07 13:20   ` Kristian Fiskerstrand
2018-09-07 13:42     ` Andreas K. Huettel [this message]
2018-09-07 13:24   ` Kristian Fiskerstrand
2018-09-07 13:41     ` Andreas K. Huettel

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=3933023.NiAyXC3Sar@porto \
    --to=dilfridge@gentoo.org \
    --cc=antarus@gentoo.org \
    --cc=gentoo-project@lists.gentoo.org \
    --cc=k_f@gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox