Rokbox module: External libraries committed into CVS

Well then, I guess we need to add the exact same issue for your own modules as well right.

Quit acting all childish and threatened.

It's a 2 way street. I see LOTS of useful modules that would be severely crippled if we followed "Guidelines" to T. The one you are thinking of was for large CODE projects with code that could get updated all the time, not simple images and an example js file like we have here. There are zero PHP files in here.

Look at your own projects instead of someone elses and keep your nose where it belongs:

Lets have a look at one of your own modules eh:
"Javascript Tools" of which you consider yourself a co-maintainer yet you fail to mention the 3rd party file in here. I could probably dig and find more, but the point is, you are just threatened by my module so you decided to post unnecessary issues in order to get it removed as you said in IRC.

The original 3rd party file can be found here:
http://plugins.jquery.com/files/jquery.cookie.js.txt

And it can also be found here in a drupal module?! What the heck?!
#
Commit #108043 by nedjo at 16:58
Javascript Tools: /modules/jstools/jquery.cookie.js 1.3

Update jquery cookie plugin.

http://drupal.org/project/cvs/57285?nid=57285&page=1&nid=57285

Now go bug someone else. This issue is resolved, it has no 3rd party downloadble code in it of any significance. If it had 200 PHP files, then thats one thing. But some images, css, and a JS file? Get a life troll.

What's with the attitude here?

By applying for a CVS account and hosting your project on drupal.org, you agree to respect the CVS usage policy, that clearly states:

DO NOT include code from a non-Drupal project in the repository. If your module requires non-Drupal code, provide a link to where the other code can be downloaded and instructions on how to install it.

I unpublished http://drupal.org/project/rokbox, to give you some time to fix this.

The attitude stems from him bitching at my wife in IRC for almost an hour and threatening her. Needless to say I dont like this guy at all, especially when his own projects do the exact same thing as I already pointed out. He was all like "I'm going to make your life hell blah blah blah". Whatever punk. Its a 2 way street, what comes around goes around.

The whole reason this issue came up at ALL is because he is the author of jLightbox, and this demo module is similar to it but has many more features and he didnt like it being around. I'm sitting here watching IRC and I can see people saying things like "He has a point about the jquery.cookie.js file. But do I go make issues about it and try to get the module yanked? No. Why? because some people might think its a useful module and by doing that, it would make the module combersome to install for non-technical people. Same thing here.

BTW, you can just keep it unpublished. I'm not going to cripple my apps just because someone thinks it needs to be harder to install. I'll just host it on my own site. Not my fault it makes his little lightbox look like a toy.

I'll just host it on my own site. I dont 'need' to host it here, it's just more convenient for users.

@crystaldawn, you're not doing yourself any favours with this completely unwarranted attack on one of Drupal's most committed contributors. There was no bitching, there were no threats, there was just a reasonable request from someone who has, as most people in the community are surely aware unless they've been living under a rock for the past 6 months, put a serious amount of thought and effort into the right way to do things, e.g. 3rd party plugin management.

I get it already. Hypocrisy runs rampant in the 'elite' drupal community. Outsiders cant do XXXX but someone who has nothing better to do than sit in IRC and make a name for themselves all day long can do XXXX while everyone ignores the real issue. You never saw the private msgs she got. Keep your nose where it belongs. You still ignore the fact that his very own projects have 3rd party files in them, as do many other drupal modules. If we went through and unpublished them all, drupal's module repo would have nothing worth installing in it. I will be removing ALL of my projects from drupal.org. I have no interest in being in a dictatorship. I'll host my own modules. And anyone else who wants to do the same can host with me free if they like, and I could careless what they put in their modules so long as it's GPL'd. This is how forks are created. Simple issues like this could cause a lot of people to become disgruntled and fork Drupal. I've seen this type of thing happen so much over the years with other development projects, linux distros, etc, it's like a broken record, it always repeats (something always forks). Just wait until the drupal 'elites' try to force people to PHP 5.2 by leveraging Drupal 7 as the requirement. I guarantee the first thing that will happen is a PHP 4/5.x fork of Drupal 7 gets released, and I'd be the first person to help with that project too.

I will be removing ALL of my projects from drupal.org

Thank you very much

PHP 4? Can you even get that anywhere anymore? By the time D7 comes out 2010 or so, PHP 4 will not even be remembered by anyone.

The files are still present in HEAD, DRUPAL-6--1-0, and DRUPAL-5--1-0.
Should the files be removed from there too, or can this report be considered completed?