Managing Software As Data » History » Version 9
Version 8 (Steve Welburn, 2012-11-13 03:46 PM) → Version 9/19 (Steve Welburn, 2012-11-13 03:47 PM)
h1. Managing Software As Data
The same issues as for data arise:
* [[Backing_up|Backing up]]
* Documentation
However, whereas data changes slowly / infrequently, software is subject to ongoing changes during a project. Source code for software usually consists of text files and should therefore be stored in a suitable version control system (e.g. "Mercurial":http://mercurial.selenic.com/, "Subversion":http://subversion.apache.org/, "git":http://git-scm.com/). Additionally, binary releases of software may be created as downloads for a project.
Additionally, documentation has broader requirements - including both documentation to make the code maintainable (e.g. comments in the code, documenting APIs, Javadoc style documentation) and user documentation to explain how to install and use the software.
The "Sound Software":http://www.soundsoftware.ac.uk project provides software project management facilities for digital music and audio research including Mercurial version control, downloads, documentation, issue lists and wikis through its "code repository":http://code.soundsoftware.ac.uk
Other possible repositories for source code include:
* "Sourceforge":http://sourceforge.net/ (Subversion, git, Mercurial, Bazaar, CVS)
* "Google code":http://code.google.com/ (Subversion, git, Mercurial)
* "github":https://github.com/ (git)
* "bitbucket":https://bitbucket.org/ (git, Mercurial)
The Sound Software project information on "choosing a version control system":http://soundsoftware.ac.uk/version-control-what-system-to-use and provides an easy-to-use graphical client for use with Mercurial. system":http://soundsoftware.ac.uk/version-control-what-system-to-use.
The same issues as for data arise:
* [[Backing_up|Backing up]]
* Documentation
However, whereas data changes slowly / infrequently, software is subject to ongoing changes during a project. Source code for software usually consists of text files and should therefore be stored in a suitable version control system (e.g. "Mercurial":http://mercurial.selenic.com/, "Subversion":http://subversion.apache.org/, "git":http://git-scm.com/). Additionally, binary releases of software may be created as downloads for a project.
Additionally, documentation has broader requirements - including both documentation to make the code maintainable (e.g. comments in the code, documenting APIs, Javadoc style documentation) and user documentation to explain how to install and use the software.
The "Sound Software":http://www.soundsoftware.ac.uk project provides software project management facilities for digital music and audio research including Mercurial version control, downloads, documentation, issue lists and wikis through its "code repository":http://code.soundsoftware.ac.uk
Other possible repositories for source code include:
* "Sourceforge":http://sourceforge.net/ (Subversion, git, Mercurial, Bazaar, CVS)
* "Google code":http://code.google.com/ (Subversion, git, Mercurial)
* "github":https://github.com/ (git)
* "bitbucket":https://bitbucket.org/ (git, Mercurial)
The Sound Software project information on "choosing a version control system":http://soundsoftware.ac.uk/version-control-what-system-to-use and provides an easy-to-use graphical client for use with Mercurial. system":http://soundsoftware.ac.uk/version-control-what-system-to-use.