The Ethics of Updating for VB3 a VB2 Hack That You Didn't Write

[amykhar]

A lot of popular hacks written for VB2 have not yet been ported over to VB3. If you are thinking about updating and releasing them, please consider the following:

1. Thou shalt not use anybody's code without their explicit permission.

2. It is good manners to let the original author of a hack have time to update their work before you pounce on it and claim authorship.

Now, if you know a better or different way to write an existing hack, the above statements don't apply. Just make sure that your work is original and that you get the original author's permission before you use their code.

Swiping code from others without credit is tacky and won't gain you a reputation as a master coder.

[filburt1]

Note that we've already deleted a newly released hack due to this already strongly implied policy. Not only is it illegal, it's immoral to just copy a hack, port it, and then post it effectively as your own.

(hint: this includes translations)

[MGM]

I agree, hacks are just like software, you can not change a few things and call it your own, or you can get sued. While you're not likely to get sued over a hack, it still isn't right, ethical, or fair to the other author.

I have yet to create my own hacks, but when I do, I will be sure not to steal code, and make sure to get explicit permission before using code from another author.

hey, my thoughts count too

MGM out

[MindTrix]

Thanks for the announcement, i think it is needed.

I'm not even going to think of converting someone elses hack to vB3. Just isnt right i tell ya!!!

[Zachery]

i did one users hack >.< only becuase i highly doubt they were going to port it, and all efforts to contact them failed and i of course gave them full credit

[KuraFire]

Originally Posted by Faranth

i did one users hack >.< only becuase i highly doubt they were going to port it, and all efforts to contact them failed and i of course gave them full credit

Same here.

[amykhar]

Personally, I think if the original author can't be contacted for permission, then his code shouldn't be used - even if you give credit. If you desperately need the functionality of the old hack, then I feel you should write it again from scratch.

RC1 just came out a few days ago. There is no way that anybody has had time to say an original author can't be found or isn't going to release their work yet. People go on vacations for longer than a week or two. People change email addresses and don't update their profiles. Just cause you can't contact William Shakespeare, it doesn't give you the right to take his works, change the dates and maybe a name or two and re-release his plays

But, that's just my personal thoughts on that matter.

[Zachery]

well i dont think i could prossibly rewite this one from scratch, its as basic ias it gets >.<

[TECK]

Originally Posted by amykhar

Personally, I think if the original author can't be contacted for permission, then his code shouldn't be used - even if you give credit. If you desperately need the functionality of the old hack, then I feel you should write it again from scratch.

I agree totally. Good to see you as team member, congrats Amy.

[KuraFire]

Originally Posted by amykhar

Just cause you can't contact William Shakespeare, it doesn't give you the right to take his works, change the dates and maybe a name or two and re-release his plays

It does if you're not trying to act like you made / wrote it.