From: Ian Campbell <Ian.Campbell@citrix.com>
To: xen-devel <xen-devel@lists.xen.org>
Subject: community develop/contributor call
Date: Wed, 7 Jan 2015 12:18:15 +0000 [thread overview]
Message-ID: <1420633095.18631.70.camel@citrix.com> (raw)
Hi all,
For a few years now I've been running a monthly phone call between
various organisations which contribute to Xen, the so called "TCT
Call"[0]. However since then the Xen Project has moved to the Linux
foundation and the introduction of the Advisory Board means this call
isn't really useful in its current form any more.
Rather than just cancelling it I've been thinking of repurposing it into
a more development focused call for all contributors (maintainers, patch
submitters etc).
The idea would be to provide a regular slot where technical and
development topics can be discussed on an on demand basis without the
need to setup an ad-hoc call each time something comes up. In other
words to provide a forum for topics such as thrashing out a more complex
design for a new feature, building consensus on how to move forward with
a stalled patch series, discussing difficult freeze exception requests
during release periods and cases where on list discussion has stalled or
those involved feel the need to have a "live" chat about it for some
reason.
My intention would be the call would be targeted at maintainers and
people who are themselves working on the code/design, although anyone
will be welcome to dial in and take part.
The plan would be to post a call for agenda items to xen-devel a week
beforehand with the call being cancelled the day before if no topics
were proposed (I have no problem with the call only happening
occasionally, there's no point in having it if there are no topics, but
if it's useful a couple of times a year it's worth having IMHO). I
will try and reach out to anyone who should be involved with a proposed
topic to try and ensure that the call has the right people on it in
order to make progress. In the event that some of the participants feel
that a topic is still being usefully discussed on list and that
discussion should remain there then I'll mediate to either gain
consensus one way or another or unblock things some other way etc.
I would expect people decide based on the published agenda each month
whether they want/need to attend. I hope that at least the maintainers
would make an effort to attend if there were topics covering their areas
(and as above I will chase where needed).
In the short term I intend to stick with the same time (5PM UK, on the
second Wednesday of the month) and cadence (monthly) as before, but I
might revisit the timing, in particular if we find the proposed topics
make the time problematic for key people who want to be involved (e.g.
folks in the Far East, for whom 5PM UK is pretty antisocial).
Since that schedule puts a call a week today (14th Jan), I'll send out a
call for agenda later today.
Ian.
[0] http://wiki.xen.org/wiki/Xen_Technical_Coordination_Team_%28TCT%29_Meeting
next reply other threads:[~2015-01-07 12:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-07 12:18 Ian Campbell [this message]
2015-01-07 15:32 ` [CALL-FOR-AGENDA] Monthly Xen.org Technical Call (2015-01-14) Ian Campbell
2015-01-07 15:37 ` Konrad Rzeszutek Wilk
2015-01-07 16:06 ` Ian Campbell
2015-01-13 19:49 ` Ian Campbell
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=1420633095.18631.70.camel@citrix.com \
--to=ian.campbell@citrix.com \
--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.