[development] Drupal's CVS policies... including 'foriegn' code in TinyMCE module?
jeff at viapositiva.net
Mon May 21 18:34:28 UTC 2007
There's no reason to even offer a CVS repository but convenience. :-)
If the code is GPL, and there is permission granted by the project's
maintainers, and the contrib module maintainers are the ones
maintaining it, isn't it acceptable for the sake of user experience?
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?
On May 21, 2007, at 1:27 PM, Gerhard Killesreiter wrote:
> 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?
More information about the development