Dear Compilation Authors
Please read any included text files and/or license files included with add-ons that you include in your compilations before you include them. Some have restrictions on inclusion/redistribution.
Edit: This is not an attempt to be an ass, but there's a LOT of compilations that are including add-ons, etc, that aren't supposed to be. |
This is only a suggestion, but I hope you consider it.
Make an actual statement on your download page that you do not want your plugins to be redistributed without your permission. Generally if I see a text document named "readme" inside of a zip folder, I am going to assume it is instructions or something along those lines. If you don't want to include a statement on your download pages (for some odd reason) then at least name your text file something that is a bit less obscure. I dunno, "Redistribution Policy" or something... On a side note, I am failing to see the issue with having Ui designers use your plugins in their uploads, especially if they list their addon credits or post a picture like they are required to do anyway. I would imagine you would want as much exposure to your work as possible. Anyway, your skins are very nice, keep up the great design work. <3 Ish |
Quote:
Quote:
Quote:
Quote:
|
I respect your views, but can I ask why? I'd like to know your reasoning behind this. ;)
|
Quote:
|
There is 2 sides to a "compilation" there are those that just post a bunch of addons they like (which I have not seen very lately) and then there is ones that have there own art, designs, etc. These are the "true" compilations and what they are meant for.
This is going to take a lot of work. :p Explicitly tell your users to get permission from you first. (Or do you not want it in ANY compilations whatsoever?) P.S.: I'd like to ask permission now while I update all the "Deuce" compilations. :D (Actually, I currently can't use ButtonFacade because the art is still using cycircled and I don't know how to port it over. Do you think you could help?) |
Quote:
Quote:
Quote:
For the record: For my files, this only applies to originals. IE Apathy, Entropy, Onyx, Caith, etc. The others (Serenity, Gears, LiteStep, etc) are simply ports to BF and don't require permission, though they may have the ReadMe file in there. I had to revamp my SVN directory and did a bunch of copy/pasting (FTL). |
Oh, okay. That is nice to know for the future :D
So it there a good tutorial on how to port over? I've read the wiki (I believe), but I am not experienced enough in art to know what to do in the changes of the art part. Do you have any advice? :P Thanks ;) |
Quote:
Quote:
I hardly think you could argue that. So, if you would demand of every single person who used a skin of yours to ask permission before uploading their ui for others to be inspired by, then may I ask, what difference does it make? Are you ever going to tell someone no? I hardly doubt it. And if that were the case, what is the difference between you telling everyone yes and them just giving you credit for the work in their upload? I really don't see your logic in this. Quote:
Quote:
Best of luck to you in resolving this matter how ever you see fit. -Ish |
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Additionally, not every compilation author credits the author of every single add-on that's included in their compilation. As far as the average user knows, the compilation author is the author of the entire package. Going back to who reads what, do you really think the users read all of the credits even if they're complete? And then there's stats. How am I supposed to track the stats of my add-ons when some of the traffic is pulled away by those who prefer compilations? Quote:
But seriously, I'm sorry if my attitude bothers you. Perhaps in the future I'll think twice about offering my work to others to use for free. |
Quote:
Quote:
Quote:
Quote:
Quote:
By no means am I saying remove your work, however I doubt you would because you like seeing the download number go up, I am saying however that you should let loose a bit on the redistribution thing. This is Ui design for fun...for a game, its not like anyone is doing any of this to make money. Anyway, as I said before, you do good work, keep it up. -Ish |
Quote:
Quote:
Quote:
Quote:
Quote:
|
I had written up a whole rationalisation with examples and stuff, but bottom line is if you create work, and it belongs to you, it's yours to demand how it be distributed. It's not enough to say "so and so created it." If that person has included a file that says "You need my permission to redistribute it" then you'd damn well better get their permission to redistribute it. Ignorance of the law is no excuse for breaking it. Why would you think someone should shove it in your face when they've made all the tools available to you?
Not following the author's published wishes in that regard is theft. And if it's too much trouble to take a look at a readme before redistributing it under your name, then shame on you. |
Regarding the ReadMe file. I actually do open those, however 99.9% that file is either instructions on how to install or other technical info such as "If you see this error than this happened..." and so on. Its been this way for as far back as I have been using PCs and freeware/shareware software (which has been a very long time indeed). Yes, I am a grizzled old geek who cut his teeth on DOS and BASIC (on old IBM-ATs and Apple IIes).
As a consequence, when ever I put together a package of mods for others (lately only a few for my guild for those who don't know were to find the mod in question), I use descriptive names for the "ReadMe" file such as "Instructions for Installation" or "How to install". The name README is a hold over from the old DOS/FAT-16 days when you were limited to 8 characters or less in your file names. I am more likely to pay attention to a license ReadMe if it was named as such as, since ReadMe is overused so much, it tends to get missed. Use terms like "License" or similar. That way there is no ambiguity AND if you find someone infringing on your work, you can easily point to it as opposed to saying its in the third paragraph of the ReadMe that 90% (yes its roughly that, years of tech support backs this up, that number may be higher :rolleyes:)of users never read in the first place. I do read all of the text files in my AddOns, but then again, I am not an "average" user since I tend to hack on those AddOns (either to fix errors I find, or to tweak to taste). |
Quote:
:D |
Quote:
Quote:
Quote:
|
Quote:
Anyway, this will be my last post. Not to be misunderstood. I totally agree that an author has full rights to his creations and reserves the right to require people to ask permission before redistributing his work. However, if that request is of such great importance, just make it more easily known that it is something you would prefer people do. If only to save yourself and other people the headaches. Have a good day all. |
Quote:
|
Quote:
|
Quote:
|
All times are GMT -6. The time now is 03:42 AM. |
vBulletin © 2024, Jelsoft Enterprises Ltd
© 2004 - 2022 MMOUI