From: Brian Woods <brian.woods@amd.com>
To: Lars Kurth <lars.kurth.xen@gmail.com>
Cc: "Chao Peng" <chao.p.peng@linux.intel.com>,
"Kevin Tian" <kevin.tian@intel.com>,
tamas@tklengyel.com,
"Razvan Cojocaru" <rcojocaru@bitdefender.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
daniel.kiper@oracle.com, "Susie Li" <susie.li@intel.com>,
"Roger Pau Monné" <royger@freebsd.org>,
"John Ji" <john.ji@intel.com>, "Babu Moger" <Babu.Moger@amd.com>,
"Rich Persaud" <persaur@gmail.com>,
paul.durrant@citrix.com, committers@xenproject.org,
"Jan Beulich" <jbeulich@suse.com>,
"Hurwitz, Sherry" <sherry.hurwitz@amd.com>,
xen-devel <xen-devel@lists.xenproject.org>,
joao.m.martins@oracle.com, "Brian Woods" <brian.woods@amd.com>,
boris.ostrovsky@oracle.com
Subject: Re: Setting up a Xen x86 community call
Date: Fri, 2 Mar 2018 15:54:11 -0600 [thread overview]
Message-ID: <20180302215410.GA31249@amd.com> (raw)
In-Reply-To: <B2025C1A-199C-4019-9ECF-AFF34FE8D702@gmail.com>
On Fri, Mar 02, 2018 at 04:39:59PM +0100, Lars Kurth wrote:
> Hi all,
> (sorry for the extensive distribution list - I went through MAINTAINERS and people who may have an interest)
>
> I would like to start organizing a recurring x86 community call to discuss and sync-up on upcoming features for Xen on x86. This call would mirror and follow a similar structure to the ARM call (see http://xen.markmail.org/thread/xqdxvqcjpf2y5ftu for the last one)
>
> I expect that the call will contain
>
> a) Coordination and Planning
> Coordinating who does what, what needs attention, what is blocked, etc.
> I would prepare a list of non-merged patch series of a certain size (e.g. more than 5 patches) and attach to the invite
> If anything is missed, I would expect that these are sent to me before the meeting
>
> b) Design and architecture related discussions: in particular for bigger, more complex items, ...
> Although all of this could be done by email, in reality, we are all human and many people find it easier to collaborate
> and communicate by talking to each other, rather than by email. This is not a must, but an option to highlight issues
>
> c) Demos, Sharing of Experiences, Sometimes discussion of specific issues/bugs/problems/...
> This is something which happens frequently on the ARM call and seems to work very well
>
> I would suggest to start with a 1 hour monthly meeting: possibly every 2nd Tue or Thu each month (depends on timing). I know that people are spread across different timezones (from China to the US), so I would like to gather thoughts before choosing a time. We may have to have alternating time-slots every other month: but this is not ideal for some.
>
> To do this, please
> * Raise your hands on whether you or your org would want to participate
\o/
> * Provide your timezone
CT
> * Provide a UTC time range when you can attend
15:00-23:00
> Your sincerely,
> Lars
>
>
--
Brian Woods
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-03-02 21:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-02 15:39 Setting up a Xen x86 community call Lars Kurth
2018-03-02 16:36 ` Roger Pau Monné
2018-03-02 16:55 ` Paul Durrant
2018-03-02 17:00 ` Andrew Cooper
2018-03-02 17:06 ` Wei Liu
2018-03-02 17:11 ` Rich Persaud
2018-03-02 17:12 ` Juergen Gross
2018-03-02 17:22 ` George Dunlap
2018-03-02 21:54 ` Brian Woods [this message]
2018-03-03 1:08 ` Tamas K Lengyel
2018-03-03 6:57 ` Ji, John
2018-03-05 10:39 ` Daniel Kiper
2018-03-06 17:29 ` Janakarajan Natarajan
2018-03-07 12:27 ` Lars Kurth
2018-03-07 14:45 ` Daniel Kiper
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=20180302215410.GA31249@amd.com \
--to=brian.woods@amd.com \
--cc=Babu.Moger@amd.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=chao.p.peng@linux.intel.com \
--cc=committers@xenproject.org \
--cc=daniel.kiper@oracle.com \
--cc=jbeulich@suse.com \
--cc=joao.m.martins@oracle.com \
--cc=john.ji@intel.com \
--cc=kevin.tian@intel.com \
--cc=lars.kurth.xen@gmail.com \
--cc=paul.durrant@citrix.com \
--cc=persaur@gmail.com \
--cc=rcojocaru@bitdefender.com \
--cc=royger@freebsd.org \
--cc=sherry.hurwitz@amd.com \
--cc=susie.li@intel.com \
--cc=tamas@tklengyel.com \
--cc=xen-devel@lists.xenproject.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.