[development] Drupal's CVS policies... including 'foriegn' code in TinyMCE module?
gerhard at killesreiter.de
Mon May 21 21:01:33 UTC 2007
-----BEGIN PGP SIGNED MESSAGE-----
Ashraf Amayreh schrieb:
> This is not totally correct, if foo, bar and baz need to include external
> code then so be it. Imagine tinyMCE needed to change pages of configuration
> files, why should users have to go through all that trouble?
If there are single config files that you'd want to distribute
preconfigured, then this is not really a problem.
> And how many
> modules do we really have that require huge external libraries?
Quite a few.
> should we assume that module developers are irresponsible enough to fill
> repository with garbage?
Because they do all the time. Not everybody, of course, but yes it happens.
For example, there's an issue that shows that there are 43 themes in our
CVS where it is questionable that they are actually under GPL.
To investigate all of them and find solutions will take a lot of work.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
-----END PGP SIGNATURE-----
More information about the development