vb.org Archive

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   vBulletin.org Site Feedback (https://vborg.vbsupport.ru/forumdisplay.php?f=7)
-   -   modification graveyard problem! gettin real annoyed now (https://vborg.vbsupport.ru/showthread.php?t=206309)

GoTTi 02-27-2009 01:41 PM

Quote:

Originally Posted by TNCclubman (Post 1755706)
Its a good idea, why doesnt everyone just take a deep breath and realize its for the greater good.

When they first imposed a seatbelt law everyone screamed and hollared...

click-it-or-ticket

King Kovifor 02-27-2009 03:08 PM

Quote:

Originally Posted by GoTTi (Post 1755704)
anyways, im over the topic. not taking any suggestions from anyone regarding it, go ahead and close the topic or move it to the graveyard. dead issue already

If you really want this taken serious by other developers, why not set the example with your products. Quick glance I've found at least one that goes completely against what you want.

hambil 02-27-2009 09:21 PM

Quote:

Originally Posted by Chadi (Post 1752402)
I agree with Gotti. I've had this issue a few times. It doesn't kill for the author to leave a note why it was moved to the GY and how to uninstall it, while keeping the original downloads there. There is no harm in doing this.

Unless things have changed since I dropped off the planet, we are not allowed to say why we left or removed our mods. Uninstall instructions by the author are a good idea though, I agree.

KW802 02-27-2009 09:31 PM

Quote:

Originally Posted by hambil (Post 1756434)
Unless things have changed since I dropped off the planet, we are not allowed to say why we left or removed our mods.

I did not realize that was a vB.org policy. Is it written anywhere or is it something that you got hit with in the past?

Lynne 02-27-2009 09:37 PM

I've seen authors leave reasons.... or I'm pretty sure I have seen reasons. But, why do they need to post a reason? I've seen authors simply write "I am closing this project" or similar in the thread. The reason why doesn't matter at all - anyone can leave uninstall instructions which is why I suggested that a user who wants to make sure there are uninstall instructions available just post them themselves in the thread.

Paul M 02-27-2009 09:37 PM

Quote:

Originally Posted by KW802 (Post 1756442)
I did not realize that was a vB.org policy. Is it written anywhere or is it something that you got hit with in the past?

There is no such policy that I'm aware of. However, the GY is read only, so you could not post to it after a mod is moved.

GoTTi 02-28-2009 12:24 AM

Quote:

Originally Posted by King Kovifor (Post 1756178)
If you really want this taken serious by other developers, why not set the example with your products. Quick glance I've found at least one that goes completely against what you want.


i dont write modifications to release, and if i did write any that were plugins, i would leave uninstall info if it were moved to the graveyard. why not?

nexialys 02-28-2009 12:36 AM

that's so hilarious to read you GoTTi... you preach for something you're not even able to provide, this become more and more pathetic...

King Kovifor 02-28-2009 01:25 AM

Quote:

Originally Posted by GoTTi (Post 1756539)
i dont write modifications to release, and if i did write any that were plugins, i would leave uninstall info if it were moved to the graveyard. why not?

Modifications, templates, anything. They all still need install instructions, yet I have missed the uninstall. Unless I'm mistaken. A wise woman I know always says, "Seeing is believing."

hambil 02-28-2009 02:42 AM

Quote:

Originally Posted by Paul M (Post 1756447)
There is no such policy that I'm aware of. However, the GY is read only, so you could not post to it after a mod is moved.

At the time of my departure, it was over some disagreements in how security holes in hacks where handled. I was angry, but for the most part rational and posted a number of suggestions for why I was so upset. The suggestions where not taken seriously at the time, and I was 'warned' that I was not to continue. Ironically, most of those suggestions have now been implemented. I also posted a note in my hacks, basically saying that they were being moved off vb.org due to policy disagreements and could be found on my site blah-blah-blah.com. I was told to remove the note.

So, whatever the official policy is, that is what happened, and not just to me.

I am not trying to stir stuff up - I'm back, and long over it, but someone asked a question and I gave an honest answer.


All times are GMT. The time now is 12:50 PM.

Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.

X vBulletin 3.8.12 by vBS Debug Information
  • Page Generation 0.01194 seconds
  • Memory Usage 1,743KB
  • Queries Executed 10 (?)
More Information
Template Usage:
  • (1)ad_footer_end
  • (1)ad_footer_start
  • (1)ad_header_end
  • (1)ad_header_logo
  • (1)ad_navbar_below
  • (8)bbcode_quote_printable
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)pagenav
  • (1)pagenav_curpage
  • (4)pagenav_pagelink
  • (1)post_thanks_navbar_search
  • (1)printthread
  • (10)printthreadbit
  • (1)spacer_close
  • (1)spacer_open 

Phrase Groups Available:
  • global
  • postbit
  • showthread
Included Files:
  • ./printthread.php
  • ./global.php
  • ./includes/init.php
  • ./includes/class_core.php
  • ./includes/config.php
  • ./includes/functions.php
  • ./includes/class_hook.php
  • ./includes/modsystem_functions.php
  • ./includes/class_bbcode_alt.php
  • ./includes/class_bbcode.php
  • ./includes/functions_bigthree.php 

Hooks Called:
  • init_startup
  • init_startup_session_setup_start
  • init_startup_session_setup_complete
  • cache_permissions
  • fetch_threadinfo_query
  • fetch_threadinfo
  • fetch_foruminfo
  • style_fetch
  • cache_templates
  • global_start
  • parse_templates
  • global_setup_complete
  • printthread_start
  • pagenav_page
  • pagenav_complete
  • bbcode_fetch_tags
  • bbcode_create
  • bbcode_parse_start
  • bbcode_parse_complete_precache
  • bbcode_parse_complete
  • printthread_post
  • printthread_complete