Submission Policies
-
I've a pretty big project I'm considering posting to this site ... actually it is so big that I may start with just posting parts of it to start with....The trouble is that: Whenever I pull interesting code into my projects I will always move through it with a fine tooth come for the purposes of: 1. Seeking full understanding of how the code in that-something works. I don't like to pull stuff in without having a very good idea as to how it works. You know, how can I hope to debug/enhance anything if I don't even understand what it is doing. 2. Making the style of all the files in the project "internally consistent" when it comes to function names, class member variables, ProperCase on functions, hungarian notation, put in comments I deem appropriate, etc. etc. etc. In other words, I can mangle up the file pretty well. I do this so that as I'm working on a project I don't have to switch mental hats evertime I step into a new file/class. Some of these files have been mangled to the point that they bear little, if any, resemblance to whatever the original file was. Moreso, I can't even remember where some of this stuff comes from anymore, so while I am willing to give deference to previous authors, and give credit where credit is due, I don't think I can completely. So here is my question: If a project is posted that contains pieces-and-parts that are partially seeded off another coders work, but whatever comments the original authors put in is lost or severely mangled; how busted will I be with the other folks on this site? I've gotten 'wiser' lately and strive to keep original authors' comments intact, but I have to admit that was not always the case. So, do I dare post a project here or will I just get crushed by the public? On another related note: If a project contains code that is published in a book, or is from commercial libraries, then should not that code be compiled into a lib to protect the copyright of that authors/publishers and also protect this site from any kind of infringement issues? The project I'm thinking of posting could be of great interest to a lot of folks, but I don't want to create a firestorm of bad vibes / ill will. Thoughts anyone? Just trying to keep the forces of entropy at bay
-
I've a pretty big project I'm considering posting to this site ... actually it is so big that I may start with just posting parts of it to start with....The trouble is that: Whenever I pull interesting code into my projects I will always move through it with a fine tooth come for the purposes of: 1. Seeking full understanding of how the code in that-something works. I don't like to pull stuff in without having a very good idea as to how it works. You know, how can I hope to debug/enhance anything if I don't even understand what it is doing. 2. Making the style of all the files in the project "internally consistent" when it comes to function names, class member variables, ProperCase on functions, hungarian notation, put in comments I deem appropriate, etc. etc. etc. In other words, I can mangle up the file pretty well. I do this so that as I'm working on a project I don't have to switch mental hats evertime I step into a new file/class. Some of these files have been mangled to the point that they bear little, if any, resemblance to whatever the original file was. Moreso, I can't even remember where some of this stuff comes from anymore, so while I am willing to give deference to previous authors, and give credit where credit is due, I don't think I can completely. So here is my question: If a project is posted that contains pieces-and-parts that are partially seeded off another coders work, but whatever comments the original authors put in is lost or severely mangled; how busted will I be with the other folks on this site? I've gotten 'wiser' lately and strive to keep original authors' comments intact, but I have to admit that was not always the case. So, do I dare post a project here or will I just get crushed by the public? On another related note: If a project contains code that is published in a book, or is from commercial libraries, then should not that code be compiled into a lib to protect the copyright of that authors/publishers and also protect this site from any kind of infringement issues? The project I'm thinking of posting could be of great interest to a lot of folks, but I don't want to create a firestorm of bad vibes / ill will. Thoughts anyone? Just trying to keep the forces of entropy at bay
RedZenBird wrote: If a project is posted that contains pieces-and-parts that are partially seeded off another coders work, but whatever comments the original authors put in is lost or severely mangled; how busted will I be with the other folks on this site? I think you are sensible to be wary in this case. It's very unlikely anyone now has 100% original code. Regularly I drop sections of say "MSDN" stuff into mt code to use as an example while I'm working, and quite often I'm happy to use there naming conventions if I'm to lazy create my own. I have done the same with code from this site and from books. I treat a copy and paste totally different from importing a whole class file. ( I know thats wrong ) Not wanting to tell you not to submit code, (sorry for the double negative) I suggest that you be darn careful with what you do submit and if you are in doubt as to the origin of a code segment. Clearly mark it as such in your submission. But as always if you submit any work publicly for peer review, expect criticism. My 2 cents Regardz Colin J Davies
Sonork ID 100.9197:Colin
You are the intrepid one, always willing to leap into the fray! A serious character flaw, I might add, but entertaining. Said by Roger Wright about me.
-
RedZenBird wrote: If a project is posted that contains pieces-and-parts that are partially seeded off another coders work, but whatever comments the original authors put in is lost or severely mangled; how busted will I be with the other folks on this site? I think you are sensible to be wary in this case. It's very unlikely anyone now has 100% original code. Regularly I drop sections of say "MSDN" stuff into mt code to use as an example while I'm working, and quite often I'm happy to use there naming conventions if I'm to lazy create my own. I have done the same with code from this site and from books. I treat a copy and paste totally different from importing a whole class file. ( I know thats wrong ) Not wanting to tell you not to submit code, (sorry for the double negative) I suggest that you be darn careful with what you do submit and if you are in doubt as to the origin of a code segment. Clearly mark it as such in your submission. But as always if you submit any work publicly for peer review, expect criticism. My 2 cents Regardz Colin J Davies
Sonork ID 100.9197:Colin
You are the intrepid one, always willing to leap into the fray! A serious character flaw, I might add, but entertaining. Said by Roger Wright about me.
Colin^Davies wrote: I suggest that you be darn careful with what you do submit and if you are in doubt as to the origin of a code segment. Clearly mark it as such in your submission. That is a good point. If I decide to move ahead with submitting this project that seems like a reasonable middle ground to take. Does not revoke/cure any 'harm done to others' but at least could indicate a 'right attitude' about what the actual source of the code may be.... Colin^Davies wrote: if you submit any work publicly for peer review, expect criticism. Criticism I can take (in fact its one way to tell if anyone 'noticed' the event), but as with any community; once the ire of the crowd is invoked, it seems that nothing else really matters much... in which case the value of the project could get lost in the fray....So in the spirit of keeping the peace, am choosing to tread carefully on to the field. However, I do want to say thanx for your taking the time to respond Just trying to keep the forces of entropy at bay
-
Colin^Davies wrote: I suggest that you be darn careful with what you do submit and if you are in doubt as to the origin of a code segment. Clearly mark it as such in your submission. That is a good point. If I decide to move ahead with submitting this project that seems like a reasonable middle ground to take. Does not revoke/cure any 'harm done to others' but at least could indicate a 'right attitude' about what the actual source of the code may be.... Colin^Davies wrote: if you submit any work publicly for peer review, expect criticism. Criticism I can take (in fact its one way to tell if anyone 'noticed' the event), but as with any community; once the ire of the crowd is invoked, it seems that nothing else really matters much... in which case the value of the project could get lost in the fray....So in the spirit of keeping the peace, am choosing to tread carefully on to the field. However, I do want to say thanx for your taking the time to respond Just trying to keep the forces of entropy at bay
RedZenBird wrote: once the ire of the crowd is invoked, it seems that nothing else really matters much... Yeah, when they want blood, nothing stops them. Also if you are in doubt as to something, you can easily run it buy the site owners or editors for an opinion. I think what we all hate is when somebody blatently copies something and claims it as their own work. Next would be when someone publishes something that is straight out copied and does not acknowledge the original author. Then you get into more grey-gray areas :(( Regardz Colin J Davies
Sonork ID 100.9197:Colin
You are the intrepid one, always willing to leap into the fray! A serious character flaw, I might add, but entertaining. Said by Roger Wright about me.
-
I've a pretty big project I'm considering posting to this site ... actually it is so big that I may start with just posting parts of it to start with....The trouble is that: Whenever I pull interesting code into my projects I will always move through it with a fine tooth come for the purposes of: 1. Seeking full understanding of how the code in that-something works. I don't like to pull stuff in without having a very good idea as to how it works. You know, how can I hope to debug/enhance anything if I don't even understand what it is doing. 2. Making the style of all the files in the project "internally consistent" when it comes to function names, class member variables, ProperCase on functions, hungarian notation, put in comments I deem appropriate, etc. etc. etc. In other words, I can mangle up the file pretty well. I do this so that as I'm working on a project I don't have to switch mental hats evertime I step into a new file/class. Some of these files have been mangled to the point that they bear little, if any, resemblance to whatever the original file was. Moreso, I can't even remember where some of this stuff comes from anymore, so while I am willing to give deference to previous authors, and give credit where credit is due, I don't think I can completely. So here is my question: If a project is posted that contains pieces-and-parts that are partially seeded off another coders work, but whatever comments the original authors put in is lost or severely mangled; how busted will I be with the other folks on this site? I've gotten 'wiser' lately and strive to keep original authors' comments intact, but I have to admit that was not always the case. So, do I dare post a project here or will I just get crushed by the public? On another related note: If a project contains code that is published in a book, or is from commercial libraries, then should not that code be compiled into a lib to protect the copyright of that authors/publishers and also protect this site from any kind of infringement issues? The project I'm thinking of posting could be of great interest to a lot of folks, but I don't want to create a firestorm of bad vibes / ill will. Thoughts anyone? Just trying to keep the forces of entropy at bay
Perhaps you could consider posting it with a simple disclaimer: I'm not sure who the original author is, but some of this code might look a lot like yours. If you feel you deserve credit, please let me know and I'll add recognition where appropriate. Just a thought. J