vb.org Archive

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

nexialys 11-04-2004 09:43 AM

my clients are posting their results after my job is done...

and see the result in trader Rating...

>> thanks again eoc_Jason...

@Dean C... everything can be bought... with no restriction, i can register 500 members and post comments and ratings on my board to make my own reputation rise... i can do it also by using these 500 registration and click 500 times on Install for my hacks...

if users are forced to put the url of the modifs, we will have proofs of the work done... !!!

G3MM4 11-04-2004 04:45 PM

It might be open to abuse but someone could find a way around this.

It's not impossible. Where there is a will, there is a way!

Princeton 11-04-2004 05:26 PM

I'm not a legal guru but, if some kind of 'trader' system is put up vbulletin could be opening the doors for litigation ... some legal consultation is advised.

A good rating coming from this site could be an endorsement for that party; and, as we all know the rating could be a 'false' good rating. It also works the other way around ... a 'false' bad rating could be bad for business (for a member) and thus open the door for grievances maybe even litigation if party has been hurt.

The proper way to do this is to leave things the way it is but to encourage users to post good/bad testimonials (posts) within the 'request' thread. I would also recommend having a disclaimer that a requestor has to read and check before posting.

just my 2cents

Dean C 11-04-2004 05:55 PM

Quote:

Originally Posted by princeton
I'm not a legal guru but, if some kind of 'trader' system is put up vbulletin could be opening the doors for litigation ... some legal consultation is advised.

A good rating coming from this site could be an endorsement for that party; and, as we all know the rating could be a 'false' good rating. It also works the other way around ... a 'false' bad rating could be bad for business (for a member) and thus open the door for grievances maybe even litigation if party has been hurt.

The proper way to do this is to leave things the way it is but to encourage users to post good/bad testimonials (posts) within the 'request' thread. I would also recommend having a disclaimer that a requestor has to read and check before posting.

just my 2cents

Some good points there princeton, and I'd have to agree with you :)

peterska2 11-04-2004 09:06 PM

Thinking out loud here (I know I do that far too often ;)) Now do you remember (how could you forget?) all the problems that were had with insanctus and the huge thread that ended up about him?

Now what if something like the usernotes system was implemented whereby people can post usernotes about the person who has done something for them and leave a review of the work that way? It could be done that only licenced members can post them and view them.

There's the other side as well where you slog your guts out doing hours and hours of work for someone who then ignores your emails when it is done even though you have been keeping them updated, doesn't respond to Pm's saying that it is completed, then even more annoyingly posts another request for the same modification to be made with a couple of extra bits for double the money. [insert angry smilie here]

A notes system could also be used for people who make requests so that other people don't get stung by people who either don't pay, or simply cut off all contact with the coder leaving them with a major custom job which is not likely to be of any value to anyone else so is not put on public release and even if it was it wouldn't be put on piblic release becasue you just know that the person that you have done the work for will then download and install it for free instead of for the $$$ that was originally agreed. (Sorry if I'm ranting a bit but this has happened to me last month to the tune of $200 and again for $40 so I'm well out of pocket for work done that sat nicely on my desktop in the folder called - awaiting release to client)

A feature I would like to see in this if something can be implemented is a compulsary link to the request that was carried out by the coder or the request that the coder is posting requester feedback on. IMO this should be auto populated by using some form of link in the service requests forum in post #1 for each thread.

On the requesters side this would be something where the requester can click to a list (perhaps dropdown-ish or member list-ish) where all licenced users with over x posts are listed. They then select the correct username and this takes them to the commenting system where they leave their comments. A simple save would then add the comments to the coders profile. There should also be something as simple as some predetirmed fields including 'coder hired', 'work completed', 'work not completed to deadline', 'coder fired', and 'job withdrawn'. These would be used to keep the system upto date with feedback and no comments would be needed for these although an optional text box should be available for freetext comments on the pre-populated set fields as above.

