[Vacm-develop] Relicensing of VACM components

[Tony K. <to...@op...>]

Hi!

I would like to ask for your comments in LGPL'ing the following
pieces of VACM:

  - libloose, the library used to interface loosely coupled VACM
              modules to nexxus,
  - libvacmclient, the library required by VACM clients to communicate
              with nexxus.

Also, the following ought to be re-licensed to allow complete
freedom in the use of the following code which would otherwise
not serve its intended purpose:

  - skel, the sample code recommended for use with libloose in building
              loosely coupled VACM modules.

The re-licensing of these components will help VACM:

  - be useful in the deployment of control solutions where the
    components or devices that need to be controlled include the use
    of 

  - be useful in the development of VACM clients, where these clients
    may require the use of proprietary software, or allow people to
    customize existing proprietary clients to allow them to become
    VACM clients.

I would like to see VACM incorporate the use of the LGPL and/or
some other open-source license that does not enforce you to apply
that license to other code.  This is the very reason why I am seeing
VACM become difficult to deploy on projects outside the open source
development community.

I understand the GPL's role in providing free software to the computing
community at large, but I find that VACM's licensing as it currently
stands does not allow it to enter the environments which would other-
wise make it useful for its intended purpose in hardware control and
management.

I would like to see these licensing changes applied to VACM, and
I hope that other developers see my point of view in extending the
usefulness of VACM to areas that the GPL otherwise does not allow.

Thanks.

-- 
------------------------------------------------------------------------
    Tony Kavadias <to...@ma...>