vb.org Archive

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   vBulletin.org Site Feedback (https://vborg.vbsupport.ru/forumdisplay.php?f=7)
-   -   Moderators (https://vborg.vbsupport.ru/showthread.php?t=210319)

Paul M 04-16-2009 10:43 AM

Lots of values are possible, but 180 is the figure decided on.

Dean C 04-16-2009 05:31 PM

So if I go on a backpacking trip this Summer, that means that after 180 days I will have to login and manually set every single one of my mods to supported again? What if one of our top mod authors falls ill, is he going to have to do this for 50+ mods individually?

Shelley_c 04-16-2009 06:15 PM

Quote:

Originally Posted by Dean C (Post 1792659)
So if I go on a backpacking trip this Summer, that means that after 180 days I will have to login and manually set every single one of my mods to supported again? What if one of our top mod authors falls ill, is he going to have to do this for 50+ mods individually?

Chances are whenever anyone goes away for a 5 odd month stint or longer they'll have access to an internet cafe of some sort or own a mobile device which allows them to login to the site which will automatically reset the 180day limit.

180 days sounds good to me. If someone knows they'll be away for 180 days they'll most likely notify the people using the mods that they'll be away for a specified amount of time. If they don't, then the mod should be reverted to unsupported.

I know if I was away for 180 days and I have all my submissions supported I'd feel the right thing to do is have them reverted back to unsupported.

Mind, if you fall ill, that's another story, but then there has to be some kind of balance that will allow the author to log back in for this limit without it being too soon and for members who think the mod is support when it's not prolonging their wait for a mod that could be unsupported for a year or longer. 180 days sounds good, you'll never get a setting that will keep everyone happy. For authors, they'll always want their mod support and kept as supported whilst it's only fair on the members that they know asap when and if a mod becomes unsupported even before the 180 days.

hambil 04-16-2009 06:21 PM

Quote:

Originally Posted by Paul M (Post 1792062)
If a developer has not logged into vb.org for more than 180 days then their mods will now show as unsupported.

Nice work, again :) Thanks Paul.

Shelley_c 04-16-2009 06:57 PM

@ Dean C - I checked your releases and all but one of your mods leading down through the 3 series are all unsupported. Only one of your scripts are marked up as supported which is for the 3.67 line so I doubt you'll get many complaints plus it would take you but a second to mark it back as installed if there is still demand for this product to be supported.

I'm replying back because they way you were talking I thought you may have had at least a score of scripts marked up as supported. I'm guessing the complaints would be warranted if you had a high count of scripts on the supported list.

it'll take you a second to mark it back up dean.

I dunno, I was looking at the profile page. I don't know how difficult or time consuming it would be to implement a icon/select box alongside Release Date - Last Updated - Total Installs were members from here and deselect whether or mot the product goes into the supported. I know they'll do it when they first post their mod but i was thinking it would be easier to select/deselect it for the authors with 20+ and on the off chance they are away for more than 180 days. Eitherway, I'm not fussed.

nexialys 04-16-2009 07:00 PM

Quote:

Originally Posted by Dean C (Post 1792659)
So if I go on a backpacking trip this Summer, that means that after 180 days...

you must be rich enough to go backpacking for more than 180 days... so i suppose you would hire a slave to click these support checkboxes again...

Quote:

Originally Posted by Dean C (Post 1792659)
What if one of our top mod authors falls ill

you really have to focus on your own situation instead of arguying for the others Dean... these Top Posters can have their own opinion, and i'm sure they do not care the same way as you are...

Paul M 04-16-2009 07:02 PM

Quote:

Originally Posted by Dean C (Post 1792659)
So if I go on a backpacking trip this Summer, that means that after 180 days I will have to login and manually set every single one of my mods to supported again?

Nope. The supported status is not changed, just the display.

Just for once, it would be nice if people actually remembered we do think about things before we do them. The fact that people would not want to change all there mods status back again did actually occur to me.

Dean C 04-16-2009 10:26 PM

Quote:

Originally Posted by Paul M (Post 1792731)
Nope. The supported status is not changed, just the display.

Just for once, it would be nice if people actually remembered we do think about things before we do them. The fact that people would not want to change all there mods status back again did actually occur to me.

Hey don't tar me with their brush ;) I was just asking a question about a scenario! Good implementation anyway, thanks Paul.

nexialys 04-16-2009 11:05 PM

Quote:

Originally Posted by Dean C (Post 1792878)
Hey don't tar me with their brush

hum, actually it was YOUR brush, don't try to diminish your impact here, you asked the question, we did not type if for you...

tsssss

anyway, i have no need for a toothbrush!

http://www.killsometime.com/Pictures...s/No-Teeth.jpg

EnIgMa1234 04-16-2009 11:55 PM

Quote:

Originally Posted by setishock (Post 1789278)
I've seen some of the coders and style makers that pour their hearts in to what they do and give first class support. Those deserve our thanks. The ones that don't offer any support when they've checked "supported" really should be dealt with and as soon as humanly possible. And include those that have you have to sign up at their forum to get any support.

You can't punish someone for releasing FREE software to a community. Where the author wants to handle support is up to him, not the members downloading it. These coders releasing their work do have lives and are not working for the members of vbulletin.org despite popular belief.


All times are GMT. The time now is 08:26 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.01059 seconds
  • Memory Usage 1,750KB
  • 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
  • (2)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