From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lars Kurth Subject: Re: [Need Input] (informal) Automotive PV drivers subproject request Date: Mon, 09 Jun 2014 14:31:11 +0100 Message-ID: <5395B71F.8060707@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> Reply-To: lars.kurth@xen.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <21397.45741.953881.375975@mariner.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Jackson Cc: Artem Mygaiev , Ian Campbell , Stefano Stabellini , Dario Faggioli , "xen-devel@lists.xen.org" , David Vrabel , Andrii Tseglytskyi List-Id: xen-devel@lists.xenproject.org On 09/06/2014 14:12, Ian Jackson wrote: > Lars Kurth writes ("Re: [Xen-devel] [Need Input] (informal) Automotive PV drivers subproject request"): >> As an aside, >> >> it looks to me as if we were close enough to draft a subproject proposal >> on the wiki. As far I can see we agreed on >> * we need a subproject > I would just like to quibble with your pathnames. I think that the > subproject should have its own subdirectory, which should contain all > of its repos. I don't mind. I missed the convention you outlined > So: > >> * we need an official xenbits.org/pvdrivers.git repo; it would also come >> with its own mailing list if desired >> * in addition we need integration branches for xen.git, linux.git, >> pvdrivers.git - it appears that the consensus here is that we use the >> same pattern as elsewhere > Rather, we should have: > > xenbits.xen.org/automotive/pvdrivers.git > xenbits.xen.org/automotive/linux.git > xenbits.xen.org/automotive/xen.git > etc. > > (FSVO "automotive"; I currently have no opinion about the project > name.) That would make sense. So we follow the convention xenbits.xen.org//pvdrivers.git 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.) > Cf xenbits.xen.org/xenclient/, xenbits.xen.org/kemari/, > xenbits.xen.org/xcp/, xenbits.xen.org/xenrt-citrix/ ... > > > NB these are mostly git url fragments, not http url fragments. So eg > "xenbits.xen.org/xenrt-citrix/" contains "xenrt.git" which is > accessible via > git clone git://xenbits.xen.org/xenrt-citrix/xenrt.git > (and also via the gitweb index etc.) > > If it is helpful there is no technical reason why it would be > difficult to provide a subproject with a webtree on xenbits that would > be accessible via http://xenbits.xen.org/subproject/. But we don't > want xenbits to be used for general-purpose web hosting. > > AIUI this particular subproject doesn't have a requirement at this > stage for a separate web hosting setup. I wasn't aware of it. And we don't need it >> (aka the location for the staging branch is in xenbits.org/people). >> Maybe with some mods, e.g. people/automotive/* instead of people/* - >> although this is not yet finally agreed. There are still differing >> opinions on naming. > I agree with Ian Campbell that we do not want subproject names in > people/. That is strictly for human beings, and contains only > "unofficial" repos. OK. Regards Lars