From wg-ar-and-pr-bounces@lists.xenproject.org Mon Dec 02 18:01:04 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 02 Dec 2013 18:01:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VnXns-0001xZ-0Y for archives@lists.xenproject.org; Mon, 02 Dec 2013 18:01:04 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VnXno-0001xA-Ip; Mon, 02 Dec 2013 18:01:01 +0000 Received: from [85.158.143.35:54573] by server-2.bemta-4.messagelabs.com id B0/3A-11386-BDACC925; Mon, 02 Dec 2013 18:00:59 +0000 X-Env-Sender: lars.kurth@citrix.com X-Msg-Ref: server-8.tower-21.messagelabs.com!1386007256!2737879!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31001 invoked from network); 2 Dec 2013 18:00:57 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-8.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 2 Dec 2013 18:00:57 -0000 X-IronPort-AV: E=Sophos;i="4.93,812,1378857600"; d="scan'208,217";a="77416565" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 02 Dec 2013 18:00:55 +0000 Received: from AMSPEX01CL02.citrite.net (10.69.46.33) by FTLPEX01CL03.citrite.net (10.13.107.80) with Microsoft SMTP Server (TLS) id 14.2.342.4; Mon, 2 Dec 2013 13:00:55 -0500 Received: from AMSPEX01CL01.citrite.net ([169.254.6.128]) by AMSPEX01CL02.citrite.net ([10.69.46.33]) with mapi id 14.02.0342.004; Mon, 2 Dec 2013 19:00:54 +0100 From: Lars Kurth To: "advisory-board@lists.xenproject.org" Thread-Topic: Strategy to build Momentum for Xen Project Thread-Index: Ac7vfX/3BhSRXFo2QmOsC1pxQckbsw== Date: Mon, 2 Dec 2013 18:00:53 +0000 Message-ID: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.16.2.168] MIME-Version: 1.0 X-DLP: MIA1 Cc: "wg-ar-and-pr@lists.xenproject.org" , Russell Pavlicek Subject: [Wg-ar-and-pr] Strategy to build Momentum for Xen Project X-BeenThere: wg-ar-and-pr@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen Project AR and PR Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5759960943324364747==" Sender: wg-ar-and-pr-bounces@lists.xenproject.org Errors-To: wg-ar-and-pr-bounces@lists.xenproject.org --===============5759960943324364747== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_B5EC053C78C5D746BD8AC3386F2303C90F2C4AAMSPEX01CL01citri_" --_000_B5EC053C78C5D746BD8AC3386F2303C90F2C4AAMSPEX01CL01citri_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Dear AB members, at LinuxCon EU (or was it NA) Mike Woster suggested that I put together a s= trategy that helps increase momentum . The basic idea of what he suggested is to express the strategy as a simple = table that we would maintain at an ongoing basis: a) Major news/message/activity on the left. Examples of entries could be: * A press release for a Xen Project release * A series of stories about new feature/benchmarks/... in the tech = media * Presence (e.g. a Xen Project booth) at an event * It could also be a vendor press release (e.g. a product release w= ith a Xen angle) * It could also be a Xen demo planned for an event by a vendor * It could also be an announcement of an activity sponsored by a AB= vendor (e.g. work such as XenGT by Intel, an intention to contribute a lar= ger piece of code, etc.) b) Major Industry / OSS events on the right The first step, is to collect as much input as can be shared. As such, I n= eed to * Identify events that AB members care about : So please let me kno= w of any Industry Events, you want me to add. These do NOT have to be open = source events. o I will just start with the major OSS events and let you add things from= there * Any items for the left side of the strategy that you want to add.= I will send this document to the board regularly for any updates. The intention of this exercise is to * Ensure that "news/message/activity" are aligned with an event tha= t provides maximum exposure * Make sure we have something positive we can cover on an ongoing b= asis * Ensure that we evenly distribute activities that build momentum o= ver the year Here is my very first go at this (I separated events by server and cloud an= d "other" for technologies that are not core to Xen today, BUT have potenti= al) Month News/Message/Activity Industry Event(s) - Server and Cloud Industry Event(s) - Other Comment / Idea Jan Xen Project: Xen 4.4 Release (see http://lists.xenproject.org/archives/html/xen-devel/2013-11/msg03798.h= tml - ETA Jan 21, could slip into Feb). Key Features * PVH DomU (experimental) * Scalability * Xen on ARM (server HW) Consider releasing & PR just before FOSDEM (e.g. Jan 27) to generate some X= en "buzz" at FOSDEM. Feb Xen Project: Booth Presence at FOSDEM (TBD) Xen Project: Co-organzing Virt & Iaas DevRoom FOSDEM, Feb 1-2, Belgium (largest FOSS event in Europe, 5000+ attendees) OpenDayLight Summit, Feb 4-5 Very Developer Centric March LF Collab Summit, March 26-28, CA Always good for collaboration, major contribution announcements, etc. April Embedded Linux Conference, April 29 - May 1 Android Builders Conference, April 29 - May 1 Build Xen+Embedded/Android momentum May Jun LC Japan, June 4-6 LF Enterprise User Summit, Jun 23-24 Automotive Summit, June 2-3 Build Xen+Automotive momentum Jul OSCON, July 20-24 Aug Provisional: Xen Project Developer Summit (with press invited) Xen Project Dev Summit, Aug 16 & 17 LC NA, Chicago, Aug 18-20 Sept Oct Xen Project: Xen 4.5 Release LC EU, Germany, Oct 13-15 Nov Dec Just to explain how this may work to maximise impact * If a vendor (e.g. Verizon has become active recently) were to pla= n a major contribution, an event such as Linux Foundation Collab Summit cou= ld be used to maximise impact * Similarly the Graduation of MirageOS may work well for Linux Foun= dation Collab Summit * We could have a build-up of articles related to Xen+Embedded to s= trengthen recent developments in Xen+Android and Xen+Automotive * We (or a AB vendor) should plan benchmarks for PVH Dom0 after the= Xen 4.3 release AND publish just before or around a specific event * LF Enterprise User Summit may be perfect to push out some user st= ories/benchmarks targeting large enterprises * Etc. We may want to add vendor specific events: e.g. for Intel, ARM, etc. We may want to add cloud events, distro events, etc. We may want to add events such as HostingCon Etc. I am taking a neutral view here: please let me know which events should be = added in your view. Best Regards Lars --_000_B5EC053C78C5D746BD8AC3386F2303C90F2C4AAMSPEX01CL01citri_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Dear AB members,

 

at LinuxCon EU (or was it NA) Mike Woster suggested = that I put together a strategy that helps increase momentum .

 

The basic idea of what he suggested is to express th= e strategy as a simple table that we would maintain at an ongoing basis:

a) Major news/message/activity on the left. Examples= of entries could be:

