On 2016-11-01 14:10:44 -0400 (-0400), Ben Swartzlander wrote:
> On 11/01/2016 12:03 PM, Jeremy Stanley wrote:
[...]
> > into it the kernel's process space. This is the closest analogue we
> > have to our drivers importing proprietary Python modules.
>
> I'm not talking about python code here. I'm
On 11/01/2016 12:03 PM, Jeremy Stanley wrote:
On 2016-11-01 00:26:11 -0400 (-0400), Ben Swartzlander wrote:
[...]
As usual I'd like to point to the Linux project as a good example
for how to handle such things. Linux is older than us and has been
dealing with drivers and proprietary code for a
On 2016-11-01 12:29:27 -0500 (-0500), Sean McGinnis wrote:
[...]
> Is importing proprietary libs really a legal issue? If it happens at
> runtime based on how the user configured the system, and they have
> whatever licensing rights _they_ need to use that library/CLI, I
> don't see an issue with
On Tue, Nov 01, 2016 at 03:47:11PM +, Jeremy Stanley wrote:
> On 2016-10-31 13:23:48 -0500 (-0500), Sean McGinnis wrote:
> > Last Tuesday we had a cross-project session around the use of
> > proprietary code/libs/binaries in OpenStack drivers. The challenge
> > we are running into is where to
On Tue, Nov 01, 2016 at 12:26:11AM -0400, Ben Swartzlander wrote:
> On 10/31/2016 02:23 PM, Sean McGinnis wrote:
> >Last Tuesday we had a cross-project session around the use of proprietary
> >code/libs/binaries in OpenStack drivers. The challenge we are running into
> >is where to draw the line
On 2016-11-01 00:26:11 -0400 (-0400), Ben Swartzlander wrote:
[...]
> As usual I'd like to point to the Linux project as a good example
> for how to handle such things. Linux is older than us and has been
> dealing with drivers and proprietary code for a very long time.
>
> Linux does a few
On 2016-10-31 13:23:48 -0500 (-0500), Sean McGinnis wrote:
> Last Tuesday we had a cross-project session around the use of
> proprietary code/libs/binaries in OpenStack drivers. The challenge
> we are running into is where to draw the line with these drivers.
> What is the appropriate policy to
On 10/31/2016 02:23 PM, Sean McGinnis wrote:
Last Tuesday we had a cross-project session around the use of proprietary
code/libs/binaries in OpenStack drivers. The challenge we are running into
is where to draw the line with these drivers. What is the appropriate policy
to have in place to
