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

Gerhard Killesreiter gerhard at killesreiter.de
Mon May 21 22:03:48 UTC 2007

Hash: SHA1

Michael Favia schrieb:
> Jeff Eaton wrote:
>> The GPL requirement makes perfect sense. But it's not like anyone is
>> asking the CVS repository admins to make sure that the TinyMCE
>> libraries are up to date, neh?
> In fact quite the opposite. Many times you have to specify exactly which
> version of the third party library to download because you haven't had
> time to rewrite the module to enable compat with the newest release,
> etc. This does lead to a lot of confusion. While I agree that
> maintaining shadow copies of third party CVS libraries isnt "fun" it is
> useful and can be an efficient way to deal with helping our users
> maximize the usability of drupal. And i think that most module
> maintainers would rather deal with periodically updating their 3rd party
> code than weed out all of the bogus bug reports and hand hold users who
> are attempting to install and configure their modules one at a time.

If that proves neccessary you should write some docs. Although e.g.
listhandler module isn't one of the really easy modules, I don't notice
many issues with it. The docs are short but to the point and seem to help.

> In
> any event shouldnt we leave it up to the maintainer at least to
> determine which is most efficient to their circumstance?

They are already free to determine what is best for them and their
module. They are not free to commit to CVS what they want. They are free
to host a "my module with everything you ever needed to run it"
somewhere else.


Version: GnuPG v1.4.6 (GNU/Linux)


More information about the development mailing list