·         A press release for a Xen Project release

·         A series of stories about new feature/benchm= arks/… in the tech media

·         Presence (e.g. a Xen Project booth) at an ev= ent

·         It could also be a vendor press release (e.g= . a product release with a Xen angle)

·         It could also be a Xen demo planned for an e= vent by a vendor

·         It could also be an announcement of an activ= ity sponsored by a AB vendor (e.g. work such as XenGT by Intel, an intentio= n to contribute a larger piece of code, etc.)

b) Major Industry / OSS events on the right

 

The first step, is to collect as much input as can b= e shared.  As such, I need to

·         Identify events that AB members care about := So please let me know of any Industry Events, you want me to add. T= hese do NOT have to be open source events.

o   I will just start with the major OSS events = and let you add things from there

·         Any items for the left side of the strategy = that you want to add. I will send this document to the board regularly for = any updates.

 

The intention of this exercise is to

·         Ensure that “news/message/activityR= 21; are aligned with an event that provides maximum exposure

·         Make sure we have something positive we can = cover on an ongoing basis

·         Ensure that we evenly distribute activities = that build momentum over the year

 

Here is my very first go at this (I separated events= by server and cloud and “other” for technologies that are not = core to Xen today, BUT have potential)

 

Month

News/Message/Activity

Industry Event(s) – Server and Cloud

Industry Event(s) – Other

Comment / Idea

Jan

