Violation of script licence

in
Subscribe to Violation of script licence 19 posts, 4 voices



GreyWyvern Scriptwright
OperaWindows

Hi Swarnava. I'm glad you like my Virtual Keyboard script, but by not including the full text of my copyright notice and disclaimer, you are in violation of my script's BSD licence. You either need to include the copyright notice/disclaimer *in full* within your source code, or remove my code from your script.

You can find the text of my copyright notice here: http://www.greywyvern.com/code/bsd.txt

Thanks,
Brian

 
Marti Scriptwright
FirefoxX11

@Swarnava/Heaven GOD,

First off, I'm not an attorney. (Standard disclaimer that I have to do)

You are treading dangerously close to having this script deleted/unlisted due to GreyWyverns notice of license violation. If you do not include this users comment block of the script posted here on USO in a timely manner, it will constitute a license violation and I will be forced to rate this as harmful. Please add the comment block from GreyWyverns script as soon as possible.

This is a sample of what you will add for the Virtual Keyboard code in your script:

/* ********************************************************************
 * HTML Virtual Keyboard Interface User Javascript - v1.29
 *   Copyright (c) 2009 - GreyWyvern
 *
 *  - Licenced for free distribution under the BSDL
 *          http://www.opensource.org/licenses/bsd-license.php
 *
 */

 
ms99 Scriptwright
FirefoxWindows

@Marti,

And because you have again read only what was of interest to you, not being rigorously (as usual)...

This is the content swarnava/hell's shit is required to publish in his script and on the presentation page "About" tab of this mixture of copy-pasted items script:

++++++++++++++++++++++++++++++++++
Copyright (c) 2009, GreyWyvern
All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

* Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
* Neither the name of the GreyWyvern nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ++++++++++++++++++++++++++++++++++

What do you say now about ? You have no clue, do you ? Useless post on this thread and wrong instructions !

Information gathered in a rush from my lawyers !!!

Vote for a removal of the script !
 
GreyWyvern Scriptwright
OperaWindows

ms99 is correct, although he is a little harsh in the way he says so. The text of the BSD licence itself needs to be included in any redistributions or modifications. I link to the latest version at opensource.org in my scripts, but keep a static copy at my website: http://www.greywyvern.com/code/bsd.txt

I link to the above static version from the script's homepage: http://www.greywyvern.com/code/javascript/keyboard

Regards.

 
Marti Scriptwright
FirefoxX11

@ms99
You are ignored due to your continued brash behaviour. Please go troll for attention and be confused elsewhere.

@GreyWyvern
The entire text does NOT need to be included based off the last quick look at your source. As we are on USO, and your script resides on USO, that is the determining source... not your personal repository. This is done for complete transparency. Having it offsite, at your personal repository, is a bad idea as you can make whatever changes you want to it and not be accountable.

Swarnava/Heaven GOD has pm'd me asking on how to do it... so give it some time please... I'm rereferencing this topic and recommending an @attribution key or @require.

@Swarnava/Heaven GOD

Reference attribution in your metadatablock with the following:

// @attribution http://userscripts.org/users/31492 (http://userscripts.org/scripts/show/10974)

Do this for any authors code that you have included, but make sure they haven't denied redistribution (In which case I'll recommend it's immediate unlisting from uso)... this is the only case where it won't work. This will allow GreyWyvern to "bloat" his own script and falls within legal counsel guidelines I have received.

To eliminate this problem in the future you also might consider just:

// @require http://userscripts.org/scripts/source/10974.user.js
...and remove GreyWyverns code altogether from your project. This will still include it as part of your script but just via @require.

 
Swarnava/Hea... Script's Author
FirefoxWindows

Updated

 
Marti Scriptwright
FirefoxX11

Swarnava/Hea... wrote:
Updated
Thanks! Don't forget to do this for any other scripts you've included... especially the @attribution. If no copyright notice exists in their code, just reference the appropriate attribution again minus the @ symbol :)

Reference commits:

 
GreyWyvern Scriptwright
OperaWindows

The entire text does NOT need to be included based off the last quick look at your source. As we are on USO, and your script resides on USO, that is the determining source... not your personal repository. This is done for complete transparency. Having it offsite, at your personal repository, is a bad idea as you can make whatever changes you want to it and not be accountable.
I am not satisfied with this. I link to the latest version of the BSD licence at opensource.org, which is the version that should be used at the time the script is copied; the txt copy I keep at my site is just a static reference. The licence which prevails is the one that should have been reproduced from opensource.org when the script was copied, and further changes to my own txt copy would not affect said licence.

If you are using Opera, navigate to opera:about to see examples of similar licences they display because they are redistributing some open source libraries. They don't simply require just a copyright link and name; the whole licence must be reproduced.

Anyone can download and use my script without any worry about the licence, but as soon as someone begins distributing my script, these licencing restrictions come into play and need to be respected. I hope you can understand that.

