From xci-devel-bounces@lists.xen.org Sun Apr 01 01:35:38 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 01 Apr 2012 01:35:38 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SE9hg-00007O-Tg; Sun, 01 Apr 2012 01:35:36 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SE9hf-00007F-Uj for xci-devel@lists.xen.org; Sun, 01 Apr 2012 01:35:36 +0000 Received: from [85.158.143.35:62166] by server-1.bemta-4.messagelabs.com id D1/60-20925-7E0B77F4; Sun, 01 Apr 2012 01:35:35 +0000 X-Env-Sender: andreww591@gmail.com X-Msg-Ref: server-16.tower-21.messagelabs.com!1333244133!6823554!1 X-Originating-IP: [209.85.210.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20290 invoked from network); 1 Apr 2012 01:35:34 -0000 Received: from mail-iy0-f173.google.com (HELO mail-iy0-f173.google.com) (209.85.210.173) by server-16.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 1 Apr 2012 01:35:34 -0000 Received: by iafj26 with SMTP id j26so3369651iaf.32 for ; Sat, 31 Mar 2012 18:35:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=phqSeFxB1o5fSJkyy1zV5iE9LteJ3XqdT/9yvVGtg/M=; b=aRTdq4phMOA1XuWiT5luVkYXoIPKQabr1rb9WmTt1RvZkZIepDTZPWfrIJYdD97dxB 7v06JGvFYfMPA6jQ7eh7jWogJT1fkNzd72sQsFYlvsNjbdDTNDQttSSvQ4y8HjQrS0d6 Ezp1pMo5G5pk6Lh3GL0r+E8qR3HrxqnVlx+pb7GA742rYcKXBDyI6sVycfyAfq9wDpju ae12NrdstK6rdC1xzf/VAxUTzqMIBjwIHbKLzegCnyf3R3koBu6DycrzAhZiCU+mYXRo iu2YvFd2n3ZTte5CQ091Cesqlwk8u/kFLKwyOg9SZOSxcSjKXUvVwCXSES0PS7wC6krw AR3w== MIME-Version: 1.0 Received: by 10.50.193.234 with SMTP id hr10mr2258385igc.14.1333244132682; Sat, 31 Mar 2012 18:35:32 -0700 (PDT) Received: by 10.231.133.201 with HTTP; Sat, 31 Mar 2012 18:35:32 -0700 (PDT) In-Reply-To: <4F7596CE.6000103@xen.org> References: <4F74593B.9000003@xen.org> <4F7596CE.6000103@xen.org> Date: Sat, 31 Mar 2012 19:35:32 -0600 Message-ID: From: Andrew Warkentin To: xen-devel@lists.xen.org Cc: xci-devel@lists.xen.org Subject: Re: [Xci-devel] [Xen-devel] Archiving XCI : Request for an Archivation Review for the XCI project X-BeenThere: xci-devel@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xci-devel-bounces@lists.xen.org Errors-To: xci-devel-bounces@lists.xen.org On 3/30/12, Lars Kurth wrote: > Andrew, > > that is good news. I see a number of options going forward, which really > depends on your preference and also what committers and maintainers in > the community think: > 1) OpenXCI as a new project hosted on Xen.org - starting as an > incubation project as per http://www.xen.org/projects/governance.html > and archive the old one. What you describe sounds sufficiently different. > > 2) OpenXCI as a separate project: Xen.org can help you promoting the > project in various ways > > If you want and have a bit more clarity on what you want to do and how > you want to achieve things, I could arrange a call with you and walk you > through the details. > I'm not quite sure which would be a better idea. I don't really have much on the OpenXCI SourceForge project (just the Mercurial repository for the graphics and input servers, as well as a tarball with the corresponding qemu patches), so it might be easier to move it to xen.org now rather than later. I do have a pretty good idea of what I want OpenXCI to be - a configurable, high-performance multi-boot alternative with good support for graphics passthrough, using a similar architecture to XenClient (but using direct GPU passthrough for one domain and either a "reverse graphics adapter" or a VNC connection to display other domains, possibly with some kind of support for 3D on non-passthrough domains using virtual GPUs being added later). _______________________________________________ Xci-devel mailing list Xci-devel@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xci-devel From xci-devel-bounces@lists.xen.org Sun Apr 01 01:35:38 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 01 Apr 2012 01:35:38 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SE9hg-00007O-Tg; Sun, 01 Apr 2012 01:35:36 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SE9hf-00007F-Uj for xci-devel@lists.xen.org; Sun, 01 Apr 2012 01:35:36 +0000 Received: from [85.158.143.35:62166] by server-1.bemta-4.messagelabs.com id D1/60-20925-7E0B77F4; Sun, 01 Apr 2012 01:35:35 +0000 X-Env-Sender: andreww591@gmail.com X-Msg-Ref: server-16.tower-21.messagelabs.com!1333244133!6823554!1 X-Originating-IP: [209.85.210.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20290 invoked from network); 1 Apr 2012 01:35:34 -0000 Received: from mail-iy0-f173.google.com (HELO mail-iy0-f173.google.com) (209.85.210.173) by server-16.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 1 Apr 2012 01:35:34 -0000 Received: by iafj26 with SMTP id j26so3369651iaf.32 for ; Sat, 31 Mar 2012 18:35:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=phqSeFxB1o5fSJkyy1zV5iE9LteJ3XqdT/9yvVGtg/M=; b=aRTdq4phMOA1XuWiT5luVkYXoIPKQabr1rb9WmTt1RvZkZIepDTZPWfrIJYdD97dxB 7v06JGvFYfMPA6jQ7eh7jWogJT1fkNzd72sQsFYlvsNjbdDTNDQttSSvQ4y8HjQrS0d6 Ezp1pMo5G5pk6Lh3GL0r+E8qR3HrxqnVlx+pb7GA742rYcKXBDyI6sVycfyAfq9wDpju ae12NrdstK6rdC1xzf/VAxUTzqMIBjwIHbKLzegCnyf3R3koBu6DycrzAhZiCU+mYXRo iu2YvFd2n3ZTte5CQ091Cesqlwk8u/kFLKwyOg9SZOSxcSjKXUvVwCXSES0PS7wC6krw AR3w== MIME-Version: 1.0 Received: by 10.50.193.234 with SMTP id hr10mr2258385igc.14.1333244132682; Sat, 31 Mar 2012 18:35:32 -0700 (PDT) Received: by 10.231.133.201 with HTTP; Sat, 31 Mar 2012 18:35:32 -0700 (PDT) In-Reply-To: <4F7596CE.6000103@xen.org> References: <4F74593B.9000003@xen.org> <4F7596CE.6000103@xen.org> Date: Sat, 31 Mar 2012 19:35:32 -0600 Message-ID: From: Andrew Warkentin To: xen-devel@lists.xen.org Cc: xci-devel@lists.xen.org Subject: Re: [Xci-devel] [Xen-devel] Archiving XCI : Request for an Archivation Review for the XCI project X-BeenThere: xci-devel@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xci-devel-bounces@lists.xen.org Errors-To: xci-devel-bounces@lists.xen.org On 3/30/12, Lars Kurth wrote: > Andrew, > > that is good news. I see a number of options going forward, which really > depends on your preference and also what committers and maintainers in > the community think: > 1) OpenXCI as a new project hosted on Xen.org - starting as an > incubation project as per http://www.xen.org/projects/governance.html > and archive the old one. What you describe sounds sufficiently different. > > 2) OpenXCI as a separate project: Xen.org can help you promoting the > project in various ways > > If you want and have a bit more clarity on what you want to do and how > you want to achieve things, I could arrange a call with you and walk you > through the details. > I'm not quite sure which would be a better idea. I don't really have much on the OpenXCI SourceForge project (just the Mercurial repository for the graphics and input servers, as well as a tarball with the corresponding qemu patches), so it might be easier to move it to xen.org now rather than later. I do have a pretty good idea of what I want OpenXCI to be - a configurable, high-performance multi-boot alternative with good support for graphics passthrough, using a similar architecture to XenClient (but using direct GPU passthrough for one domain and either a "reverse graphics adapter" or a VNC connection to display other domains, possibly with some kind of support for 3D on non-passthrough domains using virtual GPUs being added later). _______________________________________________ Xci-devel mailing list Xci-devel@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xci-devel From xci-devel-bounces@lists.xen.org Tue Apr 03 15:04:32 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 03 Apr 2012 15:04:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SF5Hb-0007wA-Jk; Tue, 03 Apr 2012 15:04:31 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SF5Ha-0007vs-KW for xci-devel@lists.xen.org; Tue, 03 Apr 2012 15:04:30 +0000 Received: from [85.158.143.99:37577] by server-1.bemta-4.messagelabs.com id C8/33-20925-D711B7F4; Tue, 03 Apr 2012 15:04:29 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-6.tower-216.messagelabs.com!1333465468!22119703!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8281 invoked from network); 3 Apr 2012 15:04:28 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-6.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 3 Apr 2012 15:04:28 -0000 Received: by bkcjg9 with SMTP id jg9so4033252bkc.32 for ; Tue, 03 Apr 2012 08:04:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=MyInUtZ0bTabbZv+rbcE16wuQdH46Q6BtUU8iOCFwU4=; b=pJejlJX7OHynO5H7i8ZU2BbGzQ0F73nS18aigLIgHemwJOqqmd+EXSRfUTxpMPZQc1 rTkS9Bz3zot7F1L/RjVdIOM0T0mfVT1gRfKt4LvRFo3LAU9ckCn9fRCweyBB5sdkS09P pAx5gp/aIml6qsl6oxzIw16S9s2iPZggpvlZ+Sk4OysJxq5SEU8mZXspvD2sqy/TGnK0 Wy/DzPvI8KsXUZDK8fbDvtCn5we08cepVV9K0LfcSOliLsMOxyDiMma3GQGob9UPPBfF P1b99Fe8iUwoQQGFopwwbdjneZVP3/LTCnA18BP9mucCBMAczGG8zT5flLlF9A+RhI9B qkxg== Received: by 10.204.133.204 with SMTP id g12mr5737057bkt.64.1333465467780; Tue, 03 Apr 2012 08:04:27 -0700 (PDT) Received: from [172.16.25.10] (b0fb52a6.bb.sky.com. [176.251.82.166]) by mx.google.com with ESMTPS id f5sm46587029bke.9.2012.04.03.08.04.25 (version=SSLv3 cipher=OTHER); Tue, 03 Apr 2012 08:04:26 -0700 (PDT) Message-ID: <4F7B1178.6050001@xen.org> Date: Tue, 03 Apr 2012 16:04:24 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: xci-devel@lists.xen.org References: <4F74593B.9000003@xen.org> <4F7596CE.6000103@xen.org> In-Reply-To: Subject: Re: [Xci-devel] [Xen-devel] Archiving XCI : Request for an Archivation Review for the XCI project X-BeenThere: xci-devel@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xci-devel-bounces@lists.xen.org Errors-To: xci-devel-bounces@lists.xen.org Andrew, in that case - we should wait for the XCI archivation review To satisfy the development process we need (copied from governance) ----------------------------------------------------------------------------------- ... Forming a Project Requirements for forming a Xen.org project: - A project needs a lead, who is willing to become the project lead of the project - A project needs a sponsor, which can be a project lead of a mature project, a member of the Xen.org advisory board or the community manager - There should be no dissent from other community members who would qualify as sponsor (see "Principle: Consensus Decision Making") - A project needs a mentor, which can be the project sponsor or a maintainer of a mature project - A project needs to have a relationship to other Xen.org projects, i.e. it aims to develop software that has a dependency on other Xen.org projects. If the project needs components in other Xen.org projects to work, then this should also be stated. - A project needs to be large and long-term enough to grant a separate project. For example adding support for a new CPU architecture, adding additional functionality on top of existing projects, etc. Adding a new feature to an existing project should be performed within an existing project. - A project will deliver code using a license that is compatible with other Xen.org projects (ideally GPLv2). ... ----------------------------------------------------------------------------------- On most of these, we are fine: - We would need however a mentor (one of the committers or existing leads) and sponsor (I can be that) - And we need to announce the intention of forming an incubation project and then giving the community a couple of weeks to provide input ----------------------------------------------------------------------------------- ... The purpose of the project formation phase is to work out what the project is about, get community buy-in and help the future project gain publicity and momentum. The formation phase is driven by the project lead. The project mentor's role is to advise and support the project lead in getting the project started. The project proposal is a document that describes and is published on wiki.xen.org: - What the project is aiming to achieve (i.e. the project charter and project goals) - What components/code and in which code lines (new or components in other projects) the project aims to deliver - Key dependencies on other Xen.org projects (if applicable) - Lists initial maintainers (if applicable) - Lists any interested parties in the project (if applicable) - Lists any planned initial code contributions (if applicable) - A rough plan on how to get through the Incubation phase ... ----------------------------------------------------------------------------------- I would expect that you have most of this (at least in your head). I can help pull the rest together and the project mentor should al,so be able to provide advice. Hope this helped Regards Lars On 01/04/2012 02:35, Andrew Warkentin wrote: > On 3/30/12, Lars Kurth wrote: >> Andrew, >> >> that is good news. I see a number of options going forward, which really >> depends on your preference and also what committers and maintainers in >> the community think: >> 1) OpenXCI as a new project hosted on Xen.org - starting as an >> incubation project as per http://www.xen.org/projects/governance.html >> and archive the old one. What you describe sounds sufficiently different. >> >> 2) OpenXCI as a separate project: Xen.org can help you promoting the >> project in various ways >> >> If you want and have a bit more clarity on what you want to do and how >> you want to achieve things, I could arrange a call with you and walk you >> through the details. >> > I'm not quite sure which would be a better idea. I don't really have > much on the OpenXCI SourceForge project (just the Mercurial repository > for the graphics and input servers, as well as a tarball with the > corresponding qemu patches), so it might be easier to move it to > xen.org now rather than later. I do have a pretty good idea of what I > want OpenXCI to be - a configurable, high-performance multi-boot > alternative with good support for graphics passthrough, using a > similar architecture to XenClient (but using direct GPU passthrough > for one domain and either a "reverse graphics adapter" or a VNC > connection to display other domains, possibly with some kind of > support for 3D on non-passthrough domains using virtual GPUs being > added later). > > _______________________________________________ > Xci-devel mailing list > Xci-devel@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xci-devel _______________________________________________ Xci-devel mailing list Xci-devel@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xci-devel From xci-devel-bounces@lists.xen.org Tue Apr 03 15:04:32 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 03 Apr 2012 15:04:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SF5Hb-0007wA-Jk; Tue, 03 Apr 2012 15:04:31 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SF5Ha-0007vs-KW for xci-devel@lists.xen.org; Tue, 03 Apr 2012 15:04:30 +0000 Received: from [85.158.143.99:37577] by server-1.bemta-4.messagelabs.com id C8/33-20925-D711B7F4; Tue, 03 Apr 2012 15:04:29 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-6.tower-216.messagelabs.com!1333465468!22119703!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8281 invoked from network); 3 Apr 2012 15:04:28 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-6.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 3 Apr 2012 15:04:28 -0000 Received: by bkcjg9 with SMTP id jg9so4033252bkc.32 for ; Tue, 03 Apr 2012 08:04:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=MyInUtZ0bTabbZv+rbcE16wuQdH46Q6BtUU8iOCFwU4=; b=pJejlJX7OHynO5H7i8ZU2BbGzQ0F73nS18aigLIgHemwJOqqmd+EXSRfUTxpMPZQc1 rTkS9Bz3zot7F1L/RjVdIOM0T0mfVT1gRfKt4LvRFo3LAU9ckCn9fRCweyBB5sdkS09P pAx5gp/aIml6qsl6oxzIw16S9s2iPZggpvlZ+Sk4OysJxq5SEU8mZXspvD2sqy/TGnK0 Wy/DzPvI8KsXUZDK8fbDvtCn5we08cepVV9K0LfcSOliLsMOxyDiMma3GQGob9UPPBfF P1b99Fe8iUwoQQGFopwwbdjneZVP3/LTCnA18BP9mucCBMAczGG8zT5flLlF9A+RhI9B qkxg== Received: by 10.204.133.204 with SMTP id g12mr5737057bkt.64.1333465467780; Tue, 03 Apr 2012 08:04:27 -0700 (PDT) Received: from [172.16.25.10] (b0fb52a6.bb.sky.com. [176.251.82.166]) by mx.google.com with ESMTPS id f5sm46587029bke.9.2012.04.03.08.04.25 (version=SSLv3 cipher=OTHER); Tue, 03 Apr 2012 08:04:26 -0700 (PDT) Message-ID: <4F7B1178.6050001@xen.org> Date: Tue, 03 Apr 2012 16:04:24 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: xci-devel@lists.xen.org References: <4F74593B.9000003@xen.org> <4F7596CE.6000103@xen.org> In-Reply-To: Subject: Re: [Xci-devel] [Xen-devel] Archiving XCI : Request for an Archivation Review for the XCI project X-BeenThere: xci-devel@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xci-devel-bounces@lists.xen.org Errors-To: xci-devel-bounces@lists.xen.org Andrew, in that case - we should wait for the XCI archivation review To satisfy the development process we need (copied from governance) ----------------------------------------------------------------------------------- ... Forming a Project Requirements for forming a Xen.org project: - A project needs a lead, who is willing to become the project lead of the project - A project needs a sponsor, which can be a project lead of a mature project, a member of the Xen.org advisory board or the community manager - There should be no dissent from other community members who would qualify as sponsor (see "Principle: Consensus Decision Making") - A project needs a mentor, which can be the project sponsor or a maintainer of a mature project - A project needs to have a relationship to other Xen.org projects, i.e. it aims to develop software that has a dependency on other Xen.org projects. If the project needs components in other Xen.org projects to work, then this should also be stated. - A project needs to be large and long-term enough to grant a separate project. For example adding support for a new CPU architecture, adding additional functionality on top of existing projects, etc. Adding a new feature to an existing project should be performed within an existing project. - A project will deliver code using a license that is compatible with other Xen.org projects (ideally GPLv2). ... ----------------------------------------------------------------------------------- On most of these, we are fine: - We would need however a mentor (one of the committers or existing leads) and sponsor (I can be that) - And we need to announce the intention of forming an incubation project and then giving the community a couple of weeks to provide input ----------------------------------------------------------------------------------- ... The purpose of the project formation phase is to work out what the project is about, get community buy-in and help the future project gain publicity and momentum. The formation phase is driven by the project lead. The project mentor's role is to advise and support the project lead in getting the project started. The project proposal is a document that describes and is published on wiki.xen.org: - What the project is aiming to achieve (i.e. the project charter and project goals) - What components/code and in which code lines (new or components in other projects) the project aims to deliver - Key dependencies on other Xen.org projects (if applicable) - Lists initial maintainers (if applicable) - Lists any interested parties in the project (if applicable) - Lists any planned initial code contributions (if applicable) - A rough plan on how to get through the Incubation phase ... ----------------------------------------------------------------------------------- I would expect that you have most of this (at least in your head). I can help pull the rest together and the project mentor should al,so be able to provide advice. Hope this helped Regards Lars On 01/04/2012 02:35, Andrew Warkentin wrote: > On 3/30/12, Lars Kurth wrote: >> Andrew, >> >> that is good news. I see a number of options going forward, which really >> depends on your preference and also what committers and maintainers in >> the community think: >> 1) OpenXCI as a new project hosted on Xen.org - starting as an >> incubation project as per http://www.xen.org/projects/governance.html >> and archive the old one. What you describe sounds sufficiently different. >> >> 2) OpenXCI as a separate project: Xen.org can help you promoting the >> project in various ways >> >> If you want and have a bit more clarity on what you want to do and how >> you want to achieve things, I could arrange a call with you and walk you >> through the details. >> > I'm not quite sure which would be a better idea. I don't really have > much on the OpenXCI SourceForge project (just the Mercurial repository > for the graphics and input servers, as well as a tarball with the > corresponding qemu patches), so it might be easier to move it to > xen.org now rather than later. I do have a pretty good idea of what I > want OpenXCI to be - a configurable, high-performance multi-boot > alternative with good support for graphics passthrough, using a > similar architecture to XenClient (but using direct GPU passthrough > for one domain and either a "reverse graphics adapter" or a VNC > connection to display other domains, possibly with some kind of > support for 3D on non-passthrough domains using virtual GPUs being > added later). > > _______________________________________________ > Xci-devel mailing list > Xci-devel@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xci-devel _______________________________________________ Xci-devel mailing list Xci-devel@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xci-devel From xci-devel-bounces@lists.xen.org Mon Apr 30 14:20:42 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 30 Apr 2012 14:20:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOrSy-00004z-VN; Mon, 30 Apr 2012 14:20:40 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOrSx-0008WK-QH for xci-devel@lists.xen.org; Mon, 30 Apr 2012 14:20:39 +0000 Received: from [193.109.254.147:26041] by server-8.bemta-14.messagelabs.com id C2/8F-23244-7BF9E9F4; Mon, 30 Apr 2012 14:20:39 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-2.tower-27.messagelabs.com!1335795638!6944931!1 X-Originating-IP: [209.85.215.173] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8309 invoked from network); 30 Apr 2012 14:20:38 -0000 Received: from mail-ey0-f173.google.com (HELO mail-ey0-f173.google.com) (209.85.215.173) by server-2.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 30 Apr 2012 14:20:38 -0000 Received: by eaaf11 with SMTP id f11so705388eaa.32 for ; Mon, 30 Apr 2012 07:20:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=74Zk9kKRa07ixsLcVK6fnwfu0kvVzMxOoNq6tUYEeoA=; b=ZGOZ6C5d17aC5XVDvW+uZFchAt+BZqSw53arr9tKUITHi9bKEEtiCKdQFSMCCpzMW+ 7yHPslBOZy6AuQ88eBj7rrGT3s89X7gqcVSPDyQyi1a05F1aSWM2/KnihsydqX/i/Jm2 wRYQPH1f6yF1XuMIttfYKQLlruk+IG3DGiKX1PIS9dXIPaRqb7dA3Cc1BwW2Zwee0utq BfesTkFLi5lERJ1NJ4jSWkLUcH+2PAO4/VKNOX4WWGNAQ8CG/7LkRUV6Lp0JyeqiCgZN WNfZnsoBXtEreaovxgICNXLJY2cv863puPhc3zqDlh1z+A3/DRY+ADKqm/wKCAQEB98A JGyg== Received: by 10.14.96.78 with SMTP id q54mr4305745eef.106.1335795637762; Mon, 30 Apr 2012 07:20:37 -0700 (PDT) Received: from [172.16.25.10] (b0fb6237.bb.sky.com. [176.251.98.55]) by mx.google.com with ESMTPS id r44sm75856255eef.2.2012.04.30.07.20.32 (version=SSLv3 cipher=OTHER); Mon, 30 Apr 2012 07:20:33 -0700 (PDT) Message-ID: <4F9E9FAF.5000908@xen.org> Date: Mon, 30 Apr 2012 15:20:31 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: xci-devel@lists.xen.org Subject: [Xci-devel] XCI archivation review X-BeenThere: xci-devel@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: List for the Xen Client Intiative List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xci-devel-bounces@lists.xen.org Errors-To: xci-devel-bounces@lists.xen.org Hi, nobody really has stepped up with respect of reviving XCI, so my proposal is to hold an archivation review the week of May 21st. Anybody who wants to participate or has a view please a) let me know that you want to participate b) Provide me with a couple of time-slots Best Regards Lars _______________________________________________ Xci-devel mailing list Xci-devel@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xci-devel From xci-devel-bounces@lists.xen.org Mon Apr 30 14:20:42 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 30 Apr 2012 14:20:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOrSy-00004z-VN; Mon, 30 Apr 2012 14:20:40 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOrSx-0008WK-QH for xci-devel@lists.xen.org; Mon, 30 Apr 2012 14:20:39 +0000 Received: from [193.109.254.147:26041] by server-8.bemta-14.messagelabs.com id C2/8F-23244-7BF9E9F4; Mon, 30 Apr 2012 14:20:39 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-2.tower-27.messagelabs.com!1335795638!6944931!1 X-Originating-IP: [209.85.215.173] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8309 invoked from network); 30 Apr 2012 14:20:38 -0000 Received: from mail-ey0-f173.google.com (HELO mail-ey0-f173.google.com) (209.85.215.173) by server-2.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 30 Apr 2012 14:20:38 -0000 Received: by eaaf11 with SMTP id f11so705388eaa.32 for ; Mon, 30 Apr 2012 07:20:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=74Zk9kKRa07ixsLcVK6fnwfu0kvVzMxOoNq6tUYEeoA=; b=ZGOZ6C5d17aC5XVDvW+uZFchAt+BZqSw53arr9tKUITHi9bKEEtiCKdQFSMCCpzMW+ 7yHPslBOZy6AuQ88eBj7rrGT3s89X7gqcVSPDyQyi1a05F1aSWM2/KnihsydqX/i/Jm2 wRYQPH1f6yF1XuMIttfYKQLlruk+IG3DGiKX1PIS9dXIPaRqb7dA3Cc1BwW2Zwee0utq BfesTkFLi5lERJ1NJ4jSWkLUcH+2PAO4/VKNOX4WWGNAQ8CG/7LkRUV6Lp0JyeqiCgZN WNfZnsoBXtEreaovxgICNXLJY2cv863puPhc3zqDlh1z+A3/DRY+ADKqm/wKCAQEB98A JGyg== Received: by 10.14.96.78 with SMTP id q54mr4305745eef.106.1335795637762; Mon, 30 Apr 2012 07:20:37 -0700 (PDT) Received: from [172.16.25.10] (b0fb6237.bb.sky.com. [176.251.98.55]) by mx.google.com with ESMTPS id r44sm75856255eef.2.2012.04.30.07.20.32 (version=SSLv3 cipher=OTHER); Mon, 30 Apr 2012 07:20:33 -0700 (PDT) Message-ID: <4F9E9FAF.5000908@xen.org> Date: Mon, 30 Apr 2012 15:20:31 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: xci-devel@lists.xen.org Subject: [Xci-devel] XCI archivation review X-BeenThere: xci-devel@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: List for the Xen Client Intiative List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xci-devel-bounces@lists.xen.org Errors-To: xci-devel-bounces@lists.xen.org Hi, nobody really has stepped up with respect of reviving XCI, so my proposal is to hold an archivation review the week of May 21st. Anybody who wants to participate or has a view please a) let me know that you want to participate b) Provide me with a couple of time-slots Best Regards Lars _______________________________________________ Xci-devel mailing list Xci-devel@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xci-devel