xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Lars Kurth <lars.kurth@xen.org>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Artem Mygaiev <artem.mygaiev@globallogic.com>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	Dario Faggioli <dario.faggioli@citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	David Vrabel <david.vrabel@citrix.com>,
	Andrii Tseglytskyi <andrii.tseglytskyi@globallogic.com>
Subject: Re: [Need Input] (informal) Automotive PV drivers subproject request
Date: Mon, 09 Jun 2014 14:31:11 +0100	[thread overview]
Message-ID: <5395B71F.8060707@xen.org> (raw)
In-Reply-To: <21397.45741.953881.375975@mariner.uk.xensource.com>

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/<subproject name>/pvdrivers.git

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.)

> 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

  reply	other threads:[~2014-06-09 13:31 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-04 13:04 Automotive PV drivers project request Artem Mygaiev
2014-06-04 14:22 ` [Need Input] (informal) Automotive PV drivers subproject request Lars Kurth
2014-06-04 16:35   ` Dario Faggioli
2014-06-05 12:47     ` Artem Mygaiev
2014-06-05 13:32       ` Dario Faggioli
2014-06-06  8:59       ` Ian Campbell
2014-06-06 13:05         ` Lars Kurth
2014-06-06 15:08           ` Ian Campbell
2014-06-06 19:49             ` Artem Mygaiev
2014-06-06 22:01               ` Dario Faggioli
2014-06-09 10:18                 ` Stefano Stabellini
2014-06-09 12:25                   ` Lars Kurth
2014-06-09 12:30                     ` Ian Campbell
2014-06-09 13:14                       ` Lars Kurth
2014-06-09 12:37                     ` Lars Kurth
2014-06-09 13:12                       ` Ian Jackson
2014-06-09 13:31                         ` Lars Kurth [this message]
2014-06-10 14:22                           ` Artem Mygaiev
2014-06-10 14:51                             ` Lars Kurth
2014-06-09 12:15               ` Lars Kurth
2014-06-11 11:37       ` Lars Kurth
2014-06-04 14:36 ` Automotive PV drivers project request Roger Pau Monné
2014-06-04 15:21   ` [Need Input] (informal) Automotive PV drivers subproject request Lars Kurth
2014-06-04 15:34     ` Roger Pau Monné
2014-06-05 13:07       ` Artem Mygaiev
2014-06-05 13:17 ` Automotive PV drivers project request David Vrabel
2014-06-05 13:22   ` Artem Mygaiev
2014-06-10 12:38     ` David Vrabel
2014-06-10 14:09       ` Lars Kurth
2014-06-10 14:18         ` Artem Mygaiev
2014-06-11 10:10           ` Stefano Stabellini
2014-06-11 15:08             ` Automotive PV drivers project request (need more input) Lars Kurth
2014-06-12  9:34               ` Stefano Stabellini
2014-06-12 13:43                 ` Paul Durrant

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=5395B71F.8060707@xen.org \
    --to=lars.kurth@xen.org \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=andrii.tseglytskyi@globallogic.com \
    --cc=artem.mygaiev@globallogic.com \
    --cc=dario.faggioli@citrix.com \
    --cc=david.vrabel@citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).