All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Guthro <ben.guthro@gmail.com>
To: "lars.kurth@xen.org" <lars.kurth@xen.org>
Cc: "xen-arm@lists.xen.org" <xen-arm@lists.xen.org>,
	"xen-api@lists.xen.org" <xen-api@lists.xen.org>,
	Ben Guthro <ben@guthro.net>,
	"cl-mirage@lists.cam.ac.uk" <cl-mirage@lists.cam.ac.uk>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [Input needed, open until Monday Aug 12th] Should we have an invite only, 1/2 day developer meeting before Xen Developer Summit (i.e. in the afternoon of October 23, Edinburgh, UK)
Date: Mon, 5 Aug 2013 10:07:15 -0400	[thread overview]
Message-ID: <1986823640401750417@unknownmsgid> (raw)
In-Reply-To: <51FFB144.1060204@xen.org>

On Aug 5, 2013, at 10:06 AM, Lars Kurth <lars.kurth@xen.org> wrote:

> On 05/08/2013 14:07, Ben Guthro wrote:
>> If someone (such as myself) has interest in this event, but was not on an 'invite only' list in the past, are you looking for such feedback?
> It is invite only in the sense of the Hackathons, where we have limited space. What we do there is
> a) Anybody can request an invite
> b) If it somebody who is totally unknown in the community asks for an invite, we will likely put them onto a waiting list
> c) People who are known and have contributed will get an invite
> d) If we still have space we go through the waiting list and see how/whether they can fit in
>
> To answer your question: anybody who is active on these lists and wants to attend should be able to get a space. The only possibility where we don't have enough space is if say 20 people say they want to come replying to the thread, I book space for 30 and then 60 people request an invite. In practice this isn't likely though.
>
> Does this answer your question?

Yes, thank you for clarification

Ben


>
> Regards
> Lars

  parent reply	other threads:[~2013-08-05 14:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <51FF91CA.7050501@xen.org>
2013-08-05 12:59 ` [Input needed, open until Monday Aug 12th] Should we have an invite only, 1/2 day developer meeting before Xen Developer Summit (i.e. in the afternoon of October 23, Edinburgh, UK) Jan Beulich
2013-08-05 13:07 ` Ben Guthro
2013-08-05 14:05   ` Lars Kurth
     [not found]   ` <51FFB144.1060204@xen.org>
2013-08-05 14:07     ` Ben Guthro [this message]
2013-08-05 13:28 ` Daniel Kiper
     [not found] ` <alpine.DEB.2.02.1308051452180.4893@kaball.uk.xensource.com>
2013-08-05 13:59   ` [XenARM] " Lars Kurth
2013-08-05 14:00     ` Stefano Stabellini
2013-08-05 14:18 ` George Dunlap
2013-08-05 15:03 ` Ian Campbell
2013-08-05 15:52 ` Konrad Rzeszutek Wilk
     [not found] ` <CAGU+autUuo7qXvxYKm-EGuvOadmfvca=0sYVyQMvTJabQXfXXA@mail.gmail.com>
2013-08-05 22:11   ` Aravindh Puthiyaparambil (aravindp)
2013-08-06  5:10 ` Matt Wilson
2013-08-06  7:04 ` Dario Faggioli
     [not found] ` <1375772671.9712.64.camel@Abyss>
2013-08-08 10:59   ` Lars Kurth
     [not found]   ` <520379F8.7010505@xen.org>
2013-09-09 17:54     ` Ben Guthro
2013-09-09 18:31 lars.kurth@xen.org
  -- strict thread matches above, loose matches on Subject: below --
2013-08-05 11:51 Lars Kurth

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=1986823640401750417@unknownmsgid \
    --to=ben.guthro@gmail.com \
    --cc=ben@guthro.net \
    --cc=cl-mirage@lists.cam.ac.uk \
    --cc=lars.kurth@xen.org \
    --cc=xen-api@lists.xen.org \
    --cc=xen-arm@lists.xen.org \
    --cc=xen-devel@lists.xen.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 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.