Xen Project: Xen 4.4 Release
(see http://lists.xenproject.org/archives/html/xen-devel/2013-11/msg03798.html - ETA Jan 21, could slip into Feb). Key Features

·         PVH DomU (experimental)

·         Scalability

·         Xen on ARM (server HW)

 

 

Consider releasing & PR just before FOSDEM (e.g.= Jan 27) to generate some Xen “buzz” at FOSDEM.

Feb

Xen Project: Booth Presence at FOSDEM (TBD) Xen Project: Co-organzing Virt & Iaas DevRoom

 

FOSDEM, Feb 1-2, Belgium
(largest FOSS event in Europe, 5000+ attendees)

 



OpenDayLight Summit, Feb 4-5

Very Developer Centric

March

 

LF Collab Summit, March 26-28, CA

 

Always good for collaboration, major contribution an= nouncements, etc.

April

 



Embedded Linux Conference, April 29 – May 1 Android Builders Conference, April 29 – May 1

Build Xen+Embedded/Android momentum

May

 

 

 

 

Jun

 

LC Japan, June 4-6

 

LF Enterprise User Summit, Jun 23-24

Automotive Summit, June 2-3

Build Xen+Automotive momentum

Jul

 

OSCON, July 20-24

 

 

Aug

Provisional: Xen Project Developer Summit (with press invited)

Xen Project Dev Summit, Aug 16 & 17
LC NA, Chicago, Aug 18-20

 

 

Sept

 

 

 

 

Oct

Xen Project: Xen 4.5 Release

LC EU, Germany, Oct 13-15

 

 

Nov

 

 

 

 

Dec

 

 

 

 

 

Just to explain how this may work to maximise impact=

·         If a vendor (e.g. Verizon has become active = recently) were to plan a major contribution, an event such as Linux Foundat= ion Collab Summit could be used to maximise impact

·         Similarly the Graduation of MirageOS may wor= k well for Linux Foundation Collab Summit

·         We could have a build-up of articles related= to Xen+Embedded to strengthen recent developments in Xen+Android a= nd Xen+Automotive

·         We (or a AB vendor) should plan benchmarks f= or PVH Dom0 after the Xen 4.3 release AND publish just before or around a s= pecific event

·         LF Enterprise User Summit may be perfect to = push out some user stories/benchmarks targeting large enterprises

·         Etc.

 

We may want to add vendor specific events: e.g. for = Intel, ARM, etc.

We may want to add cloud events, distro events, etc.=

We may want to add events such as HostingCon

Etc.

 

I am taking a neutral view here: please let me know which events shou= ld be added in your view.

 

Best Regards

Lars

--_000_B5EC053C78C5D746BD8AC3386F2303C90F2C4AAMSPEX01CL01citri_-- --===============5759960943324364747== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Wg-ar-and-pr mailing list Wg-ar-and-pr@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/wg-ar-and-pr --===============5759960943324364747==-- From wg-ar-and-pr-bounces@lists.xenproject.org Mon Dec 02 18:01:04 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 02 Dec 2013 18:01:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VnXns-0001xZ-0Y for archives@lists.xenproject.org; Mon, 02 Dec 2013 18:01:04 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VnXno-0001xA-Ip; Mon, 02 Dec 2013 18:01:01 +0000 Received: from [85.158.143.35:54573] by server-2.bemta-4.messagelabs.com id B0/3A-11386-BDACC925; Mon, 02 Dec 2013 18:00:59 +0000 X-Env-Sender: lars.kurth@citrix.com X-Msg-Ref: server-8.tower-21.messagelabs.com!1386007256!2737879!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31001 invoked from network); 2 Dec 2013 18:00:57 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-8.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 2 Dec 2013 18:00:57 -0000 X-IronPort-AV: E=Sophos;i="4.93,812,1378857600"; d="scan'208,217";a="77416565" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 02 Dec 2013 18:00:55 +0000 Received: from AMSPEX01CL02.citrite.net (10.69.46.33) by FTLPEX01CL03.citrite.net (10.13.107.80) with Microsoft SMTP Server (TLS) id 14.2.342.4; Mon, 2 Dec 2013 13:00:55 -0500 Received: from AMSPEX01CL01.citrite.net ([169.254.6.128]) by AMSPEX01CL02.citrite.net ([10.69.46.33]) with mapi id 14.02.0342.004; Mon, 2 Dec 2013 19:00:54 +0100 From: Lars Kurth To: "advisory-board@lists.xenproject.org" Thread-Topic: Strategy to build Momentum for Xen Project Thread-Index: Ac7vfX/3BhSRXFo2QmOsC1pxQckbsw== Date: Mon, 2 Dec 2013 18:00:53 +0000 Message-ID: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.16.2.168] MIME-Version: 1.0 X-DLP: MIA1 Cc: "wg-ar-and-pr@lists.xenproject.org" , Russell Pavlicek Subject: [Wg-ar-and-pr] Strategy to build Momentum for Xen Project X-BeenThere: wg-ar-and-pr@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen Project AR and PR Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5759960943324364747==" Sender: wg-ar-and-pr-bounces@lists.xenproject.org Errors-To: wg-ar-and-pr-bounces@lists.xenproject.org --===============5759960943324364747== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_B5EC053C78C5D746BD8AC3386F2303C90F2C4AAMSPEX01CL01citri_" --_000_B5EC053C78C5D746BD8AC3386F2303C90F2C4AAMSPEX01CL01citri_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Dear AB members, at LinuxCon EU (or was it NA) Mike Woster suggested that I put together a s= trategy that helps increase momentum . The basic idea of what he suggested is to express the strategy as a simple = table that we would maintain at an ongoing basis: a) Major news/message/activity on the left. Examples of entries could be: * A press release for a Xen Project release * A series of stories about new feature/benchmarks/... in the tech = media * Presence (e.g. a Xen Project booth) at an event * It could also be a vendor press release (e.g. a product release w= ith a Xen angle) * It could also be a Xen demo planned for an event by a vendor * It could also be an announcement of an activity sponsored by a AB= vendor (e.g. work such as XenGT by Intel, an intention to contribute a lar= ger piece of code, etc.) b) Major Industry / OSS events on the right The first step, is to collect as much input as can be shared. As such, I n= eed to * Identify events that AB members care about : So please let me kno= w of any Industry Events, you want me to add. These do NOT have to be open = source events. o I will just start with the major OSS events and let you add things from= there * Any items for the left side of the strategy that you want to add.= I will send this document to the board regularly for any updates. The intention of this exercise is to * Ensure that "news/message/activity" are aligned with an event tha= t provides maximum exposure * Make sure we have something positive we can cover on an ongoing b= asis * Ensure that we evenly distribute activities that build momentum o= ver the year Here is my very first go at this (I separated events by server and cloud an= d "other" for technologies that are not core to Xen today, BUT have potenti= al) Month News/Message/Activity Industry Event(s) - Server and Cloud Industry Event(s) - Other Comment / Idea Jan Xen Project: Xen 4.4 Release (see http://lists.xenproject.org/archives/html/xen-devel/2013-11/msg03798.h= tml - ETA Jan 21, could slip into Feb). Key Features * PVH DomU (experimental) * Scalability * Xen on ARM (server HW) Consider releasing & PR just before FOSDEM (e.g. Jan 27) to generate some X= en "buzz" at FOSDEM. Feb Xen Project: Booth Presence at FOSDEM (TBD) Xen Project: Co-organzing Virt & Iaas DevRoom FOSDEM, Feb 1-2, Belgium (largest FOSS event in Europe, 5000+ attendees) OpenDayLight Summit, Feb 4-5 Very Developer Centric March LF Collab Summit, March 26-28, CA Always good for collaboration, major contribution announcements, etc. April Embedded Linux Conference, April 29 - May 1 Android Builders Conference, April 29 - May 1 Build Xen+Embedded/Android momentum May Jun LC Japan, June 4-6 LF Enterprise User Summit, Jun 23-24 Automotive Summit, June 2-3 Build Xen+Automotive momentum Jul OSCON, July 20-24 Aug Provisional: Xen Project Developer Summit (with press invited) Xen Project Dev Summit, Aug 16 & 17 LC NA, Chicago, Aug 18-20 Sept Oct Xen Project: Xen 4.5 Release LC EU, Germany, Oct 13-15 Nov Dec Just to explain how this may work to maximise impact * If a vendor (e.g. Verizon has become active recently) were to pla= n a major contribution, an event such as Linux Foundation Collab Summit cou= ld be used to maximise impact * Similarly the Graduation of MirageOS may work well for Linux Foun= dation Collab Summit * We could have a build-up of articles related to Xen+Embedded to s= trengthen recent developments in Xen+Android and Xen+Automotive * We (or a AB vendor) should plan benchmarks for PVH Dom0 after the= Xen 4.3 release AND publish just before or around a specific event * LF Enterprise User Summit may be perfect to push out some user st= ories/benchmarks targeting large enterprises * Etc. We may want to add vendor specific events: e.g. for Intel, ARM, etc. We may want to add cloud events, distro events, etc. We may want to add events such as HostingCon Etc. I am taking a neutral view here: please let me know which events should be = added in your view. Best Regards Lars --_000_B5EC053C78C5D746BD8AC3386F2303C90F2C4AAMSPEX01CL01citri_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Dear AB members,

 

at LinuxCon EU (or was it NA) Mike Woster suggested = that I put together a strategy that helps increase momentum .

 

The basic idea of what he suggested is to express th= e strategy as a simple table that we would maintain at an ongoing basis:

a) Major news/message/activity on the left. Examples= of entries could be:

