Re: identifying software and licenses used in base install

If your customer is not satisfied by simply pointing to the terms that cover the whole of OpenBSD, and if they insist on some kind of audit of the whole tree. Well then, offer it - but charge more. Point out that what they're asking for would be unreasonably complex and expensive no matter

Re: identifying software and licenses used in base install

> On 01/19/18 01:12, Theo de Raadt wrote: > >> FWIW, the permission I seek is from my Legal department. > > > > That maybe your job but it isn't the project's job. > > > Enough is enough. That sentence above makes it clear who is getting > > paid for satisfying those requirements: You. > >

Re: identifying software and licenses used in base install

On 01/19/18 01:12, Theo de Raadt wrote: >> FWIW, the permission I seek is from my Legal department. > > That maybe your job but it isn't the project's job. > Enough is enough. That sentence above makes it clear who is getting > paid for satisfying those requirements: You. Huh, where did he

Re: identifying software and licenses used in base install

> > FWIW, the permission I seek is from my Legal department. They want to ensure > that 1) we don't use software having unacceptable licenses or in unacceptable > ways, and 2) that the terms of all the copyrights are adhered to (e.g., > reproducing attribution statements, etc.). > In my

Re: identifying software and licenses used in base install

"Jake D. Parsons" writes: > You seem to be railing against some perceived notion of injustice in Injustice? No. Irrelevence. > some perceived notion utopia. What is the point and agenda here? Why do Utopia? Have you ever even *run* a computer system? My point is that I'm tired of the excessive

Re: identifying software and licenses used in base install

>FWIW, the permission I seek is from my Legal department. That maybe your job but it isn't the project's job. We could write the document you need. Then the next comment would probably we that we didn't publish our procedure and have a lawyer sign off on what we did. It is a neverending

Re: identifying software and licenses used in base install

FWIW, the permission I seek is from my Legal department.  They want to ensure that 1) we don't use software having unacceptable licenses or in unacceptable ways, and 2) that the terms of all the copyrights are adhered to (e.g., reproducing attribution statements, etc.). At this point, it

Re: identifying software and licenses used in base install

2018-01-18 9:28 GMT+01:00 Janne Johansson : > 2018-01-18 8:27 GMT+01:00 : > >> > > Is there, by chance, such a breakdown available for these already? >> >> > So for "commercial vs free" or "BSD-ish vs GPL" you might be safe to know > all except the gnu stuff

Re: identifying software and licenses used in base install

Hi Nick, Nick Holland wrote on Wed, Jan 17, 2018 at 09:44:41PM -0500: > Things that aren't BSD-ish license are in /usr/src/gnu. Still true, but... > If that's where your problem is, that's what you want to leave out. ... that part is mildly misleading. Large parts below /usr/src/gnu/ *are*

Re: identifying software and licenses used in base install

Hi, cho...@jtan.com wrote on Thu, Jan 18, 2018 at 09:27:22AM +0200: > ... as more time goes by the more damage and less advantage I see > by the existence of software licenses. This is imprecise. The *proliferation* of software licenses is indeed a problem, in particular the proliferation of

Re: identifying software and licenses used in base install

Hi Kent, Kent Watsen wrote on Wed, Jan 17, 2018 at 11:11:40PM +: > I'm throwing together a quick proof-of-concept thingy to give to a > customer and thought it might be fun to use OpenBSD as the OS for the > VM image. Unfortunately, the not so fun part of it is that I'm > required to get

Re: identifying software and licenses used in base install

2018-01-18 8:27 GMT+01:00 : > "Theo de Raadt" writes: > > > Is there, by chance, such a breakdown available for these already? > > > > No. We did our best. > > To be fair, these statements are potentially contradictory. If you > (plural) only "did your best" (and what more could

Re: identifying software and licenses used in base install

cho...@jtan.com writes: > "Theo de Raadt" writes: > > > Is there, by chance, such a breakdown available for these already? > > > > > No. We did our best. > > To be fair, these statements are potentially contradictory. If you > (plural) only "did your best" (and what more could have been done?) >

Re: identifying software and licenses used in base install

On Thu, Jan 18, 2018 at 09:27:22AM +0200, cho...@jtan.com wrote: > "Theo de Raadt" writes: > > > Is there, by chance, such a breakdown available for these already? > > > > No. We did our best. > > To be fair, these statements are potentially contradictory. If you (plural) > only "did your

Re: identifying software and licenses used in base install

"Theo de Raadt" writes: > > Is there, by chance, such a breakdown available for these already? > > No. We did our best. To be fair, these statements are potentially contradictory. If you (plural) only "did your best" (and what more could have been done?) then it is at least in *theory*

Re: identifying software and licenses used in base install

On Thu, Jan 18, 2018 at 12:31 AM, Theo de Raadt wrote: > Sometimes it is almost like there is a stream of people who want us > to stop trying. > > And quit. Some of you can see it, right? yes. :( Worse, i am concerned that i might have been contributing to that effect -

Re: identifying software and licenses used in base install

> Is there, by chance, such a breakdown available for these already? No. We did our best. Always interesting that the more one works in the free software space, the more constraints get added by the public. Sometimes it is almost like there is a stream of people who want us to stop trying.

Re: identifying software and licenses used in base install

On 01/17/18 18:11, Kent Watsen wrote: > > I'm throwing together a quick proof-of-concept thingy to give to a > customer and thought it might be fun to use OpenBSD as the OS for the > VM image.  Unfortunately, the not so fun part of it is that I'm > required to get permission to

identifying software and licenses used in base install

I'm throwing together a quick proof-of-concept thingy to give to a customer and thought it might be  fun to use OpenBSD as the OS for the VM image.   Unfortunately, the not so fun part of it is that I'm required to get permission to use/distribute this open source software, which entails