Xymon Mailing List Archive search

license question

7 messages in this thread

list Jan Vojtko · Fri, 27 Feb 2009 16:34:34 +0100 ·
Hi,
we would like to use hobbit as the part of our monitoring system delivered 
to our customers. Can we do it?

Thanks and Regards
Jan


Jan Vojtko
Professional services Project manager
COMPAREX CZ s.r.o.
Dědinská 29/893
161 00 Praha 6 
Phone: +XXX XXX XXX XXX
Phone: +XXX XXX XXX XXX
Mobile: +XXX XXX XXX XXX
Fax: +XXX XXX XXX XXX
E-mail: user-d417e56601dc@xymon.invalid
www: http://www.comparex.cz
list Henrik Størner · Fri, 27 Feb 2009 18:35:58 +0100 ·
quoted from Jan Vojtko
On Fri, Feb 27, 2009 at 04:34:34PM +0100, Jan Vojtko wrote:
Hi,
we would like to use hobbit as the part of our monitoring system delivered 
to our customers.
You should read the COPYING file that comes with Hobbit, that is
the official license text for Hobbit.
Can we do it?
That means you will be "distributing" Hobbit in the legal sense of the
word, and therefore all of the terms of the GPLv2 license come into play.
What this means is essentially that if you make any modifications to
the Hobbit source code, then you must make these modifications available
to everyone - e.g. by posting the source code to your modified Hobbit
on a website. That includes any bugfixes, enhancements, custom
add-ons and modifications etc. Anything except changes to the
configuration files.

You are also obliged to provide your customers with the source code
to Hobbit if they ask for it, for a period of at least 3 years. 
And your customer is entitled to re-distribute Hobbit to others 
(if they want to do so, rather than just download it directly from 
Sourceforge).

Apart from that, you can pretty much do as you please. I would
appreciate it if you would consider contributing something to
the Hobbit developers (i.e. me) via the Paypal link on
www.xymon.com, but there is no legal obligation for you to do that.


Regards,
Henrik
list Iain M Conochie · Fri, 27 Feb 2009 17:56:45 +0000 ·
quoted from Henrik Størner
Henrik St?rner wrote:
On Fri, Feb 27, 2009 at 04:34:34PM +0100, Jan Vojtko wrote:
  
Hi,
we would like to use hobbit as the part of our monitoring system delivered to our customers.
    
You should read the COPYING file that comes with Hobbit, that is
the official license text for Hobbit.

  
Can we do it?
    
That means you will be "distributing" Hobbit in the legal sense of the
word, and therefore all of the terms of the GPLv2 license come into play.
What this means is essentially that if you make any modifications to
the Hobbit source code, then you must make these modifications available
to everyone - e.g. by posting the source code to your modified Hobbit
on a website. That includes any bugfixes, enhancements, custom
add-ons and modifications etc. Anything except changes to the
configuration files.
  
I am interested here. Say I work for a hosting company and I am selling dedicated servers. If I install the hobbit client on the server to monitor the server, am I "distributing" the code? Is this not more Software as a Service that was covered under GPLv3? Again this is just a point of interest for a Friday afternoon.

Cheers

Iain
quoted from Henrik Størner
You are also obliged to provide your customers with the source code
to Hobbit if they ask for it, for a period of at least 3 years. And your customer is entitled to re-distribute Hobbit to others (if they want to do so, rather than just download it directly from Sourceforge).

Apart from that, you can pretty much do as you please. I would
appreciate it if you would consider contributing something to
the Hobbit developers (i.e. me) via the Paypal link on
www.xymon.com, but there is no legal obligation for you to do that.


Regards,
Henrik

list Adam Goryachev · Sat, 28 Feb 2009 13:23:36 +1100 ·
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
quoted from Iain M Conochie

Iain M Conochie wrote:
Henrik St?rner wrote:
On Fri, Feb 27, 2009 at 04:34:34PM +0100, Jan Vojtko wrote:
 
Hi,
we would like to use hobbit as the part of our monitoring system
delivered to our customers.
You should read the COPYING file that comes with Hobbit, that is
the official license text for Hobbit.

