intellectual property rights?..vb6 program..
September 20, 2010 10:09am CST
have you ever experienced doing a school project by group?..how about a groupwork in creating programs in vb6 wherein you do most of the designing and codes?..your members help too but in some peripheral things only like documentation and typing..do you think they have rights over that program?..or only the one who made the program is entitled to its intellectual rights?.. what would be the best thing to do when one of your members in such groupwork wants to have a copy of that program and use it maybe for some other purpose like reference and model?..will you ask him/her to pay?..or just give the copy of the program to him/her?.. any advice would be greatly appreciated..thanks..
• Cambridge, England
20 Sep 10
Since the project is a group project for school, technically ALL the work involved in the project belongs (a) to the school and (b) collectively to all the members of the group (unless you signed anything specifically to the contrary). Since it is group work, all members of the group should, by right, have a copy of all the code and documentation. If, however, they intended to use the code (or to modify it) for 'personal gain' (in other words, in order to sell it or make money out of it) then they would certainly need the permission of the other group members and probably of the school as well. It is a well accepted principle in business that, if a programmer is employed by a company and produces code for that company in company time, it is the company that owns the code, not the programmer (unless the contract specifically stated otherwise). The same principle could be legally argued to be true in the case of a student or students producing code (or anything else) for coursework. Most schools and colleges would not, in fact, be opposed to someone using the code elsewhere but it would only be fair and polite to ask for a letter from the school allowing its use. It would certainly be proper to ask for the permission of the other members of the group who cooperated in the project, in whatever way.
23 Sep 10
very nice explanation owlwings..you have a good point there.. i feel too bad..i felt that i should've just submitted an executable version of that program and never game them the vb6 project files..tsk.. anyway, thanks for the response owlwings..very much appreciated.. have a nice day ahead..
20 Sep 10
I'm not really sure, but if you think that what you created would be worth something one day, then I guess the best thing to do before sharing your stuff with others is to have it copyrighted to your name first, and then maybe that's the time when you can start asking a price for the copy.