Documentation meets version control: an automated backup system for HTML-based help Export

@inproceedings{citeulike:5401847, abstract = {Software developers have used version control systems for years, to manage source code changes and to enable them to reproduce any given level of their software from the source code that created it. Most writing departments, however, tend to perform full-scale weekly backups at best or tempt fate by not performing any backups at worst. The two major reasons for this neglect of document version control are lack of adequate tools and the effort required by writers to deal with the inadequate tools presently available. This paper describes a tool I developed at IBM, the Automated Backup Manager (ABM), which attempts to connect the writer's documentation to a true source version control system, without reducing writer productivity}, author = {Green, R.}, booktitle = {Professional Communication Conference, 2000. Proceedings of 2000 Joint IEEE International and 18th Annual Conference on Computer Documentation (IPCC/SIGDOC 2000)}, citeulike-article-id = {5401847}, citeulike-linkout-0 = {http://dx.doi.org/10.1109/IPCC.2000.887311}, citeulike-linkout-1 = {http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=887311}, doi = {10.1109/IPCC.2000.887311}, journal = {Professional Communication Conference, 2000. Proceedings of 2000 Joint IEEE International and 18th Annual Conference on Computer Documentation (IPCC/SIGDOC 2000)}, keywords = {control, documentation, html, version}, pages = {541--548}, posted-at = {2009-08-09 20:30:44}, priority = {3}, title = {Documentation meets version control: an automated backup system for HTML-based help}, url = {http://dx.doi.org/10.1109/IPCC.2000.887311}, year = {2000} }

TY - CONF ID - citeulike:5401847 L3 - citeulike-article-id:5401847 N2 - Software developers have used version control systems for years, to manage source code changes and to enable them to reproduce any given level of their software from the source code that created it. Most writing departments, however, tend to perform full-scale weekly backups at best or tempt fate by not performing any backups at worst. The two major reasons for this neglect of document version control are lack of adequate tools and the effort required by writers to deal with the inadequate tools presently available. This paper describes a tool I developed at IBM, the Automated Backup Manager (ABM), which attempts to connect the writer's documentation to a true source version control system, without reducing writer productivity JF - Professional Communication Conference, 2000. Proceedings of 2000 Joint IEEE International and 18th Annual Conference on Computer Documentation (IPCC/SIGDOC 2000) EP - 548 TI - Documentation meets version control: an automated backup system for HTML-based help T2 - Professional Communication Conference, 2000. Proceedings of 2000 Joint IEEE International and 18th Annual Conference on Computer Documentation (IPCC/SIGDOC 2000) SP - 541 KW - control KW - documentation KW - html KW - version AU - Green, R PY - 2000/// UR - http://dx.doi.org/10.1109/IPCC.2000.887311 ER -