Changes for our software
This topic lists changes for the DODS/NVODS/OPeNDAP software. We may need to refine the exact notion because 'changes' can mean just about anything that's not already present. What I'm really going after are changes that replace the way something is done with a new implementation
or add a new wrinkle to what the software can do. This is
not the place to put ideas that will leads to major changes in the software's capabilities. For example, it's not the place to talk about the AIS.
- Builds: Continue to expand our use of the GNU autotools. This means starting to use
automake but it also means much more. This is a pretty complex topic, so I think we should devote a whole sub-page to just it. Lets call that page: SoftwareBuilds.
- Tests: Good tests are our friend. We have psychotic tests. As with the builds, tests are really complex because they are so pervasive. Lets start up a topic called SoftwareTests for it.
- Servers: Forget, for a moment, about the issue of revamping our server's dispatch software. We have a host of little problems lurking in our servers. Over time these have become a big drain on project because they draw internal resources and limit the input of external resources (i.e., broken software turns people off). Bugzilla, which is very good at tracking bugs, is not so good at listing these problems since they are not usually as fine grained as a bug. Lets call this topic ServerIssues.
- Refactoring: There's quite a bit of software that started life five or more years ago. In the intervening time the projects goals have changed, the web has changed, ... You know the drill. A refactoring is an organizational change in the software that doesn't introduce a new feature for users but does make it easier to make other changes which do result in new features. Lets call this topic SoftwareRefactoring.
--
JamesGallagher - 18 May 2004
