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

Andre Molnar mcsparkerton at yahoo.co.uk
Mon May 21 18:38:58 UTC 2007

Kevin Reynen wrote:

I think the issue has little to do with hatred of WYSIWYG.
As I understand it, the problem is that it would set a bad precedent for
CVS usage.

Lets take the case of module foo that is simple small lightweight
interface between Drupal and some massive external library.  With the
current rules module foo is only 10K in CVS.  If module foo included the
external library as well - foo suddenly grows to 300K.

But foo is really important to people - and people really like foo and
people complain about foo's install process (having to separately
download the external library).  So an exception is made for foo...

Then along comes module bar - just as important and just as popular and
another exception is made.... then along comes module baz.

Baz may or may not be important or well loved - but the maintainer says
"Why you picking on module baz when foo and bar get to include their
external libraries?"

On the project page you can always include a link to a fully packaged
TinyMCE module hosted elsewhere.  The only thing is that you would have
to maintain your own packaging.

(a person who would love to have tinymce pre-packaged but understands
completely why it shouldn't be that way)

More information about the development mailing list