That means you will be "distributing" Hobbit in the legal sense of the
word, and therefore all of the terms of the GPLv2 license come into play.
What this means is essentially that if you make any modifications to
the Hobbit source code, then you must make these modifications available
to everyone - e.g. by posting the source code to your modified Hobbit
on a website. That includes any bugfixes, enhancements, custom
add-ons and modifications etc. Anything except changes to the
configuration files.
Actually, I was of the impression you are only required to distribute
(actually, just make available in a reasonable method) the source code
to the people you have given the binaries. AFAIK, you don't *have* to
distribute it to everyone. However, any person who you have given the
binary can request the source code, and can then re-distribute the
source code to any other third party.... ie, you can't restrict it, but
you don't have to help it be distributed....
quoted from Iain M Conochie
I am interested here. Say I work for a hosting company and I am selling
dedicated servers. If I install the hobbit client on the server to
monitor the server, am I "distributing" the code? Is this not more
Software as a Service that was covered under GPLv3? Again this is just a
point of interest for a Friday afternoon.
The question I would ask is are you installing a modified version of the
hobbit client anyway? I would think most people would install the
standard hobbit client with a couple of config settings/etc... maybe
custom ext scripts (which don't fall under the hobbit license anyway),
etc...

PS, not that I am suggesting people should not share any work they do!

PPS, I did do some work for a client a number of years ago (before
hobbit, with BB) where we customised (read wrote a new) web interface.
The bb client was stock standard and re-distributed, but the work on the
server was never distributed, hence source code didn't need to be
shared. This was basically to let each client login and see their own
status, and nobody else's, and let the company
configure/setup/delete/etc the clients monitoring/passwords/etc...
Unfortunately, the company went bust, and I lost all copies of the work
I had done...

PPPS, and I am not a lawyer :)

Regards,
Adam

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkmooB8ACgkQGyoxogrTyiUo9gCgp8hehXQP9nY3X/YACBzWK4w3
TUAAmwQKYkkM6rv9tEUf7XmW3fLfKQBv
=PgBJ
-----END PGP SIGNATURE-----
list Iain M Conochie · Sun, 01 Mar 2009 10:35:37 +0000 ·
quoted from Adam Goryachev
<snip>
PPS, I did do some work for a client a number of years ago (before
hobbit, with BB) where we customised (read wrote a new) web interface.
The bb client was stock standard and re-distributed, but the work on the
server was never distributed, hence source code didn't need to be
shared. This was basically to let each client login and see their own
status, and nobody else's, and let the company
configure/setup/delete/etc the clients monitoring/passwords/etc...
Unfortunately, the company went bust, and I lost all copies of the work
I had done...
  
I think this specific issue was one of the "loopholes" that GPL v3 hopes to close. Of course since BB was not GPL it will not apply. But as i understand it if you use GPL software to provide a service over the web and you have changed the source then you have to distribute (make available) the changes. As I see it there is no provision in GPL v2 for this.

And of course I am not a lawyer :)

Cheers

Iain
quoted from Adam Goryachev
PPPS, and I am not a lawyer :)

Regards,
Adam

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkmooB8ACgkQGyoxogrTyiUo9gCgp8hehXQP9nY3X/YACBzWK4w3
TUAAmwQKYkkM6rv9tEUf7XmW3fLfKQBv
=PgBJ
-----END PGP SIGNATURE-----

list Malcolm Hunter · Tue, 17 Mar 2009 11:17:16 +0100 ·
Hi Henrik,

I'm in the process of proofreading the documentation and wondering if I'm wasting my effort as it's currently still on version 4.2.3. Is the documentation due to be updated in the near future? Also, what's the best way to feed back any corrections?

Regards,
Malcolm

-- 
Technical copy-editor & proofreader

KDE Proofreading Team
KDE British English Translation Team

http://l10n.kde.org/team-infos.php?teamcode=en_GB

Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01
list Henrik Størner · Thu, 19 Mar 2009 13:29:35 +0100 ·
Hi Malcolm,
quoted from Malcolm Hunter

On Tue, Mar 17, 2009 at 11:17:16AM +0100, Malcolm Hunter wrote:
I'm in the process of proofreading the documentation and wondering if I'm wasting my effort as it's currently still on version 4.2.3. Is the documentation due to be updated in the near future? Also, what's the best way to feed back any corrections?
I really appreciate someone doing proof-reading of my docs!

I haven't updated the docs for quite some time, but the best
thing you could do would be to grab the documents from the
Sourceforge Subversion repository - those are the current
version, and the ones I would be updating.

I can setup commit-access to the repository if that is the
easiest way for you to submit changes. If you would rather
prefer, you can also just mail me the updated files and I'll
commit the changes.


Regards,
Henrik

PS: Does this have anything to do with KDE, or is it just
a personal interest in Xymon ?