·         A press release for a Xen Project release

·         A series of stories about new feature/benchm= arks/… in the tech media

·         Presence (e.g. a Xen Project booth) at an ev= ent

·         It could also be a vendor press release (e.g= . a product release with a Xen angle)

·         It could also be a Xen demo planned for an e= vent by a vendor

·         It could also be an announcement of an activ= ity sponsored by a AB vendor (e.g. work such as XenGT by Intel, an intentio= n to contribute a larger piece of code, etc.)

b) Major Industry / OSS events on the right

 

The first step, is to collect as much input as can b= e shared.  As such, I need to

·         Identify events that AB members care about := So please let me know of any Industry Events, you want me to add. T= hese do NOT have to be open source events.

o   I will just start with the major OSS events = and let you add things from there

·         Any items for the left side of the strategy = that you want to add. I will send this document to the board regularly for = any updates.

 

The intention of this exercise is to

·         Ensure that “news/message/activityR= 21; are aligned with an event that provides maximum exposure

·         Make sure we have something positive we can = cover on an ongoing basis

·         Ensure that we evenly distribute activities = that build momentum over the year

 

Here is my very first go at this (I separated events= by server and cloud and “other” for technologies that are not = core to Xen today, BUT have potential)

 

Month

News/Message/Activity

Industry Event(s) – Server and Cloud

