Important: It is all about trust

We will not give the name of the coders out.

How could they be guilty if the policy was put into affect after we became aware of the code they placed in the products?

This is the whole point of the announcement, to let everyone know: coders, members, and staff that, now, any unethical code found in plug-ins/products will not be tolerated, just like any harmful code will not be tolerated.

[Paul M]

Originally Posted by FASherman

<long post>.

1. That will never happen - you cannot expect free code to be supported.

2. That would prevent anyone new from releasing anything - to become a coder you have to have released hacks that people have installed.

3. Far too complicated, that would put off most people.

4. Coder titles are not based on post count and never have been.

5. HOTM has already changed, the new system relies on nominations.

6. A checking procedure is planned, things don't happen overnight.

7. There is already a procedure for mods/plugins etc that pose a security risk.

8. Been discussed many times, as I understand it vb.org will not be hosting commercial work.

Also, you seem to keep going on about security and backdoors despite the fact that several posts now have clearly stated this was not the case.

[DementedMindz]

Originally Posted by JohnBee

If this is the case then the coder in question must face the responsibility for his or her actions.

yeah this is true but from what i seen it took the wrong direction and now there part of vb.org Coding Team... :surprised:

[Shaliza]

Who said anything about giving out the names of the coders? I'm talking about the name of the actual hacks.

[Adrian Schneider]

Originally Posted by Danny.VBT

We will not give the name of the coders out.

How could they be guilty if the policy was put into affect after we became aware of the code they placed in the products?

This is the whole point of the announcement, to let everyone know: coders, members, and staff that, now, any unethical code found in plug-ins/products will not be tolerated, just like any harmful code will not be tolerated.

People can be guilty of rules not yet made, though the fact remains that they are guilty.

Originally Posted by Shaliza

Who said anything about giving out the names of the coders? I'm talking about the name of the actual hacks.

For most of us, that is just as obvious.

[libertate]

Now that I am a bit calmer, it is sort of funny.

VBorg created this monster actually... by making install count an element of the stature of a programmer within VBorg. Of course a programmer is going want to get all the credit that they dully deserve. So creating a system that auto-clicks install is not such a horrible thing...

If that is all that is out there...

And yes, VBorg = Jelsoft. I don't care how much you say it isn't. Jelsoft finances the site, Jelsoft directs the site, and many Jelsoft employees run the site.

[Martin]

Originally Posted by libertate

Jelsoft directs the site, and many Jelsoft employees run the site.

Not true

[Shaliza]

I never thought it was horrible. I just didn't get why nothing was said, but that question keeps getting danced around on, but I can probably figure out why. And some people actually forget to click on it by mistake.

Originally Posted by Martin

Not true

Oh snap.

[Grae]

We will not give the name of the coders out.

wow :surprised:

Without knowing the names of these unethical coders that exploited the trust of regular members, what else can one do but assume all coders on this forum were involved. If I contributed mods to this site, I would be strongly voicing my opinion that the usernames and hacks should be exposed. Not doing so would hurt my reputation. I may not be a big part of this community or have a large post count, but I am confident that many other members feel the same way.

[Shaliza]

Well, those coders will probably keep putting it in, but now I bet loads of people are checking the codes inside out now.