To eliminate this problem in the future you also might consider just:
// @require http://userscripts.org/scripts/source/10974.user.js
...and remove GreyWyverns code altogether from your project. This will still include it as part of your script but just via @require.
I would greatly prefer this, since I am constantly updating the script with new keyboards and such. This way Swarnava's script would always be using the latest version of my script. This would also avoid the licencing issue, since Swarnava's script would no longer be distributing my own.

 
Marti Scriptwright
FirefoxX11

GreyWyvern wrote:
I am not satisfied with this. I link to the latest version of the BSD licence at opensource.org, which is the version that should be used at the time the script is copied;
He's currently linking to it at opensource.org as well. BSD does not prevail over all license types not to mention BSD is "out the door" so to speak. Plenty of other licenses are compatible with BSD.

GreyWyvern wrote:
Anyone can download and use my script without any worry about the license, but as soon as someone begins distributing my script, these licensing restrictions come into play and need to be respected. I hope you can understand that.
I do understand this quite clearly and you should understand that you implemented your license incorrectly in the first place. You gave redistribution rights clearly on USO... any off site is irrelevant because you didn't implement a full 3rd party project management system.

I do agree that @require is a much better solution, but I can also understand the reluctance of trusting another authors code if they tack on something down the line that kills it or causing a security violation. I also notice that your script is tailored to Opera... I'm always open to cross-browser scripting, but it's not defined in USO's charter. And as most of us know Opera doesn't have the capability of using @require so some other comprise needs to happen.

I do appreciate the clear and concise posts from you rather than hearing the vulgar and obnoxious comments from some others. This is how open-source is supposed to work in the community instead of head-bashing, degenerate behaviour.

 
GreyWyvern Scriptwright
OperaWindows

I do agree that @require is a much better solution, but I can also understand the reluctance of trusting another authors code if they tack on something down the line that kills it or causing a security violation. I also notice that your script is tailored to Opera... I'm always open to cross-browser scripting, but it's not defined in USO's charter. And as most of us know Opera doesn't have the capability of using @require so some other comprise needs to happen.
This argument is not logical. It is my script which works in both Opera and Firefox. Swarnava's script is the one targeted to Firefox and as his script is including mine (and not the other way around) only his script needs to include the @require statement.

If Swarnava modified his script to work in Opera, then the capability of using @require would become an issue and it would make more sense for him to include my script directly.

In any case, I suspect I am not going to get any more concessions out of Swarnava, so I suppose I am happy with the inclusion of the copyright notice as it stands now.

 
Swarnava/Hea... Script's Author
FirefoxWindows

@require features doesnot working..temme how it use thorugh require features?

 
Marti Scriptwright
FirefoxX11

Swarnava/Hea... wrote:
@require features doesnot working..temme how it use thorugh require features?
It should be working... but remember @require is only for Firefox with Greasemonkey. So @require will not work in Opera. I know you use Opera sometimes. This is why I'm telling you this.

Just like I said above try using:

// @require http://userscripts.org/scripts/source/10974.user.js
It won't show up in your script but it will be included and run by Greasemonkey. Check your gm_scripts folder for it. :)

 
Swarnava/Hea... Script's Author
Opera

I checked not working on firefox 3.5.3

 
Marti Scriptwright
FirefoxX11

Swarnava/Hea... wrote:
I checked not working on firefox 3.5.3
This would not be the first time I've heard this... Keep your code here on userscripts.org as is for now.

If you would like to check to see if the Firefox profile is corrupted... create a new profile. Instructions on how to do this are here. Then reinstall Greasemonkey into that new profile. Then try the @require with ONLY greasemonkey installed. If it still doesn't work then we're all out of luck at the moment. It is a good idea to back up your existing scripts that you have already installed with Greasemonkey.

 
Swarnava/Hea... Script's Author
FirefoxWindows

I dont Understand..Tell Me What I Want To Add?

 
Marti Scriptwright
FirefoxX11

Swarnava/Hea... wrote:
Tell Me What I Want To Add?
Do not worry about it. I was trying to see why your @require wasn't working. It is not a big deal. We can continue this at a later date when the new Greasemonkey is officially released. :)

 
Swarnava/Hea... Script's Author
FirefoxWindows

okies thanx

 
Swarnava/Hea... Script's Author
FirefoxWindows

Tinyurl Decoder Successfully work on require method but do not work keyboard

 
Marti Scriptwright
FirefoxX11

Swarnava/Hea... wrote:
Tinyurl Decoder Successfully work on require method but do not work keyboard
I will check the keyboard out this weekend. Thank you very much for trying! :)


Update... well it appears the keyboard by itself is not compatible with this system as it never showed up... perhaps I'm missing how to activate it. So I really can not help figure this out. :\ At least you have attribution in your source and we'll leave it at that.


Update... the keyboard software is so poorly designed but I did manage do get it activated. Will resume testing next week.

Cross
Presentational HTML allowed.
Use <code> for inline code and <pre> for code blocks. Use &lt; and &gt; for literal < and >.
We help break paragraphs and link your links.
or cancel