{"id":1485,"date":"2025-10-24T15:43:41","date_gmt":"2025-10-24T22:43:41","guid":{"rendered":"https:\/\/mcjones.org\/dustydecks\/?p=1485"},"modified":"2025-10-25T20:22:16","modified_gmt":"2025-10-26T03:22:16","slug":"the-software-preservation-group","status":"publish","type":"post","link":"https:\/\/mcjones.org\/dustydecks\/archives\/2025\/10\/24\/1485\/","title":{"rendered":"The Software Preservation Group"},"content":{"rendered":"\n
\"\"<\/a><\/figure>\n\n\n\n

Twenty-two years ago the Computer History Museum established an advisory committee (with staff, trustees, and volunteers) to  explore issues of identifying, collecting, preserving, and presenting software. The Museum had just moved into its present quarters; the main Revolution exhibit was still far in the future. But  the previous year, Grady Booch had gotten the ball rolling with a mass email entitled \u201cPreserving classic software products<\/a>\u201d asking for people’s \u201ctop ten list of classic software products.\u201d The replies to that email and the ensuing discussion made it clear that software collection and preservation were worth doing and needed to begin immediately, before more pioneers died and more source code was lost or destroyed.<\/p>\n\n\n\n

Monthly meetings<\/a> of the Software Collection Committee began in November 2003, covering a wide range of topics. Should collection be proactive or reactive? What priorities should guide proactive collecting? (Grady\u2019s compiled top-ten lists<\/a> provided initial input.) How should software be cataloged? How should it be presented? An initial workshop<\/a> in October 2003 mostly asked questions, but a follow-up<\/a> in May 2006 showed off work from CHM and from other organizations and individuals.<\/p>\n\n\n\n

While many discussions raged for months, restless folks began \u201cpilot projects\u201d to collect materials from the original IBM 704 FORTRAN project, Doug Engelbart\u2019s NLS\/Augment project, and the APL programming language. A web site was set up to present the results of these pilot projects and the monthly meetings. An email list with an archive<\/a> allowed people who couldn\u2019t attend the meetings to participate in many discussions.<\/p>\n\n\n\n

As time passed, interest in software preservation expanded. The Museum opened its Revolution!<\/a> exhibit in 2011 followed by Make Software: Change the World!<\/a> in 2017. Its Software History Center<\/a> centralized and expanded the software-related curatorial staff. Source code releases<\/a> became a regular occurrence. Work also went on outside the Museum. Software Heritage<\/a>, founded by INRIA, maintains a replicated repository and populates it by crawling the world\u2019s open-source software \u201cforges\u201d such as GitHub.com. <\/p>\n\n\n\n

At the same time, the committee (renamed Software Preservation Group) lost mindshare: The meetings wound down in 2007, and traffic on the email list tapered down to a standstill by 2017. However, encouraged by the success of my original FORTRAN<\/a> project, I had continued with a series of projects including LISP<\/a> and C++<\/a>. After retiring in 2010 I took on larger projects on ALGOL, Prolog, SETL, and BCPL and smaller ones on GEDANKEN, Mesa, PAL, and Poplar, plus program verification systems AFFIRM and PIVOT. Along the way, a few other people found their way to the Software Preservation Group, and created projects: Interactive C Environments<\/a> (Wendell R. Pepperdine), Emacs<\/a> (Lars Brinkhoff), and FOCAL<\/a> (Bruce Ray).<\/p>\n\n\n\n

By 2025, the \u201cProjects\u201d section of the Software Preservation Group web site was still serving a useful purpose, but the overall web site was showing its age: the landing page suggested activities no longer in progress, the underlying Plone content management  system hadn\u2019t been updated in 20 years created a burden on the Museum\u2019s IT group to keep running and backed-up, and the use of a different domain deemphasized the connection to the Museum. Discussions with David Brock and Hansen Hsu of the Museum\u2019s Software History Center led to the idea of rebuilding the web site with static HTML on a subdomain of the Museum\u2019s regular computerhistory.org.<\/p>\n\n\n\n

As the author of most of the content, I took on this effort in July 2025. It was fairly easy to convert the project web pages I\u2019d created, but I wasn\u2019t sure what to do with projects created by others that had seen little or no activity for years and decades. I managed to contact the original authors, and worked with them to tidy things up (especially Emacs). I also tracked down materials from the 2003 workshop, almost all the meetings (agendas, minutes, and presentation handouts), and the email archive.<\/p>\n\n\n\n

While waiting for word back from the NLS\/Augment and APL projects, I couldn\u2019t resist starting a brand-new project: the Modula-3<\/a> programming language. That will be the subject of another post.<\/p>\n\n\n\n

So please visit the new web site at:<\/p>\n\n\n\n

https:\/\/softwarepreservation.computerhistory.org\/<\/a><\/blockquote>\n\n\n\n

Most links to the old web site will be automatically redirected. If you see things amiss, let me know.<\/p>\n\n\n\n

<\/p>\n","protected":false},"excerpt":{"rendered":"

Twenty-two years ago the Computer History Museum established an advisory committee (with staff, trustees, and volunteers) to  explore issues of identifying, collecting, preserving, and presenting software. The Museum had just moved into its present quarters; the main Revolution exhibit was still far in the future. But  the previous year, Grady Booch had gotten the ball … Continue reading “The Software Preservation Group”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1,2],"tags":[],"class_list":["post-1485","post","type-post","status-publish","format-standard","hentry","category-general","category-software-history"],"_links":{"self":[{"href":"https:\/\/mcjones.org\/dustydecks\/wp-json\/wp\/v2\/posts\/1485","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mcjones.org\/dustydecks\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mcjones.org\/dustydecks\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mcjones.org\/dustydecks\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/mcjones.org\/dustydecks\/wp-json\/wp\/v2\/comments?post=1485"}],"version-history":[{"count":5,"href":"https:\/\/mcjones.org\/dustydecks\/wp-json\/wp\/v2\/posts\/1485\/revisions"}],"predecessor-version":[{"id":1508,"href":"https:\/\/mcjones.org\/dustydecks\/wp-json\/wp\/v2\/posts\/1485\/revisions\/1508"}],"wp:attachment":[{"href":"https:\/\/mcjones.org\/dustydecks\/wp-json\/wp\/v2\/media?parent=1485"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mcjones.org\/dustydecks\/wp-json\/wp\/v2\/categories?post=1485"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mcjones.org\/dustydecks\/wp-json\/wp\/v2\/tags?post=1485"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}