The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#1
|
||||
|
||||
![]()
Is it not possible to make some rules for the coders?
No disresprect to the coders in general, but it irritates me big time when I install a mod and ask for support, the mod is deleted without notice. I am very gratefull for the things coders make, but why not make a rule that when a mod is posted, it must kept here. I understand if a coder does not want to give support anymore or whatever, but what is the use to delete it and the replys from others? I do not think this is nice to the people who use the mods and take time to help others. Also, a topic is always handy to look back if you have a question, most of the time the answer has been given already by an other member. I asked this before, but now it happend again with another portalmod which I could not get it to work and now I am left alone with it. I do not think it must be allowed to remove them, they must think that before they post it. Ok, I can understand for sertain reasons a mod must be taken out of roulation, but just take the download away, not the topic with its helpfull stuff. Come on people, there are members who are using your good work. Don't dump them like that. |
#2
|
||||
|
||||
![]()
Another main reason is releasing it without permission as in add-on or refixed to someone elses release
|
#3
|
||||
|
||||
![]()
It makes no sense to remove a mod. I can assure you I will never remove mine. You can mark them as unsupported and basically abandon them (as I did with vbPluginOrder). There is simply no reason I can think of to remove a mod (other than the moderators and admins doing it because it breaks rules).
|
#4
|
||||
|
||||
![]()
A vulnerability in an unsupported modification? Wanting to move support to another location? It's their property and work, they can do as they please with it whether or not you agree. But I'd rather have some kind of notice left at a minimum that something has been removed.
|
#5
|
||||
|
||||
![]()
While I agree that deleting a mod isn't necessarily in the best interest of the community, it is afterall the intellectual property of the author -- whom can do as he/she pleases. Unfortunately, it's a grey area for the vBorg staff -- because if they start placing restrictions on what authors can and cannot do, they're risking pushing away the force that keeps the site up in the first place.
It's a catch 22. I can't speak for anyone else, but I personally would never delete a modification -- however, if vBorg started telling me what I can and cannot do with my released work, I would think twice about releasing my work to the community. On a related note -- I could see deleting the modification. But why the replies? /shrug |
#6
|
||||
|
||||
![]()
I'm not really sure what mod you are referring to, but I do know that Atakan KOC asked for all his mods to be removed today. If an author asks for their mods to be removed then we will do so - they "own" the work and it is their choice.
|
#7
|
|||
|
|||
![]()
Actually Paul, that is a misunderstanding. He requested some of his work to be removed, and by a mistake/misunderstanding all where removed. I spend 2 hours yesterday on a mobile connection moving them all back again.
|
#8
|
||||
|
||||
![]()
Oh yes, I see a few have returned.
|
#9
|
||||
|
||||
![]()
A coder should be able to remove his files (although that would make him a jerk), but the mod threads should never be deleted.
|
#10
|
||||
|
||||
![]()
sure. but at least an info should be left. something like: mod removed by coder ...
|
![]() |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
![]() |
|
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|