Amend Service Request forum description

[Princeton]

As stated on my first post, this has nothing to do with commerical or free addons. It has a lot to do with supporting vBulletin code-hackers at all levels.

I do not believe that these requests should be available for discussion.

• In some cases, this only leads to "promoting" the product.
• Some beta-tester requests (products) are never made available to the public (free or commercial)
• Some professionals would prefer not to have beta-testing available to the masses. eg. Beta forums
• Some professionals would like to get help on creating FAQ and/or Manual writing etc vb.org does not have the resources (nor should they) in providing authors the ability to track such events.

SOLUTION

• Do not allow discussion of such requests here on vb.org.
• Amend the SERVICE REQUEST FORUM and allow such requests to be submitted there.
• Do not allow the inclusion of product name. (minimize the promoting of product)

Such a solution would promote better addons (free or commercial).
Such a solution would promote the request for a limited time only. eg. It will not be bumped because of "discussions" going on.

-Release modifications (hack and template)
-Talk about vB

Just curious ... Is that the official description of vb.org?

[Ron1n]

Or they could just run it like they run 2.0 and 3.0...

Now, if people USE (I don't use that term lightly) us to get beta testers and then release their work elsewhere, it ends up not contributing anything to vB.org after using its very valuable resources.

So... lets just take this small risk and use it as an excuse to have coders release crappy first mods with tons of bugs.

If it were in a forum, you could have actual releases that were betas (like 2.0 and 3.0) and you wouldnt have to worry about people not releasing it to the public or trying to sell it because the beta would be available to everyone.

And to your comment about not being used... what look at the 3.0 and 2.0 forums which have 150-250 threads and several thousand messages. Thats not even including all of the threads that were posted and then moved to the appropriate forum once they were completed.

[Tony G]

Just curious ... Is that the official description of vb.org?

No. Go ask at vB.com if you want an official description for whatever reason. But I told you what vB.org is and I would have hoped you'd know by now too.

[Princeton]

Originally Posted by Tony G

No. Go ask at vB.com if you want an official description for whatever reason. But I told you what vB.org is and I would have hoped you'd know by now too.

Sorry, I don't mean to be pushing your buttons... :squareeyed:
but don't you think that should be here?

No need to reply to that ... just something you guys should think about.
(let's get back to the subject)

[MRGTB]

Well I think if a person wanting Beta Testers wants to advertise for them here. He should provide certain information by default. Remember vBSeo used Beta Testers and he still made them pay for his product in the end. But then he never said they "WOULD "get a free version for helping to beta test it!

So, if a person wants "Beta Testers" they should!

1: State if the hack is going to FREE or PAID. And if it's going to be a commercial paid hack, they should let possible beta testers know if they will get the hack for free in the end for helping beta test the paid product as a reward for helping to beta test it. (that should be made quite clear if it's going to be a paid commercial hack). Otherwise beta testers are just being used for free to help a commercial hack make money for that person who created it only, with no gains for the beta testers efforts!

2: Say if the hack is being beta tested to be released on vB.org (If not he or she should not be allowed to ask for Beta Testers here). We don't need every man and his dog from other sites using vB.org as place to poach beta testers for there own personal gains on other sites away from vb.org.

4: Is the hack FREE or COMMERCIAL, and will there be a free light version released if it's a paid hack.

[Princeton]

Originally Posted by Gary Bolton

Well I think if a person wanting Beta Testers wants to advertise for them here. He should provide certain information by default. Remember vBSeo used Beta Testers and he still made them pay for his product in the end.

If a person wants Beta Testers they should!

1: State if the hack is going to FREE or PAID. And if it's going to be a commercial paid hack, they should let beta testers know if they will get it for free in the end for helping beta test the paid hack as a reward. (that should be made quite clear if it's going to be a paid commercial hack).

2: Say if the hack is being beta tested to be released on vB.org (If not he or she should not be allowed to ask for Beta Testers here).

Regardless of what they say, you really don't know what the final outcome will be.
eg. They could turn around and do the opposite of what they say.

Request should ask for whatever it is that they are seeking (eg. testers, writers, etc) and describe the product without putting a name to it.

[MRGTB]

Originally Posted by princeton

Regardless of what they say, you really don't know what the final outcome will be.
eg. They could turn around and do the opposite of what they say.

Request should ask for whatever it is that they are seeking (eg. testers, writers, etc) and describe the product without putting a name to it.

My only concern here is this - I don't like it when you get a coder asking for Beta Testers, while at the same time not giving much other information about things. Beta Testers play an important roll in helping to iron out bugs and offer the server and forum software for free to help a coder release a good hack free of bugs.

They should get rewarded for this, I just don't think it's fair when a coder says: (Hey I need some beta testers, anybody up for it). Then after testings complete, they come out and say the hack will cost so much to buy!

I would prefare to see a site guidline introduced were things have to be made much more clear by coders asking for Beta Testers free services, so they are not fooled into thinking the hacks going to be free when it's not in the end.

Which they will have to buy even after beta testing.

[Revan]

Originally Posted by princeton

Regardless of what they say, you really don't know what the final outcome will be.
eg. They could turn around and do the opposite of what they say.

One word: Banstick.

[Paul M]

No one is going to "poach" beta testers - I'm sure they can make up their own minds as to whether they will help test a hack based on the information given (such as will it be free, will it be released here). No one is forced to be a beta tester.

[MRGTB]

Originally Posted by Paul M

No one is going to "poach" beta testers - I'm sure they can make up their own minds as to whether they will help test a hack based on the information given (such as will it be free, will it be released here). No one is forced to be a beta tester.

Yes, thats right. But it would be nice of coders to tell Beta Testers first if there creating a paid hack that they will have to pay for even after they beta test it. At least make them fully aware right from the start.

Rather than tell them it's going to be a paid hack after they have finished beta testing and the coder no longer needs there services.

PS: Paul M have you ever lived in the North West in a pie eating town, you have the same name as a person I used to know and go to school with who was into computers