[development] Drupal's CVS policies... including 'foriegn' code in TinyMCE module?

[Gerhard Killesreiter]

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

Kevin Reynen schrieb:

> Now Borris is saying the issue isn't GPL vs. LGPL, but policies
> specific to Drupal's CVS and because some of the key Drupal
> maintainers are "WYSIWYG haters", I'm not going to get any support I'd
> need for waving the "no foreign code in CVS" policy.

This has nothing to do with WYSIWYG editors (which I freely admit to loath).

The issue that there's usually no reason to have third party code in our
CVS but convenience. Other people's convenience may however
inconvenience the Drupal CVS maintainers. And since the people who run
this thing are usually very busy, we've chosen to rather inconvenience
the users and authors of WYSIWYG modules (or any modules depending on
third party code for that matter).

If I create a module that parses uploaded files, do I get to include
binaries and sources for pstoedit, wvHTML and the like?

Cheers,
	Gerhard

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGUeSefg6TFvELooQRAmD7AJ0VR4X9eDedc6XnuEKZyaF4GyGmHwCfSoc0
59HSOx23IFmvFvjza7X74Ok=
=1ydi
-----END PGP SIGNATURE-----