Re: [Xci-devel] [Xen-devel] Archiving XCI : Request for an Archivation Review for the XCI project

[Lars Kurth <lars.kurth@xxxxxxx>]

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<lars.kurth@xxxxxxx>  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@xxxxxxxxxxxxx
> http://lists.xen.org/cgi-bin/mailman/listinfo/xci-devel

_______________________________________________
Xci-devel mailing list
Xci-devel@xxxxxxxxxxxxx
http://lists.xen.org/cgi-bin/mailman/listinfo/xci-devel