From mboxrd@z Thu Jan 1 00:00:00 1970 From: Artem Mygaiev Subject: Re: [Need Input] (informal) Automotive PV drivers subproject request Date: Tue, 10 Jun 2014 17:22:08 +0300 Message-ID: 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> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3794001583040737688==" Return-path: In-Reply-To: <5395B71F.8060707@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: Ian Campbell , Stefano Stabellini , Dario Faggioli , Ian Jackson , "xen-devel@lists.xen.org" , David Vrabel , Andrii Tseglytskyi List-Id: xen-devel@lists.xenproject.org --===============3794001583040737688== Content-Type: multipart/alternative; boundary=089e0122ea1c8b086904fb7c0d11 --089e0122ea1c8b086904fb7c0d11 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable > > So: >> >> * we need an official xenbits.org/pvdrivers.git repo; it would also com= e >>> 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/ name>/pvdrivers.git > =E2=80=8BI like the idea :)=E2=80=8B However, if we allowed linux.git and xen.git in xenbits.xen.org/ name>, it does increase the risk of creating a permanent fork (i.e. the > main concerns raised by IanC, Stefano, etc.) =E2=80=8BTrue. But this is always a risk (like with mentioned XenRT), even = without staging trees in subprojects=E2=80=8B. To me it is more a matter of maintai= ners' and community discipline... Artem Mygaiev | AVP - Delivery GlobalLogic P +380.44.4929695 ext.2023 M +380.67.9211131 S rosenkrantzguildenstern www.globallogic.com http://www.globallogic.com/email_disclaimer.txt=E2=80=8B --089e0122ea1c8b086904fb7c0d11 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
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:

=C2=A0 =C2=A0xenbits.xen.org/automotive/pvdrivers.git
=C2=A0 =C2=A0xenbits.xen.org/automotive/linux.git
=C2=A0 =C2=A0xenbits.xen.org/automotive/xen.git
=C2=A0 =C2=A0etc.

(FSVO "automotive"; I currently have no opinion about the project=
name.)
That would make sense. So we follow the convention xenbits.xen.org/<subproject name>/p= vdrivers.git

=E2=80=8BI like the idea :)=E2=80=8B

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 con= cerns raised by IanC, Stefano, etc.)

=E2=80=8BTrue. But this is alw= ays a risk (like with mentioned XenRT), even without staging trees in subpr= ojects=E2=80=8B. To me it is more a matter of maintainers' and communit= y discipline...

Artem Mygaiev |=C2=A0AVP - Delivery
GlobalLogic
P +380.44.4929695 ext.2023=C2=A0
M +380.67.9211131 S rosen= krantzguildenstern

--089e0122ea1c8b086904fb7c0d11-- --===============3794001583040737688== 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 --===============3794001583040737688==--