On the coders side there should be a link in post #1 of the service request whereby the coder can rate the requester. This again should have pre-detirmined fields such as 'clear consise specifications issued', 'access required granted', 'modification completed - approval pending', 'payment pending', 'payment recieved' and 'modification installed'. Again these should have optional free text fields where additional comments can be left. The page when clicking onto the link in post #1 should be prepopulated with the requester's username and the link to the request. Again these would be used to keep the system upto date with the status of the work.

As a potential add on to this, there should be set routes where the thread autocloses. Upon the thread closing no further comments can be posted for that thread. I would like to have these set at 'coder fired' if selected by the requester, 'hack installed' by the coder, 'work completed and installed' by the requester, 'payment not recieved' by the coder but this should happen 7 days after that message is added to the requesters profile to enable time for the payment to be recieved or negotiations between the requester and coder to take place. If the status is not changed in that period of time then the thread should close but if it is updated then it should remain open unless the new status is one where the thread is to close. The ability to close own threads would not then need to be required for that forum.

Another nice little add-on that I would like to see is where the most recent status applied to that thread appears under the thread title so that anyone who browses that thread can see where it is up to. This would then potetially prevent people sending PM's applying for the coding work after someone has been offered the job and already commenced the work.



Ok so I know that sounds like a coding nightmare to write but it would be nice if something along those lines could be implemented as it would take care of a lot of current issues and also add details about the work completed. Even if no comments are added by either user involved and just the pre-determined fields used then you still get information as to if a coder completes the work or not and if the requester pays or not. These are the two most important things IMO that should be logged somewhere. After all no-one wants to hire someone who doesn't do the work or do the work and then never get paid for it.


[off topic]OMG that's my longest ever post on any of the vB sites[/off topic]

nexialys 11-04-2004 10:01 PM

peterska2 is always right (as said, thinking out loud too often too.. lol)

so the best thing to do with any kind of situation is to start an outsider freelancer management system, where all the projects are called publically, where any coder can give a resum? of the job they have done, what they provide if they do the job, etc... and clients that resume their results, satisfaction to the coder, etc...

this is already made for many freelancers websites, but none is related to vBulletin exclusivly. i've received more than 50 contracts that way in the last year... freelancers sites are good place for controling the quality of coders... i'm not always having good references when a job is done, but usually, i'm able to explain the results of any job, and why the client is not satisfied, (and yes, i many times given the excuses to be redblooded and harsh against some clients reactions)... ;)

here we can't explain a thing, we can't even answer threads directly, and 99% of the clients will never read the others' requests because they will not bring any real information on the job to be done... even many clients simply ask for "a job to be done", not giving a hint to anybody...

there is no solution for this situation, so maybe it's time to turn the page ?!
vB|Professionals is built for this single purpose, give a place for pros to display their potential and for clients to ask for services... anyway, the site is not published as is for now, as i don't have time to implement what is needed yet... i'm working on the phpAuction software that will give us a Reverse Auction that will bring that opportunity... freelancing for vB...

Xenon 11-05-2004 01:01 AM

Well, apart from advertising own sites here, nexialsys is right.
We offer the Service request forum as a platform so people who want to pay for help, can do so here.

From day one on we said, that we won't take any responsibilities about those servicerequests.
vb.org will stay a site for free hacks, and that main aspect won't change.
So that's the answer for your good but unpractial suggestions Kerry-Anne. If we'd spent so much time in those codes you suggested, it would look like vb.org would be a real portal for hireing coders, and that's what we definitelly don't want.

nexialys 11-05-2004 01:59 AM

hey hey... i forgot the advertising stuff.. lol.. sorry Stefan !

btw, this was to tell that there is external possibilities, and growing ones... no need to put everything on the same site, if someone else is taking care of the business...


All times are GMT. The time now is 06:11 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.01130 seconds
  • Memory Usage 1,770KB
  • 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
  • (1)bbcode_quote_printable
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)pagenav
  • (1)pagenav_curpage
  • (1)pagenav_pagelink
  • (1)post_thanks_navbar_search
  • (1)printthread
  • (8)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