From mboxrd@z Thu Jan 1 00:00:00 1970 From: Neil Sikka Subject: Re: Do people want a Developer Meeting on Aug 24th (before Dev Summit) Date: Wed, 24 Aug 2016 09:01:30 -0400 Message-ID: References: <7a695a45-52e8-ad80-950c-9b261fcf3098@citrix.com> <4C21178E-5FE0-4B51-A6A2-85BA50B29ADA@gmail.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4893880963184614203==" Return-path: Received: from mail6.bemta6.messagelabs.com ([193.109.254.103]) by lists.xenproject.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bcXpA-00038S-DR for xen-devel@lists.xenproject.org; Wed, 24 Aug 2016 13:02:32 +0000 Received: by mail-it0-f43.google.com with SMTP id f6so31647124ith.0 for ; Wed, 24 Aug 2016 06:01:51 -0700 (PDT) In-Reply-To: <4C21178E-5FE0-4B51-A6A2-85BA50B29ADA@gmail.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xen.org Sender: "Xen-devel" To: Lars Kurth Cc: Xen-devel , committers@xenproject.org, George Dunlap List-Id: xen-devel@lists.xenproject.org --===============4893880963184614203== Content-Type: multipart/alternative; boundary=94eb2c05d0fa7b3d5d053ad0e2ce --94eb2c05d0fa7b3d5d053ad0e2ce Content-Type: text/plain; charset=UTF-8 Hey guys, is anything happening today regarding a meeting or going out for lunch if people arrive a day early? On Thu, Jun 23, 2016 at 8:43 AM, Lars Kurth wrote: > > > On 23 Jun 2016, at 12:39, George Dunlap > wrote: > > > > On 23/06/16 12:33, Lars Kurth wrote: > >> Folks, > >> > >> do you guys want to hold a Developer Meeting on Aug 24th (before Dev > Summit). I do have space to do this, but last year's was very poorly > attended. If you could get back to me with an opinion, that would help > hugely. Alternatively it would also be possible to use the space for more > focused meetings with fewer people. In that case, I would need a number of > suggestions for meetings including meeting leaders. > >> > >> Please have a look at the schedule http://events.linuxfoundation. > org/events/xen-project-developer-summit/program/schedule ... note that on > the 26th, I kept the 2nd room free and was planning to use the Hackathon > format in parallel to the talks in the main program. rather than having > BoFs interspersed with talks. Some of the slots could be used to host the > developer meeting, of desired. > > > > So to a large degree, the actual nuts-and-bolts planning which that > > meeting was meant to cover happens now at the "hackathons" instead. > > It's important I think, however, for the XenSummit to have a venue for > > people in the industry who may not know about the Hackathons (or for > > whatever reason can't come to them) to raise issues with the core > > developers and have them discussed. > > > > If the parallel track could actually fulfill that role, then I think it > > would be enough; the key would be making sure that the appropriate > > attention could be attracted. > > That's why I asked. Maybe we can come up with a short list of topics that > need to be discussed and are worthwhile for the developer meetings. > > The idea behind using the Hackathon scheduling methodology for the > parallel track is an experiment to make assigning of topics to space mor > effective than in the past. > > I don't have an opinion one way or another. We can have a developer > meeting as well. Just shout and I will set it up. > > Lars > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel > -- My Blog: http://www.neilscomputerblog.blogspot.com/ Twitter: @neilsikka --94eb2c05d0fa7b3d5d053ad0e2ce Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hey guys, is anything happening today regarding a meeting = or going out for lunch if people arrive a day early?

On Thu, Jun 23, 2016 at 8:43 A= M, Lars Kurth <lars.kurth.xen@gmail.com> wrote:

> On 23 Jun 2016, at 12:39, George Dunlap <george.dunlap@citrix.com> wrote:
>
> On 23/06/16 12:33, Lars Kurth wrote:
>> Folks,
>>
>> do you guys want to hold a Developer Meeting on Aug 24th (before D= ev Summit). I do have space to do this, but last year's was very poorly= attended. If you could get back to me with an opinion, that would help hug= ely. Alternatively it would also be possible to use the space for more focu= sed meetings with fewer people. In that case, I would need a number of sugg= estions for meetings including meeting leaders.
>>
>> Please have a look at the schedule http://events.linuxfoundation.org/events= /xen-project-developer-summit/program/schedule ... note that = on the 26th, I kept the 2nd room free and was planning to use the Hackathon= format in parallel to the talks in the main program. rather than having Bo= Fs interspersed with talks. Some of the slots could be used to host the dev= eloper meeting, of desired.
>
> So to a large degree, the actual nuts-and-bolts planning which that > meeting was meant to cover happens now at the "hackathons" i= nstead.
> It's important I think, however, for the XenSummit to have a venue= for
> people in the industry who may not know about the Hackathons (or for > whatever reason can't come to them) to raise issues with the core<= br> > developers and have them discussed.
>
> If the parallel track could actually fulfill that role, then I think i= t
> would be enough; the key would be making sure that the appropriate
> attention could be attracted.

That's why I asked. Maybe we can come up with a short list of to= pics that need to be discussed and are worthwhile for the developer meeting= s.

The idea behind using the Hackathon scheduling methodology for the parallel= track is an experiment to make assigning of topics to space mor effective = than in the past.

I don't have an opinion one way or another. We can have a developer mee= ting as well. Just shout and I will set it up.

Lars
_____________________= __________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel



--
Twitter: @neilsikka
=
--94eb2c05d0fa7b3d5d053ad0e2ce-- --===============4893880963184614203== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWRldmVs IG1haWxpbmcgbGlzdApYZW4tZGV2ZWxAbGlzdHMueGVuLm9yZwpodHRwczovL2xpc3RzLnhlbi5v cmcveGVuLWRldmVsCg== --===============4893880963184614203==--