Industry Event(s) – Other

Comment / Idea

Jan

Xen Project: Xen 4.4 Release
(see http://lists.xenproject.org/archives/html/xen-devel/2013-11/msg03798.html - ETA Jan 21, could slip into Feb). Key Features

·         PVH DomU (experimental)

·         Scalability

·         Xen on ARM (server HW)

 

 

Consider releasing & PR just before FOSDEM (e.g.= Jan 27) to generate some Xen “buzz” at FOSDEM.

Feb

Xen Project: Booth Presence at FOSDEM (TBD) Xen Project: Co-organzing Virt & Iaas DevRoom

 

FOSDEM, Feb 1-2, Belgium
(largest FOSS event in Europe, 5000+ attendees)

 



OpenDayLight Summit, Feb 4-5

Very Developer Centric

March

 

LF Collab Summit, March 26-28, CA

 

Always good for collaboration, major contribution an= nouncements, etc.

April

 



Embedded Linux Conference, April 29 – May 1 Android Builders Conference, April 29 – May 1

Build Xen+Embedded/Android momentum

May

 

 

 

 

Jun

 

LC Japan, June 4-6

 

LF Enterprise User Summit, Jun 23-24

Automotive Summit, June 2-3

Build Xen+Automotive momentum

Jul

 

OSCON, July 20-24

 

 

Aug

Provisional: Xen Project Developer Summit (with press invited)

Xen Project Dev Summit, Aug 16 & 17
LC NA, Chicago, Aug 18-20

 

 

Sept

 

 

 

 

Oct

Xen Project: Xen 4.5 Release

LC EU, Germany, Oct 13-15

 

 

Nov

 

 

 

 

Dec

 

 

 

 

 

Just to explain how this may work to maximise impact=

·         If a vendor (e.g. Verizon has become active = recently) were to plan a major contribution, an event such as Linux Foundat= ion Collab Summit could be used to maximise impact

·         Similarly the Graduation of MirageOS may wor= k well for Linux Foundation Collab Summit

·         We could have a build-up of articles related= to Xen+Embedded to strengthen recent developments in Xen+Android a= nd Xen+Automotive

·         We (or a AB vendor) should plan benchmarks f= or PVH Dom0 after the Xen 4.3 release AND publish just before or around a s= pecific event

·         LF Enterprise User Summit may be perfect to = push out some user stories/benchmarks targeting large enterprises

·         Etc.

 

We may want to add vendor specific events: e.g. for = Intel, ARM, etc.

We may want to add cloud events, distro events, etc.=

We may want to add events such as HostingCon

Etc.

 

I am taking a neutral view here: please let me know which events shou= ld be added in your view.

 

Best Regards

Lars

--_000_B5EC053C78C5D746BD8AC3386F2303C90F2C4AAMSPEX01CL01citri_-- --===============5759960943324364747== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Wg-ar-and-pr mailing list Wg-ar-and-pr@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/wg-ar-and-pr --===============5759960943324364747==--