|
Why I Created the CTDP |
|
|
|
|
June 14, 2000My ObservationsI am an electrical engineer who has gradually been drawn more and more into the software arena. I have worked for several different company types ranging from government contractors to consumer electronics companies. I have been working in the industry for about twenty years. Over this period of time I have observed profound changes in the industry with re guard to:
The PaceI have found that new microprocessors come out so fast that if you don't purchase a new PC for two or three years, a microprocessor may be developed and obsoleted without any knowledge of the event. I have also noticed that many books that are published are obsolete before the ink is dry. This is especially true with the Linux operating system since new software and upgrades come out so often and there are so many packages. I have found that it is no longer possible to keep up with this pace as an individual. I may purchase a book today about XML, learn XML and become proficient within a few months. By this time someone has developed two more markup languages that I should at least be aware of. In the meantime two new incredible microprocessors have come out. Should I advise my management to use these technologies or not? The Documentation
Searching for a SolutionAs I became more keenly aware of the above problems I looked for ways to solve them. I began trying to put together more comprehensive documentation for my own use. Then I began to think, if I don't use this documentation on a wider scale and share it, it will be wasted since it will eventually become obsolete. So I began to call some of my friends and offer them the documentation and encourage them to pool knowledge with me so we could jointly help each other out. Unfortunately, this has not worked out as well as I'd hoped. One of my friends is commuting almost two hours per day to work (one way) and could not possibly have any time outside work to even read any documentation. Others are working long hours and have no time. Still I have not given up. The documentation that was written was meant to save time. For instance I have been working with Linux for almost three years. When I started, I wondered how it worked (engineering curiosity). I began investigating and as I did, I documented my findings. I put the findings in various Linux manuals as appropriate. I also noticed many people who are networking experts and are proficient with Windows operating systems were interested in learning Linux. Many times, questions are posted on the web asking where documentation can be found to help a beginner. There are, unfortunately, so many answers to that question the user may become even more confused. But the documentation I wrote was intended to help a beginner become as good with Linux as I now am, but only in a few weeks or months. This is because it contains my experiences with Linux in an organized and structured fashion. It gives tips on where to find help, how to use the system, and more. Save Time and Work TogetherSo I thought some windows experts should be able to use my documentation and come up to speed on Linux quickly. Perhaps some of those who saved time using my documentation could produce similar documentation for me and others to save others even more time. This way we can work together and help each other out. I believe humans were intended to work together. Why would we have written and spoken language if not? I also believe that the development of technology must be based on working together. No one person can possibly understand enough technology to build a computer from raw materials to the store shelf. This is part of the reason this project should be a huge benefit to both individuals and businesses. Searching for a SolutionWorking together on the web is the solution. Being someone who works with Linux, I had observed the Linux Documentation Project which is simply a collection of volunteers that support the Open Source community with programs and documentation. Linux was and is a product of the web. I considered joining the Linux Documentation Project but it didn't fit completely into what I wanted to do. I did not want to limit this effort to Linux alone, but wanted to get involved in several web languages and other technologies. So I looked for other organizations that I could join that had similar goals to mine. I found:
The GoalsSo what are the goals of this project and what should they be? I believe the following:
The SolutionTo accomplish the above goals, the best solution is the establishment of this Computer Technology Document Project (CTDP) with a supporting web site and associated e-mail group used as an aid in managing the project. This project must have stated goals, standards and policies to avoid misunderstanding between members. The CTDP should offer materials for sale in order to make material as widely available as possible and to allow those that do not wish to contribute to this project to use our material. This is fair to our contributors and allows members of the public to use our material. The BenefitsI believe this project will benefit both individuals like myself and business. Although originally intended to benefit individuals, I am now convinced that it will benefit businesses to a greater degree. For individuals it will accomplish the following:
ConclusionsI am convinced that this project is an idea that has now come of age. I'm convinced that this project can be a great benefit to individuals and our society. I am also convinced that conclusions about this project will be determined by the public and business.
Sincerely, |