From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Archiving PVOPS and Xen on ARM as stand-alone subprojects Date: Fri, 27 Jun 2014 12:35:18 -0400 Message-ID: <20140627163518.GA29794@laptop.dumpdata.com> References: <53AD77DA.9040408@xen.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <53AD77DA.9040408@xen.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Lars Kurth Cc: Stefano Stabellini , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.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 >