From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Lars Kurth <lars.kurth@xen.org>
Cc: Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Archiving PVOPS and Xen on ARM as stand-alone subprojects
Date: Fri, 27 Jun 2014 12:35:18 -0400 [thread overview]
Message-ID: <20140627163518.GA29794@laptop.dumpdata.com> (raw)
In-Reply-To: <53AD77DA.9040408@xen.org>
On Fri, Jun 27, 2014 at 02:55:38PM +0100, Lars Kurth wrote:
> Hi all,
> I was wondering how the community feels if we retired
>
> * http://xenproject.org/developers/teams/pvops.html
> * http://xenproject.org/developers/teams/arm-hypervisor.html
>
> as stand-alone subprojects of the Xen Projects in line
> withttp://xenproject.org/governance.html (see
> http://xenproject.org/governance.html - Archivation Review). I had already
> discussed with Stefano and Konrad and they believe this is a good idea. I
> have also raised the at the last Advisory Board meeting and the feedback was
> that this is a good, idea if we craft the messaging around this correctly as
> to not to cause confusion.
>
> Why Archive these subprojects?
> * The goal of both subprojects was to establish Xen support in Linux and ARM
> support in the Hypervisor in the upstream projects
> * This clearly has been achieved, so it is not necessary any more to keep
> these around as separate supbrojects
> * Xen support is firmly established as part of Linux kernel releases
> * ARM support is firmly established as part of the Hypervisor
>
> What does it NOT mean?
> * Development of Xen in Linux would not stop - we merely treat it as part of
> upstream development (which is what we have de-facto today)
> * Development of Xen on ARM would not stop - we merely treat it as part of
> upstream development (which again is the de-facto status today)
> * We already retired separate mailing lists and PR tends to be handled as
> part of the upstream development. The main impact is that two xenproject.org
> pages would either disappear, become smaller or become merged with (or
> subpages) of http://xenproject.org/developers/teams/hypervisor.html
>
> What are the next step?
> * Consultation (this mail)
> * Make an archivation proposal
> * Formal vote
> * Craft a positive messaging as part of a momentum press release : the
> message would be that we are making progress, that our governance model
> works and we can tie it up with the creation of say the PV driver project.
> In other words, the project is evolving and addressing issues.
>
> Any views?
+1 on archiving it.
>
> Best Regards
> Lars
>
next prev parent reply other threads:[~2014-06-27 16:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 13:55 Archiving PVOPS and Xen on ARM as stand-alone subprojects Lars Kurth
2014-06-27 16:35 ` Konrad Rzeszutek Wilk [this message]
2014-06-28 9:51 ` Juergen Gross
2014-06-30 15:18 ` Stefano Stabellini
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=20140627163518.GA29794@laptop.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=lars.kurth@xen.org \
--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.