xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Lars Kurth <lars.kurth@xen.org>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	Artem Mygaiev <artem.mygaiev@globallogic.com>
Cc: Andrii Tseglytskyi <andrii.tseglytskyi@globallogic.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	David Vrabel <david.vrabel@citrix.com>,
	Paul Durrant <paul.durrant@citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Automotive PV drivers project request (need more input)
Date: Wed, 11 Jun 2014 16:08:38 +0100	[thread overview]
Message-ID: <539870F6.8070201@xen.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1406111105290.13771@kaball.uk.xensource.com>

Hi all,

I collated this thread into 
http://wiki.xen.org/wiki/Embedded_and_Automotive_PV_Drivers_Project_Proposal 


This raises a number of extra questions besides the licensing questions 
I raised to Artem earlier.

Q1: should we have separate git repos per OS, e.g.
   git://xenbits.xen.org/pvdrivers/xen-linux-user-drivers.git
   git://xenbits.xen.org/pvdrivers/xen-qnx-drivers.git

instead of
   git://xenbits.xen.org/pvdrivers/pvdrivers.git

This sounds more user friendly and scalable

Q2: should 
http://wiki.xen.org/wiki/Windows_PV_Drivers_Incubation_Project_Proposal 
& 
http://wiki.xen.org/wiki/Embedded_and_Automotive_PV_Drivers_Project_Proposal 
share infrastructure (e.g. lists, web portal, 
git://xenbits.xen.org/pvdrivers/) or even be merged

There is no clear-cut answer.

Arguments against merging:
* Forces people with very different interests into one subproject (aka 
creates unnecessary noise)
* Dilutes Project Leadership

Arguments for merging:
* Critical mass for graduation is more easily reached (but may be fake)
* Increases chances of building a sustainable community

If we don't merge, we should not use the generic label "pvdrivers" for 
xenbits and mailing lists for this proposal, but use something more 
specific. We also need a label for the Windows PV driver project.

Best Regards
Lars

  reply	other threads:[~2014-06-11 15:08 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
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             ` Lars Kurth [this message]
2014-06-12  9:34               ` Automotive PV drivers project request (need more input) 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=539870F6.8070201@xen.org \
    --to=lars.kurth@xen.org \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=andrii.tseglytskyi@globallogic.com \
    --cc=artem.mygaiev@globallogic.com \
    --cc=david.vrabel@citrix.com \
    --cc=paul.durrant@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).