No its not some sort of silly mind game. Its called:
what are you going to copy and why. Which you answer further down.
It might perhaps seem weird at the first sight. It is far tougher to write programs this way, but I have better confidence that whenever I will need, I will be able to figure out how my programs (I have written some time ago) work. This is sort of complete memory dump.
These are my (perhaps silly) ideals.
Concerning operating systems, it is only natural, to weave information about hardware details into the document/program. I have started to look around for decent descriptions of devices I started to play with. Your site provides good content. I was interested to the license of that content.
I do not care.. Why would I care if I were to stay on topic?
I very well understand that there are tons of licenses and people tend to disaggree on them (license wars). The fact that your wiki has does not state the license explicitely has unpleasant implications and I wanted to be sure about that.
I am sure we about to find out why it has unpleasent implications.
The war over operating system market is over. I am skeptical if it is still possible to make money by coming up with a new operating system and start selling it.
I do not remember saying anything about operating systems.
I would actually have a problem with someone copying pasting the someone else's expression of a idea for the purpose of themselves producing a document. If this is the case why can you just not write it in you're own words? Since there is no way to verify you're intentions of doing so. You might want to make a lot of money and I think who wrote it is entitled to compensation of such things.
I mean a expression of a idea in writing. The actual document text, and unlikely the example code I am sure which I can be certain of so I must say (below) for a general fit anywhere case:
Point A
How about you come up with you're own example code? At the least do not just copy and paste something. I am sure there are about one hundred different ways to implement something, or am I wrong?
Or, when using some common sense and some experience working on this level. The code in that document appears to be so general as I could never think that it could be copyrighted or even brought up as a copyright infringement. Simply changing a few register names should be a absolutely effective way.
You answered my question by talking about:
kosik wrote:
It might perhaps seem weird at the first sight. It is far tougher to write programs this way, but I have better confidence that whenever I will need, I will be able to figure out how my programs (I have written some time ago) work. This is sort of complete memory dump.
This means you are not copying code. So some common sense would say no problem here. I would hope you can come to this conclusion.
I am mostly interested in the text. Rephrasing the data-sheets just to be sure that I have a copyright on it seems to me as a waste of time and it is quite boring. That is why I looked around for good content and tried to use it.
I appreciate the honesty, but you actually make no sense after the first sentence. However since you implied that you find looking through the data-sheets for a copyright notice a waste of time I assume you would like to copy the actual information about the device. Of course I notice in you're document you already have the actual information. So I assume what you want to do is copy the actual
content.
Point B
This of course is not a good idea. Someone took time to write that. Actually some people have edited it and change the look almost completely over time it appeared by looking back through the change logs on the wiki. You have some distinct parts to that wiki page:
code blocks - See
Point A
text blocks - See
Point B
tables of information - See
Point C
Point C
It is already known that information can not be copyrighted. Instead the expression of the information can be copyrighted. You have the information by comprehending the expression of it therefore it should be feasible to come up with you're own expression of this information with out resorting to copy and paste tactics just to save time because you feel lazy about doing it. By reading the document you just comprehended it. This means you now have the information in you're head and you may expression this how you like. Copying a already existing expression of this information is not good.
There should be numerous options instead of copy and pasting a expression of a idea or information. You can copy the information but not how it is expression in it's entirety. This is called copying someone elses work and calling you own. If you go into this world you are own you own and for no good reason did you enter it but just to be lazy about it in the first place.
So the problem would
not be:
- Copying the information.
- Copying the source code when you are going to translate it into some abstract language that will bear no resemblance.
The problem would be:
- Copying the expression of this information and accompanying source code in whole, and of course the source code in whole part can have some exceptions which are mentioned in
Point A (above).
To do that legaly, I have to know the license.
If that were not possible, I would at least try to do it in a moral way. That is, by explicitely citing all the information sources I used.
You are confusing me here. Do you want to copy the information or the expression of this information. How about you give a example of what it would look like when you copy it from the wiki then we could figure out if it is ok to do that or not?
And to try once more to help you understand:
- The problem is copying the expression of information.
- The problem is
not copying the information.
- The problem has nothing to do with a operating system or kernel.
And: I hold no control over the Wiki. I do not host it nor do I host this site or have any personal or business affiliation with anyone who does. You really must talk to someone else like
Combuster who made a post right after I did (above).
If this is too complicated for you to understand then you need to ask someone to clarify it for you further or educate you're self. Ignorance is no step aside or excuse for a mistake when you screw up instead it is simple a reason. The world is complicated and it is not going to get any easy any time soon. If you just can not comprehend what I am talking about them keep thinking about it until you do.
That's not my name SpooK.