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

Johan Forngren johan at forngren.com
Mon May 21 19:56:53 UTC 2007

Is it possible to do some packaging/tagging magic? Have one ready-to-go and
one almost-ready-to-go release?

On 5/21/07, Michael Favia <michael at favias.org> wrote:
> 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. In
> any event shouldnt we leave it up to the maintainer at least to
> determine which is most efficient to their circumstance?
> --
> Michael Favia                   michael at favias.org
> tel. 512.585.5650        http://michael.favias.org

  Johan Forngren :: http://johan.forngren.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/development/attachments/20070521/0dd70680/attachment.htm 

More information about the development mailing list