From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lars Kurth Subject: Re: [Need Input] (informal) Automotive PV drivers subproject request Date: Tue, 10 Jun 2014 15:51:11 +0100 Message-ID: <53971B5F.10804@xen.org> References: <538F2BA7.8060806@xen.org> <1401899758.6866.44.camel@Solace> <1402045192.29759.31.camel@kazak.uk.xensource.com> <5391BC9C.40503@xen.org> <1402067321.1313.95.camel@kazak.uk.xensource.com> <1402092104.29895.18.camel@Abyss> <5395A7B7.4080203@xen.org> <5395AA78.1080904@xen.org> <21397.45741.953881.375975@mariner.uk.xensource.com> <5395B71F.8060707@xen.org> Reply-To: lars.kurth@xen.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7582337897098217124==" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Artem Mygaiev Cc: Ian Campbell , Stefano Stabellini , Dario Faggioli , Ian Jackson , "xen-devel@lists.xen.org" , David Vrabel , Andrii Tseglytskyi List-Id: xen-devel@lists.xenproject.org This is a multi-part message in MIME format. --===============7582337897098217124== Content-Type: multipart/alternative; boundary="------------040604080103030101000101" This is a multi-part message in MIME format. --------------040604080103030101000101 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 10/06/2014 15:22, Artem Mygaiev wrote: > > However, if we allowed linux.git and xen.git in xenbits.xen.org/ > , it does increase the > risk of creating a permanent fork (i.e. the main concerns raised > by IanC, Stefano, etc.) > > > ​True. But this is always a risk (like with mentioned XenRT), even > without staging trees in subprojects​. To me it is more a matter of > maintainers' and community discipline... How about xenbits.xen.org/ /staging/ for the staging trees, if there is consensus to do this. But we can leave this open for now: it's not blocking us from moving forward I have enough to work on a formal subproject proposal and started at http://wiki.xenproject.org/wiki/Embedded_and_Automotive_PV_Drivers_Project_Proposal Regards Lars --------------040604080103030101000101 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
On 10/06/2014 15:22, Artem Mygaiev wrote:

However, if we allowed linux.git and xen.git in xenbits.xen.org/<subproject name>, it does increase the risk of creating a permanent fork (i.e. the main concerns raised by IanC, Stefano, etc.)

​True. But this is always a risk (like with mentioned XenRT), even without staging trees in subprojects​. To me it is more a matter of maintainers' and community discipline...
How about xenbits.xen.org/<subproject name>/staging/ for the staging trees, if there is consensus to do this.
But we can leave this open for now: it's not blocking us from moving forward

I have enough to work on a formal subproject proposal and started at http://wiki.xenproject.org/wiki/Embedded_and_Automotive_PV_Drivers_Project_Proposal

Regards
Lars





--------------040604080103030101000101-- --===============7582337897098217124== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --===============7582337897098217124==--