How about mods having to meet some minimum standards....

[Gio~Logist]

Originally Posted by Wayne Luke

It specifically states in the license agreement that you can have a Production/Live installation and a Test/Development installation. In fact we encourage people to have a test/development installation so you can test out upgrades and addons without affecting your live site and causing issues that would adversely affect your community.

What are the requirements for "test/development" installations. Just needa be private?

[Marco van Herwaarden]

You can read the requirements in the License Agreement

If you have a valid Software license, you may set up an additional test forum in order to test code, template and database modifications. To make this clear to us and our license verification procedures, place it in a directory called 'testvb' and be sure to password protect it. It must not be accessible by the general public.

[Rene Kriest]

Originally Posted by Marco van Herwaarden

We have no intention to change our policy on modifications. We have a limited set of guidelines/rules in place, but we try to keep low requirements for sharing solutions with the rest of thecommunity. We could add a lot of (artificial) rules a modification must follow, but that will only lower the number of submitted modifications.

Agree.

There is a rating bar and the comment section available to every addon. These two ensure that users can share their experience regarding addons. I at least browse through the comments section and take a closer look at the last entries and also on the response rate of coders who marked "supported" = yes before I consider even downloading a addon.

We all have time limitations but addons whose coders never updated in month while there are nasty bugs reported are a no-go for me. Security and stability rule, rest drools.

Testdriving on a non-productive server is not always an option because what seems to work or at lest doesn't harm can later show its real implications.

I trust in the opinion of other coders which "control" the source of other coder's addons.

[Kinneas]

Originally Posted by jdelasko

Well Marco .......... I guess that ends this conversation. Not everyone is into quality control I guess.

Attention all coders: Go ahead and post your hack job of a mod on this site. It's ok.

Maybe you should actually do your research and not just install any random mod because it looks good. Rather than expecting everyone else to police the mods for your convenience. You do realise nobody here is paid for the work they release, right?

[lasto]

Originally Posted by Kinneas

Maybe you should actually do your research and not just install any random mod because it looks good. Rather than expecting everyone else to police the mods for your convenience. You do realise nobody here is paid for the work they release, right?

why everyone getting worked up - the guy asked a decent question.So instead of we dont plan on changing our policy try spend the same energy on finding solutions to problems.
Also seeing as this is a members board - maybe asking the members once in a while what they want may help instead of always telling us what we cant have.

Originally Posted by lasto

Also seeing as this is a members board - maybe asking the members once in a while what they want may help instead of always telling us what we cant have.

For this, i would like to introduce to you the "Modification Requests (Unpaid)" forum... people suggest things they would like to see as addons/products...

sometimes, people are asking too much...

sometimes...

[jdelasko]

Originally Posted by Kinneas

Maybe you should actually do your research and not just install any random mod because it looks good. Rather than expecting everyone else to police the mods for your convenience.

Look numnuts..... nobody asked everone else to police mods for my convenience. That was an idiotic response. All I said was that mods should adhere to a specific set of guidelines. WTF is wrong with that concept? It's callled QC and QA. That simply means, letting others know exactly what modification are being made when a mod is installed, and what is required to undo those modifications. It is not always just the reverse proceedure. Some of these coders obviously put a lot of hours into a given work and asking to put a reasonable effort into documentation is not, in my opinion, an unreasonable request.

FYI - I do read the entire mod thread, and I DO indeed do my own research, so you may can the attidude.

Originally Posted by Kinneas

You do realise nobody here is paid for the work they release, right?

So what's your point? Are you saying that since something is available at no charge, it's ok to have serious flaws, and that people should just accept those serious flaws, and just shut up about them?? Anyone that actually believes that, should not post their work in the first place.

[SEOvB]

Originally Posted by jdelasko

So what's your point? Are you saying that since something is available at no charge, it's ok to have serious flaws, and that people should just accept those serious flaws, and just shut up about them?? Anyone that actually believes that, should not post their work in the first place.

True they shouldn't be posting their work, but thats just the way it goes sometimes with people who are new to programming or just trying to get started. I agree there should be some QC, but there is no real way to implement it without someone viewing and auditing every single line of code thats here.

[Shelley_c]

Originally Posted by jdelasko

Look numnuts.....

LOL Haven't heard that one for years.

[Lynne]

Sometimes too many rules will cause users to not take that first step and post their first modification. They get too worried they are going to break a rule and get their mod pulled. So, it's better to gently lead them down the right path. If they did something 'wrong' in their modification, you send them a nice PM or make a post with suggestions on what to add next - "Sometimes new people unfamiliar with modifications will install a new mod and then decide they don't need it and go to uninstall it and don't understand how to do so correctly, especially when there are files uploaded. It's a really good idea to include uninstall instructions that detail exactly what to do for these newbies." Most coders what to do it right and being polite while pointing out a problem will be much more effective than adding a rule.