Plugin Arch. for KDevelope 2.0

[Sandy Meier]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


> Could you bring some light into that if this applies to us:
>
> http://www.gnu.org/copyleft/gpl-faq.html:
>
> If a program released under the GPL uses plug-ins, what are the
> requirements for the licenses of a plug-in.
>  It depends on how the program invokes its plug-ins. If the program uses
> fork and exec to invoke plug-ins, then the plug-ins are separate programs,
> so the license for the main program makes no requirements for them.
> If the program dynamically links plug-ins, and they make function calls to
> each other and share data structures, we believe they form a single
> program, so plug-ins must be treated as extensions to the main program.
> This means they must be released under the GPL or a GPL-compatible free
> software license.
Ok, this is the paragraph for us. This means only GPL or compatible plugins 
are allowed for a GPL'ed version of KDevelop. If we don't want this we must 
change the license of KDevelop to an other license, but I think we won't get 
a majority for this. Personaly I will stick with GPL. And if Siemens or some 
others want to develop an inhouse plugin they are not forced to publish the 
sourcecode, only if they distribute the plugin to others. 


Ciao!
Sandy

- -- 
for verifying my signature or send encryted emails:
ftp://fara.cs.uni-potsdam.de/stud/smeier/public_key
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1e-SuSE (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7ZUmGNX6yrHxt6UARAuWoAJ9OCLaNCkyAMCbiSH1H7Bt+yKbOPgCgpLKi
YWlCLHrW3Zz3rWqz/8tittI=
=eNhE
-----END PGP SIGNATURE-----

-
to unsubscribe from this list send an email to kdevelop-devel-request at kdevelop.org with the following body:
unsubscribe »your-email-address«