[development] "Package" misuse

Kevin Reynen kreynen at gmail.com
Thu May 13 22:53:47 UTC 2010


I'm sure you remember this thread...


"But I think when people talk about *not* allowing
at-one-time-external GPLed code into the Drupal repository, they're
simply on crack."  -Jeff (Robbins)

The CVS policy (http://drupal.org/node/422996) never changed and is
very clear about exceptions...

"3. Exceptions can be made if the 3rd party library:

   a. had to be modified to work with Drupal and the modifications
were not accepted by the original author.
   b. is generally difficult to find in the needed version.
   c. is no longer maintained by the original author."

Obviously a specific version jquery.js doesn't meet any of these
criteria, yet 3 years later here it is in CVS...


Do you really think someone will enforce the policy on a module used
by 40,000 sites on a developer with as high profile as Jeff?

It's not much of a "policy" if some developers just ignore it.  Why
would you expect any other developers to follow it?  The policy
actually states...

"Maintainers who violate this policy or refuse to correct violations
brought to their attention may have their project unpublished or CVS
access revoked."

Sure they will.  I'll believe the community can enforce policies like
this on developers when I see it.

- Kevin

On Thu, May 13, 2010 at 3:30 PM, Earnie Boyd
<earnie at users.sourceforge.net> wrote:
> Kevin Reynen wrote:
>> I see this issue as being trivial compared to keeping third party code
>> like JQuery plugins out of modules and CVS.  That is a policy that's
>> blatantly ignored.  I have been trying/failing to get module
>> developers to adhere to like this issue in the views_rotator module...
>> http://drupal.org/node/701926
>> http://drupalcode.org/viewvc/drupal/contributions/modules/views_rotator/views-rotator.js?revision=1.6&view=markup
>> There are 4,000+ sites using that module with an old version of jQuery
>> Cycle Plugin that makes it difficult for other modules to leverage
>> features of the jQuery Cycle Plugin without going in and hacking the
>> .js file in that module.
> Yes, that is a bad one too and in my opinion, this one should be brought the
> attention of the webmasters [1] so that it can be handled.
>> I know there are improvements in the javascript handling in D7 that
>> allow one module to override another module's javascript, but that
>> doesn't change the fact that developers will ignore any "policy" if
>> there is no enforcement.
> Again, we, the users are the enforcers.  So if we find something out of line
> then we need to bring it to the attention of the administrators.
> [1] http://drupal.org/project/issues/webmasters
> --
> Earnie
> -- http://progw.com
> -- http://www.for-my-kids.com

More information about the development mailing list