vb.org Archive

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   vBulletin.org Site Feedback (https://vborg.vbsupport.ru/forumdisplay.php?f=7)
-   -   Suggestions for optimal Modification Management (https://vborg.vbsupport.ru/showthread.php?t=115642)

hambil 05-17-2006 06:57 PM

I repost this here, since I think it belongs:

I think we should hook into the hack database like Windows does for updates. A single product could be written that acts a lot like Windows Automatic Update. The user could select "automatically update" or just get notifications when they log into their board, and click on the manual update button.

The product would check what other products and plugins they have installed, and report back to the hack database to check for updates and manage install counts.

The benifit to the user would be automatic security updates and hack updates. The benifit to the coder would be an accurate install count.

It could work over https and be as secure as we can make it. Only people who install the product would be reporting to the hack database, so it's completely opt-in.

Gaskell 05-17-2006 07:16 PM

Quote:

Originally Posted by The Geek
Development

Harness some of the coders here to create the system. To do this project right, it will take ages for 1 person to do. Furthermore you wont get a fraction of the features implemented that coders and users want which will result in people whinging about it.
Sure there are security concerns - however a team working together can check one another's code and the whole thing doesn't have to go live until it gets an OK by vb staff

Sounds a good idea. Got all this unused potential here going to waste. The coders here code vB mods because they like the software. Why not let them put something back into it, at least on a small scale? Not a coder myself, but I would definately be up for some beta testing if this were to happen some time in the future.

The above points have probably already been said somewhere in a similar post on here by someone else

Quote:

Originally Posted by The Geek
Filter system.

The current flow at .org is confusing. Modifications are grouped into a few odd categories (plug ins, extensions, etc...). I see the thought behind the concept - however users want to be able to group based on functionality, not on whether they need ftp access (remember that vB needs ftp access so at some point they had to use it!).
It makes sense to be able to filter a search (or just a regular listing) of modifications that meet a particular criteria. Some suggestions off the top of my head are:

* Requires vB file changes
* Requires vB template changes
* Contains additional files
* Contains additional templates
* Known to work with vB version x
* Has more than x Installs
* Adds functionality in x Areas (sounds odd, but kind of how the categories were group before: forumdisplay changes, user profile stuff, showthread stuff, etc...)

There are loads more, and certainly you wouldn't need them all, however it could prove VERY useful to coders AND users.

Shouldnt be too much hassle, even just an advanced search based on the tick-boxes on modification releases set as a link on Forums Index (for one approach) :)

Quote:

Originally Posted by The Geek
Mini Bug tracker

I really do not feel that this would be overly difficult to implement, however it would clean things up dramatically. Allow people that have downloaded the modification to post in a bug tracker associated to that release.
This gives coders a one stop place to find, control and track bugs and the users a one stop place to see what issues are outstanding.
Leave discussion forums for troubleshooting and general discussion.

Another good suggestion. Would be canny, especially in "hot" releases where theres odd bugs in the middle of loads of "cool hack!" posts. Easier for coders to keep track of things they need to sort and to keep users up to date without spending ages looking for relevent posts :)

Quote:

Originally Posted by The Geek
The coder/designer/project smilie system.

Allow users that downloaded (and hadn't uninstalled the system) to give the coder/project on its merits (kind of like a positive only rep system):

* Functionality
* Ease of use
* Features
* Support

Let the user give them a smilie if they feel it warrants it. For instance, the functionality was good so they get a smiley face there, but support was only mediocre so they get nothing there. No rating, no frowny smiles, only big grins (i.e. this project has over 50 functionality smilies). It could be a cool incentive system. Then again, I could have had too much crack with my Cheerios this morning. Regardless, look at some kind of a rating system.

At-a-glance feedback for coders and easier for users to see what mods people are happy with? Sounds a good-'un :)

stonyarc 05-17-2006 08:16 PM

I also think that if we implement bugtracker/project management we should also make it multiuser.

That way some users can go coop on mods.

I had to put some of my projects on hold just because I don't have the time. If I could work together with another coder/designer/.... that would save time for a lot of coders/designers/members/... and maybe create some additional inspiration for the people working on the project.

Team based mod db (a team can be 1 person too).

Also I think it's vital we have some documentation standards set and included in the mod db. I noticed that since I started adding a well documented guide with all my major mods the number of "avoidable" support questions has dropped a lot.

Freesteyelz 05-18-2006 12:05 AM

If someone who've installed a hack and clicked "Install" unchecks "Receive Email from Other Members" via User CP, will he/she receive an e-mail if the hack author sends out an update?

Paul M 05-18-2006 02:16 AM

AFAIK, Yes.

Freesteyelz 05-18-2006 04:19 AM

If that's the case then there is room for the privacy argument. Though, I don't see it to be an issue at all.

GamerzWorld 05-18-2006 08:07 AM

Apart from for bug purposes what would the purpose be of knowing what version, who and when someone download your hack? If you make a mini tracker, simply make the field with version compulsory? I dont really understand why the privacy thing is an issue, as far as im aware you can already automatically send updates, so what would really change?

creedmaniac 05-18-2006 08:34 AM

i'd like to see another custom field in the installed hacks section of the usercp that allows each member to type in stuff for that hack...like a notes section for themself (i would use it for noting which site has what mods on it...since i don't install all of them on all sites..but it could be used for anything)

The Geek 05-18-2006 09:33 AM

Quote:

Originally Posted by Freesteyelz
If that's the case then there is room for the privacy argument.

Not really. What you're saying there is:

vBulletin protects privacy through not discolosing if you downloaded a modification to the author as long as you 1- don't post in the release thread and 2- make sure you have ticked 'do not recieve email'. If you have posted in the release thread and allow members to email you through the site - you have a teeny weeny risk that someone is going to add you to their chritmas card mailing list.

Considering that you can only send 1 person at a time an email - you're in for the long haul and you should start at Easter.

You can only argue the privacy thing if it is enforced across the board (which it isnt - therefore it can't matter THAT much).

To me, being able to see a history of downloads is a help for support issues(and something I rely on at thevbgeek.com) to a degree it also protects intellectual property.

BTW: I have been tinkering with this already. However I seem to recall that there was some possible discussion about a third party app for this system.

Can we get an idea if its worth spending any time at all on it or not? If it's worth investigating, then I'd like to post some stuff in the coders forum to see if it will help get the ball rolling with some other coders.

Thanks!

Freesteyelz 05-19-2006 02:38 AM

O. I didn't know I meant that. LOL.


All times are GMT. The time now is 03:06 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.01085 seconds
  • Memory Usage 1,752KB
  • 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
  • (5)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