Mission: Difference between revisions
No edit summary |
No edit summary |
||
Line 3: | Line 3: | ||
So, wiki. | So, wiki. | ||
The intended scope of this wiki is information relating to pretty much any computer from Radio Shack. I personally am not very interested in many of | The intended scope of this wiki is information relating to pretty much any computer from Radio Shack. I personally am not very interested in many of their later standard Intel/IBM PC clone machines, but I won't exclude that info if you want to add it. | ||
Initially I'm just going to dump wiki versions of some various notes and recipes that I have been keeping in Google Drive and Google Photos, and even Facebook posts. And just start building a plain disorganized list of them here as an index. Over time, the organization can be improved, just as the content itself can. Hell, at first the "content" will just be links to the the Google Drive folders | Initially I'm just going to dump wiki versions of some various notes and recipes that I have been keeping in Google Drive and Google Photos, and even Facebook posts. And just start building a plain disorganized list of them here as an index. Over time, the organization can be improved, just as the content itself can. Hell, at first the "content" will just be links to the the Google Drive folders. It's a start. | ||
This info is wildly incomplete. It is intended to be filled-in over time, rather than be compiled and presented as a finished product | This info is wildly incomplete. It is intended to be filled-in over time, rather than be compiled and presented as a finished product. It is a place where anyone can place anything Tandy related, but does NOT claim to already have everything Tandy related. | ||
But ideally, I hope to create a shared resource that outlives myself, and not just as a static copy. In 20 years, Half of the details I document today will be obsolete. In 20 years, the OSHPark and DigiKey links in an article that documents how to build a gadget today will be obsolete. A reader from that time should be able to hop in and update it with the current equivalent info, whatever that is at the time. An original article today might say "you can buy this gear here...", but tomorrow it should be able to be updated to "you can print this gear from this file...". It may, should even, still contain the original historical info for reference, but also updated info. | At first it will just have a few small things I personally have figured out and wish to document somewhere. What happens after that I don't really care that much. If no one else ever adds anything, that's fine. I'm still getting what I want, which is just a better way to host things I want to document myself than Google Drive folders. | ||
But ideally, I hope to create a shared resource that outlives myself, and not just as a static copy. In 20 years, Half of the details I document today will be obsolete. In 20 years, the OSHPark and DigiKey links in an article that documents how to build a gadget today will be obsolete. A reader from that time should be able to hop in and update it with the current equivalent info, whatever that is at the time. An original article today might say "you can buy this gear here...", but tomorrow it should be able to be updated to "you can print this gear from this file...". It may, should even, still contain the original historical info for reference, but also updated info. <nowiki>[update:] Literally <-- THIS has already just happened. The CGP-115 article originally had info I found about how to get a particular special gear from r/c helecopter hobby parts suppliers, and now there is a 3-D printed version available.[/update]</nowiki> |
Latest revision as of 18:48, 26 April 2017
There is a LOT of info out there already, in the form of several web sites and forums and mail lists, but they are all either static archives of old info, or ephemeral conversations. No ongoing living documentation. People struggle to learn things, and then that knowledge is largely lost again, because web site authors lose interest or lose the battle with time, and the info goes out of date or goes lost entirely. Sometimes you can find old info in archives of mail lists, but then when what you find is incomplete or partially incorrect or obsolete, you can't go back and correct it or update it for the next guy.
So, wiki.
The intended scope of this wiki is information relating to pretty much any computer from Radio Shack. I personally am not very interested in many of their later standard Intel/IBM PC clone machines, but I won't exclude that info if you want to add it.
Initially I'm just going to dump wiki versions of some various notes and recipes that I have been keeping in Google Drive and Google Photos, and even Facebook posts. And just start building a plain disorganized list of them here as an index. Over time, the organization can be improved, just as the content itself can. Hell, at first the "content" will just be links to the the Google Drive folders. It's a start.
This info is wildly incomplete. It is intended to be filled-in over time, rather than be compiled and presented as a finished product. It is a place where anyone can place anything Tandy related, but does NOT claim to already have everything Tandy related.
At first it will just have a few small things I personally have figured out and wish to document somewhere. What happens after that I don't really care that much. If no one else ever adds anything, that's fine. I'm still getting what I want, which is just a better way to host things I want to document myself than Google Drive folders.
But ideally, I hope to create a shared resource that outlives myself, and not just as a static copy. In 20 years, Half of the details I document today will be obsolete. In 20 years, the OSHPark and DigiKey links in an article that documents how to build a gadget today will be obsolete. A reader from that time should be able to hop in and update it with the current equivalent info, whatever that is at the time. An original article today might say "you can buy this gear here...", but tomorrow it should be able to be updated to "you can print this gear from this file...". It may, should even, still contain the original historical info for reference, but also updated info. [update:] Literally <-- THIS has already just happened. The CGP-115 article originally had info I found about how to get a particular special gear from r/c helecopter hobby parts suppliers, and now there is a 3-D printed version available.[/update]